Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error deleting ConfigConnectorContext #523

Closed
maqiuyujoyce opened this issue Aug 4, 2021 · 4 comments
Closed

Error deleting ConfigConnectorContext #523

maqiuyujoyce opened this issue Aug 4, 2021 · 4 comments
Labels
question Further information is requested

Comments

@maqiuyujoyce
Copy link
Collaborator

maqiuyujoyce commented Aug 4, 2021

Config Connector user of v1.50.0 or above may run into the following error (or a similar one) when deleting the ConfigConnectorContext:

  status:
    errors:
    - 'error during reconciliation: error verifying the Config Connector resource
      counts in namespace ''example-1234-321423'': error listing objects for gvk ''core.cnrm.cloud.google.com/v1alpha1,
      Kind=ServiceMapping'': servicemappings.core.cnrm.cloud.google.com is forbidden:
      User "system:serviceaccount:configconnector-operator-system:configconnector-operator"
      cannot list resource "servicemappings" in API group "core.cnrm.cloud.google.com"
      in the namespace "example-1234-321423"'
    healthy: false
@maqiuyujoyce maqiuyujoyce added the question Further information is requested label Aug 4, 2021
@maqiuyujoyce
Copy link
Collaborator Author

Since v1.50.0, ServiceMapping CRD has been removed from Config Connector installation bundle. If you upgraded from a version below v1.50.0 to v1.50.0 or above, the ServiceMapping CRD and its CRs may still exist, but can no longer be managed/handled by Config Connector, which causes the error. We are working on a fix and will update this issue when we have any new information.

For now, you can work around it by deleting all the ServiceMapping CRs and the ServiceMapping CRD manually before deleting the ConfigConnectorContext.

@travisrandolph-bestbuy
Copy link

@maqiuyujoyce, is there any update on this ticket?

@maqiuyujoyce
Copy link
Collaborator Author

Hi @travisrandolph-bestbuy , the workaround will be released in Config Connector 1.61.0.

@maqiuyujoyce
Copy link
Collaborator Author

Hi @travisrandolph-bestbuy , please ignore my last comment. The fix has been released in Config Connector 1.60.0. Please let us know if you have any questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants