Skip to content
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-RC5 #13203

Merged
merged 19 commits into from
Feb 11, 2022
Merged

Bump to v4.0.0-RC5 #13203

merged 19 commits into from
Feb 11, 2022

Conversation

mheon
Copy link
Member

@mheon mheon commented Feb 10, 2022

Also includes associated release notes updates and backports

edsantiago and others added 16 commits February 10, 2022 13:47
Revert containers#13049. criu-3.16.1-6.fc36 fixes the problem and is
now in fc36 stable:

   https://bodhi.fedoraproject.org/updates/FEDORA-2022-183b337712

(Yes, I confirmed that tests pass on a rawhide vm)

Signed-off-by: Ed Santiago <[email protected]>
separated cgroupNS sharing from setting the pod as the cgroup parent,
made a new flag --share-parent which sets the pod as the cgroup parent for all
containers entering the pod

remove cgroup from the default kernel namespaces since we want the same default behavior as before which is just the cgroup parent.

resolves containers#12765

Signed-off-by: cdoern <[email protected]>
Signed-off-by: cdoern <[email protected]>
Signed-off-by: cdoern <[email protected]>
Append the podman dns seach domain to the host search domains when we
use the dnsname/aardvark server. Previously it would only use podman
seach domains and discard the host domains.

Fixes containers#13103

