corosync migration failed autopkgtests

Bug #1837064 reported by Rafael David Tinoco on 2019-07-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
corosync (Ubuntu)
High
Rafael David Tinoco
Eoan
High
Rafael David Tinoco

Bug Description

From the excuses page:

corosync (2.4.4-3 to 3.0.1-2)
Maintainer: Debian HA Maintainers
164 days old
autopkgtest for corosync/3.0.1-2: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
autopkgtest for corosync-qdevice/3.0.0-4: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
autopkgtest for crmsh/3.0.1-3ubuntu1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
autopkgtest for dlm/4.0.7-4: amd64: Pass, arm64: Always failed, armhf: Always failed, i386: Pass, ppc64el: Always failed, s390x: Always failed
autopkgtest for gfs2-utils/3.2.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
autopkgtest for ocfs2-tools/1.8.5-7build1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, s390x: Ignored failure
autopkgtest for ocfs2-tools/unknown: armhf: Regression ♻
autopkgtest for pacemaker/1.1.18-2ubuntu1: amd64: Regression ♻ , arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻
autopkgtest for sbd/1.3.1-4: amd64: Ignored failure, arm64: Pass, armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: Pass
Not considered

----

Checking the regression: http://bit.ly/2LtU9TG

autopkgtest [09:47:06]: test pacemaker-node-status.sh: [-----------------------
+ DAEMON_TIMEOUT=60
+ CRM_TIMEOUT=5
+ NODE=node1
+ service corosync start
+ service pacemaker start
+ sleep 60
+ crm status
+ grep ^Online:.*node1
autopkgtest [09:48:13]: test pacemaker-node-status.sh: -----------------------]
autopkgtest [09:48:15]: test pacemaker-node-status.sh: - - - - - - - - - - results - - - - - - - - - -
pacemaker-node-status.sh FAIL non-zero exit status 1

and

autopkgtest [10:07:39]: test pacemaker-cluster-init.sh: -----------------------]
autopkgtest [10:07:41]: test pacemaker-cluster-init.sh: - - - - - - - - - - results - - - - - - - - - -
pacemaker-cluster-init.sh PASS
autopkgtest [10:07:43]: @@@@@@@@@@@@@@@@@@@@ summary
command1 PASS
command2 PASS
command3 PASS
utils.sh PASS
pacemaker-basic-resource.sh PASS
pacemaker-node-status.sh FAIL non-zero exit status 1

Changed in corosync (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Rafael David Tinoco (rafaeldtinoco)

This original problem was solved in armhf by doing:

corosync (3.0.1-2ubuntu1) eoan; urgency=medium

  * Skip autopkgtest for unprivileged containers: (LP: #1828228)
    - d/t/control: mark corosync test as skippable
    - d/t/corosync: skip if memlock can't be set to unlimited by root

Which disabled the test in any lxd unprivileged environment.

Changed in corosync (Ubuntu Eoan):
status: Confirmed → In Progress

There is still other regressions to solve:

autopkgtest for corosync-qdevice/3.0.0-4: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
(https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1837090)

autopkgtest for crmsh/4.0.0~git20190108.3d56538-3ubuntu1: amd64: Pass, arm64: Pass, armhf: Regression ♻ , i386: Pass, ppc64el: Pass, s390x: Pass
(https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1837072)

autopkgtest for sbd/1.4.0-18-g5e3283c-1: armhf: Regression ♻ , i386: Regression ♻
(https://bugs.launchpad.net/ubuntu/+source/sbd/+bug/1837091)

Corosync was cleaned up in excuses for Eoan.

Changed in corosync (Ubuntu Eoan):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers