Andrei Kvapil (kvaps) · Oct 8, 2026 · Oct 8, 2026 · Oct 8, 2026 · Oct 8, 2026 · Oct 8, 2026
@@ -17,6 +17,10 @@ on:
   # merges still exercise contract tests.
   push:
     branches: [main]
+    # The site under site/ is published on its own and has no tests.
+    paths-ignore:
+      - 'site/**'
+      - 'netlify.toml'
 
 permissions: {}
 

@@ -16,6 +16,10 @@ on:
   # merges still exercise the envtest harness.
   push:
     branches: [main]
+    # The site under site/ is published on its own and has no tests.
+    paths-ignore:
+      - 'site/**'
+      - 'netlify.toml'
 
 permissions: {}
 

@@ -7,6 +7,10 @@ name: Lint
 on:
   push:
     branches: [main]
+    # The site under site/ is published on its own and has no tests.
+    paths-ignore:
+      - 'site/**'
+      - 'netlify.toml'
 
 permissions: {}
 

@@ -0,0 +1,84 @@
+name: Deploy site to Pages
+
+# blockstor.org is the Hugo and Docsy site under site/. Netlify builds the
+# deploy previews from the same sources (netlify.toml).
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'site/**'
+      - '.github/workflows/pages.yml'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# One deployment at a time. A queued run is skipped for the newest one, but
+# a deployment in progress is allowed to finish.
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    env:
+      HUGO_VERSION: 0.164.0
+    steps:
+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        with:
+          persist-credentials: false
+
+      - name: Install Hugo
+        run: |
+          wget -q -O "${RUNNER_TEMP}/hugo.deb" \
+            "https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_linux-amd64.deb"
+          sudo dpkg -i "${RUNNER_TEMP}/hugo.deb"
+
+      - name: Setup Go
+        uses: actions/setup-go@4b73464bb391d4059bd26b0524d20df3927bd417 # v6.3.0
+        with:
+          go-version: "1.23"
+          cache: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
+        with:
+          # Hugo runs Node asset tools with "node --permission", which needs
+          # Node 22.13 or later.
+          node-version: "22"
+
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@45bfe0192ca1faeb007ade9deae92b16b8254a0d # v6.0.0
+
+      - name: Install Node.js dependencies
+        working-directory: site
+        run: npm ci
+
+      - name: Build with Hugo
+        working-directory: site
+        env:
+          HUGO_ENVIRONMENT: production
+          HUGO_ENV: production
+          BASE_URL: ${{ steps.pages.outputs.base_url }}
+        run: hugo --gc --minify --baseURL "${BASE_URL}/"
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 # v5.0.0
+        with:
+          path: ./site/public
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@368f82528645a54fb793d4d04e342629a3f51346 # v5.0.1
@@ -26,6 +26,10 @@ name: Pull Request
 on:
   pull_request:
     types: [opened, synchronize, reopened]
+    # The site under site/ is published on its own and has no tests.
+    paths-ignore:
+      - 'site/**'
+      - 'netlify.toml'
 
 # Cancel in-flight runs for the same PR when a new push arrives — saves
 # runner minutes on rapid force-push iterations.

@@ -7,6 +7,10 @@ name: E2E Tests
 on:
   push:
     branches: [main]
+    # The site under site/ is published on its own and has no tests.
+    paths-ignore:
+      - 'site/**'
+      - 'netlify.toml'
 
 permissions: {}
 

@@ -7,6 +7,10 @@ name: Tests
 on:
   push:
     branches: [main]
+    # The site under site/ is published on its own and has no tests.
+    paths-ignore:
+      - 'site/**'
+      - 'netlify.toml'
 
 permissions: {}
 

@@ -25,3 +25,9 @@
 .claude/
 pkg/satellite/pvc-dispatch-adjust.res
 linstor-migrate
+
+# blockstor.org site build output
+site/public/
+site/resources/
+site/node_modules/
+site/.hugo_build.lock
@@ -2,7 +2,7 @@
 
 ## TL;DR
 
