subham rai

@Rakshith-R isn't this issue similar to #10935 ?

> @subhamkrai this will cover #10829 right? yes, part of it not completely.

> @subhamkraiI didn't find the evidence that snapd or snap applications used a file under /mnt by `fuser -muv` or listing all `/proc//fd`. However, I confirmermed that everything worked fine...

> > @zhucan I restarted the failing CI again but seems like somehow ci failing due to the changes. Can you look at the CI errors? > > It looks...

The build is failing because `github.com/jstemmer/go-junit-report v1.0.0 // indirect` is not imported anywhere but this library is added during `make test`. I confirmed with @parth-gr also. @BlaineEXE @travisn any idea...

I also noticed in one of the PR #10638 the same error I'm seeing. Seems like the issue is coming from golang 1.18 only(I have 1.18 in my local)

should I delete this pr then?

> > should I delete this pr then? > > If we can find a fix for both 1.17 and 1.18 that works in this PR, would be nice to...

@anthonyeleven 1 .10 will somewhere around 2nd half of next month @travisn can answer better. But I think you can run toolbox yaml from the master which will give you...

@hansbogert you can disable admission controller https://github.com/rook/rook/blob/master/deploy/examples/operator.yaml#L563 but it is helpful to debug if you could share some logs 1. rook operator logs 2. secret lists(seems like the admission controller...