Mammoth Upgrade to 5.1 or Mammoth 5.1 Install Fails at "Bigdatasql::Manage_bds/Exec[install_bds]" with "No module named cryptography"
(Doc ID 2642664.1)
Last updated on FEBRUARY 28, 2020
Applies to:Oracle Big Data SQL - Version 3.0 and later
Big Data Appliance Integrated Software - Version 4.10.0 to 4.12.0 [Release 4.10]
Mammoth upgrade to 5.1 or Mammoth 5.1 install fails at "Bigdatasql::Manage_bds/Exec[install_bds]" with "No module named cryptography".
The Mammoth failure looks like:
change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/install_bds.sh &>
/opt/oracle/BDAMammoth/bdaconfig/tmp/install_bds_<EPOCH_TIMESTAMP>.out returned 1 instead of one of 
1. /opt/oracle/BDAMammoth/bdaconfig/tmp/install_bds_<EPOCH_TIMESTAMP>.out shows:
Copying BDS bundle from mammoth node to CM node...
Unzipping bds bundle...
Running BDSJaguar-4.0.0.run file...
Replacing oracle-hadoop-sql.jar file...
Copying bds config file...
Copying oracle.keytab and hdfs.keytab...
### install BDS ###
No module named cryptography. Please install the module, or upgrade Python to 2.7 or higher, and try again.
Error during the execution of the install workflow.
2. Checking the python2-cryptography rpm shows that it is not installed:
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