openstack overcloud node delete doesn't require --stack but also doesn't default to overcloud

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

Bug Description

The command should either default the value to "overcloud" (as we do in other places) or it should require that the user provides it.

At the moment it will fail as it can't find the stack "None" with a confusing error.

The third option would be to give a better error and don't start the workflow with a None stack.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (master)

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

Changed in tripleo:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (master)

Reviewed: https://review.openstack.org/395522
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=0af664656d82ab5d658228cd078691f9abc3e789
Submitter: Jenkins
Branch: master

commit 0af664656d82ab5d658228cd078691f9abc3e789
Author: Dougal Matthews <email address hidden>
Date: Wed Nov 9 10:49:47 2016 +0000

    Default the stack name to 'overcloud' in overcloud node delete

    The stack needs to be passed as either a CLI arg with --stack or via the
    environment variable OVERCLOUD_STACK_NAME. At the moment if it isn't
    provided either way the workflow is called with an empty string for the
    stack name. This will then fail.

    This change defaults the stack name to 'overcloud' which matches the
    deploy command. One of the unit tests was updated so that it didn't pass
    the default value to ensure that it can still be overwritten.

    Change-Id: Ie44d5cba90e81ae1a35a4cabc6e20a202bfddef0
    Closes-Bug: #1640244
    Partial-Bug: #1640770

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

This issue was fixed in the openstack/python-tripleoclient 5.5.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/404324

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (stable/newton)

Reviewed: https://review.openstack.org/404324
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=2ed71e8e857bd69100d12c9ac67dd034b6c3d3f1
Submitter: Jenkins
Branch: stable/newton

commit 2ed71e8e857bd69100d12c9ac67dd034b6c3d3f1
Author: Dougal Matthews <email address hidden>
Date: Wed Nov 9 10:49:47 2016 +0000

    Default the stack name to 'overcloud' in overcloud node delete

    The stack needs to be passed as either a CLI arg with --stack or via the
    environment variable OVERCLOUD_STACK_NAME. At the moment if it isn't
    provided either way the workflow is called with an empty string for the
    stack name. This will then fail.

    This change defaults the stack name to 'overcloud' which matches the
    deploy command. One of the unit tests was updated so that it didn't pass
    the default value to ensure that it can still be overwritten.

    Change-Id: Ie44d5cba90e81ae1a35a4cabc6e20a202bfddef0
    Closes-Bug: #1640244
    Partial-Bug: #1640770
    (cherry picked from commit 0af664656d82ab5d658228cd078691f9abc3e789)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 5.4.1

This issue was fixed in the openstack/python-tripleoclient 5.4.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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