Created attachment 1577180 [details] terminal log Description of problem: yum reports Failed to get unit file state for ovn-northd.service: No such file or directory /var/tmp/rpm-tmp.5P3a0a: line 5: [: =: unary operator expected Failed to get unit file state for ovirt-provider-ovn.service: No such file or directory /var/tmp/rpm-tmp.5P3a0a: line 5: [: =: unary operator expected Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. update rhv-openvswitch on host 2. 3. Actual results: warning is shown Expected results: no warning is shown Additional info: rhv-openvswitch noarch 1:2.10-6.el7ev
error message on clean install on rhvm: Failed to get unit file state for openvswitch.service: No such file or directory /var/tmp/rpm-tmp.ap2vYM: line 5: [: =: unary operator expected Failed to get unit file state for ovn-northd.service: No such file or directory /var/tmp/rpm-tmp.ap2vYM: line 5: [: =: unary operator expected Failed to get unit file state for ovirt-provider-ovn.service: No such file or directory /var/tmp/rpm-tmp.ap2vYM: line 5: [: =: unary operator expected Failed to get unit file state for ovn-controller.service: No such file or directory /var/tmp/rpm-tmp.ap2vYM: line 5: [: =: unary operator expected
Let us just remove the "/var/tmp/rpm-tmp.ap2vYM: line 5: [: =: unary operator expected" and keep the "Failed to get unit file state for openvswitch.service: No such file or directory"
FWIW, I get the same messages when installing rhv-openvswitch-1:2.11-4.el8ev.
(In reply to Miguel Duarte Barroso from comment #4) > Created attachment 1582600 [details] > double quote all the variables > > Dominik, do you mind checking if this patch addresses this issue ? Yes, looks good, thanks for the fix! Can you push this to rhv-openvswitch/refs/rhevm-4.4-* ?
Ouch, a bash-bigginer's bug of mine.
*** Bug 1725018 has been marked as a duplicate of this bug. ***
Verified with rhv-4.4.0 rhv-openvswitch-2.11-6.el8ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHV Engine and Host Common Packages 4.4), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:3309