Ok, I'm not sure how we want this bug addressed, but I do want to point out that a lot has happened with glance/keystone integration over the past few weeks. Now it looks like we nicely handle the exception like this:
glance --os_username=demo --os_password=secrete --os_auth_url=http://192.168.27.100:5000/v2.0 add name=pants disk_format=ami container_format=ami < /opt/stack/glance/images/2571cbd6-3d2c-473d-adb4-833ef67003f8 Failed to add image. Got error:
Response from Keystone does not contain a Glance endpoint.
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.
What should we set as the criteria for fixing this bug?
Ok, I'm not sure how we want this bug addressed, but I do want to point out that a lot has happened with glance/keystone integration over the past few weeks. Now it looks like we nicely handle the exception like this:
glance --os_username=demo --os_password= secrete --os_auth_url=http:// 192.168. 27.100: 5000/v2. 0 add name=pants disk_format=ami container_ format= ami < /opt/stack/ glance/ images/ 2571cbd6- 3d2c-473d- adb4-833ef67003 f8 Failed to add image. Got error:
Response from Keystone does not contain a Glance endpoint.
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.
What should we set as the criteria for fixing this bug?