Skip to content

Conformance test failure on release-1.16 - release1.21 #3632

@cevich

Description

@cevich

Description

The old VM images used by these branches contained a bug in their build script: Download the docker packages into a cache directory...and then delete the parent directory to "save disk space" 😖 This problem was fixed (going forward) around the release-1.22 timeframe.

The other issue I discovered more recently, is much easier to fix. At test runtime we can't use apt-get to install from package files. It has unavoidable behavior to always download a newer version if available. So it will happily download newer docker versions that are incompatible with the (old) tests 😖 This problem is easily fixed by switching to direct dpkg install of the cached files.

Steps to reproduce the issue:

  1. Open a PR on any of the affected branches
  2. Let the conformance test task run

Describe the results you received:

A large number of conformance tests fail for many different reasons.

Describe the results you expected:

The conformance tests should pass

Output of rpm -q buildah or apt list buildah:

varies by branch

Output of buildah version:

varies by branch

Output of podman version if reporting a podman build issue:

varies by branch

Output of cat /etc/*release:

varies by branch

Output of uname -a:

varies by branch

Output of cat /etc/containers/storage.conf:

varies by branch

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions