[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22640.
---------------------------------
Verified in DevStudio 10.2.0.AM2 build AM2-v20161014-0456-B6202.
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final, 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.2.AM2
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22803:
------------------------------------------
As described on the call
1) we won't have an alternative approach for version which don't support the feature. If user sees that something doesn't work, he'll need to refresh the connection in order to pull its actual state.
2) we should rely on the error of the response - if we catch it, then feature isn't supported and then see 1).
[~adietish] [~jcantrill], please, correct me if i'm wrong.
> Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22803
> URL: https://issues.jboss.org/browse/JBIDE-22803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23182) NullPointerException in PodLogsHandler.handleEvent
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23182?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-23182.
---------------------------------
> NullPointerException in PodLogsHandler.handleEvent
> --------------------------------------------------
>
> Key: JBIDE-23182
> URL: https://issues.jboss.org/browse/JBIDE-23182
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, pod_log_console
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.openshift.internal.ui.handler.PodLogsHandler.handleEvent(PodLogsHandler.java:46)
> at org.jboss.tools.openshift.internal.ui.handler.AbstractOpenShiftCliHandler.execute(AbstractOpenShiftCliHandler.java:70)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
> at java.lang.reflect.Method.invoke(null:-1)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> {noformat}
> Bundles:
> | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.openshift.ui | 3.3.0.v20160831-0703 | 3.3.0.v20160831-0703 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57d6df25e4b0fd7621...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23351) Deploy Docker Wizard: Image stream sometimes is not created for local docker images
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23351?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23351:
----------------------------------
Description:
When deploying a local image to OpenShift, Image stream is not created even an image has been pushed to registry. For images on docker hub it works ok.
Following message is shown in resource summary:
!is_not_created.png!
I had checked the checkbox to push to registry. But I am not able to reproduce this all the time. I was able to do it only 2 times.
was:
When deploying a local image to OpenShift, Image stream is not created even an image has been pushed to registry. For images on docker hub it works ok.
Following message is shown in resource summary:
!is_not_created.png!
> Deploy Docker Wizard: Image stream sometimes is not created for local docker images
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23351
> URL: https://issues.jboss.org/browse/JBIDE-23351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Attachments: is_not_created.png
>
>
> When deploying a local image to OpenShift, Image stream is not created even an image has been pushed to registry. For images on docker hub it works ok.
> Following message is shown in resource summary:
> !is_not_created.png!
> I had checked the checkbox to push to registry. But I am not able to reproduce this all the time. I was able to do it only 2 times.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months