Many thanks to Michael, Raghu and Robie for helping to clarify. Marking
this bug as invalid...
** Changed in: mongodb (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
Hello!
I'm using Ubuntu Server 14.04.1 in VM
# cat /etc/issue
Ubuntu 14.04.1 LTS \n \l
# uname -a
Linux vm-newsru-fe-02 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
I'm using nginx
# dpkg -l | grep nginx
ii nginx-common
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
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/1382190
** Changed in: maas
Status: Triaged = In Progress
--
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/1382190
Title:
LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
To manage
*** This bug is a duplicate of bug 1382190 ***
https://bugs.launchpad.net/bugs/1382190
** This bug has been marked a duplicate of bug 1382190
LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Title:
Openstack Neutron Database error.
To
I don't think the ordering of the package installs are important. They
run the same command. The problem seem to be that the code that creates
the secret key doesn't create it with the right permissions. The current
code in horizon/utils/secret_key.py does this:
old_umask =
** Summary changed:
- Openstack Neutron Database error.
+ Openstack Neutron Database error on package install
** Summary changed:
- Openstack Neutron Database error on package install
+ Openstack Neutron Database error on filling database
--
You received this bug notification because you are
Ah, so, the light of day: $GENERATE is only useful for networks with an
address range /24 — i.e. up to 255 addresses. After that it breaks
down, because:
$GENERATE 1-254 $.$.0.10.in-addr.arpa. IN PTR no-name-yet-$.$.maas.
Only generates 255 addresses; it's not recursive. You just get
(I'd say that option 3 is the most tasteful, as long as we can solve the
lag 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/1382190
Title:
LXCs assigned IPs by MAAS DHCP
I think #1 is too limited. This will only satisfy a subset of users, and
it's confusing to an outsider trying to deploy their charms, why won't
RabbitMQ deploy in cluster $x when it deploys fine in cluster $y?. The
answer is not easily discoverable, and the MAAS administrator may not
realise that
I don't think #3 is that bad actually; remember that's how we used to do
it before static IP days so it's tried and tested (although admittedly
the DNS was in place by the time commissioning ended).
#2 is also good, but you have to calculate which lines to generate based
on the netmask.
I'd go
Let's try #2, though we will need to limit the size of the dynamic range
as part of that.
--
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/1382190
Title:
LXCs assigned IPs by MAAS DHCP
On 23 October 2014 11:04, Julian Edwards 1382...@bugs.launchpad.net wrote:
I don't think #3 is that bad actually; remember that's how we used to do
it before static IP days so it's tried and tested (although admittedly
the DNS was in place by the time commissioning ended).
Yeah, #3 doesn't
Increasing the max pool size seems to resolve this particular issue;
maybe having a default that's a multiple of the worker configuration
would be more intelligent here?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in
** Changed in: neutron
Assignee: (unassigned) = Ann Kamyshnikova (akamyshnikova)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Title:
Openstack Neutron Database error
Of course the problem isn't that it is run twice :) I said above that
in the first run the file is created with the incorrect permissions, and
then the second run barfs at that :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Some debug later reveals that in:
agent_ports += self._get_port_fdb_entries(binding.port)
binding.port == None
looking at how this gets into this state.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in
** Summary changed:
- Insecure key file permissions
+ Insecure key file permissions when running under LXC
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
The system where we saw this bug uses file system ACLs, with defauls,
and thus the umask is ignored:
ubuntu@juju-machine-0-lxc-5:/var/lib/openstack-dashboard$ getfacl .
# file: .
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::r-x
default:other::r-x
I guess its possible that due to the level of concurrency, there are
ports in the tenant network that are not fully bound at the point where
this call is made.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
** Summary changed:
- Insecure key file permissions when running under LXC
+ Insecure key file permissions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1382632
Title:
Insecure
To clarify, I see the same behavior on bare metal, deploying machines
with MAAS using the fast-path installer, so it's not LXC-specific.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
** Changed in: nginx
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1216817
Title:
Using `fastcgi_cache` or `proxy_cache` with nginx-extras
Checked this on MySQL and MariaDB. In both cases this error does not appear.
Logs of running with MariaDB - http://paste.openstack.org/show/123532/.
I used Juno and master neutron code also, both works fine.
** Changed in: neutron
Status: New = Invalid
--
You received this bug
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I've confirmed that non-caching performance on icehouse 2014.1.3 has
been restored back to the 2014.1.1 range.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1361357
Title:
On 10/23/2014 12:27 AM, Serge Hallyn wrote:
As such, I think it would be pretty reasonable to change lxc to always
use its own path.
Serge, thanks for looking into this!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
when update from ubuntu 12.04 to 14.04
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nova-common 1:2014.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
** Tags removed: need-duplicate-check
--
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/1384715
Title:
package nova-common 1:2014.1.3-0ubuntu1 failed to install/upgrade:
subprocess
** Changed in: lxc
Importance: Undecided = High
** Changed in: lxc
Status: New = Triaged
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: lxc
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
** Changed in: juju-core
Milestone: 1.21-alpha2 = 1.21-alpha3
--
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:
logs are not logrotated
To manage notifications about
You have been subscribed to a public bug:
lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04
apt-cache policy resolvconf
resolvconf:
Installed: 1.69ubuntu1.1
Candidate: 1.69ubuntu1.1
Version table:
*** 1.69ubuntu1.1 0
500 http://ch.archive.ubuntu.com/ubuntu/
Ok. So the crucial thing shown here is that in addition to the br
interfaces, you have NetworkManager. NetworkManager sets 'nameserver
127.0.1.1', which by design will redirect DNS requests to a local
dnsmasq proxy, with dnsmasq itself picking up the configured nameservers
instead; and when set,
Yes, with the standard neutron services it works, but we have some
additional l2 and l3 plugins. WIll post config files. Here are the
packages:
We are using Ubuntu 14.04 LTS and the staging-Juno packages:
root@vm-1:/var/log/mysql# dpkg --list |grep neutron
ii neutron-common
** Attachment added: neutron.conf
https://bugs.launchpad.net/neutron/+bug/1384555/+attachment/4242437/+files/neutron.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
** Attachment added: plugin.ini
https://bugs.launchpad.net/neutron/+bug/1384555/+attachment/4242438/+files/plugin.ini
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Andres and I have discussed this further, and he pointed out that the
LXCs can take a *long* time to start. That would be sufficient time for
us to parse the leases file and update the DNS with a PTR for the new
node (option #3).
I've tested this out locally. The LXC container took ~30minutes to
Public bug reported:
I've recently ran into a few cases where it'd have been very useful to
be able to grant veth allocations to a group rather than to a user.
This will also be required for running LXC on top of Unity8.
Can we please add a syntax like:
%lxcusers veth lxcbr0 10
Which would
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.
Sounds like a good idea, thanks.
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Tags added: aa-kernel
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Status: New = Won't Fix
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Confirmed
Thank you for the detailed analysis - regarding:
... since NetworkManager should still be processed and the 127.0.1.1 should
still take precedence ...
Actually for me it is important that the 127.0.1.1 does not take precedence
but instead my local name-servers take precedence (because when my
Thanks for the information. Looks like we can apply these in debian
too.
** Also affects: qemu (Ubuntu Utopic)
Importance: High
Status: Triaged
** Also affects: qemu (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: neutron
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Title:
Openstack Neutron Database error on filling database
To
** Changed in: openvswitch (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1369294
Title:
openvswitch-datapath-dkms
Public bug reported:
After performing update from Ubuntu Server 14.04 to 14.10, the nagios-
nrpe-server 2.15-1ubuntu1 package does not seem to respect the
dont_blame_nrpe option in /etc/nagios/nrpe.cfg. This option was set to
1 and working properly under 14.04 using package version 2.15-0ubuntu1,
** Branch linked: lp:~gmb/maas/add-ptr-records-bug-1382190
--
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/1382190
Title:
LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
To manage
Public bug reported:
After upgrading ubuntu over from 12. something to the 14.04 lts release my
squid proxy did not work any longer.
It often happens that sites are loading quite long and in the end there is a
connection problem.
Just in this moments I can see the following happen in dmesg
** Changed in: neutron
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1384555
Title:
Openstack Neutron Database error on filling database
To
Can confirm that I've got the same problem on Ubuntu 14.04, Openstack
Juno using the cloud-archive repository (juno-staging), ML2 with OVS and
L2population plugins, flat and vxlan network(s), L3 HA and DVR enabled.
Used puppet-neutron to deploy.
--
You received this bug notification because you
On Thursday 23 Oct 2014 15:40:51 you wrote:
Andres and I have discussed this further, and he pointed out that the
LXCs can take a *long* time to start. That would be sufficient time for
us to parse the leases file and update the DNS with a PTR for the new
node (option #3).
I've tested this
Well, whatever we do let's please not race with the lxc creation. That
would be worse than fixing this bug. :)
--
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/1382190
Title:
LXCs
Can confirm, this messes up my Plymouth splash also.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1364630
Title:
init: Error while reading from descriptor: Broken
** Tags added: aa-kernel
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1349433
Title:
AppArmor breaks seccomp @ Apache mpm-itk
To manage notifications about this bug go to:
Happens with ubuntu 14.04 LTS mounting shares from Windows 7. Just
mounting the share with 'gedit smb://mywinserver/mypath/myfile' with no
file manager at all reproduces the bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
Public bug reported:
root@forest-laptop:~# cat /etc/issue
Ubuntu 14.04.1 LTS \n \l
root@forest-laptop:~# uname -a
Linux forest-laptop 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC
2014 i686 i686 i686 GNU/Linux
root@forest-laptop:~# lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Confirmed. It seems to be something to do with xconsole :
one@one-P35:/var/log$ cat syslog|grep pipe
Oct 24 12:17:24 one-P35 rsyslogd-2039: Could no open output pipe
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 24 12:26:58 one-P35 kernel: [ 24.812375]
Public bug reported:
I have an utterly reproducible segfault with php5-fpm 5.5.9+dfsg-
1ubuntu4.4.
Here are the top 4 backtrace frames. It looks to these relatively naive
eyes like there's memory corruption in cwd, resolved_path, trypath, and
actual_path.
This trace was generated with realpath
This is the core dump.
** Attachment added: core-php5-fpm.16825.bz2
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1385050/+attachment/4243073/+files/core-php5-fpm.16825.bz2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
61 matches
Mail list logo
