[JBoss JIRA] (WFWIP-163) WildFlyServerStatus is not present in operator description
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFWIP-163?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFWIP-163:
---------------------------------
Environment:
openshift v3.11.82
operator image: quay.io/wildfly/wildfly-operator:0.2.0
runtime image: quay.io/wildfly/wildfly-centos7:17.0
application image: quay.io/wildfly/wildfly-operator:0.2.0
was:
openshift v3.11.82
operator image: quay.io/wildfly/wildfly-operator:0.2.0
runtime image: quay.io/wildfly/wildfly-centos7:17.0
application image:
> WildFlyServerStatus is not present in operator description
> -----------------------------------------------------------
>
> Key: WFWIP-163
> URL: https://issues.jboss.org/browse/WFWIP-163
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: openshift v3.11.82
> operator image: quay.io/wildfly/wildfly-operator:0.2.0
> runtime image: quay.io/wildfly/wildfly-centos7:17.0
> application image: quay.io/wildfly/wildfly-operator:0.2.0
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> According to the [operator api documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...], the deployment pods status should be pard of operator description, but I failed to find such on OCP.
> Install the wildfly operator on OCP as described by [wildfly-operator - openshift|https://github.com/wildfly/wildfly-operator#openshift] section.
> *steps to reproduce*
> {noformat}
> $ cat << EOF > simple-jaxrs-wildfly.yaml
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> name: simple-jaxrs-wildfly
> spec:
> applicationImage: "pkremens/simple-jaxrs-wildfly"
> size: 2
> EOF
> $ oc apply -f simple-jaxrs-wildfly.yaml
> $ oc expose service/simple-jaxrs-wildfly-loadbalancer
> # verify that application is accessible
> $ ROUTE=$(oc get route.route.openshift.io/simple-jaxrs-wildfly-loadbalancer --template='{{ .spec.host }}')
> $ curl $ROUTE/ping
> pong
> $ oc describe wildflyserver simple-jaxrs-wildfly
> Name: simple-jaxrs-wildfly
> Namespace: myproject
> Labels: <none>
> Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"wildfly.org/v1alpha1","kind":"WildFlyServer","metadata":{"annotations":{},"name":"simple-jaxrs-wildfly","namespace":"myproject"},"spec":...
> API Version: wildfly.org/v1alpha1
> Kind: WildFlyServer
> Metadata:
> Creation Timestamp: 2019-07-02T13:11:58Z
> Generation: 1
> Resource Version: 4318
> Self Link: /apis/wildfly.org/v1alpha1/namespaces/myproject/wildflyservers/simple-jaxrs-wildfly
> UID: f8eb76bf-9cca-11e9-b8ee-52540043aed8
> Spec:
> Application Image: pkremens/simple-jaxrs-wildfly
> Size: 2
> Events: <none>
> {noformat}
> Operator status is not part of the object.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFWIP-163) WildFlyServerStatus is not present in operator description
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFWIP-163?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFWIP-163:
---------------------------------
Environment:
openshift v3.11.82
operator image: quay.io/wildfly/wildfly-operator:0.2.0
runtime image: quay.io/wildfly/wildfly-centos7:17.0
application image: pkremens/simple-jaxrs-wildfly
was:
openshift v3.11.82
operator image: quay.io/wildfly/wildfly-operator:0.2.0
runtime image: quay.io/wildfly/wildfly-centos7:17.0
application image: quay.io/wildfly/wildfly-operator:0.2.0
> WildFlyServerStatus is not present in operator description
> -----------------------------------------------------------
>
> Key: WFWIP-163
> URL: https://issues.jboss.org/browse/WFWIP-163
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: openshift v3.11.82
> operator image: quay.io/wildfly/wildfly-operator:0.2.0
> runtime image: quay.io/wildfly/wildfly-centos7:17.0
> application image: pkremens/simple-jaxrs-wildfly
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> According to the [operator api documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...], the deployment pods status should be pard of operator description, but I failed to find such on OCP.
> Install the wildfly operator on OCP as described by [wildfly-operator - openshift|https://github.com/wildfly/wildfly-operator#openshift] section.
> *steps to reproduce*
> {noformat}
> $ cat << EOF > simple-jaxrs-wildfly.yaml
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> name: simple-jaxrs-wildfly
> spec:
> applicationImage: "pkremens/simple-jaxrs-wildfly"
> size: 2
> EOF
> $ oc apply -f simple-jaxrs-wildfly.yaml
> $ oc expose service/simple-jaxrs-wildfly-loadbalancer
> # verify that application is accessible
> $ ROUTE=$(oc get route.route.openshift.io/simple-jaxrs-wildfly-loadbalancer --template='{{ .spec.host }}')
> $ curl $ROUTE/ping
> pong
> $ oc describe wildflyserver simple-jaxrs-wildfly
> Name: simple-jaxrs-wildfly
> Namespace: myproject
> Labels: <none>
> Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"wildfly.org/v1alpha1","kind":"WildFlyServer","metadata":{"annotations":{},"name":"simple-jaxrs-wildfly","namespace":"myproject"},"spec":...
> API Version: wildfly.org/v1alpha1
> Kind: WildFlyServer
> Metadata:
> Creation Timestamp: 2019-07-02T13:11:58Z
> Generation: 1
> Resource Version: 4318
> Self Link: /apis/wildfly.org/v1alpha1/namespaces/myproject/wildflyservers/simple-jaxrs-wildfly
> UID: f8eb76bf-9cca-11e9-b8ee-52540043aed8
> Spec:
> Application Image: pkremens/simple-jaxrs-wildfly
> Size: 2
> Events: <none>
> {noformat}
> Operator status is not part of the object.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFWIP-163) WildFlyServerStatus is not present in operator description
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFWIP-163?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFWIP-163:
---------------------------------
Environment:
openshift v3.11.82
operator image: quay.io/wildfly/wildfly-operator:0.2.0
quay.io/wildfly/wildfly-centos7:17.0
was:
openshift v3.11.82
operator 0.2.0
quay.io/wildfly/wildfly-centos7:17.0
> WildFlyServerStatus is not present in operator description
> -----------------------------------------------------------
>
> Key: WFWIP-163
> URL: https://issues.jboss.org/browse/WFWIP-163
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: openshift v3.11.82
> operator image: quay.io/wildfly/wildfly-operator:0.2.0
> quay.io/wildfly/wildfly-centos7:17.0
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> According to the [operator api documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...], the deployment pods status should be pard of operator description, but I failed to find such on OCP.
> Install the wildfly operator on OCP as described by [wildfly-operator - openshift|https://github.com/wildfly/wildfly-operator#openshift] section.
> *steps to reproduce*
> {noformat}
> $ cat << EOF > simple-jaxrs-wildfly.yaml
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> name: simple-jaxrs-wildfly
> spec:
> applicationImage: "pkremens/simple-jaxrs-wildfly"
> size: 2
> EOF
> $ oc apply -f simple-jaxrs-wildfly.yaml
> $ oc expose service/simple-jaxrs-wildfly-loadbalancer
> # verify that application is accessible
> $ ROUTE=$(oc get route.route.openshift.io/simple-jaxrs-wildfly-loadbalancer --template='{{ .spec.host }}')
> $ curl $ROUTE/ping
> pong
> $ oc describe wildflyserver simple-jaxrs-wildfly
> Name: simple-jaxrs-wildfly
> Namespace: myproject
> Labels: <none>
> Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"wildfly.org/v1alpha1","kind":"WildFlyServer","metadata":{"annotations":{},"name":"simple-jaxrs-wildfly","namespace":"myproject"},"spec":...
> API Version: wildfly.org/v1alpha1
> Kind: WildFlyServer
> Metadata:
> Creation Timestamp: 2019-07-02T13:11:58Z
> Generation: 1
> Resource Version: 4318
> Self Link: /apis/wildfly.org/v1alpha1/namespaces/myproject/wildflyservers/simple-jaxrs-wildfly
> UID: f8eb76bf-9cca-11e9-b8ee-52540043aed8
> Spec:
> Application Image: pkremens/simple-jaxrs-wildfly
> Size: 2
> Events: <none>
> {noformat}
> Operator status is not part of the object.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFWIP-163) WildFlyServerStatus is not present in operator description
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-163?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-163:
-----------------------------------
Thanks for the report, this is a regression dues to a change in operator-sdk.
I have opened an issue in https://github.com/wildfly/wildfly-operator/issues/30 and will fix it.
> WildFlyServerStatus is not present in operator description
> -----------------------------------------------------------
>
> Key: WFWIP-163
> URL: https://issues.jboss.org/browse/WFWIP-163
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: openshift v3.11.82
> operator 0.2.0
> quay.io/wildfly/wildfly-centos7:17.0
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> According to the [operator api documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...], the deployment pods status should be pard of operator description, but I failed to find such on OCP.
> Install the wildfly operator on OCP as described by [wildfly-operator - openshift|https://github.com/wildfly/wildfly-operator#openshift] section.
> *steps to reproduce*
> {noformat}
> $ cat << EOF > simple-jaxrs-wildfly.yaml
> apiVersion: wildfly.org/v1alpha1
> kind: WildFlyServer
> metadata:
> name: simple-jaxrs-wildfly
> spec:
> applicationImage: "pkremens/simple-jaxrs-wildfly"
> size: 2
> EOF
> $ oc apply -f simple-jaxrs-wildfly.yaml
> $ oc expose service/simple-jaxrs-wildfly-loadbalancer
> # verify that application is accessible
> $ ROUTE=$(oc get route.route.openshift.io/simple-jaxrs-wildfly-loadbalancer --template='{{ .spec.host }}')
> $ curl $ROUTE/ping
> pong
> $ oc describe wildflyserver simple-jaxrs-wildfly
> Name: simple-jaxrs-wildfly
> Namespace: myproject
> Labels: <none>
> Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"wildfly.org/v1alpha1","kind":"WildFlyServer","metadata":{"annotations":{},"name":"simple-jaxrs-wildfly","namespace":"myproject"},"spec":...
> API Version: wildfly.org/v1alpha1
> Kind: WildFlyServer
> Metadata:
> Creation Timestamp: 2019-07-02T13:11:58Z
> Generation: 1
> Resource Version: 4318
> Self Link: /apis/wildfly.org/v1alpha1/namespaces/myproject/wildflyservers/simple-jaxrs-wildfly
> UID: f8eb76bf-9cca-11e9-b8ee-52540043aed8
> Spec:
> Application Image: pkremens/simple-jaxrs-wildfly
> Size: 2
> Events: <none>
> {noformat}
> Operator status is not part of the object.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4200) Design and implement new DataSources API
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4200?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-4200:
-------------------------------------
Partially implemented by https://github.com/kiegroup/kogito-runtimes/commit/c2415cbaaf3c2ebc32911a...
It is still outstanding the implementation of FH in the DataStore (cannot be the FH returned by the session because 1. the store couldn't be yet linked to any session and 2. the store could be used by multiple units/sessions)
> Design and implement new DataSources API
> ----------------------------------------
>
> Key: DROOLS-4200
> URL: https://issues.jboss.org/browse/DROOLS-4200
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Priority: Major
>
> We need 2 distinct DataSources:
> * DataStream with only an append operation
> * DataStore with all 3 WMA operations (has to return a FH)
> Each RuleUnit will have a mailbox. When a RuleUnit is executed for the first time all data in its DataSources are flushed into its mailbox (wrapped in Commands). Then, when the RuleUnit is quiescent, it remains subscribed to its DataSources so that all new operation performed on them get also automatically flushed into its mailbox.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-11029) Sometimes Artemis cluster with JGroups discovery is not formed after restart
by Martin Stefanko (Jira)
[ https://issues.jboss.org/browse/WFLY-11029?page=com.atlassian.jira.plugin... ]
Martin Stefanko updated WFLY-11029:
-----------------------------------
Labels: downstream_dependency (was: )
> Sometimes Artemis cluster with JGroups discovery is not formed after restart
> ----------------------------------------------------------------------------
>
> Key: WFLY-11029
> URL: https://issues.jboss.org/browse/WFLY-11029
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Justin Bertram
> Priority: Critical
> Labels: downstream_dependency
>
> There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test.
> Test scenario:
> * Start 2 server in Artemis cluster
> * Start 2 servers with MDB connected to Artemis cluster
> ** MDB resends messages from InQueue to OutQueue from/to remote cluster
> * Send messages to InQueue
> * Restart all server (one by one)
> * Consumes messages from OutQueue
> Results:
> After the test there are missing messages in OutQueue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFCORE-3670) module defined with an alias in jboss-deployment-structure.xml with fails to parse when annotations=true
by Martin Stefanko (Jira)
[ https://issues.jboss.org/browse/WFCORE-3670?page=com.atlassian.jira.plugi... ]
Martin Stefanko updated WFCORE-3670:
------------------------------------
Labels: downstream_dependency (was: )
> module defined with an alias in jboss-deployment-structure.xml with fails to parse when annotations=true
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3670
> URL: https://issues.jboss.org/browse/WFCORE-3670
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 4.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: downstream_dependency
>
> This is a follow up to JBEAP-13094.
> Having a deployment with jboss-deployment-structure like this:
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> <module name="deployment.application-exception-api">
> <resources>
> <resource-root path="application-exception-api.jar"/>
> </resources>
> <dependencies>
> <module name="javax.ejb.api" export="true"/>
> <module name="javaee.api" export="true"/>
> <module name="javax.api" export="true"/>
> </dependencies>
> <module-alias name="deployment.api" />
> </module>
> <sub-deployment name="application-exception-ejb.jar">
> <dependencies>
> <module name="deployment.api" annotations="true" meta-inf="export"/>
> </dependencies>
> </sub-deployment>
> </jboss-deployment-structure>
> {code}
> it fails to parse.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-10968) Backup doesn't activate after shared store is reconnected
by Martin Stefanko (Jira)
[ https://issues.jboss.org/browse/WFLY-10968?page=com.atlassian.jira.plugin... ]
Martin Stefanko updated WFLY-10968:
-----------------------------------
Labels: downstream_dependency (was: )
> Backup doesn't activate after shared store is reconnected
> ---------------------------------------------------------
>
> Key: WFLY-10968
> URL: https://issues.jboss.org/browse/WFLY-10968
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Environment: NFS configuration
> {noformat}
> messaging-10.jbm.lab.bos.redhat.com:/hornetq on /mnt/hornetq/client type nfs4 (rw,nosuid,nodev,relatime,sync,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,soft,noac,nosharecache,proto=tcp,timeo=50,retrans=5,sec=sys,clientaddr=10.16.100.40,lookupcache=none,local_lock=none,addr=10.16.100.24)
> {noformat}
> Java version
> {noformat}
> java version "1.8.0_151"
> Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode
> {noformat}
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Critical
> Labels: downstream_dependency
>
> *Scenario*
> # Start live backup server pair in dedicated topology with shared store HA, with journal located on NFS
> # NFS mounted on backup server fails
> # Reconnect NFS on backup server
> # Try to shut down live EAP server
> # Backup doesn't activate
> *What happens*
> Backup is waiting for live to fail by checking its file lock. In case the connection to shared storage fails, backup logs following error.
> {noformat}
> 05:50:57,896 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=836c9b1e-f067-11e7-8763-001b21862475) AMQ224000: Failure in initialisation: java.io.IOException: Input/output error
> at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) [rt.jar:1.8.0_151]
> at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90) [rt.jar:1.8.0_151]
> at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1115) [rt.jar:1.8.0_151]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.tryLock(FileLockNodeManager.java:299) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.lock(FileLockNodeManager.java:316) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.awaitLiveNode(FileLockNodeManager.java:127) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:77) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2496) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> {noformat}
> Exception is caught in {{SharedStoreBackupActivation.run}}, and causes termination of backup activation process.
> In case the NFS is reconnected later, backup server doesn't continue in activation process and it doesn't wait for live to fail. In case the live fails, backup doesn't activate, even though it has a connection to shared storage.
> Backup should retry checking live lock even in case the storage is unavailable. It should log warning/error messages that storage is unavailable, but it should not terminate the activation process. This would allow backup to continue its duties when the storage is reconnected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months