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

[Cluster Ingress Operator] Unable to update generated CRDs while bumping new API version

XMLWordPrintable

    • Important
    • None
    • 2
    • Sprint 252
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • In Progress

      Description of problem:

      The IngressController and DNSRecord CRDs were moved to dedicated packages
following the introduction of a new method for generating CRDs in the OpenShift API repository ([openshift/api#1803|https://github.com/openshift/api/pull/1803]).

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

      How reproducible:

      Always

      Steps to Reproduce:

      1. go mod edit -replace=github.com/openshift/api=github.com/openshift/api@ff84c2c732279b16baccf08c7dfc9ff8719c4807
2. go mod tidy
3. go mod vendor
4. make update

      Actual results:

      $ make update
hack/update-generated-crd.sh
--- vendor/github.com/openshift/api/operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml    1970-01-01 01:00:00.000000000 +0100
+++ manifests/00-custom-resource-definition.yaml    2024-04-17 18:05:05.009605155 +0200
[LONG DIFF]
cp: cannot stat 'vendor/github.com/openshift/api/operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml': No such file or directory
make: *** [Makefile:39: crd] Error 1

      Expected results:

      $ make update
hack/update-generated-crd.sh 
hack/update-profile-manifests.sh

      Additional info:

       

              mmasters1@redhat.com Miciah Masters
              alebedev@redhat.com Andrey Lebedev
              Hongan Li Hongan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: