| 2015-10-15 00:15:15 |
Edward Hope-Morley |
bug |
|
|
added bug |
| 2015-10-15 00:15:22 |
Edward Hope-Morley |
nova (Ubuntu): status |
New |
In Progress |
|
| 2015-10-15 00:15:24 |
Edward Hope-Morley |
nova (Ubuntu): importance |
Undecided |
High |
|
| 2015-10-15 00:15:27 |
Edward Hope-Morley |
nova (Ubuntu): assignee |
|
Edward Hope-Morley (hopem) |
|
| 2015-10-15 00:42:19 |
Edward Hope-Morley |
branch linked |
|
lp:~hopem/nova/icehouse-lp1506257 |
|
| 2015-10-15 11:59:06 |
Corey Bryant |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-10-15 11:59:06 |
Corey Bryant |
bug task added |
|
nova (Ubuntu Trusty) |
|
| 2015-10-15 12:36:57 |
Felipe Reyes |
tags |
|
openstack sts |
|
| 2015-10-15 16:50:23 |
Edward Hope-Morley |
nova (Ubuntu Trusty): status |
New |
In Progress |
|
| 2015-10-15 16:50:25 |
Edward Hope-Morley |
nova (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2015-10-15 16:50:27 |
Edward Hope-Morley |
nova (Ubuntu Trusty): assignee |
|
Edward Hope-Morley (hopem) |
|
| 2015-10-15 16:50:34 |
Edward Hope-Morley |
nova (Ubuntu): status |
In Progress |
Fix Released |
|
| 2015-10-15 16:50:38 |
Edward Hope-Morley |
nova (Ubuntu): assignee |
Edward Hope-Morley (hopem) |
|
|
| 2015-10-15 22:42:02 |
Edward Hope-Morley |
description |
The SRU recently landed for https://bugs.launchpad.net/nova/+bug/1349888 introduced a potential upgrade regression if nova services are not upgraded all at once.
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack RemoteError: Remote error: UnsupportedVersion Endpoint does not support RPC version 3.35
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n incoming.message))\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, in _dispatch\n raise UnsupportedVersion(version)\n', u'UnsupportedVersion: Endpoint does not support RPC version 3.35\n'].
Basically, if nova-compute services are updated after nova-api services you will hit this issue if you perform volume operations. A simple solution, if possible, is to upgrade nova-compute services so that they are all in sync but I still want to remove the possibility for regression while keeping the fix from 1349888. I will propose an SRU shortly to resolve this. |
[Impact]
Resolves issue described below by making rpc client tolerant of incompatible
remote agent for reserve_block_device_name() calls which can occur during
upgrades if compute services are upgraded after clients e.g. nova-api. The
proposed fix will cause the client to fallback to a known good/suppported api
version.
[Test Case]
* Deploy openstack with all nova services on the same version and test that
volume operations, particularly attach and detach are working correctly.
* Deploy Openstack with only Nova client services upgraded (i.e. don't
upgrade nova-compute) and test that volume operations, particularly attach
and detach are working correctly.
* Perform same tests as for 1349888 to ensure the fix is still working.
[Regression Potential]
None.
The SRU recently landed for https://bugs.launchpad.net/nova/+bug/1349888 introduced a potential upgrade regression if nova services are not upgraded all at once.
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack RemoteError: Remote error: UnsupportedVersion Endpoint does not support RPC version 3.35
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n incoming.message))\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, in _dispatch\n raise UnsupportedVersion(version)\n', u'UnsupportedVersion: Endpoint does not support RPC version 3.35\n'].
Basically, if nova-compute services are updated after nova-api services you will hit this issue if you perform volume operations. A simple solution, if possible, is to upgrade nova-compute services so that they are all in sync but I still want to remove the possibility for regression while keeping the fix from 1349888. I will propose an SRU shortly to resolve this. |
|
| 2015-10-15 22:42:15 |
Edward Hope-Morley |
summary |
rpcapi version mismatch possible on upgrade |
[SRU] rpcapi version mismatch possible on upgrade |
|
| 2015-10-15 22:43:24 |
Edward Hope-Morley |
description |
[Impact]
Resolves issue described below by making rpc client tolerant of incompatible
remote agent for reserve_block_device_name() calls which can occur during
upgrades if compute services are upgraded after clients e.g. nova-api. The
proposed fix will cause the client to fallback to a known good/suppported api
version.
[Test Case]
* Deploy openstack with all nova services on the same version and test that
volume operations, particularly attach and detach are working correctly.
* Deploy Openstack with only Nova client services upgraded (i.e. don't
upgrade nova-compute) and test that volume operations, particularly attach
and detach are working correctly.
* Perform same tests as for 1349888 to ensure the fix is still working.
[Regression Potential]
None.
The SRU recently landed for https://bugs.launchpad.net/nova/+bug/1349888 introduced a potential upgrade regression if nova services are not upgraded all at once.
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack RemoteError: Remote error: UnsupportedVersion Endpoint does not support RPC version 3.35
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n incoming.message))\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, in _dispatch\n raise UnsupportedVersion(version)\n', u'UnsupportedVersion: Endpoint does not support RPC version 3.35\n'].
Basically, if nova-compute services are updated after nova-api services you will hit this issue if you perform volume operations. A simple solution, if possible, is to upgrade nova-compute services so that they are all in sync but I still want to remove the possibility for regression while keeping the fix from 1349888. I will propose an SRU shortly to resolve this. |
[Impact]
Resolves issue described below by making rpc client tolerant of incompatible
remote agent for reserve_block_device_name() calls which can occur during upgrades if compute services are upgraded after clients e.g. nova-api. The proposed fix will cause the client to fallback to a known good/supported api version.
[Test Case]
* Deploy openstack with all nova services on the same version and test that
volume operations, particularly attach and detach are working correctly.
* Deploy Openstack with only Nova client services upgraded (i.e. don't
upgrade nova-compute) and test that volume operations, particularly attach
and detach are working correctly.
* Perform same tests as for 1349888 to ensure the fix is still working.
[Regression Potential]
None.
The SRU recently landed for https://bugs.launchpad.net/nova/+bug/1349888 introduced a potential upgrade regression if nova services are not upgraded all at once.
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack RemoteError: Remote error: UnsupportedVersion Endpoint does not support RPC version 3.35
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n incoming.message))\n', u' File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, in _dispatch\n raise UnsupportedVersion(version)\n', u'UnsupportedVersion: Endpoint does not support RPC version 3.35\n'].
Basically, if nova-compute services are updated after nova-api services you will hit this issue if you perform volume operations. A simple solution, if possible, is to upgrade nova-compute services so that they are all in sync but I still want to remove the possibility for regression while keeping the fix from 1349888. I will propose an SRU shortly to resolve this. |
|
| 2015-10-16 14:53:52 |
Edward Hope-Morley |
tags |
openstack sts |
openstack sts ubuntu-sponsors |
|
| 2015-10-16 14:55:51 |
Edward Hope-Morley |
attachment added |
|
lp1506257.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/nova/+bug/1506257/+attachment/4496906/+files/lp1506257.debdiff |
|
| 2015-10-28 17:05:39 |
Chris J Arges |
nova (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-10-28 17:05:41 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-10-28 17:05:43 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2015-10-28 17:05:46 |
Chris J Arges |
tags |
openstack sts ubuntu-sponsors |
openstack sts ubuntu-sponsors verification-needed |
|
| 2015-11-02 11:00:37 |
Edward Hope-Morley |
tags |
openstack sts ubuntu-sponsors verification-needed |
openstack sts ubuntu-sponsors verification-done |
|
| 2015-11-02 14:00:53 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-server-dev/nova/icehouse |
|
| 2015-11-04 17:54:42 |
Launchpad Janitor |
nova (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-11-04 17:54:47 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