-The premise in `known-issues.md` ("satellite pod IPs come from outside the pod CIDR" / "netInterfaces[0].address=<pod-CIDR>") is wrong. On both e2e-iptables and e2e-quorum the stored `Node.spec.netInterfaces[0].address` is the host InternalIP (10.27.0.x / 10.161.0.x). What actually differs between the two stands is **who owns the Node CRD's `spec` once piraeus-operator finishes reconciling**:
+The premise in the Bug 42 entry of `known-issues.md` (since removed) ("satellite pod IPs come from outside the pod CIDR" / "netInterfaces[0].address=<pod-CIDR>") is wrong. On both e2e-iptables and e2e-quorum the stored `Node.spec.netInterfaces[0].address` is the host InternalIP (10.27.0.x / 10.161.0.x). What actually differs between the two stands is **who owns the Node CRD's `spec` once piraeus-operator finishes reconciling**:
 
 - **e2e-quorum** — piraeus runs against its own bundled `linstor-controller` (LinstorCluster `spec: {}`). Piraeus never touches the blockstor Node CRD. Spec stays exactly as `install-blockstor.sh` left it: one interface `default` with the k8s InternalIP, `generation: 1`, no `Aux/piraeus.io/*` props.
 - **e2e-iptables** — `LinstorCluster.spec.externalController.url = http://blockstor-apiserver.blockstor-system.svc:3370` was set (by an `observability-*` e2e scenario, see `tests/e2e/observability-three-way.sh:78-84` and `tests/e2e/observability-capacity-correlation.sh:240-244`). The operator now drives blockstor-apiserver as its LINSTOR backend and rewrites the Node CRD via `PUT /v1/nodes/{node}/net-interfaces/default-ipv4`: interface name changes from `default` to `default-ipv4`, `satellitePort=3366` + `satelliteEncryptionType=PLAIN` are added, and `Aux/piraeus.io/last-applied` / `Aux/piraeus.io/configured-interfaces` props appear in `spec.props`. Generation climbs to 9.
