[Bug 1866412] [NEW] resource-agents should depend on psmisc (and probably others) for the resources to work
Public bug reported: When configuring a Filesystem OCF resource with the following setup: (k)rafaeldtinoco@clubionic01:~$ crm conf show node 1: clubionic01 node 2: clubionic02 node 3: clubionic03 primitive ext4 Filesystem \ params device="/dev/clustervg/clustervol" directory="/clusterdata" fstype=ext4 primitive fence_clubionic stonith:fence_scsi \ params pcmk_host_list="clubionic01 clubionic02 clubionic03" plug="" devices="/dev/sda" \ meta provides=unfencing target-role=Started primitive lvm2 LVM-activate \ params vgname=clustervg vg_access_mode=system_id primitive virtual_ip IPaddr2 \ params ip=10.250.98.13 nic=eth3 \ op monitor interval=10s primitive webserver systemd:lighttpd \ op monitor interval=10 timeout=30 group webservergroup lvm2 ext4 virtual_ip webserver \ meta target-role=Started property cib-bootstrap-options: \ have-watchdog=false \ dc-version=1.1.18-2b07d5c5a9 \ cluster-infrastructure=corosync \ cluster-name=clubionic \ stonith-enabled=on \ stonith-action=off \ no-quorum-policy=stop \ last-lrm-refresh=1583529396 being clubionic01,02,03 all nodes configured with Ubuntu Cloud Images, I got the following error when trying to enable "ext4" resource: * ext4_monitor_0 on clubionic02 'not installed' (5): call=161, status=complete, exitreason='Setup problem: couldn't find command: fuser', last-rc-change='Fri Mar 6 21:14:36 2020', queued=0ms, exec=44ms Because the nodes were missing "psmisc" package. ** Affects: resource-agents (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: resource-agents (Ubuntu) Status: New => Confirmed ** Changed in: resource-agents (Ubuntu) Importance: Undecided => Medium ** Changed in: resource-agents (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to resource-agents in Ubuntu. https://bugs.launchpad.net/bugs/1866412 Title: resource-agents should depend on psmisc (and probably others) for the resources to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866412/+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 1866392] Re: [bionic] dlm_controld won't start due to missing device files
It only happens during package installation. Right after the package is already installed, you can "modprobe -r dlm" and "modprobe dlm" again and then the devices are properly translated from existing - from the pkg - udev rules. (k)rafaeldtinoco@clubionic03:~$ systemctl status dlm ● dlm.service - dlm control daemon Loaded: loaded (/lib/systemd/system/dlm.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-03-06 20:25:24 UTC; 1min 24s ago Docs: man:dlm_controld man:dlm.conf man:dlm_stonith Main PID: 1365 (dlm_controld) Tasks: 2 (limit: 2338) CGroup: /system.slice/dlm.service └─1365 /usr/sbin/dlm_controld --foreground Mar 06 20:25:23 clubionic03 systemd[1]: Starting dlm control daemon... Mar 06 20:25:23 clubionic03 dlm_controld[1365]: 67 dlm_controld 4.0.7 started Mar 06 20:25:24 clubionic03 systemd[1]: Started dlm control daemon. (k)rafaeldtinoco@clubionic03:~$ ls -1lah /dev/misc/* lrwxrwxrwx 1 root root 14 Mar 6 20:24 /dev/misc/dlm-control -> ../dlm-control lrwxrwxrwx 1 root root 14 Mar 6 20:24 /dev/misc/dlm-monitor -> ../dlm-monitor lrwxrwxrwx 1 root root 12 Mar 6 20:24 /dev/misc/dlm_plock -> ../dlm_plock -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1866392 Title: [bionic] dlm_controld won't start due to missing device files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1866392/+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 1866392] Re: [bionic] dlm_controld won't start due to missing device files
I have monitored udev when modprobing dlm module and those are the udev events being triggered: (k)rafaeldtinoco@clubionic01:~$ sudo udevadm monitor --kernel monitor will print the received events for: KERNEL - the kernel uevent KERNEL[10516.364250] add /module/dlm (module) KERNEL[10516.364425] add /kernel/slab/:496 (slab) KERNEL[10516.364579] add /kernel/slab/:312 (slab) KERNEL[10516.364730] add /devices/virtual/misc/dlm-control (misc) KERNEL[10516.364849] add /devices/virtual/misc/dlm-monitor (misc) KERNEL[10516.364980] add /devices/virtual/misc/dlm_plock (misc) and when being removed: KERNEL[10713.488367] remove /devices/virtual/misc/dlm_plock (misc) KERNEL[10713.488465] remove /devices/virtual/misc/dlm-control (misc) KERNEL[10713.488539] remove /devices/virtual/misc/dlm-monitor (misc) KERNEL[10713.488635] remove /kernel/slab/:496 (slab) KERNEL[10713.488692] remove /kernel/slab/:312 (slab) KERNEL[10713.488825] remove /module/dlm (module) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1866392 Title: [bionic] dlm_controld won't start due to missing device files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1866392/+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 1866392] [NEW] [bionic] dlm_controld won't start due to missing device files
Public bug reported:
Right after installing dlm and dlm_controld, when trying to start the
service, you will face:
rafaeldtinoco@clubionic01:~$ systemctl status dlm.service
● dlm.service - dlm control daemon
Loaded: loaded (/lib/systemd/system/dlm.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Fri 2020-03-06 19:13:32 UTC; 35s ago
Docs: man:dlm_controld
man:dlm.conf
man:dlm_stonith
Process: 31644 ExecStart=/usr/sbin/dlm_controld --foreground
$DLM_CONTROLD_OPTS (code=exited, status=1/FAILURE)
Process: 31643 ExecStartPre=/sbin/modprobe dlm (code=exited, status=0/SUCCESS)
Main PID: 31644 (code=exited, status=1/FAILURE)
Mar 06 19:13:21 clubionic01 systemd[1]: Starting dlm control daemon...
Mar 06 19:13:21 clubionic01 dlm_controld[31644]: 8746 dlm_controld 4.0.7 started
Mar 06 19:13:32 clubionic01 dlm_controld[31644]: 8756 cannot find device
/dev/misc/dlm-control with minor 56
Mar 06 19:13:32 clubionic01 systemd[1]: dlm.service: Main process exited,
code=exited, status=1/FAILURE
Mar 06 19:13:32 clubionic01 systemd[1]: dlm.service: Failed with result
'exit-code'.
Mar 06 19:13:32 clubionic01 systemd[1]: Failed to start dlm control daemon.
This happens even after the module "dlm" was loaded (as you can see in
the ExecStartPre= line).
(k)rafaeldtinoco@clubionic01:~$ ls -lah /dev/dlm*
crw--- 1 root root 10, 56 Mar 6 19:08 /dev/dlm-control
crw--- 1 root root 10, 55 Mar 6 19:08 /dev/dlm-monitor
crw--- 1 root root 10, 54 Mar 6 19:08 /dev/dlm_plock
And we can see hardcoded device filename paths:
dlm_controld/action.c: rv = find_udev_device("/dev/misc/dlm-control",
control_minor);
dlm_controld/action.c: rv = find_udev_device("/dev/misc/dlm-monitor",
monitor_minor);
dlm_controld/action.c: rv = find_udev_device("/dev/misc/dlm_plock",
plock_minor);
And the way rules.d files are generated:
rafaeldtinoco@workstation:~/.../dlm$ grep -r UDEVDIR *
libdlm/Makefile:UDEVDIR=/usr/lib/udev/rules.d
libdlm/Makefile:$(INSTALL) -d $(DESTDIR)/$(UDEVDIR)
libdlm/Makefile:$(INSTALL) -m 644 $(UDEV_TARGET) $(DESTDIR)/$(UDEVDIR)
And that the package contains those:
(k)rafaeldtinoco@clubionic01:~$ cat /lib/udev/rules.d/51-dlm.rules
KERNEL=="dlm-control", MODE="0666", SYMLINK+="misc/dlm-control"
KERNEL=="dlm-monitor", MODE="0666", SYMLINK+="misc/dlm-monitor"
KERNEL=="dlm_plock", MODE="0666", SYMLINK+="misc/dlm_plock"
KERNEL=="dlm_*", MODE="0660", SYMLINK+="misc/%k"
** Affects: dlm (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: dlm (Ubuntu Bionic)
Importance: Medium
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: dlm (Ubuntu)
Status: New => Confirmed
** Changed in: dlm (Ubuntu)
Status: Confirmed => Triaged
** Also affects: dlm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: dlm (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: dlm (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: dlm (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to dlm in Ubuntu.
https://bugs.launchpad.net/bugs/1866392
Title:
[bionic] dlm_controld won't start due to missing device files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1866392/+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: Triage and migration report - Friday
On Fri, Mar 6, 2020 at 2:21 PM Christian Ehrhardt < christian.ehrha...@canonical.com> wrote: > ## Triage ## > > I got 21 bugs > > I was happy to find that most of them were bumps to fix released or fixes > that were started. > One can see that the Feature Freeze has passed and bug work is increasing > again. > > The TLS v1.3 bugs were mentioned by others yesterday, no further updates > to those yet since yesterday. > > Three bugs needed a proper initial triage and some minor testing. > > One of these that is worth mentioning is: > https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1865818 > I think we should try to take a look at picking the patch and modifying > the postinst beofre 20.04. > Subscribed the team and tagged as server-next. > > > ## Proposed migration ## > > Most things in our queue are valid but depending on bigger migrations. > The obvious ruby/php candidates are being worked on. > > The one thing worth to look at (again) is python-cffi which breaks and > holds back python-defaults a while now. > Paride mentioned that test on 2020-02-27: > It seems the autopkgtest run got a sigkill: > > [...] > ..s...s.ss.Killed > > It was even mentioned before on 2020-01-16 missing dep: libffi but that is > good now. > > > Nowadays it is important to know that there is a new version of it > python-cffi | 1.13.2-1build3 | focal/universe | all > python-cffi | 1.14.0-1build1 | focal-proposed | source > python-cffi | 1.14.0-1build1 | focal-proposed/universe | all > > Recent tests had: > - the new python3-defaults against the old version of python-cffi > - the new python-cffi against python3-defaults > > One outlier also had "ModuleNotFoundError". But that was before a rebuild > to drop python 3.7 and is resolved. > The other fails of the new version still fail with the "Killed" message. > > Lets try to run that with new python + new python-cffi and do so in a > local VM for debugging right away. > > The test has a python2 and a python3 test component. > In the past both failed with the kill-symptom. > > I ran the new cffi against three sets: > - old python3-defaults > - new python3-defaults > - all-proposed > > And of course, they ALL passed the tests :-/ > So much for reproducibility. > > == 1912 passed, 88 skipped, 4 xfailed, 206 warnings in 447.83 seconds > == > == 1912 passed, 88 skipped, 4 xfailed, 231 warnings in 492.50 seconds > == > > I was running the case at lower memory then, in case the issue would be an > OOM (to see if it breaks at the same place). And that indeed is it, hitting > the same spot now. > > So it is quite likely that if we mark it as huge test it will work. > After Andreas was so kind to refresh my memory on how this is done > (Thanks!) I was opening an MP for that. > => > https://code.launchpad.net/~paelzer/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/380362 > Merged and re-tests worked, python3-cffi should now drop out of our proposed issues. > -- > Christian Ehrhardt > Staff Engineer, Ubuntu Server > Canonical Ltd > -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1866385] [NEW] [focal] kronosnet need fixes from just released upstream version
Public bug reported: >From Clusterlabs mailing list: All, We are pleased to announce the general availability of kronosnet v1.15 kronosnet (or knet for short) is the new underlying network protocol for Linux HA components (corosync), that features the ability to use multiple links between nodes, active/active and active/passive link failover policies, automatic link recovery, FIPS compliant encryption (nss and/or openssl), automatic PMTUd and in general better performance compared to the old network protocol. Highlights in this release: * Fix major interaction issues between applications gathering statistics and PMTUd. * Fix UDP socket options that could lead to knet not being properly functional * Man pages updates * Minor bug fixes Known issues in this release: * none The source tarballs can be downloaded here: https://www.kronosnet.org/releases/ Upstream resources and contacts: https://kronosnet.org/ https://github.com/kronosnet/kronosnet/ https://ci.kronosnet.org/ https://trello.com/kronosnet (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Freenode https://lists.kronosnet.org/mailman/listinfo/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team To be honest, we are so close to v1.15 that I think we should just merge latest: cd916c4 [stats] allow knet_link_get_status to operate in readlock context 86e0560 [stats] allow knet_handle_get_stats to operate in a readlock context 41f5a2a [rx] kill unused variable e61d086 [tests] rework test suite link port allocation e90cf36 [transports] use SO_REUSEADDR only for sctp fcbeda8 [man] Enhance prio description of POLICY_PASSIVE 3ba5ddf man: Change strcat to strncat ed7573d man: Fix covscan reports in doxyxml.c As it does not seem to need a freeze exception. ** Affects: kronosnet (Ubuntu) Importance: Wishlist Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Affects: kronosnet (Ubuntu Focal) Importance: Wishlist Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Also affects: kronosnet (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: kronosnet (Ubuntu Focal) Status: New => Confirmed ** Changed in: kronosnet (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: kronosnet (Ubuntu Focal) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to kronosnet in Ubuntu. https://bugs.launchpad.net/bugs/1866385 Title: [focal] kronosnet need fixes from just released upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1866385/+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 1863970] Re: FTBFS on i386 due to autopkgtest failure due to dependence on gcc, make
I believe this was fixed already so Im closing it as Fix Released. ** Changed in: kronosnet (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to kronosnet in Ubuntu. https://bugs.launchpad.net/bugs/1863970 Title: FTBFS on i386 due to autopkgtest failure due to dependence on gcc, make To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/1863970/+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 1866383] [NEW] [focal] resource-agents need fixes from just released upstream version
Public bug reported: ClusterLabs released resource-agents v4.5.0 right after our freeze for Focal: ClusterLabs is happy to announce resource-agents v4.5.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.5.0 The most significant enhancements in this release are: - bugfixes and enhancements: - iSCSILogicalUnit: fix default value for OCF_RESKEY_liot_bstype - aws-vpc-move-ip: add parameter for role to use to query/update route table - Filesystem: add trigger_udev_rules_if_need() for -U, -L, or /dev/xxx device - Filesystem: refresh UUID in the start phase - IPaddr2: add noprefixroute parameter - IPaddr2: add info to metadata that ipt_CLUSTERIP "iptables" extension is not "nft" backend compatible, and iptables-legacy support for distros that still support it - IPsrcaddr: replace local rule if using local table, and set src back to primary for device on stop - IPsrcaddr: fix failure during probe when using destination/table parameters - LVM-activate: add OCF_CHECK_LEVEL 10 check that can be enabled to verify vg or lv validity with an additional "read 1 byte" test in special cases like iSCSI SAN - MailTo: fix variable expansion - SAPInstance: clear the $DIR_EXECUTABLE variable so we catch the situation when we lose the directory with binaries after first sapinstance_init invokation - aliyun-vpc-move-ip: add support for both 'go' and 'python' versions of Aliyun CLI, and auto-detect which to use by default - apache: use get_release_id() to detect OS/distro, and fix LOAD_STATUS_MODULE issue - azure-lb set socat to default on SUSE distributions. - exportfs: allow multiple exports of same directory - iSCSILogicalUnit: add liot_bstype to handle block/fileio for targetcli, and change behavior of lio-t with portals which do not use 0.0.0.0 - ldirectord: support sched-flags - lvmlockd: fix for LVM2 v2.03+ removing lvmetad - mysql-common: return correct rc during start-action - oralsnr: allow using the same tns_admin directory for different listeners - pgsql: Support for PostgreSQL 12 - podman: improve the code for checking if an image exists - rabbitmq-cluster: ensure we delete nodename if stop action fails - redis: validate_all: fix file status tests - spec: add missing requirement (lsb-release) The full list of changes for resource-agents is available at: https://github.com/ClusterLabs/resource-agents/blob/v4.5.0/ChangeLog The fixes among all delta are: 6d0b9652 iSCSILogicalUnit: fix default value for OCF_RESKEY_liot_bstype 617adbf6 redis: validate_all: fixes file status tests 7afc581f IPsrcaddr: fixes to avoid failing during probe d763318c [podman] Simplify the code for checking if an image exists 0e73d3f4 IPsrcaddr: fixes to replace local rule if using local table caaeec0b iSCSI logical unit fix (#1435) 34b46b17 IPaddr2: add noprefixroute parameter 20ff678e Low: MailTo: fix variable expansion d821ef33 iSCSILogicalUnit.in fixes (#1427) c718050a Low: mysql-common: fix startup check And I should revisit that. ** Affects: resource-agents (Ubuntu) Importance: Wishlist Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Affects: resource-agents (Ubuntu Focal) Importance: Wishlist Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: resource-agents (Ubuntu) Status: New => Confirmed ** Changed in: resource-agents (Ubuntu) Importance: Undecided => Wishlist ** Changed in: resource-agents (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Also affects: resource-agents (Ubuntu Focal) Importance: Wishlist Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to resource-agents in Ubuntu. https://bugs.launchpad.net/bugs/1866383 Title: [focal] resource-agents need fixes from just released upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383/+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 1866384] [NEW] delv fails with "ran out of space"
Public bug reported: Upstream report: https://gitlab.isc.org/isc-projects/bind9/issues/1647 Confirmed in ubuntu 20.04: ubuntu@f1:~$ delv isc.org ;; /etc/bind/bind.keys:31: failed to add trusted key '.': ran out of space ;; setup_dnsseckeys: failure ubuntu@f1:~$ dpkg -l bind9 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii bind9 1:9.16.0-1ubuntu3 amd64Internet Domain Name Server ** Affects: bind9 (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1866384 Title: delv fails with "ran out of space" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866384/+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 1866378] [NEW] Error in handling TCP client quota limits
Public bug reported: See advisory at https://kb.isc.org/docs/operational-notification-an- error-in-handling-tcp-client-quota-limits-can-exhaust-tcp-connections- in-bind-9160 Patch: https://downloads.isc.org/isc/bind9/9.16.0/patches/bind-v9.16.0-tcp_quota_fix.patch ** Affects: bind9 (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1866378 Title: Error in handling TCP client quota limits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866378/+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 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
** Also affects: openldap (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
Thanks a lot for this Ryan, and awesome testing script! -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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: Triage report (2020-03-05)
Hi, On Fri, Mar 6, 2020 at 12:53 PM Paride Legovini wrote: > LP: #1865338 - (New)[php7.2] - zend_string_init > error: Cannot access memory > > It's difficult to take action on this one without a reproducer. > Tagged server-triage-discuss as I'd like to hear what you think. I'd try to get a backtrace from the coredump, with symbols, to determine where the crash happened. I've seen cases in the past where it was in a third-party module not shipped with ubuntu, which invalidated the bug. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Random tools I've found interesting
> On Fri, Mar 6, 2020 at 12:47 PM Ryan Harper wrote:
> > # /home/rharper/.ssh/config.defaults
> > Host *.lxd
> > User ubuntu
> > IdentityFile /home/rharper/.ssh/id_rsa
> > StrictHostKeyChecking no
> > UserKnownHostsFile /dev/null
> > ProxyCommand nc $(lxc list -c s4 $(basename %h .lxd) | awk '/RUNNING/
> > {print $4}') %p
>
> I'm sad because DNS resolution used to work out of the box for *.lxd
> domains in the past. It was easy to configure "Hey, for this domain
> lxd, use that nameserver". I haven't been able to configure this
> anymore in recent ubuntu releases. The best I got was a dns loop and
> 100% cpu usage.
I loved using the proxy command for it. I've been putting lxd network
into kvm network and using the NSS libvirt plugins to solve lxc names:
rafaeldtinoco@workstation:~$ virsh net-dumpxml default
default
c6d5e95a-6c5a-4e17-9ae3-38f43c386c0d
rafaeldtinoco@workstation:~$ cat /etc/nsswitch.conf | grep hosts
hosts: files libvirt_guest libvirt dns
rafaeldtinoco@workstation:~$ lxc profile show default | grep -B2 brdefault
name: eth0
nictype: bridged
parent: brdefault
So nss would solve all libvirt virtual machine names first, then
hostnames got by the dhcp leases from virtual machines AND lxd
containers and then all th rest. But I guess I can use .lxd and .kvm
(virsh list --all) and it will be better.
For the LXD profiles, I have a few depending on different needs:
https://github.com/rafaeldtinoco/provision/tree/master/lxd/profiles
$ lxc launch ubuntu-daily:focal apache2fix
$ lxc launch -p debian-default images: debian
$ lxc launch -p cluster ubuntu-daily:focal pacemakerdev
and all my networks are libvirt networks so I can have LXD and KVM
guests in the same bridges, like when using the cluster yaml profile
definition:
devices:
eth0:
name: eth0
nictype: bridged
parent: brdefault
type: nic
iscsi01:
name: iscsi01
nictype: bridged
parent: iscsi01
type: nic
iscsi02:
name: iscsi02
nictype: bridged
parent: iscsi02
type: nic
...
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
Re: Random tools I've found interesting
Hi
On Fri, Mar 6, 2020 at 12:47 PM Ryan Harper wrote:
> # /home/rharper/.ssh/config.defaults
> Host *.lxd
> User ubuntu
> IdentityFile /home/rharper/.ssh/id_rsa
> StrictHostKeyChecking no
> UserKnownHostsFile /dev/null
> ProxyCommand nc $(lxc list -c s4 $(basename %h .lxd) | awk '/RUNNING/
> {print $4}') %p
I'm sad because DNS resolution used to work out of the box for *.lxd
domains in the past. It was easy to configure "Hey, for this domain
lxd, use that nameserver". I haven't been able to configure this
anymore in recent ubuntu releases. The best I got was a dns loop and
100% cpu usage.
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
Re: Random tools I've found interesting
On Fri, Mar 06, 2020 at 09:46:29AM -0600, Ryan Harper wrote: > (neipa) ~ % ssh f2.lxd > Warning: Permanently added 'f2.lxd' (ECDSA) to the list of known hosts. > > ubuntu@f2:~$ I have something similar, but different: https://git.launchpad.net/~racb/+git/tools/tree/lxd-ssh Differences: No ssh host key spam as it automatically syncs ~/.ssh/known_hosts with the container's public keys. Doesn't need/rely on networking - it uses lxc exec internally. signature.asc Description: PGP signature -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Triage report (2020-03-05)
# Triage 25 bugs to triage, worth mentioning: LP: #1864958 - (Incomplete) [mysql-8.0] - package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 This could be a valid mysql "failed to install/upgrade" bug. Still waiting for feedback from the bug submitter. Lars Tangvald is driving it. LP: #1865501 - (New)[libpcap-dev] libpcap-dev and derivatives missing libpcap.pc Valid issue in Bionic, fixed in >=Eoan as noted by Andreas. Marked it as Triaged and added it to our work queues (subscription and server-next). Should be a "patch on a plate" scenario. Added a Trusty "wontfix" task for clarity, as the bug submitted mentioned Trusty. LP: #1865338 - (New)[php7.2] - zend_string_init error: Cannot access memory It's difficult to take action on this one without a reproducer. Tagged server-triage-discuss as I'd like to hear what you think. Paride -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Random tools I've found interesting
On Thu, Mar 5, 2020 at 1:53 PM Bryce Harrington <
bryce.harring...@canonical.com> wrote:
> As followup to our retrospective, this past year I've found and played
> with several tools, that I thought might be worth show-and-telling
> about, and given our corona-sprint we're in will do so via email:
>
>
> == LXD Login ==
>
> I'm always looking for ways to improve my user experience with lxc
> containers. Logging in has always felt a bit baroque, so I've been
> scouring for simpler solutions. I found out that LXD supports
> 'aliases', and that you can construct a login alias, which works pretty
> good.
>
> $ lxc alias add login 'exec @ARGS@ --mode interactive -- bash -xac
> $@bryce - exec /bin/login -p -f '
>
If you're using system containers with networking, I very much like this
ssh config:
# /home/rharper/.ssh/config.defaults
Host *.lxd
User ubuntu
IdentityFile /home/rharper/.ssh/id_rsa
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
ProxyCommand nc $(lxc list -c s4 $(basename %h .lxd) | awk '/RUNNING/
{print $4}') %p
With an update to the lxd default profile:
(neipa) ~ % cat user-data.txt
#cloud-config
ssh_authorized_keys:
- ssh-rsa
(neipa) ~ % lxc profile set default user.user-data - < user-data.txt
(neipa) ~ % lxc launch ubuntu-daily:focal f2
Creating f2
Starting f2
(neipa) ~ % ssh f2.lxd
Warning: Permanently added 'f2.lxd' (ECDSA) to the list of known hosts.
ubuntu@f2:~$
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
Re: Random tools I've found interesting
> == LXD Login == > > $ lxc alias add login 'exec @ARGS@ --mode interactive -- bash -xac $@bryce > - exec /bin/login -p -f ' > This is similar to 'ctool exec --container=mycontainer --user=bryce'. It doesn't use 'login', so I'm not sure what effect that actually has on things, but you don't need 'script /dev/null'. ctool is part of the scripts ubuntu server team uses for different things. It lives https://github.com/CanonicalLtd/uss-tableflip/tree/master/scripts . I just put a pull request up to add some better usage doc: https://github.com/CanonicalLtd/uss-tableflip/pull/38/files On Thu, Mar 5, 2020 at 2:53 PM Bryce Harrington wrote: > > As followup to our retrospective, this past year I've found and played > with several tools, that I thought might be worth show-and-telling > about, and given our corona-sprint we're in will do so via email: > > > == so-trello == > > This CLI allows programmatic interaction with Trello boards. It was > written by our own Kernel team's Andy Whitcroft. > > This looks like it could be handy for bulk operations, cronned/automated > card update tasks, and the like. > > So-trello can be downloaded from the snap store > (https://snapcraft.io/so-trello), or installed directly: > > $ sudo snap install so-trello > > > == LXD Login == > > I'm always looking for ways to improve my user experience with lxc > containers. Logging in has always felt a bit baroque, so I've been > scouring for simpler solutions. I found out that LXD supports > 'aliases', and that you can construct a login alias, which works pretty > good. > > $ lxc alias add login 'exec @ARGS@ --mode interactive -- bash -xac $@bryce > - exec /bin/login -p -f ' > > (The trailing space after the -f is important). Replace 'bryce' with > 'ubuntu' or whatever username you use in your containers. > > Unfortunately, it still requires running `script /dev/null` after > logging in... would love to figure out how to eliminate that step. > > Bonus, here's an alias to make a prettier lxc listing: > > $ lxc alias add ls 'list -c ns4,user.comment:comment' > > If I'm late to the party and y'all already know about lxd aliases, well > boo, but show me *your* aliases! (And we should add this to starter > docs...) > > > == YAML Parser for Bash scripts - yaml.sh == > > I like YAML and I like writing in Bash, but the two don't fit together > naturally. Scouring the web for solutions, I found AdrianDC's yaml.sh > which reads a YAML file and registers its parameters as prefixed ENV > vars. Quite handy. > > yaml.sh can be downloaded from: > > $ wget > https://raw.githubusercontent.com/jasperes/bash-yaml/master/script/yaml.sh > > > == shellcheck == > > Probably known to all Bash aficionados already, but 'shellcheck' is so > handy worth extra mention. It runs a lint check on bash scripts to > identify syntax improvements. Very helpful for catching errors too. > > $ sudo apt-get install shellcheck > > > == distro-info == > > Another one I'm sure you all already know about, but if not, distro-info > is another handy tool for looking up information about Debian and Ubuntu > releases. Good way to avoid hardcoding things in your own scripts. > > $ sudo apt-get install distro-info > > What's the current development version's codename? > > $ distro-info -d > focal > > What's bionic's release number? > > $ distro-info --release --series bionic | cut -d' ' -f1 > 18.04 > > Is disco still supported? > > $ (distro-info --supported | grep disco) || echo "Nope!" > Nope! > > > > > > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
** Changed in: openldap (Ubuntu) Status: New => In Progress ** Changed in: openldap (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1866119] Re: [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1
** Merge proposal unlinked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/380336 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1866119 Title: [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1866119/+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
Triage and migration report - Friday
## Triage ## I got 21 bugs I was happy to find that most of them were bumps to fix released or fixes that were started. One can see that the Feature Freeze has passed and bug work is increasing again. The TLS v1.3 bugs were mentioned by others yesterday, no further updates to those yet since yesterday. Three bugs needed a proper initial triage and some minor testing. One of these that is worth mentioning is: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1865818 I think we should try to take a look at picking the patch and modifying the postinst beofre 20.04. Subscribed the team and tagged as server-next. ## Proposed migration ## Most things in our queue are valid but depending on bigger migrations. The obvious ruby/php candidates are being worked on. The one thing worth to look at (again) is python-cffi which breaks and holds back python-defaults a while now. Paride mentioned that test on 2020-02-27: It seems the autopkgtest run got a sigkill: [...] ..s...s.ss.Killed It was even mentioned before on 2020-01-16 missing dep: libffi but that is good now. Nowadays it is important to know that there is a new version of it python-cffi | 1.13.2-1build3 | focal/universe | all python-cffi | 1.14.0-1build1 | focal-proposed | source python-cffi | 1.14.0-1build1 | focal-proposed/universe | all Recent tests had: - the new python3-defaults against the old version of python-cffi - the new python-cffi against python3-defaults One outlier also had "ModuleNotFoundError". But that was before a rebuild to drop python 3.7 and is resolved. The other fails of the new version still fail with the "Killed" message. Lets try to run that with new python + new python-cffi and do so in a local VM for debugging right away. The test has a python2 and a python3 test component. In the past both failed with the kill-symptom. I ran the new cffi against three sets: - old python3-defaults - new python3-defaults - all-proposed And of course, they ALL passed the tests :-/ So much for reproducibility. == 1912 passed, 88 skipped, 4 xfailed, 206 warnings in 447.83 seconds == == 1912 passed, 88 skipped, 4 xfailed, 231 warnings in 492.50 seconds == I was running the case at lower memory then, in case the issue would be an OOM (to see if it breaks at the same place). And that indeed is it, hitting the same spot now. So it is quite likely that if we mark it as huge test it will work. After Andreas was so kind to refresh my memory on how this is done (Thanks!) I was opening an MP for that. => https://code.launchpad.net/~paelzer/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/380362 -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 1866119] Re: [bionic] fence_scsi not working properly with Pacemaker 1.1.18-2ubuntu1.1
** Description changed: OBS: This bug was originally into LP: #1865523 but it was split. SRU: pacemaker [Impact] - * fence_scsi is not currently working in a share disk environment + * fence_scsi is not currently working in a share disk environment - * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't + * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't be able to start the fencing agents OR, in worst case scenarios, the fence_scsi agent might start but won't make scsi reservations in the shared scsi disk. - * this bug is taking care of pacemaker 1.1.18 issues with fence_scsi, + * this bug is taking care of pacemaker 1.1.18 issues with fence_scsi, since the later was fixed at LP: #1865523. [Test Case] - * having a 3-node setup, nodes called "clubionic01, clubionic02, + * having a 3-node setup, nodes called "clubionic01, clubionic02, clubionic03", with a shared scsi disk (fully supporting persistent reservations) /dev/sda, with corosync and pacemaker operational and running, one might try: rafaeldtinoco@clubionic01:~$ crm configure crm(live)configure# property stonith-enabled=on crm(live)configure# property stonith-action=off crm(live)configure# property no-quorum-policy=stop crm(live)configure# property have-watchdog=true crm(live)configure# commit crm(live)configure# end crm(live)# end rafaeldtinoco@clubionic01:~$ crm configure primitive fence_clubionic \ - stonith:fence_scsi params \ - pcmk_host_list="clubionic01 clubionic02 clubionic03" \ - devices="/dev/sda" \ - meta provides=unfencing + stonith:fence_scsi params \ + pcmk_host_list="clubionic01 clubionic02 clubionic03" \ + devices="/dev/sda" \ + meta provides=unfencing And see the following errors: Failed Actions: * fence_clubionic_start_0 on clubionic02 'unknown error' (1): call=6, status=Error, exitreason='', - last-rc-change='Wed Mar 4 19:53:12 2020', queued=0ms, exec=1105ms + last-rc-change='Wed Mar 4 19:53:12 2020', queued=0ms, exec=1105ms * fence_clubionic_start_0 on clubionic03 'unknown error' (1): call=6, status=Error, exitreason='', - last-rc-change='Wed Mar 4 19:53:13 2020', queued=0ms, exec=1109ms + last-rc-change='Wed Mar 4 19:53:13 2020', queued=0ms, exec=1109ms * fence_clubionic_start_0 on clubionic01 'unknown error' (1): call=6, status=Error, exitreason='', - last-rc-change='Wed Mar 4 19:53:11 2020', queued=0ms, exec=1108ms + last-rc-change='Wed Mar 4 19:53:11 2020', queued=0ms, exec=1108ms and corosync.log will show: warning: unpack_rsc_op_failure: Processing failed op start for fence_clubionic on clubionic01: unknown error (1) [Regression Potential] - * LP: #1865523 shows fence_scsi fully operational after SRU for that + * LP: #1865523 shows fence_scsi fully operational after SRU for that bug is done. - * LP: #1865523 used pacemaker 1.1.19 (vanilla) in order to fix + * LP: #1865523 used pacemaker 1.1.19 (vanilla) in order to fix fence_scsi. - * TODO + * There are changes to: cluster resource manager daemon, local resource + manager daemon and police engine. From all the changes, the police + engine fix is the biggest, but still not big for a SRU. This could cause + police engine, thus cluster decisions, to mal function. + + * All patches are based in upstream fixes made right after + Pacemaker-1.1.18, used by Ubuntu Bionic and were tested with fence_scsi + to make sure it fixed the issues. [Other Info] - * Original Description: + * Original Description: Trying to setup a cluster with an iscsi shared disk, using fence_scsi as the fencing mechanism, I realized that fence_scsi is not working in Ubuntu Bionic. I first thought it was related to Azure environment (LP: #1864419), where I was trying this environment, but then, trying locally, I figured out that somehow pacemaker 1.1.18 is not fencing the shared scsi disk properly. Note: I was able to "backport" vanilla 1.1.19 from upstream and fence_scsi worked. I have then tried 1.1.18 without all quilt patches and it didnt work as well. I think that bisecting 1.1.18 <-> 1.1.19 might tell us which commit has fixed the behaviour needed by the fence_scsi agent. (k)rafaeldtinoco@clubionic01:~$ crm conf show node 1: clubionic01.private node 2: clubionic02.private node 3: clubionic03.private primitive fence_clubionic stonith:fence_scsi \ params pcmk_host_list="10.250.3.10 10.250.3.11 10.250.3.12" devices="/dev/sda" \ meta provides=unfencing property cib-bootstrap-options: \ have-watchdog=false \ dc-version=1.1.18-2b07d5c5a9 \ cluster-infrastructure=corosync \ cluster-name=clubionic \ stonith-enabled=on \ stonith-action=off \ no-quorum-policy=stop \ symmetric-cluster=true
