systemd system test: run auto-update #6810
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
Testing with a local registry will be difficult unless |
Good point. We could either extend the CLI and add that as a flag or we create a custom registries.conf where we mark the registry as insecure. |
Run `podman auto-update` in the systemd system tests. Note that this is a first step to at least exercise parts of `auto-update` in the CI. The service won't get updated just yet as we need to set up a local registry, and push a new image. I do not have enough time at the moment to do that but consider this change already as an improvement. We are experiencing some issues in containers#6793 w.r.t. to auto-updates but couldn't track down the root cause yet. Signed-off-by: Valentin Rothberg <[email protected]>
vrothberg
force-pushed
the
auto-update-test
branch
from
bd0a5d6 to
43714ca
Compare
|
Repushed to get tests running again. GitHub was down today. |
|
@mheon, I want this in the v2 branch as well. Just to be sure. |
|
We really need a backports label... |
|
Changes LGTM |
|
Ready to merge :) |
|
/lgtm |
github-actions
bot
added
the
locked - please file new issue/PR
Run
podman auto-updatein the systemd system tests. Note that this isa first step to at least exercise parts of
auto-updatein the CI. Theservice won't get updated just yet as we need to set up a local
registry, and push a new image. I do not have enough time at the moment
to do that but consider this change already as an improvement.
We are experiencing some issues in #6793 w.r.t. to auto-updates but
couldn't track down the root cause yet.
Signed-off-by: Valentin Rothberg [email protected]