Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

"Python: Command Not Found" in Ubuntu 20.04LTS During Node Preparation #363

Open
emattiza opened this issue Mar 30, 2021 · 5 comments
Open

Comments

@emattiza
Copy link

Problem Description

When initiating a pool with shipyard pool add, using the microsoft-azure-batch publisher 20-04-lts ubuntu image, the python executable is not available in the newly created node's $PATH per Ubuntu's new policy of handling the system python executable name and the 2-to-3 migration. Because nodeprep.sh references "python" as the executable name in a couple spots, the executable fails to be found, and the node preparation start task fails.

Batch Shipyard Version

shipyard, version 3.9.1

Steps to Reproduce

generate a pool with an ubuntu-server-container, microsoft-azure-batch, 20-04-lts image
(shipyard pool add with a simple pool config for a single dedicated node)

Expected Results

Successful pool deploy

Actual Results

stderr.txt contains python:command not found (nodeprep.sh:385)

Redacted Configuration

pool.yaml

pool_specification:
  id: mypool
  vm_configuration:
    platform_image:
      offer: ubuntu-server-container
      publisher: microsoft-azure-batch
      sku: 20-04-lts
  vm_count:
    dedicated: 1
    low_priority: 0
  vm_size: STANDARD_A1_V2

Additional Logs

python:command not found (nodeprep.sh:385)

Additional Comments

This can be worked around by specifying a system python symlink in the additional_node_prep > pre commands. Happy to submit a pull request with changes to nodeprep.sh that test and direct to the appropriate python executable name to run so that the additional_node_prep pre-commands are no longer needed. I can always, of course, just pick a different image as well!

@alfpark
Copy link
Collaborator

alfpark commented Apr 21, 2021

Thanks for opening this issue. 20.04 isn't supported yet, but will be in the next version.

alfpark added a commit that referenced this issue Oct 4, 2021
- Resolves #363
- Add CentOS 7.8 support
- Remove CentOS 8 support
- Add Datacenter-Core-20H2
- Unblock -gs, -g2, -gensecond support
- Update Nvidia Tesla driver to 470.57.02 and CUDA 11.4
- Update Nvidia Grid driver to 470.63.01 and CUDA 11.4
- Update LIS driver to 3.4.5
@coolstate
Copy link

@emattiza @alfpark
I got this issue too.
so we can not use ubuntu20.04 published by microsoft-azure-batch with batch shipyard currently, correct?
since only ubuntu20.04 of microsoft-azure-batch in azure batch, but not supported by batch shipyard, so maybe we have to change to use other linux os images such as centos7.

@emattiza
have you resolved you issue yet? how did you resolve it?

@emattiza
Copy link
Author

emattiza commented Feb 4, 2022

@coolstate I just used an older Ubuntu image. We now use a different azure service for our needs after a refactor. Good luck!

@coolstate
Copy link

@emattiza Thank you for you reply.

@alfpark

Thanks for opening this issue. 20.04 isn't supported yet, but will be in the next version.

Do you have any release schedule for the next version?

@ecocarlisle
Copy link

ecocarlisle commented Aug 20, 2022

If you enable unverified versions you can select the dvsm from Windows which is referenced in the Microsoft tutorials and the commands will work on startup.

alfpark added a commit that referenced this issue Mar 20, 2023
- Resolves #363
- Add CentOS 7.8 support
- Remove CentOS 8 support
- Add Datacenter-Core-20H2
- Unblock -gs, -g2, -gensecond support
- Update Nvidia Tesla driver to 470.57.02 and CUDA 11.4
- Update Nvidia Grid driver to 470.63.01 and CUDA 11.4
- Update LIS driver to 3.4.5
alfpark added a commit that referenced this issue Mar 20, 2023
- Resolves #363
- Add CentOS 7.8 support
- Remove CentOS 8 support
- Add Datacenter-Core-20H2
- Unblock -gs, -g2, -gensecond support
- Update Nvidia Tesla driver to 470.57.02 and CUDA 11.4
- Update Nvidia Grid driver to 470.63.01 and CUDA 11.4
- Update LIS driver to 3.4.5
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants