Description of problem: cpma utility generated a worng apiVersion (apiVersion: quota.openshift.io/v1) against ResourceQuota resource. Version-Release number of selected component (if applicable): OCP version: 3.09 commit 3c4895c72b533fd403ad6b5dcdb69baf85455204 Severity: medium Priority: medium How reproducible: always Steps to Reproduce: 1. Apply ResourceQuota to ocp 3 cluster $ oc create -f https://raw.githubusercontent.com/XinRedhat/cpma-test/master/quota/quota-demo.yaml 2. Execute cpma utility to generate CRs 3. Check the generated object quota CR Actual results: $ view 100_CPMA-object-quota-test-resource-quota-object-quota-demo.yaml apiVersion: quota.openshift.io/v1 kind: ResourceQuota metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: null name: object-quota-demo namespace: object-quota-test ... Expected results: the apiVersion's value should be 'v1' like below, apiVersion: v1 kind: ResourceQuota metadata: ... Additional info:
Hi Xin, Thanks you for pointing this issue. I do confirm the apiVersion should be "v1" and not "quota.openshift.io/v1".
This has been addressed upstream with patch https://github.com/fusor/cpma/pull/376
Patch has been merged.
Verified with cpma version `commit ef9d17caeeb6640f49919d030bcadf69c694a1c3` and the issue is gone
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922