Gating tests are failing with ENOSPC. Try explicitly setting
TMPDIR to /var/tmp which usually has more free space.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Go 1.15 deprecates checking CN; this broke gating tests:
Get "https://localhost:5000/v2/": x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0
Easy two-line solution in the 'openssl' invocation. Huge
thanks to Nalin for tracking down and fixing while I was
still getting started:
https://github.com/containers/buildah/pull/2595
Signed-off-by: Ed Santiago <santiago@redhat.com>
Newer buildah tests now depend on encryption functionality
only present in later (2.7? 2.8?) versions of docker.io/registry.
So, undo our earlier change in which we forced registry:2.6
to use its htpasswd. Instead, tests now require httpd-tools
package and we use native host htpasswd. We revert back to
using registry:2 (no dot), which is a moving target, so be
prepared for future breakage.
Signed-off-by: Ed Santiago <santiago@redhat.com>
The docker.io/registry:2 image broke suddenly and with no warning:
https://github.com/docker/distribution-library-image/issues/106
Symptom: running 'htpasswd' from that container no longer works,
even though it's been documented for years (at docker.com) and
as of this writing still remains documented.
One solution is to run htpasswd locally (requires installing the
httpd-tools package) or using any crypt library to hash. Not
hard, but tedious, and it doesn't address the issue of the
docker registry:2 image being a moving target.
I choose to force the use of the :2.6 tag, in hopes that that
image will remain unmodified. Refactored to use FQIN instead
of shortname, and to define it in only one place.
Signed-off-by: Ed Santiago <santiago@redhat.com>
The Gating spec[1] used to recommend having one type of
YAML stanza for master, one for released branches. We
just discovered today that this breaks when master
forks into a release branch: the string 'stable'
needs to be manually changed to 'testing', and
nobody is going to remember to do that, and I can't
think of a (non-tedious) way to add automated checks.
As of 2019-08 (09d7d4f), though, the Gating spec suggests
having *both* stanzas together in the same gating.yaml
file. @pingou himself concurs[2]. Although this is
horrible duplication -- two hundred characters, repeated
with only six of those different -- it seems cleaner
than the maintenance burden of having to update
release branches.
[1] https://docs.fedoraproject.org/en-US/ci/gating/
[2] https://src.fedoraproject.org/rpms/podman/pull-request/33
Oh, also, add a new 'subject_type' line apparently "required"
even though things seem to have been working fine without it.
(Source: same commit, 09d7d4f, on gating.adoc).
Signed-off-by: Ed Santiago <santiago@redhat.com>
