Skip to content

Tart execution reports no IP available #30

Closed
@jlarmstrong

Description

@jlarmstrong

I am seeing both with local already existing images and with images pulling from github that the gitlab-tart-executor is not seeing the VM startup within the timeout. Is there any additional logging that is not documented that can help troubleshoot this behavior currently? The gitlab tart custom executor is running on an AWS instance with an EBS volume. Manually testing the clone/startup/ip resolution time appears that I'm not seeing an IP resolve for 54 seconds consistently.

Using an image that already has been pulled:

Using Custom executor...
82023/07/07 12:50:48 Cloning and configuring a new VM...
92023/07/07 12:50:48 Waiting for the VM to boot and be SSH-able...
102023/07/07 12:51:49 tart command returned non-zero exit code: "no IP address found, is your VM running?"

Using the cirruslabs image:

Using Custom executor...
82023/07/07 12:49:27 Pulling the latest version of ghcr.io/cirruslabs/macos-ventura-xcode:14.3.1...
92023/07/07 12:49:27 Cloning and configuring a new VM...
102023/07/07 12:49:27 Waiting for the VM to boot and be SSH-able...
112023/07/07 12:50:28 tart command returned non-zero exit code: "no IP address found, is your VM running?"

Secondarily the tart pull step is not always showing the image within the tart list oci entries after we prune the system of previous images and try the process again.

Versions:
Tart: 1.8.0
Gitlab executor: 15.8.2
Gitlab Tart Executor: 1.4.0

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions