No Response from any of the involved parties..
Setting to incomplete
Regards,
\sh
** Changed in: fai (Ubuntu)
Status: Triaged = Incomplete
** Changed in: xen-3.1 (Ubuntu)
Status: Opinion = Incomplete
** Changed in: fai (Ubuntu)
Status: Incomplete = Won't Fix
** Changed
I don't like to have this bug report left as incomplete and rott
somewhere in the deep dark space of LP trashbin ;)
If someone could test this with latest fai on ubuntu maverick or ubuntu
lucid, that would be a plus.
I*m, on the other hand, will raise this issue with upstream
** Changed in: fai
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of Ubuntu your using is in End of Life
status. More information may be found at:
https://wiki.ubuntu.com/Releases As well, fai (ubuntu) is updated and
issue you reported should be reproducible with the
I'm inclined to reject the bugtask for fai. It is true that fai is
affected by this, however it seems that the hypervisor is buggy here, so
there is not that much we can do about this from the fai side
** Changed in: fai (Ubuntu)
Assignee: Ubuntu FAI Developers (fai) = (unassigned)
--
dpkg
On Thu, Mar 27, 2008 at 10:42 AM, Reinhard Tartler [EMAIL PROTECTED] wrote:
I'm inclined to reject the bugtask for fai. It is true that fai is
affected by this, however it seems that the hypervisor is buggy here, so
there is not that much we can do about this from the fai side
It could be
Interestingly, here is the result of fai-setup -v on a Feisty xendomu.
It tried to continue past the error, and aborted in a different place
than Gutsy:
Setting up file (4.19-1ubuntu2) ...
Setting up cfengine2 (2.1.20-1) ...
Making a key pair for cfengine, please wait, this could take a
