Hi,
location worked form e in SLES12-GA. Bug or Feature was introduced in SLES12-SP1. Workaround: embed the desired Script in xml (CDATA).
Regards
Frank Hollmann
-----Ursprüngliche Nachricht-----
Von: Aleksandar Vesic [mailto:vesic@linux.com]
Gesendet: Dienstag, 12. Juli 2016 16:27
An: opensuse-autoinstall(a)opensuse.org
Betreff: [opensuse-autoinstall] Autoyast init-script files fail to download
Hello guys,
I tried to install SLES12SP1 but my init-script get ignored
and no file gets created at /var/adm/autoinstall/scripts. Same autoyast
profile worked for SLES 11 SP4. My post-scripts works fine.
An autoyast control file for SLES 12 SP1 with the following init-scripts
section fails:
<init-scripts config:type="list">
<script>
<filename>init12.sh</filename>
<interpreter>shell</interpreter>
<location>nfs://IP_ADDR/var/lib/autoinstall/repository/scripts
/init12.sh</location>
</script>
Same with:
<location><![CDATA[
nfs://IP_ADDR/var/lib/autoinstall/repository/scripts/init12.sh
]]></location>
After installation, this script has been executed only if I use
following section:
<source><![CDATA[
#!/bin/sh
#The entire content of the init12.sh
]]>
</source>
</script>
</init-scripts>
</scripts>
I looked into /usr/share/YaST2/clients/autoinst_scripts2_finish.rb
and found this:
# Creating init scripts for the autoyast-initscripts.service
AutoinstScripts.Write("init-scripts", false)
# systemd requires the init script to be activated in 1st stage
Can someone help me? Did I miss something?
Best Regards
Alex
----------------------
vesic(a)linux.com
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello guys,
I tried to install SLES12SP1 but my init-script get ignored
and no file gets created at /var/adm/autoinstall/scripts. Same autoyast
profile worked for SLES 11 SP4. My post-scripts works fine.
An autoyast control file for SLES 12 SP1 with the following init-scripts
section fails:
<init-scripts config:type="list">
<script>
<filename>init12.sh</filename>
<interpreter>shell</interpreter>
<location>nfs://IP_ADDR/var/lib/autoinstall/repository/scripts
/init12.sh</location>
</script>
Same with:
<location><![CDATA[
nfs://IP_ADDR/var/lib/autoinstall/repository/scripts/init12.sh
]]></location>
After installation, this script has been executed only if I use
following section:
<source><![CDATA[
#!/bin/sh
#The entire content of the init12.sh
]]>
</source>
</script>
</init-scripts>
</scripts>
I looked into /usr/share/YaST2/clients/autoinst_scripts2_finish.rb
and found this:
# Creating init scripts for the autoyast-initscripts.service
AutoinstScripts.Write("init-scripts", false)
# systemd requires the init script to be activated in 1st stage
Can someone help me? Did I miss something?
Best Regards
Alex
----------------------
vesic(a)linux.com
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello,
we have successfully installed a opensuse 12.3 with autoyast.
The System contains 3 md-raid-sets, all are a raid1.
When I try to install the same system again, I get an error message
Failure occurred during the following action:
Setting disk label of /dev/sda to MSDOS
System error code was: -1013
Continue despite the error?
Here the complete messages from y2log:
--------------------------------------------------------
2016-07-11 13:00:42 <1> dh136(3694) [libstorage]
SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mdadm
--zero-superblock --force '/dev/sda'"
2016-07-11 13:00:42 <1> dh136(3694) [libstorage]
SystemCmd.cc(addLine):592 Adding Line 1 "mdadm: Unrecognised md
component device - /dev/sda"
2016-07-11 13:00:42 <1> dh136(3694) [libstorage]
SystemCmd.cc(getUntilEOF):558 pid:4675 added lines:1 stderr:true
2016-07-11 13:00:42 <1> dh136(3694) [libstorage]
SystemCmd.cc(doExecute):279 stopwatch 0.008789s for "/sbin/mdadm
--zero-superblock --force '/dev/sda'"
2016-07-11 13:00:42 <1> dh136(3694) [libstorage]
SystemCmd.cc(doExecute):299 system() Returns:0
2016-07-11 13:00:42 <3> dh136(3694) [libstorage]
Disk.cc(checkSystemError):417 cmd:/sbin/mdadm --zero-superblock --force
'/dev/sda'
2016-07-11 13:00:42 <3> dh136(3694) [libstorage]
Disk.cc(checkSystemError):418 err:mdadm: Unrecognised md component
device - /dev/sda
2016-07-11 13:00:42 <1> dh136(3694) [libstorage]
SystemCmd.cc(execute):90 SystemCmd Executing:"/usr/sbin/parted -s
'/dev/sda' mklabel msdos"
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
SystemCmd.cc(addLine):592 Adding Line 1 "Error: Partition(s) 2 on
/dev/sda have been written, but we have been unable to inform the kernel
of the change, probably because it/they are in use. As a result, the
old partition(s) will remain in use. You should reboot now before
making further changes."
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
SystemCmd.cc(getUntilEOF):558 pid:4676 added lines:1 stderr:false
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
SystemCmd.cc(doExecute):279 stopwatch 2.151067s for "/usr/sbin/parted -s
'/dev/sda' mklabel msdos"
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
SystemCmd.cc(doExecute):299 system() Returns:1
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
SystemCmd.cc(logOutput):625 stdout:Error: Partition(s) 2 on /dev/sda
have been written, but we have been unable to inform the kernel of the
change, probably because it/they are in use. As a result, the old
partition(s) will remain in use. You should reboot now before making
further changes.
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
Disk.cc(checkSystemError):423 cmd:/usr/sbin/parted -s '/dev/sda' mklabel
msdos
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
Disk.cc(checkSystemError):424 out:Error: Partition(s) 2 on /dev/sda have
been written, but we have been unable to inform the kernel of the
change, probably because it/they are in use. As a result, the old
partition(s) will remain in use. You should reboot now before making
further changes.
2016-07-11 13:00:44 <3> dh136(3694) [libstorage]
Disk.cc(checkSystemError):445 retcode:1
2016-07-11 13:00:44 <2> dh136(3694) [libstorage]
Container.cc(setExtError):366 called with empty stderr
cmd:/usr/sbin/parted -s '/dev/sda' mklabel msdos
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
Disk.cc(doCreateLabel):1654 ret:-1013
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
Disk.cc(commitChanges):1574 ret:-1013
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
Storage.cc(commitPair):5236 err at stage:0 type:DISK cont:true
dest:false name:sda
2016-07-11 13:00:44 <1> dh136(3694) [libstorage]
Storage.cc(commitErrorPopupCb):6626 COMMIT ERROR POPUP error:-1013
last_action:Setting disk label of /dev/sda to MSDOS extended_message:
2016-07-11 13:00:44 <1> dh136(3694) [YCP] StorageClients.ycp:111
CommitErrorPopup error:-1013 last_action:Setting disk label of /dev/sda
to MSDOS extended_message:
2016-07-11 13:00:44 <1> dh136(3694) [YCP] Report.ycp:370 Failure
occurred during the following action:
Setting disk label of /dev/sda to MSDOS
System error code was: -1013
Continue despite the error?
--------------------------------------------------------------------
Any hints?
Regards
Daniel
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org