Re: SUSE-12.3 weirdness

I have posted a fix/workaround for the hang you report at 
https://bugzilla.novell.com/show_bug.cgi?id=801878#c9

You could try to provide the patched file using the <files> section. I 
cannot guarantee that this works though... I personally built an updated 
yast2 package on OBS containing the patch and it works for me so far.

Best regards,
-Joschi


On 03/18/2013 04:10 PM, Lonni J Friedman wrote:
> On Mon, Mar 18, 2013 at 3:49 AM, Thomas Fehr <[email protected]> wrote:
>> On Fri, Mar 15, Lonni J Friedman wrote:
>>
>>> I'm trying to get autoyast working with OpenSUSE-12.3.  The actual OS
>>> installation seems to work fine, but after the reboot (when it does a
>>> bunch of post-install stuff), its consistently hanging at:
>>> Preparing System for Automatic Instlallation
>>> Install required packages
>>> Checking for packages required for runlevel ---> 33%
>>>
>>> Or more accurately, it just stalls.  The system isn't hung, I can
>>> switch between virtual consoles, but the actual installation never
>>> progresses at all.  Load is 0.00.
>>>
>>> I started poking around in the newest log in /var/log/Yast2, and I see
>>> the following at the bottom of y2log:
>>>
>>> It seems like maybe its unhappy about something related to the
>>> runlevel?  My autoyast.xml has the following:
>>> #########
>>> <configure>
>>>          <runlevel>
>>>             <default>3</default>
>>>          </runlevel>
>>> #########
>>>
>>> Is this no longer supported?  The last version of the documentation
>>> seems to suggest that its still valid:
>>> http://users.suse.com/~ug/autoyast_doc/configuration.html#CreateProfile.Services
>>
>> This looks like you hit bug 801878 of bugzilla.novell.com. One of a lot
>> of fallout caused by systemd integration. Unfortiunatley it is not fixed
>> in time for 12.3 release.
>>
>
> Thanks for your reply.  Yes, that's definitely the bug (
> https://bugzilla.novell.com/show_bug.cgi?id=801878 ).  I hate systemd.
>   Yet another solution in search of a problem.
>
> I guess I'll just have to hack up some alternative mechanism for
> enforcing the runlevel.
>