tempest

Baremetal scenario has hardcoded value for wait-callback timeout

Bug #1526466 reported by Michael Turek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Mauro S M Rodrigues

Bug Description

In the baremetal scenario, we wait for the node to reach the wait-callback or active state. Currently this timeout is hard-coded as 15 seconds. Arguably, this value should be configurable.

Michael Turek (mjturek)
Changed in tempest:
assignee: nobody → Michael Turek (mjturek)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/258027

Changed in tempest:
status: New → In Progress
OpenStack Infra (hudson-openstack)
Changed in tempest:
assignee: Michael Turek (mjturek) → Mauro S M Rodrigues (maurosr)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tempest (master)

Change abandoned by Michael Turek (<email address hidden>) on branch: master
Review: https://review.openstack.org/258027
Reason: Abandoning this change as the ironic tests are moving to the ironic tree. New review here https://review.openstack.org/#/c/269249

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/ironic 5.0.0

This issue was fixed in the openstack/ironic 5.0.0 release.

Ghanshyam Mann (ghanshyammann)
Changed in tempest:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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