Description of problem: This may be a dupe of BZ1425278, which was closed without fixing, but it's very difficult to work on the RHCOS serial console with these endless messages scrolling constantly. This really can't be fixed? Version-Release number of selected component (if applicable): 46.82.202008102140-0 How reproducible: Always Steps to Reproduce: 1. Install OpenShift 2. Connect to serial console of RHCOS Actual results: [ 1731.969847] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1736.985146] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1738.356796] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1738.479952] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1738.628935] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1763.433276] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1806.802133] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1806.982003] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1808.955390] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1815.951076] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1827.257757] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1828.947888] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1834.964451] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) [ 1835.941465] SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue) Expected results: No warnings about SELinux mounts Additional info: [core@master-0 ~]$ cat /etc/os-release NAME="Red Hat Enterprise Linux CoreOS" VERSION="46.82.202008102140-0" VERSION_ID="4.6" OPENSHIFT_VERSION="4.6" RHEL_VERSION="8.2" PRETTY_NAME="Red Hat Enterprise Linux CoreOS 46.82.202008102140-0 (Ootpa)" ID="rhcos" ID_LIKE="rhel fedora" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:8::coreos" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="OpenShift Container Platform" REDHAT_BUGZILLA_PRODUCT_VERSION="4.6" REDHAT_SUPPORT_PRODUCT="OpenShift Container Platform" REDHAT_SUPPORT_PRODUCT_VERSION="4.6" OSTREE_VERSION='46.82.202008102140-0'
Unfortunately, per comment 27 on BZ#1425278 this is a message from `runc`, has been around for a long time and is unlikely to be fixed. I can send this over to the Containers team, but I expect it is going to be closed as a duplicate.
As noted in https://bugzilla.redhat.com/show_bug.cgi?id=1425278 this is an issue in runc that we've very little control over. I'm going to assign to Dan Walsh to make a final decision, in case there's an angle that he's aware of that we might be able to make a change somewhere, but I suspect he'll close this as "Won't Fix" (really can't fix) as Micah noted.
Do we see the same message from crun?
I've had to spend most of my day in RHCOS on the serial console and it's a very frustrating experience to be interrupted every few seconds by these messages. Can they be hidden somehow, if it won't be fixed?
Opened a PR upstream runc to fix this. https://github.com/opencontainers/runc/pull/2558 Hopefully this will get into the next release of runc.
Setting this to upcoming sprint as the fix is going through the review process.
The upstream PR has merged that we were waiting for, now we need to wait on upstream to release a new runc. Moving to upcoming sprint.
Jindrich and Lokesh could we release this newer version of RUNC. We have been releasing from master branch for a while, since runc has never declared a 1.0 release.
Dan, Jindrich and Lokesh, This is currently on the blocker list for OCP 4.6 which is freezing next Friday Oct 2, 2020. Can we get this done before then or do we need to move it to OCP 4.7?
Tom, I've updated runc in rhaos-4.6 to the current master - 190fcf2 - which has the PR in comment #5 applied.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196