[JBoss JIRA] (WFWIP-221) jps can't see server process in Openshift
by Jan Blizňák (Jira)
Jan Blizňák created WFWIP-221:
---------------------------------
Summary: 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
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 can find java process in /proc/*/cmdline (image has no `ps` utility).
This happens only in Openshift environment and 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.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-12613) Exclude IBM J9 JVM from Byteman-based test cases
by Richard Achmatowicz (Jira)
[ https://issues.jboss.org/browse/WFLY-12613?page=com.atlassian.jira.plugin... ]
Richard Achmatowicz reassigned WFLY-12613:
------------------------------------------
Assignee: Richard Achmatowicz
> Exclude IBM J9 JVM from Byteman-based test cases
> ------------------------------------------------
>
> Key: WFLY-12613
> URL: https://issues.jboss.org/browse/WFLY-12613
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 18.0.0.Final
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 18.0.0.Final
>
>
> The test case org.jboss.as.test.clustering.cluster.ejb.remote.byteman.LastNodeToLeaveRemoteEJBTestCase uses Byteman to check a condition for validating whether the test passes or fails. The component arquillian-extension-byteman is used to allow the use of Byteman annotations within the Arquillian test case.
> There is a problem with running Byteman-based test cases against the IBM J9 Java runtime:
> {noformat}
> [ERROR] org.jboss.as.test.clustering.cluster.ejb.remote.byteman.LastNodeToLeaveRemoteEJBTestCase Time elapsed: 1.202 s <<< ERROR!
> java.lang.RuntimeException: Could not install byteman agent
> at org.jboss.arquillian.extension.byteman.impl.client.AgentInstaller.install(AgentInstaller.java:98)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:507)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:71)
> at org.jboss.arquillian.junit.AdaptorManager.initializeAdaptor(AdaptorManager.java:23)
> at org.jboss.arquillian.junit.AdaptorManagerWithNotifier.initializeAdaptor(AdaptorManagerWithNotifier.java:19)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:109)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> Caused by: com.sun.tools.attach.AgentInitializationException: ATTACH_ERR AgentInitializationException102
> at ibm.tools.attach.J9VirtualMachine.loadAgent(J9VirtualMachine.java:66)
> at org.jboss.arquillian.extension.byteman.impl.client.AgentInstaller.install(AgentInstaller.java:91)
> ... 28 more
> {noformat}
>
> {noformat}
> [nrla@localhost wildfly-git-repo]$ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr2-20151023_01(SR2))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20151019_272764 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR2_20151019_2144_B272764
> JIT - tr.r14.java_20151006_102517.04
> GC - R28_Java8_SR2_20151019_2144_B272764_CMPRSS
> J9CL - 20151019_272764)
> JCL - 20151022_01 based on Oracle jdk8u65-b17
> {noformat}
> Until this JVM bug can be fixed, we need to exclude executions of this test against the IBM J9 JVM.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-187:
-----------------------------------
I'm not sure there is an issue here and it seems to work as expected for PVC.
https://kubernetes.io/docs/tasks/run-application/delete-stateful-set/#per...:
Deleting the Pods in a StatefulSet will not delete the associated volumes. This is to ensure that you have the chance to copy data off the volume before deleting it. Deleting the PVC after the pods have left the terminating state might trigger deletion of the backing Persistent Volumes depending on the storage class and reclaim policy. You should never assume ability to access a volume after claim deletion.
> Changes to PVC are not reflected in Operator
> --------------------------------------------
>
> Key: WFWIP-187
> URL: https://issues.jboss.org/browse/WFWIP-187
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: operator
>
> Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-187:
-----------------------------------
I'm using the metadata.generation to ensure that underlying Kubernetes resources (like StatefulSet) are up to date with the latest WildFlyServer generation.
The new annotation on StatefulSet tracks the *WildFlyServer* generation so that in the reconcile loop, if we notice that the statefulset is out of date, we update/delete it so that it complies to the latest WildFlyServer spec.
> Changes to PVC are not reflected in Operator
> --------------------------------------------
>
> Key: WFWIP-187
> URL: https://issues.jboss.org/browse/WFWIP-187
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: operator
>
> Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-12624) Return hostname instead of IP address when generating default client mapping
by Richard Achmatowicz (Jira)
Richard Achmatowicz created WFLY-12624:
------------------------------------------
Summary: Return hostname instead of IP address when generating default client mapping
Key: WFLY-12624
URL: https://issues.jboss.org/browse/WFLY-12624
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Beta1
Environment: An EJB client application interacting with a cluster of Wildfly server nodes
Reporter: Richard Achmatowicz
Assignee: Paul Ferraro
When an EJB client application interacts with a clustered Wildfly deployment, it receives topology updates from cluster nodes describing the membership of the cluster.
For each node in the cluster, a set of one or more client mappings is provided to indicate how the client may connect to the node, if it hasn't already. If the node is connected to a single network, there will be one client mapping; if the node is multi-homed and connected to two networks, there will be two client mappings, etc. Client mappings specify three things: a CIDR representation of the network the client may be on, a destination hostname or IP address and a destination port.
Client mappings may be generated by default (if none are provided in the server profile) or may be specified by the user via client mappings defined in the socket binding of the Remoting connector. For example:
{noformat}
<socket-binding name="remoting" port="1099">
<client-mapping source-network="135.121.1.29/16" destination-address="135.121.1.29" destination-port="1099"/>
</socketbinding>
{noformat}
When the client mapping information is received by the EJB client application, it is added to the discovered node registry (DNR) in the Discovery component of the EJB client. The DNR represents all known information about nodes with which the client can interact which was received from nodes in one or more clusters.
When an invocation is attempted, the Discovery component uses this information to generate a set of ServiceURLs which represent candidate targets (i.e. servers containing the deployment and module the client is invoking on) for the invocation. These service URLs use "an algorithm" to take the information in the DNR and convert that information to a corresponding set of ServiceURLs. The Discovery component will then select one such ServiceURL and return this as the target for the invocation.
The problem is that Discovery obtains its node information from various sources: client mappings associated with cluster nodes, as described above, as well as Remoting endpoints associated with established connections to nodes. These pieces of information describe at a minimum a host and a port.
The problem is that "the algorithm" used in Discovery to compute the set of ServiceURLs treats hostnames and IP addresses as simple strings. So "localhost" and "127.0.0.1" are treated as different hosts, even though they refer to the same host. This results in an incomplete/incorrect set of ServiceURLs being generated which in turn leads to incorrect Discovery failures.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-211) emptyDir.sizeLimit not propagated to Pod Spec
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-211?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-211:
-----------------------------------
[~mchoma] the issue is *not* present when I test on Kubernetes with WildFly Operator.
The issue *is* present on OpenShift with EAP Operator.
I think this is an OpenShift issue that's not related to the EAP Operator.
If I create a simple pod with a memory limit of 5Mi, it seems it is not taken into account by OpenShift:
{code}
$ cat emptydir-test.yaml
apiVersion: v1
kind: Pod
metadata:
name: emptydir-test-pod
spec:
containers:
- image: alpine
imagePullPolicy: IfNotPresent
name: myvolumes-container
command: [ 'sh', '-c', 'echo The Bench Container 1 is Running ; sleep 3600']
volumeMounts:
- mountPath: /demo
name: demo-volume
volumes:
- name: demo-volume
emptyDir:
medium: Memory
sizeLimit: 5Mi
$ oc apply -f emptydir-test.yaml
pod/emptydir-test-pod created
$ oc get -o yaml pod emptydir-test-pod
...
volumes:
- emptyDir:
medium: Memory
name: demo-volume
- name: default-token-2qwn8
secret:
defaultMode: 420
secretName: default-token-2qwn8
...
{code}
I suppose OpenShift does not accept limit for memory emptyDir (or has a default one) but I could not find a definitive answer from the doc.
I'd suggest we close this issue as this is not something that is related to the operator. Do you agree?
> emptyDir.sizeLimit not propagated to Pod Spec
> ---------------------------------------------
>
> Key: WFWIP-211
> URL: https://issues.jboss.org/browse/WFWIP-211
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: operator
>
> # {code:yaml}
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> name: operator-empty-dir
> namespace: mchoma
> spec:
> applicationImage: 'registry.access.redhat.com/jboss-eap-7/eap72-openshift:1.1'
> size: 1
> storage:
> emptyDir:
> medium: Memory
> sizeLimit: 1Mi
> {code}
> # wait until pod are started and look into pod yaml definition "1 Mi" is not there
> {code:yaml}
> ...
> serviceAccount: default
> serviceAccountName: default
> subdomain: operator-empty-dir-headless
> terminationGracePeriodSeconds: 30
> volumes:
> - emptyDir:
> medium: Memory
> name: operator-empty-dir-volume
> - name: default-token-j2grg
> secret:
> defaultMode: 420
> secretName: default-token-j2grg
> status:
> conditions:
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton resolved DROOLS-4481.
---------------------------------------
Resolution: Done
[~karreiro] [~tirelli] I updated the click-thru based on team feedback. The current mockup includes the suggested enhancements (inline alerts and import as collapsed), so I'm marking this as Resolved. Thanks!
> [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4481
> URL: https://issues.jboss.org/browse/DROOLS-4481
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 2019-08-26 17.48.30.gif, 2_introtext.png, Screen Shot 2019-08-26 at 18.11.01.png
>
>
> *Requirements*
> It should be possible to generate data types from imported data models (java classes).
> * As a user I want to be able to use data type definitions that are structured similar to Java data object models (classes) that I have defined externally.
> * As I user I want to be able to edit and update data objects that have been converted to data types, so that I can manually update the definitions.
> Import/convert data objects:
> * 5 levels deep can “introspect” and convert data model, beyond that the data type would be “any.”
> * Import (convert) only within the Data Type tab, this is not a feature of the Import/Include function as import DO’s is not supported in the DMN spec. --
> *Current scenario*
> Currently, users can create Data Objects on Business Central. See:
> !2019-08-26 17.48.30.gif|width=600!
> However users cannot re-use Data Objects as Data Types.
> ---
> *Description*
> Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one:
> !Screen Shot 2019-08-26 at 18.11.01.png|width=600!
> ---
> *Questions to clarify at requirement level*
> 1) Some DOs can be quite complex and some fields can be impossible to guess.
> - Person
> -- name (Some strange type)
> -- age (Integer)
> What should we do? Import name as "Any"? Remove the name field? Or block the Person type?
> 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4481:
--------------------------------------
Attachment: 2_introtext.png
> [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4481
> URL: https://issues.jboss.org/browse/DROOLS-4481
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 2019-08-26 17.48.30.gif, 2_introtext.png, Screen Shot 2019-08-26 at 18.11.01.png
>
>
> *Requirements*
> It should be possible to generate data types from imported data models (java classes).
> * As a user I want to be able to use data type definitions that are structured similar to Java data object models (classes) that I have defined externally.
> * As I user I want to be able to edit and update data objects that have been converted to data types, so that I can manually update the definitions.
> Import/convert data objects:
> * 5 levels deep can “introspect” and convert data model, beyond that the data type would be “any.”
> * Import (convert) only within the Data Type tab, this is not a feature of the Import/Include function as import DO’s is not supported in the DMN spec. --
> *Current scenario*
> Currently, users can create Data Objects on Business Central. See:
> !2019-08-26 17.48.30.gif|width=600!
> However users cannot re-use Data Objects as Data Types.
> ---
> *Description*
> Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one:
> !Screen Shot 2019-08-26 at 18.11.01.png|width=600!
> ---
> *Questions to clarify at requirement level*
> 1) Some DOs can be quite complex and some fields can be impossible to guess.
> - Person
> -- name (Some strange type)
> -- age (Integer)
> What should we do? Import name as "Any"? Remove the name field? Or block the Person type?
> 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-4481:
-------------------------------------------
[~karreiro] I updated the click-thru with:
* Inline alerts: Please note: the examples in my mocks are just roughs to show the general concept. The exact styling should match PatternFly 3 recommendations, to be consistent in the overall UI. See: https://www.patternfly.org/v3/pattern-library/communication/inline-notifi...
* Importing the DO in its collapsed state, and a screen to show the expanded view.
* It's not visible in the click-thru, but here's a version with inline help text at the top of the dialog. In my mockups I replaced the help text with the inline error. I think that might be okay, but if you think it's best to move the whole area down to support the alert that would be good. Here's a mockup with the intro text, though we might want [~stetson.robinson] to review it.
!2_introtext.png|thumbnail!
> [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX
> ------------------------------------------------------------------------------
>
> Key: DROOLS-4481
> URL: https://issues.jboss.org/browse/DROOLS-4481
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: 2019-08-26 17.48.30.gif, Screen Shot 2019-08-26 at 18.11.01.png
>
>
> *Requirements*
> It should be possible to generate data types from imported data models (java classes).
> * As a user I want to be able to use data type definitions that are structured similar to Java data object models (classes) that I have defined externally.
> * As I user I want to be able to edit and update data objects that have been converted to data types, so that I can manually update the definitions.
> Import/convert data objects:
> * 5 levels deep can “introspect” and convert data model, beyond that the data type would be “any.”
> * Import (convert) only within the Data Type tab, this is not a feature of the Import/Include function as import DO’s is not supported in the DMN spec. --
> *Current scenario*
> Currently, users can create Data Objects on Business Central. See:
> !2019-08-26 17.48.30.gif|width=600!
> However users cannot re-use Data Objects as Data Types.
> ---
> *Description*
> Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one:
> !Screen Shot 2019-08-26 at 18.11.01.png|width=600!
> ---
> *Questions to clarify at requirement level*
> 1) Some DOs can be quite complex and some fields can be impossible to guess.
> - Person
> -- name (Some strange type)
> -- age (Integer)
> What should we do? Import name as "Any"? Remove the name field? Or block the Person type?
> 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months