This bug was fixed in the package pacemaker - 2.0.3-3ubuntu4
---
pacemaker (2.0.3-3ubuntu4) focal; urgency=medium
* Fix clock_gettime() timing functions (LP: #1881762)
+ d/p/ubuntu-2.0.3-fixes/lp1881762-*:
- 01-Executor-systemd-execution-time-fixes.patch
-
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/392509
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/392510
--
You received this bug notification
After testing I can confirm that this new version by all accounts fixes the
reported bug.
Stopping and starting a systemd resource with timeout = "10s" does not fail
with timeouts
I tested this by installing the original 2.0.3-3ubuntu3, and reproducing the
bug.
then I upgraded to
The autopkgtests results above look like a regression in crmsh DEP8
because of some other change (an apt-cache | grep "Package" command is
not working for crmsh) and unrelated to this upload (as other tests have
passed).
--
You received this bug notification because you are a member of Ubuntu
@jason,
I could verify this SRU but I'll let you handle it as you were the
reporter. Could you please change tags from "needed" to "done" when
you're good ? This will sinalize the update can migrate from -proposed
to -updates.
Thanks again for reporting this!
-rafaeldtinoco
--
You received
Hello Jason, or anyone else affected,
Accepted pacemaker into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pacemaker/2.0.3-3ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
* Cluster resource operation timeouts are not working correctly for
systemd resources and should be working. Timeouts are important in order
for the actions executed by pacemaker - for the systemd resource in
question - don't wait forever to start
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391960
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource
** Changed in: pacemaker (Ubuntu Focal)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu Focal)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[rafaeldtinoco@gitubuntu pacemaker]$ git push pkg --delete upload/2.0.3-3ubuntu4
To ssh://git.launchpad.net/ubuntu/+source/pacemaker
- [deleted] upload/2.0.3-3ubuntu4
[rafaeldtinoco@gitubuntu pacemaker]$ git tag -d upload/2.0.3-3ubuntu4
Deleted tag 'upload/2.0.3-3ubuntu4' (was
@racb could you, please, review it again for me ? I have done what we
agreed on.
Thanks a lot!
-rafaeldtinoco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not
After having my new fix (about to be uploaded):
[rafaeldtinoco@focal01 ~]$ crm status
Cluster Summary:
* Stack: corosync
* Current DC: focal01 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated: Sun Oct 4 14:19:09 2020
* Last change: Sun Oct 4 14:19:07 2020 by root via
** Description changed:
[Impact]
- * Cluster resource timeouts are not working and should be working.
- Timeouts are important in order for the actions (done by the resource)
- don't timeout before we're expecting (sometimes starting a resource can
- take more time than the default time
** Description changed:
- SRU reviewer:
-
- The merge request has been reviewed by @paelzer initially, before the
- SRU review. The most important comment is this:
-
-
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391398/comments/1030355
-
-
I spoke to Rafael and we agreed that he would prepare a more minimal
SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications
SRU reviewer:
https://pastebin.ubuntu.com/p/PcZq7Hr3NQ/
These are the functional tests results.
There was an issue running one test, I had to re-ran, and it is all
good:
Oct 01 04:09:09 Running test SimulStop (focal02) [ 1]
Oct 01 04:09:24 Stopping Cluster Manager on all
SRU reviewer:
https://pastebin.ubuntu.com/p/rgVVb66xGd/
These are the regression tests results. All good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not
For the SRU reviewer:
I have uploaded the source code with the orig.tar.gz together (not sure
if this is a blocker as the package is waiting for approval in queue and
has not been rejected). Please find me on IRC so I can re-upload it if
needed.
Thank you!
** Description changed:
+ SRU
I can confirm that this fixes the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
Hello,
Do you have any updates on this ?
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go
** Description changed:
[Impact]
- * Cluster resource timeouts are not working and should be working.
- Timeouts are important in order for the actions (done for the resource)
+ * Cluster resource timeouts are not working and should be working.
+ Timeouts are important in order for the
** Also affects: pacemaker (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391398
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource
** Description changed:
+ [Impact]
+
+ * Cluster resource timeouts are not working and should be working.
+ Timeouts are important in order for the actions (done for the resource)
+ don't timeout before we're expecting (sometimes starting a resource can
+ take more time than the default time
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/391397
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource
These are the patches being backported from upstream:
* Post 2.0.3 release fixes backported to Ubuntu: Fix resource timeout
functionality (LP: #1881762)
debian/patches/ubuntu-2.0.3-fixes/:
-
lp1881762-0001-e0e59163-Build-configure-remove-no-longer-needed-LIBADD_INTL-.patch
-
Thanks for the work on that, very nice turn around time;
lowering to field-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage
I'll provide a PPA with:
commit c9be5b271
Merge: 72a1f4834 08e3f7e44
Author: Ken Gaillot
Date: Fri Feb 21 14:57:57 2020
Merge pull request #1992 from kgaillot/times
Fix systemd support when using clock_gettime()
and
commit 8254f3d25
Merge: 0625eb1a2 71ae72df9
Author: Ken
I'm on it now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
Because of the blocking for charmed kubernetes on focal; we're raising
this bug to field critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
This bug is preventing Charmed Kubernetes from working with hacluster on
Ubuntu 20.04 (Focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To
** Changed in: pacemaker (Ubuntu)
Status: New => Triaged
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
32 matches
Mail list logo
