** Also affects: resource-agents (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: resource-agents (Ubuntu Precise)
Status: New => Confirmed
** Changed in: resource-agents (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
This has been topic of multiple discussions
In focal:
(c)rafaeldtinoco@reviews:.../share/resource-agents/ocft$ sudo ./runocft
Making 'apache':
- case 0: check base env
- case 1: check base env: set non-existing OCF_RESKEY_statusurl
- case 2: check base env: set non-existing OCF_RESKEY_configfile
- case 3: normal start
-
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
This is already fixed in Focal and Precise
This merge will solve:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1627083
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1866383
Title:
[FFe][Focal] resource-agents
Marking it as won't fix because of the EOL for Precise.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to resource-agents in Ubuntu.
https://bugs.launchpad.net/bugs/998136
Title:
ocf RA for lxc doesn't work
To manage notifications about
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
It is unfortunate that we were unable to
Thank you for taking the time to file a bug report.
The reason for the failure seems to be:
Jun 30 03:38:03 zz376p1 ldirectord[5896]: Config file ldirectord.cf not found
Jun 30 03:38:03 zz376p1 systemd[1]: ldirectord.service: Control process exited,
code=exited status=1
And you can follow a
** Changed in: pcs (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: corosync (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
I'm setting this as won't fix as we already have a MIR for targetcli-fb:
https://bugs.launchpad.net/ubuntu/+source/targetcli-fb/+bug/1854362
So we can use LIO "by default" and in [main], replacing tgt.
That might hopefully happen in 20.10.
** Changed in: fence-agents (Ubuntu)
Status:
PPA successfully built pacemaker fixes:
https://launchpad.net/~ubuntu-server-ha/+archive/ubuntu/staging
and the merge request has been +1.
** Description changed:
- This bug backport/cherrypick fixes released after 2.0.3 release.
- The correct patches are going to be defined within this bug
** Description changed:
- Together with fix for:
-
- https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1869751 (FTBFS)
-
- This bug will also backport/cherrypick fixes released after 2.0.3
- release.
+ This bug backport/cherrypick fixes released after 2.0.3 release.
The correct
Thanks @doko,
This was fixed by:
# ftime causes deprecation errors now, but the clock_gettime replacement is
# disabled by default in 2.0.3. Enable it.
CPPFLAGS = -UPCMK_TIME_EMERGENCY_CGT
in
pacemaker (2.0.3-3ubuntu2) focal; urgency=medium
* Forcibly switch from ftime to clock_gettime,
16 matches
Mail list logo
