Bug 1496795 - Unable to create Cloud Tenant from openstack provider [RHOS 11]
Summary: Unable to create Cloud Tenant from openstack provider [RHOS 11]
Keywords:
Status: CLOSED DUPLICATE of bug 1497207
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: cfme-future
Assignee: Marek Aufart
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: 1383197
TreeView+ depends on / blocked
 
Reported: 2017-09-28 12:28 UTC by Imaan
Modified: 2018-09-13 17:19 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-13 17:19:15 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Imaan 2017-09-28 12:28:10 UTC
Description of problem:

Getting error code "404 not found" while creating tenant through cfme UI.

Version-Release number of selected component (if applicable):

5.8.1.5

How reproducible:

Always

Steps to Reproduce:

1. Go to -> compute->clouds->providers->configuration->add new cloud provider(RHOS11) ->complete the details and click on validate then add it.

2.Go to -> compute->clouds->tenants->configuration->choose create cloud tenant.

3. Choose cloud provider and specify the tenant name and click on save.

4. You will get error "404 resource not found" as shown in attachment.

Actual results:

It should create tenant.

Expected results:

It is giving an error while creating tenant as :

[----] I, [2017-09-28T06:44:13.525375 #3725:449134]  INFO -- : MIQ(MiqQueue#m_callback) Message id: [1000006610264], Invoking Callback with args: ["Finished", "error", "Expected([200]) <=> Actual(404 Not Found)\nexcon.error.response\n  :body          => \"{\\\"error\\\": {\\\"message\\\": \\\"The resource could not be found.\\\", \\\"code\\\": 404, \\\"title\\\": \\\"Not Found\\\"}}\"\n  :cookies       => [\n  ]\n  :headers       => {\n    \"Connection\"             => \"close\"\n    \"Content-Length\"         => \"93\"\n    \"Content-Type\"           => \"application/json\"\n    \"Date\"                   => \"Thu, 28 Sep 2017 05:14:03 GMT\"\n    \"Server\"                 => \"Apache/2.4.6 (Red Hat Enterprise Linux)\"\n    \"Vary\"                   => \"X-Auth-Token\"\n    \"x-openstack-request-id\" => \"req-278426ec-aebe-43f1-b086-6e76527bc792\"\n  }\n  :host          => \"10.74.129.13\"\n  :local_address => \"10.74.130.198\"\n  :local_port    => 41446\n  :path          => \"/v2.0//v3/tenants\"\n  :port          => 35357\n  :reason_phrase => \"Not Found\"\n  :remote_ip     => \"10.74.129.13\"\n  :status        => 404\n  :status_line   => \"HTTP/1.1 404 Not Found\\r\\n\"\n", "nil"]
  :path          => "/v2.0//v3/tenants"
[----] E, [2017-09-28T06:44:13.777779 #4011:91d048] ERROR -- : MIQ(cloud_tenant_controller-wait_for_task): Unable to create Cloud Tenant "t5": Expected([200]) <=> Actual(404 Not Found)
  :path          => "/v2.0//v3/tenants"


Additional Info: 

There is one workaround for this issue as : 

1. Go to -> compute->clouds->providers->select the provider->configuration->edit selected cloud provider

2. Select the API Version "keystone V3".

3. Mention the keystone V3 domain ID. In order to get the domain ID, ssh to openstack provider appliance and do #openstack domain list.

4. Validate and save.

5. Add the tenant and you will able to add the tenant successfully.

Comment 3 Dave Johnson 2017-09-28 12:44:27 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 4 Tzu-Mainn Chen 2017-09-28 14:06:18 UTC
It looks like your openstack install is using the keystone v3 endpoint, right? If so, the workaround is the correct solution. Let me know if I'm missing something!

Comment 5 Imaan 2017-10-03 06:40:50 UTC
(In reply to Tzu-Mainn Chen from comment #4)
> It looks like your openstack install is using the keystone v3 endpoint,
> right? If so, the workaround is the correct solution. Let me know if I'm
> missing something!

Hi Chen,

Yes, our openstack installation has been done using keystone v3 endpoint.

Regards,
Imaan

Comment 6 Dave Johnson 2017-10-03 06:44:52 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 7 Dave Johnson 2017-10-03 07:03:59 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 9 Tzu-Mainn Chen 2017-10-17 13:05:10 UTC
This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1497207 - would you agree?

Comment 11 Sam Lucidi 2018-09-13 17:19:15 UTC

*** This bug has been marked as a duplicate of bug 1497207 ***


Note You need to log in before you can comment on or make changes to this bug.