[QUOTE=GÃÂ¼nther Schwarz;13899]jmozdzen wrote:
Thank you very much for the instant reply to my post.
[/COLOR]> are you positive that routing, DNS etc were not taken from the other
autoyast file, too?[/COLOR]
No, these parts are the same for the old and the new file and were taken
without modifications. I did alter the parameters for the network
interfaces, MAC addresses, and hostnames inserting the values for the
Set up of routing and DNS as well as hostnames does work. It is just the
interfaces that are missing in /etc/sysconfig/network.[…]
Is the “autoinstall.xml file of a previous installation” still
accessible on 192.168.40.141? Would you mind moving it out of the way
temporarily? Did it have the same name as the one you’re trying now (I’m
thinking about some caching somewhere)?[/COLOR]
No, this won’t be accessible on the web server.
[/COLOR][COLOR=blue]> Hm, thinking about what else could go wrong… is that “old” file
available on the machine to be installed, as a left-over from an old
No, definitely not.
Might it then be possible that the installation process tries
to retrieve the “new” autoyast file, fails, and instead of bailing out,
continues with the former file?[/COLOR]
As an example, the new hostname is the right one. So this is very
From your description, I fully agree that access to the wrong autoyast file should not be the root cause. Would have been too easy a solution
[QUOTE=GÃÂ¼nther Schwarz;13899]I have the y2log, but this is hard to read and might be too
big for publishing here.
Some lines that might be of interest:
2013-06-05 11:31:59 <1> linux(8278) [YCP]
clients/inst_autoconfigure.ycp:50 removing installation network:
So it correctly removes the temporary network setup used for installation.
It seems to read the network configuration correctly from the file:
2013-06-05 11:31:46 <1> linux(8278) [YCP] NetworkInterfaces.ycp:1492
List( ) = [“eth0”, “eth1”]
I do find error messages related to eth1:
2013-06-05 11:32:10 <3> test5(8278) [bash]
ShellCommand.cc(shellcommand):78 cat: /sys/class/net/eth1/carrier: Das
Argument ist ungÃÂ¼ltig
2013-06-05 11:32:10 <1> test5(8278) [YCP] NetworkInterfaces.ycp:384
Sysfs returned $[“exit”:1, “stderr”:“cat: /sys/class/net/eth1/carrier:
Das Argument ist
2013-06-05 11:32:10 <1> test5(8278) [YCP] NovellUtils.ycp:206
NovellUtils.GetAllStaticInterfaces:current device is: eth1, active
status is false[/QUOTE]
Those error messages make me believe that that interface eth1 was taken down (not only removing the config file) or for some reason, eth1 could not be associated with the parameters you specified in the autoyast file. The only irregularity I could see is that you have “eth1” twice in your autoyast file, it might be worth a test to correct that.
[QUOTE=GÃÂ¼nther Schwarz;13899]What might be unusual is that the automatic installation is done via
eth1 which is part of a management subnet without a gateway, and is also
not the first network device. But for the installation process this
should not be relevant.[/QUOTE]
Yes, I’d expect the same.
If it works with only eth0 in the autoyast file, then fixing the duplicate node is worth a try for sure.
Regards, & good luck