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.
hey Lukas, the guide looks good, but i think it is missing the "promised" attached rsyslog.conf.
There's a step saying:
"Create file /etc/rsyslog.d/foreman.conf with content attached to this article."
- and then there's just a small part of it which is supposed to come to the end of the file: "The most important part is ElasticSearch action block at the very end of the configuration file".
Could you revisit the article and attach the missing bits?
- perhaps that step could be separated from the "Create normalization configuration files" step, so it is more obvious these are different.
VERIFIED
- tested on sat6.4.0-22
- all my comments and findings got added/addressed.
- deployed ES on a different rhel box and got the setup up and working by simply following the steps described in the article.
great job @lzap!