[opensuse-autoinstall] Re: [suse-autoinstall] SuSE 10.2 problems
On 12/7/06, Lonni J Friedman <netllama@gmail.com> wrote:
On 12/7/06, Uwe Gansert <ug@suse.de> wrote:
On Wednesday 06 December 2006 19:20, Lonni J Friedman wrote:
I have to ask. Why is autoyast being reinvented from scratch with every single release? Every single release has non-trivial changes which lead to non-ending pain &
Since 10.0 (and that was the release I took over autoyast) there was just one incompatibility (selections -> patterns). Everything else should be still compatible. The change from DTD to RNG is no icompatibility. It does not matter for your profile if RNG files are used or DTD files are used to check the syntax.
suffering. Is it too much to expect that a working autoyast.xml from one release continue to work, or at least not fail fatally, in the next release?
no, it's not. If you detect such an incompatibility that is not documented by me, feel free to open a bugreport or ask here on the list. I don't know a lot about autoyast in the pre 10.0 time but I try to keep compatibility as high as possible. I'm sorry if you had compatibility issues in the past but for the future, let me know if you have such problems. And let me know as soon as you discover such a problem please.
I just went to setup 10.2 using the autoyast file that works for SLED10, and it blew up with bad/invalid patterns. Amongst other things, basis-devel seems to have been renamed devel_basis, and kernel-devel was renamed devel_kernel.
This is the stuff i'm referring to. I shouldn't have to update the pattern names every time there's a new release.
Sadly, there are more problems. After fixing my autoyast.xml file, now the installation bombs out much earlier (which admittedly suggests that I did something wrong). Now I just got prompted to "Make sure that CD number 1i s in your drive". On Alt-F3, I see a bunch of modules getting insmodded, and then: Looking for a openSUSE CD... disk: trying to mount /dev/hda disk: /dev/hda: not a openSUSE install medium Automatic setup not possible I've got an info and autoyast.xml files inside the initrd. Thinking perhaps that support had changed such that yast now assumes that the install 'media' is always going to be in the same place as the autoyast.xml file, I tried putting the autoyast.xml file on the web server where the SuSE-10.2 installation tree is located. I added autoyast=http:/server/path/to/autoyast.xml to the append line on my pxeboot server, and now I get a completely different failure. The installer attempts to get a dhcp lease, and fails nearly instantaneously (it waits perhaps 2 seconds at most): Looking for anetwork server... Trying to activate eth0 Setting up localhost..done Sending DHCP request to eth0... no/incomplete answer. Automatic setup not possible At which point I get dumped to the manual installation dialogue, where I have no problems getting a dhcp lease and performing the installation over the network without any problems. Something is broken somewhere. It might be user error, but the fact that just dropping in an autoyast.xml from an older version doesn't work seems like a pretty huge regression. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@gmail.com LlamaLand http://netllama.linux-sxs.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Friday 08 December 2006 00:18, Lonni J Friedman wrote:
Sadly, there are more problems. After fixing my autoyast.xml file, now the installation bombs out much earlier (which admittedly suggests that I did something wrong). Now I just got prompted to "Make sure that CD number 1i s in your drive".
okay but then autoyast did not even start. The installation fails before one line of autoyast code has been executed now.
I've got an info and autoyast.xml files inside the initrd.
did you change any ownerships in the initrd? It's important that it all still belongs to root.
Thinking perhaps that support had changed such that yast now assumes that the install 'media' is always going to be in the same place as the autoyast.xml file,
that's not the case
server where the SuSE-10.2 installation tree is located. I added autoyast=http:/server/path/to/autoyast.xml to the append line on my pxeboot server, and now I get a completely different failure. The installer attempts to get a dhcp lease, and fails nearly
that's strange but of course not an autoyast failure.
Something is broken somewhere. It might be user error, but the fact that just dropping in an autoyast.xml from an older version doesn't work seems like a pretty huge regression.
autoyast was not even able to read the profile. Autoyast was not executed. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On 12/8/06, Uwe Gansert <ug@suse.de> wrote:
On Friday 08 December 2006 00:18, Lonni J Friedman wrote:
Sadly, there are more problems. After fixing my autoyast.xml file, now the installation bombs out much earlier (which admittedly suggests that I did something wrong). Now I just got prompted to "Make sure that CD number 1i s in your drive".
okay but then autoyast did not even start. The installation fails before one line of autoyast code has been executed now.
I've got an info and autoyast.xml files inside the initrd.
did you change any ownerships in the initrd? It's important that it all still belongs to root.
It does all belong to root.
server where the SuSE-10.2 installation tree is located. I added autoyast=http:/server/path/to/autoyast.xml to the append line on my pxeboot server, and now I get a completely different failure. The installer attempts to get a dhcp lease, and fails nearly
that's strange but of course not an autoyast failure.
Turns out it wasn't failing to get a DHCP lease, it got one just fine. The error message was misleading and/or useless. The problem was that there's apparently no DNS resolution at this stage of the installation (or any?), and I was specifying the hostname of the server that hosted autoyast.xml & the install tree. So when the installer couldn't resolve the name of the server to an IP, it just bombed out with that cryptic error message. I should note that the autoyast FAQ refers to autoyast=http://myserver/myconfig.xml which leads one to believe that not using the IP address of the server in the URL is acceptable. Once I changed it to the IP, the installation proceeded much further. Now it gets all the way through installing all the packages (once I updated all the pattern names *sigh*), and then fails at 'Install boot manager' with the error: /sbin/mkinitrd: line 3036: /etc/fstab: No such file or directory No '/' mountpoint specififed in /etc/fstab I've attached the autoyast.xml that I'm using. I've uploaded the y2log here: http://netllama.linux-sxs.org/y2log.bz2 thanks. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@gmail.com LlamaLand http://netllama.linux-sxs.org
On Friday 08 December 2006 18:33, Lonni J Friedman wrote:
Turns out it wasn't failing to get a DHCP lease, it got one just fine. The error message was misleading and/or useless. The problem was that there's apparently no DNS resolution at this stage of the installation (or any?)
actually there is. How do you provide the nameserver information? DHCP or nameserver=.... parameter?
autoyast FAQ refers to autoyast=http://myserver/myconfig.xml which leads one to believe that not using the IP address of the server in the URL is acceptable.
it is.
Now it gets all the way through installing all the packages (once I updated all the pattern names *sigh*), and then fails at 'Install boot manager' with the error: /sbin/mkinitrd: line 3036: /etc/fstab: No such file or directory No '/' mountpoint specififed in /etc/fstab
you have an (old?) RAID over the whole sda disk. That confuses the storage part of the installation. Remove the old RAID by hand via: dmraid -E -r /dev/sda then it should work -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Assemblage 23 - Document -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Lonni J Friedman -
Uwe Gansert