Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
1. Proposed title of this feature request
[RFE] Full Support for PXE and PXEless provisioning over VLAN tagged interfaces via Red Hat Satellite 6
2. What is the nature and description of the request?
Ensure that Satellite is capable of performing system deployments with VLAN configurations for any PXE or PXEless deployment methods.
3. Why does the customer need this? (List the business requirements here)
Using VLAN tagging ( whether on a single interface or a bond ) is a pretty common use case in the Networking\RHEL world and our end users would like to see satellite doing a complete deployment of a system with proper VLAN tagging configured as expected.
In https://access.redhat.com/solutions/2674001#fnref:12 we mention that it's "known to work" but we don't know what means by "known to work" or how far it should work and for which deployment options.
4. How would the customer like to achieve this? (List the functional requirements here)
Via provisioning feature of the satellite.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Well, Even before an user can test anything, RedHat needs to confirm the scope of support
The VLAN tagging needs to be tested for
* Static as well as DHCP based IP addressing
* Any PXE and PXEless metohds we have
* Single interface as well as for Bonded Interfaces
And it is expected to work not only during kickstart stage but also during the PXE stage.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No i believe but similar RFE is present for Bond based deployments -> https://bugzilla.redhat.com/show_bug.cgi?id=1935088
Two related BZs present as well pointing to two specific bugs i.e.
https://bugzilla.redhat.com/show_bug.cgi?id=2075717https://bugzilla.redhat.com/show_bug.cgi?id=2075358
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
As soon as possible ( or in the next major release of the product )
8. Is the sales team involved in this request and do they have any additional input?
No
9. List any affected packages or components.
Foreman
10. Would the customer be able to assist in testing this functionality if implemented?
Perhaps. RH support will definitely be able to help.
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.