ovb 3ctlr 1comp pike consistently failing to register node

Bug #1758143 reported by Rafael Folco
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Undecided
Unassigned

Bug Description

2018-03-22 15:42:30 | No valid host was found. Reason: No conductor service registered which supports driver pxe_ipmitool. (HTTP 400)

2018-03-22 15:42:22 | + openstack overcloud node import instackenv.json
2018-03-22 15:42:27 | Waiting for messages on queue '79942ba7-a2e8-4105-9a6f-16c15367ba36' with no timeout.
2018-03-22 15:42:30 | Exception registering nodes: No valid host was found. Reason: No conductor service registered which supports driver pxe_ipmitool. (HTTP 400)
2018-03-22 15:42:30 | Started Mistral Workflow tripleo.baremetal.v1.register_or_update. Execution ID: c59f5ac8-99f7-4375-8bc7-3f4a1289cb3c
2018-03-22 15:42:30 |
2018-03-22 15:42:30 | No valid host was found. Reason: No conductor service registered which supports driver pxe_ipmitool. (HTTP 400)

https://logs.rdoproject.org/05/555305/2/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-pike-branch/Z2f09609996af4bada201376880d8e099/undercloud/home/jenkins/overcloud_prep_images.log.txt.gz#_2018-03-22_15_42_22

All jobs failing the same way:

https://logs.rdoproject.org/89/554889/3/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-pike-branch/Zc6acfbc0c0ba443595b315d3416a0c9a/undercloud/home/jenkins/overcloud_prep_images.log.txt.gz

https://logs.rdoproject.org/51/555251/2/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-pike-branch/Z7afa9b59c9024251a0a15aa1695dbc89/undercloud/home/jenkins/overcloud_prep_images.log.txt.gz

https://logs.rdoproject.org/05/554705/2/openstack-check/gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-pike-branch/Z6f99897237c641b08fe341bef7d6c0c5/undercloud/home/jenkins/overcloud_prep_images.log.txt.gz

Tags: ci ovb pike
Revision history for this message
Rafael Folco (rafaelfolco) wrote :

No longer see this failure. Re-open if the issue happens again.

Changed in tripleo:
status: Triaged → Invalid
milestone: rocky-1 → none
importance: High → Undecided
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.