[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22362.
-------------------------------
Verified in the latest 4.4.3 nightly.
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
> Attachments: enabling-dev-mode-has-encountered-an-error.png
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3951.
-----------------------------
Verified in master and 1.3.0 latest.
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.3.0.GA
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-22228) Server adapter: NPE when deploying to Openshift EAP
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22228.
-------------------------------
Closing as not reproducible.
> Server adapter: NPE when deploying to Openshift EAP
> ---------------------------------------------------
>
> Key: JBIDE-22228
> URL: https://issues.jboss.org/browse/JBIDE-22228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> When I try to publish to an EAP in the CDK, I get a NullPointerException:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-23817.
-------------------------------
Works for me in the latest 4.4.3 nightly, closing.
> Scaling: is not working with OpenShift 3.4 (CDK 2.4)
> ----------------------------------------------------
>
> Key: JBIDE-23817
> URL: https://issues.jboss.org/browse/JBIDE-23817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: CDK 2.4
> Devstudio 10.3.0.AM2
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.Final
>
> Attachments: Spectacle.yJ3971.png
>
>
> Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now).
> When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again.
> This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month