You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐛 bug: reviewer agent has mysteriously inconsistent configuration for inference #14678
I use the hive for FMA, dashboard at https://hosted-llm-d-incubation-llm-d-fast-m-yfzz.apps.fmaas-vllm-d.fmaas.res.ibm.com/ . ACMM level 2. In the dashboard's overall configuration, I configured it to use an IBM-internal LiteLLM gateway. Weeks ago, when ACMM level 2 did not include the reviewer agent . Today I find that the scanner, quality, and guide agents are indeed using that. However, I find that the reviewer agent ---recently introduced by (I don't know what) --- is configured to use copilot.
Expected behavior
I expected the reviewer agent to use the same inference configuration as my other agents.
Reproduction steps
Outlined above, to the degree that I know them.
Environment
Branch/version: v5.186.4-439-g551ffc34f
Deployment method: Hive Hub
Operating system or Kubernetes version: unknown
Relevant configuration (redact secrets): ?
Logs or screenshots
Here is some of the reviewer agent's configuration:
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label triage/accepted (configured in issue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.
🔒 Claimed by @Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.
No, scanner agent, you are confused about the version of hive that is running for FMA. It is not v5.186.4-677-g4ca1d3fd2. In my previous reopen, on Nov 4, I reported that the version of hive running is crux/v0.2.0-449-g55318dc61 . Commit 55318dc is part of PR 16451 , which merged Nov 3.
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.
Reopened at the request of @MikeSpreitzer, who reported this issue.If this was closed by a merged PR, first check whether the fix has reached you: it only takes effect after it ships in a tagged release and your deployment updates to it. If your running version already contains the fix and the problem persists, please add whatever you are still seeing (running version, logs, steps) so it is not closed the same way again. See #6762 for why this command exists.
@MikeSpreitzer this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
MikeSpreitzer commentedon Oct 27, 2026
@waltforme
@dumb0002
hivecommons-hive commentedon Oct 27, 2026
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label
triage/accepted(configured inissue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.hivecommons-hive commentedon Oct 27, 2026
🔒 Claimed by @Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.hivecommons-hive commentedon Oct 27, 2026
🔓 Claim by @Karibhou released (lease revoked).
76 remaining items
kubestellar-prow commentedon Nov 5, 2026
@MikeSpreitzer: Reopened this issue.
Details
In response to this:
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.
github-actions commentedon Nov 5, 2026
Reopened at the request of @MikeSpreitzer, who reported this issue.If this was closed by a merged PR, first check whether the fix has reached you: it only takes effect after it ships in a tagged release and your deployment updates to it. If your running version already contains the fix and the problem persists, please add whatever you are still seeing (running version, logs, steps) so it is not closed the same way again. See #6762 for why this command exists.
github-actions commentedon Nov 5, 2026
@MikeSpreitzer this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.