Ge this is expected, rollbackcopy was deployed for the specific intent of ensuringin a backup existed between 4.4 and 4.5 backups. So it was removed in 4.6.

It looks like something in this code added the immutable bit on the target directory, which in turn breaks ostree upgrades.

Sam, is this something that was enabled by default for all customers, or something they had to opt-in to?  So far I've only heard of one instance.

More carefully reading Comment #1 - to reproduce this, we'd need to do a 4.4 install, then...potentially wait until the rollbackcopy kicked in (?) then do an upgrade to 4.5+ to hit this?

Where is the code for "rollbackcopy"?  I did `git log -G rollbackcopy` in both openshift/cluster-etcd-operator and openshift/etcd, no hits.  Launching a 4.4 cluster now to see this sidecar.

>It looks like something in this code added the immutable bit on the target directory, which in turn breaks ostree upgrades.

The immutable bit was set to disable rollbackcopier only in extreme cases which would of been applied by the CU or support. I will get a link.