| 2014-07-16 13:14:07 |
Dmitry Ilyin |
bug |
|
|
added bug |
| 2014-07-16 13:14:17 |
Dmitry Ilyin |
fuel: milestone |
|
5.1 |
|
| 2014-07-16 13:14:24 |
Dmitry Ilyin |
fuel: assignee |
|
Fuel OSCI Team (fuel-osci) |
|
| 2014-07-16 13:14:28 |
Dmitry Ilyin |
fuel: importance |
Undecided |
High |
|
| 2014-07-16 13:14:32 |
Dmitry Ilyin |
fuel: status |
New |
Confirmed |
|
| 2014-07-16 13:21:26 |
Dmitry Ilyin |
description |
1 |
Related bug: 1342041
Our new openstack packages have versions like 2014.1.1.fuel5.1-mira0 and previous release packages have versions like 2014.1.fuel5.0-mira4
Even if the new package version look higher then previous it's not and it creates several problems with updates.
Puppet's yum modules users versioncmp fuction to compare old and new version when it tries to update a package. It works like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs 1
1
First, it splits veriosn to componets and then compares each pair. It have returned 1 and it mean that first is newer then second. |
|
| 2014-07-16 13:27:32 |
Dmitry Ilyin |
description |
Related bug: 1342041
Our new openstack packages have versions like 2014.1.1.fuel5.1-mira0 and previous release packages have versions like 2014.1.fuel5.0-mira4
Even if the new package version look higher then previous it's not and it creates several problems with updates.
Puppet's yum modules users versioncmp fuction to compare old and new version when it tries to update a package. It works like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs 1
1
First, it splits veriosn to componets and then compares each pair. It have returned 1 and it mean that first is newer then second. |
Related bug: 1342041
Our new openstack packages have versions like 2014.1.1.fuel5.1-mira0 and previous release packages have versions like 2014.1.fuel5.0-mira4
Even if the new package version look higher then previous it's not and it creates several problems with updates.
Puppet's yum modules users versioncmp fuction to compare old and new version when it tries to update a package. It works like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs 1
1
First, it splits veriosn to componets and then compares each pair. It have returned 1 and it mean that first is newer then second. As you can see it's a second "1" to blame because it moves "fuel" to the next pair. The correct comparsion should look like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs fuel
5 vs 5
. vs .
0 vs 1
-1
But we cannot just rename the package because 2014.1.1 is the version of the OpenStack release.
There is a quick fix fot
Same problem can be seen on the Ubuntu nodes. Apt refuses to update to update packages to the "new" version because it's "older". Trying to "downgrade" to the "new" package olso doesn't work because all dependencies expect to have package that have version >= then required and older doesn't work. |
|
| 2014-07-16 13:45:13 |
Dmitry Ilyin |
description |
Related bug: 1342041
Our new openstack packages have versions like 2014.1.1.fuel5.1-mira0 and previous release packages have versions like 2014.1.fuel5.0-mira4
Even if the new package version look higher then previous it's not and it creates several problems with updates.
Puppet's yum modules users versioncmp fuction to compare old and new version when it tries to update a package. It works like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs 1
1
First, it splits veriosn to componets and then compares each pair. It have returned 1 and it mean that first is newer then second. As you can see it's a second "1" to blame because it moves "fuel" to the next pair. The correct comparsion should look like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs fuel
5 vs 5
. vs .
0 vs 1
-1
But we cannot just rename the package because 2014.1.1 is the version of the OpenStack release.
There is a quick fix fot
Same problem can be seen on the Ubuntu nodes. Apt refuses to update to update packages to the "new" version because it's "older". Trying to "downgrade" to the "new" package olso doesn't work because all dependencies expect to have package that have version >= then required and older doesn't work. |
Related bug: 1342041
Our new openstack packages have versions like 2014.1.1.fuel5.1-mira0 and previous release packages have versions like 2014.1.fuel5.0-mira4
Even if the new package version look higher then previous it's not and it creates several problems with updates.
Puppet's yum modules users versioncmp fuction to compare old and new version when it tries to update a package. It works like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs 1
1
First, it splits veriosn to componets and then compares each pair. It have returned 1 and it mean that first is newer then second. As you can see it's a second "1" to blame because it moves "fuel" to the next pair. The correct comparsion should look like this:
["2014", ".", "1", ".", "fuel", "5", ".", "0", "-", "mira", "4"]
["2014", ".", "1", ".", "fuel", "5", ".", "1", "-", "mira", "0"]
2014 vs 2014
. vs .
1 vs 1
. vs .
fuel vs fuel
5 vs 5
. vs .
0 vs 1
-1
But we cannot just rename the package because 2014.1.1 is the version of the OpenStack release.
There is a quick fix for yum provider: https://review.openstack.org/#/c/106997/
Same problem can be seen on the Ubuntu nodes. Apt refuses to update to update packages to the "new" version because it's "older". Trying to "downgrade" to the "new" package olso doesn't work because all dependencies expect to have package that have version >= then required and older doesn't work.
Obviously, we cant fix the apt problem the same way as yum can be fixed and we need some way to make new version be actually newer. The problem is also being made harder by the fact that previously released 5.0 packages cannot be renamed now.
* We can increase epoch for the new packages to force them be newer then all packages previously released.
* We can also make versioning like this: fuel5.1-2014.1.1-mira0 it should handle new releases.
* Why do we even add fuel release to packages. With updates we are implementing already wery thin connection between Fuel and OpenStack release is blurred even farther. Lets name then just like: 2014.1.1-mira0 |
|
| 2014-07-16 14:23:07 |
Dmitry Ilyin |
summary |
New OpenStack packages version is lower then previous |
[osci] New OpenStack packages version is lower then previous |
|
| 2014-07-16 17:18:12 |
Nastya Urlapova |
fuel: importance |
High |
Critical |
|
| 2014-07-17 16:50:07 |
Roman Vyalov |
fuel: assignee |
Fuel OSCI Team (fuel-osci) |
Dmitry Burmistrov (dburmistrov) |
|
| 2014-07-19 08:30:31 |
Ihor Kalnytskyi |
nominated for series |
|
fuel/5.0.x |
|
| 2014-07-19 08:30:31 |
Ihor Kalnytskyi |
bug task added |
|
fuel/5.0.x |
|
| 2014-07-19 08:44:12 |
Ihor Kalnytskyi |
nominated for series |
|
fuel/5.1.x |
|
| 2014-07-19 08:44:12 |
Ihor Kalnytskyi |
bug task added |
|
fuel/5.1.x |
|
| 2014-07-19 08:44:20 |
Ihor Kalnytskyi |
fuel/5.0.x: status |
New |
Confirmed |
|
| 2014-07-19 08:44:23 |
Ihor Kalnytskyi |
fuel/5.0.x: importance |
Undecided |
Critical |
|
| 2014-07-19 08:44:29 |
Ihor Kalnytskyi |
fuel/5.0.x: milestone |
|
5.0.2 |
|
| 2014-07-19 08:45:03 |
Ihor Kalnytskyi |
fuel/5.0.x: assignee |
|
Dmitry Burmistrov (dburmistrov) |
|
| 2014-07-19 13:31:24 |
Aleksey Kasatkin |
tags |
|
patching |
|
| 2014-07-19 13:32:09 |
Aleksey Kasatkin |
tags |
patching |
patching upgrade |
|
| 2014-07-21 08:31:13 |
Roman Vyalov |
fuel/5.0.x: importance |
Critical |
Medium |
|
| 2014-07-21 08:59:09 |
Dmitry Burmistrov |
fuel/5.1.x: status |
Confirmed |
In Progress |
|
| 2014-07-22 13:46:16 |
Dmitry Burmistrov |
fuel/5.1.x: status |
In Progress |
Fix Committed |
|
| 2014-08-05 22:41:58 |
Andrew Woodward |
fuel/5.0.x: importance |
Medium |
Critical |
|
| 2014-08-05 22:42:03 |
Andrew Woodward |
fuel/5.0.x: milestone |
5.0.2 |
5.0.1 |
|
| 2014-08-05 22:44:51 |
Andrew Woodward |
fuel/5.0.x: status |
Confirmed |
In Progress |
|
| 2014-08-06 07:22:39 |
Dmitry Burmistrov |
fuel/5.0.x: status |
In Progress |
Fix Committed |
|
| 2014-08-14 17:35:50 |
Dmitry Pyzhov |
bug task deleted |
fuel/5.1.x |
|
|
