[Bug 1709633] Re: Failed actions requiring manual clean up when resource is running
Corosync is doing it's job, if there are failures in the resource it will log those failures. What's more of an issue here is that charm- deployed clouds have very frequent failures on nova-consoleauth. Retargetting this bug. ** Package changed: corosync (Ubuntu) => nova-cloud-controller (Juju Charms Collection) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709633 Title: Failed actions requiring manual clean up when resource is running To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/nova-cloud-controller/+bug/1709633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715254] Re: nova-novncproxy process gets wedged, requiring kill -HUP
** Package changed: nova (Ubuntu) => charm-nova-cloud-controller -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715254 Title: nova-novncproxy process gets wedged, requiring kill -HUP To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1715254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701316] Re: Data corruption with hio driver
So far we've tested this build on one machine, using the below
comparison 30+ times, and it looks good.
# i=0; while :; do i=$(($i+1)); echo -n "." ; dd if=/dev/urandom
of=test.dat bs=1G count=8 iflag=fullblock ; dd if=test.dat of=/dev/hioa
bs=1G count=8 iflag=fullblock ; dd if=/dev/hioa of=read-back.dat bs=1G
count=8 ; cmp=$(md5sum test.dat read-back.dat|awk '{print $1}'|sort
-u|wc -l); if [ "$cmp" -ne 1 ]; then echo "MISMATCH" ; md5sum test.dat
read-back.dat ; echo $i; return 1; fi; done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701316
Title:
Data corruption with hio driver
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701316/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298325] Re: ifenslave can't delete interfaces from a bond
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298325 Title: ifenslave can't delete interfaces from a bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1298325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592597] Re: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630
system is headless, getting a 403 with lynx (lp#997020). what logs can I provide? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592597 Title: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592597] Re: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630
https://private-fileshare.canonical.com/~jillr/lp1592597/sosreport- os-1-20160614233237.tar.xz md5: c27d8c988ee155cf61532285866907d4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592597 Title: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592597] [NEW] 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630
Public bug reported: Following recent update to 3.13.0-88, R630 on Trusty panics on boot. Recovery boot just hangs. 3.13.0-87 was able to be booted normally once, then kernel panics on subsequent attempts. Booting is successful with the previously running kernel, 3.13.0-61. will upload an sosreport. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Attachment added: "consolescreenshots.tar.gz" https://bugs.launchpad.net/bugs/1592597/+attachment/4683973/+files/consolescreenshots.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592597 Title: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572320] Re: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova-consoleauth stopped
nova-cloud-controller: charm: nova-cloud-controller num_units: 3 to: *NCC_3x_TO options: <<: *OS_REL_ORIGIN # config-flags will likely be overloaded by additional settings like # quota_RESOURCENAME=nnn,scheduler_default_filters=... config-flags: disk_allocation_ratio=1.0 cpu-allocation-ratio: 4.0 ram-allocation-ratio: 0.9 network-manager: Neutron console-access-protocol: novnc quantum-security-groups: "yes" region: *REGION vip: *NCC_VIP vip_cidr: *VIP_CIDR ncc-hacluster: charm: hacluster options: cluster_count: 3 from juju get: single-nova-consoleauth default: true console-access-protocol novnc All three of the clouds that hit this with the most recent update are running lp:charms/trusty/nova-cloud-controller;revno=173 lp:charms/trusty/hacluster;revno=54 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572320 Title: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova- consoleauth stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1572320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572320] Re: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova-consoleauth stopped
This is happening again with the latest set of updates: Start-Date: 2016-05-17 22:11:48 Upgrade: libstdc++-4.8-dev:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), nova-novncproxy:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), libasan0:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), libquadmath0:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), gcc-4.8-base:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), cpp-4.8:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), nova-common:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), libgomp1:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), libarchive13:amd64 (3.1.2-7ubuntu2.1, 3.1.2-7ubuntu2.2), libtsan0:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), python-nova:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), neutron-common:amd64 (7.0.3-0ubuntu1~cloud0, 7.0.4-0ubuntu1~cloud0), libatomic1:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), nova-api-ec2:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), neutron-plugin-ml2:amd64 (7.0.3-0ubuntu1~cloud0, 7.0.4-0ubuntu1~cloud0), g++-4.8:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), binutils:amd64 (2.24-5ubuntu14, 2.24-5ubuntu14.1), python-neutron-fwaas:amd64 (7.0.0-0ubuntu1~cloud0, 7.0.2-0ubuntu1~cloud0), libgcc-4.8-dev:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), gcc-4.8:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), neutron-server:amd64 (7.0.3-0ubuntu1~cloud0, 7.0.4-0ubuntu1~cloud0), nova-api-os-compute:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), nova-consoleauth:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), nova-conductor:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), python-neutron:amd64 (7.0.3-0ubuntu1~cloud0, 7.0.4-0ubuntu1~cloud0), libgfortran3:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), nova-scheduler:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), nova-cert:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), nova-objectstore:amd64 (12.0.2-0ubuntu1~cloud0, 12.0.3-0ubuntu1~cloud0), libstdc++6 :amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3), libitm1:amd64 (4.8.4-2ubuntu1~14.04.1, 4.8.4-2ubuntu1~14.04.3) End-Date: 2016-05-17 22:12:23 2016-05-17 22:11:58.561 1776154 WARNING oslo_messaging.server [req-61be1a66-e2a9-4f70-b3ff-172f89d72020 - - - - -] start/stop/wait must be called in the same thread 2016-05-17 22:11:58.563 1776154 WARNING oslo_messaging.server [req-61be1a66-e2a9-4f70-b3ff-172f89d72020 - - - - -] start/stop/wait must be called in the same thread nova-consoleauth service is left in a 'stopped' state after update, this is an outage condition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572320 Title: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova- consoleauth stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1572320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572320] [NEW] nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova-consoleauth stopped
Public bug reported: Latest set of upgrades leaves nova-consoleauth service stopped. Service must manually be restarted. Trusty/Liberty. Start-Date: 2016-04-19 21:15:39 Upgrade: nova-novncproxy:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-common:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), python-nova:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-api-ec2:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-api-os-compute:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-consoleauth:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-conductor:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-scheduler:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), python-keystone:amd64 (8.0.1-0ubuntu1~cloud0, 8.1.0-0ubuntu1~cloud0), nova-cert:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0), nova-objectstore:amd64 (12.0.1-0ubuntu1~cloud0, 12.0.2-0ubuntu1~cloud0) End-Date: 2016-04-19 21:16:05 Appears to be related to nova-consoleauth.log messages: 2016-04-19 21:15:44.688 119419 WARNING oslo_messaging.server [req-7686c9be-ab85-4c84-af4e-2df15f68f511 - - - - -] start/stop/wait must be called in the same thread 2016-04-19 21:15:44.690 119419 WARNING oslo_messaging.server [req-7686c9be-ab85-4c84-af4e-2df15f68f511 - - - - -] start/stop/wait must be called in the same thread This is rolling through multiple landscape-managed clouds at the moment (probably over the next day) in case there is any other logging that would be useful. ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572320 Title: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova- consoleauth stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1572320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
** Tags added: canonical-bootstack -- 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/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+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 1477221] Re: Init script fails to stop service
** Tags added: canonical-bootstack -- 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/1477221 Title: Init script fails to stop service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1477221/+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 1477221] Re: Init script fails to stop service
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477221 Title: Init script fails to stop service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1477221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
I can reproduce with corosync 2.3.3. Using corosync 2.3.4 from ppa:mariosplivalo/corosync on trusty I've not been able to reproduce on 2 tries. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+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 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
I can reproduce with corosync 2.3.3. Using corosync 2.3.4 from ppa:mariosplivalo/corosync on trusty I've not been able to reproduce on 2 tries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
We've run into this problem after an extended maas/dhcp outage with expiring leases on metals and units. All hacluster-deployed lxc's (openstack-ha services) lost corosync-pacemaker connectivity with corosync Invalid IPC credentials, resolving with lxc reboots. This is a staging cloud so we could take down maas-dhcp to replicate/test. ** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+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 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
We've run into this problem after an extended maas/dhcp outage with expiring leases on metals and units. All hacluster-deployed lxc's (openstack-ha services) lost corosync-pacemaker connectivity with corosync Invalid IPC credentials, resolving with lxc reboots. This is a staging cloud so we could take down maas-dhcp to replicate/test. ** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350947] Re: apparmor: no working rule to allow making a mount private
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+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 1350947] Re: apparmor: no working rule to allow making a mount private
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
