Fedora 26 to 27: Update problem.

[Dario Lesca]

I have update my notebook since Fedora 18 to Fedora 26 always without
problem.

Today I have try to update Fedora 26 to 27, but after download packages
and run "dnf system-upgrade reboot", when the system restart the update
fail after a while after this boot message:

Starting System Upgrade using DNF...
    [  OK  ] Listening on D-Bus System Message Bus Socket.
             Starting Update the operating system whilst offline...
    [  OK  ] Started Update the operating system whilst offline.
    [  205.755691] dnf[967]: Errore: Sincronizzazione cache non riuscita per il repo 'updates'
    [FAILED] Failed to start System Upgrade using DNF.
    See 'systemctl status dnf-system-upgrade.service' for details.

I restart the notebook in Fedora 26 and into log I fount this error:

2017-11-16T15:37:58Z INFO --- logging initialized ---
    2017-11-16T15:37:58Z DDEBUG timer: config: 4 ms
    2017-11-16T15:37:58Z DEBUG Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync, system-upgrade
    2017-11-16T15:37:58Z DEBUG DNF version: 2.7.5
    2017-11-16T15:37:58Z DDEBUG Command: dnf system-upgrade reboot 
    2017-11-16T15:37:58Z DDEBUG Installroot: /
    2017-11-16T15:37:58Z DDEBUG Releasever: 26
    2017-11-16T15:37:58Z DEBUG cachedir: /var/cache/dnf
    2017-11-16T15:37:58Z DDEBUG Base command: system-upgrade
    2017-11-16T15:37:58Z DDEBUG Extra commands: ['system-upgrade', 'reboot']
    2017-11-16T15:37:58Z DDEBUG Cleaning up.
    2017-11-16T15:39:15Z INFO --- logging initialized ---
    2017-11-16T15:39:15Z DDEBUG timer: config: 1240 ms
    2017-11-16T15:39:16Z DEBUG Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repograph, repomanage, reposync, system-upgrade
    2017-11-16T15:39:16Z DEBUG DNF version: 2.7.5
    2017-11-16T15:39:16Z DDEBUG Command: dnf --releasever=27 system-upgrade upgrade 
    2017-11-16T15:39:16Z DDEBUG Installroot: /
    2017-11-16T15:39:16Z DDEBUG Releasever: 27
    2017-11-16T15:39:16Z DEBUG cachedir: /var/cache/dnf
    2017-11-16T15:39:16Z DDEBUG Base command: system-upgrade
    2017-11-16T15:39:16Z DDEBUG Extra commands: ['--releasever=27', 'system-upgrade', 'upgrade']
    2017-11-16T15:39:31Z DEBUG repository: uso della cache per adobe-linux-x86_64
    2017-11-16T15:39:31Z DEBUG not found deltainfo for: Adobe Systems Incorporated
    2017-11-16T15:39:31Z DEBUG not found updateinfo for: Adobe Systems Incorporated
    2017-11-16T15:39:31Z DEBUG adobe-linux-x86_64: usando metadati di gio 26 ott 2017 06:39:15 CEST.
    2017-11-16T15:39:31Z DEBUG Impossibile scaricare '    https://mirrors.fedoraproject.org/metalink?repo=updates-released-f27&arc...'    : Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for     https://mirrors.fedoraproject.org/metalink?repo=updates-released-f27&arc...     [Could not resolve host: mirrors.fedoraproject.org].
    2017-11-16T15:39:31Z DDEBUG Cleaning up.
    2017-11-16T15:39:32Z SUBDEBUG 
    Traceback (most recent call last):
      File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 229, in _perform
        return super(_Handle, self).perform(result)
      File "/usr/lib64/python3.6/site-packages/librepo/__init__.py", line 1522, in perform
        _librepo.Handle.perform(self, result)
    librepo.LibrepoException: (8, "Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for     https://mirrors.fedoraproject.org/metalink?repo=updates-released-f27&arc...     [Could not resolve host: mirrors.fedoraproject.org]", 'An Curl handle error')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
      File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 909, in load
        if self._try_revive():
      File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 857, in _try_revive
        return self._try_revive_by_metalink()
      File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 810, in _try_revive_by_metalink
        handle._perform()
      File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 233, in _perform
        raise _DetailedLibrepoError(exc, source)
    dnf.repo._DetailedLibrepoError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
      File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main
        return _main(base, args, cli_class, option_parser_class)
      File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main
        return cli_run(cli, base)
      File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 115, in cli_run
        cli.run()
      File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 1010, in run
        self._process_demands()
      File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 763, in _process_demands
        load_available_repos=self.demands.available_repos)
      File "/usr/lib/python3.6/site-packages/dnf/base.py", line 353, in fill_sack
        self._add_repo_to_sack(r)
      File "/usr/lib/python3.6/site-packages/dnf/base.py", line 118, in _add_repo_to_sack
        repo.load()
      File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 931, in load
        raise dnf.exceptions.RepoError(msg)
    dnf.exceptions.RepoError: Sincronizzazione cache non riuscita per il repo 'updates'
    2017-11-16T15:39:32Z CRITICAL Errore: Sincronizzazione cache non riuscita per il repo 'updates'

