RHEL gating tests: more journald exceptions

[edsantiago]

Followup to #8284, due to my not having noticed #8096.

RHEL gating tests are failing again due to rhbz#1895105, the
one where we can't run journalctl rootless on RHEL. #8284 fixed
this for some RHEL builds of older podman, but I missed #8096
which added yet another logs test.

This brings us to three journalctl exceptions, which means
it gets complicated because I have to refactor it all.

THIS IS NOT SUSTAINABLE. We need some way to have a similar
setup in CI, with a permission-less rootless login, so we don't
add yet another logs test some day and discover, months later,
that it doesn't work on RHEL and then have to go into crisis
mode.

Signed-off-by: Ed Santiago [email protected]

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [edsantiago]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[edsantiago]

@jnovy FYI

[rhatdan]

LGTM

[edsantiago]

@containers/podman-maintainers PTAL. Suggestions welcome on how we can catch this sort of problem earlier.

I tested the new code on a RHEL VM, and the journal tests are indeed skipped when run rootless.

[mheon]

LGTM

[mheon]

/lgtm

[mheon]

Would podman-in-a-container catch the journald case? We wouldn't have access to the host systemd, so I presume journald would blow up.

[edsantiago]

Hmmm. Looks like we lost in_podman testing when we switched to CI v2. @cevich was that intentional?

@mheon I'm not sure how to test, but my gut feel is that P-in-P would not catch this: the symptom we're looking for is:

$ journalctl -n 1
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.

This happens when journalctl is run as rootless on RHEL on an account that is not in wheel or other special magic groups. IIRC, even when we were doing P-in-P testing, the tests ran as root inside the container so any journalctl error would be different, I think?

[cevich]

Looks like we lost in_podman testing when we switched to CI v2.

It's there, just has a new name, container_integration_test...errr, where is container_system_test? I swore it was there...huh...apparently only in my imagination. Okay I'll add it...must have got lost in the shuffle.