** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the hostname as the node name instead of hardcoded 'node1'
To manage notifications about this
I did some tests, to see what the cluster behavior is when changing node name
and/or id. It all boils down to the fact that whatever is being changed, one
has to be aware that the change is being done to a live real cluster, even
though it's a simple one-node cluster. That's what you get right
> However, hacluster charm should be handling this situation. There's nothing
> special here -
> corosync has specific behaviour out of the box. Charms should handle it.
I'm trying to understand the sequence of steps that led to this situation on
Focal. From what I understand:
- install
Reviewed: https://review.opendev.org/c/openstack/charm-hacluster/+/841587
Committed:
https://opendev.org/openstack/charm-hacluster/commit/567e54d87c55f945f222a9ebbe2e9bfc1984ce5e
Submitter: "Zuul (22348)"
Branch:stable/focal
commit 567e54d87c55f945f222a9ebbe2e9bfc1984ce5e
Author: Billy
** Changed in: charm-hacluster
Status: Fix Committed => 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/1874719
Title:
[SRU] Use the hostname as the node name instead of
Thanks for taking a look at this proposed change Robie. The behavior we
are trying to backport to Focal is already present in all supported
releases, Focal is the only one that differs at the moment.
What you said is indeed true, the default configuration file is not
production ready to most of
> I'm not sure how to do that in packaging except to try to guide the
user into somehow not following the broken installation flow.
Maybe, *if* it's never useful to use corosync with the default shipped
corosync.conf, we should just not ship it, and add a
James said:
> Setting the pacemaker distro task back to new - it seems very odd that
a system designed to manage a cluster of servers would install on every
node with a non-unique node id, which is a change in behaviour from
older versions of the same software.
In Jammy, I think this is still
** Changed in: charm-hacluster
Milestone: None => 22.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the hostname as the node name instead of hardcoded 'node1'
To
Backporting the default config change to Focal breaks pacemaker DEP-8
test. The fix for this can be tracked here:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1968039
I created a separate bug to block this update in focal-proposed and
avoid users updating the package because of a
** Description changed:
[Impact]
Users upgrading from Bionic to Focal are getting a different default
- node name, previously it was the hostname and now it is using a
- hardcoded "node1". This issue was already fixed on Impish onward, so now
- only Focal is using the hardcoded "node1"
** Changed in: corosync (Ubuntu Focal)
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/1874719
Title:
[SRU] Use the hostname as the node name instead of
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/418567
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use
** Description changed:
+ [Impact]
+
+ Users upgrading from Bionic to Focal are getting a different default
+ node name, previously it was the hostname and now it is using a
+ hardcoded "node1". This issue was already fixed on Impish onward, so now
+ only Focal is using the hardcoded "node1"
** Changed in: corosync (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the hostname as the node name instead of hardcoded
Reviewed: https://review.opendev.org/c/openstack/charm-hacluster/+/834034
Committed:
https://opendev.org/openstack/charm-hacluster/commit/d1191dbcabdfd8684a86825f06c6ede266ba93ba
Submitter: "Zuul (22348)"
Branch:master
commit d1191dbcabdfd8684a86825f06c6ede266ba93ba
Author: Billy Olsen
Since this is already in Jammy, I am adding the backport of this fix to
Focal to the Server team backlog and it should be tackled "soon". Also
setting the Groovy task to Won't Fix because of the end of its standard
support.
** Tags added: server-todo
** Changed in: corosync (Ubuntu Groovy)
Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-hacluster/+/834034
** Changed in: charm-hacluster
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In the meantime, we keep having to add a post-deployment cleanup step to
our deployment guides:
Delete node1 crm resources (LP#1874719):
$ juju run -m openstack --all -- sudo crm node delete node1
Which is overkill but works.
--
You received this bug notification because you are a member
Both DD's and Lucas' PoV has merits, imho. There's no right and wrong
here. I would even prefer if we reduce the delta with Debian.
However, hacluster charm should be handling this situation. There's
nothing special here - corosync has specific behaviour out of the box.
Charms should handle it.
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: corosync (Ubuntu Hirsute)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You are right, I did not backport the fix to the older LTS releases yet,
it is still in my todo list. I was trying to convince the Debian
maintainer to accept the change but he refused to do that. I was not
willing to carry this as a delta and force us to do merges from now on,
I'd prefer to keep
Just to clarify, this is fixed in impish but is still a problem on older
releases. Is that correct?
And since the problem is fixed/fixable in corosync, this bug is probably
invalid for charm-hacluster, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/corosync/+git/corosync/+merge/414116
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/corosync/+git/corosync/+merge/414030
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/406171
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use
This bug was fixed in the package corosync - 3.1.0-2ubuntu4
---
corosync (3.1.0-2ubuntu4) impish; urgency=medium
* d/p/Make-the-example-config-valid.patch: comment out the node name in
config file (LP: #1874719). With this, we will keep the same behavior as we
have in
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/corosync/+git/corosync/+merge/404328
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use
28 matches
Mail list logo
