Branch: refs/heads/1.6.0
Home: https://github.com/tribe29/checkmk
Commit: d46dc21f32316f3a112f482f005606e8969a4c3b
https://github.com/tribe29/checkmk/commit/d46dc21f32316f3a112f482f005606e89…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2020-04-20 (Mon, 20 Apr 2020)
Changed paths:
A .werks/10778
M checks/cisco_cpu
M checks/cisco_cpu_scan_functions.include
Log Message:
-----------
10778 FIX Cisco CPU checks: relax SNMP scan function
The Cisco CPU checks discovery ordering from Werk 7458 is revisited.
There are four Cisco CPU checks: cisco_cpu, cisco_cpu_multiitem, cisco_nexus_cpu, cisco_oldcpu. We discover the Cisco CPU utilization services in the following order:
- if it's a Nexus device the cisco_nexus_cpu check is used
- if the device contains the SNMP table .1.3.6.1.4.1.9.9.109.1.1.1.1.2.* then cisco_cpu_multiitem is used
- if the device either the OID .1.3.6.1.4.1.9.9.109.1.1.1.1.8.1 or
.1.3.6.1.4.1.9.9.109.1.1.1.1.5.1 then cisco_cpu. This acts now as a
fallback and is not strict about verifying device not belonging to cisco
nexus family. This as a relaxed condition to werk 5748.
- if .1.3.6.1.4.1.9.2.1.57.0 exists then cisco_oldcpu is used
There may be Cisco hosts which have discovered the 'wrong' check type. After a re-discovery the CPU check type may change.
Change-Id: Ia71ecfb4618acedf3d4207bff7c80e195eb41273
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: d7f2db7fca4b2ff0e4137fb8fdfe384263806123
https://github.com/tribe29/checkmk/commit/d7f2db7fca4b2ff0e4137fb8fdfe38426…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-04-18 (Sat, 18 Apr 2020)
Changed paths:
M buildscripts/infrastructure/build-nodes/centos-6/Dockerfile
M buildscripts/infrastructure/build-nodes/centos-7/Dockerfile
M buildscripts/infrastructure/build-nodes/centos-8/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-10/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-8/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-9/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp1/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp2/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp3/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp4/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp5/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-15/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-14.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-16.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-18.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-19.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-19.10/Dockerfile
Log Message:
-----------
Ensure all build containers have the jenkins user/group
A clean existing local user with home directory is needed to execute
the tests without issues.
Change-Id: If177f16077940e3acf47a9fb74baaf8a0f7933f2
Commit: fd253061afa10665587c3b31304b1cee981f51ba
https://github.com/tribe29/checkmk/commit/fd253061afa10665587c3b31304b1cee9…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-04-18 (Sat, 18 Apr 2020)
Changed paths:
M buildscripts/scripts/test-pylint-3.jenkins
M buildscripts/scripts/test-python3-unit.jenkins
Log Message:
-----------
Improve containerized pylint / unit tests
* Do not use privileged mode
* Use equal container settings for checking out git
* Use Ubuntu 19.04 with the correct docker tag
Change-Id: Ie3f126af4573b46b056b82e81ab34838abea336f
Commit: 4a44d69fe1548517ec0751d7a49af94ed23f3fc0
https://github.com/tribe29/checkmk/commit/4a44d69fe1548517ec0751d7a49af94ed…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-04-18 (Sat, 18 Apr 2020)
Changed paths:
M buildscripts/infrastructure/build-nodes/centos-6/Dockerfile
M buildscripts/infrastructure/build-nodes/centos-7/Dockerfile
M buildscripts/infrastructure/build-nodes/centos-8/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-10/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-8/Dockerfile
M buildscripts/infrastructure/build-nodes/debian-9/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp1/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp2/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp3/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp4/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-12sp5/Dockerfile
M buildscripts/infrastructure/build-nodes/sles-15/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-14.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-16.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-18.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-19.04/Dockerfile
M buildscripts/infrastructure/build-nodes/ubuntu-19.10/Dockerfile
Log Message:
-----------
Fix wrong command
Change-Id: I39f93245afb772ce3a5a5a8a6c6b6f659d2bfbe4
Commit: 802b17ffe4e2b1f01663cc8ea0c0ce54a0161a22
https://github.com/tribe29/checkmk/commit/802b17ffe4e2b1f01663cc8ea0c0ce54a…
Author: Lars Michelsen <lm(a)tribe29.com>
Date: 2020-04-18 (Sat, 18 Apr 2020)
Changed paths:
M buildscripts/infrastructure/build-nodes/debian-9/Dockerfile
R buildscripts/infrastructure/os-nodes/centos-6/Dockerfile
R buildscripts/infrastructure/os-nodes/centos-7/Dockerfile
R buildscripts/infrastructure/os-nodes/centos-8/Dockerfile
R buildscripts/infrastructure/os-nodes/debian-10/Dockerfile
R buildscripts/infrastructure/os-nodes/debian-7/Dockerfile
R buildscripts/infrastructure/os-nodes/debian-8/Dockerfile
R buildscripts/infrastructure/os-nodes/debian-9/Dockerfile
R buildscripts/infrastructure/os-nodes/sles-12sp1/Dockerfile
R buildscripts/infrastructure/os-nodes/sles-12sp2/Dockerfile
R buildscripts/infrastructure/os-nodes/sles-12sp3/Dockerfile
R buildscripts/infrastructure/os-nodes/sles-12sp4/Dockerfile
R buildscripts/infrastructure/os-nodes/ubuntu-14.04/Dockerfile
R buildscripts/infrastructure/os-nodes/ubuntu-16.04/Dockerfile
R buildscripts/infrastructure/os-nodes/ubuntu-18.04/Dockerfile
R buildscripts/infrastructure/os-nodes/ubuntu-19.04/Dockerfile
R buildscripts/infrastructure/os-nodes/ubuntu-19.10/Dockerfile
R buildscripts/scripts/build-test-containers.jenkins
M buildscripts/scripts/test-composition.jenkins
M buildscripts/scripts/test-integration.jenkins
Log Message:
-----------
Drop dead os-nodes
Change-Id: If6bff2c4fad85419d568d111d33cddefa62e8ba3
Compare: https://github.com/tribe29/checkmk/compare/cbd50b763ec9...802b17ffe4e2
Branch: refs/heads/master
Home: https://github.com/tribe29/checkmk
Commit: 15d8c76a8ae9c8497e3efb91dafd6147aa4ba22c
https://github.com/tribe29/checkmk/commit/15d8c76a8ae9c8497e3efb91dafd6147a…
Author: Óscar Nájera <oscar.najera(a)tribe29.com>
Date: 2020-04-17 (Fri, 17 Apr 2020)
Changed paths:
A .werks/10778
M checks/cisco_cpu
M checks/cisco_cpu_scan_functions.include
M cmk/base/api/agent_based/register/section_plugins_legacy_scan_function.py
M tests-py3/unit/checks/test_generic_legacy_conversion.py
Log Message:
-----------
10778 FIX Cisco CPU checks: relax SNMP scan function
The Cisco CPU checks discovery ordering from Werk 7458 is revisited.
There are four Cisco CPU checks: cisco_cpu, cisco_cpu_multiitem, cisco_nexus_cpu, cisco_oldcpu. We discover the Cisco CPU utilization services in the following order:
- if it's a Nexus device the cisco_nexus_cpu check is used
- if the device contains the SNMP table .1.3.6.1.4.1.9.9.109.1.1.1.1.2.* then cisco_cpu_multiitem is used
- if the device either the OID .1.3.6.1.4.1.9.9.109.1.1.1.1.8.1 or
.1.3.6.1.4.1.9.9.109.1.1.1.1.5.1 then cisco_cpu. This acts now as a
fallback and is not strict about verifying device not belonging to cisco
nexus family. This as a relaxed condition to werk 5748.
- if .1.3.6.1.4.1.9.2.1.57.0 exists then cisco_oldcpu is used
There may be Cisco hosts which have discovered the 'wrong' check type. After a re-discovery the CPU check type may change.
Change-Id: Ia71ecfb4618acedf3d4207bff7c80e195eb41273