[release-4.16] OCPBUGS-39394: collect some nmstate customresources

[tremes]

Categories

• Bugfix
• Data Enhancement
• Feature
• Backporting
• Others (CI, Infrastructure, Documentation)

Sample Archive

• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkconfigurationpolicies/policy-name.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gatherers/clusterconfig/gather_nmstate_node_network_configuration_policy_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-39394
https://access.redhat.com/solutions/???

[openshift-ci-robot]

@tremes: This pull request references Jira Issue OCPBUGS-39394, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-39393 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Categories

• Bugfix
• Data Enhancement
• Feature
• Backporting
• Others (CI, Infrastructure, Documentation)

Sample Archive

• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkconfigurationpolicies/policy-name.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gatherers/clusterconfig/gather_nmstate_node_network_configuration_policy_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-39394
https://access.redhat.com/solutions/???

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 openshift-eng/jira-lifecycle-plugin repository.

[ncaak]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncaak, tremes

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 [ncaak,tremes]

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

[tremes]

/retest

[tremes]

/retest

[openshift-ci]

@tremes: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

[tremes]

/label backport-risk-assessed

[tremes]

/jira refresh

[openshift-ci-robot]

@tremes: This pull request references Jira Issue OCPBUGS-39394, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.

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 openshift-eng/jira-lifecycle-plugin repository.

[tremes]

@BaiyangZhou can you please add the cherry-pick approved label?

[tremes]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.z) matches configured target version for branch (4.16.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-39393 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-39393 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
• bug has dependents

Requesting review from QA contact:
/cc @BaiyangZhou

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 openshift-eng/jira-lifecycle-plugin repository.

[BaiyangZhou]

/label cherry-pick-approved

[openshift-ci-robot]

@tremes: Jira Issue OCPBUGS-39394: All pull requests linked via external trackers have merged:

• openshift/insights-operator#995

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

In response to this:

Categories

• Bugfix
• Data Enhancement
• Feature
• Backporting
• Others (CI, Infrastructure, Documentation)

Sample Archive

• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkconfigurationpolicies/policy-name.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gatherers/clusterconfig/gather_nmstate_node_network_configuration_policy_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

Breaking Changes

No

References

https://issues.redhat.com/browse/OCPBUGS-39394
https://access.redhat.com/solutions/???

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 openshift-eng/jira-lifecycle-plugin repository.

[tremes]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@tremes: #995 failed to apply on top of branch "release-4.15":

Applying: OCPBUGS-39394: collect some nmstate customresources (#986) (#989)
.git/rebase-apply/patch:4420: trailing whitespace.
      interfaces: 
.git/rebase-apply/patch:4440: trailing whitespace.
      interfaces: 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	docs/gathered-data.md
M	manifests/03-clusterrole.yaml
M	pkg/gatherers/clusterconfig/clusterconfig_gatherer.go
M	pkg/gatherers/clusterconfig/const.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/gatherers/clusterconfig/const.go
CONFLICT (content): Merge conflict in pkg/gatherers/clusterconfig/const.go
Auto-merging pkg/gatherers/clusterconfig/clusterconfig_gatherer.go
Auto-merging manifests/03-clusterrole.yaml
Auto-merging docs/gathered-data.md
CONFLICT (content): Merge conflict in docs/gathered-data.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OCPBUGS-39394: collect some nmstate customresources (#986) (#989)
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:

/cherry-pick release-4.15

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-sigs/prow repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-insights-operator
This PR has been included in build ose-insights-operator-container-v4.16.0-202409231004.p0.gb98e7c8.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.16.0-0.nightly-2024-09-23-125048