Why the offline update try to connect to "updates" online repo?

What's happen ? someone can help me?

Many thanks

[Sam Varshavchik]

Dario Lesca writes:
> ott 2017 06:39:15 CEST.
>     2017-11-16T15:39:31Z DEBUG Impossibile scaricare '     
> https://mirrors.fedoraproject.org/metalink?repo=updates-released- 
> f27&arch=x86_64'    : Cannot prepare internal mirrorlist: Curl error (6):  
> Couldn't resolve host name for      
> https://mirrors.fedoraproject.org/metalink?repo=updates-released-

Looks like this is going to be a common, very, very popular bug. Pretty sure  
this is bug 1513111.

"system-upgrade reboot" apparently now requires a fully working network  
stack, because it tries to resynchronize with all the repos, despite that  
this is supposed to be done, and it was done, by "system-upgrade download".

I think this is a bug, and it needs to be fixed.

[Terry Polzin]

So wireless won't cut it eh?

On Thu, Nov 16, 2017 at 1:39 PM, Sam Varshavchik 
wrote:
> Dario Lesca writes:
>
> ott 2017 06:39:15 CEST.
> > 2017-11-16T15:39:31Z DEBUG Impossibile scaricare '
> >
> > https://mirrors.fedoraproject.org/metalink?repo=updates-rele
> > ased-f27&arch=x86_64'    : Cannot prepare internal mirrorlist: Curl
> > error (6): Couldn't resolve host name for     https://mirrors.
> > fedoraproject.org/metalink?repo=updates-released-
>
> Looks like this is going to be a common, very, very popular bug. Pretty
> sure this is bug 1513111.
>
> "system-upgrade reboot" apparently now requires a fully working network
> stack, because it tries to resynchronize with all the repos, despite that
> this is supposed to be done, and it was done, by "system-upgrade download".
>
> I think this is a bug, and it needs to be fixed.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[murph]

It worked for me on wireless last night.  I saw no errors, not sure if
the wireless was started at that stage of the upgrade.

On Thu, Nov 16, 2017 at 1:46 PM, Terry Polzin  wrote:
> So wireless won't cut it eh?
>
> On Thu, Nov 16, 2017 at 1:39 PM, Sam Varshavchik 
> wrote:
> > Dario Lesca writes:
> > > ott 2017 06:39:15 CEST.
> > >     2017-11-16T15:39:31Z DEBUG Impossibile scaricare '
> > > https://mirrors.fedoraproject.org/metalink?repo=updates-released-f27&arc...'
> > > : Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host
> > > name for
> > > https://mirrors.fedoraproject.org/metalink?repo=updates-released-
> >
> > Looks like this is going to be a common, very, very popular bug. Pretty
> > sure this is bug 1513111.
> >
> > "system-upgrade reboot" apparently now requires a fully working network
> > stack, because it tries to resynchronize with all the repos, despite that
> > this is supposed to be done, and it was done, by "system-upgrade download".
> >
> > I think this is a bug, and it needs to be fixed.
> >
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Ulf Volmer]

On 16.11.2017 19:39, Sam Varshavchik wrote:
> "system-upgrade reboot" apparently now requires a fully working network
> stack, because it tries to resynchronize with all the repos, despite
> that this is supposed to be done, and it was done, by "system-upgrade
> download".

i doubt that is a general issue. i have just upgrade a virtual machine
from fc26 to fc27 and before the reboot i switched the NIC to the 'host
only' network. no issues.

best regards
Ulf

[Dario Lesca]

Il giorno gio, 16/11/2017 alle 13.39 -0500, Sam Varshavchik ha scritto:
> Looks like this is going to be a common, very, very popular bug.
> Pretty sure  
> this is bug 1513111.
>
> "system-upgrade reboot" apparently now requires a fully working
> network  stack, because it tries to resynchronize with all the repos,
> despite that this is supposed to be done, and it was done, by
> "system-upgrade download".
>
> I think this is a bug, and it needs to be fixed.

Thanks Sam, what Bug you talking about?, can you please post me the
link?

Thanks

[John Pilkington]

On 16/11/17 22:33, Dario Lesca wrote:
> Il giorno gio, 16/11/2017 alle 13.39 -0500, Sam Varshavchik ha scritto:
> > Looks like this is going to be a common, very, very popular bug.
> > Pretty sure
> > this is bug 1513111.
> >
> > "system-upgrade reboot" apparently now requires a fully working
> > network  stack, because it tries to resynchronize with all the repos,
> > despite that this is supposed to be done, and it was done, by
> > "system-upgrade download".
> >
> > I think this is a bug, and it needs to be fixed.
>
> Thanks Sam, what Bug you talking about?, can you please post me the
> link?
>
> Thanks

https://bugzilla.redhat.com/show_bug.cgi?id=1513111

[Sam Varshavchik]

