Is the Fedora 35 repo having troubles?

[George R Goffe]

Hi,

I've been getting these messages for a couple of days now. Is the repo having troubles?

Best regards,

George...

/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best --setopt=zchunk=0 --exclude=*kernel* --exclude=environment-modules* --exclude=Lmod upgrade
Fedora rawhide openh264 (From Cisco) - x86_64                                  3.2 kB/s | 989  B     00:00    
Fedora - Modular Rawhide - Developmental packages for the next Fedora release  0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'rawhide-modular':
  - Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=rawhide-modular&arch=x86... []
Error: Failed to download metadata for repo 'rawhide-modular': Cannot prepare internal mirrorlist: Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=rawhide-modular&arch=x86... []

[Richard Ryniker]

Also happens with F34:

Errors during downloading metadata for repository 'fedora-modular':
  - Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-34&arch=x... []
Error: Failed to download metadata for repo 'fedora-modular': Cannot prepare internal mirrorlist: Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-34&arch=x... []

Disable the three "modular" repositories and dnf will succeed.  For example:

dnf --disablerepo=fedora-modular --disablerepo=updates-modular --disablerepo=updates-testing-modular  upgrade

[u9000 (Nine)]

On Wed, 2021-03-24 at 16:00 -0400, Richard Ryniker wrote:
> Also happens with F34

I had the same issue today on F33.

[Adam Williamson]

On Wed, 2021-03-24 at 18:06 -0400, u9000 (Nine) wrote:
> On Wed, 2021-03-24 at 16:00 -0400, Richard Ryniker wrote:
> > Also happens with F34
>
> I had the same issue today on F33.

There was a bad F33 update in updates-testing briefly. It's not
actually the same bug, but similar symptoms. The bad build was systemd-
246.12-1.fc33 , systemd-246.13-1.fc33 should be better. Please update
to 246.13-1 and report in
https://bodhi.fedoraproject.org/updates/FEDORA-2021-1c1a870ceb if you
still have problems with that build.

[u9000 (Nine)]

On Wed, 2021-03-24 at 15:14 -0700, Adam Williamson wrote:
> On Wed, 2021-03-24 at 18:06 -0400, u9000 (Nine) wrote:
> > On Wed, 2021-03-24 at 16:00 -0400, Richard Ryniker wrote:
> > > Also happens with F34
> >
> > I had the same issue today on F33.
>
> There was a bad F33 update in updates-testing briefly. It's not
> actually the same bug, but similar symptoms.

I haven't enabled updates-testing on that machine; today being the first
time it happened might be a coincidence.

[Adam Williamson]

On Wed, 2021-03-24 at 19:01 +0000, George R Goffe via test wrote:
> Hi,
>
> I've been getting these messages for a couple of days now. Is the repo having troubles?
>
> Best regards,
>
> George...
>
> /usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best --setopt=zchunk=0 --exclude=*kernel* --exclude=environment-modules* --exclude=Lmod upgrade
> Fedora rawhide openh264 (From Cisco) - x86_64                                  3.2 kB/s | 989  B     00:00    
> Fedora - Modular Rawhide - Developmental packages for the next Fedora release  0.0  B/s |   0  B     00:00    
> Errors during downloading metadata for repository 'rawhide-modular':
>   - Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=rawhide-modular&arch=x86... []
> Error: Failed to download metadata for repo 'rawhide-modular': Cannot prepare internal mirrorlist: Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=rawhide-modular&arch=x86... []

You may have a bad systemd build with name resolution issues. Try
creating a file /etc/systemd/resolved.conf.d/nocache.conf with this
content:

[Resolve]
Cache=no

and restarting systemd-resolved.service, it may help. (Once the bugs
are fixed you'll want to remove it, so you get the benefits of
caching).

[Richard Ryniker]

Adam Williamson wrote on Wed, 24 Mar 2021 13:01:58 -0700:
> You may have a bad systemd build with name resolution issues. Try
> creating a file /etc/systemd/resolved.conf.d/nocache.conf with this
> content:
>
> [Resolve]
> Cache=no
>
> and restarting systemd-resolved.service, it may help.

This worked for my F34 system, but the change had to be made in the file:
   /etc/systemd/resolved.conf

Thank you, Adam.

[Adam Williamson]

On Wed, 2021-03-24 at 16:23 -0400, Richard Ryniker wrote:
> Adam Williamson wrote on Wed, 24 Mar 2021 13:01:58 -0700:
> > You may have a bad systemd build with name resolution issues. Try
> > creating a file /etc/systemd/resolved.conf.d/nocache.conf with this
> > content:
> >
> > [Resolve]
> > Cache=no
> >
> > and restarting systemd-resolved.service, it may help.
>
> This worked for my F34 system, but the change had to be made in the file:
>    /etc/systemd/resolved.conf

Doing what I said should also work, it is a config snippet for the same
file. You would have to create the directory if it didn't exist
already, sorry, didn't mention that part. Editing the file directly is
fine too, though, just very slightly less friendly for future
maintenance :D Shouldn't matter in this case.