Add Oracle HTTP Server support for RHEL 9 #124
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
added 3 commits
February 27, 2025 10:51
With RHEL 9 being supported in 8.2.0.0 - we need to ensure that it can deploy correctly.
An initial test on a RHEL9 VM failed due to
`TASK [merative.spm_middleware.weblogic : Include based on OS version variables] ***
fatal: [mfwlsorarhel9]: FAILED! => {"ansible_facts": {}, "ansible_included_var_files": [], "changed": false, "message": "Could not find or access 'os_9.yml'\nSearched in:\n\t/home/jenkins/remoting/workspace/DevOps-Jenkins-ProvisionerWrapper/playbooks/install_middleware/ansible_collections/merative/spm_middleware/roles/weblogic/vars/os_9.yml\n\t/home/jenkins/remoting/workspace/DevOps-Jenkins-ProvisionerWrapper/playbooks/install_middleware/ansible_collections/merative/spm_middleware/roles/weblogic/os_9.yml\n\t/home/jenkins/remoting/workspace/DevOps-Jenkins-ProvisionerWrapper/playbooks/install_middleware/ansible_collections/merative/spm_middleware/roles/weblogic/tasks/vars/os_9.yml\n\t/home/jenkins/remoting/workspace/DevOps-Jenkins-ProvisionerWrapper/playbooks/install_middleware/ansible_collections/merative/spm_middleware/roles/weblogic/tasks/os_9.yml\n\t/home/jenkins/remoting/workspace/DevOps-Jenkins-ProvisionerWrapper/ansible/playbooks/install_middleware/vars/os_9.yml\n\t/home/jenkins/remoting/workspace/DevOps-Jenkins-ProvisionerWrapper/ansible/playbooks/install_middleware/os_9.yml on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}`
This PR covers updates required to support this.
os_9 vars file for WLS
new Molecule test for WLS on Rocky9
new Github workflow for this test
With RHEL 9 being supported in 8.2.0.0 - we need to ensure that it can deploy correctly. An initial test on a RHEL9 VM with Oracle HTTP Server failed due to the below issues. MIssing SymLink to required lib Cert creation issues on RHEL 9
salob
approved these changes
Feb 27, 2025
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.
With RHEL 9 being supported in 8.2.0.0 - we need to ensure that it can deploy correctly.
An initial test on a RHEL9 VM with Oracle HTTP Server failed due to the below issues.
MIssing SymLink to required lib
The OHS install fails patching the system with the following error
cannot find /usr/lib64/libpthread_nonshared.aFrom research - there seems to be a requirement to create a symlink for this package when installing OHS on RHEL
Oracle Fusion Middleware 12.2.1.4.0 Support with OL/RHEL9
The suggestion in this doc is
Non-java installTypes (OBIEE, Oracle Forms and Reports, Oracle HTTP Server, Oracle Internet Directory, Oracle Traffic Director, Oracle WebLogic Proxy Plugin) complete following steps:a. As root user create symbolic link for libpthread_nonshared.acd /usr/lib64ln -s libc_nonshared.a libpthread_nonshared.ab. Press "Skip" button to continue to next pageCert creation issues on RHEL 9
Once the symlink was fixed there was a further issue creating and importing the backend and frontend p12 cert to the Oracle HTTP Server..
The error thrown is:
oracle.security.crypto.core.CipherException:oracle.security.crypto.core.InvalidKeyException:oracle.security.crypto.core.AlgorithmIdentifierException:No class found for OBJECT IDENTIFIER {1 2 840 113549 2 9}This Oracle Doc related to Oracle HTTP Server seems to have the same error.. The suggestion was to add the following to the keytool command -
Add parameter " -J-Dkeystore.pkcs12.legacy" to keytool command.However we don't use keytool, we have Oracle
orapkiSo further research suggested the issue might be creating the cert with openssl - so i added a -legacy flag to the openssl command.
This seem to work, in that the cert was imported, and the rest of the install completed successfully
Now i need to see if this impacts a deployed application on a VM