Bug 1269254 - During $evm.root['miq_provision'] vm.storage_name returns NIL. VM.Storage.Name is required for customer POC involving VMware VIX library.
During $evm.root['miq_provision'] vm.storage_name returns NIL. VM.Storage...
Status: CLOSED NOTABUG
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate (Show other bugs)
5.4.0
All All
medium Severity medium
: GA
: 5.5.0
Assigned To: Greg McCullough
Dave Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-06 15:41 EDT by Josh Carter
Modified: 2015-11-11 15:25 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-12 16:43:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh Carter 2015-10-06 15:41:20 EDT
During $evm.root['miq_provision']   vm.storage_name returns NIL.   VM.Storage.Name is required for customer POC involving VMware VIX library.

 

Current work-around is to force evm.refresh during a Power-On Event.

 

VSphere 5.5 Update 2

 

Version-Release number of selected component (if applicable):

 

5.4

 

 

How reproducible:

 

Occurs 3 out of five times.   (Really noticed this in VSPHERE 5.5 vs. VSPHERE 5.1 but could be coincident.)

 

Steps to Reproduce:

1.

2.

3.

 

Actual results:

 

 

Expected results:

 

 

Additional info:
Comment 2 Greg McCullough 2015-10-12 09:52:54 EDT
The Core refresh only populates a few values for a VM (name, IP, power state, etc) but the relationship to storage is not part of that process.  A full or targeted refresh would populate the full data about a VM.

The suggested resolution here would be to retry during the CheckProvisioned or later state waiting for the storage name to be populated.
Comment 3 Greg McCullough 2015-10-12 16:43:23 EDT
Changing status to Not a Bug as the product is working as designed.

Note You need to log in before you can comment on or make changes to this bug.