Private bug reported:
Kubernetes 1.18.5
nagios 3.5.1
20.04 charms
The Nagios gui and nagios logs are reporting what appears to be a
cosmetic error:
---
[1594944000] CURRENT SERVICE STATE:
norcross-blade06-zone01-cit-k8s01;norcross-blade06-zone01-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-blade07-zone01-cit-k8s01;norcross-blade07-zone01-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-blade07-zone02-cit-k8s01;norcross-blade07-zone02-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-blade08-zone02-cit-k8s01;norcross-blade08-zone02-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-k8s-worker-uat-1;norcross-k8s-worker-uat-1-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-k8s-worker-uat-2;norcross-k8s-worker-uat-2-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
---
I believe this to be a cosmetic error, since, going to each of these
individual units, I can run kubectl just fine, with no errors.
There are more worker units in the cluster than those listed above, so
not all worker nodes are coming back like this.
Aside from the above, there are no errors appearing in any juju-unit
logs or nagios logs.
** Affects: charm-nagios
Importance: Undecided
Status: New
** Tags: cpe-onsite
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Nagios
Charm developers, which is subscribed to Nagios Charm.
https://bugs.launchpad.net/bugs/1887948
Title:
nagios reporting kubectl cannot be run on k8s nodes
Status in Nagios Charm:
New
Bug description:
Kubernetes 1.18.5
nagios 3.5.1
20.04 charms
The Nagios gui and nagios logs are reporting what appears to be a
cosmetic error:
---
[1594944000] CURRENT SERVICE STATE:
norcross-blade06-zone01-cit-k8s01;norcross-blade06-zone01-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-blade07-zone01-cit-k8s01;norcross-blade07-zone01-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-blade07-zone02-cit-k8s01;norcross-blade07-zone02-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-blade08-zone02-cit-k8s01;norcross-blade08-zone02-cit-k8s01-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-k8s-worker-uat-1;norcross-k8s-worker-uat-1-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
[1594944000] CURRENT SERVICE STATE:
norcross-k8s-worker-uat-2;norcross-k8s-worker-uat-2-node;CRITICAL;HARD;4;Unable
to run kubectl and parse output
---
I believe this to be a cosmetic error, since, going to each of these
individual units, I can run kubectl just fine, with no errors.
There are more worker units in the cluster than those listed above, so
not all worker nodes are coming back like this.
Aside from the above, there are no errors appearing in any juju-unit
logs or nagios logs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nagios/+bug/1887948/+subscriptions
--
Mailing list: https://launchpad.net/~nagios-charmers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~nagios-charmers
More help : https://help.launchpad.net/ListHelp
