[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23152:
-------------------------------
Description:
EXEC: first deploy jboss-eap64-openshift builder image
ASSERT: wait until deployment is finished
EXEC: delete the deployment
EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
As this first scenario seems to be valid only if you're working with CDK2.2 and no proxy set, here is a scenario valid for all versions of CDK:
ASSERT: have a Docker file with an empty ENV value. You can use https://github.com/redhat-helloworld-msa/aloha and edit the Docker file and add the following statement:
{quote}ENV NOVALUE ""{quote}
EXEC: build the Docker image on the CDK Docker connection. If you use aloha (https://github.com/redhat-helloworld-msa/aloha), then you must beforehand run the "mvn package" command to get binary artifacts being produced. Select the Dockerfile, click *_Run As -> Docker Image Build_*, select the CDK Docker connection and give *_msa/aloha:1_* as image name
ASSERT: your Docker image has been generated
EXEC: from the Openshift explorer, select the *_Deploy Docker Image_*, then select the CDK Docker Connection, then click on *_Browse_* and select the *_msa/aloha:1_* image, then click on the Next button
ASSERT: you should get an error
was:
EXEC: first deploy jboss-eap64-openshift builder image
ASSERT: wait until deployment is finished
EXEC: delete the deployment
EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
> NPE when deploying image with ENV with no value
> -----------------------------------------------
>
> Key: JBIDE-23152
> URL: https://issues.jboss.org/browse/JBIDE-23152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
>
> EXEC: first deploy jboss-eap64-openshift builder image
> ASSERT: wait until deployment is finished
> EXEC: delete the deployment
> EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd)
> ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=)
> As this first scenario seems to be valid only if you're working with CDK2.2 and no proxy set, here is a scenario valid for all versions of CDK:
> ASSERT: have a Docker file with an empty ENV value. You can use https://github.com/redhat-helloworld-msa/aloha and edit the Docker file and add the following statement:
> {quote}ENV NOVALUE ""{quote}
> EXEC: build the Docker image on the CDK Docker connection. If you use aloha (https://github.com/redhat-helloworld-msa/aloha), then you must beforehand run the "mvn package" command to get binary artifacts being produced. Select the Dockerfile, click *_Run As -> Docker Image Build_*, select the CDK Docker connection and give *_msa/aloha:1_* as image name
> ASSERT: your Docker image has been generated
> EXEC: from the Openshift explorer, select the *_Deploy Docker Image_*, then select the CDK Docker Connection, then click on *_Browse_* and select the *_msa/aloha:1_* image, then click on the Next button
> ASSERT: you should get an error
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3903:
---------------------------------
[~xcoulon], any thoughts about the above?
> Platform Installer does not Setup Docker Env-Vars
> -------------------------------------------------
>
> Key: JBDS-3903
> URL: https://issues.jboss.org/browse/JBDS-3903
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 10.0.0.Alpha1
> Environment: Windows
> Reporter: Thomas Mäder
> Assignee: Xavier Coulon
>
> I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection.
> Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection.
> As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23029 at 9/13/16 5:07 AM:
-------------------------------------------------------------------
[~mlabuda] Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
I created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. *dont merge it yet*, please (I need to remove the changes to ScalingTest, that I used to test this, first)
was (Author: adietish):
[~mlabuda] Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
I created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. *dont merge it yet, please* (I need to remove the changes to ScalingTest, that I used to test this, first)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.2.Final
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23029 at 9/13/16 5:07 AM:
-------------------------------------------------------------------
[~mlabuda] Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
I created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. *dont merge it yet, please* (I need to remove the changes to ScalingTest, that I used to test this, first)
was (Author: adietish):
[~mlabuda] Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
I created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. DONT MERGE YET (I need to remove the changes to ScalingTest, that I used to test this, first)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.2.Final
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23029 at 9/13/16 5:06 AM:
-------------------------------------------------------------------
[~mlabuda] Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
I created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. DONT MERGE YET (I need to remove the changes to ScalingTest, that I used to test this, first)
was (Author: adietish):
Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
[~mlabuda] created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. DONT MERGE YET (I need to remove the changes to ScalingTest, that I used to test this, first)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.2.Final
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23029:
------------------------------------------
Annotating a test-class with the red deer runner works ok for now. I guess we can postpone further improvements to later.
[~mlabuda] created a preliminary PR here https://github.com/jbosstools/jbosstools-integration-tests/pull/1609
Please have a look and comment. DONT MERGE YET (I need to remove the changes to ScalingTest, that I used to test this, first)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.2.Final
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-23031.
---------------------------------
Verified in JBT 4.4.1.Final with docker core plugin 20160831.
> OpenShift can't push Docker Images with latest Docker Neon.1 bits
> -----------------------------------------------------------------
>
> Key: JBIDE-23031
> URL: https://issues.jboss.org/browse/JBIDE-23031
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Environment: DevStudio 10.1.0.AM3
> Docker Tooling 2.1.0.201608221023
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22640 at 9/13/16 4:37 AM:
----------------------------------------------------------------
Reopening for clarification. I think better solution would be delete server adapter on a connection deletion (cascade it). Because what is the reason to keep such a server adapter?
was (Author: mlabuda):
Reopening for clarification.
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final, 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.2.AM2
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23014:
------------------------------------------
merged into master
> Allow connections to configure the cluster namespace from which to get clusterwide templates
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23014
> URL: https://issues.jboss.org/browse/JBIDE-23014
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Jeff Cantrill
> Assignee: Jeff MAURY
> Labels: connection, connection_wizard, new_and_noteworthy, openshift, openshift_v3
> Fix For: 4.4.2.AM1
>
>
> There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months