[sles-beta] SLES12 x86_64 RC2 autoyast post-script zypper unusable, application locked by y2base

[Stefan Schubert]

Hi,
the normal way of installingadditional and customized packages in 
autoyast is defined
here: 
http://doc.opensuse.org/projects/autoyast/configuration.html#idm139795987981568

It seem that this way does not fit your requirements. OK, here is a 
really HACK.
Libzypp (which is used by zypper) just checks the file /var/run/zypp.pid 
in order
checking the lock. (which is blamed by zypper).
So you would only have to move this file to other position, call your 
zypper calls
and please move this file back after you have finished your zypper calls.
But as I have already said, this is REALLY a hack and should NOT be the 
normal way:-)

Greetings
Stefan Schubert


g155:/home/src/ISOs # cat /var/run/zypp.pid
13544
g155:/home/src/ISOs # ps aux|grep 13544
root     13544 14.6  5.9 878604 235540 pts/20  Sl+  12:40   0:10 
/usr/lib/YaST2/bin/y2base sw_single qt
root     14047  0.0  0.0   9264   928 pts/21   S+   12:41   0:00 grep 
--color=auto 13544



Am 27.08.2014 11:10, schrieb urs.frey at post.ch:
> Hi
> I am trying to install SLES12 x86_64 RC2 onto my testservers using 
> autoyast
> I have a bunch of package installations and configurations to do, 
> which are configured by puppet.
> During autoyast post-script phase zypper unfortunately is locked by 
> y2base process
> root       603     1  0 10:53 tty7     00:00:00 /bin/sh 
> /usr/lib/YaST2/startup/YaST2.Second-Stage
> root      4040   603  0 10:54 tty7     00:00:00 /bin/sh 
> /usr/lib/YaST2/startup/YaST2.call installation continue
> root      4742  4040 27 10:54 tty7     00:00:11 y2base installation 
> ("continue") ncurses
> root      7597  4742  0 10:54 tty7     00:00:00 [snapper.py] <defunct>
> root      9337  4742  0 10:54 tty7     00:00:00 y2base installation 
> ("continue") ncurses
> root      9338  9337  0 10:54 tty7     00:00:00 y2base installation 
> ("continue") ncurses
> root      9339  9338  0 10:54 tty7     00:00:00 sh -c /bin/sh -x 
> /var/adm/autoinstall/scripts/post-script.sh &> 
> /var/adm/autoinstall/logs/post-script.sh.log
> root      9340  9339  0 10:54 tty7     00:00:00 /bin/sh -x 
> /var/adm/autoinstall/scripts/post-script.sh
> root      9693  9340  0 10:54 tty7     00:00:00 ps -efww
> So when having a look at the processes together with y2base I quickly 
> get the intention, that the second stage of autoyast itself, showing 
> the ncurses screen is the y2base process. So killing of y2base would 
> not be a good idea to gain zypper access.
> So for me going back to RPM package installation to omit zypper 
> conflict within autoyast post-script is not an option.
> Moving the entire puppet configuration and OEM package installation to 
> autoyast init-script seems to be the only way.
> But autoyast init-script on the other hand does run in the background 
> while systemD  already opens the console login for root.
> Having console logins already enabled, while autoyast init-script is 
> still running is really not a good way.
> regards
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX     : ++41 (0)58 667 30 07
> E-Mail: _urs.frey at post.ch_ <mailto:urs.frey at post.ch>
>
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta


-- 
*******************************************************************************
Stefan Schubert
e-mail: schubi at suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany