Re: [Bug 1561434] Re: lxc-checkpoint failed on current newest version
On Thu, Mar 24, 2016 at 06:00:53PM -, Cui Wei wrote: > Just new I tried the updated CRIU: > > >> Linux Image Version: 4.4.0.15.16 > >> CRIU Version: 2.0-2ubuntu2 > >> LXC Version: 2.0.0~rc12-0ubuntu1 > > > The checkpoint step became success, but recovery step failed: > > + lxc-checkpoint -s -D /var/lib/lxc/cr-test/cp -n cr-test > > + lxc-checkpoint -r -D /var/lib/lxc/cr-test/cp -n cr-test > lxc-checkpoint: criu.c: do_restore: 683 criu process exited 1, output: > lxc-checkpoint: criu.c: do_restore: 631 Bad file descriptor - F_GETFD failed I believe this is fixed in rc13. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1561434 Title: lxc-checkpoint failed on current newest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1561434/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1561434] Re: lxc-checkpoint failed on current newest version
Can you please try the updated CRIU? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1561434 Title: lxc-checkpoint failed on current newest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1561434/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1561652] [NEW] init-system-helpers missing running-in-container
Public bug reported: This package used to have a useful script called running-in-container. Indeed, the bash missing binary scripts still think it does: root@criu:~# cat /etc/issue Ubuntu Xenial Xerus (development branch) \n \l root@criu:~# running-in-container The program 'running-in-container' is currently not installed. You can install it by typing: apt install init-system-helpers root@criu:~# apt install init-system-helpers Reading package lists... Done Building dependency tree Reading state information... Done init-system-helpers is already the newest version (1.29ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Can we get this script back? ** Affects: init-system-helpers (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1561652 Title: init-system-helpers missing running-in-container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1561652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1561434] Re: lxc-checkpoint failed on current newest version
Hi, What version of CRIU are you using? (`dpkg -l | grep criu`) There were some bugs with ubuntu1, so try 2.0-2ubuntu2. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1561434 Title: lxc-checkpoint failed on current newest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1561434/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1536297] [NEW] unable to lxc-start unprivileged LXC on wily due to permissions error
On Wed, Jan 20, 2016 at 05:48:52PM -, Tom Haddon wrote: > Public bug reported: > > I've followed https://help.ubuntu.com/lts/serverguide/lxc.html#lxc- > basic-usage but am getting a failure on lxc-start as follows: > > lxc-start -n container-test2 -F > lxc-start: start.c: print_top_failing_dir: 102 Permission denied - could not > access /home/mthaddon. Please grant it 'x' access, or add an ACL for the > container root. > lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 2 > lxc-start: start.c: __lxc_start: 1213 failed to spawn 'container-test2' > lxc-start: lxc_start.c: main: 344 The container failed to start. > lxc-start: lxc_start.c: main: 348 Additional information can be obtained by > setting the --logfile and --logpriority options. > > Is this because my home directory is encrypted? Which user is it trying > to connect as? The container root, i.e. the first uid you put in /etc/subuid. If you grant access to that user (either by making it world +x or adding an acl as the message says), you should be able to launch a container. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1536297 Title: unable to lxc-start unprivileged LXC on wily due to permissions error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1536297/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1514960] Re: lxc-test-checkpoint-restore fails with no explanation why
Hi,
What version of criu do you have installed? What's the host? Can you
show the output of /tmp/checkpont/{dump,restore}.log after the failure?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1514960
Title:
lxc-test-checkpoint-restore fails with no explanation why
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514960/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
The lxc in wily-proposed also works for me: inet addr:10.0.4.1 Thanks all. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
** Description changed: + + Impact: restoring containers from a checkpoint doesn't work + Development fix: LXC uses /usr/lib/x86_64-linux-gnu/lxc as the path to moun the container's root filesystem in its private mount namespace before it pivot_roots during restore. Unfortunately, that's also the location of the lxc-restore-net script which criu tries to execute. Since at this point the container's fs has already been mounted there, the callback (and thus the restore) fails. + Stable fix: Same as development fix + Testcase: create a container, then do: + sudo lxc-checkpoint -n $foo -s -D /tmp/checkpoint + sudo lxc-checkpoint -r -n $foo -D /tmp/checkpoint + + The restore fails with, + + sh: 1: /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found + + Regression potential: This can't effect anything besides lxc-checkpoint -r, which is broken anyways, so there should be no regressions. + + + A patch for this has been posted to the upstream LXC list here: https://lists.linuxcontainers.org/pipermail/lxc- devel/2014-October/010741.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
Sorry about that, turns out I copied and pasted from my terminal to create the file, which screwed up some whitespace. In any case, here's an updated debdiff that has been install tested. ** Patch added: "updated.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+attachment/4247114/+files/updated.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384751] Re: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc-restore-net: not found
Here's a debdiff for the patch. ** Patch added: "lxc.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+attachment/4246695/+files/lxc.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1384751 Title: checkpoint restore fails with /usr/lib/x86_64-linux-gnu/lxc/lxc- restore-net: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1384751/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Tycho Andersen: Work items changed: Work items for ubuntu-14.06: [tycho-s] test/fix basic multi-process criu: DONE [tycho-s] send patch to fix c/r of pseudofs mounts (pstore etc): DONE [tycho-s] c/r cgroup settings: DONE [serge-hallyn] fix btrfs issues with lxc snapshots: DONE [serge-hallyn] simplify lxc-execute: DONE [serge-hallyn] cgmanager: allow multiple controllers in a single API call: DONE Work items for ubuntu-14.07: [tycho-s] criu: figure out why checkpoint sometimes fails: INPROGRESS [tycho-s] (or serge-hallyn) implement lxc-checkpoint: TODO [tycho-s] (or serge-hallyn) design lxc-restart: TODO [tycho-s] criu: hook the network interface up at restart: TODO [serge-hallyn] cgmanager: handle co-mounted controllers: DONE [zulcss] native lxc driver for openstack: INPROGRESS [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: TODO Work items for ubuntu-14.08: [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED [serge-hallyn] (actually hazmat) image based workflow for juju: POSTPONED [jjohansen] Provide a test PPA for stacked apparmor profiles: TODO [serge-hallyn] Test apparmor stacked profiles (2d): BLOCKED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): BLOCKED - [tycho-s] c/r consoles : TODO - [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO + [tycho-s] c/r consoles : POSTPONED [tycho-s] re-attach lxc monitor at criu restart: DONE Work items for ubuntu-14.09: [serge-hallyn] design security profiles: POSTPONED [sforshee] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [sforshee] enable mounts in unprivileged containers, using fuse: DONE [tycho-s] Design unprivileged checkpoint and restart: POSTPONED + [tycho-s] additional criu breakages for basic containers (split up as we find them): TODO + [tycho-s] fix dumping ubuntu-cloud containers (missing pid fix): DONE + [tycho-s] fix co-mounted cgroup restore bug: INPROGRESS + [tycho-s] fix not being able to checkpoint restored containers: TODO -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1308772] Re: maas has no way to specify alternate IP addresses for AMT template
Yep, verified (by adding the optional power_address parameter on one of the nodes imported into the new version and noting that it does indeed override the default IP address maas has). ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1308772 Title: maas has no way to specify alternate IP addresses for AMT template To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1308772/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1305907] [NEW] boot: section in pserv.yaml is obsolete
Public bug reported: This is obsoleted by bootresources.yaml and should be removed. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1305907 Title: boot: section in pserv.yaml is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305907/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1282657] Re: lxc-create hangs in some cases on trusty
Apologies for the delay. I don't think this is an issue for us any more. I think it was probably (?) related to us calling lxc from inside d-i and having some crazy DEBIAN_* variables exported. However, (thankfully) we've devised a cleaner mechanism for what we're doing than that. ** Changed in: lxc (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1282657 Title: lxc-create hangs in some cases on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1282657/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1284652] Re: maas/installation-note could (should?) be echoed to the CLI, not a debconf note
On Wed, Mar 19, 2014 at 03:14:35PM -, Robie Basak wrote: > OK, thanks. That makes sense. I'm not sure what the original rationale > was to add that message in the first place, since in the general case we > avoid such things on Ubuntu. So I'll leave the bug open for that, but I > think we can drop the milestone if it's not blocking you. Yep, sounds good to me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1284652 Title: maas/installation-note could (should?) be echoed to the CLI, not a debconf note To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1284652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1284652] Re: maas/installation-note could (should?) be echoed to the CLI, not a debconf note
Hi Robie, On Wed, Mar 19, 2014 at 02:02:23PM -, Robie Basak wrote: > @Tycho > > Does DEBIAN_FRONTEND=noninteractive not work? Or are you unable to do > this in your case? We were listing maas as a dependency for the cloud installer, so we'd have to ask the user to run with a non-interactive frontend when they installed the cloud installer to avoid the message, which didn't seem like a great thing. However, now we've changed the process and so this bug isn't actually so relevant for us any more; we can probably close it if you want. \t -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1284652 Title: maas/installation-note could (should?) be echoed to the CLI, not a debconf note To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1284652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1284652] [NEW] maas/installation-note could (should?) be echoed to the CLI, not a debconf note
Public bug reported: Can this be echoed on the command line, instead of listed as an installation note? We'd like to not have any pop-ups when you apt-get install cloud. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1284652 Title: maas/installation-note could (should?) be echoed to the CLI, not a debconf note To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1284652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1282657] [NEW] lxc-create hangs in some cases on trusty
On Thu, Feb 20, 2014 at 04:31:16PM -, Serge Hallyn wrote:
> Thanks for filing this bug.
>
> > lxc-create -n juju-bootstrap -t ubuntu-cloud -- -r precise
>
> Does adding --no_locales, i.e.
>
> lxc-create -n juju-bootstrap -t ubuntu-cloud -- -r precise --no_locales
>
> work around the issue for you?
No, doesn't seem to.
> Could you show a full process tree at the time that lxc-create is
hung?
25223 pts/9S+ 0:00 \_ lxc-create -n
juju-bootstrap -t ubuntu-cloud -- -r precise --no_locales
25225 pts/9S+ 0:00 \_ /bin/bash
/usr/share/lxc/templates/lxc-ubuntu-cloud --path=/var/lib/l
25305 pts/9S+ 0:00 \_
/usr/bin/perl -w /usr/sbin/dpkg-reconfigure -f noninteractive tzd
25310 pts/9S+ 0:00 \_ /bin/sh
/var/lib/dpkg/info/tzdata.config reconfigure 2013g-0u
>
> ** Changed in: lxc (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1282657
>
> Title:
> lxc-create hangs in some cases on trusty
>
> Status in “lxc” package in Ubuntu:
> Incomplete
>
> Bug description:
> + lxc-create -n juju-bootstrap -t ubuntu-cloud -- -r precise
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = "en_GB:en",
> LC_ALL = "en_US.UTF-8",
> LANG = "en_US.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> locale: Cannot set LC_CTYPE to default locale: No such file or directory
> locale: Cannot set LC_MESSAGES to default locale: No such file or directory
> locale: Cannot set LC_ALL to default locale: No such file or directory
> # lxc-create is now hung
>
> locale-gen is not running, so from irc chatter with hallyn this seems
> like it is not a dupe of bug 1166841.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1282657/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1282657
Title:
lxc-create hangs in some cases on trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1282657/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1282657] [NEW] lxc-create hangs in some cases on trusty
Public bug reported:
+ lxc-create -n juju-bootstrap -t ubuntu-cloud -- -r precise
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_GB:en",
LC_ALL = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
# lxc-create is now hung
locale-gen is not running, so from irc chatter with hallyn this seems
like it is not a dupe of bug 1166841.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1282657
Title:
lxc-create hangs in some cases on trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1282657/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1281793] Re: lxc packaging w/ bridge-utils is confused
On Wed, Feb 19, 2014 at 03:53:47PM -, Stéphane Graber wrote: > What kernel are you running on? > > The last time I saw that specific error, it was with a kernel not > supporting mangle+fill-checksum. CloudFive:~/packages/cloud-installer/tools$ uname -r 3.13.0-5-generic Basically, a reasonably recent version of the stock trusty kernel. Is there somewhere I can look specifically? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1281793 Title: lxc packaging w/ bridge-utils is confused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1281793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1281793] Re: lxc packaging w/ bridge-utils is confused
Hey, sorry about that, forgot to post: CloudFive:~/packages/cloud-installer/tools 1$ sudo cat /var/log/upstart/lxc-net.log iptables: Bad rule (does a matching rule exist in that chain?). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1281793 Title: lxc packaging w/ bridge-utils is confused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1281793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1281793] [NEW] lxc packaging w/ bridge-utils is confused
Public bug reported: CloudFive:~/packages/cloud-installer/tools$ sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: bridge-utils cloud-image-utils debootstrap distro-info euca2ools libboost-thread1.54.0 liblxc0 librados2 librbd1 libseccomp2 lxc lxc-templates python-distro-info python-requestbuilder python3-lxc qemu-utils 0 upgraded, 0 newly installed, 16 to remove and 440 not upgraded. After this operation, 12.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 174629 files and directories currently installed.) Removing lxc-templates (1.0.0~rc3-0ubuntu1) ... Removing lxc (1.0.0~rc3-0ubuntu1) ... stop: Job failed while stopping invoke-rc.d: initscript lxc-net, action "stop" failed. dpkg: error processing package lxc (--remove): subprocess installed pre-removal script returned error exit status 1 lxc-net start/running Removing cloud-image-utils (0.27-0ubuntu7) ... Removing debootstrap (1.0.59) ... Removing distro-info (0.12) ... Removing euca2ools (3.0.2-1ubuntu1) ... Removing qemu-utils (1.7.0+dfsg-3ubuntu2) ... Removing librbd1 (0.72.2-1) ... Removing librados2 (0.72.2-1) ... Removing libboost-thread1.54.0:amd64 (1.54.0-4ubuntu3) ... Removing python-distro-info (0.12) ... Removing python-requestbuilder (0.1.0~beta2-1) ... dpkg: python3-lxc: dependency problems, but removing anyway as you requested: lxc depends on python3-lxc. Removing python3-lxc (1.0.0~rc3-0ubuntu1) ... dpkg: liblxc0: dependency problems, but removing anyway as you requested: lxc depends on liblxc0 (= 1.0.0~rc3-0ubuntu1). Removing liblxc0 (1.0.0~rc3-0ubuntu1) ... Removing libseccomp2:amd64 (2.1.0+dfsg-1) ... dpkg: bridge-utils: dependency problems, but removing anyway as you requested: lxc depends on bridge-utils. Removing bridge-utils (1.5-6ubuntu2) ... Processing triggers for man-db (2.6.6-1) ... Processing triggers for libc-bin (2.18-0ubuntu6) ... Errors were encountered while processing: lxc E: Sub-process /usr/bin/dpkg returned an error code (1) I'm not exactly sure what the problem is here, but autoremove should never break :-) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1281793 Title: lxc packaging w/ bridge-utils is confused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1281793/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1281758] [NEW] re-installing maas-region-controller fails
Public bug reported: When I re-install maas-region-controller on a machine (when it was uninstalled via sudo apt-get -yy purge '.*maas.*'), I see the following: Setting up maas-region-controller (1.5+bzr1951-0ubuntu1) ... * Stopping web server apache2 * * Restarting PostgreSQL 9.3 database server [ OK ] Considering dependency proxy for proxy_http: Module proxy already enabled Module proxy_http already enabled Module expires already enabled Module wsgi already enabled * Restarting message broker rabbitmq-server [ OK ] Changing password for user "maas_longpoll" ... ...done. Changing password for user "maas_workers" ... ...done. Syncing... Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 159, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 129, in _cursor self.ensure_connection() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 124, in ensure_connection self.connect() File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 124, in ensure_connection self.connect() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 112, in connect self.connection = self.get_new_connection(conn_params) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 116, in get_new_connection return Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) django.db.utils.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" It hangs there, and I have to kill a bunch of random dpkg stuff, edit the postinst file to comment that part out, finish the install, then purge the database. Two things should happen: 1. when I purge, the packaging should drop the maas database 2. it shouldn't hang like this :-) ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1281758 Title: re-installing maas-region-controller fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1281758/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1252768] [NEW] removing (including with --purge) fails on pg script
Public bug reported: After experiencing bug #1252510, I tried to apt-get purge *maas*, which failed to uninstall maas-region-controller as follows: smitten:~$ sudo dpkg --purge --force-all maas-region-controller (Reading database ... 391242 files and directories currently installed.) Removing maas-region-controller ... * Stopping web server apache2 * dpkg: error processing maas-region-controller (--purge): subprocess installed pre-removal script returned error exit status 10 Errors were encountered while processing: maas-region-controller The line it failed on was the PG helper: dbc_go maas-region-controller $@ when I commented that out, everything worked fine. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1252768 Title: removing (including with --purge) fails on pg script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1252768/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1252510] Re: Reinstalling hangs apt-get
** Description changed: I'm not sure exactly what's hanging here, but there is no IO going on, and it's been sitting like this for 10 minutes. smitten:~$ sudo dpkg --configure -a Setting up maas-region-controller (1.4+bzr1693+dfsg-0ubuntu2.2) ... - * Stopping web server apache2 * - * Restarting PostgreSQL 9.1 database server [ OK ] + * Stopping web server apache2 * + * Restarting PostgreSQL 9.1 database server [ OK ] Considering dependency proxy for proxy_http: Module proxy already enabled Module proxy_http already enabled Module expires already enabled Module wsgi already enabled - * Restarting message broker rabbitmq-server [ OK ] + * Restarting message broker rabbitmq-server [ OK ] Changing password for user "maas_longpoll" ... ...done. Changing password for user "maas_workers" ... ...done. Syncing... OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" + + + Install, maybe (? not sure if this is necessary) create a user, then apt-get autoremove *maas*, then apt-get install maas. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1252510 Title: Reinstalling hangs apt-get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1252510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1252510] [NEW] Reinstalling hangs apt-get
Public bug reported: I'm not sure exactly what's hanging here, but there is no IO going on, and it's been sitting like this for 10 minutes. smitten:~$ sudo dpkg --configure -a Setting up maas-region-controller (1.4+bzr1693+dfsg-0ubuntu2.2) ... * Stopping web server apache2 * * Restarting PostgreSQL 9.1 database server [ OK ] Considering dependency proxy for proxy_http: Module proxy already enabled Module proxy_http already enabled Module expires already enabled Module wsgi already enabled * Restarting message broker rabbitmq-server [ OK ] Changing password for user "maas_longpoll" ... ...done. Changing password for user "maas_workers" ... ...done. Syncing... OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1252510 Title: Reinstalling hangs apt-get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1252510/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
