OCPBUGS-39111: 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
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-21-41.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-24-83.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-42-30.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-61-249.us-east-2.compute.internal.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gatherers/clusterconfig/gather_nmstate_node_network_configuration_policy_test.go
• pkg/gatherers/clusterconfig/gather_nmstate_nodenetworkstate_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-39111
https://issues.redhat.com/browse/CCXDEV-14148
https://access.redhat.com/solutions/???

[openshift-ci-robot]

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

• expected the bug to target the "4.18.0" version, but no target version was set

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
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-21-41.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-24-83.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-42-30.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-61-249.us-east-2.compute.internal.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gatherers/clusterconfig/gather_nmstate_node_network_configuration_policy_test.go
• pkg/gatherers/clusterconfig/gather_nmstate_nodenetworkstate_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-39111
https://issues.redhat.com/browse/CCXDEV-14148
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]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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]

IO-test failures analyze:

[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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[tremes]

/retest

[tremes]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD a54c722 and 2 for PR HEAD a6399a0 in total

[tremes]

/retest

[tremes]

/test insights-operator-e2e-tests

[tremes]

/retest

[tremes]

Test failures are about missing file in the archive, but it's not related to this change
/override ci/prow/insights-operator-e2e-tests

[openshift-ci]

@tremes: Overrode contexts on behalf of tremes: ci/prow/insights-operator-e2e-tests

In response to this:

Test failures are about missing file in the archive, but it's not related to this change
/override ci/prow/insights-operator-e2e-tests

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-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.

[openshift-ci-robot]

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

• openshift/insights-operator#986

Jira Issue OCPBUGS-39111 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
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-21-41.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-24-83.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-42-30.us-east-2.compute.internal.json
• docs/insights-archive-sample/cluster-scoped-resources/nmstate.io/nodenetworkstates/ip-10-0-61-249.us-east-2.compute.internal.json

Documentation

• docs/gathered-data.md

Unit Tests

• pkg/gatherers/clusterconfig/gather_nmstate_node_network_configuration_policy_test.go
• pkg/gatherers/clusterconfig/gather_nmstate_nodenetworkstate_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-39111
https://issues.redhat.com/browse/CCXDEV-14148
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]

/jira backport release-4.17, release-4.16, release-4.15

[tremes]

/jira backport release-4.17,release-4.16,release-4.15

[openshift-ci-robot]

@tremes: The following backport issues have been created:

• OCPBUGS-39393 for branch release-4.17
• OCPBUGS-39394 for branch release-4.16
• OCPBUGS-39395 for branch release-4.15

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.17
/cherrypick release-4.16
/cherrypick release-4.15

In response to this:

/jira backport release-4.17,release-4.16,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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-cherrypick-robot]

@openshift-ci-robot: #986 failed to apply on top of branch "release-4.17":

Applying: OCPBUGS-39111: collect some nmstate customresources
.git/rebase-apply/patch:4408: trailing whitespace.
      interfaces: 
.git/rebase-apply/patch:4428: trailing whitespace.
      interfaces: 
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	docs/gathered-data.md
Falling back to patching base and 3-way merge...
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-39111: collect some nmstate customresources
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:

@tremes: The following backport issues have been created:

• OCPBUGS-39393 for branch release-4.17
• OCPBUGS-39394 for branch release-4.16
• OCPBUGS-39395 for branch release-4.15

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.17
/cherrypick release-4.16
/cherrypick release-4.15

In response to this:

/jira backport release-4.17,release-4.16,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 openshift-eng/jira-lifecycle-plugin repository.

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.18.0-202409031742.p0.g7bf4b55.assembly.stream.el9.
All builds following this will include this PR.