Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FZrfgWEQM4Kb8nMRmMPHEC
Template e2e tests
|
| Scenario | Check | Result |
|---|---|---|
| install 1.2.0 | install + every workload ready | pass |
| install 1.2.0 | rendered == stored (Console Drift tab) | pass |
| install 1.2.0 | amqp-listener | pass |
| install 1.2.0 | publish-consume | pass |
| install 1.2.0 | persistent-marker | pass |
| install 1.2.0 | rejects-bad-password | pass |
| install 1.2.0 | data-survives-upgrade | pass |
| install 1.2.0 | no-op upgrade ×2 (no churn) | pass |
| install 1.2.0 | uninstall removes everything | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | install 1.1.1 (starting point) | pass |
| upgrade 1.1.1 → 1.2.0 (new values) [before, on 1.1.1] | amqp-listener | pass |
| upgrade 1.1.1 → 1.2.0 (new values) [before, on 1.1.1] | publish-consume | pass |
| upgrade 1.1.1 → 1.2.0 (new values) [before, on 1.1.1] | persistent-marker | pass |
| upgrade 1.1.1 → 1.2.0 (new values) [before, on 1.1.1] | rejects-bad-password | pass |
| upgrade 1.1.1 → 1.2.0 (new values) [before, on 1.1.1] | data-survives-upgrade | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | upgrade to 1.2.0 + every workload ready | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | rendered == stored (Console Drift tab) | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | amqp-listener | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | publish-consume | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | persistent-marker | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | rejects-bad-password | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | data-survives-upgrade | pass |
| upgrade 1.1.1 → 1.2.0 (new values) | uninstall removes everything | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | install 1.0.0 (starting point) | pass |
| upgrade 1.0.0 → 1.2.0 (new values) [before, on 1.0.0] | amqp-listener | pass |
| upgrade 1.0.0 → 1.2.0 (new values) [before, on 1.0.0] | publish-consume | pass |
| upgrade 1.0.0 → 1.2.0 (new values) [before, on 1.0.0] | persistent-marker | pass |
| upgrade 1.0.0 → 1.2.0 (new values) [before, on 1.0.0] | rejects-bad-password | pass |
| upgrade 1.0.0 → 1.2.0 (new values) [before, on 1.0.0] | data-survives-upgrade | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | upgrade to 1.2.0 + every workload ready | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | rendered == stored (Console Drift tab) | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | amqp-listener | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | publish-consume | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | persistent-marker | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | rejects-bad-password | pass |
| upgrade 1.0.0 → 1.2.0 (new values) | data-survives-upgrade | warn — known issue: 1.1.0 renamed the workload and volume set ({release} → {release}-rabbitmq-vs), so upgrading from 1.0.0 starts on a new, empty volume and the queued messages are gone. Old versions are documented, not fixed (maintainer ruling 2026-10-26); the README says not to upgrade in place. | stdout did not match /^PERSISTED$/ (attempt 6/6): MISSING (messages on e2e-1.0.0: 0) |
| upgrade 1.0.0 → 1.2.0 (new values) | uninstall removes everything | pass |
|
@jacobecox template e2e tests failed, so this PR cannot merge yet. See the report above and the run logs. |
The e2e CI confirmed it: 1.1.0 renamed the workload and volume set, so a message written on 1.0.0 is gone after the upgrade (1.1.1 → 1.2.0 keeps it). Per the old-versions rule (maintainer ruling 2026-10-26) the 1.0.0 row is a knownIssue, the 1.2.0 README says not to upgrade in place, and the briefing records the trap and what the CI now proves. README and Chart.yaml lastModified only (renders unchanged). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FZrfgWEQM4Kb8nMRmMPHEC
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FZrfgWEQM4Kb8nMRmMPHEC
|
@jacobecox template e2e tests failed, so this PR cannot merge yet. See the report above and the run logs. |
jacobecox
marked this pull request as ready for review
October 26, 2026 23:56
github-actions
Bot
added
the
not-on-test-branch
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Onboards rabbitmq to the e2e CI (work item 5161). Tests only — no chart changes.
rabbitmq_conf, upgraded withvalues: new, since 1.2.0 refuses the old keys at render). 1.0.0 is what all 6 customer installs run.rabbitmqadminon the container's loopback): the AMQP port is listening, a persistent message on a durable queue is consumed back unchanged, a wrong password is refused (the control), and a message left on the starting version is still queued after the upgrade.Old-versions rule (2026-10-26): CI confirmed the 1.0.0 upgrade loses the queue (1.1.0 renamed the workload and volume set; 1.1.1 → 1.2.0 keeps it). That row is now a
knownIssue, the 1.2.0 README says not to upgrade from 1.0.0 in place, and the briefing records the trap and replaces its "NOT deploy-tested" status with what the CI proves. README and Chart.yamllastModifiedonly, so the render is unchanged.🤖 Generated with Claude Code
https://claude.ai/code/session_01FZrfgWEQM4Kb8nMRmMPHEC