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

General state of cluster is not fetched for logs #787

Open
2 tasks
tuminoid opened this issue Jun 13, 2024 · 5 comments
Open
2 tasks

General state of cluster is not fetched for logs #787

tuminoid opened this issue Jun 13, 2024 · 5 comments
Labels
triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

We are missing all the key indicators where to begin debugging, like kubectl get pods -A. We do fetch all individual logs and describes from all containters, but we don't have a clue where to look as no top-level listing is grabbed.

Add at least:

  • kubectl get pods -A
  • other key listings/statuses
@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jun 13, 2024
@tuminoid
Copy link
Member Author

/assign @smoshiur1237
/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jun 13, 2024
@Rozzii
Copy link
Member

Rozzii commented Jun 28, 2024

Please link the PRs if there are any related to this Issue, if I remember correctly there were work done related to this.

@Rozzii Rozzii moved this from Backlog to MISC WIP in Metal3 - Roadmap Jun 28, 2024
@tuminoid
Copy link
Member Author

There are no PRs related to this yet, we only fixed log collection, but did not add anything related to global state of clusters.

@Rozzii Rozzii moved this from MISC WIP to Backlog in Metal3 - Roadmap Jun 28, 2024
@smoshiur1237 smoshiur1237 removed their assignment Jul 9, 2024
@metal3-io-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2024
@Rozzii
Copy link
Member

Rozzii commented Oct 7, 2024

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Backlog
Development

No branches or pull requests

4 participants