[Bug 1475247] Re: ceph-disk-prepare --zap-disk hang
** Branch unlinked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two- phases ** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/add-zap-fix-patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Changed in: ceph-osd (Juju Charms Collection) Status: In Progress = Fix Committed ** Changed in: ceph (Juju Charms Collection) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-phases -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1475247] Re: ceph-disk-prepare --zap-disk hang
** Changed in: ceph (Ubuntu Trusty) Assignee: (unassigned) = Chris Glass (tribaal) ** Changed in: ceph (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1475247 Title: ceph-disk-prepare --zap-disk hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1475247/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
On the host. Sorry for taking so long to answer, launchpad seems to have eaten my email answer... -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Correction, on the host and on outer (just tried). -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Adding ppa:ubuntu-lxc/daily seems to solve the problem. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Ok, so it seems this isn't fixed after all. Following the exact steps reported in my original message result in a non-starting container (same error message) -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Changed in: lxc (Ubuntu) Status: Fix Released = Confirmed -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
This seems to be fixed in vivid with lxc 1.1.2: tribaal@vivid-test:~$ apt-cache policy lxc lxc: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status tribaal@vivid-test:~$ apt-cache policy lxc-templates lxc-templates: Installed: 1.1.2-0ubuntu1 Candidate: 1.1.2-0ubuntu1 Version table: *** 1.1.2-0ubuntu1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
So, the new lxcfs in vivid-proposed does *not* solve this particular problem. Again, running the daily PPA code solved this, but that means using the ppa for both vivid and trusty, not just vivid. Don't hesitate to let me know how I can test more/further versions of LXC, including git branches, if needed. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Description changed: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - - sudo su - - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config + - sudo su + - echo 'lxc.aa_profile = lxc-container-default-with-nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: - lxc.network.type = veth - lxc.network.link = lxcbr0 - lxc.network.flags = up - lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
If both the host (vivid) and the outer guest run LXC from ppa:ubuntu- lxc/daily, the tested scenario works. sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and at leas the outer guest (trusty). N.b. Only works if both the host and the first guest run the ppa code - seems like only the host running the newest code doesn't help. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
Oh, good to hear. Can I easily test what's in vivid-proposed, and/or somehow influence the landing? Since I have a pretty good test set up for this particular scenario I might as well help you guys :) -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
** Tags added: landscape -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] [NEW] Regression: Nested LXC is broken on Vivid
Public bug reported: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 889656] Re: installer stops using proxy
This is fixed since the python code (instead of bash) behaves properly now. Closing this bug (it's old, bug triage has taken a lot of dust). Feel free to reopen should this sting you again. ** Changed in: squid-deb-proxy (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/889656 Title: installer stops using proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/889656/+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 1166667] Re: The default configuration is missing the /etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
This should be fixed in the next version of squid-deb-proxy when it's released. ** Changed in: squid-deb-proxy (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/117 Title: The default configuration is missing the /etc/squid-deb- proxy/autogenerated/pkg-blacklist-regexp.acl file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/117/+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 1320587] Re: Intermittent 403 Issues
The linked branch should help with the problem, at the cost of an extra round-trip to the upstream archive. ** Branch linked: lp:~tribaal/squid-deb-proxy/refresh-ims -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1320587 Title: Intermittent 403 Issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1320587/+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 1303903] Re: sgdisk zap/clear doesn't wipe all GPT tables
** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/1303903 Title: sgdisk zap/clear doesn't wipe all GPT tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/1303903/+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 1303617] Re: Latest curtin version prevents Juju from bootstrapping on MAAS
** Also affects: curtin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1303617 Title: Latest curtin version prevents Juju from bootstrapping on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1303617/+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 1303617] Re: Latest curtin version prevents Juju from bootstrapping on MAAS
** Description changed: Curtin version: 0.1.0~bzr124-0ubuntu1 Curtin-common: 0.1.0~bzr124-0ubuntu1 Bootstrapping a juju environment on an up-to-date trusty MAAS server fails. The bootstrap node becomes pingable but never allows connections to the juju agent. Cloud init output (shows error): http://pastebin.ubuntu.com/7215883/ Cloud init log: http://pastebin.ubuntu.com/7215881/ - Reverting python-curtin and curtin-common to 0.1.0~bzr121-0ubuntu1 works - around the problem. + Reverting python-curtin and curtin-common to 0.1.0~bzr121-0ubuntu1 does + not show the problem anymore. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1303617 Title: Latest curtin version prevents Juju from bootstrapping on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1303617/+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 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
For the record, this affects the precise package as well. I would strongly recommend uploading a fixed package to the cloud-archive:tools repository since most people installing maas will use this (it's the recommended way). tribaal@maas:~$ apt-cache policy squid-deb-proxy squid-deb-proxy: Installed: 0.6.3.1 Candidate: 0.6.3.1 Version table: *** 0.6.3.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.3 0 500 http://ch.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages tribaal@maas:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.3 LTS Release:12.04 Codename: precise -- 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/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+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 1247886] Re: squid-deb-proxy is not started when installing MaaS with 13.10 server CD
Yes, I should have attached that log file in my initial report. It's the same problem :( -- 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/1247886 Title: squid-deb-proxy is not started when installing MaaS with 13.10 server CD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1247886/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Changing back to juju-core since this affects me, and I'm not using LXC containers at all. ** Package changed: lxc (Ubuntu) = juju-core (Ubuntu) ** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I hit the same problem, and don't use LXC at all on my setup. I therefore will change this bug to point back to juju-core. My MaaS lives in a KVM machine on my laptop. It can PXE boot/start-stop other KVM machines living on the same NAT'ed network. - juju bootstrap --upload-tools works (the node is spun up, and after the ubuntu install, juju status works). - I can juju deploy any charm, however: - The machines come up (the node boots, ubuntu gets installed), but juju status reports pending forever. The machine that is brought up has the same symptoms as reported above: The machine log in /var/log/juju show: 2013-11-05 18:39:02 ERROR juju runner.go:211 worker: exited deployer: exec [start --system jujud-unit-rabbitmq-server-0]: exit status 1 (start: Unable to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) Running this command by hand works when run without --system. Once ran, /var/log/juju contains a unit log as: http://pastebin.ubuntu.com/6371502/ The cloud-init log and cloud-init-output log are: http://pastebin.ubuntu.com/6371297/ http://pastebin.ubuntu.com/6371310/ I further tried to fix the situation manually by symlinking /var/lib/juju/tools/1.16.2.1-saucy-amd64/ to /var/lib/juju/tools /unit-mysql-0, but to no avail. -- 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/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge in Saucy. Steps to reproduce: - Install maas using the saucy server install CD. - Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic - Configure the rest of MaaS, click the import boot images in the UI - PXE boot a machine What happens: The machine PXE boots, gets assigned an IP address by MaaS. The node gets stuck on Trying to load: pxelinux.cfg/default and finally reboots after a timeout triggers. This results in an eternal reboot loop. What should be happening: The machine PXE boots, gets assigned an IP address, and successfully downloads a bootable image from tftp, resuming normal operations. -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Further information: Relevant stacktrace: https://pastebin.canonical.com/99705/ -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
Sorry, I used a private pastebin, here's the public equivalent: http://pastebin.ubuntu.com/6340916/ @rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try and report back! -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll subscribe to bug 1181334 instead! Thanks for your help. -- 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/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+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 1181334] Re: i386 required to install amd64
Can confirm, it would save us (the landscape team, but also other users I wager) a lot of time and disk space if we could only download amd64 images and use that successfully. -- 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/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+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
