[JBoss JIRA] (JBIDE-22959) Properties: rename Deployment to Replication Controller
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22959?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22959:
---------------------------------------
In OpenShift 1.3.0.Alpha3 release notes I see that OpenShift is gathering sense of Kubernetes deployments and it is gonna be somehow align in future. So maybe for now it's OK if web UI uses same terminology as you pointed, but in future we should this keep in mind.
> Properties: rename Deployment to Replication Controller
> -------------------------------------------------------
>
> Key: JBIDE-22959
> URL: https://issues.jboss.org/browse/JBIDE-22959
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.4.x
>
>
> We should rename Deployment in tabbed properties to Replication Controller. I was complaining about it some times ago, but now I found also good reason to change it - underlying Kubernetes technology has Deployment resources and ReplicaSets (new generation of replication controller). And those resources are something a bit different although it has similar functionality. For users coming from Kubernetes world or those who are familiar with Kubernetes, could this be a bit misleading.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23005:
-------------------------------------
Fix Version/s: 4.4.1.Final
> Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.Final
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-23005 at 8/16/16 6:46 AM:
----------------------------------------------------------------
Not sure what happened. I was able to reproduce it all the time yesterday, but today I switched to another workspace and its more difficult to reproduce. Basically sometimes there is a building workspace job or some JPA job and publishing to OpenShift job and those are somehow blocked/stucked. Sometimes there was only publishing job which hanged there for minutes and nothing happened.
Now I was able to reproduce it. I am having a workspace project jboss-kitchensink with an application on OpenShift (CDK) and server adapter for it. I restarted IDE and reenabled OpenShift 3 connection. Then I selected the server adapter and tried to start it. It was hanging for minutes and then rsync output in console has been shown. Speed of file transer seems to be ok and it should be done in blink of an eye. See attached jstack.
was (Author: mlabuda):
Not sure what happened. I was able to reproduce it all the time yesterday, but today I switched to another workspace and its more difficult to reproduce. Basically sometimes there is a building workspace job or some JPA job and publishing to OpenShift job and those are somehow blocked/stucked. Sometimes there was only publishing job which hanged there for minutes and nothing happened.
Now I was able to reproduce it. I am having a workspace project jboss-kitchensink with an application on OpenShift (CDK) and server adapter for it. I restarted IDE and reenabled OpenShift 3 connection. Then I selected the server adapter and tried to start it. It was hanging for minutes and then rsync output in console has been shown. See attached jstack.
> Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23005:
----------------------------------
Attachment: stucked_server_adapter
> Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23005:
---------------------------------------
Not sure what happened. I was able to reproduce it all the time yesterday, but today I switched to another workspace and its more difficult to reproduce. Basically sometimes there is a building workspace job or some JPA job and publishing to OpenShift job and those are somehow blocked/stucked. Sometimes there was only publishing job which hanged there for minutes and nothing happened.
Now I was able to reproduce it. I am having a workspace project jboss-kitchensink with an application on OpenShift (CDK) and server adapter for it. I restarted IDE and reenabled OpenShift 3 connection. Then I selected the server adapter and tried to start it. It was hanging for minutes and then rsync output in console has been shown. See attached jstack.
> Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22853) Missing connection error shows sometimes on existing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22853?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22853:
-------------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.1.Final)
> Missing connection error shows sometimes on existing connection
> ---------------------------------------------------------------
>
> Key: JBIDE-22853
> URL: https://issues.jboss.org/browse/JBIDE-22853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: connection, openshift_v3
> Fix For: 4.4.1.AM3
>
>
> Sometimes when I am working with console.engint.openshift.com instance where I use OAuth authentication, I get following error in error log with no stack trace when trying to create a project or application on a connection
> {code}
> Could not create project, missing connection.
> {code}
> Then when I open Edit Connection wizard via context menu of the connection, there is an error in header of the wizard "Connection for the server with this token already exists."
> Not sure what precisely it is causing and how to reproduce it with success rate 100 %.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22853) Missing connection error shows sometimes on existing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22853?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-22853.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Cannot Reproduce Bug
> Missing connection error shows sometimes on existing connection
> ---------------------------------------------------------------
>
> Key: JBIDE-22853
> URL: https://issues.jboss.org/browse/JBIDE-22853
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: connection, openshift_v3
> Fix For: 4.4.1.AM3
>
>
> Sometimes when I am working with console.engint.openshift.com instance where I use OAuth authentication, I get following error in error log with no stack trace when trying to create a project or application on a connection
> {code}
> Could not create project, missing connection.
> {code}
> Then when I open Edit Connection wizard via context menu of the connection, there is an error in header of the wizard "Connection for the server with this token already exists."
> Not sure what precisely it is causing and how to reproduce it with success rate 100 %.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23002) Connection Wizard: Remove sign up link for a new OS 2 account
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23002?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23002:
-------------------------------------
Issue Type: Enhancement (was: Feature Request)
> Connection Wizard: Remove sign up link for a new OS 2 account
> -------------------------------------------------------------
>
> Key: JBIDE-23002
> URL: https://issues.jboss.org/browse/JBIDE-23002
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Priority: Optional
> Labels: connection_wizard, openshift_v2
> Fix For: 4.4.1.Final
>
>
> As of August 1st. new OpenShift 2 accounts are not created anymore. Users are advised to start using OpenShift 3. We could remove link "If you do not have an account on OpenShift 2, please sign up here." from OpenShift Connection wizad.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23002) Connection Wizard: Remove sign up link for a new OS 2 account
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23002?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23002:
-------------------------------------
Priority: Major (was: Optional)
> Connection Wizard: Remove sign up link for a new OS 2 account
> -------------------------------------------------------------
>
> Key: JBIDE-23002
> URL: https://issues.jboss.org/browse/JBIDE-23002
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: connection_wizard, openshift_v2
> Fix For: 4.4.1.Final
>
>
> As of August 1st. new OpenShift 2 accounts are not created anymore. Users are advised to start using OpenShift 3. We could remove link "If you do not have an account on OpenShift 2, please sign up here." from OpenShift Connection wizad.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23001) Application Wizard: NPE when opening OS 2 wizard from central or shell menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23001?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23001:
-------------------------------------
Priority: Critical (was: Major)
> Application Wizard: NPE when opening OS 2 wizard from central or shell menu
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23001
> URL: https://issues.jboss.org/browse/JBIDE-23001
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: application_wizard, openshift_v2, regression
> Fix For: 4.4.1.Final
>
>
> When I am opening a New OpenShift Application wizard for OpenShift 2 connections, I get an NPE. This is caused only when opening wizard from shell menu File - New - OpenShift Application or from Central.
> stack trace of NPE:
> {code}
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:408)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121)
> at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537)
> at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months