The reporter cannot reproduce this issue either. According to snap changes there was a core refresh in last night so whatever (perhaps broken) state was present in the mount profiles or mount namespace was discarded.
I am still checking if the set of mount changes executed with the pair of layouts items and the incrementing revision would do something unexpected.
The reporter cannot reproduce this issue either. According to snap changes there was a core refresh in last night so whatever (perhaps broken) state was present in the mount profiles or mount namespace was discarded.
I am still checking if the set of mount changes executed with the pair of layouts items and the incrementing revision would do something unexpected.