Hi Felipe,
Now this has migrated to kinetic, are you still willing to propose the
SRU for this one? I'd be more than happy to sponsor it :)
You'd need to provide the debdiff (or a merge proposal for the git
ubuntu repository) and fill in the SRU template in this bug (see
This bug was fixed in the package crmsh - 4.4.0-1ubuntu1
---
crmsh (4.4.0-1ubuntu1) kinetic; urgency=medium
* Merge with Debian unstable (LP: #1971271, #1972730). Remaining changes:
- d/t/pacemaker-node-status.sh: Get the node name with "crm_node -n"
instead of using
** Changed in: crmsh (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972730
Title:
WARNING: crmadmin -S unexpected output
To manage notifications
** Changed in: crmsh (Ubuntu Jammy)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972730
Title:
WARNING: crmadmin -S unexpected output
** Changed in: crmsh (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972730
Title:
WARNING: crmadmin -S unexpected output
To
@Felipe sponsoring is certainly something we can do, however before
proceeding with the SRU we need to fix the bug in the current Ubuntu
devel release (kinetic). Ideally this should happen with Debian
packaging 4.4.0 and Ubuntu syncing it, as Lucas mentioned. Filing a bug
in Debian may help. If
On Wed, 2022-05-11 at 19:13 +, Lucas Kanashiro wrote:
> Thanks for working with upstream to fix this. Would you be willing to
> backport this fix to Jammy? Or do you prefer me to do it?
I can propose the SRU (via debdiff) if you can sponsor it :-)
>
> For Kinetic we will be moving to the
Thanks for working with upstream to fix this. Would you be willing to
backport this fix to Jammy? Or do you prefer me to do it?
For Kinetic we will be moving to the newer version (4.4.0 as upstream
suggested) so this will not be an issue. I am going to talk to the
Debian maintainer to see if we
ppa with the fix proposed at
https://github.com/ClusterLabs/crmsh/pull/972 for testing purposes
available at https://launchpad.net/~freyes/+archive/ubuntu/lp1972730
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of
The way this error is exposed in the hacluster is when running the
`stop` hook:
unit-hacluster-1: 16:53:41 DEBUG juju.worker.uniter.runner starting jujuc
server {unix @/var/lib/juju/agents/unit-hacluster-1/agent.socket }
unit-hacluster-1: 16:53:41 INFO unit.hacluster/1.juju-log Setting node
10 matches
Mail list logo
