Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-8232

`oc patch project` not working with OCP 4.12

XMLWordPrintable

    • Important
    • No
    • Proposed
    • False
    • Hide

      Customer can't continue with the upgrade process for OCP 4.12.
      All flows are dependent on this oc path project options which is not available as of now

      Failing to qualify Openshift 4.12 - customer will miss the coming PI shifting their EUS migration from 4.10 to 4.12 by 3 months which in turn will have an impact shipping their product in time to their OCP 4.10 customers who will reach OCP 4.10 EOL prior to upgrading to 4.12

      Customer has more than 150 development clusters to upgrade

       

      Show
      Customer can't continue with the upgrade process for OCP 4.12. All flows are dependent on this oc path project options which is not available as of now Failing to qualify Openshift 4.12 - customer will miss the coming PI shifting their EUS migration from 4.10 to 4.12 by 3 months which in turn will have an impact shipping their product in time to their OCP 4.10 customers who will reach OCP 4.10 EOL prior to upgrading to 4.12 Customer has more than 150 development clusters to upgrade  
    • Hide
      * Previously, the `metadata.namespace` field would be automatically populated in update and patch requests to the `projects` resource. As a result, the affected requests would generate spurious validation errors. With this release, the `projects` resource is no longer automatically populated. (link:https://issues.redhat.com/browse/OCPBUGS-8232[*OCPBUGS-8232*])
      Show
      * Previously, the `metadata.namespace` field would be automatically populated in update and patch requests to the `projects` resource. As a result, the affected requests would generate spurious validation errors. With this release, the `projects` resource is no longer automatically populated. (link: https://issues.redhat.com/browse/OCPBUGS-8232 [* OCPBUGS-8232 *])
    • Bug Fix
    • Done
    • Customer Escalated

      Description of problem:

      oc patch project command is failing to annotate the project

      Version-Release number of selected component (if applicable):

      4.12

      How reproducible:

      100%

      Steps to Reproduce:

      1. Run the below patch command to update the annotation on existing project
~~~
oc patch project <PROJECT_NAME> --type merge --patch '{"metadata":{"annotations":{"openshift.io/display-name": "null","openshift.io/description": "This is a new project"}}}'
~~~

      Actual results:

      It produces the error output below:
~~~
The Project "<PROJECT_NAME>" is invalid: * metadata.namespace: Invalid value: "<PROJECT_NAME>": field is immutable * metadata.namespace: Forbidden: not allowed on this type 
~~~

      Expected results:

      The `oc patch project` command should patch the project with specified annotation.

      Additional info:

      Tried to patch the project with OCP 4.11.26 version, and it worked as expected.
~~~
oc patch project <PROJECT_NAME> --type merge --patch '{"metadata":{"annotations":{"openshift.io/display-name": "null","openshift.io/description": "New project"}}}'

project.project.openshift.io/<PROJECT_NAME> patched
~~~

The issue is with OCP 4.12, where it is not working.

       

              bluddy Ben Luddy
              rhn-support-dpateriy Divyam Pateriya
              Rahul Gangwar Rahul Gangwar
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: