Skip to content

Cannot start harbor: pre-start script fails due to lack of python intepreter (Xenial & Jammy) #149

@dennisjbell

Description

@dennisjbell

Describe the bug

Tried to deploy as described in the manifest directory examples. First tried on ubuntu-jammy, but when that failed, tried again on ubuntu-xenial, which is used in the example manifest.

bosh deployment output:

Task 345 | 23:52:06 | L executing pre-start: harbor-app/f74876ed-744e-4c39-ad43-d58b810133af (0) (canary) (00:03:02)
                    L Error: Action Failed get_task: Task bf645736-e545-4a77-772f-e5e2ca8c636b result: 1 of 4 pre-start scripts failed. Failed Jobs: harbor. Successful Jobs: enable-bosh-dns, bosh-dns, user_add.

Content of pre-start script for harbor job:

/var/vcap/jobs/harbor/bin/pre-start: /var/vcap/packages/harbor-app/prepare: /usr/bin/python: bad interpreter: No such file or directory

There iis no /usr/bin/python on ubuntu-xenial stemcell, nor is there python in the path at all. There is /usr/bin/python3

Reproduction steps

  1. Deploy as described in the manifests examples
  2. Note failure

Expected behavior

Harbor job should start, and python should be present, or python3 should be used.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions