[JBoss JIRA] (WFWIP-175) Operator doesn't react on env removal
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFWIP-175?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFWIP-175:
---------------------------------
Description:
Removing env from WildFlyServerSpec is not reflected by Operator.
*Actual:*
* removing env doesn't trigger update action
* removed envs are never actually removed prom the projects
*Expected:*
* removing env does trigger update action
* removed envs are removed prom the projects
*Steps to reproduce:*
{code}
cat eap-operator.yaml
...
spec:
applicationImage: <image>
env:
- name: TEST_START
value: INITIAL
size: 1
...
{code}
Deploy and see the envs
{code}
oc apply -f eap-operator.yaml
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=INITIAL
{code}
change the value of variable to TEST_START=UPDATE
{code}
oc edit wildflyserver eap-operator
env:
- name: TEST_START
value: UPDATE
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
{code}
change the name of variable to TEST_UPDATE=UPDATE - {color:red}a new one is created!{color}
{code}
oc edit wildflyserver eap-operator
env:
- name: TEST_UPDATE
value: UPDATE
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
{code}
remove the entire env section from spec - {color:red}delete envs are not removed!{color}
{code}
oc edit wildflyserver eap-operator
# no pods update is triggered, operator didn't react on envs removal
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
{code}
add a new env - {color:red}pod still contains deleted envs!{color}
{code}
oc edit wildflyserver eap-operator
env:
- name: TEST_ADD
value: ADD
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
TEST_ADD=ADD
{code}
was:
Removing env from WildFlyServerSpec is not reflected by Operator.
*Actual:*
* removing env doesn't trigger update action
* removed envs are never actually removed prom the projects
*Expected:*
* removing env does trigger update action
* removed envs are removed prom the projects
*Steps to reproduce:*
{code}
cat eap-operator.yaml
...
spec:
applicationImage: <image>
env:
- name: TEST_START
value: INITIAL
size: 1
...
{code}
Deploy and see the envs
{code}
oc apply -f eap-operator.yaml
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=INITIAL
{code}
change the value of variable to TEST_START=UPDATE
{code}
oc edit wildflyserver eap-operator
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
{code}
change the name of variable to TEST_UPDATE=UPDATE - {color:red}a new one is created!{color}
{code}
oc edit wildflyserver eap-operator
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
{code}
remove the env section from spec - {color:red}delete envs are not removed!{color}
{code}
oc edit wildflyserver eap-operator
# no pods update is triggered, operator didn't react on envs removal
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
{code}
add a new env - {color:red}pod still contains deleted envs!{color}
{code}
oc edit wildflyserver eap-operator
env:
- name: TEST_ADD
value: ADD
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
TEST_ADD=ADD
{code}
> Operator doesn't react on env removal
> -------------------------------------
>
> Key: WFWIP-175
> URL: https://issues.jboss.org/browse/WFWIP-175
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Brian Stansberry
> Priority: Blocker
>
> Removing env from WildFlyServerSpec is not reflected by Operator.
> *Actual:*
> * removing env doesn't trigger update action
> * removed envs are never actually removed prom the projects
> *Expected:*
> * removing env does trigger update action
> * removed envs are removed prom the projects
> *Steps to reproduce:*
> {code}
> cat eap-operator.yaml
> ...
> spec:
> applicationImage: <image>
> env:
> - name: TEST_START
> value: INITIAL
> size: 1
> ...
> {code}
> Deploy and see the envs
> {code}
> oc apply -f eap-operator.yaml
> oc set env pod/eap-operator-0 --list | grep TEST
> TEST_START=INITIAL
> {code}
> change the value of variable to TEST_START=UPDATE
> {code}
> oc edit wildflyserver eap-operator
> env:
> - name: TEST_START
> value: UPDATE
> # wait till the eap pod is terminated, a new one is started instead
> oc set env pod/eap-operator-0 --list | grep TEST
> TEST_START=UPDATE
> {code}
> change the name of variable to TEST_UPDATE=UPDATE - {color:red}a new one is created!{color}
> {code}
> oc edit wildflyserver eap-operator
> env:
> - name: TEST_UPDATE
> value: UPDATE
> # wait till the eap pod is terminated, a new one is started instead
> oc set env pod/eap-operator-0 --list | grep TEST
> TEST_START=UPDATE
> TEST_UPDATE=UPDATE
> {code}
> remove the entire env section from spec - {color:red}delete envs are not removed!{color}
> {code}
> oc edit wildflyserver eap-operator
> # no pods update is triggered, operator didn't react on envs removal
> oc set env pod/eap-operator-0 --list | grep TEST
> TEST_START=UPDATE
> TEST_UPDATE=UPDATE
> {code}
> add a new env - {color:red}pod still contains deleted envs!{color}
> {code}
> oc edit wildflyserver eap-operator
> env:
> - name: TEST_ADD
> value: ADD
> # wait till the eap pod is terminated, a new one is started instead
> oc set env pod/eap-operator-0 --list | grep TEST
> TEST_START=UPDATE
> TEST_UPDATE=UPDATE
> TEST_ADD=ADD
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11960) Upgrade JSF based on Mojarra 2.3.9.SP03
by Steven De Groote (Jira)
[ https://issues.jboss.org/browse/WFLY-11960?page=com.atlassian.jira.plugin... ]
Steven De Groote commented on WFLY-11960:
-----------------------------------------
Not sure where else this should go, but given the bugs resolved in here have prevented us from upgrading since WildFly11, could you shed a light on when this could be expected to go public?
I mean, in which Wildfly version? A patch for 17 or immediately 18? And when would that be?
> Upgrade JSF based on Mojarra 2.3.9.SP03
> ---------------------------------------
>
> Key: WFLY-11960
> URL: https://issues.jboss.org/browse/WFLY-11960
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JSF
> Reporter: Ilia Vassilev
> Assignee: Farah Juma
> Priority: Major
> Labels: downstream_dependency
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-175) Operator doesn't react on env removal
by Petr Kremensky (Jira)
Petr Kremensky created WFWIP-175:
------------------------------------
Summary: Operator doesn't react on env removal
Key: WFWIP-175
URL: https://issues.jboss.org/browse/WFWIP-175
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Petr Kremensky
Assignee: Brian Stansberry
Removing env from WildFlyServerSpec is not reflected by Operator.
*Actual:*
* removing env doesn't trigger update action
* removed envs are never actually removed prom the projects
*Expected:*
* removing env does trigger update action
* removed envs are removed prom the projects
*Steps to reproduce:*
{code}
cat eap-operator.yaml
...
spec:
applicationImage: <image>
env:
- name: TEST_START
value: INITIAL
size: 1
...
{code}
Deploy and see the envs
{code}
oc apply -f eap-operator.yaml
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=INITIAL
{code}
change the value of variable to TEST_START=UPDATE
{code}
oc edit wildflyserver eap-operator
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
{code}
change the name of variable to TEST_UPDATE=UPDATE - {color:red}a new one is created!{color}
{code}
oc edit wildflyserver eap-operator
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
{code}
remove the env section from spec - {color:red}delete envs are not removed!{color}
{code}
oc edit wildflyserver eap-operator
# no pods update is triggered, operator didn't react on envs removal
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
{code}
add a new env - {color:red}pod still contains deleted envs!{color}
{code}
oc edit wildflyserver eap-operator
env:
- name: TEST_ADD
value: ADD
# wait till the eap pod is terminated, a new one is started instead
oc set env pod/eap-operator-0 --list | grep TEST
TEST_START=UPDATE
TEST_UPDATE=UPDATE
TEST_ADD=ADD
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12384) ManagedExecutorService keeping references on undeploy/deploy
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12384?page=com.atlassian.jira.plugin... ]
Eduardo Martins commented on WFLY-12384:
----------------------------------------
[~jbaesner] please remove the thread-factory attribute on the executor configuration and let me know if the issue persists. I believe there is a design issue allowing to plug a managed thread factory in the executors.
> ManagedExecutorService keeping references on undeploy/deploy
> ------------------------------------------------------------
>
> Key: WFLY-12384
> URL: https://issues.jboss.org/browse/WFLY-12384
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: Joerg Baesner
> Assignee: Eduardo Martins
> Priority: Major
> Labels: downstream_dependency
>
> Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
> {code}
> SEVERE [a.b.c.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]
> at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
> at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
> at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
> at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
> at a.b.c.MemberRepository.loadMembers(MemberRepository.java:77)
> at a.b.c.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
> at a.b.c.PollMembersTask.call(PollMembersTask.java:45)
> at a.b.c.PollMembersTask.call(PollMembersTask.java:25)
> at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12384) ManagedExecutorService keeping references on undeploy/deploy
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-12384?page=com.atlassian.jira.plugin... ]
Eduardo Martins edited comment on WFLY-12384 at 8/16/19 8:20 AM:
-----------------------------------------------------------------
[~jbaesner] please remove the thread-factory attribute on the executor configuration and let me know if the issue persists. I believe there is a design issue by allowing to plug a managed thread factory in the executors.
was (Author: emmartins):
[~jbaesner] please remove the thread-factory attribute on the executor configuration and let me know if the issue persists. I believe there is a design issue allowing to plug a managed thread factory in the executors.
> ManagedExecutorService keeping references on undeploy/deploy
> ------------------------------------------------------------
>
> Key: WFLY-12384
> URL: https://issues.jboss.org/browse/WFLY-12384
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: Joerg Baesner
> Assignee: Eduardo Martins
> Priority: Major
> Labels: downstream_dependency
>
> Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
> {code}
> SEVERE [a.b.c.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]
> at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
> at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
> at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
> at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
> at a.b.c.MemberRepository.loadMembers(MemberRepository.java:77)
> at a.b.c.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
> at a.b.c.PollMembersTask.call(PollMembersTask.java:45)
> at a.b.c.PollMembersTask.call(PollMembersTask.java:25)
> at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-174) eap73 image missing JBOSS_PRODUCT=eap in metadata.env
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-174?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFWIP-174:
-------------------------------
Description:
{code}
Expecting:
<{"AB_JOLOKIA_AUTH_OPENSHIFT"="true", "AB_JOLOKIA_HTTPS"="true", "AB_JOLOKIA_PASSWORD_RANDOM"="true", "AB_PROMETHEUS_JMX_EXPORTER_CONFIG"="/opt/jboss/container/prometheus/etc/jmx-exporter-config.yaml", "AB_PROMETHEUS_JMX_EXPORTER_PORT"="9799", "DEFAULT_ADMIN_USERNAME"="eapadmin", "HOME"="/home/jboss", "HOSTNAME"="test-pod", "HTTPS_ENABLE_HTTP2"="true", "JAVA_HOME"="/usr/lib/jvm/java-1.8.0", "JAVA_VENDOR"="openjdk", "JAVA_VERSION"="1.8.0", "JBOSS_CONTAINER_EAP_S2I_MODULE"="/opt/jboss/container/eap/s2i", "JBOSS_CONTAINER_JAVA_JVM_MODULE"="/opt/jboss/container/java/jvm", "JBOSS_CONTAINER_JAVA_PROXY_MODULE"="/opt/jboss/container/java/proxy", "JBOSS_CONTAINER_JOLOKIA_MODULE"="/opt/jboss/container/jolokia", "JBOSS_CONTAINER_MAVEN_35_MODULE"="/opt/jboss/container/maven/35/", "JBOSS_CONTAINER_MAVEN_DEFAULT_MODULE"="/opt/jboss/container/maven/default/", "JBOSS_CONTAINER_MAVEN_S2I_MODULE"="/opt/jboss/container/maven/s2i", "JBOSS_CONTAINER_OPENJDK_JDK_MODULE"="/opt/jboss/container/openjdk/jdk", "JBOSS_CONTAINER_PROMETHEUS_MODULE"="/opt/jboss/container/prometheus", "JBOSS_CONTAINER_S2I_CORE_MODULE"="/opt/jboss/container/s2i/core/", "JBOSS_CONTAINER_UTIL_LOGGING_MODULE"="/opt/jboss/container/util/logging/", "JBOSS_EAP_VERSION"="7.3.0.Beta", "JBOSS_HOME"="/opt/eap", "JBOSS_IMAGE_NAME"="jboss-eap-7-tech-preview/eap73-openshift-rhel7", "JBOSS_IMAGE_VERSION"="7.3.0.Beta", "JBOSS_MODULES_SYSTEM_PKGS"="org.jboss.logmanager,jdk.nashorn.api", "JOLOKIA_VERSION"="1.6.2", "KUBERNETES_PORT"="tcp://172.30.0.1:443", "KUBERNETES_PORT_443_TCP"="tcp://172.30.0.1:443", "KUBERNETES_PORT_443_TCP_ADDR"="172.30.0.1", "KUBERNETES_PORT_443_TCP_PORT"="443", "KUBERNETES_PORT_443_TCP_PROTO"="tcp", "KUBERNETES_PORT_53_TCP"="tcp://172.30.0.1:53", "KUBERNETES_PORT_53_TCP_ADDR"="172.30.0.1", "KUBERNETES_PORT_53_TCP_PORT"="53", "KUBERNETES_PORT_53_TCP_PROTO"="tcp", "KUBERNETES_PORT_53_UDP"="udp://172.30.0.1:53", "KUBERNETES_PORT_53_UDP_ADDR"="172.30.0.1", "KUBERNETES_PORT_53_UDP_PORT"="53", "KUBERNETES_PORT_53_UDP_PROTO"="udp", "KUBERNETES_SERVICE_HOST"="172.30.0.1", "KUBERNETES_SERVICE_PORT"="443", "KUBERNETES_SERVICE_PORT_DNS"="53", "KUBERNETES_SERVICE_PORT_DNS_TCP"="53", "KUBERNETES_SERVICE_PORT_HTTPS"="443", "LAUNCH_JBOSS_IN_BACKGROUND"="true", "MAVEN_VERSION"="3.5", "MICROPROFILE_CONFIG_DIR_ORDINAL"="500", "PATH"="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "PRODUCT_VERSION"="7.3.0.Beta", "S2I_SOURCE_DEPLOYMENTS_FILTER"="*.war *.ear *.rar *.jar", "container"="oci"}>
to contain:
<[JBOSS_EAP_VERSION=7.3.0.Beta,
JBOSS_HOME=/opt/eap,
JAVA_HOME=/usr/lib/jvm/java-1.8.0,
JAVA_VENDOR=openjdk,
MAVEN_VERSION=3.5,
JAVA_VERSION=1.8.0,
HOME=/home/jboss,
JBOSS_PRODUCT=eap,
PRODUCT_VERSION=7.3.0.Beta]>
but could not find:
<[JBOSS_PRODUCT=eap]>
{code}
When I look on last CD release there is really JBOSS_PRODUCT=eap
[1] https://access.redhat.com/containers/?tab=tech-details#/registry.access.r...
was:
Instead there is "org.jboss.product"="openjdk"
{code}
Expecting:
<{"architecture"="x86_64", "authoritative-source-url"="registry.access.redhat.com", "build-date"="2019-08-01T09:28:54.576292", "com.redhat.build-host"="cpt-1007.osbs.prod.upshift.rdu2.redhat.com", "com.redhat.component"="jboss-eap-7-eap73-openshift-rhel7-container", "com.redhat.deployments-dir"="/opt/eap/standalone/deployments", "com.redhat.license_terms"="https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI", "description"="Red Hat JBoss Enterprise Application Platform 7.3 OpenShift container image", "distribution-scope"="public", "io.cekit.version"="3.3.1", "io.fabric8.s2i.version.jolokia"="1.6.2-redhat-00002", "io.fabric8.s2i.version.maven"="3.5", "io.k8s.description"="Platform for building and running JavaEE applications on JBoss EAP 7.3", "io.k8s.display-name"="JBoss EAP 7.2", "io.openshift.expose-services"="8080:http", "io.openshift.s2i.destination"="/tmp", "io.openshift.s2i.scripts-url"="image:///usr/local/s2i", "io.openshift.tags"="builder,javaee,eap,eap7", "maintainer"="Red Hat", "name"="jboss-eap-7-tech-preview/eap73-openshift-rhel7", "org.jboss.container.deployments-dir"="/deployments", "org.jboss.product"="openjdk", "org.jboss.product.eap.version"="7.3.0.Beta", "org.jboss.product.openjdk.version"="1.8.0", "org.jboss.product.version"="7.3.0.Beta", "release"="99", "summary"="Red Hat JBoss Enterprise Application Platform 7.3 OpenShift container image", "url"="https://access.redhat.com/containers/#/registry.access.redhat.com/ubi7/im...", "vcs-ref"="c43e1c43e5f61690a4b18973ee3d42488e7167e2", "vcs-type"="git", "vendor"="Red Hat, Inc.", "version"="7.3.0.Beta"}>
to contain:
<[MapEntry[key="org.jboss.product", value="eap"]]>
but could not find:
<[MapEntry[key="org.jboss.product", value="eap"]]>
{code}
When I look on last CD release there is really `org.jboss.product eap`
[1] https://access.redhat.com/containers/?tab=tech-details#/registry.access.r...
> eap73 image missing JBOSS_PRODUCT=eap in metadata.env
> -----------------------------------------------------
>
> Key: WFWIP-174
> URL: https://issues.jboss.org/browse/WFWIP-174
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Ken Wills
> Priority: Major
>
> {code}
> Expecting:
> <{"AB_JOLOKIA_AUTH_OPENSHIFT"="true", "AB_JOLOKIA_HTTPS"="true", "AB_JOLOKIA_PASSWORD_RANDOM"="true", "AB_PROMETHEUS_JMX_EXPORTER_CONFIG"="/opt/jboss/container/prometheus/etc/jmx-exporter-config.yaml", "AB_PROMETHEUS_JMX_EXPORTER_PORT"="9799", "DEFAULT_ADMIN_USERNAME"="eapadmin", "HOME"="/home/jboss", "HOSTNAME"="test-pod", "HTTPS_ENABLE_HTTP2"="true", "JAVA_HOME"="/usr/lib/jvm/java-1.8.0", "JAVA_VENDOR"="openjdk", "JAVA_VERSION"="1.8.0", "JBOSS_CONTAINER_EAP_S2I_MODULE"="/opt/jboss/container/eap/s2i", "JBOSS_CONTAINER_JAVA_JVM_MODULE"="/opt/jboss/container/java/jvm", "JBOSS_CONTAINER_JAVA_PROXY_MODULE"="/opt/jboss/container/java/proxy", "JBOSS_CONTAINER_JOLOKIA_MODULE"="/opt/jboss/container/jolokia", "JBOSS_CONTAINER_MAVEN_35_MODULE"="/opt/jboss/container/maven/35/", "JBOSS_CONTAINER_MAVEN_DEFAULT_MODULE"="/opt/jboss/container/maven/default/", "JBOSS_CONTAINER_MAVEN_S2I_MODULE"="/opt/jboss/container/maven/s2i", "JBOSS_CONTAINER_OPENJDK_JDK_MODULE"="/opt/jboss/container/openjdk/jdk", "JBOSS_CONTAINER_PROMETHEUS_MODULE"="/opt/jboss/container/prometheus", "JBOSS_CONTAINER_S2I_CORE_MODULE"="/opt/jboss/container/s2i/core/", "JBOSS_CONTAINER_UTIL_LOGGING_MODULE"="/opt/jboss/container/util/logging/", "JBOSS_EAP_VERSION"="7.3.0.Beta", "JBOSS_HOME"="/opt/eap", "JBOSS_IMAGE_NAME"="jboss-eap-7-tech-preview/eap73-openshift-rhel7", "JBOSS_IMAGE_VERSION"="7.3.0.Beta", "JBOSS_MODULES_SYSTEM_PKGS"="org.jboss.logmanager,jdk.nashorn.api", "JOLOKIA_VERSION"="1.6.2", "KUBERNETES_PORT"="tcp://172.30.0.1:443", "KUBERNETES_PORT_443_TCP"="tcp://172.30.0.1:443", "KUBERNETES_PORT_443_TCP_ADDR"="172.30.0.1", "KUBERNETES_PORT_443_TCP_PORT"="443", "KUBERNETES_PORT_443_TCP_PROTO"="tcp", "KUBERNETES_PORT_53_TCP"="tcp://172.30.0.1:53", "KUBERNETES_PORT_53_TCP_ADDR"="172.30.0.1", "KUBERNETES_PORT_53_TCP_PORT"="53", "KUBERNETES_PORT_53_TCP_PROTO"="tcp", "KUBERNETES_PORT_53_UDP"="udp://172.30.0.1:53", "KUBERNETES_PORT_53_UDP_ADDR"="172.30.0.1", "KUBERNETES_PORT_53_UDP_PORT"="53", "KUBERNETES_PORT_53_UDP_PROTO"="udp", "KUBERNETES_SERVICE_HOST"="172.30.0.1", "KUBERNETES_SERVICE_PORT"="443", "KUBERNETES_SERVICE_PORT_DNS"="53", "KUBERNETES_SERVICE_PORT_DNS_TCP"="53", "KUBERNETES_SERVICE_PORT_HTTPS"="443", "LAUNCH_JBOSS_IN_BACKGROUND"="true", "MAVEN_VERSION"="3.5", "MICROPROFILE_CONFIG_DIR_ORDINAL"="500", "PATH"="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "PRODUCT_VERSION"="7.3.0.Beta", "S2I_SOURCE_DEPLOYMENTS_FILTER"="*.war *.ear *.rar *.jar", "container"="oci"}>
> to contain:
> <[JBOSS_EAP_VERSION=7.3.0.Beta,
> JBOSS_HOME=/opt/eap,
> JAVA_HOME=/usr/lib/jvm/java-1.8.0,
> JAVA_VENDOR=openjdk,
> MAVEN_VERSION=3.5,
> JAVA_VERSION=1.8.0,
> HOME=/home/jboss,
> JBOSS_PRODUCT=eap,
> PRODUCT_VERSION=7.3.0.Beta]>
> but could not find:
> <[JBOSS_PRODUCT=eap]>
> {code}
> When I look on last CD release there is really JBOSS_PRODUCT=eap
> [1] https://access.redhat.com/containers/?tab=tech-details#/registry.access.r...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-174) eap73 image missing JBOSS_PRODUCT=eap in metadata.env
by Martin Choma (Jira)
Martin Choma created WFWIP-174:
----------------------------------
Summary: eap73 image missing JBOSS_PRODUCT=eap in metadata.env
Key: WFWIP-174
URL: https://issues.jboss.org/browse/WFWIP-174
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Ken Wills
Instead there is "org.jboss.product"="openjdk"
{code}
Expecting:
<{"architecture"="x86_64", "authoritative-source-url"="registry.access.redhat.com", "build-date"="2019-08-01T09:28:54.576292", "com.redhat.build-host"="cpt-1007.osbs.prod.upshift.rdu2.redhat.com", "com.redhat.component"="jboss-eap-7-eap73-openshift-rhel7-container", "com.redhat.deployments-dir"="/opt/eap/standalone/deployments", "com.redhat.license_terms"="https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI", "description"="Red Hat JBoss Enterprise Application Platform 7.3 OpenShift container image", "distribution-scope"="public", "io.cekit.version"="3.3.1", "io.fabric8.s2i.version.jolokia"="1.6.2-redhat-00002", "io.fabric8.s2i.version.maven"="3.5", "io.k8s.description"="Platform for building and running JavaEE applications on JBoss EAP 7.3", "io.k8s.display-name"="JBoss EAP 7.2", "io.openshift.expose-services"="8080:http", "io.openshift.s2i.destination"="/tmp", "io.openshift.s2i.scripts-url"="image:///usr/local/s2i", "io.openshift.tags"="builder,javaee,eap,eap7", "maintainer"="Red Hat", "name"="jboss-eap-7-tech-preview/eap73-openshift-rhel7", "org.jboss.container.deployments-dir"="/deployments", "org.jboss.product"="openjdk", "org.jboss.product.eap.version"="7.3.0.Beta", "org.jboss.product.openjdk.version"="1.8.0", "org.jboss.product.version"="7.3.0.Beta", "release"="99", "summary"="Red Hat JBoss Enterprise Application Platform 7.3 OpenShift container image", "url"="https://access.redhat.com/containers/#/registry.access.redhat.com/ubi7/im...", "vcs-ref"="c43e1c43e5f61690a4b18973ee3d42488e7167e2", "vcs-type"="git", "vendor"="Red Hat, Inc.", "version"="7.3.0.Beta"}>
to contain:
<[MapEntry[key="org.jboss.product", value="eap"]]>
but could not find:
<[MapEntry[key="org.jboss.product", value="eap"]]>
{code}
When I look on last CD release there is really `org.jboss.product eap`
[1] https://access.redhat.com/containers/?tab=tech-details#/registry.access.r...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-173) eap73 image missing org.jboss.product=eap in metadata.labels
by Martin Choma (Jira)
Martin Choma created WFWIP-173:
----------------------------------
Summary: eap73 image missing org.jboss.product=eap in metadata.labels
Key: WFWIP-173
URL: https://issues.jboss.org/browse/WFWIP-173
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Ken Wills
Instead there is "org.jboss.product"="openjdk"
{code}
Expecting:
<{"architecture"="x86_64", "authoritative-source-url"="registry.access.redhat.com", "build-date"="2019-08-01T09:28:54.576292", "com.redhat.build-host"="cpt-1007.osbs.prod.upshift.rdu2.redhat.com", "com.redhat.component"="jboss-eap-7-eap73-openshift-rhel7-container", "com.redhat.deployments-dir"="/opt/eap/standalone/deployments", "com.redhat.license_terms"="https://www.redhat.com/en/about/red-hat-end-user-license-agreements#UBI", "description"="Red Hat JBoss Enterprise Application Platform 7.3 OpenShift container image", "distribution-scope"="public", "io.cekit.version"="3.3.1", "io.fabric8.s2i.version.jolokia"="1.6.2-redhat-00002", "io.fabric8.s2i.version.maven"="3.5", "io.k8s.description"="Platform for building and running JavaEE applications on JBoss EAP 7.3", "io.k8s.display-name"="JBoss EAP 7.2", "io.openshift.expose-services"="8080:http", "io.openshift.s2i.destination"="/tmp", "io.openshift.s2i.scripts-url"="image:///usr/local/s2i", "io.openshift.tags"="builder,javaee,eap,eap7", "maintainer"="Red Hat", "name"="jboss-eap-7-tech-preview/eap73-openshift-rhel7", "org.jboss.container.deployments-dir"="/deployments", "org.jboss.product"="openjdk", "org.jboss.product.eap.version"="7.3.0.Beta", "org.jboss.product.openjdk.version"="1.8.0", "org.jboss.product.version"="7.3.0.Beta", "release"="99", "summary"="Red Hat JBoss Enterprise Application Platform 7.3 OpenShift container image", "url"="https://access.redhat.com/containers/#/registry.access.redhat.com/ubi7/im...", "vcs-ref"="c43e1c43e5f61690a4b18973ee3d42488e7167e2", "vcs-type"="git", "vendor"="Red Hat, Inc.", "version"="7.3.0.Beta"}>
to contain:
<[MapEntry[key="org.jboss.product", value="eap"]]>
but could not find:
<[MapEntry[key="org.jboss.product", value="eap"]]>
{code}
When I look on last CD release there is really `org.jboss.product eap`
[1] https://access.redhat.com/containers/?tab=tech-details#/registry.access.r...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months