Comment # 1 on bug 1206780 from Martin Wilck

On GitHub, I am running the workflow in question every week. It can be seen
that the workflow first failed a week ago (Dec 26th). The run on Dec 19th was
successful.

https://github.com/mwilck/build-multipath/actions/workflows/rolling.yaml

The failing Dockerfile looks like this:

> FROM registry.opensuse.org/opensuse/tumbleweed:latest
> LABEL org.opencontainers.image.title="build-multipath-tools"
> LABEL org.opencontainers.image.description="container for building multipath-tools on opensuse/tumbleweed"
> RUN  zypper --quiet --non-interactive --gpg-auto-import-keys refresh && \
>    zypper --quiet --non-interactive --gpg-auto-import-keys --no-refresh install --no-recommends --force-resolution --allow-downgrade \
>    make gcc clang pkg-config gzip gawk \
>     device-mapper-devel libaio-devel systemd-devel libjson-c-devel liburcu-devel readline-devel libedit-devel libmount-devel libcmocka-devel  
> VOLUME /build
> RUN  zypper --quiet --non-interactive --gpg-auto-import-keys clean --all
> WORKDIR /build

It's the "zypper refresh" that fails; the "zypper install" step is never
reached.