This blocks dnf from accessing packages. Please remediate. Fedora 35 - x86_64 3.8 kB/s | 3.3 kB 00:00 Errors during downloading metadata for repository 'fedora': - Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 (IP: 2600:2701:4000:5211:dead:beef:fe:fed3) Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 (IP: 2600:2701:4000:5211:dead:beef:fe:fed3)
No outages listed at: https://www.fedorastatus.org/
Down for me as well, same issue.
Same here
Same problem here, unable to update or install anything. All Fedora repositories appear to be down. What did Red Hat get hit with this time?
Confirmed also an issue with CentOS 9 Stream.
Also impacting ability to build containers depending on epel I know its friday but high impact
Still happening here at 02:42 2022-02-05 UTC
Also experiencing the same issue.
I can confirm that I am having the same issue with 2600:2701:4000:5211:dead:beef:fe:fed3. I can ping the server just fine.
Services are starting to recover. Please try again in a few minutes.
still happening for me
Error: Failed to download metadata for repo 'epel-modular': Cannot prepare internal mirrorlist: Status code: 503 for https://mirrors.fedoraproject.org/metalink?repo=epel-modular-8&arch=x86_64&infra=stock&content=almalinux (IP: 209.132.190.2) [jcup@jcoupal-kp0 sites-available]$
Our docs sync script went pear shaped and our proxy servers ran out of disk space. ;(
Things should be coming back now and I will update the ticket when everything is ok.
Resolved for me now. Thanks everybody.
It's back up.
Everything should be back to normal now.
Sorry for the outage.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
It looks like it was not resolved. See our error here: https://artifacts.dev.testing-farm.io/b72557ef-410b-4754-9085-51d2e9b747a1/work-fedoraMp6tIr/log.txt
Almost at the end. around 13:41
13:41:22 out: -> Pulling image quay.io/fedora/s2i-core:35 before building image from Dockerfile.fedora. 13:41:22 out: Trying to pull repository quay.io/fedora/s2i-core ... 13:41:22 out: 35: Pulling from quay.io/fedora/s2i-core 13:41:22 out: 9c6cc3463716: Pulling fs layer 13:41:22 out: 4a0c1265bcb2: Pulling fs layer 13:41:23 out: 4a0c1265bcb2: Verifying Checksum 13:41:23 out: 4a0c1265bcb2: Download complete 13:41:23 out: 9c6cc3463716: Download complete 13:41:26 out: 9c6cc3463716: Pull complete 13:41:27 out: 4a0c1265bcb2: Pull complete 13:41:27 out: Digest: sha256:f1051ca38f7f00ba3e042c5ad163d3ee52194caf697704ef56991d4f73798561 13:41:27 out: Status: Downloaded newer image for quay.io/fedora/s2i-core:35 13:41:27 out: -> building using docker build --label io.openshift.builder-version="d8fb76d" -f "$dockerfile" "${DOCKER_BUILD_CONTEXT}" 13:41:27 out: Sending build context to Docker daemon 51.2 kB 13:41:27 out: Step 1/15 : FROM quay.io/fedora/s2i-core:35 13:41:27 out: ---> 5e55126c7d1e 13:41:27 out: Step 2/15 : ENV NAME redis VERSION 6 13:41:29 out: ---> Running in 11457c596c28 13:41:29 out: ---> 796e0af3fad9 13:41:29 out: Removing intermediate container 11457c596c28 13:41:29 out: Step 3/15 : ENV REDIS_VERSION $VERSION HOME /var/lib/redis 13:41:29 out: ---> Running in 9029e3941fbf 13:41:29 out: ---> 717e5a73add5 13:41:29 out: Removing intermediate container 9029e3941fbf 13:41:29 out: Step 4/15 : ENV SUMMARY "Redis in-memory data structure store, used as database, cache and message broker" DESCRIPTION "Redis $REDIS_VERSION available as container, is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log." 13:41:29 out: ---> Running in 664826e75fd9 13:41:29 out: ---> 406a9e915514 13:41:29 out: Removing intermediate container 664826e75fd9 13:41:29 out: Step 5/15 : LABEL summary "$SUMMARY" description "$DESCRIPTION" io.k8s.description "$SUMMARY" io.k8s.display-name "Redis 6" io.openshift.expose-services "6379:redis" io.openshift.tags "database,redis,redis6" com.redhat.component "$NAME" name "fedora/$NAME-$VERSION" version "$VERSION" usage "docker run -d --name redis_database -p 6379:6379 quay.io/fedora/$NAME-$VERSION" maintainer "SoftwareCollections.org <sclorg@redhat.com>" 13:41:29 out: ---> Running in a33a58e0e444 13:41:29 out: ---> 6ffe88123d69 13:41:29 out: Removing intermediate container a33a58e0e444 13:41:29 out: Step 6/15 : EXPOSE 6379 13:41:29 out: ---> Running in 4834e4b6d6c9 13:41:29 out: ---> f4369d031074 13:41:29 out: Removing intermediate container 4834e4b6d6c9 13:41:29 out: Step 7/15 : RUN getent group redis &> /dev/null || groupadd -r redis &> /dev/null && usermod -l redis -aG redis -c 'Redis Server' default &> /dev/null && dnf install -y yum-utils gettext policycoreutils && INSTALL_PKGS="redis" && dnf install -y --setopt=tsflags=nodocs --nogpgcheck $INSTALL_PKGS && rpm -V $INSTALL_PKGS && dnf clean all && mkdir -p /var/lib/redis/data && chown -R redis.0 /var/lib/redis && [[ "$(id redis)" == "uid=1001(redis)"* ]] 13:41:29 out: ---> Running in b93c63fb2ab9 13:41:29 out: 13:41:30 out: Fedora 35 - x86_64 0.0 B/s | 0 B 00:00 13:41:30 out: Errors during downloading metadata for repository 'fedora': 13:41:30 out: - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start] 13:41:30 out: Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start] 13:41:30 out: The command '/bin/sh -c getent group redis &> /dev/null || groupadd -r redis &> /dev/null && usermod -l redis -aG redis -c 'Redis Server' default &> /dev/null && dnf install -y yum-utils gettext policycoreutils && INSTALL_PKGS="redis" && dnf install -y --setopt=tsflags=nodocs --nogpgcheck $INSTALL_PKGS && rpm -V $INSTALL_PKGS && dnf clean all && mkdir -p /var/lib/redis/data && chown -R redis.0 /var/lib/redis && [[ "$(id redis)" == "uid=1001(redis)"* ]]' returned a non-zero code: 1 13:41:30 out: make[1]: *** [6] Error 1 13:41:30 out: make[1]: Leaving directory `/tmp/sclorg/redis-container' 13:41:30 out: make: *** [build-serial] Error 2
that is a different problem from the one that caused this. If the problem had not been resolved then nothing would have worked since Feb 4.
The issue you are showing looks like a DNS problem or a glibc problem with your test hardware:
Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start]
failure to resolve a hostname says that the system couldn't do a DNS lookup, getaddrinfo thread failed to start sounds like some sort of local resource problem.
@phracek This is a known issues buliding F35 on RHEL7 (and similar), use other base system (centos stream 8?)