2017-03-03 08:51:11 |
Marios Andreou |
bug |
|
|
added bug |
2017-03-03 08:57:14 |
Marios Andreou |
description |
Up to openvswitch 2.5 for both minor update and major upgrade in TripleO we have
had to use a special case workaround [1] to upgrade ovs 2.4->2.5 because of
bug 1635205 [2]. This is executed before the general package update as otherwise connectivity would be lost if openvswitch were upgraded with a regular yum update.
However with the arrival of openvswitch 2.6 *using* the workaround causes the
node to lose IPs whilst a regular yum update delivers ovs 2.6 without problems
(seems the rpm script fixes have arrived).
So we need to remove this workaround ... we will need it backported as far as
possible (mitaka presently?). Otherwise wherever openvswitch 2.6 is available
using the workaround to upgrade it will cause the upgrade to hang as the node
loses connectivity:
My local env where I hit this I was going from openvswitch-2.5.0-14.git20160727.el7fdp.x86_64 to openvswitch-2.6.1-8.git20161206.el7fdb.x86_64 testing the N..O upgrade workflow:
[stack@instack ~]$ upgrade-non-controller.sh --upgrade overcloud-novacompute-0
Feb 22 12:47:09 overcloud-compute-0.localdomain ovs-ctl[302367]: Configuring Open vSwitch system IDs [ OK ]
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Started Open vSwitch Database Unit.
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Starting Open vSwitch Forwarding Uni
...
--> Running transaction check
---> Package openvswitch.x86_64 1:2.6.1-8.git20161206.el7fdb will be installed
--> Finished Dependency Resolution
Updating openvswitch-2.6.1-8.git20161206.el7fdb.x86_64.rpm with nopostun option
... (nothing)
[stack@instack ~]$ ping 192.0.2.16
PING 192.0.2.16 (192.0.2.16) 56(84) bytes of data.
From 192.0.2.1 icmp_seq=1 Destination Host Unreachable
I posted https://review.openstack.org/#/c/436990/ Remove the openvswitch special case in tripleo_upgrade_node.sh Icd1517bcade36781fa0da21d045ffd9ec68efc38 (tripleo-heat-templates) to remove this for N..O but iling this bug since we'll need the backports too
[1] https://github.com/openstack/tripleo-heat-templates/blob/afcb6e01f3af573a7bdd286a65b71eee48cec204/extraconfig/tasks/pacemaker_common_functions.sh#L301-L320
[2] https://bugs.launchpad.net/tripleo/+bug/1635205 |
Up to openvswitch 2.5 for both minor update and major upgrade in TripleO we have had to use a special case workaround [1] to upgrade ovs 2.4->2.5 because of bug 1635205 [2]. This is executed before the general package update as otherwise connectivity would be lost if openvswitch were upgraded with a regular yum update.
However with the arrival of openvswitch 2.6 *using* the workaround causes the
node to lose IPs whilst a regular yum update delivers ovs 2.6 without problems (seems the rpm script fixes have arrived).
So we need to remove this workaround ... we will need it backported as far as
possible (mitaka presently?). Otherwise wherever openvswitch 2.6 is available
using the workaround to upgrade it will cause the upgrade to hang as the node
loses connectivity:
My local env where I hit this I was going from openvswitch-2.5.0-14.git20160727.el7fdp.x86_64 to openvswitch-2.6.1-8.git20161206.el7fdb.x86_64 testing the N..O upgrade workflow:
[stack@instack ~]$ upgrade-non-controller.sh --upgrade overcloud-novacompute-0
Feb 22 12:47:09 overcloud-compute-0.localdomain ovs-ctl[302367]: Configuring Open vSwitch system IDs [ OK ]
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Started Open vSwitch Database Unit.
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Starting Open vSwitch Forwarding Uni
...
--> Running transaction check
---> Package openvswitch.x86_64 1:2.6.1-8.git20161206.el7fdb will be installed
--> Finished Dependency Resolution
Updating openvswitch-2.6.1-8.git20161206.el7fdb.x86_64.rpm with nopostun option
... (nothing)
[stack@instack ~]$ ping 192.0.2.16
PING 192.0.2.16 (192.0.2.16) 56(84) bytes of data.
From 192.0.2.1 icmp_seq=1 Destination Host Unreachable
I posted https://review.openstack.org/#/c/436990/ Remove the openvswitch special case in tripleo_upgrade_node.sh Icd1517bcade36781fa0da21d045ffd9ec68efc38 (tripleo-heat-templates) to remove this for N..O but iling this bug since we'll need the backports too
[1] https://github.com/openstack/tripleo-heat-templates/blob/afcb6e01f3af573a7bdd286a65b71eee48cec204/extraconfig/tasks/pacemaker_common_functions.sh#L301-L320
[2] https://bugs.launchpad.net/tripleo/+bug/1635205 |
|
2017-03-03 11:58:22 |
Marios Andreou |
description |
Up to openvswitch 2.5 for both minor update and major upgrade in TripleO we have had to use a special case workaround [1] to upgrade ovs 2.4->2.5 because of bug 1635205 [2]. This is executed before the general package update as otherwise connectivity would be lost if openvswitch were upgraded with a regular yum update.
However with the arrival of openvswitch 2.6 *using* the workaround causes the
node to lose IPs whilst a regular yum update delivers ovs 2.6 without problems (seems the rpm script fixes have arrived).
So we need to remove this workaround ... we will need it backported as far as
possible (mitaka presently?). Otherwise wherever openvswitch 2.6 is available
using the workaround to upgrade it will cause the upgrade to hang as the node
loses connectivity:
My local env where I hit this I was going from openvswitch-2.5.0-14.git20160727.el7fdp.x86_64 to openvswitch-2.6.1-8.git20161206.el7fdb.x86_64 testing the N..O upgrade workflow:
[stack@instack ~]$ upgrade-non-controller.sh --upgrade overcloud-novacompute-0
Feb 22 12:47:09 overcloud-compute-0.localdomain ovs-ctl[302367]: Configuring Open vSwitch system IDs [ OK ]
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Started Open vSwitch Database Unit.
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Starting Open vSwitch Forwarding Uni
...
--> Running transaction check
---> Package openvswitch.x86_64 1:2.6.1-8.git20161206.el7fdb will be installed
--> Finished Dependency Resolution
Updating openvswitch-2.6.1-8.git20161206.el7fdb.x86_64.rpm with nopostun option
... (nothing)
[stack@instack ~]$ ping 192.0.2.16
PING 192.0.2.16 (192.0.2.16) 56(84) bytes of data.
From 192.0.2.1 icmp_seq=1 Destination Host Unreachable
I posted https://review.openstack.org/#/c/436990/ Remove the openvswitch special case in tripleo_upgrade_node.sh Icd1517bcade36781fa0da21d045ffd9ec68efc38 (tripleo-heat-templates) to remove this for N..O but iling this bug since we'll need the backports too
[1] https://github.com/openstack/tripleo-heat-templates/blob/afcb6e01f3af573a7bdd286a65b71eee48cec204/extraconfig/tasks/pacemaker_common_functions.sh#L301-L320
[2] https://bugs.launchpad.net/tripleo/+bug/1635205 |
Up to openvswitch 2.5 for both minor update and major upgrade in TripleO we have had to use a special case workaround [1] to upgrade ovs 2.4->2.5 because of bug 1635205 [2]. This is executed before the general package update as otherwise connectivity would be lost if openvswitch were upgraded with a regular yum update.
However with the arrival of openvswitch 2.6 *using* the workaround causes the
node to lose IPs whilst a regular yum update delivers ovs 2.6 without problems (seems the rpm script fixes have arrived).
So we need to remove this workaround ... we will need it backported as far as
possible (mitaka presently?). Otherwise wherever openvswitch 2.6 is available
using the workaround to upgrade it will cause the upgrade to hang as the node
loses connectivity:
My local env where I hit this I was going from openvswitch-2.5.0-14.git20160727.el7fdp.x86_64 to openvswitch-2.6.1-8.git20161206.el7fdb.x86_64 testing the N..O upgrade workflow:
[stack@instack ~]$ upgrade-non-controller.sh --upgrade overcloud-novacompute-0
Feb 22 12:47:09 overcloud-compute-0.localdomain ovs-ctl[302367]: Configuring Open vSwitch system IDs [ OK ]
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Started Open vSwitch Database Unit.
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Starting Open vSwitch Forwarding Uni
...
--> Running transaction check
---> Package openvswitch.x86_64 1:2.6.1-8.git20161206.el7fdb will be installed
--> Finished Dependency Resolution
Updating openvswitch-2.6.1-8.git20161206.el7fdb.x86_64.rpm with nopostun option
... (nothing)
[stack@instack ~]$ ping 192.0.2.16
PING 192.0.2.16 (192.0.2.16) 56(84) bytes of data.
From 192.0.2.1 icmp_seq=1 Destination Host Unreachable
I posted https://review.openstack.org/#/c/436990/ Remove the openvswitch special case in tripleo_upgrade_node.sh Icd1517bcade36781fa0da21d045ffd9ec68efc38 (tripleo-heat-templates) to remove this for N..O but filing this bug since we'll need the backports too
[1] https://github.com/openstack/tripleo-heat-templates/blob/afcb6e01f3af573a7bdd286a65b71eee48cec204/extraconfig/tasks/pacemaker_common_functions.sh#L301-L320
[2] https://bugs.launchpad.net/tripleo/+bug/1635205 |
|
2017-03-03 13:03:32 |
Emilien Macchi |
tripleo: milestone |
pike-1 |
ocata-rc2 |
|
2017-03-03 13:03:38 |
Emilien Macchi |
tags |
|
ocata-backport-potential |
|
2017-03-03 15:24:15 |
Marios Andreou |
tags |
ocata-backport-potential |
mitaka-backport-potential newton-backport-potential ocata-backport-potential |
|
2017-03-06 15:18:49 |
Emilien Macchi |
tripleo: milestone |
ocata-rc2 |
pike-1 |
|
2017-03-08 09:51:20 |
OpenStack Infra |
tripleo: status |
In Progress |
Fix Released |
|
2017-03-08 10:21:30 |
Saravanan KR |
bug |
|
|
added subscriber Saravanan KR |
2017-03-09 14:24:20 |
OpenStack Infra |
tags |
mitaka-backport-potential newton-backport-potential ocata-backport-potential |
in-stable-ocata mitaka-backport-potential newton-backport-potential ocata-backport-potential |
|
2017-03-10 15:53:01 |
Marios Andreou |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=1431108 |
|
2017-03-14 14:23:32 |
Marios Andreou |
tripleo: milestone |
pike-1 |
ongoing |
|
2017-03-14 15:19:05 |
OpenStack Infra |
tags |
in-stable-ocata mitaka-backport-potential newton-backport-potential ocata-backport-potential |
in-stable-newton in-stable-ocata mitaka-backport-potential newton-backport-potential ocata-backport-potential |
|
2017-03-28 07:56:57 |
Marios Andreou |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=1424945 |
|
2017-03-28 16:12:33 |
Marius Cornea |
bug |
|
|
added subscriber Marius Cornea |
2017-04-21 07:14:12 |
Marios Andreou |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=1416088 |
|