Activity log for bug #1727338

Date Who What changed Old value New value Message
2017-10-25 13:20:35 Seb-Solon bug added bug
2017-10-25 13:20:57 Seb-Solon tags cinder nova pike
2017-10-25 13:22:20 Seb-Solon description Hi there, Based on the release notes [https://docs.openstack.org/releasenotes/nova/pike.html], "Nova is now configured to use the v3 version of the Cinder API. You need to ensure that the v3 version of the Cinder API is available and listed in the service catalog in order to use Nova with the default configuration option." The block storage cookbook still specify cinderv2 and volumev2 as service_name and service_type and endpoints also seems to be pointing to v2 version. See : https://github.com/openstack/cookbook-openstack-block-storage/blob/master/attributes/default.rb#L54 and https://github.com/openstack/cookbook-openstack-block-storage/blob/master/attributes/default.rb#L127 One way to fix it is to follow the release notes advice (use v2 explicitly in nova). Another way is to start to use v3 and update the cookbook. However, I am not 100% sure other components are using the v3. In my setup I had to have both v3 and v2 endpointw, so maybe there are more code to fix to go to the v3 version Let me know if you would like more details Regards Hi there, Based on the release notes [https://docs.openstack.org/releasenotes/nova/pike.html], "Nova is now configured to use the v3 version of the Cinder API. You need to ensure that the v3 version of the Cinder API is available and listed in the service catalog in order to use Nova with the default configuration option." The block storage cookbook still specify cinderv2 and volumev2 as service_name and service_type and endpoints also seems to be pointing to v2 version. See : https://github.com/openstack/cookbook-openstack-block-storage/blob/master/attributes/default.rb#L54 and https://github.com/openstack/cookbook-openstack-block-storage/blob/master/attributes/default.rb#L127 One way to fix it is to follow the release notes advice (use v2 explicitly in nova). Another way is to start to use v3 and update the cookbook. However, I am not 100% sure other components are using the v3. In my setup I had to have both v3 and v2 endpoints, so maybe there are more code to fix to go to the v3 version Let me know if you would like more details Regards
2017-10-25 16:25:36 Samuel Cassiba openstack-chef: status New Confirmed
2017-10-25 16:25:40 Samuel Cassiba openstack-chef: importance Undecided Critical
2017-10-30 02:44:39 OpenStack Infra openstack-chef: status Confirmed In Progress
2017-10-30 02:44:39 OpenStack Infra openstack-chef: assignee Seb-Solon (openid-3)
2018-03-06 05:47:58 Samuel Cassiba openstack-chef: assignee Seb-Solon (openid-3) Samuel Cassiba (scassiba)
2018-03-06 05:48:02 Samuel Cassiba openstack-chef: status In Progress Fix Released