Unable to Create Cloud Tenant in ManageIQ with OpenStack Antelope Version
1. I’m encountering issues while creating a tenant in ManageIQ with different OpenStack versions.
- With OpenStack Yoga: The tenant creation from ManageIQ completes successfully, as expected.
- With OpenStack Antelope: The tenant creation process fails with a 'No endpoint found' error. I expected the tenant creation to be successful in both cases.
2. Steps to reproduce:
-
I have two Open Stack Providers with two versions:
- new-openstack = Antelope
- old-openstack = Yoga
-
ManageIQ version = Petrosian.
-
Attempt to create a Cloud Tenant in OpenStack Yoga:
-
Attempt to create a Cloud Tenant in OpenStack Antelope:
Can anyone assist with how to check the endpoints and fix the 'No endpoint found' error when using OpenStack Antelope?
Thanks in advance for your help!
@miq-bot add-label bug, OpenStack, tenant-creation @miq-bot assign @jeffibm @Fryguy @GilbertCherrie @agrare
@Dhamo1107 Cannot apply the following labels because they are not recognized:
-
openstack -
tenant-creation
All labels for ManageIQ/manageiq: https://github.com/ManageIQ/manageiq/labels
@Dhamo1107 'jeffibm Fryguy GilbertCherrie agrare' is an invalid assignee, ignoring...
Hey @Dhamo1107 can you change the fog log level to debug, reproduce this and then post the API request/response for this from the fog log? journalctl -t fog if you're on an appliance
Hi @agrare, this is the log:
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.