[Bug 1870235] [NEW] [focal] pacemaker v2.0.3 last upstream fixes
Public bug reported: 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: c1bc0a7f4 Merge pull request #2023 from kgaillot/fixes f00d1120f Merge pull request #2005 from clumens/tag-fixes 5c543bc73 Fix: xml: Add a new version of the tags schema. d9109fb83 Fix: tools: Apply various fixes to the crm_diff man page. 269aea44b Merge pull request #2017 from kgaillot/fixes ad532cfff Low: fencer,libstonithd: fix Y2038 issue in fence history ef2037126 Doc: libcrmcommon: fix doc string mistake f0be039f9 Merge pull request #2015 from clumens/more-blanks e2215c722 Fix: tools: One more blank line related fix for crm_mon. ef1208197 Merge pull request #2010 from kgaillot/fixes 4c997e61a Merge pull request #2006 from HideoYamauchi/trac4454-fix 7cd3ecfd3 Low: crm: Fix argument order in declaration 78db2071e Merge pull request #1999 from clumens/crm_mon-fixes 5e3b8cdba Merge pull request #2004 from jnpkrn/build-gcc10-s390x 4267f7fc4 Doc: Pacemaker Development: crm_str easy to forget, like its prime use 9acf1f9b3 Build: fix compilation -Werror compilation issue with GCC 10 with s390x 0625eb1a2 Merge pull request #1996 from kgaillot/fixes 902e79f43 Feature: Rework how a prefix for bans is given in crm_mon. 4860c572c Fix: tools: Move print_neg_location_prefix into options. 398611256 Fix: tools: Use formatted output for more errors in crm_mon. a290911ef Merge pull request #1989 from kgaillot/fixes 7599e6d98 Build: configure: fix syntax error 68bd2b4da Merge pull request #1953 from jnpkrn/build-fix-inkscape-1.0-beta-compat df6c286d9 Merge pull request #1985 from kgaillot/rhbz1760669 cdf84f849 Merge pull request #1984 from kgaillot/fixes 38ef24516 Merge pull request #1979 from kgaillot/fixes 403c5b1f8 Merge pull request #1978 from jnpkrn/gcc10-fno-common-fix ea5b06fae Merge pull request #1976 from jnpkrn/fix-process-will-not-die e0ca2a0b7 Fix: libpacemaker: Fix setting options when calling the history opt. 3fa025298 Fix: libpacemaker: Fix handling of some operation return values. 529ff2851 Merge pull request #1971 from clumens/crm_mon-fixes 5b98dd71c Fix: tools: Re-enable CGI output from crm_mon. ed6972a74 Fix: tools: Maintain a list of extra HTML headers. c2e5d2d02 Fix: tools: Correct sec vs. msec discrepancy in stonith_admin. bc6f54495 Merge pull request #1968 from kgaillot/fixes f11fedd40 Refactor: libcrmcommon,libpacemaker,tools: convert pcmk__output_new() to standard return codes 264afd724 Merge pull request #1958 from kgaillot/fixes aa779a942 Merge pull request #1960 from yoshfuji/fix-iso8601-parser-20191217 33e28dcad Merge pull request #1955 from kgaillot/fixes d671faa22 Merge pull request #1954 from aleksei-burlakov/fix-libpe_status-maintenance-mode 47ecd21b9 Build: fix unability to build with Inkscape 1.0 beta version(s) 4f5207a28 Fix: tools: Correct the crm_mon man page. The correct patches are going to be defined within this bug comments. ** Affects: pacemaker (Ubuntu) Importance: High Assignee: Rafael David Tinoco (rafaeldtinoco) Status: In Progress ** Changed in: pacemaker (Ubuntu) Status: New => In Progress ** Changed in: pacemaker (Ubuntu) Importance: Undecided => High ** Changed in: pacemaker (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1870235 Title: [focal] pacemaker v2.0.3 last upstream fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1870235/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1825992] Re: Upgrade to version 2.0 to satisfy pcs dependency
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. I have marked Disco was won't fix as it was EOL in this last January 2020. Currently, for focal we have: - PCS: 0.10.4-2ubuntu1 (Debian: 0.10.4-2, Upstream: 0.10.5) - COROSYNC: 3.0.3-2ubuntu1 (Debian: 3.0.3-2 +fixes, Upstream: v3.0.3) - PACEMAKER: 2.0.3-3ubuntu1 (Debian: 2.0.3-3, Upstream: 2.0.3) AND we're still targeting crmsh tool as the "official" way of setting up PACEMAKER. We are targeting PCS to replace CRMSH in a few releases from now (crmsh is currently back in [main] while PCS is still in [universe]). With that said I'm considering this bug as fix released since Eoan. ** No longer affects: pacemaker (Ubuntu Focal) ** Changed in: pacemaker (Ubuntu) Importance: Medium => Undecided ** Changed in: pacemaker (Ubuntu Eoan) Importance: Medium => Undecided -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1825992 Title: Upgrade to version 2.0 to satisfy pcs dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1825992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1828223] Re: pacemaker v2 appears to be missing log directory
As Paride mentioned, this is already fixed in Eoan and Focal and was an issue for Disco. ** Also affects: pacemaker (Ubuntu Focal) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Also affects: pacemaker (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Eoan) Status: New => Fix Released ** No longer affects: pacemaker (Ubuntu Focal) ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Triaged ** Changed in: pacemaker (Ubuntu) Status: Triaged => Won't Fix ** Changed in: pacemaker (Ubuntu Disco) Status: New => Won't Fix ** Changed in: pacemaker (Ubuntu) Status: Won't Fix => Fix Released ** Changed in: pacemaker (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: pacemaker (Ubuntu) Importance: Medium => Undecided -- 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/1828223 Title: pacemaker v2 appears to be missing log directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1828223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1828223] Re: pacemaker v2 appears to be missing log directory
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 resolve this defect, however there appears to be no further action possible at this time. I am therefore moving the bug to 'Incomplete'. If you disagree or have new information, we would be grateful if you could please add a comment stating why and then change the status of the bug to 'New'. -- 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/1828223 Title: pacemaker v2 appears to be missing log directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1828223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1825992] Re: Upgrade to version 2.0 to satisfy pcs dependency
** Also affects: pacemaker (Ubuntu Focal) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: pacemaker (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: pacemaker (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: pacemaker (Ubuntu Eoan) Status: Confirmed => Fix Released ** Changed in: pacemaker (Ubuntu Focal) Status: Confirmed => Fix Released ** Changed in: pacemaker (Ubuntu Focal) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: pacemaker (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1825992 Title: Upgrade to version 2.0 to satisfy pcs dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1825992/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1866383] Re: [FFe][Focal] resource-agents need fixes from recent release upstream version
This merge will solve: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383 ** Description changed: - ClusterLabs released resource-agents v4.5.0 right after our freeze for Focal: + # Feature Freeze Exception - resource-agents - + [Proposed Changes] + * Merge from v4.4.0 to v4.5.0 + + * ClusterLabs released resource-agents v4.5.0 right after our freeze for + Focal + + [Rationale for Exception] + + * resource-agents is a very important part of Ubuntu HA packageset. + + * You can follow the most important resource-agents in this e-mail + thread: + + https://lists.ubuntu.com/archives/ubuntu-devel/2020-March/040950.html + + * It is usually hard to do SRUs for resource-agents as we don't have a + quick and simple way to test all agents (as many of them depend on + specific setups) about to be fixed. + + * Best is to be synced with the upstream release... SPECIALLY since + 20.04 is a LTS version. Most of the delta is about fixes opened at + github issues and solved before their milestone. + + $ git log --no-merges v4.4.0..v4.5.0 --pretty=oneline --abbrev-commit + + fee18132 (tag: v4.5.0) build: update ChangeLog for 4.5.0 + a93fa4ee aws-vpc-move-ip: add routing_table_role parameter to metadata + 6d0b9652 iSCSILogicalUnit: fix default value for OCF_RESKEY_liot_bstype + eba85c2b (tag: v4.5.0rc1) build: update ChangeLog for 4.5.0-rc1 + a007883f lvmlockd: remove locking_type parameter from lvm.conf for LVM > v2.03 + 0a299ee9 [lvmlockd] support lvm2-2.03 removing lvmetad + 4bc84bcc Allow user to specify role with which to query/update route table + 2e288c23 oralsnr: allow using the tns_admin directory for different listeners + f77edcb0 Change 'alredy' to 'already' + b325f97e LVM-activate: add OCF_CHECK_LEVEL to control monitor action + 617adbf6 redis: validate_all: fixes file status tests + 47d75f8d rabbitmq-cluster: ensure we delete nodename if stop action fails + 5f0d15ad IPsrcaddr: remove hardcoded device when using destination parameter + 5ab3339e Remove standby.signal when promote with restart + 7afc581f IPsrcaddr: fixes to avoid failing during probe + a299281a LVM-activate: verify vg or lv validity + d763318c [podman] Simplify the code for checking if an image exists + a9fb8077 Filesystem: add trigger_udev_rules_if_need() for -U, -L, or /dev/xxx device + af39017b Filesystem: respect udevd need time to create UUID symlinks + 0eb144ac ldirectord: Support sched-flags + 92c49b6f IPaddr2: ipt_CLUSTERIP "iptables" extension not "nft" backend compatible + 0e73d3f4 IPsrcaddr: fixes to replace local rule if using local table, and set src back to primary for device on stop + caaeec0b iSCSI logical unit fix (#1435) + ce27a157 Clear out the $DIR_EXECUTABLE variable so we catch the... + a43075be High: pgsql: Support for PostgreSQL 12 + 34b46b17 IPaddr2: add noprefixroute parameter + 1da3 Filesystem: refresh UUID in the start phase + 80069756 azure-lb Set socat to default on SUSE distributions. + 9cea030b exportfs: allow multiple exports of same directory + 20ff678e Low: MailTo: fix variable expansion + d821ef33 iSCSILogicalUnit.in fixes (#1427) + 0f818916 Low: exportfs: Fix spelling error + c718050a Low: mysql-common: fix startup check + 03cc7bb5 aliyun-vpc-move-ip: add binary detection + 6341d71a Supports both 'go' and 'python' versions of Aliyun CLI + 6ee15eb2 Add missed requirement + 6eb86517 Use the function get_release_id to detect the OS. The parameter LOAD_STATUS_MODULE must be quoted. + + [Additional Information] + + Release Notes from an email to ClusterLabs HA mailing list: + + """ ClusterLabs is happy to announce resource-agents v4.5.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.5.0 The most significant enhancements in this release are: - bugfixes and enhancements: - - iSCSILogicalUnit: fix default value for OCF_RESKEY_liot_bstype - - aws-vpc-move-ip: add parameter for role to use to query/update route table - - Filesystem: add trigger_udev_rules_if_need() for -U, -L, or /dev/xxx device - - Filesystem: refresh UUID in the start phase - - IPaddr2: add noprefixroute parameter - - IPaddr2: add info to metadata that ipt_CLUSTERIP "iptables" extension is not "nft" backend compatible, and iptables-legacy support for distros that still support it - - IPsrcaddr: replace local rule if using local table, and set src back to primary for device on stop - - IPsrcaddr: fix failure during probe when using destination/table parameters - - LVM-activate: add OCF_CHECK_LEVEL 10 check that can be enabled to verify vg or lv validity with an additional "read 1 byte" test in special cases like iSCSI SAN - - MailTo: fix variable expansion - - SAPInstance: clear the $DIR_EXECUTABLE variable so we catch the situation when we lose the directory with binaries after first sapinstance_init invokation - - aliyun-vpc-move-ip: add support for both 'go' and 'python' versions of Aliyun CLI, and
[Bug 1627083] Re: ipt_CLUSTERIP is deprecated and it will removed soon, use xt_cluster instead
commit 92c49b6f2847546f3f938b10a2a97021774f0be3 Author: Jan Pokorný Date: Wed Dec 4 14:36:59 2019 +0100 IPaddr2: ipt_CLUSTERIP "iptables" extension not "nft" backend compatible Reference: https://lists.clusterlabs.org/pipermail/users/2019-December/026674.html (thread also sketches a future ambition for a [presumably, to revert the habit of a functional overloading] separate agent to use "xt_cluster" extension/cluster match). Signed-off-by: Jan Pokorný --- It is a well known upstream decision and it has been recently documented in v4.5.0 of "resource-agents". The following resource-agent description is about to get added to Focal when FFe: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383 is accepted and merge is finished. ** Also affects: resource-agents (Ubuntu) Importance: Undecided Status: New ** No longer affects: strongswan (Ubuntu) ** No longer affects: pacemaker (Ubuntu) ** Changed in: resource-agents (Ubuntu) Importance: Undecided => Wishlist ** Changed in: resource-agents (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1627083 Title: ipt_CLUSTERIP is deprecated and it will removed soon, use xt_cluster instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1627083/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1866383] Re: [focal] resource-agents need fixes from just released upstream version
** Changed in: resource-agents (Ubuntu Focal) Status: Confirmed => New ** Changed in: resource-agents (Ubuntu Focal) Importance: Wishlist => Undecided ** Changed in: resource-agents (Ubuntu Focal) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Summary changed: - [focal] resource-agents need fixes from just released upstream version + [FFe][Focal] resource-agents need fixes from recent release upstream version -- 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 need fixes from recent release upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1866383/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1490727] Re: "Invalid IPC credentials" after corosync, pacemaker service restarts
For pacemaker, this is a duplicate of:
https://bugs.launchpad.net/bugs/1439649
So, instead of marking it as duplicate, since it had charm work, I'm
removing pacemaker from the bug and leaving this comment:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/comments/20
"""
>From Corosync 2.4.1 Release Notes:
This release contains fix for one regression and few more smaller fixes.
"""
During 2.3.6 development the bug which is causing pacemaker to not work after
corosync configuration file is reloaded happened. Solution is ether to use this
fixed version (recommended) or as a quick workaround (for users who wants to
stay on 2.3.6 or 2.4.0) is to create file pacemaker (file name can be
arbitrary) in /etc/corosync/uidgid.d directory with following content (you can
also put same stanza into /etc/corosync/corosync.conf):
uidgid {
gid: haclient
}
"""
Anyone relying in Trusty or Xenial corosync:
corosync | 2.3.3-1ubuntu1 | trusty
corosync | 2.3.3-1ubuntu4 | trusty-updates
corosync | 2.3.5-3ubuntu1 | xenial
corosync | 2.3.5-3ubuntu2.3 | xenial-security
corosync | 2.3.5-3ubuntu2.3 | xenial-updates
should apply the mitigation above, like discovered previously by
commenters of this bug.
Note: Trusty is already EOS so I'm marking it as "won't fix".
Xenial should include the mitigation in a SRU.
"""
** No longer affects: pacemaker (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1490727
Title:
"Invalid IPC credentials" after corosync, pacemaker service restarts
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape/+bug/1490727/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
>From Corosync 2.4.1 Release Notes:
This release contains fix for one regression and few more smaller fixes.
"""
During 2.3.6 development the bug which is causing pacemaker to not work after
corosync configuration file is reloaded happened. Solution is ether to use this
fixed version (recommended) or as a quick workaround (for users who wants to
stay on 2.3.6 or 2.4.0) is to create file pacemaker (file name can be
arbitrary) in /etc/corosync/uidgid.d directory with following content (you can
also put same stanza into /etc/corosync/corosync.conf):
uidgid {
gid: haclient
}
"""
Anyone relying in Trusty or Xenial corosync:
corosync | 2.3.3-1ubuntu1 | trusty
corosync | 2.3.3-1ubuntu4 | trusty-updates
corosync | 2.3.5-3ubuntu1 | xenial
corosync | 2.3.5-3ubuntu2.3 | xenial-security
corosync | 2.3.5-3ubuntu2.3 | xenial-updates
should apply the mitigation above, like discovered previously by
commenters of this bug.
Note: Trusty is already EOS so I'm marking it as "won't fix".
Xenial should include the mitigation in a SRU.
** Changed in: pacemaker (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: pacemaker (Ubuntu Trusty)
Importance: Medium => Undecided
** Changed in: pacemaker (Ubuntu Xenial)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Title:
Pacemaker unable to communicate with corosync on restart under lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
** Also affects: pacemaker (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Fix Released ** Also affects: pacemaker (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Bionic) Status: New => Fix Released ** Changed in: pacemaker (Ubuntu Xenial) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu Trusty) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu Xenial) Importance: Undecided => High ** Changed in: pacemaker (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: pacemaker (Ubuntu Xenial) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1868882] Re: [SRU] Put ipmctl into Bionic (and update necessary deps)
Hello Jeff, I just synced with other engineers about this particular bug and it was brought to my attention that a MIR was attempted before and didn't pass (LP: #1854181). Unfortunately, for this case, a MIR is needed because the package is in [universe]. There is something else: $ rmadison ipmctl ipmctl | 02.00.00.3474+really01.00.00.3469-1 | eoan/universe | source, amd64 ipmctl | 02.00.00.3709+ds-1 | focal/universe | source, amd64 02.00.00.3709+ds-1 is not a final release. The best move here would be: 1) Future MIR for ipmctl package (20.10 ?), based on the feedback given: """ I'd ask you to revisit promoting it maybe in 20.10 or later. If then things turn out to be super stable and HW exists one could even later consider doing an major version SRU under the Banner of HW enablement. """ more -> https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1854181/comments/3 IF MIR passes (certainties will be reduced, but can't guarantee): 2) FFe exception to update Focal to latest released version. 4) SRU exception to update Eoan to Focal version. 3) SRU exception to make same version available to Bionic. So, for now, fastest thing to be done at your side would be to maintain a PPA enabling this HW. -- 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/1868882 Title: [SRU] Put ipmctl into Bionic (and update necessary deps) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1868882/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1870069] Re: pacemaker ftbfs in focal
*** This bug is a duplicate of bug 1869751 *** https://bugs.launchpad.net/bugs/1869751 ** This bug has been marked a duplicate of bug 1869751 [focal] pacemaker FTBFS because of deprecated ftime() -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1870069 Title: pacemaker ftbfs in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1870069/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
