Comment 28 for bug 694772

I believe there's a bug open for the lack of state transfer? If not,
we could repurpose this one?

That being said, we should remember that state transfer should *not*
be invoked by SIGTERM - so maybe it's worth keeping this one open to
remind us of that.

Scott

On Fri, Feb 4, 2011 at 4:42 PM, Clint Byrum <email address hidden> wrote:
> I'm failing to see where the "bug" in upstart is for this. telinit u
> sends SIGTERM to pid 1 blindly, which probably isn't the safest thing,
> but we can avoid doing that fairly easily.
>
> So, since the way forward to allow upstart to re-execute itself without
> losing state is not clear, I think this one should probably be closed as
> Won't Fix.
>
> Opinions?
>
> --
> You received this bug notification because you are a member of Upstart
> Developers, which is subscribed to upstart .
> https://bugs.launchpad.net/bugs/694772
>
> Title:
>  Sudden reboot during server ISO install
>
> Status in Ubuntu Studio:
>  Confirmed
> Status in Upstart:
>  New
> Status in “eglibc” package in Ubuntu:
>  Fix Released
> Status in “upstart” package in Ubuntu:
>  New
> Status in “eglibc” source package in Lucid:
>  Fix Released
> Status in “upstart” source package in Lucid:
>  New
> Status in “eglibc” source package in Maverick:
>  Fix Released
> Status in “upstart” source package in Maverick:
>  New
> Status in “eglibc” package in Debian:
>  New
>
> Bug description:
>  Binary package hint: debian-installer
>
>  I am not sure which package is the affected one, but since it affects
>  the install of the server, I am opening against d-i. I started
>  experiencing this last week at around Dec 23/24th.
>
>  Repeated with ISOs from Dec 24th to Dec 27th.
>
>  I experienced it under both a bare-metal install and a libvirt install
>  (under Natty), both under preseeded and manual installs.
>
>  Installation proceeds nicely until we get to the point of installing
>  the base system. Then, suddenly, I see a "rebooting" message flash on
>  the screen, and system does indeed reboot. Since there is no kernel
>  installed, at this point, the system hangs.
>
>  I am marking this as critical -- no tests can be performed.
>
>  I am unsure on how to collect data here, since the installer logs are
>  lost.
>
>  LAST ISO TESTED: 20101230. reboot happens on 'extracting libpcreg...'
>
>
>