tripleo

_introspect workflow doesn't include node uuid on failure

Bug #1717268 reported by Honza Pokorny
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Dougal Matthews
tripleo queens-1

Bug Description

The tripleo.baremetal.v1._introspect workflow sends a message to zaqar on failure. The error message doesn't contain the uuid of the node that failed to be introspected. The UI depends on it.

Honza Pokorny (hpokorny)
tags: added: pike-backport-potential workflows
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

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

Changed in tripleo:
assignee: nobody → Dougal Matthews (d0ugal)
status: Triaged → In Progress
Emilien Macchi (emilienm)
Changed in tripleo:
milestone: none → queens-1
Revision history for this message
Honza Pokorny (hpokorny) wrote :

Sorry, I made a mistake. This isn't actually necessary. I was inspecting the message that arrived, and the "introspected_node" value was empty. The GUI code that I mentioned actually uses the execution's input to determine which node was being worked on. While this doesn't hurt anything, it's not necessary.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/504068
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=da67c5051c6cdea76d2585e9e6ec3b8c64b3a1fb
Submitter: Jenkins
Branch: master

commit da67c5051c6cdea76d2585e9e6ec3b8c64b3a1fb
Author: Dougal Matthews <email address hidden>
Date: Thu Sep 14 15:41:17 2017 +0100

    Add the Node UUID to the failure messages from the _introspect workflow

    Closes-Bug: #1717268
    Change-Id: If3b69d8d54ff6ccdd48e80ec267b9eae9dbd7ddf

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 8.0.0

This issue was fixed in the openstack/tripleo-common 8.0.0 release.

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.