[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21920:
-------------------------------------
So the oc location is stored in a threadlocal in the UI handler but the real work is done in the background job, i.e, another thread
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: oc_binary, openshift_v3
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
> But when using port forwading, there is an error with following stack
> {code}
> com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124)
> at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110)
> at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21038:
----------------------------------------
We can't do anything for 4.3.1 here besides document this issues + SWT-GTK3=0 workaround.
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21920:
-------------------------------------
I can reproduce the problem. This is most likely due to my last change in https://github.com/jbosstools/jbosstools-openshift/commit/7a505b4a0e1b89b...
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: oc_binary, openshift_v3
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
> But when using port forwading, there is an error with following stack
> {code}
> com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124)
> at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110)
> at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21038:
-----------------------------------
Fix Version/s: 4.3.1.Final
(was: 4.3.1.CR1)
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.Final
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21038:
-----------------------------------
Priority: Major (was: Critical)
> Software/Update page is not working on Fedora 23 [JBT 4.3 / Mars]
> -----------------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Labels: doc_writer_needed, docs_getting_started_guide, docs_gettingstarted_guide, docs_installation_guide, known_issue
> Fix For: 4.3.1.CR1
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, should be more user friendly
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21731:
---------------------------------------
Here's what I found while discussing about the issue with [~scabanovich]:
The {{ServerSettingsWizardPage#loadResources(IWizard)}} method is as follow:
{code}
/**
* Loads the resources for this view, does it in a blocking way.
* @param model
* @param container
*/
private void loadResources(final IWizardContainer container) {
try {
WizardUtils.runInWizard(new Job("Loading projects and services...") {
@Override
protected IStatus run(IProgressMonitor monitor) {
ServerSettingsWizardPage.this.model.loadResources();
ServerSettingsWizardPage.this.needsLoadingResources = false;
...
{code}
but since the call to {{model.loadResources()}} fails, the next statements are skipped and the job is exited. This means that the {{needsLoadingResources}} flag remains to {{true}} and as a consequence, the {{isPageComplete()}} keeps returning {{false}}:
{code}
@Override
public boolean isPageComplete() {
return !isLoadingResources && uiHook != null && !uiHook.isDisposed() &&
!needsLoadingResources && model != null && model.getService() != null && super.isPageComplete();
}
{code}
> Server Adapter: Error shown when image is not created/pushed yet, should be more user friendly
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21731
> URL: https://issues.jboss.org/browse/JBIDE-21731
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Blocker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> 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.
> 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