[Bug 1564187] [NEW] issue with conditional in postinst
Public bug reported: I received the following message when upgrading cloud-init in Ubuntu Xenial: /var/lib/dpkg/info/cloud-init.postinst: 206: /var/lib/dpkg/info/cloud-init.postinst: -f: not found I looked at the script, and there appear to be missing brackets around the test. Specifically, line 206 should probably read: if [ ! -f /var/lib/cloud/instance/obj.pkl ]; then ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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/1564187 Title: issue with conditional in postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1564187/+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 1563697] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build
*** This bug is a duplicate of bug 1500581 *** https://bugs.launchpad.net/bugs/1500581 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1500581, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1500581 open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf) [error: implicit declaration of function ‘nd_set_link’] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1563697 Title: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1563697/+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 1562653] Re: Ubuntu 15.10: QEMU VM hang if memory >= 1T
I mean vm hang when memory >= 1100G (1024G when enable ide cdrom) instead of 1.5G. If disable hpet, the vm will hang at acpi_ex_system_memory_space_handler when memory >= 1100G If disable kvm, vm is good when memory <= 1020G, but also hang when memory >= 1024G. There is no critical information in vm.log: -- 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/1562653 Title: Ubuntu 15.10: QEMU VM hang if memory >= 1T To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1562653/+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 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
Hi, this should be fixed in libvirt 1.3.1-1ubuntu8. I'm not sure why it didn't get auto-closed. Please report if this is stlil broken for you. ** Changed in: libvirt (Ubuntu) Status: Triaged => Fix Released -- 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/1393842 Title: libvirt does not grant qemu-guest-agent channel perms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+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 1515768] Re: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy
** No longer affects: heat -- 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/1515768 Title: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1515768/+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 1536331] Re: Precise to Trusty live migration failing
Ok, so two things I've found are that 1. tcg emulated vms can't be migrated (this doesn't apply to you) 2. pc-1.0-qemu-kvm as the source machine type doesn't actually work. What works for me is when i set the machine type to pc-1.0, then set allow_incoming_qemukvm=1 in /etc/libvirt/qemu.conf on the target host. Can you try and see whether that helps in your case? -- 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/1536331 Title: Precise to Trusty live migration failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1536331/+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 1545913] Re: [FFe] juju-core 2.0
Adam has built the initial version desired for upload: https://launchpad.net/~adam-stokes/+archive/ubuntu/juju-pkg -- 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/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1564124] Re: puts 'golang-defaults' in built-using, not golang-1.6
This bug was fixed in the package dh-golang - 1.12ubuntu1 --- dh-golang (1.12ubuntu1) xenial; urgency=medium * Follow /usr/bin/go symlink when computing Built-Using. (LP: #1564124) -- Michael Hudson-DoyleThu, 31 Mar 2016 11:42:07 +1300 ** Changed in: dh-golang (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dh-golang in Ubuntu. https://bugs.launchpad.net/bugs/1564124 Title: puts 'golang-defaults' in built-using, not golang-1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1564124/+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 1556308] Re: [FFe] Please merge unbound 1.58-1 from Debian unstable
** Description changed: + FFe justification: + + The largest changes are in 1.5.7-1 -> 1.5.7-2, which allows for end + users to use unbound without configuring /etc/default/unbound in the + general case. Additionally, some chroot cruft in debian as been cleaned + up. + + Removing the default file also makes it easier to support all init + systems. + + Notable new features: + + * Support RFC7686: handle ".onion" Special-Use Domain. It is blocked by + default, and can be unblocked with "nodefault" localzone config. + + Notable bug fixes: + + * Fix that NSEC3 negative cache is used when there is no salt. + * wait for sendto to drain socket buffers when they are full. + * Fix: Swig should not be invoked with CPPFLAGS. (paves the way for reproducible builds) + * Squelch 'cannot assign requested address' log messages unless verbosity is high, it was spammed after network down. + * Fix: Do not log an error when the PID file cannot be chown'ed. (Remove the use of some capabilities, helps with Apparmor) + * iana portlist update + + The other changes are mostly compatibility fixes for netbsd and osx. + + Many thanks to Simon for helping analyze the upstream changelog and + testing. + + --- + unbound (1.5.8-1ubuntu1) xenial; urgency=medium * Merge from Debian unstable (LP: #1556308): - Revert dnstap support (dependencies not in main) -- Nishanth AravamudanFri, 11 Mar 2016 14:49:39 -0800 ** Attachment added: "unbound_changelog" https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1556308/+attachment/4617747/+files/unbound_changelog -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1556308 Title: [FFe] Please merge unbound 1.58-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1556308/+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 1556308] Re: [FFe] Please merge unbound 1.58-1 from Debian unstable
** Summary changed: - Please merge unbound 1.58-1 from Debian unstable + [FFe] Please merge unbound 1.58-1 from Debian unstable -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1556308 Title: [FFe] Please merge unbound 1.58-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1556308/+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 1562918] Re: cloud-init does not create defined users
** Branch linked: lp:~smoser/cloud-init/trunk.1562918 -- 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/1562918 Title: cloud-init does not create defined users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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 1562918] Re: cloud-init does not create defined users
Leander, I'd appreciate you giving the linked branch a test if you're up for it. I dont have time at the moment and probably wont until next week. You can either build a deb with: ./packages/bddeb or just apply the diff (copy in the new cloudinit/distros/__init__.py Thanks. -- 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/1562918 Title: cloud-init does not create defined users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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 1564168] [NEW] juju list-credentials --show-secrets does not display passwords
Public bug reported: juju list-credentials --show-secrets does not display password data, unless used with --format yaml. The following commands all fail to show additonal information using --show-secrets juju list-credentials --show-secrets juju list-credentials --format json --show-secrets juju list-credentials --format tabular --show-secrets When used with --format yaml, --show-secrets works. juju list-credentials --format yaml --show-secrets ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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/1564168 Title: juju list-credentials --show-secrets does not display passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564168/+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 1564165] [NEW] Credentials file displays unhelpful message for syntax errors
Public bug reported: If credentials.yaml contains invalid syntax, the error is ERROR credentials.blarhg.google.credentials: expected string, got map which does not accurately convey 'blarhg' is not valid syntax. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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/1564165 Title: Credentials file displays unhelpful message for syntax errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564165/+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 1564163] [NEW] environment name in credentials file is not a tag
Public bug reported: It would be nice to include a tag of the environment name from my credentials file. aws: default-credential: balloons balloons: auth-type: access-key access-key: XXXxxx secret-key: xxx Given those credentials, I expect newly launched instance on aws to be tagged with 'balloons'. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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/1564163 Title: environment name in credentials file is not a tag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564163/+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 1562918] Re: cloud-init does not create defined users
Leander, Thanks for the bug report. Sorry for the regression. I suspect that you can work around the issue by just putting your user into a group. Ie, you add 2 groups, but your user is not in either one of them. We'll get this fixed. -- 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/1562918 Title: cloud-init does not create defined users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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
Re: [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Just to be sure before I mark this as affecting upstream, could you try adding more memory, maybe -m 1024? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1564157] [NEW] juju list-credentials fails to display
Public bug reported: When a cloud is not found in your credentials file, the credentials are not listed. In addition, the credentials error given is confusing, and non-consistent. nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud maas18: cloud maas18 not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud munna-vmaas: cloud munna-vmaas not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud silcoon-vmaas: cloud silcoon-vmaas not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud jujuqa-stack: cloud jujuqa-stack not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud maas19: cloud maas19 not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud silcoon-vmaas: cloud silcoon-vmaas not found nskaggs@pixel:~$ juju list-credentials ERROR removing secrets from credentials for cloud silcoon-vmaas: cloud silcoon-vmaas not found Juju should still list all credentials in the file, as well as displaying a friendly warning about any clouds it cannot find. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- 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/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564157/+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 1563951] Re: Cloud-init does not initialize systemd machine id
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- 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/1563951 Title: Cloud-init does not initialize systemd machine id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Same issue. Stopped on the exact same spot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1564124] [NEW] puts 'golang-defaults' in built-using, not golang-1.6
Public bug reported: This is probably because it's just checking the owner of /usr/bin/go -- instead, it should follow links and report the owner of the ultimate binary. ** Affects: dh-golang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dh-golang in Ubuntu. https://bugs.launchpad.net/bugs/1564124 Title: puts 'golang-defaults' in built-using, not golang-1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1564124/+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 1522890] Re: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
zarej, refer to Bug 1512344 - this is a known problem but it's not something that's able to be fixed. -- 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/1522890 Title: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1522890/+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 1522890] Re: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This is not a bug in `nginx`. You have to shut off any other web server running on port 80 in order to install NGINX and get it to run automatically during setup. You run into the same issues installing Apache when there's another thing running on Port 80. Marking Invalid. ** Changed in: nginx (Ubuntu) Status: Expired => Won't Fix ** Changed in: nginx (Ubuntu) Status: Won't Fix => Invalid ** Changed in: nginx (Ubuntu) Status: Invalid => Won't Fix ** Changed in: nginx (Ubuntu) Status: Won't Fix => Invalid -- 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/1522890 Title: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1522890/+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 1536882] Re: upload golang1.6 package for trusty
I used this package to build docker 1.10 in my ppa: https://launchpad.net/~mwhudson/+archive/ubuntu/scratch/+packages, which seems like an adequate test to me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang-1.6 in Ubuntu. https://bugs.launchpad.net/bugs/1536882 Title: upload golang1.6 package for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1536882/+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 1522890] Re: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I was unable to install nginx package if port 80 was opened. I need to free port 80 in order to install nginx. -- 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/1522890 Title: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1522890/+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 1281758] Re: re-installing maas-region-controller fails
hi all I'm trying upgrading from maas 1.8.2 to the latest 1.9.1 version via apg-get update / upgrade commands and the mass update hangs exactly at: * Stopping web server apache2 * * Restarting PostgreSQL 9.3 database server [ OK ] Syncing... Traceback (most recent call last): File "/usr/sbin/maas-region-admin", line 68, in main() File "/usr/sbin/maas-region-admin", line 64, in main run() File "/usr/sbin/maas-region-admin", line 57, in run management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 415, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 159, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 129, in _cursor self.ensure_connection() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 124, in ensure_connection self.connect() File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 99, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 124, in ensure_connection self.connect() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 112, in connect self.connection = self.get_new_connection(conn_params) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 116, in get_new_connection return Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) django.db.utils.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" -- what is the fix for it for the upgrade of MAAS controller with the trusty release train? -- 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/1281758 Title: re-installing maas-region-controller fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1281758/+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 1555700] Re: Please merge tgt 1.0.63 from Debian (unstable)
This bug was fixed in the package tgt - 1:1.0.63-1ubuntu1 --- tgt (1:1.0.63-1ubuntu1) xenial; urgency=medium * Merge from Debian (LP: #1555700). Remaining changes: - Drop glusterfs support, package not in main. - debian/control - debian/rules - debian/tests/{admin, control, daemon, storage} - debian/tgt-glusterfs.install (Deleted) - Disable AIO backend support: untested new feature - debian/control - debian/tests/storage * Dropped changes - debian/patches/tgtd_dont_fail_on_eacces.patch: included in new release -- Ryan HarperWed, 09 Mar 2016 16:51:44 -0600 ** Changed in: tgt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1555700 Title: Please merge tgt 1.0.63 from Debian (unstable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+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 1545913] Re: [FFe] juju-core 2.0
No, there is no KVM local provider in Juju 2.0. Product management has made the determination that the lxd tool provides the needed functionality for both the lxc and kvm use cases. lxd in Juju 2.0 will be the answer. -- 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/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1545913] Re: [FFe] juju-core 2.0
xnox, there is this bug: https://bugs.launchpad.net/juju- core/+bug/1547665 -- 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/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1564077] Re: ipaddr.IPv4Network object miscalculates network addresses
Looks like the issue can be worked around by calling Supernet() with prefixlen_diff=0 at the end of the computation. I have the impression that blanking the host part and shifting the network mask are done in the wrong order, but I haven't seen the code. New program: from sys import argv import ipaddr ip1 = ipaddr.IPv4Network(argv[1]) ip2 = ipaddr.IPv4Network(argv[2]) print "Testing ", str(ip1), str(ip2) while ip1 != ip2: print ip1,ip2 ip1 = ip1.Supernet() ip2 = ip2.Supernet() print "Ending ", ip2 print "Fixed ending ", ip2.Supernet(prefixlen_diff=0) Results: $ python ipaddr-bug-test.py 10.53.45.24 10.53.45.255 Testing 10.53.45.24/32 10.53.45.255/32 10.53.45.24/32 10.53.45.255/32 10.53.45.24/31 10.53.45.255/31 10.53.45.24/30 10.53.45.254/30 10.53.45.24/29 10.53.45.252/29 10.53.45.24/28 10.53.45.248/28 10.53.45.16/27 10.53.45.240/27 10.53.45.0/26 10.53.45.224/26 10.53.45.0/25 10.53.45.192/25 Ending 10.53.45.128/24 Fixed ending 10.53.45.0/24 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ipaddr in Ubuntu. https://bugs.launchpad.net/bugs/1564077 Title: ipaddr.IPv4Network object miscalculates network addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-ipaddr/+bug/1564077/+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 1546957] Re: [MIR] lua-lpeg, needed by nmap
Override component to main lua-lpeg 0.12.2-1 in xenial amd64: universe/interpreters/optional/100% -> main lua-lpeg 0.12.2-1 in xenial arm64: universe/interpreters/optional/100% -> main lua-lpeg 0.12.2-1 in xenial armhf: universe/interpreters/optional/100% -> main lua-lpeg 0.12.2-1 in xenial i386: universe/interpreters/optional/100% -> main lua-lpeg 0.12.2-1 in xenial powerpc: universe/interpreters/optional/100% -> main lua-lpeg 0.12.2-1 in xenial ppc64el: universe/interpreters/optional/100% -> main lua-lpeg 0.12.2-1 in xenial s390x: universe/interpreters/optional/100% -> main 7 publications overridden. Override component to main lua-lpeg 0.12.2-1 in xenial: universe/interpreters -> main 1 publication overridden. ** Changed in: lua-lpeg (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1546957 Title: [MIR] lua-lpeg, needed by nmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1546957/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)
squid3-3.5.12-1ubuntu3 uploaded already by stgraber handled using the dpkg-maintscript-helper to clean up the old /etc/init.d/squid3 file. This debdiff handles the second task of removing the check on how to restart squid and just calls invoke-rc.d squid restart unconditionally. I've tested this in a wily -> xenial upgrade, as well as a trusty -> xenial upgrade; squid, squidGuard, and squid-deb-proxy work as expected after upgrading to 1ubuntu4 version. ** Patch added: "drop-version-check-service-restart.debdiff" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4617474/+files/drop-version-check-service-restart.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1473691 Title: [FFe] squid: Update to latest upstream release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1564077] [NEW] ipaddr.IPv4Network object miscalculates network addresses
Public bug reported: When using the IPv4Network.Supernet() call, the resulting address is calculated incorrectly. Instead of presenting the all-zeros address in the host part, the first bit of the host part is kept as it was, causing an incorrect address to be displayed. This only appears to be a display issue, the network objects behave as they should (at least for the equality operator). The following python program can be used to see the issue. from sys import argv import ipaddr ip1 = ipaddr.IPv4Network(argv[1]) ip2 = ipaddr.IPv4Network(argv[2]) print "Testing ", str(ip1), str(ip2) while ip1 != ip2: print ip1,ip2 ip1 = ip1.Supernet() ip2 = ip2.Supernet() print "Ending ", ip2 This program takes two addresses and attempts to find the network in common, using the Supernet call to locate it. However, below is the output of the program. $ python ipaddr-bug-test.py 10.53.45.24 10.53.45.255 Testing 10.53.45.24/32 10.53.45.255/32 10.53.45.24/32 10.53.45.255/32 10.53.45.24/31 10.53.45.255/31 10.53.45.24/30 10.53.45.254/30 10.53.45.24/29 10.53.45.252/29 10.53.45.24/28 10.53.45.248/28 10.53.45.16/27 10.53.45.240/27 10.53.45.0/26 10.53.45.224/26 10.53.45.0/25 10.53.45.192/25 Ending 10.53.45.128/24 Note how the program correctly shows the /32 addresses, but when getting the supernet for the second address, it mistakenly shows 10.53.45.255/31 when the correct value should have been 10.53.45.254/31. The same happens in all the stages, and is very obvious when doing the computation on a broadcast address. Finally, the address is constructed with the wrong network address. As for system data, here goes all the data indicated in the submission instructions: $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy python-ipaddr python-ipaddr: Installed: 2.1.10-1 Candidate: 2.1.10-1 Version table: *** 2.1.10-1 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python-ipaddr 2.1.10-1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 30 17:17:20 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-02-29 (29 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: python-ipaddr UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-ipaddr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-ipaddr in Ubuntu. https://bugs.launchpad.net/bugs/1564077 Title: ipaddr.IPv4Network object miscalculates network addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-ipaddr/+bug/1564077/+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
Re: [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Could you try this using upstream qemu? git clone http://git.qemu.org/git/qemu.git cd qemu sudo apt-get -y build-dep qemu ./configure --target-list=ppc64-softmmu make cd ppc64-softmmu ./qemu-system-ppc64 [...] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1546957] Re: [MIR] lua-lpeg, needed by nmap
** Changed in: lua-lpeg (Ubuntu) Status: New => Fix Committed ** Changed in: lua-lpeg (Ubuntu) Assignee: Ubuntu Server Team (ubuntu-server) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1546957 Title: [MIR] lua-lpeg, needed by nmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1546957/+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 1563089] Re: Memory Leak when new cluster configuration is formed.
The attachment "Xenial Patch" 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 corosync in Ubuntu. https://bugs.launchpad.net/bugs/1563089 Title: Memory Leak when new cluster configuration is formed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+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 1563551] Re: [FFe] Sync ethtool 1:4.5-1 (main) from Debian testing (main)
** Summary changed: - [FFE] Sync ethtool 1:4.5-1 (main) from Debian testing (main) + [FFe] Sync ethtool 1:4.5-1 (main) from Debian testing (main) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/1563551 Title: [FFe] Sync ethtool 1:4.5-1 (main) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/1563551/+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 1563089] Re: Memory Leak when new cluster configuration is formed.
** Patch added: "Xenial Patch" https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4617458/+files/fix-lp-1563089-xenial.debdiff ** Changed in: corosync (Ubuntu Wily) Status: New => In Progress ** Changed in: corosync (Ubuntu Wily) Importance: Undecided => High ** Changed in: corosync (Ubuntu Wily) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1563089 Title: Memory Leak when new cluster configuration is formed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+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 1546957] Re: [MIR] lua-lpeg, needed by nmap
Ubuntu Server Team now subscribed. ** Changed in: lua-lpeg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1546957 Title: [MIR] lua-lpeg, needed by nmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1546957/+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 584862] Re: libvirt launches dnsmasq for non-dhcp networks.
(Closed per discussion in the rh bug) ** Changed in: libvirt (Ubuntu) Status: Confirmed => Won't Fix -- 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/584862 Title: libvirt launches dnsmasq for non-dhcp networks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/584862/+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 1563089] Re: Memory Leak when new cluster configuration is formed.
** Also affects: corosync (Ubuntu Wily) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1563089 Title: Memory Leak when new cluster configuration is formed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+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 1563089] Re: Memory Leak when new cluster configuration is formed.
** Changed in: corosync (Ubuntu) Status: New => In Progress ** Changed in: corosync (Ubuntu Trusty) Status: New => In Progress ** Changed in: corosync (Ubuntu) Importance: Undecided => High ** Changed in: corosync (Ubuntu Trusty) Importance: Undecided => High ** Changed in: corosync (Ubuntu) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) ** Changed in: corosync (Ubuntu Trusty) Assignee: (unassigned) => Jorge Niedbalski (niedbalski) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1563089 Title: Memory Leak when new cluster configuration is formed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+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 1563089] Re: Memory Leak when new cluster configuration is formed.
** Description changed: [Environment] Trusty 14.04.3 Packages: ii corosync 2.3.3-1ubuntu1 amd64Standards-based cluster framework (daemon and modules) ii libcorosync-common4 2.3.3-1ubuntu1 amd64Standards-based cluster framework, common library [Reproducer] - 1) I deployed an HA environment using this bundle (http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/dev/next-ha.yaml) with a 3 nodes installation of cinder related to an HACluster subordinate unit. $ juju-deployer -c next-ha.yaml -w 600 trusty-kilo 2) I changed the default corosync transport mode to unicast. $ juju set cinder-hacluster corosync_transport=udpu 3) I assured that the 3 units were quorated - cinder/0# corosync-quorumtool + cinder/0# corosync-quorumtool Votequorum information -- Expected votes: 3 Highest expected: 3 Total votes: 3 - Quorum: 2 - Flags:Quorate + Quorum: 2 + Flags:Quorate Membership information -- - Nodeid Votes Name - 1002 1 10.5.1.57 (local) - 1001 1 10.5.1.58 - 1000 1 10.5.1.59 + Nodeid Votes Name + 1002 1 10.5.1.57 (local) + 1001 1 10.5.1.58 + 1000 1 10.5.1.59 The primary unit was holding the VIP resource 10.5.105.1/16 - root@juju-niedbalski-sec-machine-4:/home/ubuntu# ip addr + root@juju-niedbalski-sec-machine-4:/home/ubuntu# ip addr 2: eth0:mtu 1500 qdisc netem state UP group default qlen 1000 - link/ether fa:16:3e:d2:19:6f brd ff:ff:ff:ff:ff:ff - inet 10.5.1.57/16 brd 10.5.255.255 scope global eth0 -valid_lft forever preferred_lft forever - inet 10.5.105.1/16 brd 10.5.255.255 scope global secondary eth0 -valid_lft forever preferred_lft forever + link/ether fa:16:3e:d2:19:6f brd ff:ff:ff:ff:ff:ff + inet 10.5.1.57/16 brd 10.5.255.255 scope global eth0 + valid_lft forever preferred_lft forever + inet 10.5.105.1/16 brd 10.5.255.255 scope global secondary eth0 + valid_lft forever preferred_lft forever 4) I manually added a TC queue for the eth0 interface on the node holding the VIP resource, introducing a 350 ms delay. $ sudo tc qdisc add dev eth0 root netem delay 350ms - 5) Right after adding the 350ms on the cinder/0 unit, the corosync process informs that one of the processors failed, and is forming a new + 5) Right after adding the 350ms on the cinder/0 unit, the corosync process informs that one of the processors failed, and is forming a new cluster configuration. - + Mar 28 21:57:41 juju-niedbalski-sec-machine-5 corosync[4584]: [TOTEM ] A processor failed, forming new configuration. Mar 28 22:00:48 juju-niedbalski-sec-machine-5 corosync[4584]: [TOTEM ] A new membership (10.5.1.57:11628) was formed. Members Mar 28 22:00:48 juju-niedbalski-sec-machine-5 corosync[4584]: [QUORUM] Members[3]: 1002 1001 1000 Mar 28 22:00:48 juju-niedbalski-sec-machine-5 corosync[4584]: [MAIN ] Completed service synchronization, ready to provide service. This happens on all of the units. 6) After receiving this message, I remove the queue from eth0: $ sudo tc qdisk del dev eth0 root netem Then, the following statement is written in the master node: Mar 28 22:00:48 juju-niedbalski-sec-machine-4 corosync[9630]: [TOTEM ] A new membership (10.5.1.57:11628) was formed. Members Mar 28 22:00:48 juju-niedbalski-sec-machine-4 corosync[9630]: [QUORUM] Members[3]: 1002 1001 1000 Mar 28 22:00:48 juju-niedbalski-sec-machine-4 corosync[9630]: [MAIN ] Completed service synchronization, ready to provide service. - - 7) While executing 5 and 6 repeatedly, I ran the following command to track the SZ and RSS memory usage of the + 7) While executing 5 and 6 repeatedly, I ran the following command to track the VSZ and RSS memory usage of the corosync process: root@juju-niedbalski-sec-machine-4:/home/ubuntu# tc qdisc add dev eth0 root netem delay 350ms root@juju-niedbalski-sec-machine-4:/home/ubuntu# tc qdisc del dev eth0 root netem - $ sudo while true; do ps -o sz,rss -p $(pgrep corosync) 2>&1 | grep -E + $ sudo while true; do ps -o vsz,rss -p $(pgrep corosync) 2>&1 | grep -E '.*[0-9]+.*' | tee -a memory-usage.log && sleep 1; done - The results shows that both sz and rss are increased over time at a high - ratio. + The results shows that both vsz and rss are increased over time at a + high ratio. 25476 4036 ... (after 5 minutes). 135644 10352 [Fix] - So preliminary based on this reproducer, I think that this commit (https://github.com/corosync/corosync/commit/600fb4084adcbfe7678b44a83fa8f3d3550f48b9) + So preliminary
[Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)
Debian testing now has the maintenance release 3.5.15. Changes to squid-3.5.15 (23 Feb 2016): - Bug 3870: assertion failed: String.cc: 'len_ + len <65536' in ESI::CustomParser - Fix multiple assertion on String overflows - Fix unit test errors on MacOS - Better handling of huge response headers. Fewer incorrect "Bug #3279" messages. - Log noise reduction for eCAP Changes to squid-3.5.14 (16 Feb 2016): - Bug 4437: Fix Segfault on Certain SSL Handshake Errors - Bug 4431: C code is not compiled with CFLAGS - Bug 4418: FlexibleArray compile error with GCC 6 - Bug 4378: assertion failed: DestinationIp.cc:60: 'checklist->conn() && checklist->conn()->clientConnection != NULL' - Fix invalid FTP connection handling on blocked content - Fix handling of shared memory left over by Squid crashes or bugs - Fix mgr:config report 'qos_flows mark' output - Fix compile error in CPU affinity - Fix %un logging external ACL username - Avoid more certificate validation memory leaks - ... and some documentation updates Changes to squid-3.5.13 (06 Jan 2016): - Bug 4397: DragonFly BSD, POSIX shared memory is implemented as filepath - Bug 4387: Kerberos build errors on Solaris - TLS: Support Ephemeral Elliptic Curve Diffie-Hellman (EECDH) key exchange - TLS: Complete certificate chains using external intermediate certificates - Avoid memory leaks when an X.509 certificate validator is used with SslBump - Fix connection retry and fallback after failed server TLS connections - Fix GnuTLS detection via pkg-config - Fix startup crash with a misconfigured (too-small) shared memory cache - ... and some documentation updates -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1473691 Title: [FFe] squid: Update to latest upstream release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1563393] Re: [FreezeException Needed] Update nginx to 1.9.13.
** Summary changed: - [FFe Needed] Update nginx to 1.9.13. + [FreezeException Needed] Update nginx to 1.9.13. -- 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/1563393 Title: [FreezeException Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Hi, looking at the information in the Description, it looks like you still have /dev/nbd0 attached to the file you're using in qemu. Just to be sure, does this still happen when you disconnect that first? -- 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/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Yes. I only mounted (a different file) to troubleshoot what was going on. The issue was happening before and after mounting. I have since unmounted it. -- 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/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1563887/+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 1563887] [NEW] qemu-system-ppc64 freezes on starting image on ppc64le
You have been subscribed to a public bug by Jon Grimm (jgrimm): qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,2:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,3:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 cpu_cores: Number of cores present = 8 cpu_coreson: Number of cores online = 8 cpu_smt: SMT=8 lscfg_vp: Error: [Errno 2] No such file or directory: 'lscfg' lsmcode: Error: [Errno 2] No such file or directory: 'lsmcode' ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug blocks-hwcert-server ppc64el uec-images xenial --
[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
** Description changed: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. - ubuntu@alpine01:~$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file= - xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio - qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': No such file or directory - ubuntu@alpine01:~$ cd kvm - ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive f - ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio + ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
[Bug 1564043] [NEW] winbindd not able to start on system startup
Public bug reported: I have installed samba, winbind, libpam-winbind, libnss-winbind, kerberos, etc. so that I am able to in principle connect to a Windows Server 2008 R2 active directory controller for AD based logins from Ubuntu. I am able to use wbinfo -i, wbinfo -u, wbinfo -g to get the list of users and see that the connection to the server is working. My smb.conf is also configured for winbind user enum = yes, so that getent passwd and getent group lists those from the server machine (implying nsswitch.conf is also correct). I don't know how to get winbind to start automatically on startup and the apt install scripts didn't do this as expected. The problem is, on startup of Ubuntu 16.04, the winbind service is not started. This prevents logging in via the console, or the lightdm manager with a domain user name and password. I see that: root@leon-ubuntu:/run/systemd/generator.late# systemctl status winbind ● winbind.service - LSB: start Winbind daemon Loaded: loaded (/etc/init.d/winbind; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) root@leon-ubuntu:/run/systemd/generator.late# service winbind status ● winbind.service - LSB: start Winbind daemon Loaded: loaded (/etc/init.d/winbind; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) root@leon-ubuntu:/run/systemd/generator.late# systemctl enable winbind.service winbind.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install enable winbind insserv: warning: current start runlevel(s) (empty) of script `winbind' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `winbind' overrides LSB defaults (0 1 6). insserv: pushd() can not change to directory /etc/init.d: No such file or directory update-rc.d: error: insserv rejected the script header I see no particular log entries in /var/log on startup, so it appears confirmed that Ubuntu doesn't start winbind on startup as one would expect. If I am to manually start the winbind service with: # service winbind start then logging in works fine and everything is good and works as expected. or with: # systemctl winbind start ● winbind.service - LSB: start Winbind daemon Loaded: loaded (/etc/init.d/winbind; bad; vendor preset: enabled) Active: active (running) since Mi 2016-03-30 21:10:34 CEST; 38s ago Docs: man:systemd-sysv-generator(8) Process: 3841 ExecStart=/etc/init.d/winbind start (code=exited, status=0/SUCCE Tasks: 2 (limit: 512) CGroup: /system.slice/winbind.service ├─3860 /usr/sbin/winbindd -d10 └─3861 /usr/sbin/winbindd -d10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: msdfs: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: dmapi: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: registry: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: scavenger: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: dns: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: ldb: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: tevent: 10 Mär 30 21:10:34 leon-ubuntu winbind[3841]: Maximum core file size limits now 167 Mär 30 21:10:34 leon-ubuntu winbind[3841]:...done. Mär 30 21:10:34 leon-ubuntu systemd[1]: Started LSB: start Winbind daemon. The relevant configuration of nsswitch.conf: passwd: compat winbind group: compat winbind shadow: compat The relevant configuration of smb.conf: [global] realm = HOME.LAN workgroup = HOME security = ADS dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab netbios name = leon-ubuntu dns proxy = no #idmap uid = 1-2 #idmap gid = 1-2 idmap config *:backend = tdb idmap config *:range = 2000- idmap config HOME:backend = rid idmap config HOME:schema_mode = rfc2307 idmap config HOME:range = 1-9 idmap config HOME:default = yes winbind nss info = rfc2307 winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes winbind refresh tickets = yes winbind normalize names = yes store dos attributes = yes vfs objects = acl_xattr map acl inherit = yes name resolve order = bcast host lmhosts wins template shell = /bin/bash template homedir = /home/%U client use spnego = yes client ntlmv2 auth = yes encrypt passwords = yes restrict anonymous = 2 usershare max shares = 100 usershare allow guests = yes The results of the file /run/systemd/generator.late/winbind.service is: # Automatically generated by systemd-sysv-generator [Unit] Documentation=man:systemd-sysv-generator(8) SourcePath=/etc/init.d/winbind Description=LSB: start Winbind daemon Before=shutdown.target After=network-online.target After=remote-fs.target After=systemd-journald-dev-log.socket After=samba.service Wants=network-online.target Conflicts=shutdown.target
[Bug 1536331] Re: Precise to Trusty live migration failing
Well this is unnerving. After re-installing the current versions of qemu-kvm on the source host, it continues to work. -- 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/1536331 Title: Precise to Trusty live migration failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1536331/+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 1536331] Re: Precise to Trusty live migration failing
Ok, so reverting the qemu-kvm on the precise source host to 1.0+noroms- 0ubuntu14.18 seems to fix it. (And then using pc-1.0 machine type and setting allow_incoming_qemukvm = 1 on the destination) -- 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/1536331 Title: Precise to Trusty live migration failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1536331/+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 1563551] Re: [FFE] Sync ethtool 1:4.5-1 (main) from Debian testing (main)
** Summary changed: - Sync ethtool 1:4.5-1 (main) from Debian testing (main) + [FFE] Sync ethtool 1:4.5-1 (main) from Debian testing (main) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/1563551 Title: [FFE] Sync ethtool 1:4.5-1 (main) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/1563551/+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 1563990] Re: Need a GUI option to set per node kernel parameters
** Changed in: maas (Ubuntu) Importance: Undecided => Wishlist ** Changed in: maas (Ubuntu) Status: New => Triaged ** Also affects: maas Importance: Undecided Status: New ** No longer affects: maas (Ubuntu) ** Changed in: maas Importance: Undecided => Wishlist ** Changed in: maas Status: New => Triaged ** Changed in: maas Milestone: None => next -- 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/1563990 Title: Need a GUI option to set per node kernel parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1563990/+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 1513267] Re: [SRU] network_data.json not found in openstack/2015-10-15/
Hello Mathieu, or anyone else affected, Accepted nova into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nova/2:12.0.2-0ubuntu1 in a few hours, and then 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: nova (Ubuntu Wily) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1513267 Title: [SRU] network_data.json not found in openstack/2015-10-15/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1513267/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
Upgrading from the 1.9.12 packages to the 1.9.13 packages works without any issues. There are no failures to update. Adding install/history logs shortly for each version, and a screenshot done through nginx-core to show that the defaults work and the application runs. It also includes a picture of the VMware Workstation window to the VM running Xenial to show its IP, and that nginx-core's nginx executable is running. -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
Runtime screenshot - shows the 'default' landing page of nginx-core, done via VM, and the IP data for the VM, the pidof output to show nginx is running, and the default landing page via web browser to that VM's IP address. ** Attachment added: "Screenshot - Xenial VM IP, Xenial pidof output showing nginx is running, and default landing page (via 14.04 Host) on Chrome to show running." https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617288/+files/Screenshot_nginx-core_running.png -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
This is the nginx-core installation and apt logs. ** Attachment added: "nginx-core apt logs" https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617282/+files/install_logs_nginx-core.txt -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1559935] Re: [SRU] nova 12.0.2, keystone 8.1.0
Hello James, or anyone else affected, Accepted nova into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nova/2:12.0.2-0ubuntu1 in a few hours, and then 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: nova (Ubuntu Wily) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1559935 Title: [SRU] nova 12.0.2, keystone 8.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1559935/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
DebDiff between 1.9.12-0ubuntu1 and 1.9.13-0ubuntu1. ** Patch added: "Debdiff, nginx 1.9.12-0ubuntu1 to 1.9.13-0ubuntu1" https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617290/+files/nginx_xenial_1.9.12_1.9.13.debdiff -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
This needs to be examined for freeze exception. We are past FinalBetaFreeze, so this needs review before I even upload it to the repositories. -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
This is the nginx-extras installation and apt logs. ** Attachment added: "nginx-extras apt logs" https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617286/+files/install_logs_nginx-extras.txt -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
This is the nginx-light installation and apt logs. ** Attachment added: "nginx-light apt logs" https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617283/+files/install_logs_nginx-light.txt -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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 1563990] [NEW] Need a GUI option to set per node kernel parameters
Public bug reported: In the near future, we'd expect to have a number of new ARM64 platforms ( Cavium, APM, Qualcomm, Broadcom etc) supported in Ubuntu 16.04 LTS. Some of these use UEFI + DTB as the default boot mechanism, whereas others are expected to use UEFI +ACPI as thedefault boot mode. Upstream kernel (and hence Ubuntu 16.04) currently defaults to booting with DTB mechanism when it finds DTB info on the platform, which many of the UEFI+ACPI boot mode platforms also tend to provide as a backup. So we need to be able to pass a kernel parameter to force ACPI mode boot for platforms which would like to use UEFI +ACPI as the default boot mode. MaaS API today provides a method to pass in per node kernel parameters via tags. But there is no way today to do this from GUI. So this is request to add the MaaS GUI capability to allow passing the per node kernel parameters. ** Affects: maas Importance: Wishlist Status: Triaged ** Tags: arm64 hs-arm64 ** Tags added: arm64 hs-arm64 -- 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/1563990 Title: Need a GUI option to set per node kernel parameters To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1563990/+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 1563393] Re: [FFe Needed] Update nginx to 1.9.13.
This is the nginx-full installation and apt logs. ** Attachment added: "nginx-full apt logs" https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617284/+files/install_logs_nginx-full.txt -- 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/1563393 Title: [FFe Needed] Update nginx to 1.9.13. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+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-x-server-core] General server work for Xenial
Blueprint changed by Thomas Ward: Work items changed: Work items for ubuntu-15.11: [serge-hallyn] etckeeper: DONE [paelzer] NIS merge: DONE Work items for ubuntu-15.12: [raharper] : tgt merge (bug 1524982): DONE [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE [kick-d] exim4 merge: DONE Work items for ubuntu-16.01: [stgraber] unbound merge: DONE [kick-d] amavisd-new merge: DONE [vorlon] freeipmi merge and cleanup (=3days): DONE [vorlon] freeipmi12 to 16 transition: DONE [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE [louis-bouchard] nut merge: DONE [nacc] logwatch merge: DONE Work items for ubuntu-16.02: [nacc] php7.0 for Xenial (in main now, still removing php5): INPROGRESS [kick-d] NTP merge, cleanup and PPS support: MIR for pps-tools: DONE [arges] libvirt merge (bug 1533003) : DONE [arges] libvirt-python: DONE [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): DONE [smoser] openiscsi merge: DONE [racb] MySQL cleanup (=2days): TODO [racb] MySQL flags fix (=5days): TODO [lars-tangvald] MySQL move to 5.7: DONE [racb] squid3 merge (=4days): INPROGRESS [racb] libecap (squid3 dependency): INPROGRESS [nacc] logwatch cleanup: DONE [nacc] Tomcat updates and cleanup: DONE [nacc] Java-related work: DONE [nacc] puppet merge and cleanup: DONE [rharper] docker.io 1.10 or greater: DONE [louis-bouchard] clamav merge: DONE [jamespage] crmsh and pacemaker: DONE [teward] Update nginx to 1.9.11 (bug 1543624): DONE [kick-d] Amavisd-new update: DONE [kick-d] moin merge: DONE [kick-d] urlgrabber merge: DONE Work items for ubuntu-16.04: - [teward] Update nginx to 1.9.13 (bug 1563393): TODO + [teward] Update nginx to 1.9.13 (bug 1563393): INPROGRESS [paelzer] DPDK MIR: DONE [teward] Update nginx to 1.10.x after upstream release: BLOCKED Work items: [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO [paelzer] DPDK upstream work: DONE [serge-hallyn] enable numa in qemu (was actually done in vivid!): DONE [racb] HTTP/2 related work (=1days): TODO [racb] mail-stack-delivery deprecation plan: TODO dovecot merge (doko: done in wily, update to 2.2.2x would be good): DONE [kick-d] Get postfix migrated: DONE -- General server work for Xenial https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core -- 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 1545913] Re: [FFe] juju-core 2.0
local-kvm provider is not available in the beta, and is a regression compared with juju-core 1.25. Is there going to be a local kvm provider? (or e.g. libvirt provider on par with lxd provider) -- 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/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1515145] Re: xm migrate --live panics hypervisor
The attachment "x86/mm: Make MM locks recursive." seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1515145 Title: xm migrate --live panics hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1515145/+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 1563951] [NEW] Cloud-init does not initialize systemd machine id
Public bug reported: Systemd uses /etc/machine-id file to uniquely identify the machine and to provide machine ID to D-Bus. This file is generated with `systemd- machine-id-setup` command that should be run on system installation (or at least when a system is provisioned). However, cloud-init does not do this. As far as I can see, all Wily Werewolf VMs provisioned in EC2 have the same machine-id ff1bed6402c14c57ac03a074cdb7479e. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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/1563951 Title: Cloud-init does not initialize systemd machine id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951/+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 1396956] Re: package clamav-freshclam 0.98.5+dfsg-0ubuntu0.14.10.1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1
*** This bug is a duplicate of bug 1398001 *** https://bugs.launchpad.net/bugs/1398001 ** This bug has been marked a duplicate of bug 1398001 package clamav 0.98.5+dfsg-0ubuntu0.14.10.1 failed to install/upgrade: beroendeproblem - lämnar okonfigurerad -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1396956 Title: package clamav-freshclam 0.98.5+dfsg-0ubuntu0.14.10.1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1396956/+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 1398001] Re: package clamav 0.98.5+dfsg-0ubuntu0.14.10.1 failed to install/upgrade: beroendeproblem - lämnar okonfigurerad
Hi rolfc, thank you for reporting that bug. It appears on your system some conffiles were deleted. modified.conffile..etc.apparmor.d.usr.sbin.clamd: [deleted] modified.conffile..etc.init.d.clamav.daemon: [deleted] modified.conffile..etc.logcheck.ignore.d.paranoid.clamav.daemon: [deleted] modified.conffile..etc.logcheck.ignore.d.server.clamav.daemon: [deleted] That is like just "rm" those files instead of removing a package. I'd recommend purging (apt-get remove --purge) the clamav packages and reinstalling them to get rid of the issue. I'll set the bug status to incomplete, please feel free to reopen if the problem persists. In that case please add what you did to purge/reinstall and the new/old error log. ** Changed in: clamav (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1398001 Title: package clamav 0.98.5+dfsg-0ubuntu0.14.10.1 failed to install/upgrade: beroendeproblem - lämnar okonfigurerad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1398001/+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 1515768] Re: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy
** Also affects: heat (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** No longer affects: heat (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heat in Ubuntu. https://bugs.launchpad.net/bugs/1515768 Title: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1515768/+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
Re: [Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)
On Wed, Mar 30, 2016 at 04:41:12AM -, Ryan Harper wrote: > As far as I can see, the entire versioned code block here is wrong, and > > you should *only* be restarting squid. > The block (without my addition) is from debian itself. Yes, and I believe it's wrong there also (unless their previous squid3 package, unlike ours, didn't stop itself in the prerm?) > update-rc.d squid defaults 30 >/dev/null OK, someone's living in 2005... The '30' sequence number is obsolete, and also why is this not being driven by debhelper? > However, this failed in our dist-upgrade from trusty scenario as the squid3 > service file no longer > exists. Reading your analysis; it seems that /etc/init.d/squid3 should > still be on disk; > but it was not. No. I said that in an upgrade from trusty, there *was no* /etc/init.d/squid3 init script, only an /etc/init/squid3.conf upstart job. And your maintainer script is removing /etc/init/squid3.conf on upgrade; which is why the Debian logic fails. > In the dist-upgrade from trusty case; I believe we can just use the squid > restart. Yes. > In the upgrade from wily case, it's not clear to me why the > /etc/init.d/squid3 service > file would still be on disk when it wasn't when upgrading from trusty? Because the wily version of the package *has* an /etc/init.d/squid3 file, whereas the trusty package does not. And nothing in the xenial package is handling the removal of this stale conffile. So: - fix the maintainer script to remove /etc/init.d/squid3 on upgrade - drop all the versioned upgrade logic and just call invoke-rc.d squid restart. BTW, note that dpkg-maintscript-helper has to be called from several different maintainer scripts with the same arguments, not just from the preinst - the squid package already has several bugs because it's not doing this correctly. This is a royal pain to get right by hand, and all right-thinking maintainers would use debian/squid.maintscript as documented in dh_installdeb, instead of hand-editing maintainer scripts and trying to keep them all in sync. This *probably* will DTRT in the package, despite the fact that squid3 is using the one-step-removed-from-obsolete debhelper compat level 5. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1473691 Title: [FFe] squid: Update to latest upstream release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1515145] Re: xm migrate --live panics hypervisor
debian/patches/xsa97-hap-4.1-prereq.patch is the combination of * commit 301493fb027648db6808b66d1ccf849f524b8422 x86/mm: dedup the various copies of the shadow lock functions * commit eca988de7381e5efe58792dc166611e4523d33b3 x86/mm: merge the shadow, hap and log-dirty locks into a single paging lock. but it's missing * commit 5bf494a7bf3674f32ebaab1b70b76e5f174812a3 x86/mm: Make MM locks recursive. which leads to a recursive locking call to crash the hypervisor. With the patch applied "xm migrate -c -l $dom $host" works again. ** Patch added: "x86/mm: Make MM locks recursive." https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1515145/+attachment/4617139/+files/0001-x86-mm-Make-MM-locks-recursive.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1515145 Title: xm migrate --live panics hypervisor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1515145/+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 1446332] Re: package clamav-daemon (not installed) failed to install/upgrade: unable to delete control info file `/var/lib/dpkg/info/clamav-daemon.postlist': Is a directory
Hi Jeff, Thanks for you report - I've seen several such reports popping up around the same time. Almost all others had success with purging and reinstalling the clamav packages. I'd ask you to do the same. I set the bug to incomplete to ease scanning open bugs, please feel free to reopen if the bug persists. ** Changed in: clamav (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1446332 Title: package clamav-daemon (not installed) failed to install/upgrade: unable to delete control info file `/var/lib/dpkg/info/clamav- daemon.postlist': Is a directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1446332/+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 1447842] Re: package clamav-base (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi Ken, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: clamav (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1447842 Title: package clamav-base (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1447842/+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 1559356] Re: package clamav-freshclam 0.98.7+dfsg-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
It seems that some or all of the package was removed manually. Therefore the upgrade is failing >From your logs: chown: invalid user: ‘clamav:adm’ ... modified.conffile..etc.apparmor.d.usr.sbin.clamd: [deleted] modified.conffile..etc.init.d.clamav.daemon: [deleted] modified.conffile..etc.logcheck.ignore.d.paranoid.clamav.daemon: [deleted] modified.conffile..etc.logcheck.ignore.d.server.clamav.daemon: [deleted] Please consider purging (apt-get remove --purge) and re-installing it to get rid of the messages. Marking as incomplete, please feel free to reopen if after correctly "re-populating" ** Changed in: clamav (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1559356 Title: package clamav-freshclam 0.98.7+dfsg-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1559356/+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 1493049] Re: memory corruption during live-migration in TCG mode
Hello Pavel, or anyone else affected, Accepted qemu into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg- 2ubuntu1.23 in a few hours, and then 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: qemu (Ubuntu Trusty) Status: Confirmed => Fix Committed ** Tags added: verification-needed -- 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/1493049 Title: memory corruption during live-migration in TCG mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1493049/+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 1561103] Re: Multipath assigned user_friendly_names during initramfs
@taco-screen-team I'd suggest for @cyphermox (formerly @mathieu-tl) to look at this one. Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1561103 Title: Multipath assigned user_friendly_names during initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1561103/+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 1563487] Re: do not delete /etc/network/interfaces.d/eth0.cfg
** Changed in: cloud-images Assignee: (unassigned) => Dan Watkins (daniel-thewatkins) -- 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/1563487 Title: do not delete /etc/network/interfaces.d/eth0.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1563487/+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 1561103] Re: Multipath assigned user_friendly_names during initramfs
** Changed in: multipath-tools (Ubuntu) Status: New => Triaged ** Changed in: multipath-tools (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1561103 Title: Multipath assigned user_friendly_names during initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1561103/+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 1563296] Re: cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in /etc/network/interfaces.d/ in snappy leaving the boot completely network-less
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Oliver Grawert (ogra) -- 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/1563296 Title: cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in /etc/network/interfaces.d/ in snappy leaving the boot completely network-less To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1563296/+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 1563887] [NEW] qemu-system-ppc64 freezes on starting image on ppc64le
Public bug reported: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file= xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': No such file or directory ubuntu@alpine01:~$ cd kvm ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive f ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,2:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,3:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 cpu_cores: Number of cores
[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
In Ubuntu 14.04.4 running on the same hardware, the fix was to update qemu-system-ppc from cloud-archive:kilo. This repository is only supported on trusty and contains an earlier version of qemu-system-ppc than what is available on xenial. ** Description changed: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM - mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. + mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no + error output. ubuntu@alpine01:~$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file= xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio qemu-system-ppc64: -drive file=seed.iso,if=virtio: Could not open 'seed.iso': No such file or directory ubuntu@alpine01:~$ cd kvm ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive f ile=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40
[Bug 1555700] Re: Please merge tgt 1.0.63 from Debian (unstable)
** Changed in: tgt (Ubuntu) Importance: Undecided => Medium ** Changed in: tgt (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1555700 Title: Please merge tgt 1.0.63 from Debian (unstable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+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 1563878] [NEW] package python-simplegeneric 0.8.1-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: update bug ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-simplegeneric 0.8.1-1 ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24 Uname: Linux 3.16.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Wed Mar 30 16:02:14 2016 DuplicateSignature: package:python-simplegeneric:0.8.1-1:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2015-09-07 (205 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: simplegeneric Title: package python-simplegeneric 0.8.1-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: simplegeneric (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to simplegeneric in Ubuntu. https://bugs.launchpad.net/bugs/1563878 Title: package python-simplegeneric 0.8.1-1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplegeneric/+bug/1563878/+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 1522371] Re: iproute2: seg fault with 'ip link type gre ...' commands
** Changed in: iproute2 (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1522371 Title: iproute2: seg fault with 'ip link type gre ...' commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1522371/+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 1563027] Re: vsftpd 3.0.3-3ubuntu1 fails to start on installation
I have been working on parallel on this one & opened a bug in debian : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819546 listen_ipv6 was reverted from YES to NO following Debian Bug: #803999 to allign with the manpage statement. Either we revert it back & adapt the manpage or we force it in the systemd unit & document accordingly ** Changed in: vsftpd (Ubuntu) Assignee: Chris J Arges (arges) => Louis Bouchard (louis-bouchard) ** Bug watch added: Debian Bug tracker #819546 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819546 ** Changed in: vsftpd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1563027 Title: vsftpd 3.0.3-3ubuntu1 fails to start on installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1563027/+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 1563296] Re: cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in /etc/network/interfaces.d/ in snappy leaving the boot completely network-less
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563296 The short term fix is to disable cloud-init's networking code by writing a file /etc/cloud/cloud.cfg.d/99-snappy-disable-network-config.cfg with: | network: |config: "disabled" The file is yaml text. This unfortunately, will have two shortcomings: a.) ConfigDrive and other cases where the datasource provides network config will not have that networking rendered on snappy. b.) cloud-init has slightly smarter "fallback" config than snappy (to my limited knowledge). if cloud-init does not find networking configuration from a source, then it defines a fallback as roughly equivalent to "dhcp on eth0" , but the 'eth0' name is chosen by finding an existing network device and filtering out those that are not connected. Later we will have 2 options to re-enable this 1.) snappy could delegate writing of network config to cloud-init 2.) cloud-init could feed network config it found to snappy and let snappy write the config. '2' could be accomplished via snappy REST interface or shell via: http://paste.ubuntu.com/15559735/ Having this happen via 'fallback' (and thus all the time) might mean that cloud-init would overwrite what the gadget snap provided. So maybe for fallback case, cloud-init would want to first query if there was gadget provided config, and if not then provide the fallback. -- 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/1563296 Title: cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in /etc/network/interfaces.d/ in snappy leaving the boot completely network-less To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1563296/+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 1510693] Re: Cloud-Init 0.7.5 does not work with MAAS 1.9.0 (beta1+bzr4417)
Hi. Can you still reproduce this? I'm not aware of any problems like this with cliff init and maas. ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- 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/1510693 Title: Cloud-Init 0.7.5 does not work with MAAS 1.9.0 (beta1+bzr4417) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1510693/+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 1532072] Re: cloud-init fails with UnicodeDecodeError
** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- 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/1532072 Title: cloud-init fails with UnicodeDecodeError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1532072/+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 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v
This bug was fixed in the package corosync - 2.3.3-1ubuntu2 --- corosync (2.3.3-1ubuntu2) trusty; urgency=medium * Patches to solve logsys file leaks (LP: #1530837) + /d/p/Fix-compiler-warning-introduced-by-previous-patch.patch + /d/p/Handle-SIGSEGV-and-SIGABRT-signals.patch + /d/p/leak-produced-by-corosync-v.patch -- Rafael David TinocoWed, 09 Mar 2016 09:56:58 +0100 ** Changed in: corosync (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1530837 Title: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+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 1530837] Update Released
The verification of the Stable Release Update for corosync has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1530837 Title: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+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 1562918] Re: cloud-init does not create defined users
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High -- 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/1562918 Title: cloud-init does not create defined users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1562918/+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 1563296] Re: cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in /etc/network/interfaces.d/ in snappy leaving the boot completely network-less
Hmm. You can disable cloud-init writing network config by putting config in /etc/cloud/cloud.cfg.d/ that says network: config: disabled However, that will entirely disable cloud init writing networking information that the data source provided it with. Currently that is openstack config drive or NoCloud. But in the future it will be other sources. Basically, the cloud can provide the intended networking to the instance, and the instance should apply it. 2 options I can think of are 1 adding function for cloud-init to not write 'fallback' networking config but still write carapace provided config 2 having cloud init read and render the snappy provided config ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High -- 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/1563296 Title: cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in /etc/network/interfaces.d/ in snappy leaving the boot completely network-less To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1563296/+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 1528251] Re: WARNING: no suitable primes in /etc/ssh/primes
Patch attached upstream https://bugzilla.mindrot.org/show_bug.cgi?id=2559 see https://bugzilla.mindrot.org/attachment.cgi?id=2801 As far as I understand there is no further actions for s390x port. @OP this is a minor problem, and best addressed upstream, see upstream bug report linked. ** Bug watch added: OpenSSH Portable Bugzilla #2559 https://bugzilla.mindrot.org/show_bug.cgi?id=2559 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=2559 Importance: Unknown Status: Unknown ** Changed in: openssh (Ubuntu) Importance: Low => Wishlist -- 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/1528251 Title: WARNING: no suitable primes in /etc/ssh/primes To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1528251/+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 1528251] Re: WARNING: no suitable primes in /etc/ssh/primes
Sorry, I mean OpenSSH in general of course, not just the client. And yes, the other end ought to be able to cope with stronger primes. But that's not what this bug is about: it specifically says "The alleged problem is the reference to /etc/ssh/primes instead of /etc/ssh/moduli". -- 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/1528251 Title: WARNING: no suitable primes in /etc/ssh/primes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1528251/+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 1528251] Re: WARNING: no suitable primes in /etc/ssh/primes
Sigh. No. It's a perfectly obvious bug in the OpenSSH client, it's just mostly cosmetic (i.e. it's checking two files but then only warning about one). Please read the original bug description carefully before closing this or arguing further about whether it's valid. ** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: Invalid => Triaged -- 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/1528251 Title: WARNING: no suitable primes in /etc/ssh/primes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1528251/+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 1563791] [NEW] cnf file ignored
Public bug reported: File named mysqld.cnf on folder /etc/mysql/conf.d with content: [mysqld] character-set-server=utf8 collation-server=utf8_general_ci Is ignored altogether, albeit the configuration of my.cnf stated that all files on that folder is read. Placing the file on /etc/mysql/mysql.conf.d (with different name naturally as there is one already there) doesn't work either. Renaming the files with starting numbers doesn't affect either (placing the stated file before or after the existing ones). The only way to change the those server settings are by adding those configurations into the existing /etc/mysql/mysql.conf.d/mysqld.cnf which defeats the purpose of having configuration folders and allow overridings. Also, it would be useful to have an equivalent symlink configuration system as it happens with apache2 (and other software packages) to turn on/off functionality. ** Affects: mysql-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: config -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1563791 Title: cnf file ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1563791/+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 1528251] Re: WARNING: no suitable primes in /etc/ssh/primes
Surely the bug is in Client: Prompt 2 v2.5.2 (Build 23057) on IOS 9.2.1 (see https://panic.com/prompt/), and you should report to them that it should use stronger keys to authenticate, no? We do not provide support for third party ssh clients. And we will not weaken our server to support weak clients. Also wily 15.10 on amd64, is out of scope for s390x support on xenial. Please let me know, if you can reproduce this at all with Ubuntu clients and Ubuntu server on s390x. ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- 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/1528251 Title: WARNING: no suitable primes in /etc/ssh/primes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1528251/+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