KiroCrew pack EBS volume attached but not mounted or mapped.

[royosherove]

in KiroCrew pack, the EBS attached volume is attached but not mounted. shoud also be auto-mounted and mapped so that the agent /home/ec2-user/workplace is mapped there so we have more space

[royosherove]

👻 Bode is on this · Kiro Crew Issue Radar
awaiting-merge · PR #107 · updated 14:07 UTC

progress

• 11:28 claimed — issue KiroCrew pack EBS volume attached but not mounted or mapped. #105 is a targeted pack/bootstrap bug, not a duplicate; existing KiroCrew history covers other installer concerns and no prior EBS/workplace fix

• 11:28 concluded root cause — packs/kirocrew/manifest.yaml and packs/registry.yaml declare data_volume_gb: 0, so deploy/bootstrap.sh skips the EBS mount; its only data bind mount is the OpenClaw-specific .openclaw path, with no KiroCrew agent workspace mapping

• 11:28 confirmed the attached-but-unused path — CloudFormation can attach data device when DataVolumeSize is nonzero, while bootstrap still follows the KiroCrew registry value and logs that no data volume was requested

• 11:28 next — update the KiroCrew data-volume metadata, regenerate the derived registry, add the KiroCrew workplace bind mount, and add regression coverage before opening the same PR

• 11:32 opened PR #107 from b63df9a; the PR includes Fixes #105, the EBS-backed workplace mount, service write access, and the regression test

• 11:40 addressed the P1 review finding in 72fb265: the dependent workplace bind mount is non-fatal when the persistent data mount is unavailable, remains ordered after it, and legacy fstab state is migrated safely; focused validation passed

• 11:41 post-push reconciliation — all current check-run entries pass; the PR is mergeable and clean, with no new review or requester activity; legacy status API has zero contexts and remains pending, so the PR stays open for human review/merge

• 14:07 handed issue KiroCrew pack EBS volume attached but not mounted or mapped. #105 to human review — the permitted crew: needs human label is now applied; PR fix(kirocrew): mount EBS-backed workspace #107 remains open and unmerged with all check-run entries passing