Description of problem:
When provisioning instance on GCE, The requests switches various states and statuses from unknown-pending trough OK-pending to error-finished.
It seems like when request with cloud-init script is created, the "Last Message" is:
[EVM] VM [jhenner-test] Step [CheckProvisioned] Status [Error Creating VM] Message [[ArgumentError]: wrong number of arguments (given 1, expected 0)]
but this is not required condition to make the request fail.
Note that in the CFME, it looks like the VM is created fine as it can be found among the cloud instances
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Go trough the instance provisioning dialogue, fill all the required params
2. Optionally select Customize -> Customize Template: cloud-init
4. Observe the request statuses.
Request status changes and won't finish on OK
Request status changes and finishes fine with and without cloud-init
It may be possible that the disk of the VM may be left present on storage even after VM deleted using CFME.
Created attachment 1477636 [details]
There is an outstanding PR for the cloud-init issue here: https://github.com/ManageIQ/manageiq-providers-google/pull/66
The BZ description is confusing since it talks about cloud-init but says it is not required. I expect the PR above will fix the first issue.
So, without cloud-init involved can you detail what the issue you are reporting is?
The problem with creating a CM with cloud-init is present on 5.10 as well as on 5.9
(In reply to Greg McCullough from comment #3)
> There is an outstanding PR for the cloud-init issue here:
> The BZ description is confusing since it talks about cloud-init but says it
> is not required. I expect the PR above will fix the first issue.
> So, without cloud-init involved can you detail what the issue you are
> reporting is?
Ok scratch that it is not required condition. I cannot reproduce the problem without the cloud-init being involved now.
PR in review: https://github.com/ManageIQ/manageiq-providers-google/pull/69
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.