ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
Description
Activity
Dafna Ron August 16, 2018 at 10:08 AM
The issue was a change on centos ppc package name which caused vdsm to fail when it fetch noarch packages
Danken created a fix and this can be closed
Dafna Ron August 9, 2018 at 12:15 PM
check-merge is not related to the packages missing since they are build in the build-artifacts that succeeded.
However, from the check-merge we can see that Edi's patch: https://gerrit.ovirt.org/#/c/93546/
also failed CQ which is why we are missing those packages.
I re-triggered the patch and then I can re-check the packages.
Edward Haas August 8, 2018 at 2:04 PM
As mentioned in the error:
'1.2.3.256/255.255.0.0' does not appear to be an IPv4 or IPv6 interface
1.2.3.256 is not a valid IP, but this may just be a result of a real check in the tests.
Piotr Kliczewski August 8, 2018 at 8:45 AM
This could be related to check-merge job [1] failure. I checked the logs and found that functional tests were unable to connect to vdsm:
2018-08-07 19:34:39,578::ssh.py::get_ssh_client::367::lago.ssh:EBUG::Socket error connecting to vdsm_functional_tests_host-el7: timed out
2018-08-07 19:34:39,579::ssh.py::get_ssh_client::381::lago.ssh:EBUG::Still got 99 tries for vdsm_functional_tests_host-el7
2018-08-07 19:34:43,587::ssh.py::get_ssh_client::367::lago.ssh:EBUG::Socket error connecting to vdsm_functional_tests_host-el7: [Errno None] Unable to connect to port 22 on 192.168.200.2
I checked that vdsm log and found setupNetwork failure:
Aug 7 15:20:50 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR u'1.2.3.4/' does not appear to be an IPv4 or IPv6 interface#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in _call_#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, "u'1.2.3.4/' does not appear to be an IPv4 or IPv6 interface")
Aug 7 15:20:50 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR gateway or netmask were given without ip address#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in _call_#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, 'gateway or netmask were given without ip address')
Aug 7 15:20:50 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR gateway or netmask were given without ip address#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in _call_#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, 'gateway or netmask were given without ip address')
Aug 7 15:20:51 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR u'1.2.3.256/255.255.0.0' does not appear to be an IPv4 or IPv6 interface#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in _call_#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, "u'1.2.3.256/255.255.0.0' does not appear to be an IPv4 or IPv6 interface")
@danken @Edward Haas have you seen it before?
[1] https://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/225/
Eyal Edri August 8, 2018 at 7:54 AM
we need both, cc @Piotr Kliczewski and @Francesco Romani
Dafna Ron August 8, 2018 at 7:25 AM
@danken @Sandro Bonazzola
which of these packages are actually needed? https://pastebin.com/AEVtv8gv
do we need vdsm-jsonrpc or just vdsm-jsonrpc-java?
if we do need vdsm-jsonrpc then we have a lower version in tested.
Dafna Ron August 8, 2018 at 7:01 AMEdited
here are the logs and full build:
https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2810/
https://pastebin.com/Ry4UHhtM
I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java.
will re-run reposync tool and also look into the package and where its coming from