Skip to content

Conversation

markgoddard
Copy link
Contributor

While not pretty, this workaround avoids manual intervention after the
runner is power cycled.

@markgoddard markgoddard requested a review from a team as a code owner January 19, 2023 09:20
@markgoddard markgoddard self-assigned this Jan 19, 2023
@priteau
Copy link
Member

priteau commented Jan 19, 2023

Could this ever cause the runner to lose its DHCP lease?

@markgoddard markgoddard force-pushed the wallaby-builder-workaround branch from b350128 to 60a461a Compare January 19, 2023 09:53
@markgoddard
Copy link
Contributor Author

Could this ever cause the runner to lose its DHCP lease?

Good question. Needs some testing.

While not pretty, this workaround avoids manual intervention after the
runner is power cycled.

Co-Authored-By: Pierre Riteau <pierre@stackhpc.com>
@markgoddard markgoddard force-pushed the wallaby-builder-workaround branch from 60a461a to 08920c5 Compare January 19, 2023 12:10
@markgoddard markgoddard merged commit 251b4c5 into stackhpc/wallaby Jan 19, 2023
@markgoddard markgoddard deleted the wallaby-builder-workaround branch January 19, 2023 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants