Description of problem: Now in cri-o system container the log-level=debug, In product we should avoid use debug mode. Version-Release number of selected component (if applicable): crio version 1.0.2 commit: "29077fa6fbd85f0ca9c453ab1bf1ff7b02bc3f5c" How reproducible: Always Steps to Reproduce: 1.Get cri-o from private registry then check the loglevel [root@ip-172-18-4-251 cri-o.0]# pwd /var/lib/containers/atomic/cri-o.0 [root@ip-172-18-4-251 cri-o.0]# cat rootfs/usr/bin/run.sh #!/bin/sh # Ensure that new process maintain this SELinux label PID=$$ LABEL=`tr -d '\000' < /proc/$PID/attr/current` printf %s $LABEL > /proc/self/attr/exec exec /usr/bin/crio --log-level=debug 2. 3. Actual results: Expected results: Additional info:
cri-o related bugs are not blocking 3.7, all cri-o bugs should default target release of 3.8.
Giuseppe, Can we fix this in the installer config?
PR here: https://github.com/projectatomic/atomic-system-containers/pull/139
PR merged, moved to MODIFIED
Verify on crio version 1.8.2 # cd /var/lib/containers/atomic/cri-o.0 # ./rootfs/usr/bin/crio --version crio version 1.8.2 # cat rootfs/usr/bin/run.sh #!/bin/sh # Ensure that new process maintain this SELinux label PID=$$ LABEL=`tr -d '\000' < /proc/$PID/attr/current` printf %s $LABEL > /proc/self/attr/exec exec /usr/bin/crio --log-level=$LOG_LEVEL # cat config.json |grep "LOG_LEVEL" "LOG_LEVEL=info",
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, 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-2018:0489