Open
Conversation
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
State of the game
Still not green, but I need to report the status in order to get instructions for further steps.
Opening this as the ubuntu OS has some chance of success imho.
The ubuntu test is failing on the
verifystep - thehaproxy-http.logandhaproxy-tcp.logare not present. This might be similar to #19.The bigger question is whether or not to pursue the ubuntu track:
Rocky and RHEL in docker/molecule:
On Rockylinux9 and also RHEL9 in molecule see also #24
The images above I cannot either make work at all, or, when they work, they also show the same problem -
rsyslogservice will not restart. I am not able to fix it by installing from different repo either - "error" (if it is one, because it is very long and confusing) attached at the bottom. Capping of rsyslog version for the one which is working on our RHEL 9 VMs did not work either.Note: the health-check cmd
rsyslogd -N1is actually giving a positive resultRHEL 9 VM:
This seems to me like the most reasonable path to pursue.
I have created a playbook based on this role and ran it on 134.36.4.3 RHEL9 testing VM. This went without errors. The
rsyslogis already pre-installed on this VM, so the problem which occurs with docker images on Rocky/RHEL (see above) does not happen.The only drawback: The
haproxy-tcp.logfile does not seem to exist. But I believe the logrotation is working:Error from the
rsyslogfailed start:rsyslogd-dn-output.txt