[JBoss JIRA] (JBIDE-21582) Server adapter: always publishes on Eclipse startup
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21582?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21582:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an OpenShift v3 server adapter (ex. called "eap-app at OpenShift 3 (10.1.2.2)")
# EXEC: File > Restart to restart Eclipse
Result:
* Eclipse is restarted, Servers view is visible: OS 3 server adapter is "[Started]" and turns to "[Started, Publishing...]"
* if you didnt check "Save password" when creating your connection, you now have the connection dialog popping up, prompting you to provide the password for your connection
Result:
You get the connection dialog (if you didnt store the password) or at least the SSL certificate dialog presented right after Eclipse restarted since the server adapter is publishing right away.
The actual callstack shows that OpenshiftResourceChangeListener.MagicProjectChangeJob is triggering a publish upon startup:
{code}
Connection.authorize() line: 232
Connection.connect() line: 205
Connection.retryList(String, OpenShiftException, String) line: 410
Connection.getResources(String, String) line: 365
OpenShiftServerUtils.getService(IServerAttributes, Connection) line: 244
OpenShiftServerUtils.getService(IServerAttributes) line: 233
OpenShiftServerBehaviour.publish(int, List<IModule[]>, IProgressMonitor, IAdaptable) line: 45
Server.publishImpl(int, List<IModule[]>, IAdaptable, IProgressMonitor) line: 3172
Server.publish(int, IProgressMonitor) line: 1330
OpenshiftResourceChangeListener$MagicProjectChangeJob.autoPublish(IResourceChangeEvent) line: 227
OpenshiftResourceChangeListener$MagicProjectChangeJob.run(IProgressMonitor) line: 208
{code}
was:
# ASSERT: make sure you have an OpenShift v3 server adapter (ex. called "eap-app at OpenShift 3 (10.1.2.2)")
# EXEC: File > Restart to restart Eclipse
Result:
* Eclipse is restarted, Servers view is visible: OS 3 server adapter is "[Started]" and turns to "[Started, Publishing...]"
* if you didnt check "Save password" when creating your connection, you now have the connection dialog popping up, prompting you to provide the password for your connection
Result:
You get the connection dialog (if you didnt store the password) or at least the SSL certificate dialog presented right after Eclipse restarted since the server adapter is publishing right away.
The actual callstack shows that OpenshiftResourceChangeListener.MagicProjectChangeJob is triggering a publish upon startup:
{code}
Connection.authorize() line: 232
Connection.connect() line: 205
Connection.retryList(String, OpenShiftException, String) line: 410
Connection.getResources(String, String) line: 365
OpenShiftServerUtils.getService(IServerAttributes, Connection) line: 244
OpenShiftServerUtils.getService(IServerAttributes) line: 233
OpenShiftServerBehaviour.publish(int, List<IModule[]>, IProgressMonitor, IAdaptable) line: 45
Server.publishImpl(int, List<IModule[]>, IAdaptable, IProgressMonitor) line: 3172
Server.publish(int, IProgressMonitor) line: 1330
OpenshiftResourceChangeListener$MagicProjectChangeJob.autoPublish(IResourceChangeEvent) line: 227
OpenshiftResourceChangeListener$MagicProjectChangeJob.run(IProgressMonitor) line: 208
{code}
> Server adapter: always publishes on Eclipse startup
> ---------------------------------------------------
>
> Key: JBIDE-21582
> URL: https://issues.jboss.org/browse/JBIDE-21582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: usage-on-splash.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21791:
---------------------------------------------
So you suggest that anytime I start a forge command forge will force a save all on every open editor ?
I find that very crappy and a very leaky abstraction.
Could it be done only for resources that gets opened for editing ?
> Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21791
> URL: https://issues.jboss.org/browse/JBIDE-21791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.1.Beta2
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 4.3.1.CR1
>
> Attachments: eclipse-add.png
>
>
> Similar problem as FORGE-2605 but this time its in Eclipse.
> See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog.
> I wonder if the fix should be like in IDEA to save the file before the command is run.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21801) On Windows, can't Download Runtimes for JBoss EAP and JBoss Fuse
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21801?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-21801:
-----------------------------------------
When I try to log with my redhat account, it works.
Just after the login I'm redirected to another page which is asking me to accept the license. After accepting i'm redirected to the same page in the screenshot 7-allinformationprovided
> On Windows, can't Download Runtimes for JBoss EAP and JBoss Fuse
> ----------------------------------------------------------------
>
> Key: JBIDE-21801
> URL: https://issues.jboss.org/browse/JBIDE-21801
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Beta2
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
> Attachments: 1-preferencepage.png, 2-selectRuntime.png, 3-clickDownLoadAndInstall.png, 4-selectEactVersion.png, 5-fillCredentials.png, 6-PleaseuseFollowingLink.png, 7-allInformationprovided.png
>
>
> first technical investigation:
> - the url used to retrieve information on the Terms and conditions page is (I put a breakpoint on DownloadmanagertermsAndConditionsFragment.getTCResponseString): https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%...
> and it returns:
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <result>
> <htmlText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use <a href="https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f...">following link</a> instead!]]></htmlText>
> <plainText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f... instead!]]></plainText>
> <customParams>
> <param name="company" label="Company" />
> <param name="country" label="Country" >
> <options multiple="false">
> </options>
> </param>
> <param name="downloadURL" label="Downloaded file" >
> <options multiple="false">
> <option key="https://www.jboss.org/download-manager/content/origin/files/sha256/e5/e5b..."/>
> </options>
> </param>
> </customParams>
> </result>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21795) [CDK Server Wizard] NPE when adding a new Username
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21795?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21795:
-------------------------------------
I honestly can't figure out what's going on here to replicate it. He's replicated it even on clean / new workspaces, but if it's a clean / new workspace, there shouldn't be any domains to sort.... just the two automatic domains (access.redhat.com and jboss, and both should have names).
> [CDK Server Wizard] NPE when adding a new Username
> ---------------------------------------------------
>
> Key: JBIDE-21795
> URL: https://issues.jboss.org/browse/JBIDE-21795
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- Fred Bricon wrote: ---
> Opened new Server wizard,
> selected CDK server,
> clicked on "Add..." button on username line
>
> code: 0
> plugin: org.eclipse.ui_3.107.0.v20150507-1945
> message: Unhandled event loop exception
> fingerprint: 9d325d266855ea6cd9425941c0fecec0
> exception class: java.lang.NullPointerException
> exception message: -
> number of children: 0
>
> java.lang.NullPointerException: null
> at java.lang.String.compareTo(String.java:1155)
> at org.jboss.tools.foundation.core.credentials.internal.CredentialsModel$1.compare(CredentialsModel.java:198)
> at org.jboss.tools.foundation.core.credentials.internal.CredentialsModel$1.compare(CredentialsModel.java:1)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1454)
> at java.util.Collections.sort(Collections.java:175)
> at org.jboss.tools.foundation.core.credentials.internal.CredentialsModel.getDomains(CredentialsModel.java:196)
> at org.jboss.tools.foundation.ui.credentials.internal.NewCredentialUserDialog.createDialogArea(NewCredentialUserDialog.java:118)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.foundation.ui.credentials.internal.NewCredentialUserDialog.create(NewCredentialUserDialog.java:84)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent.addUserPressed(ChooseCredentialComponent.java:130)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent.access$1(ChooseCredentialComponent.java:126)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent$3.widgetSelected(ChooseCredentialComponent.java:121)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$1.widgetSelected(ServersView2.java:116)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1564)
> at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:6010)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(OS.java:-2)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2571)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool(OS.java:-2)
> at org.eclipse.swt.internal.cocoa.NSRunLoop.runMode(NSRunLoop.java:42)
> at org.eclipse.swt.widgets.Display.sleep(Display.java:4740)
> at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopIdle(WorkbenchAdvisor.java:368)
> at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.eventLoopIdle(IDEWorkbenchAdvisor.java:858)
> at org.eclipse.ui.internal.Workbench$3.eventLoopIdle(Workbench.java:521)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
>
>
> General Information:
> reported-by: Fred Bricon
> anonymous-id: edd62de2-d4be-4d9f-8cab-817f6b18834d
> eclipse-build-id: 4.5.2.M20160113-1000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.10.5 (x86_64) - cocoa
> jre-version: 1.8.0_65-b17
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.core.databinding.observable_1.5.0.v20150422-0725
> 2. org.eclipse.core.databinding_1.5.0.v20150422-0725
> 3. org.eclipse.core.runtime_3.11.1.v20150903-1804
> 4. org.eclipse.e4.ui.workbench_1.3.1.v20160107-1220
> 5. org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621
> 6. org.eclipse.equinox.app_1.3.300.v20150423-1356
> 7. org.eclipse.equinox.launcher_1.3.100.v20150511-1540
> 8. org.eclipse.jface_3.11.0.v20151124-1540
> 9. org.eclipse.swt_3.104.1.v20160113-0811
> 10. org.eclipse.ui_3.107.0.v20150507-1945
> 11. org.eclipse.ui.ide.application_1.1.0.v20150422-0725
> 12. org.eclipse.ui.ide_3.11.0.v20150825-2158
> 13. org.eclipse.wst.server.ui_1.5.202.v201602111638
> 14. org.jboss.tools.foundation.core_1.2.1.qualifier
> 15. org.jboss.tools.foundation.ui_1.2.1.qualifier
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://redhat.ctrlflow.com/committers/#/problems/56d47a21e4b0a0de48c2b252
> * Manual: https://redhat.ctrlflow.com/community/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21795) [CDK Server Wizard] NPE when adding a new Username
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21795?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21795:
-----------------------------------------------
[~fbricon], please check if the fix toJBIDE-21803 managed to fix this issue too.
> [CDK Server Wizard] NPE when adding a new Username
> ---------------------------------------------------
>
> Key: JBIDE-21795
> URL: https://issues.jboss.org/browse/JBIDE-21795
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- Fred Bricon wrote: ---
> Opened new Server wizard,
> selected CDK server,
> clicked on "Add..." button on username line
>
> code: 0
> plugin: org.eclipse.ui_3.107.0.v20150507-1945
> message: Unhandled event loop exception
> fingerprint: 9d325d266855ea6cd9425941c0fecec0
> exception class: java.lang.NullPointerException
> exception message: -
> number of children: 0
>
> java.lang.NullPointerException: null
> at java.lang.String.compareTo(String.java:1155)
> at org.jboss.tools.foundation.core.credentials.internal.CredentialsModel$1.compare(CredentialsModel.java:198)
> at org.jboss.tools.foundation.core.credentials.internal.CredentialsModel$1.compare(CredentialsModel.java:1)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1454)
> at java.util.Collections.sort(Collections.java:175)
> at org.jboss.tools.foundation.core.credentials.internal.CredentialsModel.getDomains(CredentialsModel.java:196)
> at org.jboss.tools.foundation.ui.credentials.internal.NewCredentialUserDialog.createDialogArea(NewCredentialUserDialog.java:118)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.foundation.ui.credentials.internal.NewCredentialUserDialog.create(NewCredentialUserDialog.java:84)
> at org.eclipse.jface.window.Window.open(Window.java:792)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent.addUserPressed(ChooseCredentialComponent.java:130)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent.access$1(ChooseCredentialComponent.java:126)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent$3.widgetSelected(ChooseCredentialComponent.java:121)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$1.widgetSelected(ServersView2.java:116)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1564)
> at org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:6010)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(OS.java:-2)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2571)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool(OS.java:-2)
> at org.eclipse.swt.internal.cocoa.NSRunLoop.runMode(NSRunLoop.java:42)
> at org.eclipse.swt.widgets.Display.sleep(Display.java:4740)
> at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopIdle(WorkbenchAdvisor.java:368)
> at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.eventLoopIdle(IDEWorkbenchAdvisor.java:858)
> at org.eclipse.ui.internal.Workbench$3.eventLoopIdle(Workbench.java:521)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
>
>
> General Information:
> reported-by: Fred Bricon
> anonymous-id: edd62de2-d4be-4d9f-8cab-817f6b18834d
> eclipse-build-id: 4.5.2.M20160113-1000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.10.5 (x86_64) - cocoa
> jre-version: 1.8.0_65-b17
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.core.databinding.observable_1.5.0.v20150422-0725
> 2. org.eclipse.core.databinding_1.5.0.v20150422-0725
> 3. org.eclipse.core.runtime_3.11.1.v20150903-1804
> 4. org.eclipse.e4.ui.workbench_1.3.1.v20160107-1220
> 5. org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621
> 6. org.eclipse.equinox.app_1.3.300.v20150423-1356
> 7. org.eclipse.equinox.launcher_1.3.100.v20150511-1540
> 8. org.eclipse.jface_3.11.0.v20151124-1540
> 9. org.eclipse.swt_3.104.1.v20160113-0811
> 10. org.eclipse.ui_3.107.0.v20150507-1945
> 11. org.eclipse.ui.ide.application_1.1.0.v20150422-0725
> 12. org.eclipse.ui.ide_3.11.0.v20150825-2158
> 13. org.eclipse.wst.server.ui_1.5.202.v201602111638
> 14. org.jboss.tools.foundation.core_1.2.1.qualifier
> 15. org.jboss.tools.foundation.ui_1.2.1.qualifier
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://redhat.ctrlflow.com/committers/#/problems/56d47a21e4b0a0de48c2b252
> * Manual: https://redhat.ctrlflow.com/community/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, could be more user friendly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21731 at 3/1/16 6:29 PM:
-----------------------------------------------------------------------
Wizard takes all tag images for all services. It is possible that user wants to select a service for which image tag with deployment folder is available, while as it is now, loading may fail because _another_ image tag is not yet ready. While loading resources in the wizard, we can for each imageRef (in DeploymentResourceMapper.getImageStreamTagsFor(Deployment)) call getResource(ResourceKind.IMAGE_STREAM_TAG,...) in try-catch to get and save the problem. Method getImageStreamTagsFor() now is used only by ServerSettingViewModel, and it does not need the entire resources, it gets them only to convert to json and look inside for the deployment folder. So, method getImageStreamTagsFor(), or its copy more useful for server adapter may return mapping of IService not to collection of IResource objects, but to collection of bean objects that will contain
- String imageRef;
- String imageTagJson; (null if failed)
- OpenShiftExceptioned exception; (not null if failed).
When user selects a service in the wizard, then if for this service
a) all image tags are successfully retrieved (beans have no exceptions) - just deployment folder is derived;
b) some image tags are successfully retrieved and provide deployment folder, but some image tags failed - deployment folder is derived and warning informs user that an image/images for the service are in build at the moment;
c) some or all image tags failed, and deployment folder cannot be derived - user is warned about that.
Anyway, user can enter deployment folder manually and complete the wizard.
Also, we can add to the wizard a checkbox 'Derive deployment folder at publishing', and when it is checked it will disable deployment folder text input, so that user can complete not ignoring the warning, but instructing server to do what you described above.
[~adietish], can all or part of this be ok?
was (Author: scabanovich):
Wizard takes all tag images for all services. It is possible that user wants to select a service for which image tag with deployment folder is available, while as it is now, loading may fail because _another_ image tag is not yet ready. While loading resources in the wizard, we can for each imageRef (in DeploymentResourceMapper.getImageStreamTagsFor(Deployment)) call getResource(ResourceKind.IMAGE_STREAM_TAG,...) in try-catch to get and save the problem. Method getImageStreamTagsFor() now is used only by ServerSettingViewModel, and it does not need the entire resources, it gets them only to convert to json and look inside for the deployment folder. So, method getImageStreamTagsFor(), or its copy more useful for server adapter may return mapping of IService not to collection of IResource objects, but to collection of bean objects that will contain
- String imageRef;
- String imageTagJson; (null if failed)
- OpenShiftExceptioned exception; (not null if failed).
When user selects a service in the wizard, then if for this service
a) all image tags are successfully retrieved (beans have no exceptions) - just deployment folder is derived;
b) some image tags are successfully retrieved and provide deployment folder, but some image tags failed - deployment folder is derived and warning informs user that an image/images for the service are in build at the moment;
c) some or all image tags failed, and deployment folder cannot be derived - user is warned about that.
Anyway, user can enter deployment folder manually and complete the wizard.
Also, we can add to the wizard a checkbox 'Derive deployment folder at publishing' - that when checked will disable deployment folder text input, so that user can complete not ignoring the warning, but instructing server to do what you described above.
[~adietish], can all or part of this be ok?
> Server Adapter: Error shown when image is not created/pushed yet, could be more user friendly
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21731
> URL: https://issues.jboss.org/browse/JBIDE-21731
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: cannot_get_image.png
>
>
> When I create a new OS3 application and then I want to create a new server adapter, an image for this application has to be built and pushed to OpenShift's local image registry. If build is still running, what is often happening on internal OSE instance (it takes minutes - pushing of images), then there is an error message that loading of image failed. User without solid overview of OS3 background would not be able to figure out why it is happening, because even Image stream is shown, but the image is not there yet.
> Screenshot of error:
> !cannot_get_image.png!
> Full error log:
> {code}
> com.openshift.restclient.OpenShiftException: Could not get resource django-example:latest in namespace image: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:481)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:306)
> at org.jboss.tools.openshift.core.connection.Connection.getResource(Connection.java:378)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$5(DeploymentResourceMapper.java:106)
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getImageStreamTagsFor(DeploymentResourceMapper.java:107)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$2(DeploymentResourceMapper.java:87)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getAllImageStreamTags(DeploymentResourceMapper.java:85)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.createImageStreamsMap(ServerSettingsViewModel.java:334)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.<init>(ServerSettingsViewModel.java:327)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.lambda$1(ServerSettingsViewModel.java:279)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.createImageStreamTagsMap(ServerSettingsViewModel.java:277)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:261)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:255)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$15.run(ServerSettingsWizardFragment.java:695)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.NotFoundException: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:230)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:141)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:302)
> ... 36 more
> Caused by: java.io.FileNotFoundException: https://console.engint.openshift.com/oapi/v1/namespaces/image/imagestream...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 39 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, could be more user friendly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21731 at 3/1/16 6:27 PM:
-----------------------------------------------------------------------
Wizard takes all tag images for all services. It is possible that user wants to select a service for which image tag with deployment folder is available, while as it is now, loading may fail because _another_ image tag is not yet ready. While loading resources in the wizard, we can for each imageRef (in DeploymentResourceMapper.getImageStreamTagsFor(Deployment)) call getResource(ResourceKind.IMAGE_STREAM_TAG,...) in try-catch to get and save the problem. Method getImageStreamTagsFor() now is used only by ServerSettingViewModel, and it does not need the entire resources, it gets them only to convert to json and look inside for the deployment folder. So, method getImageStreamTagsFor(), or its copy more useful for server adapter may return mapping of IService not to collection of IResource objects, but to collection of bean objects that will contain
- String imageRef;
- String imageTagJson; (null if failed)
- OpenShiftExceptioned exception; (not null if failed).
When user selects a service in the wizard, then if for this service
a) all image tags are successfully retrieved (beans have no exceptions) - just deployment folder is derived;
b) some image tags are successfully retrieved and provide deployment folder, but some image tags failed - deployment folder is derived and warning informs user that an image/images for the service are in build at the moment;
c) some or all image tags failed, and deployment folder cannot be derived - user is warned about that.
Anyway, user can enter deployment folder manually and complete the wizard.
Also, we can add to the wizard a checkbox 'Derive deployment folder at publishing' - that when checked will disable deployment folder text input, so that user can complete not ignoring the warning, but instructing server to do what you described above.
[~adietish], can all or part of this be ok?
was (Author: scabanovich):
Wizard takes all tag images for all services. It is possible that user wants to select a service for which image tag with deployment folder is available, while as it is now, loading may fail because _another_ image tag is not yet ready. While loading resources in the wizard, we can for each imageRef (in DeploymentResourceMapper.getImageStreamTagsFor(Deployment)) call getResource(ResourceKind.IMAGE_STREAM_TAG,...) in try-catch to get and save the problem. Method getImageStreamTagsFor() now is used only by ServerSettingViewModel, and it does not need the entire resources, it gets them only to convert to json and look inside for the deployment folder. So, method getImageStreamTagsFor(), or its copy more useful for server adapter may return mapping of IService not to collection of IResource objects, but to collection of bean objects that will contain
- String imageRef;
- String imageTagJson; (null if failed)
- OpenShiftExceptioned exception; (not null if failed).
When user selects a service in the wizard, then if for this service
a) all image tags are successfully retrieved (beans have no exceptions) - just deployment folder is derived;
b) some image tags are successfully retrieved and provide deployment folder, but some image tags failed - deployment folder is derived and warning informs user that an image/images for the service are in build at the moment;
c) some or all image tags failed, and deployment folder cannot be derived - user is warned about that.
Anyway, user can enter deployment folder manually and complete the wizard.
Also, we can add to the wizard a checkbox 'Derive deployment folder at publishing' - that when checked will disable deployment folder text input, so that user can complete not ignoring the warning, but instructing server to do what you described above.
[~adietish], can all or part of this be ok?
> Server Adapter: Error shown when image is not created/pushed yet, could be more user friendly
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21731
> URL: https://issues.jboss.org/browse/JBIDE-21731
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: cannot_get_image.png
>
>
> When I create a new OS3 application and then I want to create a new server adapter, an image for this application has to be built and pushed to OpenShift's local image registry. If build is still running, what is often happening on internal OSE instance (it takes minutes - pushing of images), then there is an error message that loading of image failed. User without solid overview of OS3 background would not be able to figure out why it is happening, because even Image stream is shown, but the image is not there yet.
> Screenshot of error:
> !cannot_get_image.png!
> Full error log:
> {code}
> com.openshift.restclient.OpenShiftException: Could not get resource django-example:latest in namespace image: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:481)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:306)
> at org.jboss.tools.openshift.core.connection.Connection.getResource(Connection.java:378)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$5(DeploymentResourceMapper.java:106)
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getImageStreamTagsFor(DeploymentResourceMapper.java:107)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$2(DeploymentResourceMapper.java:87)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getAllImageStreamTags(DeploymentResourceMapper.java:85)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.createImageStreamsMap(ServerSettingsViewModel.java:334)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.<init>(ServerSettingsViewModel.java:327)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.lambda$1(ServerSettingsViewModel.java:279)
> at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.createImageStreamTagsMap(ServerSettingsViewModel.java:277)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:261)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:255)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$15.run(ServerSettingsWizardFragment.java:695)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.NotFoundException: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "imageStreamTag \"django-example:latest\" not found",
> "reason": "NotFound",
> "details": {
> "name": "django-example:latest",
> "kind": "imageStreamTag"
> },
> "code": 404
> }
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:230)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:141)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:302)
> ... 36 more
> Caused by: java.io.FileNotFoundException: https://console.engint.openshift.com/oapi/v1/namespaces/image/imagestream...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161)
> ... 39 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