@@ -116,5 +116,5 @@ Both `tests/e2e/observability-three-way.sh:81-84` and `tests/e2e/observability-c
 ## Recommended next steps
 
 1. Apply fix (A) + (B), each as its own commit.
-2. Rewrite `docs/known-issues.md` Bug 42 entry to match what's actually happening (interface-name + props churn from externalController-mode piraeus), drop the unsupported pod-CIDR claim, and adjust severity (P3 — cosmetic / fragility, not a DRBD outage).
+2. Rewrite the Bug 42 entry (the page has since been removed) to match what's actually happening (interface-name + props churn from externalController-mode piraeus), drop the unsupported pod-CIDR claim, and adjust severity (P3 — cosmetic / fragility, not a DRBD outage).
 3. Optional follow-up: add a contract test asserting that `snapshot_fetcher.peerAddr()` resolves correctly when the only NetInterface is named `default-ipv4`. That pins fix (A) and would have caught this earlier.
@@ -60,6 +60,7 @@ Row IDs match the command-catalogue indexes used by `cli-parity-refresh.sh` (see
 | 42 | `r d <rd> <nonexistent-node>` (idempotent resource delete) | WIRE_SHAPE | permanent | BLOCKSTOR idempotent-delete envelope. Deleting a resource placement on a node that holds none returns `SUCCESS: resource already absent: <node> on <rd>`; upstream LINSTOR returns `WARNING: Node: <rd>, Resource: <node> not found`. Both exit 0. Deliberate: a CSI `DeleteVolume` / operator retry on an already-removed placement MUST be idempotent. Same family as the snapshot-delete idempotency in row 33. Pinned by the resource-delete REST handler's already-absent path (`pkg/rest/resources.go`). |
 | 40 | `n c <node> <ip> --node-type Satellite` (node-create success envelope) | WIRE_SHAPE | permanent | BLOCKSTOR envelope shape on satellite node registration. BS emits `node created: <node>` + a `SUCCESS: No active connection to satellite '<node>'` line; upstream emits `New node '<node>' registered.` (with a UUID detail) + a `WARNING: No active connection to satellite '<node>'` line whose Details explain the controller will (re-)establish the connection. Both register the node and exit 0; the operator-visible outcome (node exists, awaiting satellite handshake) is identical. The "no active connection" notice is INFO/SUCCESS-class in BS vs WARNING-class upstream, and BS does not surface the volatile node UUID inline. Envelope-shape only; no behavioural divergence. |
 | 16 | `ps l` (physical-storage list — `size` field) | WIRE_SHAPE | 2026-12-31 | BS `/v1/physical-storage` omits the per-device `size` key that python-linstor's `show_physical_storage` reads unconditionally (`linstor/responses.py` `devices.size`), so `linstor ps l` raises `KeyError: 'size'` and exits 2 against BS where upstream renders the table and exits 0. `ps l` is a hardware-discovery convenience surface; linstor-csi / piraeus-operator never call it, and the device-pool creation path (`ps create-device-pool`, cli-matrix `ps-cdp-*`) is unaffected. Tracked as a missing wire field to populate on the physical-storage DTO; whitelisted until then. |
+| 86 | `node interface modify <node> <nic> --active` | BEHAVIOR | permanent | blockstor has no satellite-to-controller connection to re-target: the satellite talks only to the Kubernetes API through the in-cluster Service. `NodeNetInterface` carries no `Active` field, and the REST `is_active` flag is synthesised on read as "first interface", so `--active` changes nothing. To make another interface active, reorder `spec.netInterfaces` so it comes first; a changed address reaches the node's DRBD configuration after its satellite pod restarts. Pinned by `TestSatelliteFlagsLackControllerBindAddress` and `TestNodeCRDHasNoActiveField` in `pkg/satellite/stream/redial_spec_test.go`. |
 
 ## Open (block merge until addressed)
 

@@ -10,7 +10,7 @@ Fix (this PR): relax the apiserver validator to mirror upstream, AND make the Re
 
 The residual failures are unchanged from the table below (all class (a) Node/satellite-convergence + class (b) apiserver scale-out cache race + Bug 33 satellite-snapshot finalizer drain in AfterEach teardown — the latter affects lowercase snapshots too).
 
-Prior baseline (pre-audit): **56/74 specs pass** (74 ran; 17 skipped; 1 pending) after seven wire-shape gaps and three concurrency races were closed. The same job-config is used here. The audit collected 9 hard failures during the first 16 seconds of the run before the harness wedged on a snapshot-data-plane test (`sanity-controller-source-vol-*`) waiting for a satellite-side reconcile that never converged on the e2e-lc1 stand (Bug 33 territory — see `docs/known-issues.md`). Wire-shape and routing observations cover all 18 expected failures from the prior baseline.
+Prior baseline (pre-audit): **56/74 specs pass** (74 ran; 17 skipped; 1 pending) after seven wire-shape gaps and three concurrency races were closed. The same job-config is used here. The audit collected 9 hard failures during the first 16 seconds of the run before the harness wedged on a snapshot-data-plane test (`sanity-controller-source-vol-*`) waiting for a satellite-side reconcile that never converged on the e2e-lc1 stand (Bug 33 territory, since closed by the orphan DRBD sweeper). Wire-shape and routing observations cover all 18 expected failures from the prior baseline.
 
 ## Failure-class legend
 
@@ -60,6 +60,6 @@ So the **post-fix expected pass rate stays at 56/74**. The new finding from this
 2. **CreateSnapshot empty-name validation** (c, #12-#13) — single check, flips two FAILs to PASS. Surfaces a real bug-class (silent slug-of-empty).
 3. **DeleteSnapshot folds unknown-RD into success** (b, #14) — one-liner, flips one FAIL to PASS, closes a CSI idempotence corner.
 4. **ListSnapshots empty-result envelope + exact-fit pagination** (c, #15-#16) — small handler tweaks, flips two FAILs to PASS.
-5. **Bug 33 satellite-finalizer storm** — not a csi-sanity gap per se, but the audit blocker for re-running the suite cleanly. Already tracked in `docs/known-issues.md` (Bug 33 — closed by 5.34 sweeper; the storm seen on this run was a residual from the controller crashloop before Bug 41 RBAC was applied to the live stand).
+5. **Bug 33 satellite-finalizer storm** — not a csi-sanity gap per se, but the audit blocker for re-running the suite cleanly. Tracked as Bug 33 (closed by 5.34 sweeper; the storm seen on this run was a residual from the controller crashloop before Bug 41 RBAC was applied to the live stand).
 
 After (1)–(4) the expected pass rate is **64/74**. The remaining 10 failures are all (a) (kernel-mount Node Service + satellite-convergence snapshot/clone tests) and are out of scope for the single-pod csi-sanity harness; running them needs a real piraeus-operator deployment with a CSI Node sidecar per worker and a stand with reliable satellite reconcile.
@@ -38,7 +38,7 @@ Each row names the Tier 2 test(s) that exercise the same REST/CRD/reconciler pat
 | `placement-label-sync.sh` | NodeLabelSyncReconciler mirroring k8s labels → `Aux/...` props; envtest IS real k8s API. | Group A `TestGroupANodeAuxLabelSync` |
 | `recovery-false-diskless.sh` | Today asserts 404 on `r mkavail` (handler not wired). Pure wire-shape probe — no kernel-state contract. | Group F wire-shape probes; will move to Tier 4 when the handler lands and the test becomes "adopt existing on-disk state" |
 
-`lc-rd-delete-churn.sh` is **kept** despite touching the same handlers — it runs 10 iterations and watches `dmesg`/`zfs list` for orphan ZVOLs and `node_id of X instead of Y` kernel warnings (cited by `docs/known-issues.md` as the validation source for the storage-sweeper). That assertion needs a live cluster.
+`lc-rd-delete-churn.sh` is **kept** despite touching the same handlers — it runs 10 iterations and watches `dmesg`/`zfs list` for orphan ZVOLs and `node_id of X instead of Y` kernel warnings (the validation source for the storage-sweeper). That assertion needs a live cluster.
 
 ---