-
Bug
-
Resolution: Done
-
Optional
-
7.7.1.GA
-
None
-
-
-
-
-
-
ER1
-
2020 Week 22-24 (from May 25), 2020 Week 37-39 (from Sep 7), 2021 Week 34-36 (from Aug 23), 2021 Week 37-39 (from Sep 13), 2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25), 2021 Week 46-48 (from Nov 15)
I'm just passing on https://bugzilla.redhat.com/show_bug.cgi?id=1802272 as there doesn't seem to be a BZ component for RHPAM. I have no actual knowledge about this bug at all; please have a look at it. Simply copying over the summary:
Description of problem:
In the container image registry.redhat.io/rhpam-7/rhpam-kieserver-rhel8, there is a symbolic link at /usr/local/s2i/scl-enable-maven that points to /opt/jboss/container/maven/default/scl-enable-maven.
[jboss@6b70467d8f9b ~]$ ls -l /usr/local/s2i/scl-enable-maven
lrwxrwxrwx. 1 jboss root 51 Jan 29 11:20 /usr/local/s2i/scl-enable-maven -> /opt/jboss/container/maven/default/scl-enable-maven
However, listing the contents of that directory shows:
[jboss@6b70467d8f9b ~]$ ls /opt/jboss/container/maven/default/
'*' jboss-settings.xml maven.sh
The symlink is therefore invalid and attempting to execute results in failure.
Version-Release number of selected component (if applicable):
- latest
- 7.6.0-2.1580292314
- 7.6.0-2
- (Possibly more ?)
How reproducible:
Steps to Reproduce:
1.
docker run -it --rm registry.redhat.io/rhpam-7/rhpam-kieserver-rhel8:7.6.0-2.1580292314 /bin/bash
2.
[jboss@6b70467d8f9b ~]$ /usr/local/s2i/scl-enable-maven
Actual results:
bash: /usr/local/s2i/scl-enable-maven: No such file or directory
Expected results:
scl-enable-maven should be executed
- is related to
-
CLOUD-3394 /opt/jboss/container/maven/default/* link points to non-existent path
- New
-
OPENJDK-194 s2i/run attempts to source missing scl-enable-maven
- Verified