-
Notifications
You must be signed in to change notification settings - Fork 93
Dev: migration: implement corosync.conf migration for corosync 3 (jsc#PED-8252) #1422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev: migration: implement corosync.conf migration for corosync 3 (jsc#PED-8252) #1422
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3c620cf
to
2d4c6db
Compare
fdcdc65
to
c6cd605
Compare
04ea10f
to
69020cc
Compare
69020cc
to
ab808d1
Compare
fa10732
to
68bd445
Compare
In
|
No output for remote nodes |
68bd445
to
389d007
Compare
FAIL as the fatal error sounds too strong to me. No matter it is corosync2 or corosync3 environment, nothing wrong to run |
486020b
to
16cd739
Compare
9e1b95b
to
38d9896
Compare
(cherry picked from commit 3264f0d)
(cherry picked from commit e656662)
…c#PED-11808) (cherry picked from commit 72cd46f)
(cherry picked from commit 54def35)
…jsc#PED-11808) (cherry picked from commit 7bf54e9)
(cherry picked from commit 84143c4)
…PED-11808) should use recursive queries (cherry picked from commit 4b7e42d)
…ilesystem_with_fstype (cherry picked from commit 48aca45)
(cherry picked from commit 1e48317)
(cherry picked from commit 97fa52b)
as it is not a hard requirement to upgrade pacemaker 2 to 3.
…ed with `--fix` (jsc#PED-8252)
…jsc#PED-8252) * should not run the migration if already migrated * should not tell users to run `crm cluster health sles16 --fix` if already migrated
so that we can report an error without blocking migration.
…PED-8252) No matter the cluster is running or not, there is nothing wrong to run the check or fix.
… some non-fatal problems which need manual fix (jsc#PED-8252) also refactor the return code of _check_impl()
…cluster (jsc#PED-8252) crmsh generates incorrect bindnetaddr when joining a corosync 2 multicast cluster. This should be fixed before used in nodelist.
…ide effects (jsc#PED-8252)
5328fc2
to
e73323d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work
Thanks!
This pull request implements migrating
corosync.conf
from corosync 2 to corosync 3, including:udpu
andudp
toknet
crypto_hash
is set tosha1
, which is the default value in corosync 2, upgrades it to the new default in corosync 3,sha256
.Use Cases
Check When All Green for Migration
Check When Already Migrated
Run Migration
Try to Run Migration When Already Migrated