[Bug 1838024] Re: pacemaker migration failed autopkgtests

2019-08-15 Thread Rafael David Tinoco
Pacemaker was cleanup for Eoan migrations. ** Changed in: pacemaker (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838024 Title: pacemaker m

[Bug 1838024] Re: pacemaker migration failed autopkgtests

2019-08-08 Thread Rafael David Tinoco
After some test clean ups we did, we could obtain: pacemaker (1.1.18-2ubuntu1 to 2.0.1-4ubuntu2) Maintainer: Ubuntu Developers 13 days old autopkgtest for booth/1.0-162-g27f917f-2: amd64: Pass, arm64: Pass, armhf: Always failed, i386: Always failed, ppc64el: Pass, s390x: Pass autopkgtest for crms

[Bug 1838024] Re: pacemaker migration failed autopkgtests

2019-07-26 Thread Rafael David Tinoco
Related bug: 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/1838024 Title: pacemaker migration failed autopkgtests To manage notifica

[Bug 1838024] Re: pacemaker migration failed autopkgtests

2019-07-26 Thread Rafael David Tinoco
I'll rewrite both, corosync and pacemaker simple tests, and give it a try in new package versions. It will have more output (to debug possible issues) and will try to wait for an event, instead of waiting for time only. -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1838024] Re: pacemaker migration failed autopkgtests

2019-07-26 Thread Rafael David Tinoco
Last autopkgtest that succeed shows: autopkgtest [07:14:15]: test pacemaker: [--- + sleep 60 + crm_mon -1 + hostname -s + fgrep -20 Online: [ autopkgtest ] Stack: corosync Current DC: autopkgtest (version 1.1.18-2b07d5c5a9) - partition WITHOUT quorum Last updated: Tue Jul 16 07