Cinder v1 API deprecated - move to cinder v2 API

Bug #1481542 reported by Jimmy McCrory
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-ansible
Fix Released
Medium
Jesse Pretorius
Kilo
Fix Released
Medium
Jesse Pretorius
Trunk
Fix Released
Medium
Jesse Pretorius

Bug Description

Cinder V1 API is deprecated as of the Juno release, and Nova is still configured to use it.
Enable the V2 API in Cinder and set cinder_catalog_info in nova.conf to use it.

[cinder]
catalog_info =volumev2:cinderv2:internalurl

cinder v2 was also made the default for nova in Kilo.
https://review.openstack.org/#/c/124468/3

http://specs.openstack.org/openstack/nova-specs/specs/juno/implemented/support-cinderclient-v2.html

Revision history for this message
Ian Cordasco (icordasc) wrote :

We're still using v1 in Kilo and Master, so I've targeted all appropriate and affected versions. I'm not sure if this a priority for Juno but I'd consider it one for Kilo and Master.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

It seems that for Juno, this is fine. However for Kilo this adds deprecation warnings in the logs (increasing log disk usage) and in Liberty using Cinder API v1 is causing failures in gate checks.

I'm raising the trunk importance to critical as this is becoming a blocker for merges to master.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

I'm also setting the milestone for resolving this in Kilo to 11.2.0 as this will likely require changing the service catalogue entry.

summary: - Configure nova to use cinder v2 api
+ Cinder v1 API deprecated - use cinder v2 api
summary: - Cinder v1 API deprecated - use cinder v2 api
+ Cinder v1 API deprecated - move to cinder v2 api
summary: - Cinder v1 API deprecated - move to cinder v2 api
+ Cinder v1 API deprecated - move to cinder v2 API
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to os-ansible-deployment (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/214045

Changed in openstack-ansible:
status: Confirmed → In Progress
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Reducing the priority as this does not seem to affect the master gate check builds. The issue appears to be elsewhere.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/214045
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=16d1a5150411eee9a9dd41e624d8b4e39fdf681c
Submitter: Jenkins
Branch: master

commit 16d1a5150411eee9a9dd41e624d8b4e39fdf681c
Author: Jesse Pretorius <email address hidden>
Date: Tue Aug 18 08:17:17 2015 +0100

    Switch Nova/Tempest to use/test Cinder API v2

    As per https://blueprints.launchpad.net/cinder/+spec/deprecate-v1-api
    the Cinder API v1 was designated as deprecated in Juno and was meant
    to be removed in Kilo, but appears to still be usable in Kilo.

    This patch configures Nova to use the Cinder v2 API instead of the
    v1 API.

    This patch configures Tempest to test both the Cinder v1 and v2 API's
    for now. Once the API is removed upstream we can change this.

    DocImpact
    Closes-Bug: #1481542
    Change-Id: I6513c07e1b5d5653b84ad0b2b490ac8451f2bdf1

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/220081

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/220081
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=ae4ed6e4fae3fc7ca67004115c3b52f85cd61bfa
Submitter: Jenkins
Branch: kilo

commit ae4ed6e4fae3fc7ca67004115c3b52f85cd61bfa
Author: Jesse Pretorius <email address hidden>
Date: Tue Aug 18 08:17:17 2015 +0100

    Switch Nova/Tempest to use/test Cinder API v2

    As per https://blueprints.launchpad.net/cinder/+spec/deprecate-v1-api
    the Cinder API v1 was designated as deprecated in Juno and was meant
    to be removed in Kilo, but appears to still be usable in Kilo.

    This patch configures Nova to use the Cinder v2 API instead of the
    v1 API.

    This patch configures Tempest to test both the Cinder v1 and v2 API's
    for now. Once the API is removed upstream we can change this.

    DocImpact
    Closes-Bug: #1481542
    Change-Id: I6513c07e1b5d5653b84ad0b2b490ac8451f2bdf1
    (cherry picked from commit 16d1a5150411eee9a9dd41e624d8b4e39fdf681c)

no longer affects: openstack-ansible/juno
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.