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 |
||
|---|---|---|
| .. | ||
| destructive | ||
| nondestructive | ||
| tasks | ||
| README.md | ||
| destructive-ansible.yml | ||
| destructive-unit.yml | ||
| execute_batch.yml | ||
| libinsttest.sh | ||
| libtest-core.sh | ||
| nondestructive.yml | ||
| playbook-run.sh | ||
| provision.sh | ||
| run.sh | ||
README.md
This directory holds tests that use the Fedora Standard Test Interface.
The high level structure is that we take a qcow2 file, inject built RPMs into it, and then use Ansible to run tests.
See .papr.yml for canonical usage.
For local development, you should cache the qcow2 somewhere
stable (outside of this git repo). Also note that ../ci/build-rpms.sh
does not pick up uncommitted changes! Stated more strongly, you
currently need to run build-rpms.sh after every change.
To run just a specific test, use e.g.:
env TEST_SUBJECTS=/path/to/qcow2 ./playbook-run.sh -e tests=.*pull nondestructive.yml