tripleo

Strange output of "openstack baremetal configure boot"

Bug #1619717 reported by Dmitry Tantsur on 2016-09-02

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tripleo	Fix Released	Low	Julie Pichon	tripleo newton-rc1 "newton-rc1"

Bug Description

Here's how it looks:

$ openstack baremetal configure boot
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
Successfully configured all nodes.
Successfully configured all nodes.
Successfully configured all nodes.
Successfully configured all nodes.
Successfully configured all nodes.
Successfully configured all nodes.

It should either print a message per node with a node UUID or just print a successful message once.

Tags:

Julie Pichon (jpichon) on 2016-09-05

Changed in tripleo:
assignee:	nobody → Julie Pichon (jpichon)

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-09-06: Fix proposed to python-tripleoclient (master)

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

Changed in tripleo:
status:	Triaged → In Progress

Julie Pichon (jpichon) on 2016-09-12

Changed in tripleo:
milestone:	none → newton-rc1

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-09-16: Fix merged to python-tripleoclient (master)

Reviewed: https://review.openstack.org/366051
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=824620cc8b82c02409f9aafc68e8fdd2d8016970
Submitter: Jenkins
Branch: master

commit 824620cc8b82c02409f9aafc68e8fdd2d8016970
Author: Julie Pichon <email address hidden>
Date: Tue Sep 6 11:26:27 2016 +0100

Remove excessive output when configuring nodes

    The legacy 'baremetal configure boot' command calls the 'configure'
    workflow individually for each node, causing a success/failure message
    to be printed each time. The configured node UUID(s) are included in
    the execution output, so printing a specific message for each node is
    possible. However, considering that with many nodes this would make it
    easy for failure messages to go unnoticed, and that the command prior
    to the Mistral migration had no output, this patch removes the message
    when nothing went wrong instead.

Change-Id: I3f1df8046ad92328fe0ee47fa073c58ca9ad5f20
Closes-Bug: #1619717

Changed in tripleo:
status:	In Progress → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-09-19: Fix proposed to python-tripleoclient (stable/newton)

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

Julie Pichon (jpichon) on 2016-09-19

tags:

added: newton-backport-potential

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-09-22: Fix merged to python-tripleoclient (stable/newton)

Reviewed: https://review.openstack.org/372477
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=313b7301a00dfce6c0078d2eb604e5c6c59c9edd
Submitter: Jenkins
Branch: stable/newton

commit 313b7301a00dfce6c0078d2eb604e5c6c59c9edd
Author: Julie Pichon <email address hidden>
Date: Tue Sep 6 11:26:27 2016 +0100

Remove excessive output when configuring nodes

    Change-Id: I3f1df8046ad92328fe0ee47fa073c58ca9ad5f20
    Closes-Bug: #1619717
    (cherry picked from commit 824620cc8b82c02409f9aafc68e8fdd2d8016970)