Red Hat Bugzilla – Bug 1469364
[VM Provision] - Destination 'Cluster' should be required in order to submit VM provision
Last modified: 2018-03-01 08:14:47 EST
Created attachment 1296083 [details]
Description of problem:
[VM Provision] - Destination 'Cluster' should be required in order to submit VM provision.
When trying to provision VM in cfme 5.8.1, it is allowed to submit the request without specifing the destination cluster, but in the end we failing with error:
[2017-07-11T02:02:15.719206 #2959:125e210] ERROR -- : Q-task_id([miq_provision_1]) <AutomationEngine> <AEMethod update_provision_status> VM Provision Error: [EVM] VM [test_cfme_vm1] Step [CheckProvisione
d] Status [Error Creating VM] Message [[MiqException::MiqProvisionError]: Destination cluster not provided]
Currently the required feilds for submit request are:
Destination 'Cluster' should be required as well if VM provision will fail in the end because of: 'Destination cluster not provided'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Lifecycle > Open provision vm dialog
2. Select a source template
3. Provide e-mail, network and VM name and press 'Submit'
VM provision has failed -
VM Provision Error: [EVM] VM [test_cfme_vm1] Step [CheckProvisioned] Status [Error Creating VM] Message [[MiqException::MiqProvisionError]: Destination cluster not provided
Make destination 'Cluster' required for submit
The problem starts with the current behavior, if the Infra rhv-m provider has a DC with 2 active clusters, which means a running host in each cluster in the DC, this bug will happen, because in case of two clusters in the DC which have a running host each, the destination cluster will be set to default <none> by cfme on the provision VMs flow.
- If the destination DC, has only one active cluster, the only cluster in the DC which have a running host, then the active cluster will be set by cfme as the default destination cluster.
- So, because of this current behaviour, if i have a DC with 2 active clusters in the destination, the cluster will be set to <none> and because there is no requirement for it, I'm able to do submit, but then fail to provision VM.
Oved - Can someone on your team take a look. I am actually surprised that we have not had this field marked required since it is the only placement field that the backend checks for RHV.
Also want to point out that if we mark this field as required the field will also need a "required_method" property so it handles the "Choose Automatically" option.
Example VMWare field:
New commit detected on ManageIQ/manageiq/master:
Author: Moti Asayag <firstname.lastname@example.org>
AuthorDate: Tue Oct 24 16:33:37 2017 +0300
Commit: Moti Asayag <email@example.com>
CommitDate: Tue Oct 24 17:03:41 2017 +0300
Require cluster for RVH VM provision
In order to provision VM on RHV, when not selecting the auto-placement,
user should specify the destination cluster as well.
The PR enforces the selection of the destination cluster.
.../dialogs/miq_dialogs/miq_provision_redhat_dialogs_template.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
I have followed steps to reproduce. VM now cannot be provisioned w/o cluster, so the mentioned error won't occur.
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.