John Pilkington writes:
> On 16/11/17 22:33, Dario Lesca wrote:
> > Il giorno gio, 16/11/2017 alle 13.39 -0500, Sam Varshavchik ha scritto:
> > > Looks like this is going to be a common, very, very popular bug.
> > > Pretty sure
> > > this is bug 1513111.
> > >
> > > "system-upgrade reboot" apparently now requires a fully working
> > > network  stack, because it tries to resynchronize with all the repos,
> > > despite that this is supposed to be done, and it was done, by
> > > "system-upgrade download".
> > >
> > > I think this is a bug, and it needs to be fixed.
> >
> > Thanks Sam, what Bug you talking about?, can you please post me the
> > link?
> >
> > Thanks
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1513111

The plot thickens. By pointing changing the URL to the server own's repo to  
a file:/// URL its upgraded succeeding. Now, it's up on F27, and serving the  
local repository.

But now, an upgrade of another server failed because, once again, 'system- 
upgrade reboot' decided to resync during its reboot, and it failed to reach  
the local server. The local repo server itself is up, 'system-upgrade  
download' doesn't squeak, but the server being upgraded apparently does not  
have networking during 'system-upgrade reboot'.

This explains why someone else managed to upgrade a wireless laptop without  
networking. Something is going horribly sideways here. 'system-upgrade  
reboot' is whining only about my local repo:

Nov 16 18:20:29 monster.email-scan.com dnf[1026]: Failed to synchronize  
cache for repo 'my', disabling.

Which is immediately followed by about dozen packages from this repo that  
it's "Unable to match":

Nov 16 18:20:36 monster.email-scan.com dnf[1026]: Unable to match package:  
cone-0.96.1-4.fc27.x86_64 my

And followed by a dozen more. But no mention is made of thousands of  
packages from fedora, and fedora-updates! So why is this dumb thing refuses  
to run only because it can't reach my repository, but it doesn't feel the  
need to verify that the stock fedora repositories are reachable over the  
network?

Of course, I can always copy my local repo to the same server, and stick a  
file:/// URL on it. But why do I need to do something so stupid? No reason  
why this shouldn't work, as is.

The only thing I could possibly think of is that, for my local repository, I  
do not use a signing PGP key. Is that the B.S.? I'll find out later tonight.

[Gordon Messmer]

On 11/16/2017 02:47 PM, John Pilkington wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1513111

The bug appears to be that dnf processes the last metadata update time 
while in the offline system-upgrade mode.  I was able to work around the 
problem by re-running "dnf system-upgrade download --releasever 27" 
immediately before "dnf system-upgrade reboot"

[Gordon Messmer]

On 11/16/2017 03:34 PM, Sam Varshavchik wrote:
> This explains why someone else managed to upgrade a wireless laptop 
> without networking. Something is going horribly sideways here. 
> 'system-upgrade reboot' is whining only about my local repo:

Does your repository configuration specify a very short 
"metadata_expire" setting?

[Sam Varshavchik]

Gordon Messmer writes:
> On 11/16/2017 03:34 PM, Sam Varshavchik wrote:
> > This explains why someone else managed to upgrade a wireless laptop without  
> > networking. Something is going horribly sideways here. 'system-upgrade  
> > reboot' is whining only about my local repo:
>
> Does your repository configuration specify a very short "metadata_expire"  
> setting?

Yes, it did. This seems to trigger "system-upgrade reboot" to try to refresh  
it during the reboot.

(solved) Fedora 26 to 27: Update problem.

[Dario Lesca]

Il giorno gio, 16/11/2017 alle 18.09 +0100, Dario Lesca ha scritto:
> I have update my notebook since Fedora 18 to Fedora 26 always without
> problem.
>
> Today I have try to update Fedora 26 to 27, but after download
> packages
> and run "dnf system-upgrade reboot", when the system restart the
> update
> fail after a while after this boot message
> ....
> Why the offline update try to connect to "updates" online repo?
>
> What's happen ? someone can help me?

I have successful updated downgrade dnf to previous version.

$ sudo dnf downgrade dnf -y

Before downgrade:
[lesca@dodo ~]$ rpm -q dnf
dnf-2.7.5-1.fc26.noarch

After downgrade:
[lesca@dodo ~]$ rpm -q dnf
dnf-2.5.1-1.fc26.noarch

Then I have move all rpm downloaded from new (bugged?) dnf into some
repo subfolder, into old place user by old (worked) dnf with:

$ sudo  mv /var/lib/dnf/system-upgrade/*/packages/*rpm /var/lib/dnf/system-upgrade/.

Then I have run 
$ sudo dnf system-upgrade download --releasever=27 --refresh

and

$ sudo dnf system-upgrade reboot

And finally the update is done.

Thanks

(solved) Fedora 26 to 27: Update problem.

[Dario Lesca]

Il giorno sab, 18/11/2017 alle 10.47 +0100, Dario Lesca ha scritto:
> $ sudo dnf downgrade dnf -y

Today

Another upgrade from f26 to f27 failed after reboot

Another dnf downgrade done

Another successful update using old dnf version.