القائمة
KubeVirt lab testing for common. Use when testing a common PR against bluefin, bluefin-lts, or dakota on ghost.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/projectbluefin/common --skill lab-testingيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Manage OS-managed Homebrew packages. Use when adding/removing default brew packages, moving tools between RPM and brew, or auditing image-vs-brew placement.
OEM hardware first-boot setup hooks in projectbluefin/common. Use when adding hardware-specific setup, understanding hook directories and versioning contract, or applying shellcheck requirements.
CI policy and tooling — SHA pinning, pre-commit guards, Renovate digest tracking, and workflow config. Use when editing .github/workflows/ files.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | lab-testing |
| version | 1.1 |
| last_updated | 2026-07-29 |
| id | lab-testing |
| one_line_purpose | Boot images on the KubeVirt lab and collect test logs. |
| entry_point | docs/skills/lab-testing/SKILL.md |
| category | test-authoring |
| mcp_compliance_level | partial |
| optimization_status | draft |
| status | active |
| dependencies | [] |
| tags | ["lab","testing","kubevirt"] |
| description | KubeVirt lab testing for common. Use when testing a common PR against bluefin, bluefin-lts, or dakota on ghost. |
| metadata | {"type":"reference"} |
projectbluefin/common is the shared OCI layer consumed by every downstream variant.
A regression in system_files/shared/ breaks bluefin, bluefin-lts, AND dakota simultaneously.
Lab testing on ghost catches what GitHub Actions E2E cannot: KVM-backed full boots,
real systemd unit activation, services that need device nodes, and cold-start timing.
| Signal you want | Use |
|---|---|
| Pre-merge: does this common change compose correctly? | pr-e2e.yml (PR gate) |
| Post-merge: does the shared layer regress any variant? | e2e.yml (post-merge E2E) |
| Real systemd journal — any service failures? | Lab: log-scan-* workflows |
| Boot time, startup ordering, GNOME session smoke | Lab: bluefin-qa-pipeline suites=smoke |
| System contract (bootc, read-only /usr, staged deploy) | Lab: bluefin-qa-pipeline suites=system |
| Hardware-only bugs (suspend, USB-C, GPU PM) | Physical machines (exo-1 etc.) |
GitHub Actions E2E (e2e.yml) uses QEMU on ubuntu-latest runners.
The lab uses KubeVirt on ghost (Ryzen AI MAX+ 395, 64GB RAM, full KVM).
Neither replaces the other. Lab tests run on demand; E2E runs on every push.
| Changed path | Lab variants to test |
|---|---|
system_files/shared/** | bluefin + lts + dakota (all three) |
system_files/bluefin/** | bluefin + lts |
| dconf / GNOME settings | bluefin + lts (dakota GNOME stack is BST-sourced) |
just/, Justfile, *.just | all three (ujust ships to all variants) |
Containerfile changes | all three |
When you verify a PR through the ghost cluster, the result must be posted as a PR comment. This is the canonical evidence format for cluster verification. Copy the template from , fill every field with real CLI evidence (workflow name/phase, , pod/VMI state), and update an existing report comment from you rather than stacking duplicates.
argo logsThis report is an explicit exception to the normal "don't post comments describing your actions" convention — it is the lab result, not a status update.
| Item | Value |
|---|---|
| Cluster | k3s on ghost (192.168.1.102) |
| VM compute host | ghost — all KubeVirt VMs pinned here |
| Argo UI | http://192.168.1.102:32746 |
| WorkflowTemplates | provision-bluefin-vm, bib-build-and-push, teardown-bluefin-vm, dakota-bst, toggle-testing-rebase, bluefin-qa-pipeline, dakota-qa-pipeline, bluefin-migration-test |
| SSH key secret | bluefin-test-ssh-key in argo namespace |
| SSH user | bluefin-test |
Critical networking rule: log-collection and test pods MUST set
nodeSelector: kubernetes.io/hostname: ghost. KubeVirt masquerade NAT iptables
rules live in the virt-launcher pod netns. A pod on exo-1 cannot reach VM IPs.
This skill was split on 2026-07-29 to stay under the 200-line soft budget (it
was 910 lines). Core when/scope/posting/infra guidance stays above; the rest
moved to references/:
| Need | Reference |
|---|---|
| Golden disk status, live toggle-testing methodology, firing up all three variants, reading journal output, submit smoke+system quick-start | references/methodology.md |
| Baseline vs delta methodology for reviewing a PR that touches systemd units/timers | references/pr-review-baselines.md |
| Known issues and operational gotchas (SSH hangs, Argo template resolution, BIB build failures, capacity checks, VMI namespaces, etc.) | references/known-issues.md |
Lab tests and GitHub Actions E2E are complementary, not redundant:
common PR
│
├─► pr-e2e.yml ──────── PR gate: common suite on composed image
│ (QEMU, ubuntu-latest, ~12 min)
│
├─► [merge to main]
│
├─► e2e.yml ─────────── post-merge: smoke+common on all 3 tags
│ (QEMU, ubuntu-latest, ~15 min)
│
└─► lab (on demand) ───── real KVM boot, systemd journal, system suite
(KubeVirt on ghost, full OS boot)
The lab catches:
After=, Wants= wiring in unit files)ublue-system-setup.service or ublue-user-setup.service failures/sys or /proc paths absent in QEMUlibsetup.sh version-script failures)For each failed unit or journal error found:
system_files/ path owns the unit or configbug:
common if the unit/config ships from system_files/bluefin/bluefin-lts/dakota if it's variant-specific