In our prod landscape we get about 10-60 cinder-volume warning messages (e.g.):
2017-03-14 12:13:13.357 25218 WARNING cinder.context [req-e752f6f7-1cf1-436c-b8c8-0b5405e26f21 - - - - -] Unable to get internal tenant context: Missing required config parameters.
2017-03-14 12:13:13.358 25218 WARNING cinder.volume.flows.manager.create_volume [req-e752f6f7-1cf1-436c-b8c8-0b5405e26f21 - - - - -] Unable to get Cinder internal context, will not use image-volume cache.
This happens in context of using Cinder/NetApp image cache cloning when creating new Cinder volume.
When I disable Chef Client on the control node in Lab where cinder-volume is running and changing cinder.conf:
cinder_internal_tenant_project_id = <service project id>
cinder_internal_tenant_user_id = <block storage service user id>
and restart the cinder-volume service these warnings will disappear when creating Cinder volumes with Glance image.
Can you please introduce these two cinder.conf parameters to the Cinder Barclamp raw attributes.
In our prod landscape we get about 10-60 cinder-volume warning messages (e.g.):
This happens in context of using Cinder/NetApp image cache cloning when creating new Cinder volume. When I disable Chef Client on the control node in Lab where cinder-volume is running and changing cinder.conf:
and restart the cinder-volume service these warnings will disappear when creating Cinder volumes with Glance image.
Can you please introduce these two cinder.conf parameters to the Cinder Barclamp raw attributes.