Re: State of Autoyast for OpenSUSE 13.1

Thank you so much for the info!

In the mentioned BNC 846011, there is a DUD provided that is supposed to 
fix the problem.

Unfortunately, I can *NOT* confirm that the DUD fixes the problem. I can 
see it gets fetched at the very start of AutoYast, but then everything 
is then same.

Should there be any sign of the DUD in y2log(-1) ? Because there is 
nothing there...



On 01/30/2014 11:26 AM, 686f6c6d wrote:
> On Thu, Jan 30, 2014 at 10:40 AM, Joschi Brauchle
> <[email protected]> wrote:
>> Is this a known problem? Or are there known problems for 13.1?
>
> This is a known bug (BNC# below), it was discussed on this ML a few
> weeks back. You need to remove your <add-on> section completely.
>
> It is "fixed" already, but fixed in the case of AutoYAST sadly always
> means "only fixed in the next release", even for crippling bugs like
> this, that affects every single user. For that particular problem I'm
> using the following <post-script>:
>
> ---------- 8< ----------
>        <!-- workaround for BNC#846011 (fixed for 13.2 since ~2014-01-26) -->
>        <script>
>          <network_needed config:type="boolean">true</network_needed>
>          <filename>post-manual-repos</filename>
>          <interpreter>shell</interpreter>
>          <source><![CDATA[#!/bin/bash
> # doesn't work in pre: read-only fs.
>
> # install repo is added by install= cmdline param.
>
> echo "[suse_update]
> name=SUSE updates (13.1)
> enabled=1
> autorefresh=1
> baseurl=http://repohost/suse/update/13.1/
> type=rpm-md
> gpgcheck=1
> gpgkey=http://repohost/suse/update/13.1/repodata/repomd.xml.key" >>
> /etc/zypp/repos.d/update.repo
>
> echo "[something_stable]
> name=something (13.1)
> enabled=1
> autorefresh=1
> baseurl=http://repohost/acmecorp/something:/stable/openSUSE_13.1/
> type=rpm-md
> gpgcheck=1
> gpgkey=http://repohost/acmecorp/something:/stable/openSUSE_13.1/repodata/repomd.xml.key"
>>> /etc/zypp/repos.d/something.repo
> ]]></source>
>        </script>
> ---------- >8 ----------
>
>
> I don't remember any new problems in 13.1 from the top of my head
> right now (maybe the problem with empty resolv.conf I had in 12.x now
> happens in an earlier stage, not sure). Will post if I find something,
> our profiles are quite huge nowaways.
>
>

-- 
Dipl.-Ing. Joschi Brauchle, M.S.

Institute for Communications Engineering (LNT)
Technische Universitaet Muenchen (TUM)
80290 Munich, Germany

Tel (work): +49 89 289-23474
Fax (work): +49 89 289-23490
E-mail: [email protected]
Web: http://www.lnt.ei.tum.de/