Red Hat Bugzilla – Bug 1258651
importing new nodes from instackenv will overwrite existing nodes capabilities
Last modified: 2015-12-21 11:55:07 EST
Description of problem:
when import new nodes from a new instackenv.json file, it will overwrite the capabilities field in existing nodes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a new instackenv.json file with new nodes information
2. import using openstack baremetal import --json instackenv.json
3. notice existing nodes capabilities field are overwritten. roles such as controller and compute is removed
should not disturb existing node information
this is a duplicate of bug 1241199.
*** This bug has been marked as a duplicate of bug 1241199 ***
This is not a duplicate. This is two completely different code paths.
A simple workaround is to use a new file for new systems. Do not add new systems to the old json file.
I will do some investigation as to whether a code fix is appropriate here. But it seems that documentation is the best fix.
So, code change might be needed - if the file contains a node which already exists, tell user that the file contains already existing nodes which were already registered, so no action will be performed on these.
This appears to be fixed in os-cloud-config 0.2.10.
I am not seeing this issue with the GA code
The reported issue doesn't reproduce.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.