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 1056075 - Update fails because no intermediate internet connection available
Summary: Update fails because no intermediate internet connection available
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-21 13:54 UTC by Soren Wacker
Modified: 2014-06-11 09:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-11 09:38:42 UTC


Attachments (Terms of Use)

Description Soren Wacker 2014-01-21 13:54:13 UTC
Description of problem:
The current OS update requires a restart of the system. After the restart, I must type in my internet password. However, before I can do that I get the message "Failed to update. Network access was required but not available". 

Version-Release number of selected component (if applicable):
Don't have the update ID or so. I just says "OS Update: Includes performances..."

How reproducible:
Start OS update.
Use a wireless network that requires a password.

Expected results:
The update should give me the chance to establish an internet connection before it fails.

Comment 1 Jan Zeleny 2014-01-21 14:14:24 UTC
Need much more information here: what Fedora? What program do you use to do the update, how do you start it, ... anything you can imagine might be relevant. I don't believe this has something to do with yum, as it is not officially recommended way to update the system IIRC.


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