| 2017-06-30 09:03:53 |
Alfredo Moralejo |
bug |
|
|
added bug |
| 2017-06-30 09:04:21 |
Alfredo Moralejo |
summary |
netwoking-fujitsu release moved to lower version in master |
netwoking-fujitsu release tags moved to lower version in master |
|
| 2017-06-30 09:06:39 |
Alfredo Moralejo |
description |
Looking at git tag history on https://github.com/openstack/networking-fujitsu/releases we see that tags 4.0.2 and 4.0.3 were pushed after 4.1.0 which is higher that newer ones. This breaks the upgrades path, as a system with 4.1.0 will detect 4.0.2 and 4.0.3 as a downgrade.
I'd say the easiest solution is to push a new tag 4.1.1 as soon as possible in the repo. |
Looking at git tag history on https://github.com/openstack/networking-fujitsu/releases we see that tag 4.0.3 was pushed after 4.1.0 which is higher. This breaks the upgrades path, as a system with 4.1.0 will detect 4.0.3 as a downgrade.
I'd say the easiest solution is to push a new tag 4.1.1 as soon as possible in the repo. |
|
| 2017-07-28 04:47:48 |
Yushiro FURUKAWA |
networking-fujitsu: importance |
Undecided |
Medium |
|
| 2017-07-28 04:48:35 |
Yushiro FURUKAWA |
networking-fujitsu: status |
New |
Confirmed |
|
| 2017-08-09 04:15:34 |
Yushiro FURUKAWA |
networking-fujitsu: assignee |
|
Yushiro FURUKAWA (y-furukawa-2) |
|
| 2017-08-09 04:15:46 |
Yushiro FURUKAWA |
networking-fujitsu: status |
Confirmed |
Fix Released |
|
| 2017-08-09 23:32:59 |
Yushiro FURUKAWA |
networking-fujitsu: status |
Fix Released |
In Progress |
|
| 2017-08-10 11:40:52 |
Yushiro FURUKAWA |
networking-fujitsu: status |
In Progress |
Fix Released |
|
