[opensuse-factory] 13.1: no NIC configured at boot after zypper dup upgrade
On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn@steve-ss.com> wrote:
On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 16/10/13 15:29, Rich Coe escribió:
I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup.
On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either.
Any tips to configure eth0 at boot or diagnose the issue?
Thanks.
There is no eth0 or eth1 or whatever eth.. by default now. interfaces are named according to http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... .. that document contains instructions to "go back" to the old names..
Christian,
I opened a bugzilla yesterday because after a 12.3 => 13.1 upgrade I didn't have a configured interface of any name.
<https://bugzilla.novell.com/show_bug.cgi?id=845886>
I had to go into yast and configure it before it showed up with any name.
After configuring via yast, it showed up when I ran ifconfig. I assumed it was VMware related, but I don't know.
Greg
Hi 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what was usually eth0. ifup failed. I too ran yast where I found that the default route had been deleted. I re-entered it and yast completed whereupon ifup eth0 began working again.
Will this be the norm for the upgrade to 13.1? Thanks, L x
Lynn, Did you open a bugzilla? If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me. My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs. I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM. I used: - Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup - choose uninstall vmware client packages (2 different interactions with zypper) - let it run to completion - reboot - login as root - ifconfig The only interface displayed is lo (loopback). I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2013-10-16 at 17:24 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn@steve-ss.com> wrote:
On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 16/10/13 15:29, Rich Coe escribió:
I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup.
On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either.
Any tips to configure eth0 at boot or diagnose the issue?
Thanks.
There is no eth0 or eth1 or whatever eth.. by default now. interfaces are named according to http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... .. that document contains instructions to "go back" to the old names..
Christian,
I opened a bugzilla yesterday because after a 12.3 => 13.1 upgrade I didn't have a configured interface of any name.
<https://bugzilla.novell.com/show_bug.cgi?id=845886>
I had to go into yast and configure it before it showed up with any name.
After configuring via yast, it showed up when I ran ifconfig. I assumed it was VMware related, but I don't know.
Greg
Hi 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what was usually eth0. ifup failed. I too ran yast where I found that the default route had been deleted. I re-entered it and yast completed whereupon ifup eth0 began working again.
Will this be the norm for the upgrade to 13.1? Thanks, L x
Lynn,
Did you open a bugzilla?
If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me.
My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs.
I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM.
I used:
- Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup
- choose uninstall vmware client packages (2 different interactions with zypper)
- let it run to completion - reboot - login as root - ifconfig
The only interface displayed is lo (loopback).
I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla.
Greg
Hi Greg Hope you don't mind. As it sees to be the same, I added it to your bugzilla with a link back here. Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/16/2013 04:24 PM, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn@steve-ss.com> wrote:
On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 16/10/13 15:29, Rich Coe escribió:
I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup.
On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either.
Any tips to configure eth0 at boot or diagnose the issue?
Thanks.
There is no eth0 or eth1 or whatever eth.. by default now. interfaces are named according to http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... .. that document contains instructions to "go back" to the old names..
Christian,
I opened a bugzilla yesterday because after a 12.3 => 13.1 upgrade I didn't have a configured interface of any name.
<https://bugzilla.novell.com/show_bug.cgi?id=845886>
I had to go into yast and configure it before it showed up with any name.
After configuring via yast, it showed up when I ran ifconfig. I assumed it was VMware related, but I don't know.
Greg
Hi 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what was usually eth0. ifup failed. I too ran yast where I found that the default route had been deleted. I re-entered it and yast completed whereupon ifup eth0 began working again.
Will this be the norm for the upgrade to 13.1? Thanks, L x
Lynn,
Did you open a bugzilla?
If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me.
My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs.
I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM.
I used:
- Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup
- choose uninstall vmware client packages (2 different interactions with zypper)
- let it run to completion - reboot - login as root - ifconfig
The only interface displayed is lo (loopback).
I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla.
A "zypper dup" from 12.3 to 13.1 on two different real machines worked for me with no problem other than plasma-nm was installed instead on plasmoid-networkmanager. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 16 Oct 2013 17:24:32 -0400 Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn@steve-ss.com> wrote:
On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 16/10/13 15:29, Rich Coe escribió:
I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup.
On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either.
Any tips to configure eth0 at boot or diagnose the issue?
Thanks.
There is no eth0 or eth1 or whatever eth.. by default now. interfaces are named according to http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... .. that document contains instructions to "go back" to the old names..
Christian,
I opened a bugzilla yesterday because after a 12.3 => 13.1 upgrade I didn't have a configured interface of any name.
<https://bugzilla.novell.com/show_bug.cgi?id=845886>
I had to go into yast and configure it before it showed up with any name.
After configuring via yast, it showed up when I ran ifconfig. I assumed it was VMware related, but I don't know.
Greg
Hi 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what was usually eth0. ifup failed. I too ran yast where I found that the default route had been deleted. I re-entered it and yast completed whereupon ifup eth0 began working again.
Will this be the norm for the upgrade to 13.1? Thanks, L x
Lynn,
Did you open a bugzilla?
If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me.
My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs.
I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM.
I used:
- Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup
- choose uninstall vmware client packages (2 different interactions with zypper)
- let it run to completion - reboot - login as root - ifconfig
The only interface displayed is lo (loopback).
I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla.
Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I had opened a bugzilla for the upgrade issue as well. https://bugzilla.novell.com/show_bug.cgi?id=841632 So far no joy. I can't upgrade any hardwired systems until this bug is fixed. Rich -- Rich Coe rcoe@wi.rr.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
op 16-10-13 23:24, Greg Freemyer schreef:
On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn@steve-ss.com> wrote:
On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 16/10/13 15:29, Rich Coe escribió:
I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup.
On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either.
Any tips to configure eth0 at boot or diagnose the issue?
Thanks.
There is no eth0 or eth1 or whatever eth.. by default now. interfaces are named according to http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... .. that document contains instructions to "go back" to the old names..
Christian,
I opened a bugzilla yesterday because after a 12.3 => 13.1 upgrade I didn't have a configured interface of any name.
<https://bugzilla.novell.com/show_bug.cgi?id=845886>
I had to go into yast and configure it before it showed up with any name.
After configuring via yast, it showed up when I ran ifconfig. I assumed it was VMware related, but I don't know.
Greg Hi 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what was usually eth0. ifup failed. I too ran yast where I found that the default route had been deleted. I re-entered it and yast completed whereupon ifup eth0 began working again.
Will this be the norm for the upgrade to 13.1? Thanks, L x
Lynn,
Did you open a bugzilla?
If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me.
My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs.
I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM.
I used:
- Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup
- choose uninstall vmware client packages (2 different interactions with zypper)
- let it run to completion - reboot - login as root - ifconfig
The only interface displayed is lo (loopback).
I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla.
Greg As I replied to the issue Richat Coe opened, maybe it is bug 844146? Eventually I did a fresh install of 13.1RC1, and now I have a functioning network (with the new network names). The bug seemed to boil down to a problem with avahi-autoipd.
Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
All, I just closed the bug associated with this thread. It was a user error (yes, I was the user). I expected "ifconfig" to show me all interfaces including "down" interfaces. It doesn't, I needed to be running "ifconfig -a" See https://bugzilla.novell.com/show_bug.cgi?id=845886#c7 for more detail if you care. Greg -- Greg Freemyer On Thu, Oct 17, 2013 at 2:17 PM, Jogchum Reitsma <j.reitsma@hccnet.nl> wrote:
op 16-10-13 23:24, Greg Freemyer schreef:
On Wed, Oct 16, 2013 at 4:52 PM, lynn <lynn@steve-ss.com> wrote:
On Wed, 2013-10-16 at 16:18 -0400, Greg Freemyer wrote:
On Wed, Oct 16, 2013 at 2:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 16/10/13 15:29, Rich Coe escribió:
I'm running 13.1. I have a fixed ip-address configured for eth0 and it supposed to config with ifup.
On boot, eth0 does not get configured. Running 'ifup eth0' does not configure eth0 either.
Any tips to configure eth0 at boot or diagnose the issue?
Thanks.
There is no eth0 or eth1 or whatever eth.. by default now. interfaces are named according to
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... .. that document contains instructions to "go back" to the old names..
Christian,
I opened a bugzilla yesterday because after a 12.3 => 13.1 upgrade I didn't have a configured interface of any name.
<https://bugzilla.novell.com/show_bug.cgi?id=845886>
I had to go into yast and configure it before it showed up with any name.
After configuring via yast, it showed up when I ran ifconfig. I assumed it was VMware related, but I don't know.
Greg
Hi 12.3 to 13.1 upgrade same here but on vbox. The upgrade knocked out what was usually eth0. ifup failed. I too ran yast where I found that the default route had been deleted. I re-entered it and yast completed whereupon ifup eth0 began working again.
Will this be the norm for the upgrade to 13.1? Thanks, L x
Lynn,
Did you open a bugzilla?
If this is not a pure VMware related bug, this is seeming like a major / potential showstopper bug to me.
My bugzilla again is: <https://bugzilla.novell.com/show_bug.cgi?id=845886> I have it set as priority "none" currently because I thought it only impacted VMware installs.
I repeated my upgrade test of VWware appliance from 12.3 => 13.1 on another VM.
I used:
- Set Repos to 12.3 OSS and 12.3 OSS upgrade repos only. - zypper dup to ensure a pure 12.3 environment was in place - change the 2 repos to the 13.1 equivalents - zypper dup
- choose uninstall vmware client packages (2 different interactions with zypper)
- let it run to completion - reboot - login as root - ifconfig
The only interface displayed is lo (loopback).
I don't need this VM to be functional, so I'll leave it like that if anyone wants me to do any troubleshooting. If you want it properly tracked, please ask via bugzilla.
Greg
As I replied to the issue Richat Coe opened, maybe it is bug 844146? Eventually I did a fresh install of 13.1RC1, and now I have a functioning network (with the new network names). The bug seemed to boil down to a problem with avahi-autoipd.
Jogchum
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op vrijdag 18 oktober 2013 17:28:22 schreef Greg Freemyer:
All,
I just closed the bug associated with this thread. It was a user error (yes, I was the user).
I expected "ifconfig" to show me all interfaces including "down" interfaces. It doesn't, I needed to be running "ifconfig -a"
ifconfig is deprecated, ip is the replacement. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Oct 18, 2013 at 6:27 PM, Freek de Kruijf <f.de.kruijf@gmail.com> wrote:
Op vrijdag 18 oktober 2013 17:28:22 schreef Greg Freemyer:
All,
I just closed the bug associated with this thread. It was a user error (yes, I was the user).
I expected "ifconfig" to show me all interfaces including "down" interfaces. It doesn't, I needed to be running "ifconfig -a"
ifconfig is deprecated, ip is the replacement.
hell, I'm probably deprecated. Doesn't mean I can't do anything! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Freek de Kruijf -
Greg Freemyer -
Jogchum Reitsma -
Larry Finger -
lynn -
Rich Coe