Skip to content

fix(kirocrew): mount EBS-backed workspace - #107

Open
royosherove wants to merge 2 commits into
mainfrom
crew/bode/issue-105
Open

fix(kirocrew): mount EBS-backed workspace#107
royosherove wants to merge 2 commits into
mainfrom
crew/bode/issue-105

Conversation

@royosherove

Copy link
Copy Markdown
Member

Summary

  • Request the KiroCrew data volume in the pack manifest and registry, and regenerate the derived registry JSON.
  • Mount /mnt/ebs-data/workplace at /home/ec2-user/workplace during bootstrap, migrate existing workspace content, and persist the bind mount in /etc/fstab.
  • Allow the KiroCrew gateway service to write to the protected workspace path.

Verification

  • bash tests/test-kirocrew-ebs.sh — base failed 6/6 assertions; implementation passes 7/7.
  • bash tests/test-sync-registry.sh — 46/0.
  • bash packs/kirocrew/test.sh — 73/0.
  • bash tests/test-pack-contracts.sh — 177/0.
  • Bootstrap syntax, new-code ShellCheck, exact validation syntax/ShellCheck command, and git diff --check pass.
  • bash deploy/test-bootstrap.sh reports one inherited failure from two pre-existing SC1090 warnings; pristine main reproduces the same warning-only failure. No CI or gate configuration was changed.

Fixes #105

Fixes #105

Crew: Bode (Kiro Crew Issue Radar)

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b63df9afc9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread deploy/bootstrap.sh Outdated
mount --bind /mnt/ebs-data/workplace /home/ec2-user/workplace
fi
if ! grep -qF "/mnt/ebs-data/workplace /home/ec2-user/workplace none bind 0 0" /etc/fstab; then
echo "/mnt/ebs-data/workplace /home/ec2-user/workplace none bind 0 0" >> /etc/fstab

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Make the workspace bind mount tolerate a missing EBS volume

On a reboot where the EBS volume is temporarily unavailable, its /mnt/ebs-data fstab entry is allowed to fail via nofail, but this new bind-mount entry is still required. Because /mnt/ebs-data/workplace then does not exist on the underlying root filesystem, the bind mount fails and can prevent local-fs.target from completing, potentially leaving the instance in emergency mode. Mark this dependent mount as non-fatal while preserving its ordering after /mnt/ebs-data.

Useful? React with 👍 / 👎.

Address review feedback by making the dependent bind mount non-fatal when the EBS volume is unavailable, preserving mount ordering, and migrating the legacy fstab entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

KiroCrew pack EBS volume attached but not mounted or mapped.

1 participant