chore(release): v0.1.15#171
Conversation
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
|
Warning Review limit reached
More reviews will be available in 57 minutes and 37 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the CHANGELOG.md for the v0.1.15 bugfix release, detailing two robustness fixes: the satellite waiting for the backing zvol device to resolve a udev race, and the apiserver falling back to the direct API reader to prevent spurious 404s on cache-missed resource definitions. The review feedback suggests minor stylistic improvements in the changelog text, specifically capitalizing 'Cozystack' and 'Apiserver' for consistency, and correcting the hyphenation of 'resource definition'.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| ## v0.1.15 — 2026-06-22 | ||
|
|
||
| Bugfix release. Two satellite/apiserver robustness fixes surfaced while validating blockstor as the cozystack storage backend (full heavy-app e2e on a 3-node Talos+QEMU stand). Primary backend focus: ZFS thin (zvol-backed). |
There was a problem hiding this comment.
The project name Cozystack should be capitalized for consistency with other occurrences in the changelog (such as on line 153).
| ### Fixed | ||
|
|
||
| - **Satellite waits for the backing zvol device before mkfs/attach (#170)** — on ZFS-thin, `zfs create` returns before udev has created the `/dev/zvol/...` device node, so the satellite's mkfs/attach could fire against a not-yet-present device and fail with "does not exist" on the first reconcile, leaving the volume unattached until a later retry. The satellite now polls the backing block device (`blockdev --getsize64`, with a best-effort `udevadm settle`) up to a bounded timeout before mkfs/attach, closing the zfs/udev race. Pinned at L1 (`reconciler_zvol_device_wait_test`, which fails on the pre-fix path). | ||
| - **apiserver resolves a cache-missed resource-definition via the direct API reader (#170)** — the apiserver runs multiple replicas with no leader election, so a `GET /v1/resource-definitions/{rd}` can load-balance to a replica whose informer cache has not yet observed a just-committed RD and return a spurious 404 (surfaced by linstor-csi as `ControllerPublishVolume failed: 404`). The RD GET now falls back to the uncached API reader on a cache NotFound — mirroring the existing volume-definition cache-lag handling — so a committed-but-not-yet-cached RD is resolved instead of 404'd. Pinned at L1 (`resource_definitions_rd404_internal_test`, which fails on the pre-fix path). |
There was a problem hiding this comment.
For consistency with other bullet points (such as the one on line 13 starting with Satellite), the first word of this bullet point should be capitalized. Additionally, "resource definition" is used as a noun phrase here and should not be hyphenated. Suggested change: - Apiserver resolves a cache-missed resource definition via the direct API reader (#170) — the apiserver runs multiple replicas with no leader election, so a GET /v1/resource-definitions/{rd} can load-balance to a replica whose informer cache has not yet observed a just-committed RD and return a spurious 404 (surfaced by linstor-csi as ControllerPublishVolume failed: 404). The RD GET now falls back to the uncached API reader on a cache NotFound — mirroring the existing volume-definition cache-lag handling — so a committed-but-not-yet-cached RD is resolved instead of 404'd. Pinned at L1 (resource_definitions_rd404_internal_test, which fails on the pre-fix path).
1 participant
Cut v0.1.15 — bugfix release with the two satellite/apiserver robustness fixes from #170 (zvol-device-wait mkfs race + RD GET cache-miss API-reader fallback), surfaced validating blockstor as the cozystack storage backend. Tagging
v0.1.15after merge triggers the release pipeline (3 ghcr images + GitHub Release from this CHANGELOG section).