[release-4.10] Bug 2048609: Configure hostnames via ignition #37

openshift-cherrypick-robot · 2022-01-31T15:36:54Z

This is an automated cherry-pick of #35

/assign sadasu

openshift-ci · 2022-01-31T15:38:08Z

@openshift-cherrypick-robot: Bugzilla bug 2041183 has been cloned as Bugzilla bug 2048609. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2048609: Configure hostnames via ignition

In response to this:

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 · 2022-01-31T15:38:13Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2048609, which is invalid:

expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, but it targets "4.10.0" instead

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

In response to this:

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.

sadasu · 2022-01-31T16:30:35Z

/bugzilla refresh

openshift-ci · 2022-01-31T16:31:53Z

@sadasu: This pull request references Bugzilla bug 2048609, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.10.0) matches configured target release for branch (4.10.0)
bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2041183 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Bugzilla bug 2041183 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yporagpa@redhat.com), skipping review request.

In response to this:

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.

zaneb · 2022-01-31T16:59:20Z

/lgtm

sadasu · 2022-01-31T16:59:24Z

/retest

sadasu · 2022-02-01T13:14:19Z

/retest

sadasu · 2022-02-01T13:53:57Z

/test e2e-metal-ipi-serial-ipv6

openshift-ci · 2022-02-01T13:53:58Z

@sadasu: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-metal-ipi
/test e2e-metal-ipi-serial-ipv4
/test images
/test lint
/test unit

Use /test all to run all jobs.

In response to this:

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.

zaneb · 2022-02-01T14:59:39Z

/approve

openshift-ci · 2022-02-01T15:01:21Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, zaneb

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~~ [zaneb]

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

openshift-bot · 2022-02-01T15:59:24Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

sadasu · 2022-02-17T20:44:42Z

/label backport-risk-assessed

openshift-ci · 2022-02-17T20:44:49Z

@sadasu: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

In response to this:

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.

sadasu · 2022-03-30T17:55:51Z

openshift/release#27428 specifies users that can add the backport-risk-assessed label.

zaneb · 2022-03-31T13:37:42Z

/bugzilla refresh

openshift-ci · 2023-04-18T06:29:03Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-19T01:00:32Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-19T01:00:41Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-20T01:00:18Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-20T01:00:24Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-21T01:00:27Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-21T01:00:41Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-22T01:00:27Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-22T01:00:41Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-23T01:00:33Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-23T01:00:37Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-24T01:00:37Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-24T01:00:45Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-25T01:00:42Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-25T01:00:49Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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-bot · 2023-04-26T01:00:42Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2023-04-26T01:00:49Z

@openshift-bot: This pull request references Bugzilla bug 2048609, which is invalid:

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is CLOSED (DEFERRED) instead
expected dependent Bugzilla bug 2041183 to target a release in 4.11.0, 4.11.z, but it targets "4.10.z" instead

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

In response to this:

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.

dtantsur · 2023-04-26T07:10:51Z

/lgtm cancel
/hold

openshift-bot · 2023-07-25T09:01:07Z

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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

openshift-bot · 2023-08-25T00:30:06Z

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

openshift-ci · 2023-08-25T09:49:07Z

@openshift-cherrypick-robot: 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/test-infra repository. I understand the commands that are listed here.

openshift-bot · 2023-09-25T00:00:44Z

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci · 2023-09-25T00:01:25Z

@openshift-bot: Closed this PR.

In response to this:

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.

Configure hostnames via ignition

1773d24

openshift-ci bot assigned sadasu Jan 31, 2022

openshift-cherrypick-robot mentioned this pull request Jan 31, 2022

Bug 2041183: Configure hostnames via ignition #35

Merged

openshift-ci bot changed the title ~~[release-4.10] Bug 2041183: Configure hostnames via ignition~~ [release-4.10] Bug 2048609: Configure hostnames via ignition Jan 31, 2022

openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jan 31, 2022

openshift-ci bot requested review from hardys and zaneb January 31, 2022 15:40

openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jan 31, 2022

openshift-ci bot assigned zaneb Jan 31, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 31, 2022

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 1, 2022

openshift-ci bot removed the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Mar 31, 2022

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 26, 2023

openshift-ci bot assigned dtantsur Apr 26, 2023

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2023

openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2023

openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 25, 2023

openshift-ci bot closed this Sep 25, 2023

[release-4.10] Bug 2048609: Configure hostnames via ignition #37

[release-4.10] Bug 2048609: Configure hostnames via ignition #37

Uh oh!

Conversation

openshift-cherrypick-robot commented Jan 31, 2022

Uh oh!

openshift-ci bot commented Jan 31, 2022

Uh oh!

openshift-ci bot commented Jan 31, 2022

Uh oh!

sadasu commented Jan 31, 2022

Uh oh!

openshift-ci bot commented Jan 31, 2022

Uh oh!

zaneb commented Jan 31, 2022

Uh oh!

sadasu commented Jan 31, 2022

Uh oh!

sadasu commented Feb 1, 2022

Uh oh!

sadasu commented Feb 1, 2022

Uh oh!

openshift-ci bot commented Feb 1, 2022

Uh oh!

zaneb commented Feb 1, 2022

Uh oh!

openshift-ci bot commented Feb 1, 2022

Uh oh!

openshift-bot commented Feb 1, 2022

Uh oh!

sadasu commented Feb 17, 2022

Uh oh!

openshift-ci bot commented Feb 17, 2022

Uh oh!

sadasu commented Mar 30, 2022

Uh oh!

zaneb commented Mar 31, 2022

Uh oh!

openshift-ci bot commented Apr 18, 2023

Uh oh!

openshift-bot commented Apr 19, 2023

Uh oh!

openshift-ci bot commented Apr 19, 2023

Uh oh!

openshift-bot commented Apr 20, 2023

Uh oh!

openshift-ci bot commented Apr 20, 2023

Uh oh!

openshift-bot commented Apr 21, 2023

Uh oh!

openshift-ci bot commented Apr 21, 2023

Uh oh!

openshift-bot commented Apr 22, 2023

Uh oh!

openshift-ci bot commented Apr 22, 2023

Uh oh!

openshift-bot commented Apr 23, 2023

Uh oh!

openshift-ci bot commented Apr 23, 2023

Uh oh!

openshift-bot commented Apr 24, 2023

Uh oh!

openshift-ci bot commented Apr 24, 2023

Uh oh!

openshift-bot commented Apr 25, 2023

Uh oh!

openshift-ci bot commented Apr 25, 2023

Uh oh!

openshift-bot commented Apr 26, 2023

Uh oh!

openshift-ci bot commented Apr 26, 2023

Uh oh!

dtantsur commented Apr 26, 2023

Uh oh!

openshift-bot commented Jul 25, 2023

Uh oh!

openshift-bot commented Aug 25, 2023

Uh oh!

openshift-ci bot commented Aug 25, 2023

Uh oh!