Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug 2060970: data/data/coreos/fcos.json: update initial FCOS to 35.20220213.3.0 #5680

Merged
merged 1 commit into from
Mar 8, 2022
Merged

Bug 2060970: data/data/coreos/fcos.json: update initial FCOS to 35.20220213.3.0 #5680

merged 1 commit into from
Mar 8, 2022

Conversation

vrutkovs
Copy link
Member

@vrutkovs vrutkovs commented Mar 4, 2022

This updates latest FCOS used for OKD to FCOS 35.20220213.3.0

@vrutkovs vrutkovs changed the title data/data/coreos/fcos.json: update initial FCOS to 35.20220213.3.0 Bug 2060970: data/data/coreos/fcos.json: update initial FCOS to 35.20220213.3.0 Mar 4, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Mar 4, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2022

@vrutkovs: This pull request references Bugzilla bug 2060970, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.11.0) matches configured target release for branch (4.11.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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

In response to this:

Bug 2060970: data/data/coreos/fcos.json: update initial FCOS to 35.20220213.3.0

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
Copy link
Member Author

vrutkovs commented Mar 4, 2022

/test okd-e2e-vsphere
/test okd-e2e-gcp

@vrutkovs
Copy link
Member Author

vrutkovs commented Mar 4, 2022

/cherry-pick release-4.10
/hold

for OKD rehearsals

@openshift-cherrypick-robot
Copy link

@vrutkovs: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.10
/hold

for OKD rehearsals

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 openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2022
@vrutkovs
Copy link
Member Author

vrutkovs commented Mar 4, 2022

/hold cancel

installs passed on all OKD tests

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2022
@vrutkovs
Copy link
Member Author

vrutkovs commented Mar 5, 2022

/retest

@patrickdillon
Copy link
Contributor

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 8, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2022
@openshift-bot
Copy link
Contributor

/retest-required

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

6 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 8, 2022 •
edited
Loading

@vrutkovs: The following tests 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/e2e-aws-single-node d8c8ff3 link false /test e2e-aws-single-node
ci/prow/e2e-metal-ipi-ovn-ipv6 d8c8ff3 link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-libvirt d8c8ff3 link false /test e2e-libvirt
ci/prow/okd-e2e-aws-upgrade d8c8ff3 link false /test okd-e2e-aws-upgrade
ci/prow/okd-e2e-gcp d8c8ff3 link false /test okd-e2e-gcp
ci/prow/e2e-crc d8c8ff3 link false /test e2e-crc
ci/prow/e2e-ibmcloud d8c8ff3 link false /test e2e-ibmcloud
ci/prow/e2e-openstack d8c8ff3 link false /test e2e-openstack
ci/prow/okd-e2e-vsphere d8c8ff3 link false /test okd-e2e-vsphere
ci/prow/e2e-azure-upi d8c8ff3 link false /test e2e-azure-upi

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.

@vrutkovs
Copy link
Member Author

vrutkovs commented Mar 8, 2022

/skip

@openshift-bot
Copy link
Contributor

/retest-required

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

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-merge-robot openshift-merge-robot merged commit 24493a1 into openshift:master Mar 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 8, 2022

@vrutkovs: All pull requests linked via external trackers have merged:

Bugzilla bug 2060970 has been moved to the MODIFIED state.

In response to this:

Bug 2060970: data/data/coreos/fcos.json: update initial FCOS to 35.20220213.3.0

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-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Mar 8, 2022
Closed
@openshift-cherrypick-robot
Copy link

@vrutkovs: new pull request created: #5690

In response to this:

/cherry-pick release-4.10
/hold

for OKD rehearsals

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@miabbott miabbott Awaiting requested review from miabbott

@sohankunkerkar sohankunkerkar Awaiting requested review from sohankunkerkar

Assignees

@patrickdillon patrickdillon

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@vrutkovs @openshift-cherrypick-robot @patrickdillon @openshift-bot @openshift-merge-robot