** 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.
** 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
** 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
** 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
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
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
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
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.
** 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
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
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,
** 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:
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
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
** 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:
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
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
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
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
** 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:
** 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
** 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
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:
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
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
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
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
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
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
@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
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
Hi John!
I recently started helping on the server guide as well, and so here are a
few tips I can share:
- Follow the procedure outlined here [1] for the source checkout and
lanchpad/bzr integration.
- Using LXC containers, it's very simple to spin up a new, pristine Ubuntu
Saucy machine (sudo
32 matches
Mail list logo
