AutoYaST network configuration broken by updates

SUSE Linux Enterprise Server SLES Install-Boot
1

Hello,

configuring network settings in an AutoYaST profile does not work anymore for SLES-12.
It worked for SLES11-SP3 for years and for SLES-12 with patches up to Aug. 10 2015.
It stopped working when appying updates at Sep. 16 2015. I did no tests with intermediate
patch levels. With the today patches applied, it does still not work!

To reproduce the behaviour, make an installation with the following profile and see,
/etc/sysconfig/network/ifcfg-eth1 and -eth2 are missing, and the interfaces are not
configured (ip a). ethtool shows “link detected” for all interfaces (kvm on SLES-12).

<?xml version="1.0" encoding="utf8"?> dhcp eth0 auto no dhcp eth1 auto no static eth2 auto no 192.168.123.5 255.255.255.128 head.de autoyast-test false false false linux root

Regards,
Oliver

2

osw2,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

3

I have created a service request on that topic: SR #10975582701

4

On 28/10/2015 12:04, osw2 wrote:
[color=blue]

I have created a service request on that topic: SR #10975582701[/color]

That would seem to be your best option. Perhaps you can update this
thread when you have an answer? I’ll also try asking someone next week
during SUSECon.

Thanks.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

5

Seeing the same problem here, along with some other bugs concerning connecting to the registration server and repositories. I use ask dialogs to enter the network information, but that is probably irrelevant.
Hope you update the thread when you get a response to your SR.

6

As far as I know ask-dialogs just modify “/tmp/profile/modified.xml”, so I also suppose that’s not relevant. I will post here, when there is a valuable response.

7

The bug is fixed in yast2-network-3.1.112.10-2.19.1.x86_64.rpm, which mentions 2 bugs related to
AutoYaST2 and networking. It is available since Nov. 5th.
Sadly support just said “It works fine for me”, but at least it led me to check the update channel.
Wish I had access to the bug database…

So long,
Oliver

8

On 12/11/2015 15:44, osw2 wrote:
[color=blue]

The bug is fixed in yast2-network-3.1.112.10-2.19.1.x86_64.rpm, which
mentions 2 bugs related to
AutoYaST2 and networking. It is available since Nov. 5th.
Sadly support just said “It works fine for me”, but at least it led me
to check the update channel.
Wish I had access to the bug database…[/color]

Thanks for taking the time to update this thread.

Whilst you may not have access to the bug database you do have access to
the RPM’s own changelog (via “rpm -q --changelog ”) but
unfortunately on this occasion it doesn’t appear to have been updated
(which seems odd so I’ll report to my contacts).

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.