Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1985256

Summary:	[machines] bus type is not correct when adding a disk
Product:	Red Hat Enterprise Linux 8	Reporter:	YunmingYang <yunyang>
Component:	cockpit-appstream	Assignee:	Katerina Koukiou <kkoukiou>
Status:	CLOSED MIGRATED	QA Contact:	YunmingYang <yunyang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	mmarusak, mpitt, xchen
Target Milestone:	beta	Keywords:	MigratedToJIRA, Reopened, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 12:59:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description YunmingYang 2021-07-23 09:08:52 UTC

Description of problem:
When adding disk with "Custom path" for a VM(bus type of system disk is 'ide'), then select "Device" to "CD/DVD disc" and  select back to "Disk image file", at this time, click "Show additional options", "Bus" will be "sata". Then, click "Add", the bus of new added disk is "ide"


Version-Release number of selected components (if applicable):
cockpit-machines-249-1.el8.noarch
cockpit-249-1.el8.x86_64
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64

How reproducible:
100%


Steps to Reproduce:
1 Import a VM with "Unknown" for its "Operating system"
2 Go to the VM detail page, then click "Add disk"
3 Switch "Source" to "Custom path"
4 Select "Device" to "CD/DVD disc"
5 Select "Device" to "Disk image file"
6 Click "Show additional options", then input Custom path
7 Click "Add"

Actual results:
1 After step 6, bus of "additional options" is "sata"
2 After step 7, the disk will be added successfully, but its bus is "ide"

Expected results:
1 After step 7, The bus will be added successfully, and its bus is "sata"

Additional info:

Comment 1 Katerina Koukiou 2021-07-30 13:56:00 UTC

Upstream PR https://github.com/cockpit-project/cockpit-machines/pull/296

Comment 4 YunmingYang 2021-08-25 14:09:13 UTC

Test Versions:
cockpit-machines-251-1.el8.noarch
cockpit-251-1.el8.x86_64
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64


Test Steps:
1 Import a VM with "Unknown" for its "Operating system"
2 Go to the VM detail page, then click "Add disk"
3 Switch "Source" to "Custom path"
4 Select "Device" to "CD/DVD disc"
5 Select "Device" to "Disk image file"
6 Click "Show additional options", extend "Bus"
7 Click "Add"
8 Re-open "Add disk" dialog, then select 'Source' to "Custom path"
9 Select "Device" to "CD/DVD disc", then select back to "Disk image file", after that select "Device" to "CD/DVD disc" again
10 Click "Show additional options"
11 Click "Add"


Actual results:
1 In step 6, there is a disabled option which is "ide"
2 In step 7, the disk will be added successfully, but its bus is "ide"
3 In step 10, the "Bus" of "CD/DVD disc" is "ide"
4 In step 11, the disk will be added successfully, but its bus is "ide"


Expected results:
1 In step 6, there is no 'ide' option
2 In step 7, the disk should be added successfully, and its bus should not be "ide"
3 In step 10, the "Bus" of "CD/DVD disc" should no be "ide"
4 In step 11, the disk should be added successfullym and its bus should not be "ide"


Additional info:
I think this BZ caused by "custom path" getting bus value from the same type disks of the VM. Maybe we should disable this behavior, and just setState()


Test Results:
According to the results, there still something needed to be fixed, move 'Status' back to ASSIGNED.

Comment 6 Martin Pitt 2021-08-30 03:49:29 UTC

Moving to 8.6.

Comment 14 RHEL Program Management 2023-01-23 07:27:46 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 17 RHEL Program Management 2023-08-16 07:28:33 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 19 RHEL Program Management 2023-09-15 12:54:08 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 20 RHEL Program Management 2023-09-15 12:59:14 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 "RHEL-" 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.