https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c2 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com --- Comment #2 from Tim Hardeck 2013-02-28 13:57:53 UTC --- There was a bug against 12.2 for this issue: bnc#780441 but it might be something else according to Thomas. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c7 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|thardeck@suse.com | --- Comment #7 from Tim Hardeck 2013-03-05 09:10:19 UTC --- Created an attachment (id=528130) --> (http://bugzilla.novell.com/attachment.cgi?id=528130) output of systemctl show for all three services -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c9 --- Comment #9 from Thomas Renninger 2013-03-05 10:12:10 UTC --- I looked at this for 12.2, but there it was slightly different. Afaik on 12.2 only specific machines run into this. Now every machine I tried runs into this. What is missing in nfs-utils is proper systemd integration (not sure whether someone else looked at this meanwhile, I will attach my work I've already done against 12.2 nfs-utils package). I never came to test this on 12.2, this does not help for 12.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c12 --- Comment #12 from Tim Hardeck 2013-03-05 10:37:16 UTC --- I am not using the Networkmanager, I am using ifup with static ip configuration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c17 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Basesystem |YaST2 InfoProvider| |thardeck@suse.com QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #17 from Ludwig Nussel 2013-03-05 15:09:39 CET --- I fail to see how this has anything to do with insserv. ypbind and autofs are systemd services. The yast2 nis module is buggy though, it doesn't enable them (will file bug for that). Check for i in rpcbind.socket ypbind autofs; do systemctl status $i; done to make sure those services are enabled and running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c19 --- Comment #19 from Thomas Renninger 2013-03-05 17:38:57 UTC --- Created an attachment (id=528240) --> (http://bugzilla.novell.com/attachment.cgi?id=528240) nfs-utils .spec file changes to intergrate an systemd nfs.target This was my try to fix 12.2. IMO something like this is missing to be able to synchronize with nfs. Even better would be to further separate nfs targets. The same someone wanted to do in init V already (/etc/init.d/nfs): # XXX: there should be separate init scripts for these really IDMAPD_BIN=/usr/sbin/rpc.idmapd GSSD_BIN=/usr/sbin/rpc.gssd STATD_BIN=/usr/sbin/rpc.statd Fedora has something similar. I will attach the real nfs.target file as well. I could imagine, that might have helped on 12.2, where my machine worked with ypbind (but slower ones did not?), but it got worse and you now always do not get ypbind working. So I could imagine there are several issues, the nfs.target may address one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c21 --- Comment #21 from Thomas Renninger 2013-03-05 17:43:05 UTC ---

Fedora has something similar They had not split targets to imapd/gssd/statd yet and I tried to more or less adopt the dependencies of nfs.target to what services we have. I need some review/testing and I can submit this (or adjusted).

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c22 --- Comment #22 from Tim Hardeck 2013-03-10 09:30:53 UTC --- After installing 12.3 GM I still had network issues in Stage 2 but after fixing them manually this issue is gone for me. Was anything updated in this regard besides the NetworkManager which isn't started anymore if it is disabled? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c24 --- Comment #24 from Michael Karbach 2013-03-29 08:47:28 UTC --- Sorry, I also have this bug and I am using ifup with dhcp. I have updated from OS-12.1 to OS-12.3 via DVD. Unfortunately I do not know what to do for fixing this upon reading the above messages. Manually restarting the services from post one solves this problem temporary. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c26 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|thardeck@suse.com | --- Comment #26 from Tim Hardeck 2013-04-01 13:22:22 UTC --- (In reply to comment #24)

Sorry, I also have this bug and I am using ifup with dhcp. I have updated from OS-12.1 to OS-12.3 via DVD. Have you checked if the process NetworkManager is running?

(In reply to comment #25)

Note, in addition to the above problems, also sshd and cupsd are not started and have to be start manually too. Sounds like an upgrade issue - maybe because of the direct update from 12.1 to 12.3 and the systemd changes.

Have you tried activating the services again with chkconfig or yast? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c28 --- Comment #28 from Tim Hardeck 2013-04-01 15:59:23 UTC --- (In reply to comment #27)

* Yes, NW is running: 481 0.0 0.2 241864 8528 ? Ssl 08:54 0:00 /usr/sbin/NetworkManager --no-daemon

Is this ok, if one is using if-up? No, it is not ok. I would try to enable the NetworkManager in `yast2 lan` and after confirming the change enable the traditional method again.

* Yes, I have done this with yast2. But I am wondering, in expert-mode I do not see the options for different runlevels. Is this also due to systemd? It seems that way: http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c30 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #30 from Tim Hardeck 2013-04-01 16:34:29 UTC --- Could we update the NetworkManager or systemd packages so that during a dist upgrade from earlier openSUSE versions the sysconfig NetworkManager entry is analyzed and the links set accordingly? It seems that only the unrequested start of NetworkManager is causing this issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c32 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |mt@suse.com InfoProvider|mt@suse.com | --- Comment #32 from Marius Tomaschewski 2013-04-02 11:42:37 UTC --- (In reply to comment #30)

Could we update the NetworkManager or systemd packages so that during a dist upgrade from earlier openSUSE versions the sysconfig NetworkManager entry is analyzed and the links set accordingly?

The /etc/sysconfig/network/config NETWORKMANAGER variable is migrated on update from <= 12.2 to 12.3, fixed in bnc#803058. See "rpm -q --scripts sysconfig" and also "rpm -q --scripts NetworkManager" on 12.3-final (RC2). More exactly, the variable is migrated, when the previous sysconfig were providing it. When you've had some 12.3-Beta/RC version installed before, the migration is *not* preformed [some tools may still set it using own obsolete defaults]. Also not, when you try to trigger it with e.g.: echo 'NETWORKMANAGER="no"' >> /etc/sysconfig/network/config

It seems that only the unrequested start of NetworkManager is causing this issue.

Yes, it does. ifup refuses do do anything when NetworkManager is enabled. This happens on systems which were updated to some 12.3-Beta or RC before. As this bug is reported with "Found in Version: RC2", I'd say we can close it as dup of bnc#803058 -- we've already verified the migration in several duplicates. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=806725 https://bugzilla.novell.com/show_bug.cgi?id=806725#c34 Tim Hardeck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #34 from Tim Hardeck 2013-04-02 11:51:30 UTC --- This autofs issue might still happen if the NetworkManager is used but there is another report for this issue. Marking as resolved. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.