Allow brute-cleanup to work with RAC #67
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remount /dev/shm if necessary
brute-cleanup was originally designed for single-node, Oracle Restart installs; on RAC clusters I ran into a few issues and making a few fixes: - Making existing service shutdown and CRS deconfigure run only on non-RAC clusters (detected by the presence or ansence of a cluster_name in the inventory file) - Adding a somewhat hacky RAC hard shutdown using the OHASD shutdown handler, plus rootcrs.sh. Why not use Oracle's deinstall? I'd prefer not to depend on a response file taht may or may not reflect current reality, but rather do as generic a deconfigure/shutdown as possible - Adding tfa (trace file anaalyzer) to the kill list, as well as removing the initscript itself - I ran into a case where umount failed on /u01 but lsof showed nothing in use. a lazy (umount -l) seems to resolve by simply detaching the mount, and seems to fit the context of a "brute cleanup", especially since we're going to zero out the device later anyway. Ansible's mount handler doens't support the option, so we're reverting to shell here, with the unfortuantely side effect that nonexistant mounts will generated ignored error messages.
A few more objects that can be left behind if CRS deconfig scripts fail for some reason: shared memory segments, semaphors, and kernel modules (ACFS, ASMFD, etc). In the spirit of a brute cleanup, let's yank stragglers the hard way.
Forcibly unloading oracleasm will impact the ability to identify ASM devices, so delay kernel module removal until disks and asmlib are already removed.
Using pkill instead of a pipeline to avoid error messages when these processes don't exist. And thus avoid the need for complicated return code processing.
|
Tested the The run is documented in this gpaste (internal): This LGTM from a non-rac standpoint. |
|
Able to test run this multiple times successfully for a single-node RAC cleanup. |
jcnars
approved these changes
Apr 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
brute-cleanup was originally designed for single-node, Oracle Restart installs; on RAC clusters I ran into a few issues and making a few fixes: