7468600029
For `rpm-ostree ex livefs` we have a use case of pushing a rollback deployment. There's no reason this should require deleting the staged deployment (and doing so actually breaks livefs which tries to access it as a data source). I was initially very conservative here, but I think it ends up being fairly easy to retain the staged deployment. We need to handle two cases: First, when the staged is *intentionally* deleted; here, we just need to unlink the `/run` file, and then everything will be sync'd up after reloading. Second, (as in the livefs case) where we're retaining it, e.g. adding a deployment to the end. What I realized here is that we can have the code keep `new_deployments` as view without staged, and then when we do the final reload we'll end up re-reading it from disk anyways. Closes: #1672 Approved by: jlebon |
||
|---|---|---|
| .. | ||
| README.md | ||
| itest-bare-root.sh | ||
| itest-deploy-selinux.sh | ||
| itest-label-selinux.sh | ||
| staged-deploy.yml | ||
| var-mount.yml | ||
README.md
This suite of tests is run from PAPR. Everything in here is destructive; it's
recommended to only run them in disposable virtual machines. This is done
in tests/fedora-str/sysinstalled-tests.yml, which currently uses a single VM
and runs the tests serially. It's likely in the future this will be changed
to do one VM per test.