E-CLOUD: Cloning Imported ADB-Shared Environment Fails When Provisioning Mid-Tier with Error - Can not determine the gem executable path without puppet location known.
(Doc ID 3021629.1)
Last updated on MAY 09, 2024
Applies to:
PeopleSoft Cloud Manager - Version 17 and laterInformation in this document applies to any platform.
Symptoms
Cloning ADB-Shared (Autonomous Database) environment that was previously imported to PeopleSoft Cloud Manager (CM) fails when provisioning mid-tier nodes.
The mid-tier node's /home/opc/log/1709655297646726900/psft_activity_middletier_oci_clone_2_20240305_164745/remote_out.log contains the following error:
2024-03-05 16:48:24,847 ERROR psc_linux_data.py 142 Can not determine the gem executable path without puppet location known.
NoneType: None
2024-03-05 16:48:24,847 ERROR psc_activity.py 123 Got exception while executing the Activity. ex:Can not determine the gem executable path without puppet location known.
Traceback (most recent call last):
File "/home/opc/cloud/psc_cloud/psc_activity/psc_activity.py", line 119, in execute
exit_code = self.execute_activities()
File "/home/opc/cloud/psc_cloud/psc_activity/psc_midtier_oci_clone.py", line 274, in execute_activities
psft_instance_data = self.get_psft_utils().encrypt_user_passwords(psft_instance_data, psft_platform_data)
File "/home/opc/cloud/psc_cloud/psc_utils/psc_utils.py", line 1122, in encrypt_user_passwords
eyaml_executable = platform_info.get_eyaml_executable()
File "/home/opc/cloud/psc_cloud/psc_data/psc_linux_data.py", line 109, in get_eyaml_executable
self.gem_executable = self.get_gem_executable()
File "/home/opc/cloud/psc_cloud/psc_data/psc_linux_data.py", line 143, in get_gem_executable
raise PsftDataException('Can not determine the gem executable path without puppet location known.')
psc_cloud.psc_utils.psc_exception.PsftDataException: Can not determine the gem executable path without puppet location known.
The issue can be reproduced at will with the following steps:
1. Import an environment in Cloud Manager by going to Environments tile and clicking on the Import Environment button.
2. Perform a clone by clicking on Environments tile > Related Actions button corresponding to the environment to be cloned and selecting Clone Environment. Observe it fail on mid-tier provisioning.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |