RunnerStatusLocallyWorkingButNotFromWorkflow

[skc949-user]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

logs_69845468666.zip

it worked in local you can see below :

and even i granted following permissions : still failing the workflow

and i saw fetch runner task in the below workflow appears to be correct and it is passed you can verify the logs: output:

why from workflow it is not giving accurate answer: here is the yaml file 👍

`name: GitHub Self-Hosted Runner Monitor

on:
workflow_dispatch:

permissions:
contents: read

jobs:
runner-check:
runs-on: [self-hosted, Linux, X64]
steps:
- name: Checkout repo
uses: actions/checkout@v4

  - name: Install dependencies (gh + jq)
    run: |
      sudo apt-get update
      sudo apt-get install -y gh jq



  - name: Fetch runner status (CSV)
    env:
      GH_TOKEN:  ${{ secrets.ORG_RUNNER_TOKEN }}
    run: |
      OWNER="skc949"
      CSV="github_runners.csv"
     
      echo "Repository,RunnerName,OS,Status,Busy" > $CSV

      # Get repositories
      REPOS=$(gh repo list $OWNER --limit 100 --json nameWithOwner --jq '.[].nameWithOwner')

      for REPO in $REPOS; do
        echo "Checking $REPO"

        RESPONSE=$(gh api -H "Accept: application/vnd.github+json" "/repos/$REPO/actions/runners")

        echo "$RESPONSE" | jq -r '
          .runners[]? |
          "\("'"$REPO"'"),\(.name),\(.os),\(.status),\(.busy)"' >> $CSV
      done

  - name: Send email (Gmail)
    if: always()
    uses: dawidd6/action-send-mail@v3
    with:
      server_address: smtp.gmail.com
      server_port: 465
      secure: true
      username: ${{ secrets.GMAIL_USERNAME }}
      password: ${{ secrets.GMAIL_APP_PASSWORD }}
      subject: GitHub Runner Status Report
      to: shyam9270@gmail.com
      from: GitHub Runner Monitor
      body: |
        Please find attached GitHub self-hosted runner status report.
      attachments: github_runners.csv`

Please suggest

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