F26->F27 w/ dnf system-upgrade: Failed to synchronize cache for repo 'updates'

[Richard Shaw]

I usually have trouble upgrading because I keep a local repository of
packages and because they are shared via NFS dnf treats them as local files
and doesn't download them. I've worked around that (F25->F26) by disabling
it temporarily and distro-syncing after update.

I've also disabled my squid package cache proxy just in case but still the
problem remains. I haven't seen anything on the list and most of the google
search results are not for F26 to F27 upgrades so does anyone have a clue
what's going on?

Thanks,
Richard

[Sam Varshavchik]

Richard Shaw writes:

>  « HTML content follows »
>
>  I usually have trouble upgrading because I keep a local repository of  
>  packages and because they are shared via NFS dnf treats them as local files  
>  and doesn't download them. I've worked around that (F25->F26) by disabling it 
>
>  temporarily and distro-syncing after update.
>
>
>  I've also disabled my squid package cache proxy just in case but still the  
>  problem remains. I haven't seen anything on the list and most of the google  
>  search results are not for F26 to F27 upgrades so does anyone have a clue  
>  what's going on? 
Bug 1513111

[Richard Shaw]

On Mon, Nov 20, 2017 at 6:04 AM, Sam Varshavchik <mrsam(a)courier-mta.com&gt;
wrote:

>  Bug 1513111 

Thanks for the pointer...  I'm not in a hurry to upgrade so I may just wait
for a "fix" instead of messing with the workaround.

Thanks,
Richard

[Sam Varshavchik]

Richard Shaw writes:

>  On Mon, Nov 20, 2017 at 6:04 AM, Sam Varshavchik
> <<URL:mailto:mrsam@courier- 
>  mta.com&gt;mrsam(a)courier-mta.com&gt; wrote:
>
>
>     Bug 1513111
>
>
>
>  Thanks for the pointer...  I'm not in a hurry to upgrade so I may just wait  
>  for a "fix" instead of messing with the workaround. 
It is relatively simple to temporarily edit the .conf files in  
/etc/yum.repos.d for whatever custom repository you have that have a short  
expiration period, and set them to a month, or something. Then, delete  
everything that was downloaded the first time, and do a 'dnf system-upgrade  
download' again.

This should put a sufficiently long metadata expiration on the downloaded  
packages so that dnf doesn't try to refresh them during a 'dnf system- 
upgrade reboot'. After the upgrade restore the original expiration  
settings, and do a 'dnf clean all'.

[Richard Shaw]

On Mon, Nov 20, 2017 at 1:18 PM, Sam Varshavchik <mrsam(a)courier-mta.com&gt;
wrote:

>  It is relatively simple to temporarily edit the .conf files in
>  /etc/yum.repos.d for whatever custom repository you have that have a short
>  expiration period, and set them to a month, or something. Then, delete
>  everything that was downloaded the first time, and do a 'dnf system-upgrade
>  download' again.
>
>  This should put a sufficiently long metadata expiration on the downloaded
>  packages so that dnf doesn't try to refresh them during a 'dnf
>  system-upgrade reboot'. After the upgrade restore the original expiration
>  settings, and do a 'dnf clean all'. 

It's a machine I don't use very often so no hurry and at this point it's
more on principal :) I admittedly only skimmed both the bugzilla and the
github issue but I didn't see any response from the dnf team. This seems
serious enough to warrant attention.

Thanks,
Richard