sbd autopkgtest regresion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| sbd (Ubuntu) |
Medium
|
Rafael David Tinoco |
Bug Description
While proposed-migration shows us:
sbd (1.3.1-4 to 1.4.0-18-
Maintainer: Debian HA Maintainers
Section: universe/misc
68 days old
autopkgtest for sbd/1.4.
Invalidated by dependency
Depends: sbd pacemaker (not considered)
Not considered
previous rdependency triggered autopkgtests (corosync as trigger) reported:
autopkgtest for sbd/1.3.1-4: amd64: Ignored failure, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Pass
autopkgtest [19:17:07]: test corosync: [------
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
autopkgtest [19:17:09]: test corosync: -------
autopkgtest [19:17:13]: test corosync: - - - - - - - - - - results - - - - - - - - - -
corosync FAIL non-zero exit status 1
Investigate if its intermittent or not.
Changed in sbd (Ubuntu): | |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
status: | New → Confirmed |
importance: | Undecided → Medium |
Christian Ehrhardt (paelzer) wrote : | #2 |
I did some combined triggers with the new corosync / pacemaker.
It is still failing (only on armhf btw).
You did some magic there:
sbd (1.3.1-4 to 1.4.0-18-
Maintainer: Debian HA Maintainers
Section: universe/misc
90 days old
autopkgtest for sbd/1.4.
Invalidated by dependency
Depends: sbd pacemaker (not considered)
Not considered
I guess this bug is "wont fix" now ?
Thanks!
Christian Ehrhardt (paelzer) wrote : | #4 |
With those new triggers we always see the service failing:
Setting up corosync (3.0.1-2ubuntu1) ...
Created symlink /etc/systemd/
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
Setting up autopkgtest-satdep (0) ...
Processing triggers for systemd (240-6ubuntu9) ...
Processing triggers for libc-bin (2.29-0ubuntu3) ...
(Reading database ... 75495 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [07:33:56]: test corosync: [------
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
Installing that on an armhf VM myself.
$ sudo apt install sdb corosync
...
Christian Ehrhardt (paelzer) wrote : | #5 |
This actually works just fine ...
ubuntu@
Hit:1 http://
Hit:2 http://
Hit:3 http://
Get:4 http://
Hit:5 http://
Get:6 http://
Get:7 http://
Get:8 http://
Get:9 http://
Get:10 http://
Get:11 http://
Get:12 http://
Get:13 http://
Get:14 http://
Get:15 http://
Get:16 http://
Fetched 1151 kB in 40s (29.0 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
48 packages can be upgraded. Run 'apt list --upgradable' to see them.
ubuntu@
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
binfmt-support ca-certificates
libcpg4 libicsharpcode-
libicsharpcod
libmono-
libmono-
libmono-
libmono-
libxslt1.1 mono-4.0-gac mono-gac mono-runtime mono-runtime-common mono-runtime-sgen
xsltproc
Suggested packages:
libicsharpcod
| libgnome2-0 | konqueror
The following NEW packages will be installed:
binfmt-support ca-certificates
libcorosync-
libicsharpcod
libmono-
libmono-
libmono-
Christian Ehrhardt (paelzer) wrote : | #6 |
So after we now know that this would actually work we have to realize that this is just another case of failing on the armhf container (which Rafael already explained is the case).
Suggestion:
- fail-badtest this version
- submit to Debian to replace the isolation-container with isolation-machine
Christian Ehrhardt (paelzer) wrote : | #7 |
Actually since we upload a new version already, we can skip the badtest.
We block on others still, so it won't give us a speed bonus to resolve this.
Christian Ehrhardt (paelzer) wrote : | #8 |
Uploaded to Eoan with isolation-machine on the failing test.
Suggested to Debian as well in https:/
Christian Ehrhardt (paelzer) wrote : | #9 |
The upload worked and arm is fixed as expected.
This triggered an issue with both x86 tests, but that was expected as we have known that they only work if executred with the new pacemaker/corosync in proposed.
I have re-triggered those two to resolve as well.
corosync (in regard to sbd) is unblocked now.
looks like crmsh has a similar issue, I'm fixing it!
G.
Launchpad Janitor (janitor) wrote : | #11 |
This bug was fixed in the package sbd - 1.4.0-18-
---------------
sbd (1.4.0-
* d/t/control: corosync won't always start correctly in containers breaking
the corosync test when the test dependencies are installed. Needs to be
marked isolation-machine (LP: #1837091)
-- Christian Ehrhardt <email address hidden> Fri, 09 Aug 2019 07:24:40 +0200
Changed in sbd (Ubuntu): | |
status: | Confirmed → Fix Released |
This is blocking: /bugs.launchpad .net/ubuntu/ +source/ corosync/ +bug/1837064
https:/