Description of problem: After VM is provisioned with preemptible property being check, it the VM properties in https://CFME/vm_cloud/explorer Properties field Preemptive reads "No" instead of "Yes". Version-Release number of selected component (if applicable): Version 5.9.4.4.20180816162527_c00eb23 How reproducible: always Steps to Reproduce: 1. Start creating a VM using CFME provisioning 2. in the process, select Preemptible in the Properties tab 3. Finish Creating the VM. Actual results: VM reported as not being Preemptive Expected results: VM reported as Preemptible Additional info: maybe there is some type preempti_ble_ preempti_ve_
Hi Tom, Can you test to see if this PR fixes this: https://github.com/ManageIQ/manageiq-providers-google/pull/66 thanks Bronagh
This happens on 5.10 too.
I'm on it!
Bronagh: Unfortunately the linked PR is not fixing this. I'll prepare a new PR which would adapt to the API changes on Google side. Instead of ``` clone option = { ... :preemptible => true, ... } ``` they have now a new property "scheduling" defined like: ``` clone option = { ... :scheduling = { ... :preemptible => true, ... }, ... } ``` Sigh.
PR in review: https://github.com/ManageIQ/manageiq-providers-google/pull/70
Merged!
Works with 5.10.0.14
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