Octane creates incorrect release for upgrades
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
Critical
|
Sergey Abramov | ||
Bug Description
The cluster_upgrade extension creates incorrect release for upgrades that does not have necessary attributes, such as networks_metadata, modes, extensions and etc.
Steps to reproduce:
1. Deploy the 7.0 environment with Ceph+VLAN and without network template
2. Upgrade the Fuel Master node to 8.0 and then to 9.1
3. Create an upgrade release by the next command:
fuel2 release clone $ORIG_ID $BASE_RELEASE_ID
4. Remember an ID of the new release in $RELEASE_ID
5. Create an upgrade environment:
octane upgrade-env $ORIG_ID $RELEASE_ID
Expected result:
All commands passed successfully.
Actual result:
Creating of the upgrade environment fails.
Workaround:
Copy all necessary attributes from $BASE_RELEASE_ID to $RELEASE_ID by SQL queries in DB.
| Changed in fuel: | |
| assignee: | nobody → Sergey Abramov (sabramov) |
| Changed in fuel: | |
| status: | New → In Progress |
| summary: |
- Octane upgrade-release command not found + Octane creates incorrect release for upgrades |
| description: | updated |
| Changed in fuel: | |
| milestone: | none → 9.1 |
| importance: | Undecided → Critical |
| Sergey Abramov (sabramov) wrote | #1 |
| Sergey Abramov (sabramov) wrote | #2 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
| Changed in fuel: | |
| status: | Fix Committed → Fix Released |
| OpenStack Infra (hudson-openstack) wrote Change abandoned on fuel-octane (master) | #3 |
https:/