On Thu, Mar 9, 2017, 3:11 PM Oved Ourfali <oourf...@redhat.com> wrote:
> Both hosts are Up. > When you try to add the label the host is still not up, but a few seconds > later it moves to Up. > We are not sure why they were not up though. Y. > > On Thu, Mar 9, 2017 at 2:55 PM, Dan Kenigsberg <dan...@redhat.com> wrote: > > On Thu, Mar 9, 2017 at 1:50 PM, Daniel Belenky <dbele...@redhat.com> > wrote: > > Test failed: basic_sanity.assign_hosts_network_label > > > > Link to failed job: test-repo_ovirt_experimental_master/5754 > > > > Link to all logs: logs from Jenkins > > > > Error snippet from log: > > > > lago.utils: ERROR: Error while running thread > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in > > _ret_via_queue > > queue.put({'return': func()}) > > File > > > "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/005_network_by_label.py", > > line 56, in _assign_host_network_label > > host_nic=nic > > File > > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", > line > > 16231, in add > > headers={"Correlation-Id":correlation_id, "Expect":expect} > > File > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", > > line 79, in add > > return self.request('POST', url, body, headers, cls=cls) > > File > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", > > line 122, in request > > persistent_auth=self.__persistent_auth > > File > > > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", > > line 79, in do_request > > persistent_auth) > > File > > > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", > > line 162, in __do_request > > raise errors.RequestError(response_code, response_reason, > response_body) > > RequestError: > > status: 409 > > reason: Conflict > > detail: Cannot add Label. Operation can be performed only when Host > status > > is Maintenance, Up, NonOperational. > > Leon, could you look into this job's engine.log? I suspect that the > added log entry there would state that the host has fallen off to > non-responding. If so, I suspect a bug in the transport layer. > _______________________________________________ > > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > > _______________________________________________ > Devel mailing list > de...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra