Ok - one last fix remains, and then we're done with this bug.
xen-3.3 3.3.0-1ubuntu7~hardy1 is currently in hardy-backports.
Backporting 3.3.0-1ubuntu7.1 from Intrepid to Hardy should be safe and
should fix the bug in backports.
** Summary changed:
- errors in xendomains init script
+ [hardy-bac
This bug was fixed in the package xen-3.3 - 3.3.0-1ubuntu7.1
---
xen-3.3 (3.3.0-1ubuntu7.1) intrepid-proposed; urgency=low
* debian/xen-utils-3.3.xendomains.init: fix cut bug (LP: #216761).
Patch by Carl Fooks
-- Evan BroderTue, 24 Feb 2009 16:32:43 -0500
** Changed in:
** Also affects: hardy-backports
Importance: Undecided
Status: New
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Tags added: verification-done
** Tags removed: verification-needed
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Well, I don't think many people are running Xen hosts on Intrepid, since
there isn't a dom0-capable kernel. However, I hacked a test VM together
using the Hardy kernel.
Since I'm already running in a VM, I can only do fairly limited testing,
but I was able to install a VM using xen-tools, boot it
Tom, this SRU is for xen-3.3 in intrepid right now. xen-3.3 does not
exist in hardy proper, so I take it you are using a backport.
Did anyone test the update in intrepid-proposed and can test whether it
still works, and also whether it fixes this bug? Thanks!
--
errors in xendomains init script
Can anybody tell me why this bug has occurred in the first place?
It was the fault of whom?
It must be very careful before you make changes in the system.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ub
This update has broken my Xen install on Ubuntu Server 8.04.2 with the
Ubuntu Xen 2.6.18 kernel.
I am no longer able to use the Xen tools to access my instances at the
console, shut them down, or start them up.
Is there a version mismatch? The update changelog has:
* debian/xen-utils-3.3.xendoma
I destroyed my instances and then created them again, and they seem to
be working fine again now.
But I had restarted the host system several times, which I thought also
restarted the guests!?
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notifi
Yeah, when I originally created the patch it was for Xen 3.3, and I
forgot to change it for the Xen 3.2 version of the patch. It's a typo,
but the package is actually for Xen 3.2
Are you sure you don't have hardy-backports turned on? If you let apt
install the libxen3 from hardy-backports, that wi
Oh, ok, good.
That's the point of the xendomains script - when you shutdown, it saves
the guests' current state to disk (/var/lib/xen/save, I think), and when
you startup, it restores any domains that are saved into that directory.
Before it would just shut them down because of the typo that the
Removed verification-done tag for initiating the xen-3.3 intrepid SRU.
** Tags removed: verification-done
** Changed in: xen-3.3 (Ubuntu Intrepid)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/
This bug was fixed in the package xen-3.2 - 3.2.0-0ubuntu10.1
---
xen-3.2 (3.2.0-0ubuntu10.1) hardy-proposed; urgency=low
* debian/xen-utils-3.3.xendomains.init: fix cut bug (LP: #216761)
Patch by Carl Fooks
-- Evan BroderMon, 15 Dec 2008 22:26:49 -0500
** Changed in: xe
** Tags added: verification-done
** Tags removed: verification-needed
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Martin, I've tested the version in hardy-proposed and can confirm that
it works for me (and didn't introduce any regressions on my system).
(Granted, I suspect that doesn't count for /too/ much since it is my
patch :-P, but there it is.)
--
errors in xendomains init script
https://bugs.launchpad
** Changed in: xen-3.3 (Ubuntu Intrepid)
Status: Fix Committed => In Progress
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks, upload sponsored.
** Changed in: xen-3.3 (Ubuntu Intrepid)
Status: Confirmed => Fix Committed
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Whoops - that patch was backwards. Let's try this one instead.
** Attachment added: "xen-3.3_3.3.0-1ubuntu7.1.debdiff"
http://launchpadlibrarian.net/23083113/xen-3.3_3.3.0-1ubuntu7.1.debdiff
** Description changed:
Binary package hint: xen-utils-3.2
The xendomains init script has a cou
Here's an updated version of the SRU for Intrepid with a corrected
version number
** Attachment added: "xen-3.3_3.3.0-1ubuntu7.1.debdiff"
http://launchpadlibrarian.net/23083056/xen-3.3_3.3.0-1ubuntu7.1.debdiff
** Description changed:
Binary package hint: xen-utils-3.2
The xendomains in
There's no xen in the intrepid-proposed queue.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Accepted xen-3.2 into hardy-proposed; please test and give feedback
here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: xen-3.2 (Ubuntu Hardy)
Status: Confirmed => Fix Committed
** Tags adde
Martin, both uploaded to -proposed.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Martin, both uploaded to -proposed.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Unsubscribing motu-sru team because the package is in main.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
This really should be fixed in Hardy, since Hardy is a LTS i think these
minor issues should be fixed!
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Looks fine for an SRU. Bryce, mind sponsoring those, too?
** Changed in: xen-3.3 (Ubuntu Hardy)
Status: New => Invalid
** Changed in: xen-3.3 (Ubuntu Intrepid)
Status: New => Confirmed
** Changed in: xen-3.2 (Ubuntu Jaunty)
Status: Confirmed => Invalid
** Changed in: xen-3.
I still believe that this bug is substantial enough that it qualifies
for an SRU to both Hardy and Intrepid.
Since 3.3.0-1ubuntu7 is the version in Intrepid,
xen-3.3_3.3.0-1ubuntu8.debdiff posted above should still be valid for
Intrepid.
I'm attaching xen-3.2_3.2.0-0ubuntu11.debdiff, which should
This bug was fixed in the package xen-3.3 - 3.3.0-1ubuntu8
---
xen-3.3 (3.3.0-1ubuntu8) jaunty; urgency=low
* debian/xen-utils-3.3.xendomains.init: fix cut bug (LP: #216761).
Patch by Carl Fooks
-- Evan BroderSat, 13 Dec 2008 12:35:28 -0500
** Changed in: xen-3.3 (Ubuntu
Thanks; sponsored!
** Changed in: xen-3.3 (Ubuntu Jaunty)
Status: New => Fix Committed
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment removed: "xen-3.3_3.3.0-1ubuntu8.debdiff"
http://launchpadlibrarian.net/20405420/xen-3.3_3.3.0-1ubuntu8.debdiff
** Attachment added: "xen-3.3_3.3.0-1ubuntu8.debdiff"
http://launchpadlibrarian.net/20406413/xen-3.3_3.3.0-1ubuntu8.debdiff
--
errors in xendomains init script
ht
I guess this should probably be fixed in Jaunty before I try to get an
SRU for Hardy.
I've attached the debdiff that fixes this problem in xen-utils-3.3 on
Jaunty.
** Attachment added: "xen-3.3_3.3.0-1ubuntu8.debdiff"
http://launchpadlibrarian.net/20405420/xen-3.3_3.3.0-1ubuntu8.debdiff
--
e
Patch works on Ubuntu 8.0.4.1 Please reassign to package maintainer to
include the fix.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
This bug still affects the xen-3.3-utils package in Jaunty
** Also affects: xen-3.3 (Ubuntu)
Importance: Undecided
Status: New
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
Binary package hint: xen-utils-3.2
The xendomains init script has a couple of errors.
- These errors cause the normal migrate then save then shutdown mechanisms
- to fail, and instead skip straight to the "shutdown all" stage, which is
- a major departure from the
** Description changed:
- The xendomains init script has a couple of errors, that while not fatal
- are annoying!
+ The xendomains init script has a couple of errors.
- I've attached a patch file to fix the two that were bothering me.
+ These errors cause the normal migrate then save then shutd
** Changed in: xen-3.2 (Ubuntu)
Status: New => Confirmed
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
If some of the configurable paths in /etc/default/xendomains contain
spaces, then the script fails. Like the previous patch, many of the $var
probably need to have double quotes around them. However, I'm no bash
expert either.
** Attachment added: "Fixes some problems with paths in /etc/default/xe
Just wanted to create a patch for this myself, but too late :-)
Did not net test this patch, however I confirm a bug fixed by it at line 186 in
xendomains script.
I vote for inclusion of this one, too.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this
Confirmed. Patch should be included.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Confirmed. Please include this patch in the release. Thanks.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Confirmed. Carl Fooks' patch works perfectly. Thanks.
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I noticed this too. I reported the change in the behavior of cut out of
concern that it would affect other scripts but this was the only case I
found.
https://bugs.launchpad.net/ubuntu/+source/xen-common/+bug/211262
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You
The specific errors, emitted during startup, were one to do with cut,
which was just a simple typo at line 186, in the parseln function, and
the second was the test at line 196 caused an error saying (something
like) "test: = unary operator expected. I simply wrapped that one in
quotes (not sure i
** Attachment added: "xendomains.patch"
http://launchpadlibrarian.net/13407539/xendomains.patch
--
errors in xendomains init script
https://bugs.launchpad.net/bugs/216761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
44 matches
Mail list logo
