| 2015-12-16 10:42:11 |
Dmitry Burmistrov |
bug |
|
|
added bug |
| 2015-12-16 10:48:02 |
Roman Vyalov |
fuel: importance |
Critical |
High |
|
| 2015-12-16 10:48:21 |
Roman Vyalov |
tags |
area-build area-mos |
area-build |
|
| 2015-12-16 10:53:56 |
Dmitry Burmistrov |
description |
A bug number of our packages have current release version in the version string like `2.5.3-3.el7~mos8.0.3`.
It leads to following issues:
- such packages have to be rebuilt for new release even if it was not changed
- rebuilt packages will be involved in the upgrade flow, but it is not necessary because the package code base was not changed.
Need to remove all mentions of mos release from packages version string and rebuild it.
It have to be done before mos 8.0 is released |
A bug number of our packages have current release version in the version string like `2.5.3-3.el7~mos8.0.3`.
It leads to following issues:
- such packages have to be rebuilt for new release even if it was not changed
- rebuilt packages will be involved in the upgrade flow, but it is not necessary because the package code base was not changed.
Need to remove all mentions of mos release from packages version string and rebuild it.
It have to be done before mos 8.0 is released
Related specs:
- https://review.openstack.org/256416
- https://review.openstack.org/252580 |
|
| 2015-12-16 13:17:27 |
Roman Vyalov |
tags |
area-build |
area-build patching |
|
| 2015-12-19 18:17:07 |
Dmitry Burmistrov |
description |
A bug number of our packages have current release version in the version string like `2.5.3-3.el7~mos8.0.3`.
It leads to following issues:
- such packages have to be rebuilt for new release even if it was not changed
- rebuilt packages will be involved in the upgrade flow, but it is not necessary because the package code base was not changed.
Need to remove all mentions of mos release from packages version string and rebuild it.
It have to be done before mos 8.0 is released
Related specs:
- https://review.openstack.org/256416
- https://review.openstack.org/252580 |
A big number of our packages have current release version in the version string like `2.5.3-3.el7~mos8.0.3`.
It leads to following issues:
- such packages have to be rebuilt for new release even if it was not changed
- rebuilt packages will be involved in the upgrade flow, but it is not necessary because the package code base was not changed.
Need to remove all mentions of mos release from packages version string and rebuild it.
It have to be done before mos 8.0 is released
Related specs:
- https://review.openstack.org/256416
- https://review.openstack.org/252580 |
|
| 2015-12-28 10:15:53 |
Fuel Devops McRobotson |
fuel: status |
Confirmed |
In Progress |
|
| 2015-12-28 12:07:45 |
Dmitry Burmistrov |
fuel: assignee |
Dmitry Burmistrov (dburmistrov) |
Igor Yozhikov (iyozhikov) |
|
| 2015-12-28 12:33:51 |
Roman Vyalov |
tags |
area-build patching |
area-mos patching |
|
| 2015-12-29 12:00:32 |
Igor Yozhikov |
fuel: status |
In Progress |
Fix Committed |
|
| 2016-02-10 15:10:19 |
Timur Nurlygayanov |
fuel: status |
Fix Committed |
Fix Released |
|
