'oc apply' consistently fails to update deploymentconfigs after creation with origin 3.7.0 #17998
Comments
pweil-
added
component/apps
kind/bug
|
@mc-meta how do you create the apps? does the DC have trigger? Also can you gist the result of |
|
Hi @mfojtik , as I'm working with @mc-meta on this I can provide some first feedback to you. The apps are created with The "add the prefix" part was not something we wanted/needed to do, it was just a workaround that seems to actually work, we mentioned it to help pinpointing the root cause. I'll have a go at |
|
Hi again @mfojtik , I'm attaching log files as requested. output-0.log refers to the first output-1.log refers to a second |
|
I have the same issue. Usually I would expect apply to update the configs, but my changes are not applied to the configs I defined in a template. Any updates on this? Basically what I try to do is to apply a template to the project after a build in case something changed in the setup. Bad idea? |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
When running a simple (silly) teaching demo workflow at:
on minishift(with 3.7.0)/openshift origin 3.7.0 we are facing some problems that were not there in previous versions (e.g. 3.6.1).
We are able to initially deploy the applications and create deployment configs via 'oc apply -f'.
App components come up just fine and all works as expected, but subsequent invocations to update deploymentconfigs fail with ImagePullBackOff and at some point dc deployment is rolledback.
From relevant errors, this seems to be related with the use of relative image coordinates:
If we prefix image reference with default registry docker-registry.default.svc:5000, 'oc apply' works as expected and problem seems to disappear:
As anticipated, this behaviour is not present on openshift versions <= 3.6.1 and 'oc apply' is able to consistently update existing objects even with references to relative images.
Version
[root@mid1-s101orig-1 ~]# oc version
oc v3.7.0+7ed6862
kubernetes v1.7.6+a08f5eeb62
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://origin-cluster-stg.dodi.tech:8443
openshift v3.7.0+7ed6862
kubernetes v1.7.6+a08f5eeb62
Steps To Reproduce
Current Result
pods are not coming up with ImagePullBackOff and at some point dc deployment is rolledback:
Expected Result
Be able to do simple updates to deploymentconfigs with 'oc apply' even when relative image references are present (as during initial creation)
Additional Information
Same behaviour seems to be present on minishift with 3.7.0. A similar report has already been filed with minishift/minishift#1821 and relevant origin issue #17705
Thanks for any insight.
The text was updated successfully, but these errors were encountered: