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.
Description of problem:
I updated the "PXELinux global default" where I updated ONTIMEOUT option and set it to 'discovery' from 'local'.
Also I updated the "pxelinux_discovery" snippet with correct proxy.type and proxy port. template was updated.
However, later when I re-run the installer, all changes were gone and they don't persists after re-running the installer. I'm not sure the expected behavior but I think template changes should persists.
Version-Release number of selected component (if applicable):
sat6.3 snap5
How reproducible:
Steps to Reproduce:
1. make changes in "PXELinux global default" and "pxelinux_discovery"
2. re-run installer
3.
Actual results:
template changes doesn't persists
Expected results:
changes should persists
Additional info:
Thanks for the report Sachin, I think this is a duplicate of bz 1382008, please look there suggested solution and the status. If I misunderstood the report, please reopen.
*** This bug has been marked as a duplicate of bug 1382008 ***