azblk handler: Fix http error reply being printed to stdout or applied to nbd device
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf install --refresh --advisory=FEDORA-2019-20aa23d56e \*Please log in to add feedback.
This update has been submitted for testing by xiubli.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been submitted for testing by xiubli.
This update has been pushed to testing.
Tested it and works for me.
uname -a
Linux f305.1.18-300.fc30.x86_64 #1 SMP Mon Jul 15 15:42:34 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
rpm -qli nbd-runner
Name : nbd-runner Version : 0.4 Release : 3.fc30 Architecture: x86_64 Install Date: Fri 26 Jul 2019 09:13:31 AM IST Group : Unspecified Size : 247690 License : GPLv2 or LGPLv3+ Signature : (none) Source RPM : nbd-runner-0.4-3.fc30.src.rpm Build Date : Thu 25 Jul 2019 07:01:15 PM IST Build Host : buildhw-10.phx2.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : https://github.com/gluster/nbd-runner Bug URL : https://bugz.fedoraproject.org/nbd-runner Summary : A daemon that handles the IO requests from NBD devices in server side Description : A daemon that handles the userspace side of the NBD (Network Block Device) back-store. /etc/sysconfig/nbd-runner /usr/lib/.build-id /usr/lib/.build-id/62 /usr/lib/.build-id/62/ab7e2e2f3f5c9edd11499552d105da4b8faa1b /usr/lib/.build-id/ac /usr/lib/.build-id/ac/47fa7a4a787c6e2d9fa8e514558cfa1cfdcd50 /usr/lib/.build-id/c9 /usr/lib/.build-id/c9/d34e1748cd6a19eb92242af8c4b536a6c0eadc /usr/lib/.build-id/f9 /usr/lib/.build-id/f9/c31112bfa6d8a99f555bb9d07df9e0d36da011 /usr/lib/systemd/system/nbd-runner.service /usr/lib64/nbd-runner /usr/lib64/nbd-runner/libazblk_handler.so /usr/lib64/nbd-runner/libutils.so /usr/lib64/nbd-runner/libutils.so.0 /usr/lib64/nbd-runner/libutils.so.0.0.0 /usr/sbin/nbd-cli /usr/sbin/nbd-runner /usr/share/doc/nbd-runner /usr/share/doc/nbd-runner/README.md /usr/share/licenses/nbd-runner /usr/share/licenses/nbd-runner/COPYING-GPLV2 /usr/share/licenses/nbd-runner/COPYING-LGPLV3 /usr/share/man/man8/nbd-cli.8.gz /usr/share/man/man8/nbd-runner.8.gz /var/log/nbd-runner/nbd-runner-glfs.log /var/log/nbd-runner/nbd-runner.log
systemctl daemon-reload; systemctl restart nbd-runner; systemctl status nbd-runner
● nbd-runner.service - Network Block Device For Distributed Storages Loaded: loaded (/usr/lib/systemd/system/nbd-runner.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2019-07-26 09:13:40 IST; 15ms ago Main PID: 24460 (nbd-runner) Tasks: 2 (limit: 2353) Memory: 1.0M CGroup: /system.slice/nbd-runner.service └─24460 /usr/sbin/nbd-runner threads 2
Jul 26 09:13:40 f30 systemd[1]: Started Network Block Device For Distributed Storages. Jul 26 09:13:40 f30 nbd-runner[24460]: create_file_output:510: log file path now is '/var/log/nbd-runner/nbd-runner.log' Jul 26 09:13:40 f30 nbd-runner[24460]: main:335: Starting... Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_open_handlers:1185: num_handlers: 1 Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_parse_from_json_config_file:342: handler type 0 is not registered! Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_parse_from_json_config_file:342: handler type 0 is not registered! Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_parse_from_json_config_file:342: handler type 0 is not registered! Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_parse_from_json_config_file:342: handler type 0 is not registered! Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_parse_from_json_config_file:342: handler type 0 is not registered! Jul 26 09:13:40 f30 nbd-runner[24460]: nbd_parse_from_json_config_file:342: handler type 0 is not registered!
And the spec file looks good.
Thanks.
The .spec looks goot to me. Thanks xiubo.
This update can be pushed to stable now if the maintainer wishes
Tested azblk handler and nbd-runner. Looks good.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.