[nailgun] New releases must be created during upgrade/update script run on master
Bug #1336379 reported by
Aleksey Kasatkin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Committed
|
Critical
|
Ihor Kalnytskyi | ||
| 5.0.x |
Fix Committed
|
Critical
|
Ihor Kalnytskyi | ||
Bug Description
There are no releases generation during upgrade/update script run on master. Releases.yaml is created by hands. Releases must be generated automatically during upgrade/update script run. Orchestration data must be generated for new releases.
| Changed in fuel: | |
| assignee: | nobody → Igor Kalnitsky (ikalnitsky) |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-web (master) | #1 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-web (stable/5.0) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-web (stable/5.0) | #3 |
| summary: |
- New releases must be created during upgrade/update script run on master + [nailgun] New releases must be created during upgrade/update script run + on master |
| no longer affects: | fuel/5.1.x |
| tags: | added: upgrade |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 501e601c2c5dbf3
Author: Igor Kalnitsky <email address hidden>
Date: Tue Jul 1 19:02:13 2014 +0300
Add orchestration_data to releases if empty
We need to set orchestration_data manually if it doesn't exist in
openstack.yaml. It's a workaround of the issuee when we don't have
versioned puppers/repos on 5.0.1/5.1.
Implements blueprint upgrade-to-5-1
Closes-Bug: #1336379
Change-Id: I9241753008338d