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

[IMPROVEMENT] Support bundle collects Volume, Longhorn-System, and related information, including Longhorn upgrade history #8605

Open
roger-ryao opened this issue May 20, 2024 · 2 comments
Labels
kind/improvement Request for improvement of existing function require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/manual-test-plan Require adding/updating manual test cases if they can't be automated
Milestone

Comments

@roger-ryao
Copy link

Is your improvement request related to a feature? Please describe (馃憤 if you like this request)

According to #7687, @derekbit and I believe there's a need to improve the Support Bundle to collect Volume, Longhorn-System, and related information, including upgrade history. This enhancement could potentially assist us in identifying how to reproduce the issue from upgrade scenarios.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

#7687

@roger-ryao roger-ryao added require/doc Require updating the longhorn.io documentation require/manual-test-plan Require adding/updating manual test cases if they can't be automated kind/improvement Request for improvement of existing function require/backport Require backport. Only used when the specific versions to backport have not been definied. labels May 20, 2024
@innobead
Copy link
Member

innobead commented May 20, 2024

I thought support bundle already able to collect all Longhorn CRs and logs. What extra info we want to collect?

cc @c3y1huang

@derekbit
Copy link
Member

derekbit commented May 20, 2024

I think what @roger-ryao meant is the Longhorn system can record the versioning history of upgrades within the longhorn-system and record the versioning information in resources, for example, which Longhorn version created the backup resource. These information can be recorded in labels of resources or other fields.

This is not related to the improvement of the support bundle.

@innobead innobead added this to the Backlog milestone May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/improvement Request for improvement of existing function require/backport Require backport. Only used when the specific versions to backport have not been definied. require/doc Require updating the longhorn.io documentation require/manual-test-plan Require adding/updating manual test cases if they can't be automated
Projects
None yet
Development

No branches or pull requests

3 participants