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.
I think this RFE is not clear.
From https://bugzilla.redhat.com/show_bug.cgi?id=1509049#c2, it seems this only affects nm-connection-editor.
Could you better describe what is requested? And how anaconda is going to use this? Thank you.
(In reply to Thomas Haller from comment #1)
> I think this RFE is not clear.
>
> From https://bugzilla.redhat.com/show_bug.cgi?id=1509049#c2, it seems this
> only affects nm-connection-editor.
>
> Could you better describe what is requested? And how anaconda is going to
> use this? Thank you.
Redirecting needinfo to Radek
Yes, we'd need to be able to constrain somehow the types of devices (exclude bond0) created in Anaconda GUI, that is: nm-c-e. As for use from anaconda this would be achieved by passing a cmdline option (profile file?) to nm-c-e. Seems like a whole new mechanism would be needed. But I think we need to clear up other questions before starting to work on the GUI part (https://bugzilla.redhat.com/show_bug.cgi?id=1509049#c8).
Comment 4Beniamino Galvani
2020-04-07 16:30:34 UTC
Hi Radek,
do you have any update? Should we start to plan the work on this?
The bug 1509049 has been closed as wontfix because it is impossible to support the feature in kickstart for Anaconda in RHEL 8, so definitely not an 8.5 (or even 8.X) material. I am closing the bug with the same resolution as bug 1509049.