Hello! Do we have any advances on this? I can see that the PR is approved, but not more movements on it. Could we know anything? Regards, Oscar
something's gone wrong with the unit tests and crio tests. I haven't had time to investigate, and may need to call reinforcements to help. Thanks for your patience
verified in version: oc v3.11.317 kubernetes v1.11.0+d4cacc0 run the following script and found no cases: #!/bin/bash docker ps -q | while read line; do if [ `find /var/log/containers -name *$line* | wc -l` = "0" ] then name=`docker inspect $line | grep "Name" | head -n 1 | cut -d ":" -f 2 | head -c 6` if [ $name != '"/k8s' ] then docker inspect $line | grep "Name" | head -n 1 fi fi done
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 3.11.318 bug fix and enhancement update), 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:5107
Adding my comments from Case 03292252 Also to add more clarification I am the OCP TAM for this customer. The key to this case is they are looking for guidance in developing a custom solution to re-create the sym links as they are worried that their existing custom deployments could possibly break with an upgrade. So what they are looking for is a way, if possible to have a custom script (much like the one provided here that can be modified to re-create those links and possibly be incorporated into a cron job to run at whatever times they deem are safe to run) Thanks! Kenan Fyfe