Description of problem: Using the default provision UI (from CLOUD->Instances->Lifecycle->Provision) Version-Release number of selected component (if applicable): 5.3.2.6.20150108100920_387a856 How reproducible: Always Steps to Reproduce: 1. Go to Cloud->Instances in the UI 2. Select Lifecycle -> Provision Instances 3. Provision an Instance to a Non-Admin Tenant Actual results: Instance failes at check_provision method, from the automate log: [----] I, [2015-01-15T21:31:23.431112 #40062:12fd0a4] INFO -- : Q-task_id([miq_provision_415000000000003]) Invoking [inline] method [ManageIQ/Cloud/VM/Provisioning/StateMachines/Methods/che ck_provisioned] with inputs [{}] [----] I, [2015-01-15T21:31:23.431825 #40062:12fd0a4] INFO -- : Q-task_id([miq_provision_415000000000003]) <AEMethod [ManageIQ/Cloud/VM/Provisioning/StateMachines/Methods/check_provisioned] > Starting [----] I, [2015-01-15T21:31:23.707729 #40062:56bb750] INFO -- : Q-task_id([miq_provision_415000000000003]) <AEMethod check_provisioned> ProvisionCheck returned <error> for state <finished> and status <Error> [----] I, [2015-01-15T21:31:23.716856 #40062:12fd0a4] INFO -- : Q-task_id([miq_provision_415000000000003]) <AEMethod [ManageIQ/Cloud/VM/Provisioning/StateMachines/Methods/check_provisioned]> Ending Instance actually provisions successfully in OpenStack though. Expected results: Instance provisions and the provisioning request does not fail at check_provision Additional info:
Can you confirm if this is resolved with the change from Bug 1182795? If so we can close as a dup.
Based on the description, yes this sounds like the same issue. *** This bug has been marked as a duplicate of bug 1182795 ***