This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1615733 - Image based provisioning cannot add SCSI controller
Summary: Image based provisioning cannot add SCSI controller
Keywords:
Status: CLOSED MIGRATED
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-08-08 14:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:30:51 UTC
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 Migrated None 2024-08-08 14:44:03 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.
Comment 24 Eric Helms 2024-06-05 21:30:51 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.