Signed-off-by: Paul Holzinger <[email protected]>
Bumps [github.com/buger/goterm](https://github.com/buger/goterm) from 1.0.1 to 1.0.4.
- [Release notes](https://github.com/buger/goterm/releases)
- [Commits](buger/goterm@v1.0.1...v1.0.4)

---
updated-dependencies:
- dependency-name: github.com/buger/goterm
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
foramtError was written as err
[NO NEW TESTS NEEDED]

Signed-off-by: myml <[email protected]>
It seems we are ignoring output from healthcheck session.
Open a valid pipe to healthcheck session in order read its output.

Use common pipe for both `stdout/stderr` since that was the previous
behviour as well.

Signed-off-by: Aditya R <[email protected]>
All the healthcheck return output now but systems tests is written to
expect empty output which seems wrong.

Modify jq output to contain newline character rather than actual newline

Signed-off-by: Aditya R <[email protected]>
Followup to containers#13129: remove a no-longer-necessary workaround
for a healthcheck bug.

Signed-off-by: Ed Santiago <[email protected]>
…son in reponse

Lot of clients are expecting proper `Content-type: application/json`
configured in response headers of `/build` compat api. Following commit
fixes that.

Fixes issues where code is setting header field after writing header
which is wrong. We must set `content-type` before we write and flush
http header.

Signed-off-by: Aditya R <[email protected]>
When running podman inside systemd user units, it is possible that
systemd kills the rootless netns slirp4netns process because it was
started in the default unit cgroup. When the unit is stopped all
processes in that cgroup are killed. Since the slirp4netns process is
run once for all containers it should not be killed. To make sure
systemd will not kill the process we move it to the user.slice.

Fixes containers#13153

Signed-off-by: Paul Holzinger <[email protected]>
'killContainerTimeout' is already 5 second
[NO NEW TESTS NEEDED]

Signed-off-by: myml <[email protected]>
Right now it is not possible to look at the API version for a specific
version. docs.podman.io always show the latest version from the main
branch. This is not want many users want so they now have the ability to
select a different version.

Fixes containers#12796

Signed-off-by: Paul Holzinger <[email protected]>
I do not know why this code was added but it is wrong. We should never
use a plugin dir as config dir. Also this will fail for netavark. The
correct default will be set in c/common so podman should not touch it.

[NO NEW TESTS NEEDED]

Ref containers#13183

Signed-off-by: Paul Holzinger <[email protected]>
The `podman network connect` and `podman network disconnect`
commands give containers access to different networks than the
ones they were created with; these networks can also have DNS
servers associated with them. Until now, however, we did not
modify resolv.conf as network membership changed.

With this PR, `podman network connect` will add any new
nameservers supported by the new network to the container's
/etc/resolv.conf, and `podman network disconnect` command will do
the opposite, removing the network's nameservers from
`/etc/resolv.conf`.

Fixes containers#9603

Signed-off-by: Matthew Heon <[email protected]>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2022
@rhatdan
Copy link
Member

rhatdan commented Feb 10, 2022

We might want to hold this up untile @lsm5 Figures out containers/storage#1131

@mheon
Copy link
Member Author

mheon commented Feb 10, 2022

I'll leave this open to let CI bake, but I'm fine waiting for that to get resolved.

@mheon
Copy link
Member Author

mheon commented Feb 10, 2022

API unit tests are failing, on a test that seems to validate that the current version is compatible with the API. This makes me think the bump to v4.0.0 as the minimum is conflicting with the v4.0.0-dev version set.

@Luap99
Copy link
Member

Luap99 commented Feb 10, 2022

The api test are hard coded for v3.1,see

.Components[0].Details.MinAPIVersion=3.1.0 \
You have to change this to 4.0 as well.

@mheon
Copy link
Member Author

mheon commented Feb 10, 2022

@Luap99 That's the APIv2 tests - the unit tests are failing very differently.

@mheon
Copy link
Member Author

mheon commented Feb 10, 2022

Specifically

func TestSupportedVersion(t *testing.T) {
req, err := http.NewRequest("GET",
fmt.Sprintf("/v%s/libpod/testing/versions", version.APIVersion[version.Libpod][version.CurrentAPI]),
nil)
if err != nil {
t.Fatal(err)
}
req = mux.SetURLVars(req, map[string]string{"version": version.APIVersion[version.Libpod][version.CurrentAPI].String()})
rr := httptest.NewRecorder()
handler := http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
_, err := SupportedVersionWithDefaults(r)
switch {
case errors.Is(err, ErrVersionNotGiven): // for compat endpoints version optional
w.WriteHeader(http.StatusInternalServerError)
fmt.Fprint(w, err.Error())
case errors.Is(err, ErrVersionNotSupported): // version given but not supported
w.WriteHeader(http.StatusBadRequest)
fmt.Fprint(w, err.Error())
case err != nil:
w.WriteHeader(http.StatusInternalServerError)
fmt.Fprint(w, err.Error())
default: // all good
w.WriteHeader(http.StatusOK)
fmt.Fprint(w, "OK")
}
})
handler.ServeHTTP(rr, req)
if status := rr.Code; status != http.StatusOK {
t.Errorf("handler returned wrong status code: got %v want %v",
status, http.StatusOK)
}
// Check the response body is what we expect.
expected := `OK`
if rr.Body.String() != expected {
t.Errorf("handler returned unexpected body: got %q want %q",
rr.Body.String(), expected)
}
}
is failing - returning 400 not 200

Signed-off-by: Matthew Heon <[email protected]>
Signed-off-by: Matthew Heon <[email protected]>
@edsantiago
Copy link
Member

Three failures in int tests, all of them remote. Unfortunately I can't figure out any elements common to the failures.

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

It's all manifest changes. I don't think I did any backports that would affect that code?

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

I'm going to restart just one of the tests, in the hopes that it was transitory; if that passes we're probably OK.

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

Nope, failures are consistent. OK...

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

It's all manifest failures. Nearest I can tell there are no manifest-related changes in this PR, either to code or tests. I'm going to get another PR pushed to try and verify.

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

I don't know how, but bumping minimum API version breaks the Libpod API manifest endpoints. I want to debug this, but it's Friday afternoon, so I'm going to vote that we release the RC now and debug later.

CI is barfing and this seems like the most likely cause.

Signed-off-by: Matthew Heon <[email protected]>
@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

One flake (I hope...) - restarted

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

Another flake. Restarted.

@mheon
Copy link
Member Author

mheon commented Feb 11, 2022

Ready

@rhatdan
Copy link
Member

rhatdan commented Feb 11, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 11, 2022
@openshift-merge-robot openshift-merge-robot merged commit b0a445e into containers:v4.0 Feb 11, 2022
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants