[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25830?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25830:
---------------------------------------
I think that if OS connection was created with CDK server adapter, there is quite big chance that oc binary resides in given ($MINISHIFT_HOME|~/.minishift)/cache/oc/win|darwin|linux/$version/ folder. Just saying...
On the other side, we can put two weights on the scales. User having everything working out of box vs. let/force him to choose proper oc binary (version he wants to use, not the one we find for him). Just my 0.02.
> After starting CDK server adapter OpenShift Connection does not work when oc is not on path
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-25830
> URL: https://issues.jboss.org/browse/JBIDE-25830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Labels: cdk_server_adapter, connection
> Fix For: 4.5.3.Final
>
>
> OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25865) Mylyn: CoreException: Unexpected error: Forbidden
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25865?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25865:
-------------------------------
Fix Version/s: 4.5.x
> Mylyn: CoreException: Unexpected error: Forbidden
> -------------------------------------------------
>
> Key: JBIDE-25865
> URL: https://issues.jboss.org/browse/JBIDE-25865
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.5.3.AM3
> Environment: F28
> Reporter: Josef Kopriva
> Fix For: 4.5.x
>
>
> {code:java}
> eclipse.buildId=11.3.0.AM3-v20180322-1027-B2194
> java.version=1.8.0_161
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.mylyn.builds.core
> Error
> Tue Mar 27 12:24:58 CEST 2018
> Running build 'openshift.itests' failed
> org.eclipse.core.runtime.CoreException: Unexpected error: Forbidden
> at org.eclipse.mylyn.internal.hudson.core.HudsonCorePlugin.toCoreException(HudsonCorePlugin.java:61)
> at org.eclipse.mylyn.internal.hudson.core.HudsonServerBehaviour.runBuild(HudsonServerBehaviour.java:808)
> at org.eclipse.mylyn.builds.internal.core.operations.RunBuildOperation$1.doExecute(RunBuildOperation.java:55)
> at org.eclipse.mylyn.builds.internal.core.operations.BuildJob.run(BuildJob.java:79)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.eclipse.mylyn.internal.hudson.core.client.HudsonException: Forbidden
> at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.run(HudsonOperation.java:169)
> at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient.runBuild(RestfulHudsonClient.java:417)
> at org.eclipse.mylyn.internal.hudson.core.HudsonServerBehaviour.runBuild(HudsonServerBehaviour.java:806)
> ... 3 more
> Caused by: org.eclipse.mylyn.commons.repositories.core.auth.AuthenticationException: Forbidden
> at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.validate(HudsonOperation.java:273)
> at org.eclipse.mylyn.commons.repositories.http.core.CommonHttpOperation.executeOnce(CommonHttpOperation.java:119)
> at org.eclipse.mylyn.commons.repositories.http.core.CommonHttpOperation.execute(CommonHttpOperation.java:86)
> at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient$7.execute(RestfulHudsonClient.java:403)
> at org.eclipse.mylyn.internal.hudson.core.client.HudsonOperation.run(HudsonOperation.java:167)
> ... 5 more
> {code}
> I have tried to delete secure storage and set up it again and check user permissions, but it didn't help.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25905) [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25905?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-25905:
----------------------------------
Description:
[Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard.
Service Ports table starts to behave awkward after reset.
!service-ports.gif!
was:
[Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard.
Service Ports table starts to behave awkward after reset.
> [Deploy Image to OpenShift ->Service & Routing Settings] Service Port table awkward behavior after reset
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25905
> URL: https://issues.jboss.org/browse/JBIDE-25905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Environment: Windows 10 Pro
> Reporter: Denis Golovin
> Attachments: service-ports.gif
>
>
> [Service & Routing Settings] page in [Deploy Image to OpenShift] Wizard.
> Service Ports table starts to behave awkward after reset.
> !service-ports.gif!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25830 at 4/5/18 6:02 PM:
------------------------------------------------------------------
[~rob.stryker] on that I'd agree yes, it makes no sense to do a disk search. We could maybe prompt the user with the preferences?
was (Author: adietish):
[~rob.stryker] on that I'd agree yes, it makes no sense to do a disk search. We could maybe prompt the user with in the preferences?
> After starting CDK server adapter OpenShift Connection does not work when oc is not on path
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-25830
> URL: https://issues.jboss.org/browse/JBIDE-25830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Labels: cdk_server_adapter, connection
> Fix For: 4.5.3.Final
>
>
> OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25830) After starting CDK server adapter OpenShift Connection does not work when oc is not on path
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25830?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25830:
------------------------------------------
[~rob.stryker] on that I'd agree yes, it makes no sense to do a disk search. We could maybe prompt the user with in the preferences?
> After starting CDK server adapter OpenShift Connection does not work when oc is not on path
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-25830
> URL: https://issues.jboss.org/browse/JBIDE-25830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Labels: cdk_server_adapter, connection
> Fix For: 4.5.3.Final
>
>
> OpenShift connection should be working, when user starts CDK server adapter, even if you do not have oc on path. In my opinion OpenShift connection should be working "out of box" when user starts CDK server adapter.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25670:
------------------------------------------
[~jkopriva] please review https://github.com/jbosstools/jbosstools-openshift/pull/1718. Thx!
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.Final
>
> Attachments: Screenshot_20180213_123635.png, image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
> Some pods may be in terminating state and disappear eventually.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (JBIDE-25837) CDK detected again after devstudio restart
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25837?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25837:
-------------------------------------
Opened 2 PRs:
https://github.com/jbosstools/jbosstools-base/pull/614
https://github.com/jbosstools/jbosstools-openshift/pull/1719
The first one is necessary, the second is just an improvement. Both should be committed though.
> CDK detected again after devstudio restart
> ------------------------------------------
>
> Key: JBIDE-25837
> URL: https://issues.jboss.org/browse/JBIDE-25837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.3.Final
>
> Attachments: cdk-repetitive-detection.png
>
>
> This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when selecting a quick fix in runtime detection dialog).
> I had an installation of devstudio and as usual, cdk server adapter was automatically there. That's expected - when I install devstudio and start it, runtime detection will notice ~/.minishift exists and will quietly create a server adapter with minishift binary location missing.
> Then I installed updates and restarted the IDE. On the next start, I was shown the runtime detection dialog - it showed cdk (based on existing ~/.minishift) and it show an error that minishift binary is missing. This seems to be a bug - there was no new server found, only the existing cdk adapter.
> !cdk-repetitive-detection.png!
> I checked again on a clean installation and was able to reproduce easily - a simple IDE restart will do. See the steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years