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.
DescriptionJ.H.M. Dassen (Ray)
2011-11-09 15:31:05 UTC
3. What is the nature and description of the request?
The customer would like to see the Deployment Guide's Networking Section
modified to suggest using `alias netdev-bond0 bonding` in place of `alias bond0
bonding` due to BZ 680360.
4. Why does the customer need this? (List the business requirements
here)
The customer specifically requested for this enhancement after following the
documentation and receiving warning messages.
5. How would the customer like to achieve this? (List the functional
requirements here)
The customer would like to see the official documentation updated to reflect
that `alias netdev-bond0 bonding` should be used in place of `alias bond0
bonding`
6. For each functional requirement listed in question 4, specify how
Red Hat and the customer can test to confirm the requirement is
successfully implemented.
Red Hat can modify the documentation and the customer can verify that it
appears similar to the warning message displayed.
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
No, BZ 680360 describes the issue and the resolution, but does not include
documentation modification.
8. How quickly does this need resolved? (desired target release)
As soon as possible, pending resources.
9. Does this request meet the RHEL Bug and Feature Inclusion Criteria
(please review)
Yes, documentation modification.
10. List the affected packages
N/A
11. Would the customer be able to assist in testing this functionality
if implemented?
N/A