Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690199 - Unclear error message received when provisioning a new host failed
Summary: Unclear error message received when provisioning a new host failed
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-19 01:32 UTC by matt jia
Modified: 2019-03-20 03:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description matt jia 2019-03-19 01:32:56 UTC
Description of problem:

When using image-based improvising to provision a new host in Vmware, it returns
an error message like this:

Error message given:
Failed to create a compute WPRVCS102 (VMware) instance example.test.com: undefined method `[]' for nil:NilClass

It is unclear to say what is wrong.

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

6.4

How reproducible:

Easy


Steps to Reproduce:
1. configure a compute profile and select a wrong storage/leave it blank
2. using image-based provisioning to provision a new host in Vmaware
3.

Actual results:

Failed to create a compute WPRVCS102 (VMware) instance example.test.com: undefined method `[]' for nil:NilClass


Expected results:

It should tell exactly what goes wrong, such as the storage is chose or sth like that.


Additional info:

The trackback only tells where the error is from in the code. Sometimes, we have to guess this is a problem with the storage. But without a clear message, we can't really tell what is going on.


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