-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to v4.0.0 final #13255
Bump to v4.0.0 final #13255
Conversation
When attempting to create a network with a name that already exists, a 409 status code will be returned [NO NEW TESTS NEEDED] Signed-off-by: Jhon Honce <[email protected]>
Fixes: containers#12763 Signed-off-by: Daniel J Walsh <[email protected]>
Checkpoint/restore pod tests are not running with an older runc and now that runc 1.1.0 appears in the repositories it was detected that the tests were failing. This was not detected in CI as CI was not using runc 1.1.0 yet. Signed-off-by: Adrian Reber <[email protected]>
These are copies of the CNI tests with modifications wherever neccessary. Signed-off-by: Lokesh Mandvekar <[email protected]>
[NO NEW TESTS NEEDED] Signed-off-by: Morten Linderud <[email protected]>
Add some docs about the different network backends. Also remove the CNI word from network since we refer to either a netavark or CNI config. Signed-off-by: Paul Holzinger <[email protected]>
Merge the two tests to speed up testing. Both built the exact same images. Signed-off-by: Valentin Rothberg <[email protected]>
Signed-off-by: Patrycja Guzik <[email protected]> containers#13078 follow-up
Signed-off-by: Jason T. Greene <[email protected]>
Set proxy settings (such as `HTTP_PROXY`, and others) for the whole guest OS with setting up `DefaultEnvironment` with a `systemd` configuration file `default-env.conf`, a `profile.d` scenario file - `default-env.sh` and a `environment.d` configuration file `default-env.conf` The **actual** environment variables are read by podman at a start, then they are encrypted with base64 into a single string and after are provided into a VM through QEMU Firmware Configuration (fw_cfg) Device Inside a VM a systemd service `envset-fwcfg.service` reads the providead encrypted string from fw_cfg, decrypts and then adds to the files - `/etc/systemd/system.conf.d/default-env.conf` - `/etc/profile.d/default-env.sh` - `/etc/environment.d/default-env.conf` At the end this service execute `systemctl daemon-reload` to propagate new variables for systemd manager [NO NEW TESTS NEEDED] Closes containers#13168 Signed-off-by: esendjer <[email protected]>
…ck claim helper Signed-off-by: Jason T. Greene <[email protected]>
…t=t|f Switch default to rootless for mac and windows Signed-off-by: Jason T. Greene <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon 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 |
73466d0
to
3a77cb7
Compare
Failures are real. It's related to the minimum API version bump to v4.0.0, and it's somewhere in the manifest endpoints. Tests look sane, code is suspicious - https://github.com/containers/podman/blob/main/pkg/bindings/manifests/manifests.go#L110 references API versions under v4.0? Will continue looking but I am not an expert on this part of the code @jwhonce PTAL |
I suspect it has to do with the wrapper to support v3.x with 4.x libpod. My brain is too fried however. I've pinged @jwhonce @flouthoc and @Luap99 to PTAL 8a7e709#diff-044d310f157316ea3de231effda8f6822c587dd263482131fc09b6a2c12b0ddaR167 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TomSweeneyRedHat I am not a lot familiar with recent changes that went into manifests list operations
API, I think @jwhonce can tell this better but here is what i think is causing the issues.
With operations for service version greater than or equal to 4.0.0
now libpod uses a common PUT
to /manifests
with operation selected in payload
and new flow calls func ManifestModify(
in the end.
I think there might be issue in the way we are handling error here https://github.com/containers/podman/blob/main/pkg/api/handlers/libpod/manifests.go#L399.
It could use utils.Error(
to write error as it looks like in some cases error is being returned correctly but for some cases it is not writing error payload and also ignoring actual status.
But this is just my suspect I'm sure @jwhonce can tell this better.
/lgtm |
Branch forced 4.0 only endpoints Signed-off-by: Jhon Honce <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
e23f25e
to
d59749d
Compare
Repushed with Jhon's fixes included |
/lgtm |
Two flakes. Rerunning. |
Looks like tests are going to pass |
/hold cancel |
As the title says. Final backports, release notes updates, and the version bump.