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

Fix self hosted runner Action field behavior change #2881

Merged
merged 1 commit into from
Jan 20, 2022

Conversation

davidvonthenen
Copy link
Contributor

@davidvonthenen davidvonthenen commented Jan 20, 2022

What this PR does / why we need it

There were two issues:

Additional changes:

  • Added some debugging for tracing
  • Put GitHub and EC2 clients into respective structs
  • Added an "all else fails" clean up thread that checks for github clients that are idle and attempts to clean them up

Details for the Release Notes (PLEASE PROVIDE)

Fix self hosted runner Action field behavior change

Which issue(s) this PR fixes

Fixes: #2870

Describe testing done for PR

It's currently running on the webhook instances and fielding jobs

Special notes for your reviewer

NA

@davidvonthenen davidvonthenen requested a review from a team January 20, 2022 02:36
@github-actions github-actions bot added the owner/release-eng Work executed by VMware release engineering team label Jan 20, 2022
@davidvonthenen davidvonthenen force-pushed the fix/selfhostedrunner branch 4 times, most recently from ac80644 to be711cc Compare January 20, 2022 04:57
@davidvonthenen davidvonthenen marked this pull request as ready for review January 20, 2022 05:08
@davidvonthenen
Copy link
Contributor Author

This is ready for review!

@karuppiah7890
Copy link
Contributor

hey @dvonthenen 👋 I wanted to check how you debugged this issue, so that I could learn too. How did you get the logs of the TCE webhook service running in AWS? I noticed the 3 AWS EC2 instances named TCE Webhook, and I'm assuming those were running the service. I couldn't find any logs in CloudWatch. Did you SSH into the machine and check the logs? I think I can't SSH into it unless my public key is added to the ~/.ssh/authorized_keys file. I was wondering if we can use CloudWatch or something similar or if I can get SSH access to the machines so that I can help debug too 😄

Let me know what you think :)

@davidvonthenen
Copy link
Contributor Author

Yea, I just ssh'ed in. We can talk offline and add your keys to those instances.

@davidvonthenen davidvonthenen marked this pull request as draft January 20, 2022 16:08
@davidvonthenen davidvonthenen force-pushed the fix/selfhostedrunner branch 2 times, most recently from 1e984ca to c628e2e Compare January 20, 2022 17:27
@davidvonthenen davidvonthenen marked this pull request as ready for review January 20, 2022 17:28
stmcginnis
stmcginnis previously approved these changes Jan 20, 2022
Copy link
Contributor

@stmcginnis stmcginnis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me, and we can always follow up on anything else.

@nrb nrb merged commit 7db20fd into vmware-tanzu:main Jan 20, 2022
@davidvonthenen davidvonthenen deleted the fix/selfhostedrunner branch February 7, 2022 16:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-not-required owner/release-eng Work executed by VMware release engineering team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Self hosted AWS runners not being available in some GitHub Actions workflows
5 participants