[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22810:
-------------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> OpenShift Explorer: empty at start
> ----------------------------------
>
> Key: JBIDE-22810
> URL: https://issues.jboss.org/browse/JBIDE-22810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.2.AM1
>
> Attachments: EmptyViewAtStart.png
>
>
> When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections.
> I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22915:
-------------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Deploy Docker Image: Replication controller is not created for some images
> --------------------------------------------------------------------------
>
> Key: JBIDE-22915
> URL: https://issues.jboss.org/browse/JBIDE-22915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM1
>
>
> When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1")
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22239:
------------------------------------------
[~jcantrill] can you please comment? I'm unsure.
> Allow a user to choose to permanently update their desired replicas for their deployment
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22239
> URL: https://issues.jboss.org/browse/JBIDE-22239
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3
> Fix For: 4.4.1.Final
>
>
> When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest:
> * Adding a custom dialog in the "..to.." option
> * Update to use a spinner
> * Add a checkbox to 'make the change perminent'
> * If checkbox=true, you should only need to update the dc if it has a configchange trigger.
> * Optionally show checkbox if unable to determine the dc associated with the deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21857:
-------------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.4.2.AM1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months