Bug 2256464

Summary: Installer option --puppet-environment should be renamed to --puppet-agent-environment
Product: Red Hat Satellite Reporter: Amit Agarwal <amiagarw>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: ehelms, mjivraja, peter.vreman
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:40:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amit Agarwal 2024-01-02 13:03:05 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/release_notes/index

Section Number and Name: "Chapter 1. Summary of Changes"

Describe the issue: Inconsistent installer option puppet-environment. 
With Satellite 6.14 some of the satellite-installer options/flags were removed or renamed and some new options were added.
 


In Sat6.13  there was the option puppet-puppetmaster that is now replaced with puppet-agent-server-hostname.  The second option that is only for the puppet agent configuration 'puppet-environment' is not renamed to the 'puppet-agent-' argument namespace.  This makes the configuration inconsistent, what is the agent server in a different space but the environment that is also only relevant for the agent not in the agent namespace


"--puppet-environment" that is now is inconsistent without the "--puppet-agent-..." prefix although it is also a configuration dedicated to the puppet agent running on the satellite server itself.

Comment 1 Malhar Jivrajani 2024-01-04 06:19:44 UTC
Hi @amiagarw 

Are you looking for this? https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/release_notes/new-features

Comment 2 Amit Agarwal 2024-01-04 13:15:00 UTC
@mjivraja  Yes, That's correct.

Comment 4 Amit Agarwal 2024-01-12 20:19:24 UTC
Cu is looking for an update and its seems a valid request.

Comment 5 Amit Agarwal 2024-02-09 21:31:24 UTC
Cu is looking for an update and its seems a valid request.

Below documentation was the fix for the Other case 03661105 related to the option --foreman-proxy-content-puppet,--puppet-puppetmaster suddenly not supported anymore without any documentation that it is removed/replaced

 https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/release_notes/new-features



This query is related to the option  "--puppet-environment" that is now is inconsitent without the "--puppet-agent-..." prefix although it is also a configuration dedicated to the puppet agent running on the satellite server itself.

Comment 6 Malhar Jivrajani 2024-03-27 12:09:13 UTC
After carefully reviewing this BZ, it seems this does not require any action from the Document side at present. 

Customer is asking to rename the current `--puppet-environment` to `--puppet-agent-environment` but it seems to be a Development side action item. 

We are waiting if the BZ requires action from the Documentation or Development side.

@amiagarw Can you please link the support case to this BZ? Also, can you please interact with customer once again if we really need action item from Documentation side.

Thank you.

Comment 7 Eric Helms 2024-06-06 16:40:23 UTC
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.

Comment 8 Red Hat Bugzilla 2024-10-05 04:27:06 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days