[
https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi...
]
Dmitrii Bocharov commented on JBIDE-22626:
------------------------------------------
[~jeffmaury] [~jcantrill], great thanks for your replies!
[~jeffmaury] no, i'm not adding a new container. I'm calling
DefaultClient.update() and as a proof the request is a PUT request: see my comment:
{method=PUT,
url=https://10.1.2.2:8443/oapi/v1/namespaces/sample-project/deploymentconfigs/aloha,
tag=null}
[~jcantrill] yes, _refresh_ is working exactly like this - returns the latest version of
the resource to later be updated. And this is the thing i'm doing. Firstly i get DC
from connection, see my example for servceaboce: _stubService_ method, where
_findServiceFor(parameters.getProject().getName())_ exactly calls _connection.refresh()_
and then i set new parameters for them (e.g. from deploy wizard) and try to call
_connection.update()_. And it works for Route, ImageStream(can see added new tag in web
console), but doesn't work for DC.
I'll try to update the line to which you provided the link.
About the second container, yes, that's really strange. I'll try to work on it
again to replicate.
Updating deployed docker image on OpenShift does not work
---------------------------------------------------------
Key: JBIDE-22626
URL:
https://issues.jboss.org/browse/JBIDE-22626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Final
Reporter: Marián Labuda
Assignee: Dmitrii Bocharov
Priority: Critical
Labels: docker, openshift_v3
Fix For: 4.4.1.Final
In JBIDE-22515 was fixed use case when user have an image with specific tag. That works
now ok.
But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this
specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything
finish without an error. No new resources are created, but no existing resources are
modified to contain this new image. Deployment config still contains tag :0.8 and thus new
deployment is not done.
Basically we need to modify deployment config in such cases to contains newer tag and let
OpenShift do all magic and redeploy it.
In order to add this version tag after semicolon, right-click on the image -> Add tag
-> Re-type namespace/imagename + add ":0.8" e.g.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)