Hey Justin,
Interestingly, I noticed the same issue just today in our CI. Did some debugging in [1], but here is a quick summary.
Due to the new way of gaining and dropping administrative access in Cockpit, this message crept up into every test.
We of course adjusted our tests, but due to locking down versions of cockpit tests in external projects, this change was not propagated.
The best option is to bump up the version of tests to 219. I just did that for two external projects that were affected, see for example [2].
If that would be impractical (possibly as it would break your tests in any other way), then just calling `allow_authorize_journal_messages()` in every affected test should be enough.
I checked how you run tests and you pick tests from rhel-8.2 branch [3], which is now locked down. We don't have yet 8.3 branch, we use master for that. I suggest using tag `219`, that should work.
Hope this helps!
MM
--
Matej Marušák
Software Engineer
Red Hat
