-
Notifications
You must be signed in to change notification settings - Fork 92
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
[crmsh-4.6] Dev: pre-migration: implement pre-migration checks for SLES 16 (jsc#PED-11808) #1629
[crmsh-4.6] Dev: pre-migration: implement pre-migration checks for SLES 16 (jsc#PED-11808) #1629
Conversation
70f74a6
to
1a80eee
Compare
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. |
d9038c6
to
a2518dd
Compare
a740b3f
to
2bcad35
Compare
stonith:fence_vmware-rest | ||
stonith:fence_wti | ||
stonith:fence_xenapi | ||
stonith:fence_zvm |
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.
How has the above data been generated?
Can we automatically do that based on the locally installed resource-agents and fence-agents-* rpm?
Or, can we generate the data at the time crmsh using it (_load_supported_resource_agents)?
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.
How has the above data been generated?
Extracted the file list from resource-agents/fence-agents.
Can we automatically do that based on the locally installed resource-agents and fence-agents-* rpm?
No, because we need to know what is supported by SLES 16 instead of SLES 15 SP6.
2932b25
to
8cf8ef3
Compare
22ea8a0
to
a338bc6
Compare
Suggestion:1. Add completer for
|
Suggestion: 6. How about there are Failed Resource Actions?For some reason, some RA failed. For now, 7. crm report collect pre-migration infoI think we also need to collect the output of 8. Inaccurate usage?
Should be
The same for #1422 9. Fence agents checking
Better to add what's the alternative?
|
2dff378
to
d1563aa
Compare
d1563aa
to
d9c0449
Compare
Usages changed to
|
handler.handle_tip(f'Corosync transport "{transport}" will be deprecated in corosync 3.', [ | ||
'After migrating to SLES 16, run "crm cluster health sles16 --fix" to migrate it to transport "knet".', | ||
]) | ||
if corosync.get_value("totem.rrp_mode") in {'active', 'passive'}: |
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.
Although with low possibility, rrp_mode
can be set to none
for the one-ring
should include none
value here
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.
none
means SRP, which is supported and does not needs any actions.
…PED-11808) should use recursive queries
…ilesystem_with_fstype
d9c0449
to
94926c5
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.
Looks good to me, great work!
Thanks!
8fc0558
to
b51ec24
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, some feedback,
-
Reporting the CIB related check results in "localhost" section is misleading, since they are concepts at the cluster level when the cluster is running.
-
How to interpret the cluster is down? Since in such case, the CIB check is kind of local. Hence, the related open question is should CIB check run in the remote node?
-
"Good to migrate to SLES 16." on ha-1-2 is not right, while CIB check is "FAIL" at the cluster level in the summary section.
-
Sounds the following information is duplicate in my view
------ localhost ------
...
[FAIL] Please fix all the "FAIL" problems above before migrating to SLES 16.
****** summary ******
[FAIL] Please fix all the "FAIL" problems above before migrating to SLES 16.
b51ec24
to
abe07c3
Compare
abe07c3
to
7670957
Compare
Wonderful, thanks for the great work! |
97fa52b
into
ClusterLabs:4.6-pre-migration-staging
This pull request implements pre-migration checks for SLES 16. These checks are expected to run before migrating to SLES 16.
These checks ensure all the cluster nodes runs the latest version of corosync 2.x and pacemaker 2.1.x, and report used resource agents and fence agents that will be removed in SLES 16. It also provides advice for further actions need to take after migration.
Use Cases
crm cluster health sles16
crm cluster health sles16 --fix
When some of the nodes are offline