September 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 897636] nm-connection-editor: Failed to get zones from FirewallD: (2) The name org.fedoraproject.FirewallD1 was not provided by any .service files
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=897636 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.gnome.org/ | |show_bug.cgi?id=737687 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #9 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Marius Tomaschewski from comment #8) > (In reply to Dominique Leuenberger from comment #7) > > (In reply to Marius Tomaschewski from comment #6) > > > (In reply to Dominique Leuenberger from comment #4) > > > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/data/ > > > > NetworkManager.service.in?id=1d89bc0004ec27fbc0c89f17861118c78d7eeab5 and > > > > the referenced bug (https://bugzilla.redhat.com/show_bug.cgi?id=876218#c49) > > > > have a very nice story why NM is not tearing down the network on 'systemctl > > > > stop NetworkManager' > > > > > > > > => on a shutdown, if you have a NFS mounted root, the root 'disappears' on > > > > you and the shutdown hangs... > > > > > > Ah... yes. Then I'd say: kill -9 dhclient in this case would do the right > > > thing (same as sysconfig were doing before ;-) > > > > done by what? if we don't want it and do not care for remote FS root, then > > we can disable this and simply kill the network on the go; > > By NM when there is a remote FS. if NM were to do that: then the shutdown issue as described in the referenced git commit will be happening: once the network is down, you don't have access to those remote FS anymore (and if this is the wish, then we simply patch out the KillMode=Process away) > > Question would be: what is more common: > > - User switching NM off completely to switch to wicked > > (if done through Yast, yast should be able to take care of terminating > > dhclient as well) > > if done by means of services, well, the user better know what he does :) > > Skilled user -- perhaps: when he notices this left over. Otherwise there > is dhclient running and breaking the currently used network service. The not skilled user would switch using Yast... which should have the knowledge of what to do to properly switch... switching is certainly not the daily task... > > of > > > > updating NetworkManager package and triggering a restart (on Factory this > > happens often... ) > > > > => I'm in favor of keeping NM the way it is; and for the case of a user > > switching between NM and wicked, have yast to the right things (which would > > mean for this bug: 'wontfix'...it actually does not describe an explicit > > issue after all > > It is IMO definitely not a WONTFIX as it breaks networking. The new service > isn't able to work properly when the old leaves running dhcp clients. switching is not a daily task and should get it's sep handling in the switching code... there I don't object it terminating more tasks.. on a simple restart of the NM service, it just sounds wrong. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #8 from Marius Tomaschewski <mt(a)suse.com> --- (In reply to Dominique Leuenberger from comment #7) > (In reply to Marius Tomaschewski from comment #6) > > (In reply to Dominique Leuenberger from comment #4) > > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/data/ > > > NetworkManager.service.in?id=1d89bc0004ec27fbc0c89f17861118c78d7eeab5 and > > > the referenced bug (https://bugzilla.redhat.com/show_bug.cgi?id=876218#c49) > > > have a very nice story why NM is not tearing down the network on 'systemctl > > > stop NetworkManager' > > > > > > => on a shutdown, if you have a NFS mounted root, the root 'disappears' on > > > you and the shutdown hangs... > > > > Ah... yes. Then I'd say: kill -9 dhclient in this case would do the right > > thing (same as sysconfig were doing before ;-) > > done by what? if we don't want it and do not care for remote FS root, then > we can disable this and simply kill the network on the go; By NM when there is a remote FS. > Question would be: what is more common: > - User switching NM off completely to switch to wicked > (if done through Yast, yast should be able to take care of terminating > dhclient as well) > if done by means of services, well, the user better know what he does :) Skilled user -- perhaps: when he notices this left over. Otherwise there is dhclient running and breaking the currently used network service. > of > > updating NetworkManager package and triggering a restart (on Factory this > happens often... ) > > => I'm in favor of keeping NM the way it is; and for the case of a user > switching between NM and wicked, have yast to the right things (which would > mean for this bug: 'wontfix'...it actually does not describe an explicit > issue after all It is IMO definitely not a WONTFIX as it breaks networking. The new service isn't able to work properly when the old leaves running dhcp clients. The problem is also: when you start dhclient again, the dhclient script _may_ deconfigure the interface / address family it currently handles; this depends on the script implementation of course. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 897636] nm-connection-editor: Failed to get zones from FirewallD: (2) The name org.fedoraproject.FirewallD1 was not provided by any .service files
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

