Environment:
This issue affects all released versions of Yugabyte.
Issue:
When running the manual provisioning script while deploying a new universe, it throws below error
Script:
$ sudo /opt/yugabyte/yugaware/data/provision/eb9e484a-10f4-403a-9c42-150d33134a65/provision_instance.debug.py --ip ${ip} --mount_points /vol_01/apps_data_01/yb_data --ask_password
Error:
execute_command(['/opt/yugabyte/devops/bin/ybcloud.sh', 'onprem', 'access', 'edit-vault', '--private_key_file', '/opt/yugabyte/yugaware/data/keys/eb9e484a-10f4-403a-9c42-150d33134a65/dev-cloud-key.pem', '--has_sudo_pass'])
Traceback (most recent call last):
File "/opt/yugabyte/yugaware/data/provision/eb9e484a-10f4-403a-9c42-150d33134a65/provision_instance.debug.py", line 84, in <module>
execute_command(construct_vault_command(args), password=password)
File "/opt/yugabyte/yugaware/data/provision/eb9e484a-10f4-403a-9c42-150d33134a65/provision_instance.debug.py", line 60, in execute_command
p = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE, env=new_env)
File "/usr/lib64/python2.7/subprocess.py", line 711, in init
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Resolution:
The above error can be solved if we execute the script from the Yugaware container instead of the Yugaware host.
Please use the below command to login into the yugaware container from the yugaware platform host:
sudo docker exec -it yugaware
Note- In the platform UI, it does not mention that script should run in a container instead of host.
Doc link: https://docs.yugabyte.com/latest/yugabyte-platform/configure-yugabyte-platform/set-up-cloud-provider/on-premises/#running-the-pre-provisioning-script
Comments
0 comments
Please sign in to leave a comment.