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
Show a message or warning if custom-hiera.yaml or custom answers file is being used by satellite-installer
2. What is the nature and description of the request?
A change in installer\foreman_maintain code to show a message\warning ( in bold ) about the usage of custom-hiera or any custom answers file.
3. Why does the customer need this? (List the business requirements here)
* custom-hiera.yaml: The user can mention many things here which are or mainly aren't possible to achive via installer options and hence the end-user needs to know if satellite is inheriting any values\settings mentioned in custom-hiera.yaml file. We don't need to be specific but we can definitely tell users that they have something defined in the same file which will be considered by installer.
* Custom Answers file: Satellite by-default comes with /etc/foreman-installer/scenarios.d/satellite-answers.yaml file but we also support users to define and use their own answers file. Sometimes, when we leave things in user's control, They can remove certain important options from the answers file which may be required for future upgrades but such attempts would fail due to having those missing answers\options or their wrong values.
Example: Pulp2-Pulp3 migration fails\completes witout performing anything i.e.
~~
Prepare content for Pulp 3:
Checking for valid Katello configuraton.
Switchover is already complete, skipping migration work.
[OK]
~~
And this is because the user have wrong values set for the required options in their custom answers file. Support case 03301603 ( Comment 50 and above ) is a good example of how things can easily take a weird turn.
4. How would the customer like to achieve this? (List the functional requirements here)
RH Support only requests here to add a warning\message ( in bold ) whenever some valid yaml block is present in custom-hiera or a custom answers file is used by installer.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Depends on Point 4 but
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No, as far as I can say
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
As soon as it is feasible.
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-installer
- satellite-installer
10. Would the customer be able to assist in testing this functionality if implemented?
RH Support can
11. Additional information:
NA
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.
1. Proposed title of this feature request Show a message or warning if custom-hiera.yaml or custom answers file is being used by satellite-installer 2. What is the nature and description of the request? A change in installer\foreman_maintain code to show a message\warning ( in bold ) about the usage of custom-hiera or any custom answers file. 3. Why does the customer need this? (List the business requirements here) * custom-hiera.yaml: The user can mention many things here which are or mainly aren't possible to achive via installer options and hence the end-user needs to know if satellite is inheriting any values\settings mentioned in custom-hiera.yaml file. We don't need to be specific but we can definitely tell users that they have something defined in the same file which will be considered by installer. * Custom Answers file: Satellite by-default comes with /etc/foreman-installer/scenarios.d/satellite-answers.yaml file but we also support users to define and use their own answers file. Sometimes, when we leave things in user's control, They can remove certain important options from the answers file which may be required for future upgrades but such attempts would fail due to having those missing answers\options or their wrong values. Example: Pulp2-Pulp3 migration fails\completes witout performing anything i.e. ~~ Prepare content for Pulp 3: Checking for valid Katello configuraton. Switchover is already complete, skipping migration work. [OK] ~~ And this is because the user have wrong values set for the required options in their custom answers file. Support case 03301603 ( Comment 50 and above ) is a good example of how things can easily take a weird turn. 4. How would the customer like to achieve this? (List the functional requirements here) RH Support only requests here to add a warning\message ( in bold ) whenever some valid yaml block is present in custom-hiera or a custom answers file is used by installer. 5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Depends on Point 4 but 6. Is there already an existing RFE upstream or in Red Hat Bugzilla? No, as far as I can say 7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? As soon as it is feasible. 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-installer - satellite-installer 10. Would the customer be able to assist in testing this functionality if implemented? RH Support can 11. Additional information: NA