Bug ID | 900376 |
---|---|
Summary | Upgrading OpenSuse 13.1 using zipper or yast2 triggers network failures |
Classification | openSUSE |
Product | openSUSE 13.1 |
Version | Final |
Hardware | x86-64 |
OS | openSUSE 13.1 |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | Network |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | foolishewe@hotmail.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Created attachment 609401 [details]
Tar bundle of command output and log files from the initial bug report
I have a Toshiba P855-S200 laptop that ran OpenSuse 12.1 (or was it 12.2)
without incident. I recently brought it back on line and updated the to
OpenSuse 13.1 from installation media (DVD) which went very smoothly. However
when I do the post install upgrade of packages, the networking fails (both
wireless and wired). The wireless adapter sees routers and connects using
Network Manager (on KDE). It appears that DNS is working (e.g. nslookup
cnn.com has the expected results), however actually retrieving data fails (e.g.
wget cnn.com fails). This causes the online update to fail to download
packages about 2/3 of the way through (always at the same point). Rebooting
does not fix this.
I am able to reproduce this, since I can use the install media to "Update"
which actually reverts the updated packages. I've tried this several times and
it appears to fail at the same point.
What information is needed to track this down?
How can I successfully upgrade my packages so that I get bug fixes and (more
importantly) security updates?
Please find attached a file name failedupgrade.tgz, which contains the
following information
tar tzvf ./failedupgrade.tgz
drwxr-xr-x dummy/users 0 2014-10-08 21:25 ./failedupgradeinfo/
-rw-r--r-- dummy/users 524 2014-10-08 07:51
./failedupgradeinfo/iwconfig.log
-rw-r--r-- dummy/users 995 2014-10-08 21:23 ./failedupgradeinfo/wget.log
-rw-r--r-- dummy/users 1367 2014-10-08 08:01 ./failedupgradeinfo/resolv.conf
-rw-r--r-- dummy/users 126 2014-10-08 07:52 ./failedupgradeinfo/uname.log
-rw-r--r-- dummy/users 61382 2014-10-08 08:07 ./failedupgradeinfo/dmesg.log
-rw-r--r-- dummy/users 143734 2014-10-08 08:00 ./failedupgradeinfo/rpmqa.log
-rw-r--r-- dummy/users 930961 2014-10-08 08:22
./failedupgradeinfo/wpa_supplicant.log
iwconfig.log - the output of iwconfig
wget.log - the output of nslookup cnn.com and wget cnn.com after the failed
on-line update
resolv.conf - the actual resolv.conf file (I changed it to use faster dns
servers).
uname.log - the output of uname -a after the failed on-line update
demesg.log - the output of dmesg after the failed on-line update
rpmqa.log - the output of rpm -q -a after the failed on-line update
wpa_supplicant.log - the wpa_supplicant.log file
zypperlr.log - the output of zypper lr after the failed on-line upgrade
attempt.
Steps to reproduce:
1) Install 13.1 from media and upgrade the existing installation.
2) If necessary, remove the apper package, it interferes with zypper and
yast2's software management.
3) Do Yast on-line update. Observe loss of network connectivity.