Skip to content

[operations] docs: add runbook for expired gh-aw stop-time gate detection - #6771

Open
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
operations/scheduled-workflow-stop-time-6769
Open

[operations] docs: add runbook for expired gh-aw stop-time gate detection#6771
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
operations/scheduled-workflow-stop-time-6769

Conversation

@kubestellar-hive

Copy link
Copy Markdown
Contributor

Summary

Adds runbooks/scheduled-workflow-stop-time.md, documenting a gap confirmed in #6769: devstats.lock.yml and daily-team-status.lock.yml (gh-aw generated) embed a hard-coded GH_AW_STOP_TIME that expired ~8 months ago, silently disabling every scheduled run since (grey skipped, not a red ❌ failure), with zero alerting.

Why doc-only

The real fix is recompiling the two .lock.yml files from their .md sources with an extended/removed stop-after, which requires gh-aw tooling and a maintainer with workflows permission — agent tokens cannot write files under .github/workflows/*. This PR adds the manual-detection and recovery guidance in the meantime, following the same pattern as runbooks/stale-workflow-monitoring.md and runbooks/scorecard-monitoring.md.

Changes

  • runbooks/scheduled-workflow-stop-time.md (new): scope, known gap, manual detection steps, recovery.
  • README.md: link the new runbook from the Operational Readiness index.

Fixes #6769

— filed under operations policy (ACMM L6, ISSUES_AND_PRS mode).

— hive: agent=operations backend=copilot model=claude-sonnet-4-6

devstats.lock.yml and daily-team-status.lock.yml have hard-coded
GH_AW_STOP_TIME gates that expired ~8 months ago, silently skipping
every scheduled run since with no failure alert (grey skipped runs,
not red X). Agent tokens lack the workflows permission needed to
recompile the affected .lock.yml files, so this documents manual
detection and the maintainer-side recovery path.

Fixes #6769

Signed-off-by: Copilot <copilot@github.com>
@kubestellar-hive

Copy link
Copy Markdown
Contributor Author

Important

Held for human sign-off on the direction, not on the code.

This PR's only tracked rationale is #6769, which the hive filed itself — issue #6769 was filed by kubestellar-hive[bot] and no human has acknowledged it. An agent-filed issue does not, on its own, establish that anyone agreed to the direction (hivecommons/hive#5117).

The change may well be right; nothing here is a review of it. To release the hold, acknowledge the direction on that issue — comment on it, assign yourself, or add the approved-direction label — and remove the hold label here.

@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Sep 6, 2026
@kubestellar-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@netlify

netlify Bot commented Sep 6, 2026

Copy link
Copy Markdown

Deploy Preview for kubestellar-docs ready!

Name Link
🔨 Latest commit 588fd94
🔍 Latest deploy log https://app.netlify.com/projects/kubestellar-docs/deploys/6a9de160d5c02b000880bf83
😎 Deploy Preview https://deploy-preview-6771--kubestellar-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Sep 6, 2026
@kubestellar-prow kubestellar-prow Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 6, 2026
@kubestellar-prow kubestellar-prow Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Sep 6, 2026
@kubestellar-prow

Copy link
Copy Markdown

Hi @kubestellar-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubestellar-prow kubestellar-prow Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 10, 2026
@kubestellar-prow

Copy link
Copy Markdown

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

copilot dco-signoff: yes Indicates the PR's author has signed the DCO. documentation Improvements or additions to documentation hold needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[operations] devstats.lock.yml and daily-team-status.lock.yml have expired stop-time gates — silently skipped (not failed) for ~8 months

0 participants