Bug #25013
closedVM getting provisioned with the wrong storage.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1607408
Description of problem:
When creating the VM on VMware, if we create two storage and select two different data clusters in them. Then VM is created only on the first cluster of first storage.
If we directly select the datastore from two different data clusters then VM gets create successfully.
How reproducible:
Create a new host.
Steps to Reproduce:
1. Deploy on VMware (compute resource)
2. Go to Virtual Machine tab and add two storage.
3. In first storage, Select any Data cluster.
4. In second storage, Select Data cluster different from the first.
5. Create the VM.
6. Go to vSphere client, see the storage configuration of created VM. Also, can be cross-checked by clicking on edit VM on satellite.
Actual results:
VM is created only on one data cluster.
Expected results:
VM should have two storage from two different data clusters.
Additional info:
This is caused because API call (JSON packet) is created wrongly, Only data cluster( "storage_pod") must be sent in the API call but data store is also forwarded with the packet. Below is the related upstream bug.
https://projects.theforeman.org/issues/19311
Also, related to - https://bugzilla.redhat.com/show_bug.cgi?id=1489516
Updated by Marek Hulán almost 6 years ago
- Subject changed from VM getting provisioned with the wrong storage. to VM getting provisioned with the wrong storage.
- Assignee changed from Chris Roberts to Ondřej Ezr
Updated by Ondřej Ezr over 5 years ago
- Related to Bug #19311: Data store is selected when datastore cluster is set in compute profile when creating new host added
Updated by Ondřej Ezr over 5 years ago
- Related to deleted (Bug #19311: Data store is selected when datastore cluster is set in compute profile when creating new host)
Updated by Ondřej Ezr over 5 years ago
- Has duplicate Bug #19311: Data store is selected when datastore cluster is set in compute profile when creating new host added
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/6454 added
Updated by Ondřej Ezr over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset ad1a01dac45784dfdf143f011179a67666f0c337.