[Bug 1022612] Re: private instance IPs can only reach public IPs in other regions, not the same region
>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 if VMs use their floating IP to communicate with other virtual machines - particularly on the same physical host. Traffic from VM to VM accross the fixed network does not have this issue, and this is the recommended path. To ensure traffic doesn't get SNATed to the floating range, explicitly set dmz_cidr=x.x.x.x/y. x.x.x.x/y is the range of floating ips for each pool of floating ips you define. This configuration is also necessary to make source_groups work if the vms in the source group have floating ips. """ This might help... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1022612 Title: private instance IPs can only reach public IPs in other regions, not the same region To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1022612/+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 1536297] [NEW] unable to lxc-start unprivileged LXC on wily due to permissions error
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? Here are my permissions on /home: $ ls -lh /home/ total 212K drwx-- 113 mthaddon mthaddon 204K Jan 20 17:41 mthaddon drwxr-xr-x 2 safechain nogroup 4.0K Jul 31 2014 safechain ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.5-0ubuntu0.15.10.3 Uname: Linux 4.2.0-040200rc3-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Wed Jan 20 17:34:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-04 (1569 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-11-19 (62 days ago) 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: apport-bug i386 wily -- 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 1536297] Re: unable to lxc-start unprivileged LXC on wily due to permissions error
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.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 1551299] [NEW] Unable to run LXC commands on xenial guest in trusty host with --share-net 1
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 attach apport report. ** 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/1551299 Title: Unable to run LXC commands on xenial guest in trusty host with --share-net 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+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 1551304] [NEW] Unable to run LXC commands on xenial guest in trusty host with --share-net 1
*** 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 3.13.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Mon Feb 29 15:51:10 2016 Ec2AMI: ami-0142 Ec2AMIManifest: FIXME Ec2AvailabilityZone: prodstack-zone-1 Ec2InstanceType: cpu1-ram2-disk50 Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 KernLog: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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 apport-bug ec2-images trusty ** This bug has been marked a duplicate of bug 1551299 Unable to run LXC commands on xenial guest in trusty host with --share-net 1 -- 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/1551304 Title: Unable to run LXC commands on xenial guest in trusty host with --share-net 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551304/+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 1551299] Re: Unable to run LXC commands on xenial guest in trusty host with --share-net 1
** 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://bugs.launchpad.net/bugs/1551299 Title: Unable to run LXC commands on xenial guest in trusty host with --share-net 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+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 1551299] Re: Unable to run LXC commands on xenial guest in trusty host with --share-net 1
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1551299 Title: Unable to run LXC commands on xenial guest in trusty host with --share-net 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1551299/+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 1078213] Re: juju-machine-agent.log/logs are not logrotated
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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 506985] [NEW] Upgrade from rabbitmq-server 1.54 -> 1.7.0 wiped users and vhosts
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) Importance: Undecided Status: New -- Upgrade from rabbitmq-server 1.54 -> 1.7.0 wiped users and vhosts https://bugs.launchpad.net/bugs/506985 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in ubuntu. -- 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 347525] Re: [jaunty] Please package ec2-api-tools for i386
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. -- 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 807091] Re: "internal error character device (null) is not using a PTY" when using virsh console
I'm seeing this on trusty/icehouse: root@furud:~# virsh list --all IdName State 32instance-2bb1 running 37instance-2bb2 running 4237 instance-6b86 running 4238 instance-6b87 running root@furud:~# virsh console instance-6b87 Connected to domain instance-6b87 Escape character is ^] error: internal error: character device is not using a PTY ** Changed in: nova (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/807091 Title: "internal error character device (null) is not using a PTY" when using virsh console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/807091/+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 1376459] Re: 1.5.4+bzr2294-0ubuntu1.1 maas-dhcp package update stops external dhcpd
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 external dhcpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1376459/+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
