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.

Bug 2207823

Summary: There is no documentation on how to reset journald logging back to default
Product: Red Hat Satellite Reporter: Alexey Masolov <amasolov>
Component: InstallationAssignee: Aneta Šteflová Petrová <apetrova>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: agadhave, ehelms, mjivraja
Target Milestone: UnspecifiedKeywords: Documentation, 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: 2023-08-04 12:08:04 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 Alexey Masolov 2023-05-17 03:46:43 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/administering_red_hat_satellite/index#Configuring_Logging_to_Journal_admin

Section Number and Name: 
17.6. Configuring Logging to Journal

Describe the issue: 
There is no procedure on how to revert the change back to default.

Suggestions for improvement: 
satellite-installer \
--reset-foreman-logging-layout \
--reset-foreman-logging-level \
--reset-foreman-logging-type \
--reset-foreman-proxy-log


Additional information:

Comment 1 Marie Hornickova 2023-05-17 08:36:38 UTC
Hello Alexey,

Thank you very much for reporting this suggestion for improvement! 

The BZ will go through proper team triage and once the documentation is updated, the link will be shared in this ticket.

Thank you!

Comment 2 Aneta Šteflová Petrová 2023-07-06 10:42:21 UTC
PR submitted for review: https://github.com/theforeman/foreman-documentation/pull/2278

Comment 3 Aneta Šteflová Petrová 2023-07-24 12:24:29 UTC
Merged: https://github.com/theforeman/foreman-documentation/pull/2278#event-9899543107

Comment 5 Red Hat Bugzilla 2023-12-03 04:25:09 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days