[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23152:
------------------------------------------
could reproduce and verify the fix with the 2nd scenarion.
merged PR into master.
> 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
> Assignee: Dmitrii Bocharov
> Labels: openshift, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: Dockerfile
>
>
> 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, 8 months
[JBoss JIRA] (JBIDE-23210) Application wizard: builder image application are created all the time for first project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23210 at 10/3/16 11:26 AM:
--------------------------------------------------------------------
"Deploy Docker Image..." (in the context menu of projects in the OpenShift explorer) wasnt loading projects. The fix & making sure projects are only loaded once (from the same connection) is in https://github.com/jbosstools/jbosstools-openshift/pull/1333
was (Author: adietish):
"Deploy Docker Image..." wasnt loading project, fix and making sure projects are only loaded once (from the same connection) is in https://github.com/jbosstools/jbosstools-openshift/pull/1333
> Application wizard: builder image application are created all the time for first project
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-23210
> URL: https://issues.jboss.org/browse/JBIDE-23210
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Environment: # openshift version
> openshift v3.2.1.15
> kubernetes v1.2.0-36-g4a3f9c5
> etcd 2.2.5
> Reporter: Peng Li
> Assignee: Andre Dietisheim
> Labels: application_wizard, deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png
>
>
> Creation of an application based on builder image ignore preselected project and is created on first project all the time. This is happening only for builder images. Template based application are not affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-23210) Application wizard: builder image application are created all the time for first project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23210:
----------------------------------------
Assignee: Andre Dietisheim
Resolution: Done
merged into master
> Application wizard: builder image application are created all the time for first project
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-23210
> URL: https://issues.jboss.org/browse/JBIDE-23210
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Environment: # openshift version
> openshift v3.2.1.15
> kubernetes v1.2.0-36-g4a3f9c5
> etcd 2.2.5
> Reporter: Peng Li
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png
>
>
> Creation of an application based on builder image ignore preselected project and is created on first project all the time. This is happening only for builder images. Template based application are not affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-23210) Application wizard: builder image application are created all the time for first project
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23210:
-------------------------------------
Labels: application_wizard deploy_docker_wizard openshift_v3 (was: application_wizard openshift_v3)
> Application wizard: builder image application are created all the time for first project
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-23210
> URL: https://issues.jboss.org/browse/JBIDE-23210
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Environment: # openshift version
> openshift v3.2.1.15
> kubernetes v1.2.0-36-g4a3f9c5
> etcd 2.2.5
> Reporter: Peng Li
> Assignee: Andre Dietisheim
> Labels: application_wizard, deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png
>
>
> Creation of an application based on builder image ignore preselected project and is created on first project all the time. This is happening only for builder images. Template based application are not affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22767:
----------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> Deploy Docker Wizard: Create image stream contains wrong tags in some cases
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22767
> URL: https://issues.jboss.org/browse/JBIDE-22767
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.4.2.AM2
>
>
> In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...).
> Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image.
> Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-23281) CoreException below ArquillianUIUtil.getArquillianProperties (thrown in StringSubstitutionEngine.resolve)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23281?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-23281:
----------------------------------
Fix Version/s: 4.4.2.AM2
> CoreException below ArquillianUIUtil.getArquillianProperties (thrown in StringSubstitutionEngine.resolve)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23281
> URL: https://issues.jboss.org/browse/JBIDE-23281
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.2.AM1
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Reference to undefined variable JBOSS_HOME
> {noformat}
> org.eclipse.core.runtime.CoreException: Reference to undefined variable JBOSS_HOME
> at org.eclipse.core.internal.variables.StringSubstitutionEngine.resolve(StringSubstitutionEngine.java:261)
> at org.eclipse.core.internal.variables.StringSubstitutionEngine.substitute(StringSubstitutionEngine.java:192)
> at org.eclipse.core.internal.variables.StringSubstitutionEngine.performStringSubstitution(StringSubstitutionEngine.java:87)
> at org.eclipse.core.internal.variables.StringVariableManager.performStringSubstitution(StringVariableManager.java:591)
> at org.eclipse.core.internal.variables.StringVariableManager.performStringSubstitution(StringVariableManager.java:357)
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:460)
> at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:644)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:208)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:766)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:637)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:654)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:615)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:590)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:878)
> 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.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:875)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1244)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1270)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.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:4024)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.core.variables | 3.3.0.v20160419-1720 | 3.3.0.v20160419-1720 |
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.arquillian.ui | 1.2.200.v20160607-1706 | 1.2.200.v20160607-1706 |
> Operating Systems:
> | MacOSX | 10.12.0 | 10.12.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57e68cade4b06c2b2e...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months