[patch] MASCORE-15768: technote to add known issue for Civil Image Stitching PVC migration failure for 8.x to 9.0 migration - #435
Merged
Conversation
…itching PVC migration failure.
bmoferrall
approved these changes
Jul 27, 2026
Contributor
|
@bhavsar909 please remove this technote from ppc64le and s390x files, we need it only amd64 yaml file |
…v9-260730 catalogs for ppc64le and s390x files.
prveenkumr
approved these changes
Jul 29, 2026
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
3 participants
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.
Summary
Adds a known issue entry to the v9-260730 catalog editorial notes (all three architectures: amd64, ppc64le, s390x) documenting a permanent Failure state in the Imagestitching CR after upgrading IBM Maximo Manage from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed.
This issue was silently present across the last three FVT runs (May, June, July). It caused a hard pipeline timeout in the July run (#2084), blocking the suite_app_upgrade task at ~60 minutes.
Root Cause
The 8.7.x imagestitching operator (ibm-mas-imagestitching) auto-created the PVC during initial deployment but never wrote pvcname back into the CR spec. The 9.0.x operator (tag 1.0.11, streams 1.1.x / 2.0.x) introduced a hard-fail behaviour when spec.settings.pvc.pvcname is absent, causing the CR to enter a permanent Failure state on every reconcile.
There is no automatic migration in the 9.0.x upgrade path to backfill this field.
problem: a behavioural contract was inverted without a migration
Commit 07f8efb (MAXCI-6343, Jun 25 2024) changed the meaning of spec: {} from "operator owns the PVC lifecycle" to "hard fail". There was no migration step. Commit 07f8efb (MAXCI-6343, Jun 25 2024, tagged at 1.0.2-81-g07f8efb) was merged into master (PR) and from there promoted into 1.1.x and 2.0.x-dev. It never landed on 1.0.x or 1.0.x-dev.
Note: This issue affects only customers upgrading from 8.7.x to 9.0.x who had Civil Image Stitching deployed prior to upgrade. Fresh 9.0.x installations are not affected.