Hi Spike, Thanks a lot for sharing this, it's comforting to know that the issue has been observed other places. But I have to say it's also a bit unsettling to learn that it occurred *within* Dell and still had made its way to Dell's customers... And thanks for the much easier reproducer.
Soorej, could you please give Spike's example a try? Our kickstart infrastructure is quite involved and tied to many site-specific things that will make it quite difficult to export to try in a different environment. Also, I'm not sure what you mean by "creating the iso". We're not creating any ISO, we're just deploying servers, and would like to be able to upgrade their firmwares in a single pass while they're being deployed. Hence our wish to use "dsu -n" in the %post section of a kickstart file. Cheers, -- Kilian On Tue, May 23, 2017 at 9:00 AM, <[email protected]> wrote: > Dell - Internal Use - Confidential > > Killian, > > > > I work in Dell I/T, so my team is a consumer of dsu – like you. I believe > this is very much related to a similar ‘dsu –n’ situation my team has > experienced. > > > > And it’s probably easier to reproduce than having to re-kickstart a server > every time. > > > > We have implemented a “firstboot” utility in our /etc/rc.local code. Like > so: > > # firstboot utility > > for script in `ls /etc/rc.d/init.d/firstboot.d/*` > > do > > echo "Executing script at $script" > > nohup $script >> /var/log/firstboot.log 2>&1 && rm $script > > sleep 10 > > done > > > > The intent is if you wish to execute something not now, but on next reboot – > you drop a little scriptlet in /etc/rc.d/init.d/firstboot.d/ dir. And it > gets executed on next reboot. And then deleted, so it gets executed only on > next reboot. > > > > Mainly we use this in our initial post-build customizations. For those 1-2 > specific activities that we can’t perform on the install media’s kernel. > > > > Anyway, we have noticed that if we drop down a “firstboot” scriptlet that > does ‘dsu –n’, it doesn’t do any flashing. Whereas, in a regular > environment ‘dsu –n’ flashes fine. > > > > We never were able to identify why. Whether it was due to not having a > controlling TTY, or what. Ultimately, we went another away. So at this > point, it’s a curiosity item only – I’d forgotten until you mentioned it. > > > > Spike White > > Dell I/T > > > > > > Date: Sat, 20 May 2017 22:46:22 -0700 > > From: Kilian Cavalotti <[email protected]> > > Subject: Re: [Linux-PowerEdge] DSU replaces '-n' option with '-p' > > To: Patrick Boutilier <[email protected]> > > Cc: [email protected] > > Message-ID: > > > <CAJz=vjhfgzrt8yo6gtwcyp6zsk-qipx0+23y6vcmwfippvx...@mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > Thanks for the suggestion. "dsu -n" actually applies the updates when run > > in a regular environment, outside of the Kickstart file. > > > > > > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > -- Kilian _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
