>From http://docs.openstack.org/folsom/openstack-compute/admin/content
/associating-public-ip.html:
"""
Traffic between VMs using floating IPs:
Note that due to the way floating IPs are implemented using a source NAT (SNAT
rule in iptables), inconsistent behaviour of security groups can be seen
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
Thanks, that seems to work. I guess it was just an expectation issue -
didn't realise I'd have to fix things up manually to get unprivileged
containers to work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs
Public bug reported:
I've created a xenial LXC on a trusty host as follows:
http://paste.ubuntu.com/15244552/
I'm able to run commands inside the LXC without "--share-net 1" but any
time I try with "--share-net 1" it fails, such as:
http://paste.ubuntu.com/15243604/ (strace output).
Will attac
*** This bug is a duplicate of bug 1551299 ***
https://bugs.launchpad.net/bugs/1551299
Public bug reported:
This is a duplicate of 1551299
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxc 1.0.8-0ubuntu0.3
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux
** Attachment added: "apport.lxc.qo3lud5p.apport"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+attachment/4584512/+files/apport.lxc.qo3lud5p.apport
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:
Shouldn't be using "--share-net 1". Need to "lxc-start -n $container-
name -d" and then "lxc-attach -n $container-name -- cmd". Needed lxc
from trusty-backports too.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: canonical-webops
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
juju-machine-agent.log/logs are not logrotated
To manage no
Public bug reported:
Binary package hint: rabbitmq-server
Per http://pastebin.ubuntu.com/356068/, on upgrading from 1.54 -> 1.7.0,
users and vhosts are wiped out. I checked in #rabbitmq on freenode, and
the suggestion there was that this is a packaging bug.
** Affects: rabbitmq-server (Ubuntu)
Great, thanks. I can confirm they weren't there before, but are
available now.
--
[jaunty] Please package ec2-api-tools for i386
https://bugs.launchpad.net/bugs/347525
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ec2-api-tools in ubuntu
I'm seeing this on trusty/icehouse:
root@furud:~# virsh list --all
IdName State
32instance-2bb1 running
37instance-2bb2 running
4237 instance-6b86 runn
Just experienced the same issue with 1.5.4+bzr2294-0ubuntu1.2
--
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/1376459
Title:
1.5.4+bzr2294-0ubuntu1.1 maas-dhcp package update stops exte
12 matches
Mail list logo
