Node naming lost between environments
Bug #1422720 reported by
Jon Skarpeteig
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Wishlist
|
Sebastian Kalinowski |
Bug Description
When naming a discovered, unassigned node - the expectation is that this naming survives getting added and removed from an environment.
Currently, this nodename is reset to "unknown" when removed from an environment - triggering a need to name this node in between every configuration change of a node in between environments.
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 6.1 |
tags: | added: feature |
Changed in fuel: | |
milestone: | 6.1 → next |
importance: | Medium → Wishlist |
Changed in fuel: | |
milestone: | next → 7.0 |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: area-python |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/221268
Review: https:/