Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513749 - Fail to upgrade Fedora, and no clue to fix it
Summary: Fail to upgrade Fedora, and no clue to fix it
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Mracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-15 22:04 UTC by Charlie Mordant
Modified: 2017-11-22 13:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-22 13:30:45 UTC


Attachments (Terms of Use)

Description Charlie Mordant 2017-11-15 22:04:49 UTC
Description of problem:

I followed the dnf upgrade procedure, but have an error on the last step (dnf system-upgrade reboot.
Erreur : le système n’est pas prêt pour la mise à niveau
dnf.cli.CliError: --releasever doit être ultérieure à la version courante du système.
2017-11-15T21:55:54Z CRITICAL Erreur : --releasever doit être ultérieure à la version courante du système.
2017-11-15T21:58:56Z INFO --- logging initialized ---
2017-11-15T21:58:56Z DDEBUG timer: config: 2 ms
2017-11-15T21:58:56Z 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-15T21:58:56Z DEBUG DNF version: 2.7.5
2017-11-15T21:58:56Z DDEBUG Command: dnf system-upgrade reboot 
2017-11-15T21:58:56Z DDEBUG Installroot: /
2017-11-15T21:58:56Z DDEBUG Releasever: 27
2017-11-15T21:58:56Z DEBUG cachedir: /var/cache/dnf
2017-11-15T21:58:56Z DDEBUG Base command: system-upgrade
2017-11-15T21:58:56Z DDEBUG Extra commands: ['system-upgrade', 'reboot']
2017-11-15T21:58:56Z DDEBUG Cleaning up.
2017-11-15T21:58:56Z SUBDEBUG 
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 95, in _main
    cli.configure(list(map(ucd, args)), option_parser())
  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 889, in configure
    self.command.configure()
  File "/usr/lib/python3.6/site-packages/dnf-plugins/system_upgrade.py", line 319, in configure
    self._call_sub("check")
  File "/usr/lib/python3.6/site-packages/dnf-plugins/system_upgrade.py", line 330, in _call_sub
    subfunc()
  File "/usr/lib/python3.6/site-packages/dnf-plugins/system_upgrade.py", line 400, in check_reboot
    raise CliError(_("system is not ready for upgrade"))
dnf.cli.CliError: le système n’est pas prêt pour la mise à niveau
2017-11-15T21:58:56Z CRITICAL Erreur : le système n’est pas prêt pour la mise à niveau


I then tried to reinstall package (sudo dnf system-upgrade download --releasever=27 --allowerasing), but:
dnf.cli.CliError: --releasever doit être ultérieure à la version courante du système.
2017-11-15T21:59:47Z CRITICAL Erreur : --releasever doit être ultérieure à la version courante du système.

How can I get back to a clean state and upgrade correctly?
 

Version-Release number of selected component (if applicable):
27

How reproducible:
I don't know, upgrade told me no specific message (it only wasn't just able to recognize one on the listed repo)

Steps to Reproduce:
1.
2.
3.

Actual results:
Unable to upgrade, neither going back

Expected results:
Upgrade done!

Additional info:

Any help would be appreciated, I'm not an Unix Guru, but can execute comment and give feedback, even opening the server as it is a personal one (contact cmordant1@gmail.com)

Comment 1 Charlie Mordant 2017-11-22 13:30:45 UTC
Fixed: You should reboot and have a screen to follow the upgrade step (choose language, keyboard, ...) from there.


Note You need to log in before you can comment on or make changes to this bug.