[Group.of.nepali.translators] [Bug 1849042] Re: xenial/linux-kvm: 4.4.0-1061.68 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849051 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1849042 Title: xenial/linux-kvm: 4.4.0-1061.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849051 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849042/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: maas (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: maas (Ubuntu Bionic) Assignee: (unassigned) => Blake Rouse (blake-rouse) ** Also affects: maas/2.4 Importance: Undecided Status: New ** Changed in: maas/2.4 Status: New => Fix Committed ** Changed in: maas/2.4 Milestone: None => 2.4.3 ** Changed in: maas/2.4 Assignee: (unassigned) => Blake Rouse (blake-rouse) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: New Status in MAAS: Fix Committed Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Committed Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: [Impact] * systemd thinks the service is running, but it does not respond to any commands or requests. Also, it doesn't respond to signals other than kill -9. service restarts hang, rndc hangs. * being that the deadlock is in bind9 that ships in bionic the issue needs to be backported to 2.4.3 so MAAS from the archive in bionic can handle the deadlock and get bind9 unstuck. * change in MAAS watches for this case to occur with bind9, then MAAS will force kill the service and restart it. [Test Case] * very hard to reproduce but the issue occurs when bind9 deadlocks, it response to nothing over the network or rndc. SIGTERM does not kill it only SIGKILL works to force kill the process and get systemd to restart it. [Regression Potential] * possible that bind9 will not be started correctly or possible that bind9 will be placed into a forever restart loop To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1848834] Re: ClusterMon resource creation core-dumps while created with extra_option -E
Yeah he was running on 16.04 which means he was using 1.1.14-2ubuntu1.6 Neither could I reproduce the crashes :-/ But I'm glad to hear that for you it was resolved after using -e And even more glad that you found newer versions working better for you ´. I hope this bug helps further users that might run into this to find your workaround, but I don't see a crash to debug and fix in the package yet (just as Paride) ** Also affects: pacemaker (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Xenial) Status: New => Incomplete ** Changed in: pacemaker (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1848834 Title: ClusterMon resource creation core-dumps while created with extra_option -E Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Incomplete Bug description: Hi I have a 2 nodes cluster with a number of resources working fine. I am using Ubuntu 16.04 with Pacemaker: 1.1.14 The moment i create a ClusterMon resource with an extra_option "-E" to run a script, it crashes and i can see the following in dmesg [73880.444953] crm_mon[20739]: segfault at 0 ip 7f948cc5c746 sp 7ffed0cb0fb8 error 4 in libc-2.23.so[7f948cbd1000+1c] I am using the following command to create the resource: pcs resource create newRes ClusterMon user="root" extra_options="-E /usr/local/bin/new.sh " OR pcs resource create newRes ocf:pacemaker:ClusterMon user="root" extra_options="-E /usr/local/bin/new.sh " and immediately i see following in /var/log/messages 2019-10-19T01:53:11.783763-04:00 master daemon notice crmd 17042 notice: Operation newRes_monitor_0: not running (node=master.dhcp, call=85, rc=7, cib-update=58, confirmed=true) 2019-10-19T01:53:12.097529-04:00 master daemon info systemd - Started Session c75 of user root. 2019-10-19T01:53:12.105468-04:00 master auth info systemd-logind - New session c75 of user root. 2019-10-19T01:53:12.150340-04:00 master daemon notice lrmd 17039 notice: newRes_start_0:30376:stderr [ mesg: ttyname failed: Inappropriate ioctl for device ] 2019-10-19T01:53:12.186340-04:00 master daemon notice crmd 17042 notice: Operation newRes_start_0: ok (node=master.dhcp, call=86, rc=0, cib-update=59, confirmed=true) 2019-10-19T01:53:12.195312-04:00 master kern info kernel - crm_mon[30398]: segfault at 0 ip 7f9cfbe41746 sp 7ffd971060e8 error 4 in libc-2.23.so[7f9cfbdb6000+1c] 2019-10-19T01:53:12.216644-04:00 master auth info systemd-logind - Removed session c75. 2019-10-19T01:53:12.241439-04:00 master daemon notice lrmd 17039 notice: newRes_monitor_1:30406:stderr [ /usr/lib/ocf/resource.d/heartbeat/ClusterMon: 155: kill: No such process ] 2019-10-19T01:53:12.241980-04:00 master daemon notice lrmd 17039 notice: newRes_monitor_1:30406:stderr [ ] 2019-10-19T01:53:12.245273-04:00 master daemon notice crmd 17042 notice: master.dhcp-newRes_monitor_1:87 [ /usr/lib/ocf/resource.d/heartbeat/ClusterMon: 155: kill: No such process\n\n ] Note: - All other types of resources i.e. IPAddr, Drbd, systemd are working fine. - Also, if the newRes is created wihtout -E, it works fine. - Script has no complicated code. Event without the "echo" command i am seeing same issue. cat /usr/local/bin/new.sh #!/bin/sh echo "HELLO from Crm_mon script" >> /var/log/messages exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1848834/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
