Setting up deployed_before in generated cluster attributes
Bug #1602281 reported by
Rodion Tikunov
This bug report is a duplicate of:
Bug #1529691: Stop deployment while adding compute node to existing cluster leads to the destruction of the cluster.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Critical
|
Fuel Sustaining | ||
5.1.x |
Confirmed
|
Critical
|
Rodion Tikunov | ||
6.0.x |
Confirmed
|
Critical
|
Rodion Tikunov | ||
6.1.x |
Confirmed
|
Critical
|
Rodion Tikunov | ||
7.0.x |
In Progress
|
Critical
|
Rodion Tikunov |
Bug Description
Detailed bug description:
This bug related with https:/
Environments <8.0 need to set attribute "deployed_before": {"value": true} in generated cluster attributes after successful deploy.
Steps to reproduce:
1. Deploy any environment (1 controller and 1 compute nodes)
2. Connect to nailgun database and make query:
nailgun=# select generated from attributes;
Expected results:
"deployed_before": {"value": true}
Expected results:
"deployed_before": {"value": false} or even attribute doesn't exist
Impact:
The bug mentioned in the description could not be fixed without this attribute.
Additional information:
Affects all versions <8.0
Changed in fuel: | |
milestone: | 7.0-updates → 7.0-mu-5 |
Changed in fuel: | |
importance: | Undecided → Critical |
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
status: | New → Confirmed |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 7.0-mu-5 → 10.0 |
status: | Confirmed → Invalid |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 340827/ should fix this