Disable 5.0(.х) for new envs after upgrade master node to 5.1 (not in experimental mode)
Bug #1368100 reported by
Nastya Urlapova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ihor Kalnytskyi |
Bug Description
After upgrade master node to 5.1 user should have ability deploy new environments - only 5.1 version.
5.0.2 will be use ONLY for patching old envs.
Please leave possibility of deployment of older versions in experimental mode.
*Update for 6.0*
For 6.0 it should be fixed on nailgun side and removed hardcoded logic in UI.
Create new field which can be used for filtering out releases, which cannot be installed.
Changed in fuel: | |
milestone: | none → 5.1 |
assignee: | nobody → Fuel UI Team (fuel-ui) |
summary: |
- Disable 5.0.2 for new envs after upgrade master node to 5.1 (not in + Disable 5.0(.х) for new envs after upgrade master node to 5.1 (not in experimental mode) |
description: | updated |
Changed in fuel: | |
status: | In Progress → Fix Committed |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → Fix Committed |
no longer affects: | fuel/6.0.x |
Changed in fuel: | |
status: | Fix Released → In Progress |
importance: | Critical → High |
assignee: | Alexandra Morozova (astepanchuk) → Igor Kalnitsky (ikalnitsky) |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
There are several ways how we can do it
1. hardcode on UI
2. add in release table additional column 'available' and set False for those release which we want to disable, add data migration where set False for 5.0, 5.0.1 releases, and UI will be able to handle it, also it will require to add validation on api side