Importing nodes before any images are registered causes the CLI to hang

Bug #1645296 reported by Dougal Matthews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Dougal Matthews

Bug Description

If you run the command "openstack overcloud node import ~/instackenv.json" before registering images in Glance (because it failed or you skipped a step) then the CLI command will hang forver.

The Mistral workflow will actually fail, but this has exposed a bug in Mistral that causes the Workflow to never be marked as errored - it is stuck in the RUNNING state. See: https://bugs.launchpad.net/mistral/+bug/1645295

We should make sure that all error values we pass to the Result class are converted to strings.

Changed in tripleo:
status: Confirmed → In Progress
Dougal Matthews (d0ugal)
tags: added: tripleoclient
Changed in tripleo:
milestone: none → ocata-3
Ryan Brady (rbrady)
Changed in tripleo:
milestone: ocata-3 → ocata-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

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

commit 0aee2ceb3ca2b26e5271f357b68deca912668f89
Author: Dougal Matthews <email address hidden>
Date: Mon Nov 28 12:35:09 2016 +0000

    Convert exceptions to strings when passing them to the Result class

    The Mistral Result class expects the error property to be either a
    string or a dict. Other types, like exceptions, can cause errors in
    mistral which in turn cause a critical failure. See the Mistral bug
    report: https://bugs.launchpad.net/mistral/+bug/1645295

    This change also updates one use of the Result class that doesn't use
    kwargs.

    Change-Id: Ia93f298e5181bae92d7a08468d33c255d38b996a
    Closes-Bug: #1645296

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

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

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.