Skip to content

OCPBUGS-2640: Fix 'invalid magic number 0' bug (#11338)#143

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.11from
jan--f:pr-11338-4.11
Oct 21, 2022
Merged

OCPBUGS-2640: Fix 'invalid magic number 0' bug (#11338)#143
openshift-merge-robot merged 1 commit intoopenshift:release-4.11from
jan--f:pr-11338-4.11

Conversation

@jan--f
Copy link

@jan--f jan--f commented Oct 20, 2022

Signed-off-by: Ganesh Vernekar ganeshvern@gmail.com
(cherry picked from commit 83d738e)

@codesome @jan--f
Fix 'invalid magic number 0' bug (prometheus#11338)
f072fc4 
Signed-off-by: Ganesh Vernekar <ganeshvern@gmail.com>
(cherry picked from commit 83d738e)
@openshift-ci
Copy link

openshift-ci bot commented Oct 20, 2022

@jan--f: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-2640: Fix 'invalid magic number 0' bug (prometheus#11338)

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-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 20, 2022
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 20, 2022

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-1718 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-1718 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
  • bug has dependents

Requesting review from QA contact:
/cc @juzhao

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Signed-off-by: Ganesh Vernekar ganeshvern@gmail.com
(cherry picked from commit 83d738e)

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-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Oct 20, 2022
@openshift-ci openshift-ci bot requested review from raptorsun and sthaha October 20, 2022 11:06
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 20, 2022
@simonpasquier
Copy link

simonpasquier commented Oct 20, 2022

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. lgtm Indicates that a PR is ready to be merged. labels Oct 20, 2022
@openshift-ci
Copy link

openshift-ci bot commented Oct 20, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, simonpasquier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [jan--f,simonpasquier]

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

@openshift-ci
Copy link

openshift-ci bot commented Oct 20, 2022

@jan--f: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@juzhao
Copy link

juzhao commented Oct 21, 2022

tested with PR on SNO cluster, rebooted the node for a few times, did not see the error.
/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 21, 2022
@juzhao
Copy link

juzhao commented Oct 21, 2022

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 21, 2022
@openshift-merge-robot openshift-merge-robot merged commit e751c61 into openshift:release-4.11 Oct 21, 2022
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 21, 2022

@jan--f: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Signed-off-by: Ganesh Vernekar ganeshvern@gmail.com
(cherry picked from commit 83d738e)

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.

@raptorsun raptorsun mentioned this pull request Nov 4, 2022
Merged
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/prometheus that referenced this pull request Dec 16, 2025
@jacobbaungard
Konflux: set correct target branch (openshift#143)
5068799 
Signed-off-by: Jacob Baungard Hansen <jacobbaungard@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@raptorsun raptorsun Awaiting requested review from raptorsun

@sthaha sthaha Awaiting requested review from sthaha

Assignees

@simonpasquier simonpasquier

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@jan--f @openshift-ci-robot @simonpasquier @juzhao @openshift-merge-robot @codesome