On BDA 5.1 and Lower Mammoth Actions like Decommission/Reprovision Fail with "Could not parse for environment production: Permission denied - /opt/oracle/BDAMAammoth/puppet/manifest/<filename>.pp"
(Doc ID 2847299.1)
Last updated on APRIL 17, 2023
Applies to:
Big Data Appliance Integrated Software - Version 4.13.0 to 5.1.0 [Release 4.10 to 5.0]Linux x86-64
Symptoms
NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.
Mammoth actions like node decommisssion /node reprovision, etc. fail with errors like:
Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Permission denied - /opt/oracle/BDAMAammoth/puppet/manifest/site.pp at /opt/oracle/BDAMAammoth/puppet/manifest/site.pp on node <MAMMOTH_HOSTNAME>
Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Permission denied - /opt/oracle/BDAMAammoth/puppet/manifest/environment.pp at /opt/oracle/BDAMAammoth/puppet/manifest/environment.pp on node <MAMMOTH_HOSTNAME>
Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Permission denied - /opt/oracle/BDAMAammoth/puppet/manifest/password.pp at /opt/oracle/BDAMAammoth/puppet/manifest/password.pp on node <MAMMOTH_HOSTNAME>
The same errors will be present in /var/log/messages on the mammoth node.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |