Description of problem: Unable to set cloud_tenant in service dialog. [----] E, [2018-01-08T03:08:22.597714 #16330:57ab0d4] ERROR -- : Q-task_id([service_template_provision_task_1000000000017]) <AutomationEngine> <AEMethod update_serviceprovision_status> Service Provision Error: Server [EVM] Service [nonetwork-20180108-030643] Step [checkprovisioned] Status [Error Creating Service] Message [[NoMethodError]: undefined method `[]' for nil:NilClass] Version-Release number of selected component (if applicable): CFME 5.8.2-3 How reproducible: 100% Steps to Reproduce: 1. Create a dialog with a dropdown list of cloud_tenant 2. No matter I set id, name or ems_ref of one tenant, the error will occur 3. Actual results: Expected results: The cloud_tenant can be selected in the dropdown list like cloud_network and instance_type Additional info:
The associated support case has the automation.log but I would also like the evm.log and production.log that go along with this issue.
Hi Greg, I can reproduce the issue in my local environment. I reproduced the issue again and would you please login to my machine to have a check ? Reproduce environment: 10.72.32.167 root/smartvm Service dialog: nonetwork miq_provision_1000000000021 Timestamp: 2018-01-10T09:26:27 Thank you very much ! Best Regards, Chen
madhu - Can you review this setup. I am hoping they just need some direction on how to configure.
Madhu, is there any progress here per comment 6? Chen has provided a environment, can you please take a look and provide guidance. THX.
Re-assigning to Tina to review.
The issue is caused by the Service Dialog populating cloud_tenant as a string, when the code is expecting it to be an array. ----] I, [2018-01-31T13:04:42.543243 #4325:f61134] INFO -- : Q-task_id([miq_provision_1000000000024]) MIQ(ManageIQ::Providers::Openstack::CloudManager::Provision#log_clone_options) Prov Options: :cloud_tenant = "1000000000001" Created: https://github.com/ManageIQ/manageiq-providers-openstack/pull/223
*** Bug 1549131 has been marked as a duplicate of this bug. ***
Hello Omri, Can you please verify the patch provided. Do let us know if any additional information required from my end. Regards, Neha Chugh
Hello Jadh, Do we have an update on this? Regards, Neha Chugh
Verified o 5.10.0.11
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212