[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22005:
---------------------------------------
This could also be maybe the connection is open so long that it times out? Can you describe how long it was open and provide any eclipse logs that may be relevant?
> Unexpected EOF in pod log
> -------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21967?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21967:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Cannot create server adapter if there is a running build on a project although there are more projects
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21967
> URL: https://issues.jboss.org/browse/JBIDE-21967
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21992:
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21998) "Open in Web browser" displays a dialog to select a route
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21998?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21998:
-----------------------------------------------
[~adietish], please take a look if I did it right.
> "Open in Web browser" displays a dialog to select a route
> ---------------------------------------------------------
>
> Key: JBIDE-21998
> URL: https://issues.jboss.org/browse/JBIDE-21998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2016-03-30 00.20.48.png
>
>
> I have an OpenShift project with 2 services: one {{eap-app}} and one NodeJS.
> For the {{eap-app}} service, I have a corresponding server adapter.
> When I select {{<eap-app server adapter> > Show In > Web Browser}}, I have the following dialog to select a route, but that seems wrong because I already selected the {{eap-app}} service, so there's no reason to propose me the route to the NodeJS service.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months