OCPBUGS-52393: rename 'master' to 'main' for node-feature-discovery

[DennisPeriquet]

This PR is in support of renaming the default branch for https://github.com/openshift/node-feature-discovery from 'master' to 'main'.

Unhold this PR only when:

• the default branch for https://github.com/openshift/node-feature-discovery has been renamed to 'main'
• You have verified that the CI jobs are working as expected either by running '/pj-rehearse' or by inspection.

/hold

[openshift-ci-robot]

@DennisPeriquet: This pull request references Jira Issue OCPBUGS-52393, which is invalid:

• expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.19.z" 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:

This PR is in support of renaming the default branch for https://github.com/openshift/node-feature-discovery from 'master' to 'main'.

Unhold this PR only when:

• the default branch for https://github.com/openshift/node-feature-discovery has been renamed to 'main'
• You have verified that the CI jobs are working as expected either by running '/pj-rehearse' or by inspection.

/hold

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.

[DennisPeriquet]

/jira refresh

[openshift-ci-robot]

@DennisPeriquet: This pull request references Jira Issue OCPBUGS-52393, 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.20.0) matches configured target version for branch (4.20.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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.

[DennisPeriquet]

/retest config

[openshift-ci]

@DennisPeriquet: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test app-ci-config-dry

/test boskos-config

/test boskos-config-generation

/test build01-dry

/test build03-dry

/test build04-dry

/test build05-dry

/test build06-dry

/test build07-dry

/test build09-dry

/test build10-dry

/test build11-dry

/test check-gh-automation

/test check-gh-automation-tide

/test ci-operator-config

/test ci-operator-config-metadata

/test ci-operator-registry

/test ci-secret-bootstrap-config-validation

/test ci-testgrid-allow-list

/test clusterimageset-validate

/test config

/test core-valid

/test generated-config

/test generated-dashboards

/test hosted-mgmt-dry

/test image-mirroring-config-validation

/test jira-lifecycle-config

/test openshift-image-mirror-mappings

/test ordered-prow-config

/test owners

/test pr-reminder-config

/test prow-config

/test prow-config-filenames

/test prow-config-semantics

/test pylint

/test release-config

/test release-controller-config

/test rover-groups-config-validation

/test secret-generator-config-valid

/test services-valid

/test stackrox-stackrox-stackrox-stackrox-check

/test step-registry-metadata

/test step-registry-shellcheck

/test sync-rover-groups

/test vsphere02-dry

/test yamllint

The following commands are available to trigger optional jobs:

/test build02-dry

/test check-cluster-profiles-config

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-release-check-gh-automation

pull-ci-openshift-release-master-ci-operator-config

pull-ci-openshift-release-master-ci-operator-config-metadata

pull-ci-openshift-release-master-ci-operator-registry

pull-ci-openshift-release-master-config

pull-ci-openshift-release-master-core-valid

pull-ci-openshift-release-master-generated-config

pull-ci-openshift-release-master-ordered-prow-config

pull-ci-openshift-release-master-owners

pull-ci-openshift-release-master-prow-config-filenames

pull-ci-openshift-release-master-prow-config-semantics

pull-ci-openshift-release-master-release-controller-config

pull-ci-openshift-release-master-services-valid

pull-ci-openshift-release-openshift-image-mirror-mappings

pull-ci-openshift-release-yamllint

In response to this:

/retest config

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.

[DennisPeriquet]

/test config

[openshift-bot]

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[DennisPeriquet]

/remove-lifecycle stale

[openshift-bot]

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[DennisPeriquet]

/remove-lifecycle stale

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@DennisPeriquet: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-node-feature-discovery-main-images	openshift/node-feature-discovery	presubmit	Presubmit changed
pull-ci-openshift-node-feature-discovery-main-unit	openshift/node-feature-discovery	presubmit	Presubmit changed
pull-ci-openshift-node-feature-discovery-main-verify	openshift/node-feature-discovery	presubmit	Presubmit changed
pull-ci-openshift-node-feature-discovery-main-verify-deps	openshift/node-feature-discovery	presubmit	Presubmit changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DennisPeriquet, liangxia

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:

• ci-operator/config/openshift/node-feature-discovery/OWNERS [liangxia]
• ci-operator/jobs/openshift/node-feature-discovery/OWNERS [liangxia]

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

[DennisPeriquet]

/pj-rehearse pull-ci-openshift-node-feature-discovery-main-images

[openshift-ci-robot]

@DennisPeriquet: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[DennisPeriquet]

/pj-rehearse ack
/hold cancel

[openshift-ci-robot]

@DennisPeriquet: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@DennisPeriquet: 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]

@DennisPeriquet: Jira Issue OCPBUGS-52393: All pull requests linked via external trackers have merged:

• openshift/release#67853

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

In response to this:

This PR is in support of renaming the default branch for https://github.com/openshift/node-feature-discovery from 'master' to 'main'.

Unhold this PR only when:

• the default branch for https://github.com/openshift/node-feature-discovery has been renamed to 'main'
• You have verified that the CI jobs are working as expected either by running '/pj-rehearse' or by inspection.

/hold

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.