[JBoss JIRA] (SWSQE-478) Install Istioctl on the demand when is needed
by Guilherme Baufaker Rêgo (Jira)
Guilherme Baufaker Rêgo created SWSQE-478:
---------------------------------------------
Summary: Install Istioctl on the demand when is needed
Key: SWSQE-478
URL: https://issues.jboss.org/browse/SWSQE-478
Project: Kiali QE
Issue Type: Sub-task
Reporter: Guilherme Baufaker Rêgo
Assignee: Guilherme Baufaker Rêgo
When it is pre-installed instioctl, sometimes it may lead to a situation that istioctl uses a different version than istio files
See SWSQE-475 for that situation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3216) Async dependencies resolution or add loading indicator during scesim creation
by Daniele Zonca (Jira)
Daniele Zonca created DROOLS-3216:
-------------------------------------
Summary: Async dependencies resolution or add loading indicator during scesim creation
Key: DROOLS-3216
URL: https://issues.jboss.org/browse/DROOLS-3216
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Daniele Zonca
Assignee: Daniele Zonca
When user create the first scesim file in the project, the system creates the JUnit activator file and it adds the needed dependencies.
After that the system takes several seconds (5-6) to retrieve all the dependencies.
During this time the editor still blank without any indicator or information to the user about what is going on.
This happens only for the first scesim creation in the project
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (SWSQE-476) PRT Output Improve
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-476?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-476:
------------------------------------------
Sprint: Kiali Sprint #13 (was: Kiali Sprint #13)
> PRT Output Improve
> ------------------
>
> Key: SWSQE-476
> URL: https://issues.jboss.org/browse/SWSQE-476
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
>
> Feedback from developers.
> When PRT fails because of some internal reason, e.g. bookinfo install fails, devs are confused. Or if e2e tests fail for some other reason.
> What we need to do, when PRT fails due to other reason that e2e tests broken by PR, then the bot should comment in PR that "PRT is broken, contact to QE".
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-10654) In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-10654?page=com.atlassian.jira.plugin... ]
Chao Wang reassigned WFLY-10654:
--------------------------------
Assignee: (was: Chao Wang)
> In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10654
> URL: https://issues.jboss.org/browse/WFLY-10654
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 13.0.0.Final
> Reporter: Chao Wang
> Priority: Major
>
> Deployment(from management console) of a simple Jar file in EAP 7.1.x causes the ejb cache container to start , which should not be the case .
> From EAP 7.1.x onwards @clustered annotation has been depricated and EJB application is required to start clustering , but in contradiction to this even if we deploy ant jar file (let's say ojdbc6.jar ) the container treats it as an EJB application and starts the EJB cache container as seen in the logs below :
> ~~~~
> 1,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb
> 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb
> 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel ejb
> 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel ejb
> 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia]
> 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia]
> 22:14:21,676 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200]
> 22:14:21,678 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200]
> ~~~~
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month