This bug was fixed in the package sbd - 1.4.0-18-g5e3283c-1ubuntu1
---
sbd (1.4.0-18-g5e3283c-1ubuntu1) eoan; urgency=medium
* d/t/control: corosync won't always start correctly in containers breaking
the corosync test when the test dependencies are installed. Needs to be
looks like crmsh has a similar issue, I'm fixing it!
G.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837091
Title:
sbd autopkgtest regresion
To manage notifications about this bug go to:
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
Uploaded to Eoan with isolation-machine on the failing test.
Suggested to Debian as well in https://salsa.debian.org/ha-
team/sbd/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
This actually works just fine ...
ubuntu@eoan-armhf:~$ sudo apt update
Hit:1 http://ports.ubuntu.com/ubuntu-ports eoan InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports eoan-updates InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports eoan-backports InRelease
Get:4
With those new triggers we always see the service failing:
Setting up corosync (3.0.1-2ubuntu1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/corosync.service →
/lib/systemd/system/corosync.service.
Job for corosync.service failed because the control process exited with error
You did some magic there:
sbd (1.3.1-4 to 1.4.0-18-g5e3283c-1)
Maintainer: Debian HA Maintainers
Section: universe/misc
90 days old
autopkgtest for sbd/1.4.0-18-g5e3283c-1: amd64: Pass, arm64: Pass, armhf: Pass,
i386: Pass, ppc64el: Pass, s390x: Pass
Invalidated by dependency
Depends: sbd
I did some combined triggers with the new corosync / pacemaker.
It is still failing (only on armhf btw).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837091
Title:
sbd autopkgtest regresion
To
This is blocking:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1837064
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837091
Title:
sbd autopkgtest regresion
To manage notifications
** Changed in: sbd (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: sbd (Ubuntu)
Status: New => Confirmed
** Changed in: sbd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
12 matches
Mail list logo
