maniankara/jx-troubleshooting_medium.md

## jx-troubleshooting_medium.md

      
    Raw
  

              jx-troubleshooting_medium.md
            
          
Description
Error
Resolution


No Jenkins service found in development namespace
 anoop@myMac ~ $ jx create lile 
? Pick a name for the new project: mygrpc
Created lile project at mygrpcect: (myapp)
mygrpc error: no Jenkins service be found in the development namespace!
Are you sure you installed Jenkins X? Try: http://jenkins-x.io/getting-started/
anoop@myMac ~ $
Your user account is lacking permissions, see section 'Elevate privileges for ClusterRoleBindings'


jx hangs/kubectl top node shows heavy load
 anoop@myMac ~ $ kubectl top nodes | awk {'print $1 " " $3'}
NAME CPU%
gke-jx-default-pool-47e201fa-hwc9 14%
gke-jx-default-pool-47e201fa-pjmd 82%
gke-jx-default-pool-47e201fa-v3cl 23%
Increase the number of nodes atleast to 4


jenkins-maven node offline
[Pipeline] node
Still waiting to schedule task
All nodes of label ‘jenkins-maven’ are offline
check the status of all the pods with kubectl get po --all-namespaces and you should see the failed pod.
Description	Error	Resolution
No Jenkins service found in development namespace	`anoop@myMac ~ $ jx create lile` `? Pick a name for the new project: mygrpc` `Created lile project at mygrpcect: (myapp)` `mygrpc error: no Jenkins service be found in the development namespace!` `Are you sure you installed Jenkins X? Try: http://jenkins-x.io/getting-started/` `anoop@myMac ~ $`	Your user account is lacking permissions, see section 'Elevate privileges for ClusterRoleBindings'
jx hangs/kubectl top node shows heavy load	`anoop@myMac ~ $ kubectl top nodes \| awk {'print $1 " " $3'}` `NAME CPU%` `gke-jx-default-pool-47e201fa-hwc9 14%` `gke-jx-default-pool-47e201fa-pjmd 82%` `gke-jx-default-pool-47e201fa-v3cl 23%`	Increase the number of nodes atleast to 4
jenkins-maven node offline	`[Pipeline] node` `Still waiting to schedule task` `All nodes of label ‘jenkins-maven’ are offline`	check the status of all the pods with `kubectl get po --all-namespaces` and you should see the failed pod.