[Bug 829265] New: autoyast chroot script with chrooted=true cannot be retrieved via nfs
https://bugzilla.novell.com/show_bug.cgi?id=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c0 Summary: autoyast chroot script with chrooted=true cannot be retrieved via nfs Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: All OS/Version: SLES 11 Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST AssignedTo: fehr@suse.com ReportedBy: sebastian.herbszt@tfa.verwalt-berlin.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20100101 Firefox/17.0 The specified chroot script in the autoyast profile cannot be retrieved via nfs. Reproducible: Always Steps to Reproduce: Perform network installation via nfs and put the following in the autoyast profile: <scripts> <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <filename>chroot-script-20120313.sh</filename> <interpreter>shell</interpreter> <location><![CDATA[nfs://10.16.77.245/export/os/SLES11/autoyast/scripts/chroot-script-20120313.sh]]></location> </script> </chroot-scripts> </scripts> Actual Results: 2013-07-12 14:41:26 <1> U1160005(3478) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Calling YaST client autoinst_scripts2_finish 2013-07-12 14:41:26 <1> U1160005(3478) [YCP] clients/autoinst_scripts2_finish.ycp:33 starting autoinst_scripts2_finish 2013-07-12 14:41:26 <1> U1160005(3478) [YCP] AutoinstScripts.ycp:728 Writing chroot script into /mnt/var/adm/autoinstall/scripts/chroot-script-20120313.sh 2013-07-12 14:41:26 <1> U1160005(3478) [YCP] autoinstall/io.ycp:64 Scheme:nfs Host:10.16.77.245 Path:/export/os/SLES11/autoyast/scripts/chroot-script-20120313.sh Localfile:/mnt/var/adm/autoinstall/scripts/chroot-script-20120313.sh 2013-07-12 14:41:26 <1> U1160005(3478) [agent-system] SystemAgent.cc(Execute):1129 mkdir /tmp/YaST2-03478-3mbweF/tmp_mount 2013-07-12 14:41:26 <2> U1160005(3478) [YCP] autoinstall/io.ycp:185 Mount failed 2013-07-12 14:41:26 <3> U1160005(3478) [YCP] AutoinstScripts.ycp:733 script nfs://10.16.77.245/export/os/SLES11/autoyast/scripts/chroot-script-20120313.sh could not be retrieved 2013-07-12 14:41:26 <1> U1160005(3478) [YCP] AutoinstScripts.ycp:778 Script Execution command: /bin/sh -x /var/adm/autoinstall/scripts/chroot-script-20120313.sh 2&> /var/adm/autoinstall/logs/chroot-script-20120313.sh.log 2013-07-12 14:41:26 <1> U1160005(3478) [YCP] clients/autoinst_scripts2_finish.ycp:58 autoinst_scripts2_finish finished 2013-07-12 14:41:26 <1> U1160005(3478) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Called YaST client returned. Expected Results: 2013-07-12 15:22:54 <1> U1160005(3572) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Calling YaST client autoinst_scripts2_finish 2013-07-12 15:22:54 <1> U1160005(3572) [YCP] clients/autoinst_scripts2_finish.ycp:33 starting autoinst_scripts2_finish 2013-07-12 15:22:54 <1> U1160005(3572) [YCP] AutoinstScripts.ycp:728 Writing chroot script into /mnt/var/adm/autoinstall/scripts/chroot-script-20120313.sh 2013-07-12 15:22:54 <1> U1160005(3572) [YCP] autoinstall/io.ycp:64 Scheme:nfs Host:10.16.77.245 Path:/export/os/SLES11/autoyast/scripts/chroot-script-20120313.sh Localfile:/mnt/var/adm/autoinstall/scripts/chroot-script-20120313.sh 2013-07-12 15:22:54 <1> U1160005(3572) [agent-system] SystemAgent.cc(Execute):1129 mkdir /tmp/YaST2-03572-D0c7IP/tmp_mount 2013-07-12 15:22:54 <1> U1160005(3572) [YCP] autoinstall/io.ycp:196 Copy Command: /bin/cp /tmp/YaST2-03572-D0c7IP/tmp_mount/chroot-script-20120313.sh /mnt/var/adm/autoinstall/scripts/chroot-script-20120313.sh 2013-07-12 15:22:54 <1> U1160005(3572) [YCP] AutoinstScripts.ycp:778 Script Execution command: /bin/sh -x /var/adm/autoinstall/scripts/chroot-script-20120313.sh 2&> /var/adm/autoinstall/logs/chroot-script-20120313.sh.log 2013-07-12 15:22:54 <1> U1160005(3572) [YCP] clients/autoinst_scripts2_finish.ycp:58 autoinst_scripts2_finish finished The problem can be reproduced on SLES 11 up to and including SP3. The following incomplete change fixes this issue: --- /usr/share/YaST2/include/autoinstall/io.ycp 2013-04-30 18:34:01.000000000 +0200 +++ /tmp/linux/suse/x86_64-sles11/y2update/include/autoinstall/io.ycp 2013-07-12 10:14:29.000000000 +0200 @@ -179,7 +179,10 @@ y2milestone("Starting portmap: %1", SCR::Execute (.target.bash, "/sbin/portmap") ); } - if (!(boolean)SCR::Execute(.target.mount, [ Host + ":" + dirname(Path), mount_point ], "-o nolock" ) && + string mountcmd = "/bin/mount " + Host + ":" + dirname(Path) + " " + mount_point + " -o nolock"; + y2milestone("mountcmd: %1", mountcmd); + + if ((WFM::Execute (.local.bash, mountcmd ) !=0 ) && !(boolean)SCR::Execute(.target.mount, [ Host + ":" + dirname(Path), mount_point ], "-t nfs4" ) ) { y2warning("Mount failed"); -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c1 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com AssignedTo|fehr@suse.com |lslezak@suse.com --- Comment #1 from Thomas Fehr <fehr@suse.com> 2013-07-15 13:33:35 UTC --- Problem is that inst_kickoff.ycp does switch of loading of dependant modules via /bin/echo "/etc/nothing" >/proc/sys/kernel/modprobe This breaks capability of mounting nfs version 3 (since nfsv3.ko is dependent on nfs_acl.ko) Since the reasons for adding this were long time ago (bnc#20627 and should be obsolete meanwhile since it was moved to start of package install with bnc#172149 anyway) I would suggest to simply remove this code from inst_kickoff.ycp. Reassigned to appropriate maintainer. -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c2 Ladislav Slezak <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED --- Comment #2 from Ladislav Slezak <lslezak@suse.com> 2013-07-15 14:24:36 UTC --- Fixed in yast2-packager-2.24.1 (https://github.com/yast/yast-packager/pull/14) -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c3 --- Comment #3 from Thomas Fehr <fehr@suse.com> 2013-07-15 14:59:47 UTC --- This problem is also in SLES 11 code base, so we need to be aware of possible upcoming L3 requests. But since the problem was also present in previous SLES releases, it seems it does not happen too often. -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c4 --- Comment #4 from Ladislav Slezak <lslezak@suse.com> 2013-07-15 15:21:38 UTC --- Thomas, is possible to work around it by some AutoYast script? I mean is it possible to write the proper value into /proc/sys/kernel/modprobe after inst_kickoff.ycp is finished? -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c5 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@suse.com AssignedTo|lslezak@suse.com |fehr@suse.com --- Comment #5 from Thomas Fehr <fehr@suse.com> 2013-07-15 15:42:02 UTC --- Of course one could simply fetch scripts via schemes http or ftp instead of nfs. But if one insists for some reasons to use nfs as source for his scripts it would be tricky. pre-scripts and post-partitioning scripts run too early. init-scripts run too late. On could add a chroot script with in placed code in xml file at start of chroot-scripts list like this: <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">false</chrooted> <source><![CDATA[ echo "/sbin/modprobe" > /proc/sys/kernel/modprobe ]]></source> </script> <script> other scripts using nfs as URL scheme </script> </chroot-scripts> This should fix module autoloading (did not try that yet) But since the problem exists since at least SLES11 lifetime and was not reported yet it either does not hit too many customers or they silently use ftp or http when having trouble with nfs. Note that if one installs via nfs or gets autoyast.xml via nfs, the problem does also not show up since before package install autoloading works and if modules are already loaded later nfs mount works too. While verifying the fix, I ran into another problem with nfs scripts in chroot environment that seems unrelated to nfs mount problem. I will have another look and reassign the bug back to me. -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c6 --- Comment #6 from Sebastian Herbszt <sebastian.herbszt@tfa.verwalt-berlin.de> 2013-07-15 15:57:08 UTC --- (In reply to comment #2)
Fixed in yast2-packager-2.24.1 (https://github.com/yast/yast-packager/pull/14)
I tried to verify this fix in SLES 11 SP3 with a custom DUD, but the problem still persists. -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c7 --- Comment #7 from Sebastian Herbszt <sebastian.herbszt@tfa.verwalt-berlin.de> 2013-07-15 16:02:27 UTC --- (In reply to comment #5)
Note that if one installs via nfs or gets autoyast.xml via nfs, the problem does also not show up since before package install autoloading works and if modules are already loaded later nfs mount works too.
We actually hit this problem while installing via nfs and getting our autoyast profile via nfs: install=nfs://10.16.77.245/export/os/SLES11-SP3/iso/SLES-11-SP3-DVD-x86_64-GM-DVD1.iso autoyast=nfs://10.16.77.245/export/os/SLES11/autoyast/profiles/U1160005.xml -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c8 --- Comment #8 from Thomas Fehr <fehr@suse.com> 2013-07-15 16:09:30 UTC --- Yes, I am currently investigating this second problem. I ran into failing nfs mount (which quite clearly could be attributed to disabled module autoload) while trying to reproduce the problem here and assumed this is the only problem. It seems it is not... -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c9 --- Comment #9 from Sebastian Herbszt <sebastian.herbszt@tfa.verwalt-berlin.de> 2013-07-15 17:02:37 UTC --- Our workaround in comment #0 partially reverts the fix for bug 329791. That commit ("fetching profile from NFS fixed (#329791). 2.16.0") changed "WFM::Execute" to "SCR::Execute". -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c10 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #10 from Thomas Fehr <fehr@suse.com> 2013-07-16 13:42:39 UTC --- And as far as I see chroot scripts with "chrooted=true" via nfs (and cifs) since the above mentioned fix. I have now a hopefully final fix. It works fine in my test cases (where the original problem was visible). It would be helpful if you could test the attached dud with 13.1. -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c11 --- Comment #11 from Thomas Fehr <fehr@suse.com> 2013-07-16 13:43:44 UTC --- Created an attachment (id=548185) --> (http://bugzilla.novell.com/attachment.cgi?id=548185) dud to fix the bug in openSuSE 13.1 -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c12 --- Comment #12 from Thomas Fehr <fehr@suse.com> 2013-07-16 14:37:38 UTC --- Created an attachment (id=548197) --> (http://bugzilla.novell.com/attachment.cgi?id=548197) dud for SLE11 SP3 -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c13 --- Comment #13 from Sebastian Herbszt <sebastian.herbszt@tfa.verwalt-berlin.de> 2013-07-17 13:25:06 UTC --- We tested the DUD for SLES 11 SP3 and the problem seems fixed. -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:56530:low -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c15 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:56530:low |maint:running:56530:low | |maint:released:sle11-sp3:56 | |542 --- Comment #15 from Swamp Workflow Management <swamp@suse.de> 2014-04-29 15:51:56 UTC --- Update released for: autoyast2, autoyast2-installation Products: SLE-DEBUGINFO 11-SP3 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP3 (i386, x86_64) SLE-SERVER 11-SP3 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP3 (i386, x86_64) -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c16 --- Comment #16 from Swamp Workflow Management <swamp@suse.de> 2014-04-29 19:04:24 UTC --- SUSE-RU-2014:0579-1: An update that has 5 recommended fixes can now be installed. Category: recommended (low) Bug References: 829265,830253,836366,852617,864421 CVE References: Sources used: SUSE Linux Enterprise Server 11 SP3 for VMware (src): autoyast2-2.17.73-0.7.1 SUSE Linux Enterprise Server 11 SP3 (src): autoyast2-2.17.73-0.7.1 SUSE Linux Enterprise Desktop 11 SP3 (src): autoyast2-2.17.73-0.7.1 -- 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=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:56530:low |maint:released:sle11-sp3:56 |maint:released:sle11-sp3:56 |542 |542 | -- 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.
participants (1)
-
bugzilla_noreply＠novell.com