chore(deps): update dependency containers/automation_images to v20240513 - autoclosed

[renovate]

This PR contains the following updates:

Package	Update	Change
containers/automation_images	major	20240411t124913z-f39f38d13 -> 20240513t140131z-f40f39d13

---

Release Notes

containers/automation_images (containers/automation_images)

v20240513t140131z-f40f39d13

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: renovate[bot]
Once this PR has been reviewed and has the lgtm label, please assign ashley-cui for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[packit-as-a-service]

Ephemeral COPR build failed. @containers/packit-build please check.

[edsantiago]

I'm having a very hard time grokking those test logs, but this:

creating read-only layer with ID \"897856b864da34858af854187ea37dd01eafe09e988691597cad51eb8673bf49\": no space left on device", err:(*fmt.wrapError)(0xc0002ea460)}

...makes me suspect that we can't use tmpfs-/tmp on buildah: too diskhoggy. I've run into the same problem with 1minutetip. Only solution I can think of is to hardcode TMPDIR=/var/tmp. Any other ideas?

[edsantiago]

Plug for my podman-ginkgo-highlight GreaseMonkey script, which colorizes the PASS/FAIL lines. Still very human-unfriendly, but better.

[Luap99]

I'm having a very hard time grokking those test logs, but this:

creating read-only layer with ID \"897856b864da34858af854187ea37dd01eafe09e988691597cad51eb8673bf49\": no space left on device", err:(*fmt.wrapError)(0xc0002ea460)}

...makes me suspect that we can't use tmpfs-/tmp on buildah: too diskhoggy. I've run into the same problem with 1minutetip. Only solution I can think of is to hardcode TMPDIR=/var/tmp. Any other ideas?

Didn't we already run on tmpfs (on fedora) before my changes? AFAICT you tested the tmpfs thing with #5470?
If anything my tmpfs change should made the tmpfs bigger so I do not see why it would run of of space suddenly.

[edsantiago]

Didn't we already run on tmpfs (on fedora) before my changes?

Conformance tests run on Debian.

Looking more closely, I see:

• TestConformance/copy_with_--chown -- fails only on vfs, with ENOSPC
• TestConformance/ci-pipeline-modified -- fails on both vfs and overlay, with a real-looking error

As it turns out, there's some really weird clunky code that downloads docker-* packages in the VMs, but only installs them in buildah CI, so my get-versions script can't compare. This is the difference I found, manually, between the VM builds:

-5:26.0.0-1~debian.12~bookworm
+5:26.1.2-1~debian.12~bookworm    (basically, 26.0 to 26.1)

Conformance tests, IIRC, are very docker-dependent and break every time docker changes.

WHEW. After all that, I think the TL;DR is

1. use TMPDIR=/var/tmp on debian
2. fix conformance tests to deal with new docker

[Luap99]

Ah that is a mess, would be great to get the distro name into the task names. Because if there is none I am going to assume it uses fedora stable.

setting TMPDIR=/var/tmp sounds like a reasonable work around, actual test fixes for docker changes would likely be a @nalind task.

[edsantiago]

Agreed, actual fix needs @nalind attention. Here's (what I believe is) the relevant error output, to save on click-and-hunt time:

[+0571s]     conformance_test.go:484: 
                 	Error Trace:	/var/tmp/go/src/github.com/containers/buildah/tests/conformance/conformance_test.go:484
                 	            				/var/tmp/go/src/github.com/containers/buildah/tests/conformance/conformance_test.go:343
                 	            				/var/tmp/go/src/github.com/containers/buildah/tests/conformance/conformance_test.go:161
                 	Error:      	Image configurations differ as committed in Docker format
                 	Test:       	TestConformance/ci-pipeline-modified
                 	Messages:   	Fields which only exist in buildah version: parent
                 	            	Fields present in both versions have different values:
                 	            	Field                              Docker                                                       buildah
                 	            	config:WorkingDir                  /go/src/github.com/openshift/ocp-release-operator-sdk        /go/src/github.com/openshift/ocp-release-operator-sdk/
                 	            	container_config:WorkingDir        /go/src/github.com/openshift/ocp-release-operator-sdk        /go/src/github.com/openshift/ocp-release-operator-sdk/
             conformance_test.go:488: 
                 	Error Trace:	/var/tmp/go/src/github.com/containers/buildah/tests/conformance/conformance_test.go:488
                 	            				/var/tmp/go/src/github.com/containers/buildah/tests/conformance/conformance_test.go:343
                 	            				/var/tmp/go/src/github.com/containers/buildah/tests/conformance/conformance_test.go:161
                 	Error:      	Image configurations differ when converted to OCI format
                 	Test:       	TestConformance/ci-pipeline-modified
                 	Messages:   	Fields which only exist in buildah version: config:Labels
                 	            	Fields present in both versions have different values:
                 	            	Field                    Docker                                                       buildah
                 	            	config:WorkingDir        /go/src/github.com/openshift/ocp-release-operator-sdk        /go/src/github.com/openshift/ocp-release-operator-sdk/
[+0572s]     conformance_test.go:377: Dockerfile contents:
                 FROM busybox
                 WORKDIR /go/src/github.com/openshift/ocp-release-operator-sdk/
                 ENV GOPATH=/go
                 RUN env | grep -E -v '^(HOSTNAME|OLDPWD)=' | LANG=C sort | tee /env-contents.txt

[cevich]

I agree with Paul's suggestion it would be nice to have "Debian" in the task name. I can toss a quick PR to do this.

As it turns out, there's some really weird clunky code that downloads docker-* packages in the VMs, but only installs them in buildah CI

For some more context here, in case it helps:

IIRC the conformance tests use to run on Fedora and Ubuntu, until it became impossible/hard to install docker on Fedora. We also use to install the "latest" Docker at runtime, but this wrecked havoc with testing on release branches and flake all the time. CI VM build was updated to cache the packages for runtime install well before the switch to Debian. Much duct-tape has been piled on since then no doubt. Point is, these machinations are all very very old. I would not at all be opposed to improvements, so long as any changes are likely to survive long-term release-branch testing.

[cevich]

Also need to update:

    FEDORA_NAME: "fedora-40"
    PRIOR_FEDORA_NAME: "fedora-39"
    DEBIAN_NAME: "debian-13"