1590512 – Unable to build VM in Storage Pod that does not have DRS enabled.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1590512 - Unable to build VM in Storage Pod that does not have DRS enabled.

Summary: Unable to build VM in Storage Pod that does not have DRS enabled.

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Compute Resources - VMWare
Sub Component:
Version:	6.5.0
Hardware:	x86_64
OS:	Linux
Priority:	high
Severity:	high
Target Milestone:	Unspecified
Assignee:	satellite6-bugs
QA Contact:	Lukáš Hellebrandt
Docs Contact:
URL:	https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2018-06-12 18:08 UTC by Chris Roberts
Modified:	2023-12-15 16:05 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-08-01 18:35:12 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	23911	0	Normal	New	Unable to build VM in Storage Pod that does not have DRS enabled	2021-01-15 15:25:59 UTC

Description Chris Roberts 2018-06-12 18:08:47 UTC

Description of problem:
I am trying to build a VM on a VMware Storage Pod that does not have DRS enabled and it keeps failing.

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

Foreman 1.18


How reproducible:


Steps to Reproduce:
1. Install Foreman and add VMware compute resource
2. Build VM selecting Storage POD
3. Watch the error

Actual results:

2018-06-12T12:53:16 [I|app|fb52d] Adding Compute instance for jim-paleo.toledo.satellite.lab.eng.rdu2.redhat.com
2018-06-12T12:53:17 [I|app|fb52d] Loaded compute resource data for networks in 0.818438204 seconds
2018-06-12T12:53:18 [W|app|fb52d] Failed to create a compute VMware (VMware) instance jim-paleo.toledo.satellite.lab.eng.rdu2.redhat.com: InvalidArgument: A specified parameter was not correct: podSelectionspec.storagePod

Expected results:
For it to build correctly.

Additional info:

Comment 1 Chris Roberts 2018-06-12 18:11:19 UTC

I tested this with DRS off on the storage pod:

http://nimb.ws/4sp9J3

And had the VM HDD selection set as the Storage Pod:

http://nimb.ws/ic1VHK

I did get the same error you are getting:

http://nimb.ws/tgOEmN

Along with the stack trace from the production log.

2018-06-12T12:53:16 [I|app|fb52d] Adding Compute instance for jim-paleo.toledo.satellite.lab.eng.rdu2.redhat.com
2018-06-12T12:53:17 [I|app|fb52d] Loaded compute resource data for networks in 0.818438204 seconds
2018-06-12T12:53:18 [W|app|fb52d] Failed to create a compute VMware (VMware) instance jim-paleo.toledo.satellite.lab.eng.rdu2.redhat.com: InvalidArgument: A specified parameter was not correct: podSelectionspec.storagePod

I then tested it with DRS enabled:

http://nimb.ws/LuFKW9

And it worked correctly:

http://nimb.ws/UvbVe5

http://nimb.ws/FghnSq

Comment 4 Satellite Program 2018-06-27 18:02:30 UTC

Upstream bug assigned to chrobert

Comment 5 Bryan Kearney 2019-07-02 18:01:56 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 6 Bryan Kearney 2019-08-01 18:35:12 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

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