Affected images:

• jboss-eap-7-xp1-openjdk8-runtime-openshift-rhel7-container-1.0-3
  • Runtime image incorrectly references SCL, which isn't needed to build (no RPMs are installed) - FIXED
• jboss-eap-7-eap73-openj9-11-openshift-rhel8-container-7.3.0-2
  • Contains RPMs that is shouldn't, likely due to use of unpublished pulp repos - FIXED

• jboss-eap-7-eap73-openjdk8-runtime-openshift-rhel7-container-7.3.1-2
  • Runtime image references SCL, which is not needed (no RPMs are installed) - FIXED
• jboss-eap-7-eap73-openj9-11-openshift-rhel8-container-7.3.0-2
  • Contains RPMs it shouldn't

For these issues, they fall into some different categories:

(1)  RHEL images, usually runtime that reference SCL in the content_sets.yml files – this won't be used, as the only thing installed from SCL is maven. Fix is to remote the reference to SCL in the content_sets.yml in the github repo and rebuild with cekit (cekit generates this file automatically.)

(2) OpenJ9 images using  include_unpublished_pulp_repos: true in the compose: element – this will potentially include unreleased RPMs, which shoudn't be pushed out as GA (yet)

(3) Missing content_sets.yml / container.yml in built images. FM references a specific dist-git commit when it rebuilds images, so if there is an invalid configuration for the commit SHA it will rebuild, this will always be wrong until a newer, corrected image is pushed GA.