[jboss-jira] [JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images

[Kevin Earls (JIRA)]

    [ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562417#comment-13562417 ] 

Kevin Earls commented on SWSQE-113:
-----------------------------------

We've switched to the B12 cluster, and things have improved.  I am now able to deploy ElasticSearch.  However, builds fail trying to deploy test applications using the fabric8 maven plugin.  (I have talked to a contact on that team.  They have not yet tested vs 3.9, but are planning to so tomorrow) . I will add log messages from this later, but currently I am experiencing problem 1 below.

There are some other issues.

1. I sometimes get errors when I attempt to open the Jenkins console at jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com’s server IP address 
2. Even when I've been able to deploy ES, one of the nodes sometimes fails, even when not under load.
3. I've seen the following popup on the OpenShift console several times.

An error occurred connecting to the server.
Failed to list appliedclusterresourcequotas/quota.openshift.io/v1 (status -1)
Failed to list resourcequotas/v1 (status -1)
Refresh




> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
>                 Key: SWSQE-113
>                 URL: https://issues.jboss.org/browse/SWSQE-113
>             Project: Kiali QE
>          Issue Type: QE Task
>            Reporter: Kevin Earls
>            Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images.  I have already started working with [~fbrychta] but we have not completely resolved this yet.  
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible.  In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)