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

OCPBUGS-30239: Prevent OVS-configuration to run before kdump #4213

Merged
merged 1 commit into from Mar 13, 2024

Conversation

jbtrystram
Copy link
Contributor

Kdump will generate it's initramfs based on the running state when kdump.service run If OVS has already run, the kdump fails to gather a working network config, which prevent network log exports, sush as SSH.

See https://issues.redhat.com/browse/OCPBUGS-28239

Ideally we would need that to be backported to 4.14, otherwise I will add a systemd drop-in as a workaround in RHCOS

Kdump will generate it's initramfs based on the running state when kdump.service run
If OVS has already run, the kdump fails to gather a working network config,
which prevent network log exports, sush as SSH.
See https://issues.redhat.com/browse/OCPBUGS-28239
Copy link
Member

@travier travier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/retest

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2024
@travier
Copy link
Member

travier commented Feb 26, 2024

/title OCPBUGS-28239: Prevent OVS-configuration to run before kdump

@travier
Copy link
Member

travier commented Feb 26, 2024

/retitle OCPBUGS-28239: Prevent OVS-configuration to run before kdump

@openshift-ci openshift-ci bot changed the title Prevent OVS-configuration to run before kdump OCPBUGS-28239: Prevent OVS-configuration to run before kdump Feb 26, 2024
@jbtrystram
Copy link
Contributor Author

/retest

@yuqi-zhang
Copy link
Contributor

/approve

Seems safe, but also just in case

/hold

cc @trozet @cybertron in case there's any concerns, as the networking team generally manages that template

@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 Feb 26, 2024
Copy link
Contributor

openshift-ci bot commented Feb 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jbtrystram, travier, yuqi-zhang

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 Feb 26, 2024
@coiby
Copy link

coiby commented Feb 28, 2024

This PR looks good to me!

@jbtrystram
Copy link
Contributor Author

/retest

@cybertron
Copy link
Member

Makes sense. I have also run into issues using an ovs bridge in an initrd so I can see where that would be a problem.

@cybertron
Copy link
Member

/jira refresh

Not sure why the bot did not pick up the reference in the PR title.

@openshift-ci-robot
Copy link
Contributor

@cybertron: Jira Issue OCPBUGS-28239 is in a security level that is not in the allowed security levels for this repo.
Allowed security levels for this repo are:

  • Red Hat Employee
  • default

In response to this:

/jira refresh

Not sure why the bot did not pick up the reference in the PR title.

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.

@jbtrystram
Copy link
Contributor Author

/retitle OCPBUGS-30239: Prevent OVS-configuration to run before kdump

@openshift-ci openshift-ci bot changed the title OCPBUGS-28239: Prevent OVS-configuration to run before kdump OCPBUGS-30239: Prevent OVS-configuration to run before kdump Mar 5, 2024
@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 Mar 5, 2024
@openshift-ci-robot
Copy link
Contributor

@jbtrystram: This pull request references Jira Issue OCPBUGS-30239, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

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:

Kdump will generate it's initramfs based on the running state when kdump.service run If OVS has already run, the kdump fails to gather a working network config, which prevent network log exports, sush as SSH.

See https://issues.redhat.com/browse/OCPBUGS-28239

Ideally we would need that to be backported to 4.14, otherwise I will add a systemd drop-in as a workaround in RHCOS

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.

@jbtrystram
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@jbtrystram: This pull request references Jira Issue OCPBUGS-30239, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

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.

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.

@jbtrystram
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 5, 2024
@openshift-ci-robot
Copy link
Contributor

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

Requesting review from QA contact:
/cc @mike-nguyen

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.

@openshift-ci openshift-ci bot requested a review from mike-nguyen March 5, 2024 09:15
@travier
Copy link
Member

travier commented Mar 7, 2024

/unhold
based on @cybertron comment.

@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 7, 2024
@travier
Copy link
Member

travier commented Mar 7, 2024

/retest
Can someone from the MCO team do final pass / merge on this PR? Thanks

@jbtrystram
Copy link
Contributor Author

jbtrystram commented Mar 7, 2024

Note that this requires a fresh build of RHCOS with this fix

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 53bbe70 and 2 for PR HEAD e1770af in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD a073953 and 1 for PR HEAD e1770af in total

@yuqi-zhang
Copy link
Contributor

The PR has all the necessary labels, just seems that single node job is flaky.

/test e2e-gcp-op-single-node

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD da2a7ae and 0 for PR HEAD e1770af in total

@openshift-ci-robot
Copy link
Contributor

/hold

Revision e1770af was retested 3 times: holding

@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 11, 2024
@sinnykumari
Copy link
Contributor

Let's retry
/retest
/hold cancel

@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 13, 2024
Copy link
Contributor

openshift-ci bot commented Mar 13, 2024

@jbtrystram: The following test 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/okd-scos-e2e-aws-ovn e1770af link false /test okd-scos-e2e-aws-ovn

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-merge-bot openshift-merge-bot bot merged commit a24148c into openshift:master Mar 13, 2024
16 of 17 checks passed
@openshift-ci-robot
Copy link
Contributor

@jbtrystram: Jira Issue OCPBUGS-30239: All pull requests linked via external trackers have merged:

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

In response to this:

Kdump will generate it's initramfs based on the running state when kdump.service run If OVS has already run, the kdump fails to gather a working network config, which prevent network log exports, sush as SSH.

See https://issues.redhat.com/browse/OCPBUGS-28239

Ideally we would need that to be backported to 4.14, otherwise I will add a systemd drop-in as a workaround in RHCOS

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.

@sinnykumari
Copy link
Contributor

/cherry-pick release-4.15

@openshift-cherrypick-robot

@sinnykumari: new pull request created: #4259

In response to this:

/cherry-pick release-4.15

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
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-machine-config-operator-container-v4.16.0-202403141746.p0.ga24148c.assembly.stream.el8 for distgit ose-machine-config-operator.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-03-21-152650

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants