869213 – After zypper update, on 3/18/2014 network interfaces configured for on cable connect will no come up

Bug 869213 - After zypper update, on 3/18/2014 network interfaces configured for on cable connect will no come up

Summary: After zypper update, on 3/18/2014 network interfaces configured for on cable ...

Status:	RESOLVED DUPLICATE of bug 869761

Alias:	None

Product:	openSUSE 13.1
Classification:	openSUSE
Component:	Network (show other bugs)
Version:	Final
Hardware:	x86-64 openSUSE 13.1

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	Marius Tomaschewski
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2014-03-19 16:45 UTC by Gary Ernst
Modified:	2014-04-15 12:19 UTC (History)
CC List:	2 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Gary Ernst 2014-03-19 16:45:21 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0

This may be a duplicate of 866870. I was unable to review the details
I have two laptops, a Lenovo t430 and a Toshiba tecra Both with opensuse 13.1 x86_64. Both laptops worked without issue until the update.Both have ethernet and wireless interfaces. They were both configured with on cable connect with the ethernet interface configured for a higher priority. Both as DHCP. I can circumvent by configuring the ethernet as "on boot" and the wireless as "manual".
via yast.

Reproducible: Always

Steps to Reproduce:
1.configure as described above with latest zypper updates
2.reboot
3.
Actual Results:  
The only interface that shows active from an ifconfig command is the local loopback

Expected Results:  
When connected via cable, Ethernet succesfuly configured via DHCP

Comment 2 Nicholas Omann 2014-03-26 23:37:36 UTC

I have the same issue. For me I am using Parallels Desktop to run on a MacBook Pro. I have also been able to resolve it by changing the configuration to on boot or by manually running dhcpcd.

Comment 3 Marius Tomaschewski 2014-04-15 01:52:15 UTC

Does it work for you with the recently released sysconfig-0.81.5-26.1?
When not, please reopen.

*** This bug has been marked as a duplicate of bug 869761 ***

Comment 4 Gary Ernst 2014-04-15 12:19:48 UTC

Yes. All seems to back to normal