[release-4.12] OCPBUGS-11623: node-exporter: disable btrfs collector

[vrutkovs]

Profiling shows that node-exporter is using ~16% of CPU time on updating btrfs details. This FS is not included in RHEL kernels, so it can be safely disabled

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Cherry-pick of #1941 on release-4.12

[openshift-ci]

@vrutkovs: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

node-exporter: disable btrfs collector

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vrutkovs]

/jira cherrypick OCPBUGS-11536

[openshift-ci-robot]

@vrutkovs: Jira Issue OCPBUGS-11536 has been cloned as Jira Issue OCPBUGS-11623. Will retitle bug to link to clone.
/retitle OCPBUGS-11623: node-exporter: disable btrfs collector

In response to this:

/jira cherrypick OCPBUGS-11536

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@vrutkovs: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-11623: node-exporter: disable btrfs collector

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@vrutkovs: This pull request references Jira Issue OCPBUGS-11623, which is invalid:

• expected dependent Jira Issue OCPBUGS-11536 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Profiling shows that node-exporter is using ~16% of CPU time on updating btrfs details. This FS is not included in RHEL kernels, so it can be safely disabled

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Cherry-pick of #1941 on release-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vrutkovs]

/retitle [release-4.12] OCPBUGS-11623: node-exporter: disable btrfs collector

[openshift-ci]

@vrutkovs: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.12] OCPBUGS-11623: node-exporter: disable btrfs collector

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jan--f]

/lgtm
/label backport-risk-assessed

[jan--f]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, vrutkovs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jan--f]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[slashpai]

/jira refresh

[openshift-ci-robot]

@slashpai: This pull request references Jira Issue OCPBUGS-11623, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.12.z) matches configured target version for branch (4.12.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-11536 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-11536 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
• bug has dependents

Requesting review from QA contact:
/cc @juzhao

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[slashpai]

/skip
/retest

[openshift-ci]

@vrutkovs: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/versions	5151fc9	link	false	/test versions

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[juzhao]

/label cherry-pick-approved
/label qe-approved

[openshift-ci-robot]

@vrutkovs: Jira Issue OCPBUGS-11623: All pull requests linked via external trackers have merged:

• openshift/cluster-monitoring-operator#1944

Jira Issue OCPBUGS-11623 has been moved to the MODIFIED state.

In response to this:

Profiling shows that node-exporter is using ~16% of CPU time on updating btrfs details. This FS is not included in RHEL kernels, so it can be safely disabled

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

Cherry-pick of #1941 on release-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vrutkovs]

/cherrypick release-4.11

[openshift-cherrypick-robot]

@vrutkovs: #1944 failed to apply on top of branch "release-4.11":

Applying: assets: disable btrfs collector in node-exporter
Using index info to reconstruct a base tree...
M	assets/node-exporter/daemonset.yaml
M	jsonnet/components/node-exporter.libsonnet
Falling back to patching base and 3-way merge...
Auto-merging jsonnet/components/node-exporter.libsonnet
CONFLICT (content): Merge conflict in jsonnet/components/node-exporter.libsonnet
Auto-merging assets/node-exporter/daemonset.yaml
CONFLICT (content): Merge conflict in assets/node-exporter/daemonset.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 assets: disable btrfs collector in node-exporter
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-4.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.