[Bug 543911] New: upgrading from 11.2 to 11.2M8, the update of nfs-client unmounts nfs directories
http://bugzilla.novell.com/show_bug.cgi?id=543911 Summary: upgrading from 11.2 to 11.2M8, the update of nfs-client unmounts nfs directories Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.14) Gecko/2009090900 SUSE/3.0.14-0.1.2 Firefox/3.0.14 I had the 11.2M8 repo available over NFS, and was going through an upgrade from 11.1 to 11.2M8. At the point where nfs-client gets upgraded, the nfs mount was unmounted and of course was unable to continue (I manually remounted it and was thereafter able to continue - however - it shouldn't have done that.) It would seem as though upgrades over NFS would be problematic! Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543911
Martin Vidner
http://bugzilla.novell.com/show_bug.cgi?id=543911
User nfbrown@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c1
Neil Brown
http://bugzilla.novell.com/show_bug.cgi?id=543911
zhu rensheng
http://bugzilla.novell.com/show_bug.cgi?id=543911
User aj@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c4
Andreas Jaeger
http://bugzilla.novell.com/show_bug.cgi?id=543911
User locilka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c5
Lukas Ocilka
http://bugzilla.novell.com/show_bug.cgi?id=543911
User ro@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c6
Ruediger Oertel
http://bugzilla.novell.com/show_bug.cgi?id=543911
Andreas Jaeger
http://bugzilla.novell.com/show_bug.cgi?id=543911
User jkupec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c7
--- Comment #7 from Ján Kupec
Setting NEEDINFO: Jano, what zypper does (similarly to Installation adjusting YAST_IS_RUNNING) that upgraded RPMs don't do dangerous actions?
Nothing. The rpms are supposed to work even with plain rpms, they should not do any dangerous actions :O) AFAIK, YAST_IS_RUNNING is just telling the packages to avoid running suseconfig, since yast will do it once for all at the end of installation. Nevertheless, zypper does not set this variable, as this solution should be replaced with a better one at the RPM level (see bug 365649). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543911
User jkupec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c8
--- Comment #8 from Ján Kupec
Nothing. The rpms are supposed to work even with plain rpms i mean 'plain rpm command'
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543911
User nfbrown@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c9
--- Comment #9 from Neil Brown
http://bugzilla.novell.com/show_bug.cgi?id=543911
User jnelson-suse@jamponi.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c10
--- Comment #10 from Jon Nelson
http://bugzilla.novell.com/show_bug.cgi?id=543911
User nfbrown@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c11
Neil Brown
Will that work in the context of SuSEfirewall (which, for NFSv3, uses obtains the rpc port numbers dynamically) or will they remain bound to the same port?
That is a very good point. statd is the only service which this might be a problem for. If statd was started without specifying a port to use (as is normal) it will typically choose different ports numbers for UDP and TCP. If we kill and restart it, it is not possible to ask it to choose the same two port numbers. If a port number is specified, it will be used for both UDP and TCP. So the options seem to be to either - rerun the firewall rules after restarting statd - not restart statd if there is a firewall active. - hard code a number to be used by statd always While the last would be simplest, it is not possible to choose a number that will always be free. The second would also be fairly simply I suspect, if we found a security hole in statd, we would really want it to be restarted on an update. So that leaves the first option. I think that would be if [ -e /sbin/SuSEfirewall2 ]; then if /sbin/SuSEfirewall2 status < /dev/null > /dev/null then /sbin/SuSEfirewall2 on > /dev/null fi fi Ludwig: I think you are the maintainer of SuSEfirewall2 - would that be a safe thing to put in /etc/init.d/nfs to run after 'statd' has been restarted in response to "/etc/init.d/nfs restart" ?? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543911
User lnussel@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c12
Ludwig Nussel
http://bugzilla.novell.com/show_bug.cgi?id=543911
User nfbrown@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c13
--- Comment #13 from Neil Brown
http://bugzilla.novell.com/show_bug.cgi?id=543911
User nfbrown@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c14
--- Comment #14 from Neil Brown
http://bugzilla.novell.com/show_bug.cgi?id=543911
User nfbrown@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543911#c15
--- Comment #15 from Neil Brown
http://bugzilla.novell.com/show_bug.cgi?id=543911#c16
Neil Brown
http://bugzilla.novell.com/show_bug.cgi?id=543911
http://bugzilla.novell.com/show_bug.cgi?id=543911#c17
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=543911
http://bugzilla.novell.com/show_bug.cgi?id=543911#c18
--- Comment #18 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com