[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22767:
-------------------------------------
Fix Version/s: 4.4.1.AM3
> Deploy Docker Wizard: Create image stream contains wrong tags in some cases
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22767
> URL: https://issues.jboss.org/browse/JBIDE-22767
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.4.1.AM3
>
>
> In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...).
> Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image.
> Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22746) Port forwarding shell is not opened
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22746?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22746:
-------------------------------------
Fix Version/s: 4.4.1.Final
> Port forwarding shell is not opened
> -----------------------------------
>
> Key: JBIDE-22746
> URL: https://issues.jboss.org/browse/JBIDE-22746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v2
> Fix For: 4.4.1.Final
>
>
> When I select a context menu item in context menu of an OpenShift 2 application, Port Forwarding dialog is not opened. Right after click on the item there is a running job Verifying SSH session but once its finished, nothing happens. There is even no error/warning in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22603:
------------------------------------
[~mlabuda] can you check with master as I cannot reproduce and some important changes about watch management has been brought by okhttp implementation of Openshift REST client
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: explorer, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22862) Example "." found when searching for a Camel quickstart
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-22862:
-----------------------------------
Summary: Example "." found when searching for a Camel quickstart
Key: JBIDE-22862
URL: https://issues.jboss.org/browse/JBIDE-22862
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 4.4.1.AM1
Environment: JBoss Fuse Tools must be installed
Reporter: Fred Bricon
When the JBoss Fuse tools are installes, the Camel examples are available in JBoss Central. If you search for Camel, An example named "." is returned. It fails to import.
See !http://content.screencast.com/users/fbricon/folders/Jing/media/36fb717a-1cd8-4c6a-8c25-b74d46c4c6be/00000447.png|width=700!
That example should not be returned.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months