Also can you run this with --loglevel=10 and check what is being sent to the server when the forbidden error occurs?
We are trying to find out what changed in the Pod spec that is breaking update. On 22 August 2017 at 12:22:37, Michal Fojtik ([email protected]) wrote: > That is after you switched to 3.6? Does this affect all pods or just some? > Does the pods that can't be edited have secret volumes? > > > On 22 August 2017 at 12:05:11, Stéphane Klein ([email protected]) > wrote: > > When I try to edit pods : > > > > oc edit pod app-2-8bh3m > > > > If I update a label I have this error: > > > > # Please edit the object below. Lines beginning with a '#' will be ignored, > > # and an empty file will abort the edit. If an error occurs while saving > > this file will be > > # reopened with the relevant failures. > > # > > # pods "app-2-8bh3m" was not valid: > > # * spec: Forbidden: pod updates may not change fields other than > > `containers[*].image` or `spec.activeDeadlineSeconds` > > # > > apiVersion: v1 > > kind: Pod > > metadata: > > annotations: > > kubernetes.io/created-by: | > > > > {"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicationController","namespace":"groulot","name":"app-2","uid":"b8debf4a-8705-11e7-bd32-005056b1755a","apiVersion":"v1","resourceVersion":"26178167"}} > > openshift.io/deployment-config.latest-version: "2" > > openshift.io/deployment-config.name: app > > openshift.io/deployment.name: app-2 > > openshift.io/scc: groulot > > creationTimestamp: 2017-08-22T06:47:17Z > > generateName: app-2- > > labels: > > deployment: app-2-test > > deploymentconfig: app > > name: app > > name: app-2-8bh3m > > namespace: groulot > > resourceVersion: "26178220" > > selfLink: /api/v1/namespaces/groulot/pods/app-2-8bh3m > > uid: bd079ad1-8705-11e7-bd32-005056b1755a > > spec: > > containers: > > - image: > > 172.30.201.95:5000/openshift/ta-s2i-php-prod@sha256:f6da85d9b0aada51f45f776d8c04941f7ada1fe0219776b5eb0ccb1bab20a3e3 > > imagePullPolicy: Always > > name: app > > ... > > > > 2017-08-22 11:35 GMT+02:00 Michal Fojtik : > > > > > Can you please post the YAML representation of the > > > 'test-secret-6-qz4ar' pod? Or another > > > pod that failed. > > > > > > Thanks! > > > > > > > > > On 21 August 2017 at 23:49:56, Stéphane Klein > > > ([email protected]) wrote: > > > > Hi, > > > > > > > > when I try to upgrade OpenShift Origin v1.5.1 cluster to v3.6.0 I have > > > many > > > > errors when Ansible execute « Upgrade all storage » task: > > > > https://github.com/openshift/openshift-ansible/blob/ > > > release-3.6/playbooks/common/openshift-cluster/upgrades/ > > > upgrade_control_plane.yml#L11 > > > > > > > > Many line errors like: > > > > > > > > error: pods/test-secret-6-qz4ar -n issue-29059: Pod > > > > \"test-secret-6-qz4ar\" is invalid: spec: Forbidden: pod updates may not > > > > change fields other than `containers[*].image` or > > > > `spec.activeDeadlineSeconds` > > > > > > > > What is it? How can I fix it? > > > > > > > > Best regards, > > > > Stéphane > > > > -- > > > > Stéphane Klein > > > > blog: http://stephane-klein.info > > > > cv : http://cv.stephane-klein.info > > > > Twitter: http://twitter.com/klein_stephane > > > > _______________________________________________ > > > > users mailing list > > > > [email protected] > > > > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > > > > > > > > > > > > > > -- > > Stéphane Klein > > blog: http://stephane-klein.info > > cv : http://cv.stephane-klein.info > > Twitter: http://twitter.com/klein_stephane > > > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
