Skip to content

Commit 7c46b77

Browse files
committed
docs(platform): reconcile the linstor advisory rationale with the check
The check header states the LINSTOR field names were confirmed on a live controller; the values.yaml advisoryChecks comment still said they were not confirmed. Reconcile both to the accurate state: field names are confirmed on a live healthy controller, but faulty-state detection is not yet exercised against a degraded cluster, which is why linstor stays advisory by default. Signed-off-by: IvanHunters <[email protected]>
1 parent 5d3a6cb commit 7c46b77

1 file changed

Lines changed: 8 additions & 6 deletions

File tree

‎packages/core/platform/values.yaml‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -55,12 +55,14 @@ preflight:
5555
# check whose blocking behaviour is not yet trusted enough to hard-block an
5656
# existing customer's upgrade.
5757
#
58-
# linstor is advisory by default: its parsing of live `linstor -m` output
59-
# relies on LINBIT REST API field values (connection_status/disk_state) that
60-
# have not yet been confirmed against a live controller in e2e. Until that
61-
# evidence exists (see cozystack-pr-test), a wrong assumption there must warn,
62-
# never hard-block a healthy upgrade. Once e2e confirms the semantics, a
63-
# follow-up removes linstor from this default and lets it gate.
58+
# linstor is advisory by default. Its parsing of live `linstor -m` output
59+
# relies on LINBIT REST API fields (connection_status/disk_state): the field
60+
# NAMES are confirmed on a live healthy controller, but the FAULTY-state
61+
# detection (the denylist of bad disk_states) has not yet been exercised
62+
# against a genuinely degraded cluster. Until that e2e evidence exists (see
63+
# cozystack-pr-test), a wrong assumption there must warn, never hard-block a
64+
# healthy upgrade. Once e2e confirms the faulty-state path, a follow-up
65+
# removes linstor from this default and lets it gate.
6466
advisoryChecks: [linstor]
6567
# Bundle deployment configuration
6668
bundles:

0 commit comments

Comments
 (0)