Verify operation in glance

[Dalton Cézane]

I installed the Glance service according to the tutorial, but received the following error when testing the image creation:

glance image-create --name "cirros" --file Downloads/cirros-0.4.0-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility=public
WARNING: The client is falling back to v1 because the accessing to v2 failed. This behavior will be removed in future versions
usage: glance [--version] [-d] [-v] [--get-schema] [-f]
              [--os-image-url OS_IMAGE_URL]
              [--os-image-api-version OS_IMAGE_API_VERSION]
              [--profile HMAC_KEY] [--os-region-name OS_REGION_NAME]
              [--os-auth-token OS_AUTH_TOKEN]
              [--os-service-type OS_SERVICE_TYPE]
              [--os-endpoint-type OS_ENDPOINT_TYPE] [--insecure]
              [--os-cacert <ca-certificate>]
              [--os-cert <certificate>] [--os-key <key>]
              [--timeout <seconds>] [--collect-timing]
              [--os-auth-type <name>] [--os-auth-url OS_AUTH_URL]
              [--os-system-scope OS_SYSTEM_SCOPE]
              [--os-domain-id OS_DOMAIN_ID]
              [--os-domain-name OS_DOMAIN_NAME]
              [--os-project-id OS_PROJECT_ID]
              [--os-project-name OS_PROJECT_NAME]
              [--os-project-domain-id OS_PROJECT_DOMAIN_ID]
              [--os-project-domain-name OS_PROJECT_DOMAIN_NAME]
              [--os-trust-id OS_TRUST_ID]
              [--os-default-domain-id OS_DEFAULT_DOMAIN_ID]
              [--os-default-domain-name OS_DEFAULT_DOMAIN_NAME]
              [--os-user-id OS_USER_ID] [--os-username OS_USERNAME]
              [--os-user-domain-id OS_USER_DOMAIN_ID]
              [--os-user-domain-name OS_USER_DOMAIN_NAME]
              [--os-password OS_PASSWORD]
              <subcommand> ...
glance: error: unrecognized arguments: --visibility=public

If I remove the "--visitiblity=public", I get the following:
glance image-create --name "cirros" --file Downloads/cirros-0.4.0-x86_64-disk.img --disk-format qcow2 --container-format bare
WARNING: The client is falling back to v1 because the accessing to v2 failed. This behavior will be removed in future versions
HTTPMultipleChoices (HTTP 300) Requested version of OpenStack Images API is not available.

And if I run with the openstack command, I receive the following error:
openstack image list
HttpException: 500: Server Error for url: http://openstack-controller:9292/v2/images, Internal Server Error

What can be wrong with my installation if I didnt receive error messages during installation?

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [ ] This doc is inaccurate in this way: ______
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - The mailing list: https://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

-----------------------------------
Release: 22.0.0.0rc2.dev2 on 2019-11-18 14:17:08
SHA: b5437773b20db3d6ef20d449a8a43171c8fc7f69
Source: https://opendev.org/openstack/glance/src/doc/source/install/verify.rst
URL: https://docs.openstack.org/glance/wallaby/install/verify.html

[Dalton Cézane (daltoncezane)]

I noticed that even specifying the name for the Glance service, the system did not register it:
openstack service list
+----------------------------------+----------+----------+
| ID | Name | Type |
+----------------------------------+----------+----------+
| 8318ed8175a641be935b243869b2399e | keystone | identity |
| deb4b7f24a4a46898cf22b89be6c78a9 | | image |
+----------------------------------+----------+----------+

I do not know why the service name is empty if I specified it during the creation (openstack service create --name glance --description "OpenStack Image" image).

[Abhishek Kekane (abhishek-kekane)]

I think this issue is not glance related but deployment specific. Can you add more information here like;

Which version of OpenStack are you using.
Which deployment tool have you used.
Output of openstack endpoint list

[Dalton Cézane (daltoncezane)]

Hello, @Abhishek. I am installing the Openstack Wallaby on Ubuntu 20.04. I followed this tutorial: https://docs.openstack.org/glance/wallaby/install/install-ubuntu.html

And this is the endpoint list:
openstack catalog list
+----------+----------+--------------------------------------------------+
| Name | Type | Endpoints |
+----------+----------+--------------------------------------------------+
| keystone | identity | RegionOne |
| | | admin: http://openstack-controller:5000/v3/ |
| | | RegionOne |
| | | internal: http://openstack-controller:5000/v3/ |
| | | RegionOne |
| | | public: http://openstack-controller:5000/v3/ |
| | | |
| | image | RegionOne |
| | | internal: http://openstack-controller:9292 |
| | | RegionOne |
| | | public: http://openstack-controller:9292 |
| | | RegionOne |
| | | admin: http://openstack-controller:9292 |
| | | |
+----------+----------+--------------------------------------------------+

[Dalton Cézane (daltoncezane)]

A curiosity: the tutorial says to configure the "auth_url" information (auth_url = http://controller:5000), but the glance-api.conf file has "auth_uri". Can we use any of these options, auth_url or auth_uri?

[Dalton Cézane (daltoncezane)]

I tested the two options and found different results.

When using "auth_uri", I got the following message:
openstack image list
Failed to contact the endpoint at http://openstack-controller:9292 for discovery. Fallback to using that endpoint as the base url.
Failed to contact the endpoint at http://openstack-controller:9292 for discovery. Fallback to using that endpoint as the base url.
The image service for : exists but does not have any supported versions.

When using "auth_url", I got the following message:
openstack image list
HttpException: 500: Server Error for url: http://openstack-controller:9292/v2/images, Internal Server Error

So, what option should I use (auth_uri, which is the option in the file, or auth_url, which is the option suggested in the documentation)?

[Dalton Cézane (daltoncezane)]

I cannot reproduce the problem anymore, but I believe it is related to memcached service that was not running. After restarted the service, I found that in an attempt to solve the problem I had changed memcached_servers to "http://controller..." instead of just "controller...". Then I fix the configuration, restarted the service and now it is working.

[Franck Alomassor (falomassor)]

How did you solve your problem I am having similar issue with glance deployment. Did you use uri or url or you used both?

[Bui Doan Dang (dang2705)]

Is there any way to fix this bugs? i have the same problen with senlin yoga

[Dalton Cézane (daltoncezane)]

@Franck Alomassor and @Bui Doan, take a look at my last comment. Maybe you also get success changing the memcached_servers configuration and restarting the service. Best regards.

[Cyril Roelandt (cyril-roelandt)]

@Bui Doan Dang: can you show us your config & logs?