yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #18897
[Bug 1354499] [NEW] boot from volume fails when upgrading using cinder v1 API
Public bug reported:
In c5402ef4fc509047d513a715a1c14e9b4ba9674f we added support for the new
cinder V2 API.
When a user who was previously using the Cinder v1 API (which would have
been required) updates to the new code the immediate defaults cause the
cinder v2 API to be chosen. This is because we now default
cinder_catalog_info to 'volumev2:cinder:publicURL'. So if a user was
using the previous default value of 'volumev2:cinder:publicURL' their
configuration would now be broken.
Given the new deprecation code hasn't been released yet I think we need
to wait at least one release before we can make this change to our
cinder_catalog_info default value.
** Affects: nova
Importance: Critical
Assignee: Dan Prince (dan-prince)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Dan Prince (dan-prince)
** Changed in: nova
Importance: Undecided => Critical
** Changed in: nova
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1354499
Title:
boot from volume fails when upgrading using cinder v1 API
Status in OpenStack Compute (Nova):
In Progress
Bug description:
In c5402ef4fc509047d513a715a1c14e9b4ba9674f we added support for the
new cinder V2 API.
When a user who was previously using the Cinder v1 API (which would
have been required) updates to the new code the immediate defaults
cause the cinder v2 API to be chosen. This is because we now default
cinder_catalog_info to 'volumev2:cinder:publicURL'. So if a user was
using the previous default value of 'volumev2:cinder:publicURL' their
configuration would now be broken.
Given the new deprecation code hasn't been released yet I think we
need to wait at least one release before we can make this change to
our cinder_catalog_info default value.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1354499/+subscriptions
Follow ups
References