[JBoss JIRA] (JBIDE-22166) NullPointerException in CDICoreNature.dispose
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22166?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22166:
-------------------------------------
https://github.com/jbosstools/jbosstools-javaee/pull/396
> NullPointerException in CDICoreNature.dispose
> ---------------------------------------------
>
> Key: JBIDE-22166
> URL: https://issues.jboss.org/browse/JBIDE-22166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.CR1
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.Alpha1
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.core.CDICoreNature.dispose(CDICoreNature.java:721)
> at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:96)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
> at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:265)
> at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:368)
> at org.eclipse.core.internal.resources.Project.move(Project.java:964)
> at org.eclipse.jdt.internal.corext.refactoring.changes.RenameJavaProjectChange.doRename(RenameJavaProjectChange.java:76)
> at org.eclipse.jdt.internal.corext.refactoring.AbstractJavaElementRenameChange.perform(AbstractJavaElementRenameChange.java:89)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.access$0(DynamicValidationStateChange.java:1)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange$1.run(DynamicValidationStateChange.java:113)
> at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5409)
> at org.eclipse.jdt.internal.corext.refactoring.changes.DynamicValidationStateChange.perform(DynamicValidationStateChange.java:116)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
> at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160310-1245 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160222-1238 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160118-2055 |
> | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.7.0.v20160120-1732 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20151129-1935 |
> | org.eclipse.team.svn | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.svn.core | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.svn.ui | 3.0.3.I20151228-1700 | 3.0.3.I20151228-1700 |
> | org.eclipse.team.ui | 3.7.300.v20151117-1911 | 3.7.300.v20151117-1911 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20160108-0627 |
> | org.jboss.tools.cdi.core | 1.7.1.CR1-v20160129-2014-B69 | 1.8.0.Alpha1-v20160108-2123-B916 |
> Operating Systems:
> | Linux | 4.0.4 | 4.0.4 |
> | MacOSX | 10.10.5 | 10.11.3 |
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [https://redhat.ctrlflow.com/reviewers/#!/problems/56cb04b0e4b0f02ab70a7d85 this page] 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, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22515:
--------------------------------
Steps to Reproduce:
0a - clone and import https://github.com/redhat-helloworld-msa/aloha
0b- in openshift explorer, create a new redhat-helloworld-msa project
1- perform a maven CLI build
2- right click on the DockerFile, Run As Docker Image Build, select CDK docker connection, repo name as foo/aloha
3- right click on redhat-helloworld-msa, Deploy Docker Image...
4- select push image to registry, go next and finish
5- image is pushed, 3 resources are created eventually.
6- app is deployed and accessible online
Docker update:
7- change some response in AlohaVerticle
8- repeat all steps from #1
=> image is pushed but there's an error message popping up about resource conflicts
=> app is still updated properly on openshift
was:
0a - clone and import https://github.com/redhat-helloworld-msa/aloha
0b- once built, go in openshift explorer, create a new redhat-helloworld-msa project
1- perform a maven CLI build
2- right click on the DockerFile, Run As Docker Image Build, select CDK docker connection, repo name as foo/aloha
3- right click on redhat-helloworld-msa, Deploy Docker Image...
4- select push image to registry, go next and finish
5- image is pushed, 3 resources are created eventually.
6- app is deployed and accessible online
Docker update:
7- change some response in AlohaVerticle
8- repeat all steps from #1
=> image is pushed but there's an error message popping up about resource conflicts
=> app is still updated properly on openshift
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22515:
--------------------------------
Priority: Critical (was: Major)
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22515:
--------------------------------
Steps to Reproduce:
0a - clone and import https://github.com/redhat-helloworld-msa/aloha
0b- once built, go in openshift explorer, create a new redhat-helloworld-msa project
1- perform a maven CLI build
2- right click on the DockerFile, Run As Docker Image Build, select CDK docker connection, repo name as foo/aloha
3- right click on redhat-helloworld-msa, Deploy Docker Image...
4- select push image to registry, go next and finish
5- image is pushed, 3 resources are created eventually.
6- app is deployed and accessible online
Docker update:
7- change some response in AlohaVerticle
8- repeat all steps from #1
=> image is pushed but there's an error message popping up about resource conflicts
=> app is still updated properly on openshift
was:
0 - clone and import https://github.com/redhat-helloworld-msa/aloha
1- perform a maven CLI build
2- right click on the DockerFile, Run As Docker Image Build, select CDK docker connection, repo name as foo/aloha
3- once built, go in openshift explorer, create a new redhat-helloworld-msa project
4- right click on redhat-helloworld-msa, Deploy Docker Image...
5- select push image to registry, go next and finish
6- image is pushed, 3 resources are created eventually.
7- app is deployed and accessible online
Docker update:
8- change some response in AlohaVerticle
9- repeat all steps from #1
=> image is pushed but there's an error message popping up about resource conflicts
=> app is still updated properly on openshift
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22515:
--------------------------------
Fix Version/s: 4.4.0.Final
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22515:
--------------------------------
Labels: respin-a (was: )
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22515:
-------------------------------------
tentatively targetting respin-a
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-22515 at 6/3/16 12:06 PM:
--------------------------------------------------------------
tentatively targeting respin-a
was (Author: fbricon):
tentatively targetting respin-a
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-22193.
---------------------------------
Resolution: Done
Fixed with https://github.com/jbosstools/jbosstools-openshift/commit/189fd3dfc006086...
However the scenario where the image is updated has an issue. See following JBIDE-22515
> Can't deploy locally built docker images
> ----------------------------------------
>
> Key: JBIDE-22193
> URL: https://issues.jboss.org/browse/JBIDE-22193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.4.0.Final
>
>
> I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift
> Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything
> Here's what the CLI generates from
> {quote}
> eval "$(vagrant service-manager env docker)"
> $ oc login 10.1.2.2:8443 -u openshift-dev -p devel
> Login successful.
> $ oc new-project my-ghost
> Now using project "my-ghost" on server "https://10.1.2.2:8443".
> $ docker pull ghost
> $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost
> $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io
> $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost
> $ oc new-app --image-stream=ghost --name=ghost
> $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io
> {quote}
> Deployment Config
> {noformat}
> {
> "kind" : "DeploymentConfig",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "ghost",
> "namespace" : "my-ghost",
> "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost",
> "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "29849",
> "creationTimestamp" : "2016-04-16T11:45:02Z",
> "labels" : {"app" : "ghost"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"}
> },
> "spec" : {
> "strategy" : {
> "type" : "Rolling",
> "rollingParams" : {
> "updatePeriodSeconds" : 1,
> "intervalSeconds" : 1,
> "timeoutSeconds" : 600,
> "maxUnavailable" : "25%",
> "maxSurge" : "25%"
> }
> },
> "triggers" : [
> {"type" : "ConfigChange"},
> {
> "type" : "ImageChange",
> "imageChangeParams" : {
> "automatic" : true,
> "containerNames" : ["ghost"],
> "from" : {
> "kind" : "ImageStreamTag",
> "namespace" : "my-ghost",
> "name" : "ghost:latest"
> },
> "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8"
> }
> }
> ],
> "replicas" : 1,
> "selector" : {
> "app" : "ghost",
> "deploymentconfig" : "ghost"
> },
> "template" : {
> "metadata" : {
> "labels" : {
> "app" : "ghost",
> "deploymentconfig" : "ghost"
> },
> "annotations" : {
> "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]",
> "openshift.io/generated-by" : "OpenShiftNewApp"
> }
> },
> "spec" : {
> "volumes" : [{"name" : "ghost-volume-1"}],
> "containers" : [{
> "name" : "ghost",
> "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8",
> "ports" : [{
> "containerPort" : 2368,
> "protocol" : "TCP"
> }],
> "volumeMounts" : [{
> "name" : "ghost-volume-1",
> "mountPath" : "/var/lib/ghost"
> }],
> "terminationMessagePath" : "/dev/termination-log",
> "imagePullPolicy" : "Always"
> }],
> "restartPolicy" : "Always",
> "terminationGracePeriodSeconds" : 30,
> "dnsPolicy" : "ClusterFirst"
> }
> }
> },
> "status" : {
> "latestVersion" : 1,
> "details" : {"causes" : [{"type" : "ConfigChange"}]}
> }
> }
> {noformat}
> Image Stream
> {noformat}
> {
> "kind" : "ImageStream",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "ghost",
> "namespace" : "my-ghost",
> "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost",
> "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "29842",
> "creationTimestamp" : "2016-04-16T11:44:37Z",
> "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"}
> },
> "status" : {
> "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost",
> "tags" : [{
> "tag" : "latest",
> "items" : [{
> "created" : "2016-04-16T11:44:37Z",
> "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8",
> "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8"
> }]
> }]
> }
> }
> {noformat}
> When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy.
> {quote}
> - Clone https://github.com/burrsutter/cdk_helloworlds/
> - import java/wildflyswarm_helloworld as a Maven Project
> - Run a Maven build (Run As > Maven > package)
> - Edit Dockerfile: replace `FROM rhel7` with `FROM centos`
> - right click on Dockerfile > Run As > Docker Image build
> - Select `CDK Server Adapter at localhost` connection
> - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm
> - from OpenShift explorer, create a fredo project
> - In OpenShift explorer, right-click the fredo project and Deploy Docker Image...
> - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image
> - swarm as resource name
> - click next
> - Deployment configuration & scalability page displays, click next
> - click add route button, click finish
> - resources are created, but no deployment happens
> {quote}
> Here are the resources created from Eclipse:
> Deployment Config
> {noformat}
> {
> "metadata" : {
> "name" : "swarm",
> "namespace" : "fredo",
> "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm",
> "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "30206",
> "creationTimestamp" : "2016-04-16T12:10:17Z",
> "labels" : {"deploymentconfig" : "swarm"},
> "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"}
> },
> "spec" : {
> "strategy" : {
> "type" : "Rolling",
> "rollingParams" : {
> "updatePeriodSeconds" : 1,
> "intervalSeconds" : 1,
> "timeoutSeconds" : 600,
> "maxUnavailable" : "25%",
> "maxSurge" : "25%"
> }
> },
> "triggers" : [
> {"type" : "ConfigChange"},
> {
> "type" : "ImageChange",
> "imageChangeParams" : {
> "automatic" : true,
> "containerNames" : ["swarm"],
> "from" : {
> "kind" : "ImageStreamTag",
> "name" : "swarm:latest"
> }
> }
> }
> ],
> "replicas" : 1,
> "selector" : {"deploymentconfig" : "swarm"},
> "template" : {
> "metadata" : {"labels" : {"deploymentconfig" : "swarm"}},
> "spec" : {
> "containers" : [{
> "name" : "swarm",
> "image" : "fredo/swarm:latest",
> "ports" : [{
> "name" : "8080-tcp",
> "containerPort" : 8080,
> "protocol" : "TCP"
> }],
> "terminationMessagePath" : "/dev/termination-log",
> "imagePullPolicy" : "Always"
> }],
> "restartPolicy" : "Always",
> "terminationGracePeriodSeconds" : 30,
> "dnsPolicy" : "ClusterFirst"
> }
> }
> },
> "apiVersion" : "v1",
> "kind" : "DeploymentConfig"
> }
> {noformat}
> Image Stream
> {noformat}
> {
> "metadata" : {
> "name" : "swarm",
> "namespace" : "fredo",
> "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm",
> "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "30202",
> "creationTimestamp" : "2016-04-16T12:10:16Z",
> "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"}
> },
> "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"},
> "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"},
> "apiVersion" : "v1",
> "kind" : "ImageStream"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months