The cloud-image builder picked up the change and is building images.
They are with the LP buildds now. I will update this bug once
publication completes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launc
Cloud image downloads for amd64, i386, and ppc64el are available @ http
://cloud-images.ubuntu.com/proposed/wily/20151024/
The amd64 image is also available in canonistack lcy02 region as
lp1509414/wily-proposed
--
You received this bug notification because you are a member of Ubuntu
Server
Cloud images build from proposed are available.
Next action:
--
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 lat
Cloud images build from proposed are available.
Next action:
- Verification of proposed package.
--
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 clo
Should this issue be fixed on current Ubuntu 15.04?
Having systemd 219-7ubuntu6 installed, this issue still appears.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1422125
Title:
ntpdat
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/1509661
Title:
package xinetd 1:2.3.15-4 failed to install/upgrade: subprocess
installed post-i
Public bug reported:
during upgrade from 15.04 to 15.10
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: xinetd 1:2.3.15-4
ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
Uname: Linux 4.2.0-17-generic i686
ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
Date: Sat Oct 24 12:24:25
I've been running the autofs-ldap & autofs binaries from 14.04 in 15.10,
they work fine.
I had different issues with the 14.10 and 15.04 binaries (on their
respective releases), which never worked with LDAP, but appeared to hard
lock rather than segfault so it was harder to track down.
--
You re
New image works for me in lxc:
lxcbr0Link encap:Ethernet HWaddr 76:79:3e:90:1c:88
inet addr:10.0.4.1 Bcast:0.0.0.0 Mask:255.255.255.0
--
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/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/150945
Be aware in your testing that the lxd-net's service can come up slowly
depending on the speed of your cloud instance. Without the bridge
(lxcbr0) the container's networking will function prior to that service
starting; watch out for this false positive in your testing.
--
You received this bug no
This is possibly not the Intel firmware bug mentioned in my previous
comment but an older one:
X18/X25-M/V G2 series with Firmware before 2CV102J8 may hang if self-
test log is read. G1 series may also be affected. Smartctl and smartd
print a related warning for G2 series but not for G1.
Please u
** Changed in: tmux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tmux in Ubuntu.
https://bugs.launchpad.net/bugs/1439405
Title:
tmux window pane navigation no longer directional
To mana
Kicked off instances for testing with Juju. Will update with results
once my testing is complete.
--
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 cl
For python-invoke this was fixed in https://launchpad.net/ubuntu/+source
/python-invoke/0.9.0-2.
** Changed in: python-invoke (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-rtslib-fb
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 broke
Public bug reported:
There's no network inside Docker containers in Ubuntu 15.10.
Steps to reproduce:
1, Install Ubuntu 15.10
2, Install docker.io package
3, Execute "sudo docker run -it ubuntu:14.04"
4, At the container's root prompt execute "ping www.ubuntu.com" or "ping
91.189.89.110"
Expect
I just tried filling out the contributor agreement (so far I am the sole
author of the changes), but I'm not sure what to put for the project
contact and it is required. Do I put you, Serge?
Thanks for the comments on GitHub. I'll address them asap and get the
changes into bzr.
--
You received t
Quoting Joseph Bisch (josephbi...@gmail.com):
> I just tried filling out the contributor agreement (so far I am the sole
> author of the changes), but I'm not sure what to put for the project
> contact and it is required. Do I put you, Serge?
Uh, I'm really not sure. Putting me down sounds right.
Tested wily-proposed cloud-image running in local kvm. Started wily-
proposed container via lxc (using ubuntu-cloud template), verified the
container's lxcbr0 looks fine (10.0.4.1), verified networking works (via
www.google.com).
--
You received this bug notification because you are a member of
I was able to For stage two, at least with systemd, I changed
/lib/systemd/system/lxd-startup.service to:
[Unit]
Description=Container hypervisor based on LXC - boot time check
After=cgmanager.service lxd-unix.socket
Requires=cgmanager.service lxd-unix.socket
[Service]
Type=oneshot
ExecStart=/usr
I've also tested manually and via our OpenStack installer and lxcbr0 is
assigned (10.0.4.1) and the network is able to reach out to the internet
as before.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.laun
I added the Debian guest related commits to
https://code.launchpad.net/~josephbisch/vmbuilder/debian. I also added
Debian Stretch and tested out creating a KVM image of it.
I notice that my full name doesn't show up in the list of revisions like
it does for other people. I guess I don't have my lo
** Changed in: rabbitmq-server (Ubuntu)
Assignee: (unassigned) => MD NADEEM (mail2nadeem92)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1199474
Title:
rabbitmq fails
This lxc debdiff (not appropriate upstream lxc) and a pull request
against lxd-pkg-ubuntu (https://github.com/lxc/lxd-pkg-ubuntu/pull/7)
combined should implement stage 2 of the fix.
Note I've tested these when separately implemented by hand, but have not
built packages with this debdiff+pull-requ
** Changed in: rabbitmq-server (Ubuntu)
Assignee: MD NADEEM (mail2nadeem92) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1199474
Title:
rabbitmq fails
Verified that Juju can start lxc containers with the proposed changes.
The containers came up and were able to communicate with the state
server, even when on a separate machine.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ub
My testing with the cloud image containing the proposed package has been
successful.
Just a note again that the test case detailed in the description is fine
with the understanding that network testing needs to ensure the lxc-net
service has started lxcbr0 or a false positive is possible (per comm
Serge - your changes from comment #22 will break juju with lxc. juju
will need to be modified to call systemctl add-wants multi-user.target
lxc.service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchp
On Sunday, October 25, 2015 03:12:44 AM you wrote:
> Serge - your changes from comment #22 will break juju with lxc. juju
> will need to be modified to call systemctl add-wants multi-user.target
> lxc.service
If that's the case, this approach for a fix probably isn't appropriate for an
SRU.
--
I agree, the stage 2 fix for this issue concerns me with regard to
regressing current use cases.
As much as I'd like to get rid of the rest of this issue (any user of
10.0.4.0/24 behind a router looses connectivity to that subnet), we must
make sure we do not regress anyone who's been relying on "
[Expired for bcache-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: bcache-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launch
Public bug reported:
This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
1.0.7-0ubuntu0.9 (or anything that incorporates
0003-CVE-2015-1335.patch). Basically, the limitation is obvious when
using recursive bind mounts because ensure_not_symlink() only checks the
last line of /proc
This bug was fixed in the package w3m - 0.5.3-25
---
w3m (0.5.3-25) unstable; urgency=medium
* Update 020_debian.patch to v0.5.3+git20151010
- Remove incomplete special_domain tests (closes: #385702)
- Fix unknown key in keymap.lynx (LP: #265144)
* Set Priority to optional
Public bug reported:
Description:Ubuntu 15.10
Release:15.10
samba:
Installed: 2:4.1.17+dfsg-4ubuntu2
Candidate: 2:4.1.17+dfsg-4ubuntu2
Version table:
*** 2:4.1.17+dfsg-4ubuntu2 0
500 http://my.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg
36 matches
Mail list logo
