[JBoss JIRA] (WFWIP-200) Runtime changes to sessionAffinity are not reflected in underlying objects
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-200?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFWIP-200:
------------------------------------
I can confirm I dont see issue anymore with latest eap operator jboss-eap-7-tech-preview-eap-operator:jb-eap-7.3-operator-rhel8-containers-candidate-66988-20191001135536
> Runtime changes to sessionAffinity are not reflected in underlying objects
> --------------------------------------------------------------------------
>
> Key: WFWIP-200
> URL: https://issues.jboss.org/browse/WFWIP-200
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: operator
>
> Any changes (adding, removing or updating) made to sessionAffinity attribute after WildFlyServer CR was created are not reflected in underlying Service kubernetes object.
> Reproducer:
> # create CR
> {code}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> generation: 1
> name: eap-cd
> namespace: default
> spec:
> applicationImage: >-
> brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
> size: 1
> {code}
> # Edit CR with sessionAffinity: true
> {code}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> generation: 1
> name: eap-cd
> namespace: default
> spec:
> applicationImage: >-
> brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
> size: 1
> sessionAffinity: true
> {code}
> # Service object eap-cd-loadbalancer is not updated
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-200) Runtime changes to sessionAffinity are not reflected in underlying objects
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-200?page=com.atlassian.jira.plugin.... ]
Martin Choma closed WFWIP-200.
------------------------------
> Runtime changes to sessionAffinity are not reflected in underlying objects
> --------------------------------------------------------------------------
>
> Key: WFWIP-200
> URL: https://issues.jboss.org/browse/WFWIP-200
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: operator
>
> Any changes (adding, removing or updating) made to sessionAffinity attribute after WildFlyServer CR was created are not reflected in underlying Service kubernetes object.
> Reproducer:
> # create CR
> {code}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> generation: 1
> name: eap-cd
> namespace: default
> spec:
> applicationImage: >-
> brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
> size: 1
> {code}
> # Edit CR with sessionAffinity: true
> {code}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> generation: 1
> name: eap-cd
> namespace: default
> spec:
> applicationImage: >-
> brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
> size: 1
> sessionAffinity: true
> {code}
> # Service object eap-cd-loadbalancer is not updated
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift
by Jean Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ]
Jean Francois Denise edited comment on WFWIP-221 at 10/1/19 12:52 PM:
----------------------------------------------------------------------
[~jbliznak] It doesn't occur when running an image built with s2i, you observe the issue with a run of the builder image. Right?
was (Author: jdenise):
[~jbliznak] It doesn't occur when running an image built with s2i, you observe the issue with a run of the builder image.
> jps can't see server process in Openshift
> -----------------------------------------
>
> Key: WFWIP-221
> URL: https://issues.jboss.org/browse/WFWIP-221
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jean Francois Denise
> Priority: Critical
>
> This is somewhat curious issue.
> When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility).
> This happens only in Openshift environment and it is a regression to what was working with latest published CD image.
> Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process.
> {code:java}
> # this works fine
> docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh
> sh-4.4$ /opt/eap/bin/openshift-launch.sh &
> sh-4.4$ jps -l
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift
by Jean Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ]
Jean Francois Denise commented on WFWIP-221:
--------------------------------------------
[~jbliznak] It doesn't occur when running an image built with s2i, you observe the issue with a run of the builder image.
> jps can't see server process in Openshift
> -----------------------------------------
>
> Key: WFWIP-221
> URL: https://issues.jboss.org/browse/WFWIP-221
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jean Francois Denise
> Priority: Critical
>
> This is somewhat curious issue.
> When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility).
> This happens only in Openshift environment and it is a regression to what was working with latest published CD image.
> Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process.
> {code:java}
> # this works fine
> docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh
> sh-4.4$ /opt/eap/bin/openshift-launch.sh &
> sh-4.4$ jps -l
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift
by Jean Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ]
Jean Francois Denise commented on WFWIP-221:
--------------------------------------------
[~jbliznak], did you try to delete /tmp/hsperfdata_jboss (if possible) and start the pod.
> jps can't see server process in Openshift
> -----------------------------------------
>
> Key: WFWIP-221
> URL: https://issues.jboss.org/browse/WFWIP-221
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jean Francois Denise
> Priority: Critical
>
> This is somewhat curious issue.
> When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility).
> This happens only in Openshift environment and it is a regression to what was working with latest published CD image.
> Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process.
> {code:java}
> # this works fine
> docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh
> sh-4.4$ /opt/eap/bin/openshift-launch.sh &
> sh-4.4$ jps -l
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFWIP-221?page=com.atlassian.jira.plugin.... ]
Jan Blizňák edited comment on WFWIP-221 at 10/1/19 11:58 AM:
-------------------------------------------------------------
Additional info - jps can't see even itself if that is of any help.
I googled this: https://stackoverflow.com/questions/3805376/jps-returns-no-output-even-wh...
This led me to test the content of /tmp and indeed there is difference:
released CD image 17.0.5:
{code:java}
$ id
uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000
$ ls -lna /tmp
total 4
drwxrwxrwt. 1 0 0 30 Oct 1 15:56 .
drwxr-xr-x. 1 0 0 58 Oct 1 15:56 ..
drwxr-xr-x. 2 1000290000 0 17 Oct 1 15:56 hsperfdata_jboss
drwxr-xr-x. 2 0 0 16 Sep 6 14:42 hsperfdata_root
-rwx------. 1 0 0 1379 Jul 23 16:18 ks-script-4c1pmxe1
{code}
eap-cd-openshift-rhel8:18.0-EAP7-1216:
{code:java}
$ id
uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000
$ $ ls -lna /tmp
total 12
drwxrwxrwt. 1 0 0 83 Oct 1 15:36 .
drwxr-xr-x. 1 0 0 58 Oct 1 15:35 ..
-rw-r--r--. 1 1000290000 0 93 Oct 1 15:35 cli-script-property-1569944155.cli
-rw-r--r--. 1 1000290000 0 410 Oct 1 15:35 ds-timer-service-data-store
drwxr-xr-x. 2 185 0 6 Sep 30 17:01 hsperfdata_jboss
drwxr-xr-x. 2 0 0 16 Sep 30 16:59 hsperfdata_root
-rwx------. 1 0 0 1379 Sep 16 12:25 ks-script-mr2oi4id
{code}
See the difference at hsperfdata_jboss user, maybe that can help. I don't know why jboss user has different.
was (Author: jbliznak):
Additional info - jps can't see even itself if that is of any help.
I googled this: https://stackoverflow.com/questions/3805376/jps-returns-no-output-even-wh...
This led me to test the content of /tmp and indeed there is difference:
released CD image 17.0.5:
{code:java}
$ id
uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000
$ ls -l /tmp
total 4
drwxr-xr-x. 2 jboss root 17 Oct 1 15:23 hsperfdata_jboss
drwxr-xr-x. 2 root root 16 Sep 6 14:42 hsperfdata_root
-rwx------. 1 root root 1379 Jul 23 16:18 ks-script-4c1pmxe1
{code}
eap-cd-openshift-rhel8:18.0-EAP7-1216:
{code:java}
$ id
uid=1000290000(jboss) gid=0(root) groups=0(root),185(jboss),1000290000
$ ls -l /tmp
total 12
-rw-r--r--. 1 jboss root 93 Oct 1 15:26 cli-script-property-1569943601.cli
-rw-r--r--. 1 jboss root 410 Oct 1 15:26 ds-timer-service-data-store
drwxr-xr-x. 2 185 root 6 Sep 30 17:01 hsperfdata_jboss
drwxr-xr-x. 2 root root 16 Sep 30 16:59 hsperfdata_root
-rwx------. 1 root root 1379 Sep 16 12:25 ks-script-mr2oi4id
{code}
See the difference at hsperfdata_jboss user, maybe that can help. I don't know why jboss user has different.
> jps can't see server process in Openshift
> -----------------------------------------
>
> Key: WFWIP-221
> URL: https://issues.jboss.org/browse/WFWIP-221
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jean Francois Denise
> Priority: Critical
>
> This is somewhat curious issue.
> When pod of app image is deployed (server is started) and switch to terminal in Openshift GUI, doing `jps -l` does nothing although I can see in logs that server is up and I can find java process in /proc/*/cmdline (image has no `ps` utility).
> This happens only in Openshift environment and it is a regression to what was working with latest published CD image.
> Funnily, when I try to run the image in docker and start the server by /opt/eap/bin/openshift-launch.sh, then jps can see the java process.
> {code:java}
> # this works fine
> docker run -it docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... sh
> sh-4.4$ /opt/eap/bin/openshift-launch.sh &
> sh-4.4$ jps -l
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years