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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Error in uninstall job #5132

Closed
khushboo-rancher opened this issue Dec 22, 2022 · 2 comments
Closed

[BUG] Error in uninstall job #5132

khushboo-rancher opened this issue Dec 22, 2022 · 2 comments
Assignees
Labels
area/install-uninstall-upgrade Install, Uninstall or Upgrade related area/system-backup-restore Longhorn system backup restore kind/bug priority/0 Must be fixed in this release (managed by PO) severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact)
Milestone

Comments

@khushboo-rancher
Copy link
Contributor

Describe the bug (馃悰 if you encounter this issue)

The below error appears in the logs for uninstall job for supportbundle api.

W1222 19:41:49.829202       1 reflector.go:324] github.com/longhorn/longhorn-manager/k8s/pkg/client/informers/externalversions/factory.go:117: failed to list *v1beta2.SupportBundle: supportbundles.longhorn.io is forbidden: User "system:serviceaccount:longhorn-system:longhorn-uninstall-service-account" cannot list resource "supportbundles" in API group "longhorn.io" at the cluster scope

To Reproduce

Steps to reproduce the behavior:

  1. Install Longhorn v1.4.0-rc2
  2. Uninstall Longhorn. using the manifest at https://github.com/longhorn/longhorn/blob/v1.4.0-rc2/uninstall/uninstall.yaml
  3. Error appears in the logs as the supportbundles is missing from the apiGroups's resources

Environment

  • Longhorn version: v1.4.0-rc2
  • Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
@khushboo-rancher khushboo-rancher added kind/bug severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact) labels Dec 22, 2022
@innobead innobead added the priority/0 Must be fixed in this release (managed by PO) label Dec 22, 2022
@innobead innobead added this to the v1.4.0 milestone Dec 22, 2022
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Dec 23, 2022

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:

  • Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
    The PR is at

  • Which areas/issues this PR might have potential impacts on?
    Area deployment
    Issues

  • If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
    The LEP PR is at

  • If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
    The UI issue/PR is at

  • If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
    The documentation issue/PR is at

  • If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
    The automation skeleton PR is at
    The automation test case PR is at
    The issue of automation test case implementation is at (please create by the template)

  • If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
    The engine automation PR is at

  • If labeled: require/manual-test-plan Has the manual test plan been documented?
    The updated manual test plan is at

  • If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
    The compatibility issue is filed at

@chriscchien
Copy link
Contributor

Verified in longhorn master head images and v1.4.x head images with test steps
Result Pass

In both master-head and v1.4.x head, after uninstall complete, did not see error log related to supportbundles in job longhorn-uninstall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install-uninstall-upgrade Install, Uninstall or Upgrade related area/system-backup-restore Longhorn system backup restore kind/bug priority/0 Must be fixed in this release (managed by PO) severity/2 Function working but has a major issue w/o workaround (a major incident with significant impact)
Projects
None yet
Development

No branches or pull requests

5 participants