[Bug 1287050] Re: No auth_uri in api-paste.conf (Configure a Block Storage Service controller in OpenStack Installation Guide for Ubuntu 12.04 (LTS) - havana)
** Changed in: cinder (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1287050 Title: No auth_uri in api-paste.conf (Configure a Block Storage Service controller in OpenStack Installation Guide for Ubuntu 12.04 (LTS) - havana) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1287050/+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 1287607] [NEW] Invalid opcode on client registration in ADC master role
Public bug reported: System Information: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Package version: samba4: 4.0.3+dfsg1-0.1ubuntu4 samba: 2:4.1.3+dfsg-2ubuntu3 What did I expect to happen: Client auto-registration when running samba as active directory master works What happened instead: Client could not register (active directory master could not perform operation) Additional information: /var/log/messages contains information about a trap kernel: [ 155.531461] traps: samba[956] trap invalid opcode ip:7f55b1e328de sp:7fff834b9c38 error:0 in libHDB_SAMBA4.so.0[7f55b1e31000+2000] Remedy: As a solution I downloaded the newer 2:4.1.5+dfsg-1 from https://packages.debian.org/sid/samba and compiled from source. The bug did not occur, clients were successfully able to register ** Affects: samba4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba4 in Ubuntu. https://bugs.launchpad.net/bugs/1287607 Title: Invalid opcode on client registration in ADC master role To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1287607/+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 882878]
This is an autogenerated message for OBS integration: This bug (712683) was mentioned in https://build.opensuse.org/request/show/224303 Factory / openssh -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/882878 Title: With IPv6 disabled, openssh will not forward X connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/882878/+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 1286194] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.2: openvswitch kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openvswitch (Ubuntu) Status: New = Confirmed -- 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/1286194 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.2: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1286194/+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 834930] Re: Need a way to manage SSH keys in a juju environment.
** Tags added: canonical-is -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/834930 Title: Need a way to manage SSH keys in a juju environment. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/834930/+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 1278466] Re: [FFe] ceph firefly 0.78.1 stable update
** Summary changed: - [FFe] ceph firefly stable update + [FFe] ceph firefly 0.78.1 stable update -- 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/1278466 Title: [FFe] ceph firefly 0.78.1 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1278466/+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 1287666] [NEW] qemu-nbd processes left behind after instance deletion
You have been subscribed to a public bug: We have a couple of nova compute nodes which have ended up with a load of qemu-nbd processes: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 24365 root 20 0 364m 2304 988 R 86 0.0 445:23.55 qemu-nbd 10512 root 20 0 363m 2044 924 R 70 0.0 512:55.08 qemu-nbd 28618 root 20 0 294m 2292 980 R 66 0.0 255:53.59 qemu-nbd 31353 root 20 0 294m 2300 984 R 65 0.0 254:18.38 qemu-nbd 12326 root 20 0 289m 2028 920 R 65 0.0 451:57.23 qemu-nbd 1031 root 20 0 361m 2040 920 R 64 0.0 253:19.43 qemu-nbd 28248 root 20 0 291m 2032 924 R 64 0.0 442:52.39 qemu-nbd 5999 root 20 0 294m 2292 984 R 64 0.0 198:28.80 qemu-nbd 28179 root 20 0 291m 2028 920 R 64 0.0 256:06.30 qemu-nbd 13010 root 20 0 291m 2036 924 R 62 0.0 512:27.49 qemu-nbd 18671 root 20 0 300m 2292 988 R 61 0.0 449:27.23 qemu-nbd Looking at these processes, most of them refer to instances that no longer exist: # ps -ef | fgrep 10512 root 10512 1 80 00:35 ?08:34:07 /usr/bin/qemu-nbd -c /dev/nbd9 /srv/nova/instances/baf8f430-2a6d-4fee-82d3-12d2a0db32e5/disk # ls -l /srv/nova/instances/baf8f430-2a6d-4fee-82d3-12d2a0db32e5/disk ls: cannot access /srv/nova/instances/baf8f430-2a6d-4fee-82d3-12d2a0db32e5/disk: No such file or directory There are no obvious errors in the logs to suggest anything went wrong. This is version 1:2013.2.1-0ubuntu1~cloud0 running on precise. Bug #1250231 appears to be describing something very similar if it helps in any way. ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- qemu-nbd processes left behind after instance deletion https://bugs.launchpad.net/bugs/1287666 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova 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 1287666] Re: qemu-nbd processes left behind after instance deletion
** Project changed: nova = nova (Ubuntu) -- 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/1287666 Title: qemu-nbd processes left behind after instance deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1287666/+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 1262225] Re: openvswitch 1.4.6 is not compatible with the 3.11 saucy HWE kernel
** Also affects: openvswitch-lts-saucy (Ubuntu) Importance: Undecided Status: New ** Changed in: openvswitch-lts-saucy (Ubuntu Precise) Status: New = In Progress ** Changed in: openvswitch-lts-saucy (Ubuntu Precise) Importance: Undecided = High ** Changed in: openvswitch-lts-saucy (Ubuntu Precise) Assignee: (unassigned) = James Page (james-page) ** Changed in: openvswitch-lts-saucy (Ubuntu) Status: New = Invalid ** Changed in: openvswitch (Ubuntu Precise) Status: Triaged = Won't Fix -- 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/1262225 Title: openvswitch 1.4.6 is not compatible with the 3.11 saucy HWE kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1262225/+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 1287706] [NEW] [ffe] Please sync or merge bind9 9.9.5 from Debian
*** This bug is a security vulnerability *** Public security bug reported: Bind 9.9.5 is an Extended Support Version (ESV) of bind9, which means it will be supported by ISC for a period of 4 years. I would like our LTS release to get an ESV version of bind9 so our maintenance and security support will be easier. I don't believe upgrading from 9.9.3 would pose any issue at this period in the development cycle as it is a minor update. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1287706 Title: [ffe] Please sync or merge bind9 9.9.5 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1287706/+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 1287706] Re: [ffe] Please sync or merge bind9 9.9.5 from Debian
FFe approved and synced, as all our delta appears to be in Debian now. ** Changed in: bind9 (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1287706 Title: [ffe] Please sync or merge bind9 9.9.5 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1287706/+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 1287726] [NEW] Wrong evaluation whether json is valid or not
Public bug reported: # php -r 'var_dump(json_decode(\\xff\));' string(1) � Should be: # php -r 'var_dump(json_decode(\\xff\));' NULL Since a large (and growing) number of services use JSON for communication, it's quite bad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: php5-json 1.3.2-2build1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 14:34:43 2014 Ec2AMI: ami-8df705fa Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: c3.xlarge Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: php-json UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php-json (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287730] [NEW] openldap segfault on startup with delta-syncrepl MMR
Public bug reported: We have setup a LDAP master-master replication using delta-sync. On the 2-node cluster, one server fail to restart with a segfault immediately after the startup. Every time we restart the server, it fail with: /# slapd -u openldap -g openldap -d stats -f /etc/ldap/slapd.conf 5315e2a1 @(#) $OpenLDAP: slapd (Sep 19 2013 22:39:38) $ buildd@panlong:/build/buildd/openldap-2.4.28/debian/build/servers/slapd 5315e2a1 hdb_db_open: database cn=accesslog: unclean shutdown detected; attempting recovery. 5315e2a3 hdb_db_open: database dc=qa,dc=example,dc=net: unclean shutdown detected; attempting recovery. 5315e2a6 = bdb_inequality_candidates: (entryCSN) not indexed 5315e2db slapd starting Segmentation fault (core dumped) On syslog: slapd[4506]: segfault at 5e ip 7f13dd954f29 sp 7f13c0a4c800 error 4 in slapd[7f13dd8bb000+128000] Using a coredump and slapd-dbg, the stacktrace of segfault is: #0 syncrepl_op_modify (op=0x7f13c0a4d280, rs=optimized out) at ../../../../servers/slapd/syncrepl.c:2132 #1 0x7f13dd9640fa in overlay_op_walk (op=0x7f13c0a4d280, rs=0x7f13c0a4cd50, which=op_modify, oi=0x7f13de46e2f0, on=optimized out) at ../../../../servers/slapd/backover.c:661 #2 0x7f13dd9642bb in over_op_func (op=0x7f13c0a4d280, rs=optimized out, which=optimized out) at ../../../../servers/slapd/backover.c:723 #3 0x7f13dd956b6f in syncrepl_message_to_op (si=0x7f13de46f390, op=0x7f13c0a4d280, msg=0x7f13a8109660) at ../../../../servers/slapd/syncrepl.c:2316 #4 0x7f13dd95b6ad in do_syncrep2 (si=0x7f13de46f390, op=0x7f13c0a4d280) at ../../../../servers/slapd/syncrepl.c:986 #5 do_syncrepl (ctx=optimized out, arg=0x7f13de46f180) at ../../../../servers/slapd/syncrepl.c:1522 #6 0x7f13dd4559aa in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x7f13dc38de9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f13dc0ba3fd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x in ?? () This bug look really like upstream bug ITS#7354 [1] : * failure at same function, at same line (same if ( ml-sml_flags == SLAP_MOD_INTERNAL )) * same wrong value in ml variable (0x40) * same setup as title in ITS ticket (delta-syncrepl with master-master) I don't know how to reproduce the situation, so it's pretty hard to do test. The fix for this issue is very short, it's a one line fix [2]. Note: If the one-line fix is not backported, another solution could be to update openldap version to 2.4.33, which include this fix. Sadly trusty only have 2.4.31. [1]: http://www.openldap.org/its/index.cgi/Software%20Bugs?id=7354;selectid=7354;usearchives=1 [2]: http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=3f71f756013a61b6a3cf7c529e1ec42675f5e040 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1287730 Title: openldap segfault on startup with delta-syncrepl MMR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1287730/+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 1230917] Re: php5-fpm logrotate errors after package switched to upstart
php5-5.4 from php5-oldstable doesn't have an upstart script, so this bug is not there. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1230917 Title: php5-fpm logrotate errors after package switched to upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+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 1262225] Re: openvswitch 1.4.6 is not compatible with the 3.11 saucy HWE kernel
** Tags added: verfication-needed ** Tags removed: verfication-needed ** Tags added: verification-needed -- 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/1262225 Title: openvswitch 1.4.6 is not compatible with the 3.11 saucy HWE kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1262225/+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 1287772] [NEW] cannot deploy trusty
Public bug reported:
Using cloud-tools archive (same is true for saucy), I tried to deploy trusty,
and go tthe api error back:
{distro_series: [Value u'trusty' is not a valid choice.]}
We should be able to deploy trusty using a stable release right now
(cloud tools or 13.04).
upstream commit that did that was revno 1789.1.1
=== modified file 'etc/maas/import_pxe_files'
--- etc/maas/import_pxe_files 2013-10-24 03:00:39 +
+++ etc/maas/import_pxe_files 2013-12-17 20:01:13 +
@@ -12,7 +12,7 @@
fi
-#RELEASES=precise quantal raring saucy
+#RELEASES=precise quantal raring saucy trusty
#ARCHES=amd64/generic i386/generic armhf/highbank armhf/generic
#LOCALE=en_US
#IMPORT_EPHEMERALS=1
=== modified file 'src/maasserver/enum.py'
--- src/maasserver/enum.py 2013-10-07 09:12:40 +
+++ src/maasserver/enum.py 2013-12-17 20:01:13 +
@@ -146,6 +146,8 @@
raring = 'raring'
#:
saucy = 'saucy'
+#:
+trusty = 'trusty'
DISTRO_SERIES_CHOICES = (
(DISTRO_SERIES.default, 'Default Ubuntu Release'),
@@ -153,6 +155,7 @@
(DISTRO_SERIES.quantal, 'Ubuntu 12.10 Quantal Quetzal'),
(DISTRO_SERIES.raring, 'Ubuntu 13.04 Raring Ringtail'),
(DISTRO_SERIES.saucy, 'Ubuntu 13.10 Saucy Salamander'),
+(DISTRO_SERIES.trusty, 'Ubuntu 14.04 LTS Trusty Tahr'),
)
** Affects: cloud-archive
Importance: Medium
Status: Confirmed
** Affects: maas (Ubuntu)
Importance: Medium
Status: Fix Released
** Affects: maas (Ubuntu Saucy)
Importance: Medium
Status: Confirmed
** Also affects: maas (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Fix Released
** Changed in: maas (Ubuntu Saucy)
Status: New = Confirmed
** Changed in: maas (Ubuntu Saucy)
Importance: Undecided = Medium
** Changed in: cloud-archive
Status: New = Confirmed
** Changed in: cloud-archive
Importance: Undecided = Medium
** Changed in: maas (Ubuntu)
Importance: Undecided = Medium
--
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/1287772
Title:
cannot deploy trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1287772/+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 1278897] Re: dovecot warns about moved ssl certs on upgrade
** Changed in: dovecot (Ubuntu Trusty) Assignee: (unassigned) = James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1278897 Title: dovecot warns about moved ssl certs on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1278897/+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 1262225] Re: openvswitch 1.4.6 is not compatible with the 3.11 saucy HWE kernel
Hello James, or anyone else affected, Accepted into precise-proposed. The package will build now and be available in a few hours in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: openvswitch-lts-saucy (Ubuntu Precise) Status: In Progress = Fix Committed -- 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/1262225 Title: openvswitch 1.4.6 is not compatible with the 3.11 saucy HWE kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1262225/+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 1287730] Re: openldap segfault on startup with delta-syncrepl MMR
I've attached the debdiff patch for trusty. I'm building a backport for precise to test if slapd can start with this patch applied (the server on which the issue occure is running precise). ** Patch added: lp1287730.debdiff https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1287730/+attachment/4006937/+files/lp1287730.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1287730 Title: openldap segfault on startup with delta-syncrepl MMR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1287730/+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 1244713] Re: invalid syntax for check_ssh plugin
** Tags added: saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1244713 Title: invalid syntax for check_ssh plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1244713/+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
[Blueprint servercloud-1311-openstack] Openstack Next Steps
Blueprint changed by Chuck Short: Work items changed: Work items for ubuntu-13.11: Setup Trusty Icehouse in Openstack-CI: DONE Setup Precise Icehouse in Openstack-CI: DONE Write MIR report for httpretty: INPROGRESS Write MIR report for mox3: INPROGRESS Setup staging PPA for precise icehouse: DONE Write MIR report for python-librabbitmq: DONE Write MIR report for librabbitmq: DONE Write MIR report beanstalkc: INPROGRESS Write MIR report for beanstalkd: INPROGRESS Porting of clients and oslo-incubator to python3: INPROGRESS Work items for ubuntu-13.12: [zulcss] Update libvirt to 1.2.0: INPROGRESS [zulcss] Package libvirt-python 1.2.0: DONE [zulcss] Sync packages from Trusty to Cloud Archive staging: DONE [zulcss] Package Trove for Ubuntu: DONE [zulcss] Package Savannah for Ubuntu: INPROGRESS Package Ironic for Ubuntu: TODO [zulcss] Package openstack icehouse-1: DONE [james-page] Neutron packaging review and deprecation of old-style plugins - ML2: DONE [james-page] Nova hypervisor packaging review and re-jig to support libvirt-less drivers: DONE [zulcss] Write MIR for mox3: DONE Porting of clients and oslo-incubator to python3: INPROGRESS [smb] MRE work for xen for Precise: DONE [smb] MRE work for xen for Raring: DONE [smb] MRE work for xen for Saucy: DONE [zulcss] Update oslo.messaging to 1.2.0~a11: DONE [zulcss] Package swift 1.11.0: DONE [zulcss] Write MIR for oslo.messaging: DONE [zulcss] Package oslo.rootwrap: DONE [zulcss] Package swift-bench: DONE [zulcss] Package python-designateclient: DONE [zulcss] Package python-workflow: DONE [zulcss] Package python-savannaclient: DONE [zulcss] Add versioned dependency for six for wsme: DONE [zulcss] Write MIR for oslo.rootwrap (#1259985): INPROGRESS [zulcss] Write MIR for python-pycadf (#1259984): INPROGRESS Work items for ubuntu-14.01: [zulcss] Update libvirt to 1.2.0: DONE [zulcss] Update libvirt to 1.2.1: DONE [zulcss] Update libvirt-python to 1.2.1: DONE [zulcss] Sync libvirt-python from Debian Unstable: DONE [zulcss] Write MIR for libvirt-python (#1262758): DONE [zulcss] Write MIR for oslo.rootwrap (#1259985): DONE [zulcss] Write MIR for python-pycadf (#1259984): DONE [james-page] Work out series upgrade with the juju-core team: INPROGRESS [zulcss] Package Savannah for Ubuntu: INPROGRESS [zulcss] Package savanna-extra for Ubuntu: INPROGRESS [zulcss] Package savanna-dashboard for Ubuntu: INPROGRESS [zulcss] Package savanaa-iamge-elements for Ubuntu: INPROGRESS [zulcss] Package python-manillaclient for Ubuntu: DONE [zulcss] Package manilla for Ubuntu: INPROGRESS [zulcss] Package python-savanaclient for Ubuntu: DONE [zulcss] Package swift 1.12.0: INPROGRESS [zulcss] Package Ironic for Ubuntu: DONE [zulcss] Package python-ironicclient: DONE [zulcss] Write MIR for Heat (#1267557): INPROGRESS [james-page] Monitor packaging for docker for Ubuntu/Debian: DONE [james-page] test docker.io (distro) on 14.04 (memcached tutorial tested): DONE [james-page] test lxc-docker (upstream) on 14.04 (memcached tutorial tested): DONE [zulcss] Write tools to integrate trusty testing upstream: INPROGRESS [zulcss] have non-voting ci-gate tests running on trusty: INPROGRESS [zulcss] Write tools to integrate libvirt-lxc testing upstream: INPROGRESS Discuss contribution of Juju/OpenStack documentation upstream (annegentle): TODO [zulcss] Package python-pyghmi: DONE [zulcss] Package openstack icehouse-2: DONE [zulcss] Prep cloud archive for icehouse-2: INPROGRESS [zulcss] Write MIR for python-taskflow(#1271617): DONE [zulcss] Write MIR for python-concurrent.futures (#1271606): DONE [zulcss] Write MIR for python-networkx (#1271609): DONE Porting of clients and oslo-incubator to python3: INPROGRESS Integrate trusty with devstack for 3rd party testing: INPROGRESS Integrate libvirt-lxc with devstack for 3rd party testing: INPROGRESS Work items for ubuntu-14.02: Write MIR for python-qpid: POSTPONED Upgrade path testing and validation from precise-CA-trusty: TODO Package openstack icehouse-3: TODO Porting of clients and oslo-incubator to python3: INPROGRESS [zulcss] Write MIR for Heat (#1267557): INPROGRESS [zulcss] Write tools to integrate trusty testing upstream: INPROGRESS [zulcss] have non-voting ci-gate tests running on trusty: INPROGRESS [zulcss] Write tools to integrate libvirt-lxc testing upstream: INPROGRESS [zulcss] Prep cloud archive for icehouse-2: DONE Integrate trusty with devstack for 3rd party testing: INPROGRESS Integrate libvirt-lxc with devstack for 3rd party testing: INPROGRESS [zulcss] Package Manilla for icehouse-3: DONE [zulcss] Package python-manillacleint for icehouse-3: DONE [zulcss] Package oslo.messaging 1.3.0a7: DONE [zulcss] Perform upgrade testing from E - I: DONE [zulcss] Perform upgrade testing from G - I: TODO [zulcss] Perform upgrade testing from F - I: TODO
[Bug 1287772] Re: cannot deploy trusty
** Branch linked: lp:~smoser/ubuntu/saucy/maas/lp1287772 -- 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/1287772 Title: cannot deploy trusty To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1287772/+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 1240260] Re: juju bootstrap does not honor https_proxy in environment when fetching tools
** Changed in: juju-core Milestone: 1.18.0 = 1.17.3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1240260 Title: juju bootstrap does not honor https_proxy in environment when fetching tools To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240260/+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 1244355] Re: needs to use add-apt-repository for cloud-archive:string
** Branch linked: lp:ubuntu/precise-proposed/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1244355 Title: needs to use add-apt-repository for cloud-archive:string To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1244355/+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 1287840] [NEW] FFE: libvirt-1.2.2
Public bug reported:
This is a rather large release with a few new features including
beginning of support for the BSD hypervisor, and a lot of significant
improvements in various place like linux containers, network storage,
Xen drivers, internals etc ... Also of note the fixes for the LXC security
bug CVE-2013-6456:
Features:
- bhyve: add a basic driver (Roman Bogorodskiy)
- add LXC from native conversion tool (Cédric Bosdonnat)
- vbox: add support for v4.2.20+ and v4.3.4+ (Jean-Baptiste Rouault)
- Introduce Libvirt Wireshark dissector (Yuto KAWAMURA)
Security:
- CVE-2013-6456: Avoid unsafe use of /proc/$PID/root in LXC hotunplug code
(Daniel P. Berrange)
- CVE-2013-6456: Avoid unsafe use of /proc/$PID/root in LXC chardev hostdev
hotplug (Daniel P. Berrange)
- CVE-2013-6456: Avoid unsafe use of /proc/$PID/root in LXC block hostdev
hotplug (Daniel P. Berrange)
- CVE-2013-6456: Avoid unsafe use of /proc/$PID/root in LXC USB hotplug (Daniel
P. Berrange)
- CVE-2013-6456: Avoid unsafe use of /proc/$PID/root in LXC disk hotplug
(Daniel P. Berrange)
- CVE-2013-6456: Avoid unsafe use of /proc/$PID/root in LXC shutdown/reboot
code (Eric Blake)
Documentation:
- bhyve: add basic documentation (Roman Bogorodskiy)
- Add docs about use of systemd journal for logging (Daniel P. Berrange)
- Auto-generate the table of contents in logging doc (Daniel P. Berrange)
- Fix heading level in logging docs (Daniel P. Berrange)
- Document the keyboard as a valid input type (Ján Tomko)
- bandwidth: Adjust documentation (John Ferlan)
- remove auth from secret XML format (Ján Tomko)
- LXC: added some doc on domxml-from-native with mention of limitations (Cédric
Bosdonnat)
- libxl: fix libxlDoDomainSave documentation (Jim Fehlig)
- grammar fixes in formatdomain (Chen Hanxiao)
- maint: fix grammar in conf file (Eric Blake)
- Fix minor typo in governance doc (Justin Clift)
- Write up the project governance process (Daniel P. Berrange)
- man: shm-merge-across-nodes is optional (Ján Tomko)
- docs/page.xls: remove unnecessary namespace attribute (Pavel Hrdina)
- add a permalink to html headers (Dan Kenigsberg)
- storage: Add document for possible problem on volume detection (Osier Yang)
- Add note for node-memory-tune (Osier Yang)
- Improve the document for nodesuspend (Osier Yang)
- refer to the correct event ID for DomainEventIOErrorReasonCallback (Claudio
Bley)
- Add sample output of Wireshark dissector (Yuto KAWAMURA)
- Add missing space in clock documentation (Christophe Fergeau)
Portability:
- build: skip virportallocatortest on cygwin (Eric Blake)
- build: ignore cygwin toolchain droppings (Eric Blake)
- build: avoid ld_preload tests on mingw (Eric Blake)
- build: fix cgroups on non-Linux (Eric Blake)
- build: fix build on 32-bit hosts (Eric Blake)
- maint: update to latest gnulib, for older autoconf (Eric Blake)
- Fix build of portallocator on mingw (Ján Tomko)
- lxc: Don't shadow global symbol link (Peter Krempa)
- storage: Fix build with older compilers afeter gluster snapshot series (Peter
Krempa)
- spec: add missing dep of libvirt-daemon-config-network (Thierry Parmentelat)
- spec: require libvirt-daemon-driver-interface only when built (Thierry
Parmentelat)
- Fixed build with clang. (Cédric Bosdonnat)
- Rename 'index' in virCapabilitiesGetCpusForNode (Ján Tomko)
- qemuxml2argvmock: Mock time() on non-linux platforms too (Michal Privoznik)
- build: Fix 'make rpm' in VPATH with wireshark (Martin Kletzander)
- Remove windows thread implementation in favour of pthreads (Daniel P.
Berrange)
- Fix pthread_sigmask check for mingw32 without winpthreads (Daniel P. Berrange)
- Skip check-augeas-lockd when QEMU is disabled (Daniel P. Berrange)
- maint: add configure checks for BSD CPU affinity (Roman Bogorodskiy)
- BSD: implement virProcess{Get,Set}Affinity (Roman Bogorodskiy)
- tests: Fix PCI test data filenames for Windows (Matthias Bolte)
- wireshark: Fix VPATH build (Jiri Denemark)
- Honour prefix in wireshark install dir (Daniel P. Berrange)
- Use AC_PATH_PROG to search for dmidecode (Roman Bogorodskiy)
Bug fixes:
- bhyve: defined domains should be persistent (Roman Bogorodskiy)
- Fix journald PRIORITY values (Daniel P. Berrange)
- spec: Fix braces around macros (Peter Krempa)
- spec: Use correct versions of libgfapi in RHEL builds (Peter Krempa)
- network: unplug bandwidth and call networkRunHook only when appropriate
(Laine Stump)
- network: don't even call networkRunHook if there is no network (Laine Stump)
- Fix memory leak in virSCSIDeviceListDel() (Nehal J Wani)
- libxl: queue domain event earlier in shutdown handler (Jim Fehlig)
- virsh: mark CPU usage field names as translatable (Ján Tomko)
- virsh: initialize str to NULL to solve a build issue (Chen Hanxiao)
- virsh: Don't leak buffer if GetFDs fails in cmdCreate (Ján Tomko)
- libvirt-guests: Wait for libvirtd to initialize (Michal Privoznik)
- virSystemdCreateMachine: Set dependencies for slices (Michal Privoznik)
- Ignore additional fields in iscsiadm
[Bug 1287841] [NEW] FFE: libvirt-python 1.2.2
Public bug reported: 2014-02-20 Martin Kletzander mklet...@redhat.com generator: Skip exporting only sentinels When enum type has '_LAST' in its name, but is not the last type in that enum, it's skipped even though it shouldn't be. Currently, this is the case for only VIR_NETWORK_UPDATE_COMMAND_ADD_LAST inside an enum virNetworkUpdateCommand. Also, since _LAST types can have other enums instead of values, that needs to be filtered out using a try-except when converting the value. 2014-02-13 Philipp Hahn h...@univention.de Fix stream related spelling mistakes Consistent spelling of all-uppercase I/O. 2014-02-12 Eric Blake ebl...@redhat.com examples: demonstrate network events Commit 6ea5be0 added network event callback support, so we might as well demonstrate that it works by updating our example. * examples/event-test.py: Add network event, fix typos. 2014-02-04 Eric Blake ebl...@redhat.com maint: ignore editor files * .gitignore: Exclude emacs cruft. ** Affects: libvirt-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt-python in Ubuntu. https://bugs.launchpad.net/bugs/1287841 Title: FFE: libvirt-python 1.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1287841/+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 1230917] Re: php5-fpm logrotate errors after package switched to upstart
yeah, woops. I did apt-add-repository ppa:ondrej/php5-oldstable, but apparently it redirects to ondrej/php5 without me realizing it. I do appreciate the new upstart style approach to the init script, that was a great change. I was concerned converting initscripts to upstart would lose custom actions and things like reload (which I see is commented out currently) That's unrelated to this though. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1230917 Title: php5-fpm logrotate errors after package switched to upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+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 1287730] Re: openldap segfault on startup with delta-syncrepl MMR
The attachment lp1287730.debdiff seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1287730 Title: openldap segfault on startup with delta-syncrepl MMR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1287730/+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 1254111] Re: MAAS tft server lacks uEFI netboot files.
** Changed in: maas Assignee: (unassigned) = Blake Rouse (blake-rouse) -- 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/1254111 Title: MAAS tft server lacks uEFI netboot files. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1254111/+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 1287879] Re: fatal error running test suite on arm64
** Also affects: gccgo-go (Ubuntu) Importance: Undecided Status: New ** Description changed: The following was seen running the juju-core unittests on an arm64 - instance. The I substituted gccgo-4.9 gccgo-go for golang and juju- + instance. I substituted gccgo-4.9 gccgo-go for golang and juju- mongodb for mongodb-server $ make check go test launchpad.net/juju-core/... oklaunchpad.net/juju-core 11.164s unexpected fault address 0x3e8167b fatal error: fault [signal 0xb code=0x1 addr=0x3e8167b] goroutine 8 [running]: - :0 + :0 - :0 + :0 - :0 + :0 - :0 + :0 - :0 + :0 - :0 + :0 created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 1 [semacquire]: main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:744 main.runTest - /build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508 + /build/buildd/gccgo-go-1.2/src/cmd/go/test.go:508 main.main - /build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161 + /build/buildd/gccgo-go-1.2/src/cmd/go/main.go:161 goroutine 3 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 5 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 6 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 7 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 9 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 10 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 11 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 12 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable created by main.do.pN12_main.builder - /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 + /build/buildd/gccgo-go-1.2/src/cmd/go/build.go:722 goroutine 246 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 213 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 240 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 255 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 235 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 251 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable goroutine 256 [runnable]: goroutine 33 [runnable]: goroutine 94 [chan receive]: main.$nested29 - /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:21 + /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:21 created by main.processSignals - /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:20 + /build/buildd/gccgo-go-1.2/src/cmd/go/signal.go:20 goroutine 254 [syscall]: - goroutine in C code; stack unavailable + goroutine in C code; stack unavailable make: *** [check] Error 2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gccgo-go in Ubuntu. https://bugs.launchpad.net/bugs/1287879 Title: fatal error running test suite on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1287879/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 1287943] [NEW] vm-builder needs trusty suite
Public bug reported: When using vm-builder it should be able to specify 'trusty' as a suite. ** Affects: vm-builder (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
** Description changed: + [Impact] When using vm-builder it should be able to specify 'trusty' as a suite. + + [Test Case] + sudo vmbuilder kvm ubuntu --suite trusty + + [Regression Potential] + This just adds another release name. ** Also affects: vmbuilder Importance: Undecided Status: New ** Changed in: vmbuilder Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: vm-builder (Ubuntu) Assignee: (unassigned) = Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
Thanks for submitting this bug. ** Changed in: vm-builder (Ubuntu) Importance: Undecided = High ** Changed in: vm-builder (Ubuntu) Status: New = In Progress ** Also affects: vm-builder (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: vm-builder (Ubuntu Saucy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287943] Re: vm-builder needs trusty suite
** Changed in: vmbuilder Assignee: Chris J Arges (arges) = (unassigned) ** Changed in: vm-builder (Ubuntu) Assignee: Chris J Arges (arges) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287964] [NEW] MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Public bug reported: Beginning with MAAS 1.5+bzr1977-0ubuntu2 and up to today's daily builds (1.5+bzr1977+2064+245~ppa0~ubuntu14.04.1), maas no longer seems to either detect or properly configure the BMCs on Dell PowerEdge servers during enlistment. I've noticed two scenarios: 1) When the system enlists, the enlistment itself appears to work OK, but, when I look at the node in the MAAS WebUI, MAAS tells me that there is no power type set and that I need to set one. 2) The system enlists OK, and node's Power Parameters in the UI appear to be filled out fine. In other words, the correct Power driver is populated as well as the correct IP address for the BMC. I also have a 'maas' power user and generated password. However, if I click 'commission node' nothing happens (i.e. the node doesn't power on). Workarounds: In scenario #1 if I go and fill out the IPMI information by hand for an affected node, then commissioning, etc. works fine after that. In scenario #2 if I change the Power User and Power Password parameters in the UI to what's already on the BMC (i.e. root/calvin), then commissioning, etc. works fine after that. This is the first time in a while that PowerEdge didn't 'just work' with MAAS with regard to power settings. I know there has been some churn in the IPMI department lately for MAAS. I'll be attaching logs for each one of the PowerEdges affected by the respective scenarios. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+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 1287943] Re: vm-builder needs trusty suite
** Changed in: vm-builder (Ubuntu) Status: In Progress = Fix Released ** Changed in: vm-builder (Ubuntu Precise) Status: New = Triaged ** Changed in: vm-builder (Ubuntu Saucy) Status: New = Triaged ** Changed in: vm-builder (Ubuntu Precise) Importance: Undecided = High ** Changed in: vm-builder (Ubuntu Saucy) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1287943 Title: vm-builder needs trusty suite To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1287943/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Here are the logs from a PowerEdge M610, which exhibits scenario #2. Scenario #2 seems to be the most common problem I've been having as of late. If you need logs from the commissioning phase on one of these I can try and grab those, too. ** Attachment added: M610-cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007488/+files/M610-cloud-init.tar.gz ** Description changed: Beginning with MAAS 1.5+bzr1977-0ubuntu2 and up to today's daily builds (1.5+bzr1977+2064+245~ppa0~ubuntu14.04.1), maas no longer seems to either detect or properly configure the BMCs on Dell PowerEdge servers during enlistment. I've noticed two scenarios: 1) When the system enlists, the enlistment itself appears to work OK, but, when I look at the node in the MAAS WebUI, MAAS tells me that there is no power type set and that I need to set one. - - 2) The system enlists OK, and node's Power Parameters in the UI appear to be filled out fine. In other words, the correct Power driver is populated as well as the correct IP address for the BMC. I also have a 'maas' power user and generated password. However, if I click 'commission node' nothing happens (i.e. the node doesn't power on). + 2) The system enlists OK, and node's Power Parameters in the UI appear + to be filled out fine. In other words, the correct Power driver is + populated as well as the correct IP address for the BMC. I also have a + 'maas' power user and a pre-generated password. However, if I click + 'commission node' nothing happens (i.e. the node doesn't power on). Workarounds: - In scenario #1 if I go and fill out the IPMI information by hand for an - affected node, then commissioning, etc. works fine after that. + In scenario #1 if I go and fill out all of the IPMI information by hand + for an affected node, then commissioning, etc. works fine after that. In scenario #2 if I change the Power User and Power Password parameters - in the UI to what's already on the BMC (i.e. root/calvin), then - commissioning, etc. works fine after that. + in the UI from 'maas' and the pre-generated password to what's already + on the BMC (i.e. root/calvin), then commissioning, etc. works fine after + that. This is the first time in a while that PowerEdge didn't 'just work' with MAAS with regard to power settings. I know there has been some churn in the IPMI department lately for MAAS. I'll be attaching logs for each one of the PowerEdges affected by the respective scenarios. -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
I'm attaching the cloud-init logs from a PowerEdge R805, which exhibits scenario #1. ** Attachment added: R805-cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007487/+files/R805-cloud-init.tar.gz -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
** Changed in: maas (Ubuntu) Assignee: (unassigned) = Jason Hobbs (jason-hobbs) -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
I see this on the cloud-init-output.log for the R805: Traceback (most recent call last): File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 309, in module main() File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 276, in main apply_ipmi_user_settings(user_settings) File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 194, in apply_ipmi_user_settings verify_ipmi_user_settings(ipmi_user_number, user_settings) File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 183, in verify_ipmi_user_settings raise IPMIError(message) __main__.IPMIError: IPMI user setting verification failures: for 'Enable_User', expected 'Yes', actual 'None'. This isn't anything that I've seen before and won't be fixed by any recent fixes. I don't see anything immediately wrong in the R610 log - please try that again with tomorrow's daily. ** Changed in: maas (Ubuntu) Status: New = 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+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 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs
@pitti, the version now in ppa should fix your virtfs problem. ** Changed in: qemu (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1285505 Title: [ppa 2.0~git-20140225] SIGABRT with -virtfs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285505/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Please do not file project bugs on the source package, use the maas project instead. ** Also affects: maas Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: In Progress = Invalid ** Changed in: maas Status: New = In Progress ** Changed in: maas Assignee: (unassigned) = Jason Hobbs (jason-hobbs) ** Changed in: maas Importance: Undecided = High -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
** Tags added: server-hwe -- 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+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 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
This bug also affects the source package, so updating accordingly. ** Changed in: maas (Ubuntu) Status: Invalid = 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/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+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 1287992] [NEW] package libisccc90 1:9.9.3.dfsg.P2-4ubuntu1 failed to install/upgrade: paketet libisccc90 är inte redo för att konfigureras kan inte konfigurera (aktuell status är half-installed
Public bug reported: Fresh install cant update ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libisccc90 1:9.9.3.dfsg.P2-4ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Mar 5 01:44:00 2014 DuplicateSignature: package:libisccc90:1:9.9.3.dfsg.P2-4ubuntu1:paketet libisccc90 är inte redo för att konfigureras kan inte konfigurera (aktuell status är half-installed) ErrorMessage: paketet libisccc90 är inte redo för att konfigureras kan inte konfigurera (aktuell status är half-installed) InstallationDate: Installed on 2014-03-05 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: bind9 Title: package libisccc90 1:9.9.3.dfsg.P2-4ubuntu1 failed to install/upgrade: paketet libisccc90 är inte redo för att konfigureras kan inte konfigurera (aktuell status är half-installed) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1287992 Title: package libisccc90 1:9.9.3.dfsg.P2-4ubuntu1 failed to install/upgrade: paketet libisccc90 är inte redo för att konfigureras kan inte konfigurera (aktuell status är half-installed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1287992/+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 1204456] Re: neutron ml2 plugin test failures
It is tricky in my venv environment. take neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled as an example, using $./run_tests.sh neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled (testr) would run okay, while using $./run_tests.sh -d neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled (testtools.run) would report following error: File /home/stack/neutron/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py, line 331, in do_execute cursor.execute(statement, parameters) OperationalError: (OperationalError) no such table: ml2_vlan_allocations u'SELECT ml2_vlan_allocations.physical_network AS ml2_vlan_allocations_physical_network, ml2_vlan_allocations.vlan_id AS ml2_vlan_allocations_vlan_id, ml2_vlan_allocations.allocated AS ml2_vlan_allocations_allocated \nFROM ml2_vlan_allocations' () -- 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/1204456 Title: neutron ml2 plugin test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1204456/+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 1259860] Re: Apparmor doesn't allow volume to attach in 13.10 Ubuntu
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1259860 Title: Apparmor doesn't allow volume to attach in 13.10 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1259860/+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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
** Description changed:
We've been seeing a lot of instances simply vanish from the network.
Usually people have been willing to work around this by simply rebooting
or re-creating their instances, but it's troubling for long-running
instances (especially those that have volumes associated).
Here's the relevant bit of nova-network.log for one of these:
- 2012-07-16 14:06:32 DEBUG nova.rpc.amqp [-] received {u'_context_roles':
[u'admin'], u'_context_request_id':
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', u'_context_read_deleted': u'no',
u'args': {u'address': u'10.55.60.141'}, u'_context_auth_token': 'SANITIZED',
u'_context_is_admin': True, u'_context_project_id': None,
u'_context_timestamp': u'2012-07-16T14:06:32.169100', u'_context_user_id':
None, u'method': u'release_fixed_ip', u'_context_remote_address': None} from
(pid=493) _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
- 2012-07-16 14:06:32 DEBUG nova.rpc.amqp
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] unpacked context:
{'user_id': None, 'roles': [u'admin'], 'timestamp':
'2012-07-16T14:06:32.169100', 'auth_token': 'SANITIZED', 'remote_address':
None, 'is_admin': True, 'request_id':
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', 'project_id': None,
'read_deleted': u'no'} from (pid=493) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
- 2012-07-16 14:06:32 DEBUG nova.network.manager
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] Released IP |10.55.60.141|
from (pid=493) release_fixed_ip
/usr/lib/python2.7/dist-packages/nova/network/manager.py:1260
+ 2012-07-16 14:06:32 DEBUG nova.rpc.amqp [-] received {u'_context_roles':
[u'admin'], u'_context_request_id':
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', u'_context_read_deleted': u'no',
u'args': {u'address': u'10.55.60.141'}, u'_context_auth_token': 'SANITIZED',
u'_context_is_admin': True, u'_context_project_id': None,
u'_context_timestamp': u'2012-07-16T14:06:32.169100', u'_context_user_id':
None, u'method': u'release_fixed_ip', u'_context_remote_address': None} from
(pid=493) _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
+ 2012-07-16 14:06:32 DEBUG nova.rpc.amqp
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] unpacked context:
{'user_id': None, 'roles': [u'admin'], 'timestamp':
'2012-07-16T14:06:32.169100', 'auth_token': 'SANITIZED', 'remote_address':
None, 'is_admin': True, 'request_id':
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', 'project_id': None,
'read_deleted': u'no'} from (pid=493) _safe_log
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
+ 2012-07-16 14:06:32 DEBUG nova.network.manager
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] Released IP |10.55.60.141|
from (pid=493) release_fixed_ip
/usr/lib/python2.7/dist-packages/nova/network/manager.py:1260
Then the dhcpbridge shows it being revoked:
- 2012-07-16 14:04:29 DEBUG nova.dhcpbridge [-] Called 'old' for mac
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=23699) main
/usr/bin/nova-dhcpbridge:113
- 2012-07-16 14:06:32 DEBUG nova.dhcpbridge [-] Called 'del' for mac
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=24946) main
/usr/bin/nova-dhcpbridge:113
+ 2012-07-16 14:04:29 DEBUG nova.dhcpbridge [-] Called 'old' for mac
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=23699) main
/usr/bin/nova-dhcpbridge:113
+ 2012-07-16 14:06:32 DEBUG nova.dhcpbridge [-] Called 'del' for mac
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=24946) main
/usr/bin/nova-dhcpbridge:113
Is there any way we can find out what might have placed the
release_fixed_ip event on the message queue? There doesn't seeem to be
any other mention of the IP in the nova logs on any of our systems.
--
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/1026621
Title:
nova-network gets release_fixed_ip events from someplace, but the
database still keeps them associated with instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1026621/+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 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs
Confirmed, this works now. Thanks! Closing, as this only affected the PPA. ** Changed in: qemu (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1285505 Title: [ppa 2.0~git-20140225] SIGABRT with -virtfs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285505/+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
