-
Bug
-
Resolution: Done
-
Blocker
-
EAP-XP-2.0.0.CR1
-
None
-
False
-
False
-
-
-
-
-
-
GA
-
Undefined
-
The image stream import templates creates XP2 image streams with [2.0,latest] tags
$ oc get imagestream NAME IMAGE REPOSITORY TAGS UPDATED jboss-eap-xp2-openjdk8-openshift default-route-openshift-image-registry.apps-crc.testing/pkremens-namespace/jboss-eap-xp2-openjdk8-openshift 2.0,latest jboss-eap-xp2-openjdk8-runtime-openshift default-route-openshift-image-registry.apps-crc.testing/pkremens-namespace/jboss-eap-xp2-openjdk8-runtime-openshift 2.0,latest
but the docs within the quickstarts are using 1.0, thus the examples won't work if following the docs.
Docs example:
$ oc new-app --template={ImagePrefixVersion}-basic-s2i \ -p EAP_IMAGE_NAME=jboss-{ImagePrefixVersion}-openjdk8-openshift:1.0 \ -p EAP_RUNTIME_IMAGE_NAME=jboss-{ImagePrefixVersion}-openjdk8-runtime-openshift:1.0 \ -p IMAGE_STREAM_NAMESPACE="{artifactId}-project" \ -p SOURCE_REPOSITORY_URL="{EAPQuickStartRepo}" \ -p SOURCE_REPOSITORY_REF="{EAPQuickStartRepoRef}" \ -p CONTEXT_DIR="{artifactId}"
Maybe we should simply go with the ":latest" to avoid these.
- blocks
-
CLOUD-3860 EAP XP 2.0 OpenShift Image Release
- Closed
- is cloned by
-
WFLY-14239 jboss-eap-xp2 imagestreams-templates are using a wrong (2.0) tag
- Closed
- is related to
-
JBEAP-20647 Update the Using Eclipse MicroProfile with JBoss EAP XP 2.0.0 guide to work with XP2 OCP images instead of XP1
- Closed
- relates to
-
JBEAP-20718 xp-2.0.0.GA-CR1 documentation within the quickstarts refer XP1 images/templates instead of XP2
- Closed