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.

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

Revert "daemon: Make binary writing idempotent" #3831

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

dgoodwin
Copy link
Contributor

@dgoodwin dgoodwin commented Aug 1, 2023

Reverts #3825
Jira issues: https://issues.redhat.com/browse/TRT-1175

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

  • This change is breaking ci 4.14 payloads, suspect will affect nightlies once it's picked up there. Details in Jira.

Not 100% sure this wasn't a flake as it's only had once payload to surface, but it looks real to me.

CC: @sinnykumari

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 1, 2023
@openshift-ci-robot
Copy link
Contributor

@dgoodwin: This pull request references Jira Issue OCPBUGS-16921, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, 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:

Reverts #3825
Jira issues: https://issues.redhat.com/browse/TRT-1175

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

  • This change is breaking ci 4.14 payloads, suspect will affect nightlies once it's picked up there. Details in Jira.

Not 100% sure this wasn't a flake as it's only had once payload to surface, but it looks real to me.

CC: @sinnykumari

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.

@sinnykumari
Copy link
Contributor

Not entirely sure if this is the cause of failure but we can debug that later. Fine with getting this reverted if this helps us unblock our payload.
/approve

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Aug 1, 2023

/payload-aggregate periodic-ci-openshift-release-master-ci-4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade 3

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2023

@dgoodwin: trigger 1 job(s) for the /payload-(job|aggregate) command

  • periodic-ci-openshift-release-master-ci-4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c38cf560-3061-11ee-8e01-26090682b9c6-0

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 1, 2023
@sinnykumari
Copy link
Contributor

umm, PR #3825 also made it to nightly 4.14.0-0.nightly-2023-08-01-020603 . Shouldn't we also seeing this issue in this nightly?

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Aug 1, 2023

That payload is not completing for some reason, something is broken there, so we've got no minor upgrade signal, pretty confident we will see it there once this is resolved.

@sinnykumari
Copy link
Contributor

yeah, missed that this nightly haven't completed.

@sinnykumari
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, sinnykumari

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

@sinnykumari
Copy link
Contributor

looks like payload job got killed. rerunning
/payload-aggregate periodic-ci-openshift-release-master-ci-4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade 3

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2023

@sinnykumari: trigger 1 job(s) for the /payload-(job|aggregate) command

  • periodic-ci-openshift-release-master-ci-4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7e69f9e0-3077-11ee-8425-3e50a8856472-0

@cgwalters
Copy link
Member

#3832 should fix the bugs that this caused

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Aug 1, 2023

Pod got deleted unexpectedly... 😠

/payload-aggregate periodic-ci-openshift-release-master-ci-4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade 3

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2023

@dgoodwin: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message. could not check if the user dgoodwin is trusted for pull request openshift/machine-config-operator#3831: error checking dgoodwin for trust: failed to check if comment came from myself: fetching userdata from GitHub: Get "http://ghproxy/app": dial tcp 172.30.229.2:80: i/o timeout

Please contact an administrator to resolve this issue.

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Aug 1, 2023

We're going to merge, we this really looks too related to not be the cause.

Authors: please bear in mind any implications for this code in 4.13 as Trevor called out on slack.

If we're wrong and this is not the cause, our deepest apologies :)

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Aug 1, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@dgoodwin: An error was encountered querying GitHub for users with public email ([email protected]) for bug OCPBUGS-16921 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: connect: connection refused

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

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 kubernetes/test-infra repository.

@cgwalters
Copy link
Member

Sure, makes sense to me to merge, it will re-break dnf-based RHEL nodes but I think that's fine, we can redo #3832 on top of the revert.

@dgoodwin
Copy link
Contributor Author

dgoodwin commented Aug 1, 2023

Thanks @cgwalters

Anyone know how to get past whatever is broken with the jira label? I moved the bug back to ASSIGNED

@cgwalters cgwalters changed the title Revert "OCPBUGS-16921: daemon: Make binary writing idempotent" Revert "daemon: Make binary writing idempotent" Aug 1, 2023
@openshift-ci-robot openshift-ci-robot removed jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 1, 2023
@openshift-ci-robot
Copy link
Contributor

@dgoodwin: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Reverts #3825
Jira issues: https://issues.redhat.com/browse/TRT-1175

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

  • This change is breaking ci 4.14 payloads, suspect will affect nightlies once it's picked up there. Details in Jira.

Not 100% sure this wasn't a flake as it's only had once payload to surface, but it looks real to me.

CC: @sinnykumari

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.

@cgwalters
Copy link
Member

Do we need a jira to merge?

@cgwalters
Copy link
Member

Well anyways if we just want to merge this, for some reason I still have the "merge button" here on this repository so...I can just...push it?

@cgwalters cgwalters merged commit 9c50df6 into openshift:master Aug 1, 2023
@dgoodwin dgoodwin deleted the revert-3825-master branch August 1, 2023 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants