[JBoss JIRA] (SWSQE-110) Update OC on Ansible Image
by Guilherme Baufaker Rêgo (JIRA)
Guilherme Baufaker Rêgo created SWSQE-110:
---------------------------------------------
Summary: Update OC on Ansible Image
Key: SWSQE-110
URL: https://issues.jboss.org/browse/SWSQE-110
Project: Kiali QE
Issue Type: Bug
Reporter: Guilherme Baufaker Rêgo
Assignee: Filip Brychta
Started by user Guilherme Baufaker Rêgo
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Still waiting to schedule task
jenkins-slave-ansible-os-client-tools-kxpss is offline
Running on jenkins-slave-ansible-os-client-tools-kxpss in /home/jenkins/workspace/Istio+Mesh+Ansible Pipeline
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Clone Istio Repository)
[Pipeline] checkout
Cloning the remote Git repository
Cloning repository https://github.com/gbaufake/istio.git
> git init /home/jenkins/workspace/Istio+Mesh+Ansible Pipeline/istio # timeout=10
Fetching upstream changes from https://github.com/gbaufake/istio.git
> git --version # timeout=10
> git fetch --tags --progress https://github.com/gbaufake/istio.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://github.com/gbaufake/istio.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/gbaufake/istio.git # timeout=10
Fetching upstream changes from https://github.com/gbaufake/istio.git
> git fetch --tags --progress https://github.com/gbaufake/istio.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/kiali-addon^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/kiali-addon^{commit} # timeout=10
Checking out Revision e5be3cd1b2acc60e3ce4ed798f91366947367e17 (refs/remotes/origin/kiali-addon)
> git config core.sparsecheckout # timeout=10
> git checkout -f e5be3cd1b2acc60e3ce4ed798f91366947367e17
Commit message: "Kiali as Istio Addon"
> git rev-list --no-walk e5be3cd1b2acc60e3ce4ed798f91366947367e17 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Ansible Playbook)
[Pipeline] dir
Running in /home/jenkins/workspace/Istio+Mesh+Ansible Pipeline/istio/install/ansible
[Pipeline] {
[Pipeline] sh
[ansible] Running shell script
+ oc login https://osemaster.os37-gbaufake.osepool.centralci.eng.rdu2.redhat.com:8443 --token=cXd1vapqDSQbW3kWxg7qvuuGgKglMlxvQUaGzH4Mf5s --insecure-skip-tls-verify
Logged into "https://osemaster.os37-gbaufake.osepool.centralci.eng.rdu2.redhat.com:8443" as "user1" using the token provided.
You have access to the following projects and can switch between them with 'oc project <projectname>':
bookinfo
* default
istio-system
kiali-test-box
kiali-test-breadth-sink
kiali-test-breath
kiali-test-circle
kiali-test-circle-callback
kiali-test-depth
kiali-test-depth-sink
kiali-test-hourglass
kube-public
kube-system
logging
management-infra
openshift
openshift-infra
openshift-node
samples
Using project "default".
Welcome! See 'oc help' to get started.
[Pipeline] sh
[ansible] Running shell script
+ oc version
oc v1.5.0+031cbe4
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
[~fbrychta] can you update oc to 3.7?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (DROOLS-2421) Unexpected response from rule engine for windowing rules
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2421?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-2421:
-------------------------------------
Can you please provide a complete reproducer of this issue?
> Unexpected response from rule engine for windowing rules
> --------------------------------------------------------
>
> Key: DROOLS-2421
> URL: https://issues.jboss.org/browse/DROOLS-2421
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final
> Reporter: Bishnu Shankar Pandey
> Assignee: Mario Fusco
>
> Here the sample code of my window rule :
> rule "Sliding window test1"
> agenda-group "g0"
> when
> exists Fact( (facts["parameter2"] ) != null && facts["source"] == "A0") && $number: Number() from accumulate(Fact(facts["parameter2"] != null && $t : Double.valueOf(facts["parameter2"]) && facts["source"] == "A0") over window:time(2m) , sum($t))
> then
> globalList.add("2 Minute Sum of parameter2 of Source A0 is " + $number );
> end
> rule "Sliding window test2"
> agenda-group "g0"
> when
> exists Fact( (facts["parameter2"] ) != null && facts["source"] == "A1") && $number: Number() from accumulate(Fact(facts["parameter2"] != null && $t : Double.valueOf(facts["parameter2"]) && facts["source"] == "A1") over window:time(2m) , sum($t))
> then
> globalList.add("2 Minute Sum of parameter2 of Source A1 is " + $number );
> end
> I am sending request from 2 different sources. I am getting response as 0.0 after some time. I check the values in the working memory by using collect as List for the parameter values. I have found that the previous values got deleted when the response is 0.0. I need immediate help.
> Some important info:
> Fact is the class Object and it has a Hashmap(facts) as class variable. The factmap contains the variable name as key and its value as variable value.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (WFLY-10143) Standalone JMS client is failing with: java.lang.ClassNotFoundException: javax.json.JsonValue with jboss-client.jar
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-10143?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-10143:
---------------------------------------
[~jmesnil] Yes, i've just tried it with Wildfly master (0fa3f2a06fbeff769d0f94e6aab5279f78e2cf92) and it works. Thanks!
> Standalone JMS client is failing with: java.lang.ClassNotFoundException: javax.json.JsonValue with jboss-client.jar
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10143
> URL: https://issues.jboss.org/browse/WFLY-10143
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Blocker
> Fix For: 13.0.0.Beta1
>
>
> If standalone JMS client is using only jboss-client.jar on classpath then during look up of connection factory fails with:
> {code}
> Exception in thread "Thread-0" java.lang.NoClassDefFoundError: javax/json/JsonValue
> at org.apache.activemq.artemis.uri.schema.connector.TCPTransportConfigurationSchema.getTransportConfigurations(TCPTransportConfigurationSchema.java:68)
> at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:44)
> at org.apache.activemq.artemis.uri.schema.serverLocator.TCPServerLocatorSchema.internalNewObject(TCPServerLocatorSchema.java:33)
> at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:86)
> at org.apache.activemq.artemis.utils.uri.URISchema.newObject(URISchema.java:30)
> at org.apache.activemq.artemis.utils.uri.URIFactory.newObject(URIFactory.java:59)
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.newLocator(ServerLocatorImpl.java:411)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:209)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:202)
> at org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory.<init>(ActiveMQJMSConnectionFactory.java:34)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.jboss.marshalling.reflect.SerializableClass.invokeConstructor(SerializableClass.java:340)
> at org.jboss.marshalling.reflect.SerializableClass.callNoArgConstructor(SerializableClass.java:292)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1408)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
> at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
> at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
> at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
> at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
> at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jboss.jms.client.ProducerTransAck.run(ProducerTransAck.java:78)
> Caused by: java.lang.ClassNotFoundException: javax.json.JsonValue
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 33 more
> {code}
> This is because javax.json-api jar is missing.
> Wildfly 12 jms-client-bom does not suffer by this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months
[JBoss JIRA] (WFLY-9699) Add attribute to model which will indicate that backup is synchronized with live server
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-9699?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil reassigned WFLY-9699:
---------------------------------
Assignee: (was: Jeff Mesnil)
> Add attribute to model which will indicate that backup is synchronized with live server
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-9699
> URL: https://issues.jboss.org/browse/WFLY-9699
> Project: WildFly
> Issue Type: Feature Request
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Miroslav Novak
> Priority: Critical
>
> If HA is configured with replicated journal then it takes some time to backup to synchronize with live server. Once backup is in sync with live then following information appears in server.log:
> {code}
> 13:20:00,739 INFO [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-netty-threads-457000966)) AMQ221024: Backup server ActiveMQServerImpl::serverUUID=bc015b34-fd73-11e5-80ca-1b35f669abb8 is synchronized with live-server.
> 13:20:01,500 INFO [org.apache.activemq.artemis.core.server] (Thread-2 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@41f992ab-83559664)) AMQ221031: backup announced
> {code}
> Reading server logs to see whether backup is in sync is not convinient and user friendly way. Could we add this information to model so it can be detected through CLI command?
> New attribute with name {{synchronized-with-live}} should be added to {{/subsystem=messaging-activemq/server=default/ha-policy=replication-slave}}
> This information can be gathered by calling: {{SharedNothingBackupActivation.isRemoteBackupUpToDate()}}
> Additionally we should provide this attribute also in replicated live server in: {{/subsystem=messaging-activemq/server=default/ha-policy=replication-master}} as Administrator might want to know whether live can be shutdown.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 9 months