fix(hermes): host-side chown for CRD child agent PVCs on Linux k3d#511
Open
HananINouman wants to merge 1 commit into
Open
fix(hermes): host-side chown for CRD child agent PVCs on Linux k3d#511HananINouman wants to merge 1 commit into
HananINouman wants to merge 1 commit into
Conversation
PR #481 only repaired hermes-<id> volumes after hermes.Sync (master agent). Child agents live under agent-<name> and are provisioned by the controller or agent-factory without that path, so hermes-data stayed 1000:1000 while Hermes runs as 10000:10000 and crash-looped on Permission denied under /data/.hermes. Extend EnsureHermesDataPVCOwnership to agent-<name>/hermes-data, call it from obol agent new and obol sell demo quant, and add obol agent repair-perms for factory-only creates that cannot docker-exec the k3d node from in-cluster. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #481 only repaired hermes- volumes after hermes.Sync (master agent). Child agents live under agent- and are provisioned by the controller or agent-factory without that path, so hermes-data stayed 1000:1000 while Hermes runs as 10000:10000 and crash-looped on Permission denied under /data/.hermes.
Extend EnsureHermesDataPVCOwnership to agent-/hermes-data, call it from obol agent new and obol sell demo quant, and add obol agent repair-perms for factory-only creates that cannot docker-exec the k3d node from in-cluster.
Summary
What changed:
Why it matters:
Risk level:
Commit under test:
Base branch:
Scope
Validation
CI checks:
Unit tests:
Integration tests:
Flow tests:
Release smoke:
Live Chain Evidence
Do not include private keys, seed phrases, passwords, hostnames, personal paths, or raw bearer tokens.
Network:
RPC/provider:
Facilitator:
Contracts and tokens:
Wallet roles:
Balances:
Transaction receipts:
Runtime Evidence
QA environment:
Images:
Kubernetes / stack:
Model and routing:
Artifacts and logs:
Demo readiness:
Review Notes
Known gaps:
Follow-ups:
Reviewer focus: