yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #64241
[Bug 1692982] Re: Need --strict option for nova-manage cell_v2 discover_hosts
Reviewed: https://review.openstack.org/467218
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aaae213bf32096c56cb1bfcb4d0ac3cafd1c13fb
Submitter: Jenkins
Branch: master
commit aaae213bf32096c56cb1bfcb4d0ac3cafd1c13fb
Author: Eric Berglund <esberglu@xxxxxxxxxx>
Date: Tue May 23 22:26:28 2017 -0400
Add strict option to discover_hosts
This adds a --strict option that can be passed in when calling the
nova-manage cell_v2 discover_hosts command. When this option is used,
the command will only return success if a new host has been found.
In any other case it is considered a failure.
Closes-Bug: #1692982
Change-Id: I942af11a3987e1edce67423c66931ad9ece65587
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1692982
Title:
Need --strict option for nova-manage cell_v2 discover_hosts
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Description
===========
The "nova-manage cell_v2 discover_hosts" currently exits with code 0 unless something seriously breaks during the command execution. There should be a path for this command to exit with a failure code unless an unmapped host is found. If one is found, it should be considered a success.
Proposal
========
Add a --strict option (defaulting to false) to the nova-manage cell_v2 discover_hosts command. When this option is provided, the command will succeed with exit code 0 if any unmapped hosts are discovered. In any other case it will fail with exit code 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1692982/+subscriptions
References