1 0

[Bug 756673] New: problem with quota managing by yast2
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=756673 https://bugzilla.novell.com/show_bug.cgi?id=756673#c0 Summary: problem with quota managing by yast2 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: akorzen(a)jhmi.edu QAContact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110420 SUSE/3.6.17-0.2.1 Firefox/3.6.17 if you try to manage quotas for users or groups by yast2 it always displays 0 however it saves and remembers the quotas, if you check it by repquota -a but it is not possible to get back to 0 (unlimited) it needs to be done by edquota thanks anna Reproducible: Always Steps to Reproduce: 1. 2. 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.

1 3

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #7 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Marius Tomaschewski from comment #6) > (In reply to Dominique Leuenberger from comment #4) > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/data/ > > NetworkManager.service.in?id=1d89bc0004ec27fbc0c89f17861118c78d7eeab5 and > > the referenced bug (https://bugzilla.redhat.com/show_bug.cgi?id=876218#c49) > > have a very nice story why NM is not tearing down the network on 'systemctl > > stop NetworkManager' > > > > => on a shutdown, if you have a NFS mounted root, the root 'disappears' on > > you and the shutdown hangs... > > Ah... yes. Then I'd say: kill -9 dhclient in this case would do the right > thing (same as sysconfig were doing before ;-) done by what? if we don't want it and do not care for remote FS root, then we can disable this and simply kill the network on the go; Question would be: what is more common: - User switching NM off completely to switch to wicked (if done through Yast, yast should be able to take care of terminating dhclient as well) if done by means of services, well, the user better know what he does :) of updating NetworkManager package and triggering a restart (on Factory this happens often... ) => I'm in favor of keeping NM the way it is; and for the case of a user switching between NM and wicked, have yast to the right things (which would mean for this bug: 'wontfix'...it actually does not describe an explicit issue after all -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #6 from Marius Tomaschewski <mt(a)suse.com> --- (In reply to Dominique Leuenberger from comment #4) > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/data/ > NetworkManager.service.in?id=1d89bc0004ec27fbc0c89f17861118c78d7eeab5 and > the referenced bug (https://bugzilla.redhat.com/show_bug.cgi?id=876218#c49) > have a very nice story why NM is not tearing down the network on 'systemctl > stop NetworkManager' > > => on a shutdown, if you have a NFS mounted root, the root 'disappears' on > you and the shutdown hangs... Ah... yes. Then I'd say: kill -9 dhclient in this case would do the right thing (same as sysconfig were doing before ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #5 from Marius Tomaschewski <mt(a)suse.com> --- I'd guess the reason for KillMode=process was the following: On update, you want to restart NetworkManager, but not break the network connectivity if possible [and thus probably the update]. A SIGTERM sent to dhclient would cause that it deconfigure the interface, except it is stopped using "dhclient -x ifname" or kill -SIGKILL. I'd say, we can reassign this bug to NetworkManager to handle the stop and update cases properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #4 from Dominique Leuenberger <dimstar(a)opensuse.org> --- http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/data/Netwo… and the referenced bug (https://bugzilla.redhat.com/show_bug.cgi?id=876218#c49) have a very nice story why NM is not tearing down the network on 'systemctl stop NetworkManager' => on a shutdown, if you have a NFS mounted root, the root 'disappears' on you and the shutdown hangs... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 895447] yast2 lan leaves part of NetworkManager running
by bugzilla_noreply＠novell.com 30 Sep '14

30 Sep '14

http://bugzilla.suse.com/show_bug.cgi?id=895447 --- Comment #3 from Marius Tomaschewski <mt(a)suse.com> --- (In reply to Dominique Leuenberger from comment #1) > NetworkManager.service contains: > > # NM doesn't want systemd to kill its children for it > KillMode=process Ah... thanks -- this explains a lot :-) > this obviously is the reason for dhclient to stick around... question would > be why this was decided... will inquire about the full rationale. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0