Re: [opensuse-autoinstall] boolean values in ask scripts broken in SLES 11 SP1
On Mon, 2010-08-30 at 17:34 +0200, Uwe Gansert wrote:
on Thursday 26 August 2010 Andrew Daugherity wrote:
somewhere. Can this be fixed with a driver update?
I just noticed that you are using stage=cont. Then a driverupdate might not be the best way to fix that. I could send you a RPM if that helps you? You'd have to install that then via add-on for example. Would that be an option for you?
I think I'd need both then to truly fix this, although the second stage problem (registration) is the one I care about... let me see if I understand correctly: * to fix a problem in the first stage, I need a driver update * to fix something in the second stage (post-reboot), I need an updated RPM installed in the first stage? (As an aside, I guess this would be the way to fix the "keep_install_network loses DNS and routes bug" described at http://hedgehogpainter.livejournal.com/7022.html ?) Since you can't set repo priorities in autoyast (that I know of) would it pick up this package from my local YUM repo (instead of the one from sles11-sp1-pool) if it had a higher version? Thanks, -- Andrew Daugherity Systems Analyst Division of Research & Graduate Studies Texas A&M University -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Monday 30 August 2010 Andrew Daugherity wrote:
I think I'd need both then to truly fix this, although the second stage problem (registration) is the one I care about... let me see if I understand correctly: * to fix a problem in the first stage, I need a driver update * to fix something in the second stage (post-reboot), I need an updated RPM installed in the first stage?
yes, that's correct. There are possibilities, with a special driverupdate, to install a RPM for the second stage too with a DUD. So if you need a 1st stage fix anyway, I might build such a driverupdate
(As an aside, I guess this would be the way to fix the "keep_install_network loses DNS and routes bug" described at http://hedgehogpainter.livejournal.com/7022.html ?)
what do you mean? how is that connected to this issue?
Since you can't set repo priorities in autoyast (that I know of) would it pick up this package from my local YUM repo (instead of the one from sles11-sp1-pool) if it had a higher version?
yes, that should work -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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 Mon, 2010-08-30 at 18:03 +0200, Uwe Gansert wrote:
(As an aside, I guess this would be the way to fix the "keep_install_network loses DNS and routes bug" described at http://hedgehogpainter.livejournal.com/7022.html ?)
what do you mean? how is that connected to this issue?
It isn't, except that it could presumably be fixed in the same way, with
an updated RPM. An "aha!" moment if you will.
I wasn't sure how to fix that bug (your post-script linked from the
livejournal page is attached to a BNC bug marked private, so I can't
view it), so I ended up making separate profiles for each subnet with
gateway and DNS info hardcoded.
Despite the claim that is was fixed in SLES 11 SP1 it apparently isn't
-- a minimal network section with just keep_install_network works until
the network configuration runs in stage2 and then it drops the default
gateway and DNS servers, which breaks e.g. files retrieved from http.
I'm not really worried about that bug, as long as it gets fixed sometime
(hopefully by sp2). The vast majority of my installations can use DHCP
so it's not really a problem to hardcode the special cases.
Thanks for all your help.
--
Andrew Daugherity
Hi all,
I wasn't sure how to fix that bug (your post-script linked from the livejournal page is attached to a BNC bug marked private, so I can't view it)
Please find the XML snippet attached to this message. Merge it into <scripts> part of your profile. There's nothing really secret about it, so (unlike the bug itself) I think it can be made public. Maybe I should have embedded it into the original blogpost.
Despite the claim that is was fixed in SLES 11 SP1 it apparently isn't ... I'm not really worried about that bug, as long as it gets fixed sometime (hopefully by sp2).
Would you mind opening a new bug and attaching YaST logs from the failed installation to it? Otherwise "sometime" will mean "never". It's not technically possible to re-open the original bug and make it accessible to general public, so it has to be done via new bug. B. -- \\\\\ Katarina Machalkova \\\\\\\__o OOo developer __\\\\\\\'/_ & hedgehog painter
on Monday 30 August 2010 Andrew Daugherity wrote:
what do you mean? how is that connected to this issue?
It isn't, except that it could presumably be fixed in the same way, with an updated RPM. An "aha!" moment if you will.
okay, I see
I wasn't sure how to fix that bug (your post-script linked from the livejournal page is attached to a BNC bug marked private, so I can't view it),
I don't like that "secret SLES bugs" policy either :-/ Bubli was so kind to post the script to the list an hour ago. I've sent you a dud and I hope you can test it. All others can get it here too: http://www.suse.de/~ug/download/ it's for i586/x86_64 SLES11/SLED11 -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Shades" by mind.in.a.box -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Andrew Daugherity -
Katarina Machalkova -
Uwe Gansert