Packages versions issue after env 5.0 is upgraded to 5.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Vladimir Kuklin | ||
6.0.x |
Fix Committed
|
High
|
Dmitry Ilyin |
Bug Description
Steps to reproduce:
1. Deploy cluster 1 with release 2014.1 (5.0) and Ubuntu/HA
2. Upload and unpack tarball with fuel-5.1 release (build #491) to /var
3. run upgrade.sh with openstack
4. Navigate to UI and update cluster 1 to release 2014.1.1-5.0.2
5. Wait until update has finished and update cluster 1 back to release 2014.1 (5.0)
Expected result: all packages versions are returned to the same versions as it were before updating to 5.0.2
Actual result: after updating back to 5.0 several packages keep installed versions from 5.0.2 :
Package: python-
Originally on the 5.0: 1.3.0~a9-0ubuntu1
After updating to 5.0.2: 1.3.0-fuel5.
After updating back to 5.0: 1.3.0-fuel5.
Package: python-sqlalchemy
Originally on the 5.0: 0.8.2-1~cloud1
After updating to 5.0.2: 0.8.2-ubuntu1
After updating back to 5.0: 0.8.2-ubuntu1
Package: python-
Originally on the 5.0: 0.8.2-1~cloud1
After updating to 5.0.2: 0.8.2-ubuntu1
After updating back to 5.0: 0.8.2-ubuntu1
Package: python-testtools
Originally on the 5.0: 0.9.32-
After updating to 5.0.2: 0.9.35-0ubuntu1
After updating back to 5.0: 0.9.35-0ubuntu1
May be connected with https:/
{"build_id": "2014-09-
Changed in mos: | |
milestone: | none → 5.1 |
affects: | mos → fuel |
Changed in fuel: | |
milestone: | 5.1 → none |
milestone: | none → 5.1 |
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
assignee: | Dmitry Ilyin (idv1985) → Vladimir Kuklin (vkuklin) |
Changed in fuel: | |
assignee: | Vladimir Kuklin (vkuklin) → Dmitry Ilyin (idv1985) |
Changed in fuel: | |
assignee: | Dmitry Ilyin (idv1985) → Vladimir Kuklin (vkuklin) |
Changed in fuel: | |
milestone: | 6.1 → 5.1.2 |
Dennis, which steps did you follow to do this? It looks like, older manifests and repos were not configured for this deployment and puppet just ran a regular deployment with newer manifests and newer packages. Actually, we do rollback only if deployment fails and then Nailgun switches repositories and manifests to older ones. I am not aware of the test case where we allow user to rollback his environment if update was successful.