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.

Sign up for GitHub

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

Jump to bottom

Evaluate Fleet gitRepo states inside fleet cluster details view #11428

Open
aalves08 opened this issue Jul 12, 2024 · 1 comment
Open

Evaluate Fleet gitRepo states inside fleet cluster details view #11428

aalves08 opened this issue Jul 12, 2024 · 1 comment
Labels
area/fleet kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone
v2.11.0

Comments

@aalves08
Copy link
Member

Setup

  • Rancher version: 2.9-head
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug

This is more of an investigative issue rather than an actual bug at this point.

Fleet git repo state inside a fleet cluster details view shows that the git repo has a cluster state of Ready despite the actual cluster not being available... Is this representation accurate? If not, let's fix it.

To Reproduce

Result
Is this state representation accurate?

Expected Result

Have the state representation accurate.

Screenshots

Screenshot 2024-07-12 at 10 21 30 Screenshot 2024-07-12 at 10 21 43

Additional context
@aalves08 aalves08 added this to the v2.10.0 milestone Jul 12, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jul 12, 2024
@nwmac nwmac modified the milestones: v2.10.0, v2.11.0 Sep 27, 2024
@nwmac nwmac modified the milestones: v2.12.0, v2.11.0 Nov 1, 2024
@torchiaf
Copy link
Member

This issue involves UX refactoring.
We need to provide Bundles/GitRepos status in a clear way.

@torchiaf torchiaf mentioned this issue Jan 21, 2025
Open
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fleet kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Milestone
v2.11.0
Development

No branches or pull requests
3 participants
@nwmac @torchiaf @aalves08