Red Hat Bugzilla – Bug 1403529
Unable to access the virtual machine configuration: provisioning error
Last modified: 2018-01-19 16:01:54 EST
Found that the storage ems_ref value from the HostStorage model was returning a nil which was passed to VMware. A nil value for storage means to provision the template to the same storage which the host did not have access to. The root cause of the HostStorage nil value was determined to be a rubyrep error during the provider refresh. Note: In version 5.6 the ems_ref value is stored in the reserves table.
This was being caused by a regression in rubyrep which caused the trigger which recorded the changes to the reserves table to always fail. This was fixed in rubyrep in this PR https://github.com/ManageIQ/rubyrep/pull/10 The new tag of rubyrep was included in darga in this PR to ManageIQ https://github.com/ManageIQ/manageiq/pull/13186 I have removed the cfme-future and cfme-5.7.z flags because rubyrep does not exist in those versions.
New commit detected on ManageIQ/manageiq/darga: https://github.com/ManageIQ/manageiq/commit/15ac122e7a26866e4cf2890e9132e5edc39baf30 commit 15ac122e7a26866e4cf2890e9132e5edc39baf30 Author: Nick Carboni <ncarboni@redhat.com> AuthorDate: Wed Dec 14 17:22:25 2016 -0500 Commit: Nick Carboni <ncarboni@redhat.com> CommitDate: Wed Dec 14 17:22:25 2016 -0500 Move rubyrep to the newest version This includes a fix which ensures the special trigger row variables, NEW and OLD are not quoted in trigger functions. This was breaking replication for the reserves table. https://bugzilla.redhat.com/show_bug.cgi?id=1403529 Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
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://rhn.redhat.com/errata/RHBA-2017-0474.html