The current 3.0.2 upgrade docs don't tell users to re-pull any S2I images. There is an issue, for example, with the EAP image where we are using the same tag (6.4) but the underlying image has changed to deal with a non-compatible change in the way we run Docker images.
The attached Knowledge Base Solution should provide enough documentation for this, issue. Erik can you confirm?
If the oc import fixes the specific EAP S2I problem then I guess the KCS is "the" solution.
Resolved via KCS: https://access.redhat.com/solutions/2188121