rancher
/
fleet-docs
mirror of https://github.com/rancher/fleet-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix formatting of troubleshooting intro (#208) 

This fixes indenting for nested lists to be treated as such, instead of
appearing as code blocks.
This commit is contained in:
Corentin Néau 2024-12-17 11:18:26 +01:00 committed by GitHub
parent 801d3089d6
commit bf3da29b8a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 24 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/troubleshooting.md
View File

@ -5,18 +5,18 @@ This section contains commands and tips to troubleshoot Fleet.
## Where to look for root causes of issues
The first things to check when Fleet behaves unexpectedly would be:
* `fleet-controller` logs on the management cluster: has Fleet failed to reconcile any resource's (bundle, bundle
deployment) current state with its expected state?
* `gitjob` pod logs on the management cluster: has Fleet encountered any issue while creating jobs to generate new
bundles for new commits found in monitored git repositories?
* status of the `GitRepo` for which resources are not properly deployed:
* How many `Ready Bundle Deployments` does it list?
* How many bundle deployments are listed as expected? How many do you expect to see?
* Keep in mind that a `GitRepo` creates a bundle per path; each bundle leads to as many bundle deployments
as there are target clusters. A mismatch between `Desired Ready Clusters` and your own expectation could point to a
targeting issue.
* Which resources are listed in the `GitRepo`'s status?
* Which commit appears in the `GitRepo`'s status?
* `fleet-controller` logs on the management cluster: has Fleet failed to reconcile any resource's (bundle, bundle
deployment) current state with its expected state?
* `gitjob` pod logs on the management cluster: has Fleet encountered any issue while creating jobs to generate new
bundles for new commits found in monitored git repositories?
* status of the `GitRepo` for which resources are not properly deployed:
* How many `Ready Bundle Deployments` does it list?
* How many bundle deployments are listed as expected? How many do you expect to see?
* Keep in mind that a `GitRepo` creates a bundle per path; each bundle leads to as many bundle deployments
as there are target clusters. A mismatch between `Desired Ready Clusters` and your own expectation could point to a
targeting issue.
* Which resources are listed in the `GitRepo`'s status?
* Which commit appears in the `GitRepo`'s status?
If the issue is specific to a target cluster, one might want to check Fleet agent logs on that cluster: has Fleet failed
to deploy a bundle deployment on that cluster?

24
versioned_docs/version-0.11/troubleshooting.md
View File

@ -5,18 +5,18 @@ This section contains commands and tips to troubleshoot Fleet.
## Where to look for root causes of issues
The first things to check when Fleet behaves unexpectedly would be:
* `fleet-controller` logs on the management cluster: has Fleet failed to reconcile any resource's (bundle, bundle
deployment) current state with its expected state?
* `gitjob` pod logs on the management cluster: has Fleet encountered any issue while creating jobs to generate new
bundles for new commits found in monitored git repositories?
* status of the `GitRepo` for which resources are not properly deployed:
* How many `Ready Bundle Deployments` does it list?
* How many bundle deployments are listed as expected? How many do you expect to see?
* Keep in mind that a `GitRepo` creates a bundle per path; each bundle leads to as many bundle deployments
as there are target clusters. A mismatch between `Desired Ready Clusters` and your own expectation could point to a
targeting issue.
* Which resources are listed in the `GitRepo`'s status?
* Which commit appears in the `GitRepo`'s status?
* `fleet-controller` logs on the management cluster: has Fleet failed to reconcile any resource's (bundle, bundle
deployment) current state with its expected state?
* `gitjob` pod logs on the management cluster: has Fleet encountered any issue while creating jobs to generate new
bundles for new commits found in monitored git repositories?
* status of the `GitRepo` for which resources are not properly deployed:
* How many `Ready Bundle Deployments` does it list?
* How many bundle deployments are listed as expected? How many do you expect to see?
* Keep in mind that a `GitRepo` creates a bundle per path; each bundle leads to as many bundle deployments
as there are target clusters. A mismatch between `Desired Ready Clusters` and your own expectation could point to a
targeting issue.
* Which resources are listed in the `GitRepo`'s status?
* Which commit appears in the `GitRepo`'s status?
If the issue is specific to a target cluster, one might want to check Fleet agent logs on that cluster: has Fleet failed
to deploy a bundle deployment on that cluster?