Bug 1615733 - Image based provisioning cannot add SCSI controller
Summary: Image based provisioning cannot add SCSI controller
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-14 06:56 UTC by Sanket Jagtap
Modified: 2024-03-20 19:42 UTC (History)
3 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24887 0 Normal New Image based provisioning cannot add SCSI controller 2020-08-03 11:14:13 UTC
Red Hat Bugzilla 1538597 0 urgent CLOSED Cannot add new disk to VM when using image based to provision 2021-12-10 15:36:17 UTC
Red Hat Issue Tracker SAT-23180 0 None None None 2024-02-11 20:21:42 UTC

Internal Links: 1538597

Description Sanket Jagtap 2018-08-14 06:56:15 UTC
Description of problem:
While doing Image based provisioning, you cannot add more SCSI controller to the provisioned VM

Version-Release number of selected component (if applicable):
Build: Satellite 6.4.0 snap17

How reproducible:
Always

Steps to Reproduce:
1. Create a VM using Image based provisioning
2. In the VM tab, under storage section, add a new controller
3.

Actual results:
Unable to save
Failed to create a compute vmware (VMware) instance patti-jacobitz.domiain: InvalidController: The device '2' is referring to a nonexisting controller '1,001'. 

Expected results:
Host should be created

Additional info:
PFA production log

Comment 4 Marek Hulan 2018-09-11 10:06:48 UTC
Created redmine issue https://projects.theforeman.org/issues/24887 from this bug

Comment 8 Bryan Kearney 2019-09-03 19:06:59 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 12 Bryan Kearney 2020-01-31 21:06:19 UTC
Upstream bug assigned to chrobert

Comment 13 Bryan Kearney 2021-03-17 20:03:08 UTC
Upstream bug assigned to chrobert

Comment 14 Bryan Kearney 2021-04-13 10:14:59 UTC
Upstream bug assigned to chrobert

Comment 16 Bryan Kearney 2021-10-01 00:00:48 UTC
Upstream bug assigned to chrobert

Comment 17 Bryan Kearney 2022-02-17 16:01:26 UTC
Upstream bug assigned to chrobert

Comment 18 Bryan Kearney 2022-06-10 00:00:54 UTC
Upstream bug assigned to chrobert

Comment 21 Brad Buckingham 2024-02-11 20:37:14 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 23 Brad Buckingham 2024-03-20 19:42:04 UTC
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional discussion; however, it may be closed in a future iteration.


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