Skip to content

Rename api group to sharedresource.openshift.io#39

Closed
adambkaplan wants to merge 13 commits intoopenshift:masterfrom
adambkaplan:rename-api-group
Closed

Rename api group to sharedresource.openshift.io#39
adambkaplan wants to merge 13 commits intoopenshift:masterfrom
adambkaplan:rename-api-group

Conversation

@adambkaplan
Copy link
Copy Markdown
Contributor

  • Rename api group to sharedresource.storage.openshift.io.
  • Update base CRD definition and type registration with new group name.
  • Regenerated deployment YAMLs.
  • Rename pkg/api/projectedresource to pkg/api/sharedresource
  • Rename arguments for update/generated.sh to use new name
  • Regenerate informers and listers
  • Rename golang package imports
  • Update controller with new informer factory name
  • Update e2e tests to use new client
  • Rename CRD manifest to "sharedresource"
  • Move base YAML manifest to the sharedresource/v1alpha1 directory
  • Add rename to update-crd.sh

@openshift-ci openshift-ci Bot requested review from coreydaley and otaviof July 28, 2021 19:08
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 28, 2021
@adambkaplan adambkaplan changed the title Rename api group to sharedresource.storage.openshift.io Rename api group to sharedresource.openshift.io Jul 29, 2021
Rename image to csi-driver-shared-resource for CI.
@coreydaley
Copy link
Copy Markdown

/retest

- Rename api group to sharedresource.storage.openshift.io.
- Update base CRD definition and type registration with new group name.
- Regenerated deployment YAMLs.
- Rename pkg/api/projectedresource to pkg/api/sharedresource
- Rename arguments for update/generated.sh to use new name
- Regenerate informers and listers
- Rename golang package imports
- Update controller with new informer factory name
- Update e2e tests to use new client
- Rename CRD manifest to "sharedresource"
- Move base YAML manifest to the sharedresource/v1alpha1 directory
- Add rename to update-crd.sh and deploy-in-CI.sh
- Use "csi-driver-shared-resource" for namespace and core components
- Add suffixes for cluster role bindings
- Rename csi driver deployment manifests to use desired ordering
- Clarify comments in deploy scripts
- Regenerate client
- Update SAR check to use new api group
- Use new group name when creating RBAC in test framework
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 3, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coreydaley
Copy link
Copy Markdown

@adambkaplan I think that https://github.com/openshift/csi-driver-shared-resource/blob/master/Dockerfile needs to be updated to reflect the new github repository name and go package name?

@coreydaley
Copy link
Copy Markdown

coreydaley commented Aug 3, 2021

From the test logs:

2021-08-03T16:13:07.904133683Z STEP 8: COPY --from=builder /go/src/github.com/openshift/csi-driver-projected-resource/_output/csi-driver-projected-resource /usr/bin/
2021-08-03T16:13:08.690272181Z STEP 9: ENTRYPOINT null
2021-08-03T16:13:08.690272181Z STEP 10: CMD ["/usr/bin/csi-driver-projected-resource"]

Update component names to check in e2e tests.
- Update component names in install docs
- Update driver name in example YAML.
Fix driver name used in tests
@adambkaplan
Copy link
Copy Markdown
Contributor Author

I honestly don't know how CI works without registering the CSIDriver object. Kube can't create pods if the CSI driver isn't registered with the cluster. I don't see anything in openshift/release or the make commands which indicate we register the CSI driver object in our test.

@coreydaley
Copy link
Copy Markdown

@adambkaplan

 "message": "MountVolume.SetUp failed for volume \"my-csi-volume\" : rpc error: code = InvalidArgument desc = the csi driver volumeAttribute 'share' reference had an error: share.projectedresource.storage.openshift.io \"e2e-test-csi-driver-projected-resource-kdjtt\" not found",

@adambkaplan
Copy link
Copy Markdown
Contributor Author

@coreydaley this is the moment where I screamed at the top of my lungs, "WHAT'S GOING ON?!" [1]

I suspect that either:

  1. We aren't deploying the driver we want in CI
  2. The client code that we're generating in this tree is somehow hard-coding the previous apigroup.

The only way I think we can address the situation is close this PR, and start fresh with generated code from openshift/api and openshift/client-go vendored in.

[1] https://www.youtube.com/watch?v=6NXnxTNIWkc

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 6, 2021

@adambkaplan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-operator 3b6a5df link /test e2e-aws-operator
ci/prow/e2e-aws-operator-slow 3b6a5df link /test e2e-aws-operator-slow
ci/prow/e2e-aws-operator-disruptive 3b6a5df link /test e2e-aws-operator-disruptive
ci/prow/e2e-aws-csi-driver 3b6a5df link /test e2e-aws-csi-driver
ci/prow/e2e-aws-csi-driver-slow 3b6a5df link /test e2e-aws-csi-driver-slow
ci/prow/e2e-aws-csi-driver-disruptive 3b6a5df link /test e2e-aws-csi-driver-disruptive

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 6, 2021

@adambkaplan: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 6, 2021
@adambkaplan
Copy link
Copy Markdown
Contributor Author

/close

@openshift-ci openshift-ci Bot closed this Aug 16, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 16, 2021

@adambkaplan: Closed this PR.

Details

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants