[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 updated JBIDE-25670:
-------------------------------------
Fix Version/s: 4.5.3.Final
(was: 4.5.x)
> 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)
7 years, 6 months
[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 updated JBIDE-25670:
-------------------------------------
Sprint: devex #147 April 2018
> 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)
7 years, 6 months
[JBoss JIRA] (JBIDE-25836) Windows overlapping when selecting a quick fix in runtime detection dialog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25836?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25836:
-------------------------------------
So, it's disappearing as proper on linux. We have code to hide it once the new file-chooser is opened:
{code}
Listener hideUnfocusedPopup = new Listener() {
public void handleEvent(final Event event) {
Display.getDefault().asyncExec(new Runnable() {
public void run() {
Widget w = event.widget;
Control control = Display.getDefault().getFocusControl();
if (control == null || (control != getTree() && control != popupTable)) {
popupShell.setVisible(false);
}
}
});
}
};
{code}
And this is the stack trace showing the focusOut event is called which then hides the shell:
{code}
Shell.setVisible(boolean) line: 2359
RuntimeCheckboxTreeViewer$5$1.run() line: 180
RunnableLock.run(Display) line: 37
UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 182
Display.runAsyncMessages(boolean) line: 4497
Display.idleProc(long) line: 3194
OS._gtk_dialog_run(long) line: not available [native method]
OS.gtk_dialog_run(long) line: 6940
FileDialog.openChooserDialog() line: 349
FileDialog.open() line: 300
MissingMinishiftResolutionProvider$MissingMinishiftResolution.getFile(File, Shell) line: 52
{code}
If the shell is there, it must somehow not be getting the focusOut event during FileDialog.open().
> Windows overlapping when selecting a quick fix in runtime detection dialog
> --------------------------------------------------------------------------
>
> Key: JBIDE-25836
> URL: https://issues.jboss.org/browse/JBIDE-25836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: set-minishift-location.png
>
>
> The quickfix column of runtime detection will show a sort of a tooltip with list of actions when you click the errors. This tooltip/window is somehow broken - it will be displayed above everything all the time. So even if I select "Set minishift binary location" and a file picker is opened, this tooltip is above the file picker and obstructs my selection.
> !set-minishift-location.png!
> Side question: Why is the tooltip so big even if there is just one action?
> This is on Mac. Latest nightly of devstudio 11.3.0.AM3.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25901) MINISHIFT_HOME is not propagated to new detected cdk binary properly
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25901?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-25901:
---------------------------------------
[~adietish] we're discussing this issue with Rob ATM and we ended up agreeing that probably not that much needs to change. Once we're done we will sum up the current functionality and add it to https://issues.jboss.org/browse/RHDEVDOCS-724 to be documented.
As to what $MINISHIFT_HOME is for: In CLI, by default, ~/.minishift is used for storing of all the data, but you can change this by defining your MINISHIFT_HOME env var and pointing it to another directory. That way minishift/cdk will use that directory instead.
There was a feature request a while back to support this variable in devstudio, i.e. use the custom directory instead of the default (if $MINISHIFT_HOME is set for the Eclipse process). But it turns out that this is quite a pain to do right - you don't always want to use this, especially if you download a new CDK binary directly in Eclipse.
> MINISHIFT_HOME is not propagated to new detected cdk binary properly
> --------------------------------------------------------------------
>
> Key: JBIDE-25901
> URL: https://issues.jboss.org/browse/JBIDE-25901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Following some of the changes to how cdk and runtime detection works (most notably that path to cdk binary can now be used for searching), I wanted to try and see if $MINISHIFT_HOME is still respected and works properly. And it seems to fail.
> I started devstudio with MINISHIFT_HOME=/Users/rasp/minishift_home, then ran runtime detection against /Users/rasp/tmp where a cdk binary was found. But the newly created adapter had this set up as minishift home: /Users/rasp/tmp/MINISHIFT_HOME
> That seems totally wrong.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25901) MINISHIFT_HOME is not propagated to new detected cdk binary properly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25901?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25901:
------------------------------------------
[~mmalina] I'm a bit of a noob in this area, what is the purpose of $MINISHIFT_HOME? How is your setup affected if this variable isnt set properly?
> MINISHIFT_HOME is not propagated to new detected cdk binary properly
> --------------------------------------------------------------------
>
> Key: JBIDE-25901
> URL: https://issues.jboss.org/browse/JBIDE-25901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> Following some of the changes to how cdk and runtime detection works (most notably that path to cdk binary can now be used for searching), I wanted to try and see if $MINISHIFT_HOME is still respected and works properly. And it seems to fail.
> I started devstudio with MINISHIFT_HOME=/Users/rasp/minishift_home, then ran runtime detection against /Users/rasp/tmp where a cdk binary was found. But the newly created adapter had this set up as minishift home: /Users/rasp/tmp/MINISHIFT_HOME
> That seems totally wrong.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25871) Server adapter: spring-boot-camel-xml adapter cannot rsync: no rsync nor tar available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25871?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25871:
------------------------------------------
I currently experience odd behaviours with OSO east2, the camel/springboot demo app template is not fully executing, it won't create the service. When then trying to remove the partial resources nothing happens, in Eclipse and in Web UI.
> Server adapter: spring-boot-camel-xml adapter cannot rsync: no rsync nor tar available
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25871
> URL: https://issues.jboss.org/browse/JBIDE-25871
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: rsync, server_adapter, springboot
> Fix For: 4.5.3.Final
>
> Attachments: fuse-on-openshift.zip, pod-running.png, rsync-fails.png
>
>
> # ASSERT: have project *camel-ose-springboot-xml* imported to your workspace (from attached archive fuse-on-openshift)
> # ASSERT: have a connection to https://console.starter-us-east-2.openshift.com with a project *<username>-stage*
> # EXEC: deploy project *camel-ose-springboot-xml* project via fabric-8 maven plugin:
> {code}
> mvn clean install fabric8:deploy \
> -Dkubernetes.master=https://console.starter-us-east-2.openshift.com \
> -Dkubernetes.namespace=adietish-stage \
> -Dkubernetes.auth.basic.username=<username> \
> -Dkubernetes.auth.basic.password=<password> \
> -Dfabric8.mode=openshift \
> -Dkubernetes.trust.certificates=true \
> -Dfabric8.build.strategy=s2i \
> -Dkubernetes.auth.tryServiceAccount=false \
> -Dfabric8.generator.from=fabric8/s2i-java \
> -Dfabric8.generator.fromMode=docker \
> -Dkubernetes.auth.tryKubeConfig=false
> {code}
> # ASSERT: you have a pod running for a service *camel-ose-springboot-xml*
> !pod-running.png!
> # EXEC: create a server adapter for your service *camel-ose-springboot-xml*
> # ASSERT: adapter starts automatically and starts to sync local project to OpenShift
> Result:
> RSync fails, you're told that the container has no strategy for syncing, neither rsync nor tar are available.
> !rsync-fails.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25672) Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25672?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25672:
------------------------------------------
[~dbocharov] please rievew https://github.com/jbosstools/jbosstools-openshift/pull/1717. Thx!
> Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25672
> URL: https://issues.jboss.org/browse/JBIDE-25672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.5.3.Final
>
> Attachments: image-2018-01-29-15-48-29-101.png
>
>
> # ASSERT: have a connection to open.paas.redhat.com
> # EXEC: create a new app based on the "s2i-spring-boot-camel-xml" template. Have the project imported to your workspace and the server adapter created
> # ASSERT: a server adapter "s2i-spring-boot-camel-xml" is created
> # EXEC: wait for the adapter to get "[started]"
> Result:
> After some waiting time the adapter throws the following error:
> !image-2018-01-29-15-48-29-101.png!
> In the Eclipse log you find the following:
> {code}
> !MESSAGE Could not launch server s2i-spring-boot-camel-xml (DeploymentConfig) at OpenShift 3 (open.paas.redhat.com)
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.tools.openshift.internal.core.server.debug.DebugContext.<init>(DebugContext.java:64)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.createDebugContext(OpenShiftLaunchController.java:199)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:93)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25672) Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25672?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25672:
------------------------------------------
I cannot reproduce this any longer. So I went for improving the error message which should by itself improve the user experience: https://github.com/jbosstools/jbosstools-openshift/pull/1717
> Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25672
> URL: https://issues.jboss.org/browse/JBIDE-25672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.5.3.Final
>
> Attachments: image-2018-01-29-15-48-29-101.png
>
>
> # ASSERT: have a connection to open.paas.redhat.com
> # EXEC: create a new app based on the "s2i-spring-boot-camel-xml" template. Have the project imported to your workspace and the server adapter created
> # ASSERT: a server adapter "s2i-spring-boot-camel-xml" is created
> # EXEC: wait for the adapter to get "[started]"
> Result:
> After some waiting time the adapter throws the following error:
> !image-2018-01-29-15-48-29-101.png!
> In the Eclipse log you find the following:
> {code}
> !MESSAGE Could not launch server s2i-spring-boot-camel-xml (DeploymentConfig) at OpenShift 3 (open.paas.redhat.com)
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.tools.openshift.internal.core.server.debug.DebugContext.<init>(DebugContext.java:64)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.createDebugContext(OpenShiftLaunchController.java:199)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:93)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months