Bug 1251708 - fedup 21-22 on KVM VPS fails after reboot - stuck on progress bar
fedup 21-22 on KVM VPS fails after reboot - stuck on progress bar
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: fedup-dracut (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Will Woods
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-08 20:53 EDT by Dimitris
Modified: 2016-07-19 13:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 13:25:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dimitris 2015-08-08 20:53:17 EDT
Description of problem:

Trying to upgrade a VPS KVM instance from F21 to F22.  The fedup run itself completes but the system hangs almost immediately after reboot; I haven't been able to disable the progress bar to see if there's something relevant displayed on the console at that point.  TTY2 is not accessible (I only have console access from the VNC view).

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

fedup: 0.9.2-1.fc21
systemd: 216-25.fc21

How reproducible:

every time

Steps to Reproduce:
1. fedup --network 22
2. fedup completes with:

setting up update...
finding updates 100% [=======================================================================================================================]
WARNING: potential problems with upgrade
  firewalld-config-standard-0.3.14.2-2.fc21.noarch (no replacement) requires firewalld-0.3.14.2-2.fc21.noarch (replaced by firewalld-0.3.14.2-2.fc22.noarch)
verify local files 100% [====================================================================================================================]
testing upgrade transaction
rpm transaction 100% [=======================================================================================================================]
rpm install 100% [===========================================================================================================================]
setting up system for upgrade
Packages without updates:
  basesystem-10.0-10.fc21.noarch
  firewalld-config-standard-0.3.14.2-2.fc21.noarch
  python-decorator-3.4.0-5.fc21.noarch
  rootfiles-8.1-17.fc21.noarch

WARNING: problems were encountered during transaction test:
  broken dependencies
    firewalld-config-standard-0.3.14.2-2.fc21.noarch requires firewalld-0.3.14.2-2.fc21.noarch
These packages may have problems after the upgrade.

3. Upon reboot, to try to diagnose I edit the grub boot entry and change:
  - gfxpayload=text
  - add nosplash to kernel command line

Actual results:

system boots into upgrade entry and very soon displays the graphical Fedora logo with progress bar, then hangs.

Pressing escape (verified - it is being sent by the VNC client) does nothing, so I can't see the text console.

Expected results:

Expected to at least have the text console visible.  Previous F20-F21 fedup on the same VPS instance had gone off without any issues.

Additional info:
Comment 1 Fedora End Of Life 2016-07-19 13:25:35 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

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