Skip to content

Conversation

@sinnykumari
Copy link
Contributor

systemd's implementation of InaccessiblePaths has
quadratic behavior in number of mounts.
The fix to rpm-ostree is inbound. But...adding this workaround which
has the MCD dynamically reconfigure the system to drop that config will
help unstick clusters so they can get the real fix.

Manual backport of PR #329

systemd's implementation of `InaccessiblePaths` has
quadratic behavior in number of mounts.
The fix to rpm-ostree is inbound.  But...adding this workaround which
has the MCD dynamically reconfigure the system to drop that config will
help unstick clusters so they can get the real fix.

Manual backport of PR openshift#329
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 17, 2022

@sinnykumari: 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:

daemon: Add a workaround for bug 2111817

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 17, 2022
@sinnykumari sinnykumari changed the title daemon: Add a workaround for bug 2111817 OCPBUGS-197: daemon: Add a workaround for bug 2111817 Aug 17, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 17, 2022

@sinnykumari: 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-197: daemon: Add a workaround for bug 2111817

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 jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 17, 2022
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sinnykumari: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead
  • expected [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197) to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

Details

In response to this:

systemd's implementation of InaccessiblePaths has
quadratic behavior in number of mounts.
The fix to rpm-ostree is inbound. But...adding this workaround which
has the MCD dynamically reconfigure the system to drop that config will
help unstick clusters so they can get the real fix.

Manual backport of PR #329

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 Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 17, 2022

@sinnykumari: 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:

/bugzilla 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.

@sinnykumari
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sinnykumari: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead
  • expected [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197) to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

Details

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.

@sdodson
Copy link
Member

sdodson commented Aug 17, 2022

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sdodson: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead
  • expected [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197) to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

Details

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.

@sdodson
Copy link
Member

sdodson commented Aug 17, 2022

/jira refresh
Just trying to figure out what field the bot uses for

expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sdodson: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead
  • expected [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197) to depend on a bug targeting a version in 4.12.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

Details

In response to this:

/jira refresh
Just trying to figure out what field the bot uses for

expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead

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 Author

Fixed depends on, retrying
/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sinnykumari: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected the bug to target the "4.11.0" version, but it targets "4.11.z" instead
  • expected dependent Jira Issue OCPBUGSM-47294 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is QE Review instead
  • expected dependent Jira Issue OCPBUGSM-47294 to target a version in 4.12.0, 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.

Details

In response to this:

Fixed depends on, retrying
/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.

@sdodson
Copy link
Member

sdodson commented Aug 17, 2022

@sinnykumari I think the jira bug validation rules aren't correct, I'll follow up with w/ DPTP on that if you can work on getting QE to test the 4.12 bug in the mean time.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 17, 2022

@sinnykumari: 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-upgrade-single-node aef55a4 link false /test e2e-aws-upgrade-single-node
ci/prow/e2e-aws-disruptive aef55a4 link false /test e2e-aws-disruptive
ci/prow/e2e-aws-single-node aef55a4 link false /test e2e-aws-single-node

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.

@sinnykumari
Copy link
Contributor Author

@sinnykumari I think the jira bug validation rules aren't correct, I'll follow up with w/ DPTP on that if you can work on getting QE to test the 4.12 bug in the mean time.

Yeah, working on it!

@sinnykumari
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot removed the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Aug 17, 2022
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sinnykumari: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected dependent Jira Issue OCPBUGSM-47294 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is QE Review 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.

Details

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.

@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Aug 17, 2022
@sdodson
Copy link
Member

sdodson commented Aug 17, 2022

openshift/release#31412 will fix the jira config up

@sdodson
Copy link
Member

sdodson commented Aug 17, 2022

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 17, 2022

@sdodson: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected dependent Jira Issue OCPBUGSM-47294 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is QE Review 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.

Details

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

/label backport-risk-assessed

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 17, 2022

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

Details

In response to this:

/label backport-risk-assessed

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.

@yuqi-zhang
Copy link
Contributor

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

Is that... new?

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 17, 2022
Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

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

/lgtm

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

openshift-ci bot commented Aug 17, 2022

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [sinnykumari,yuqi-zhang]

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 Author

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

Is that... new?

/label backport-risk-assessed

That's because Colin wasn't added in the list. Should be now with openshift/release#31449 merged.

@sinnykumari
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 18, 2022

@sinnykumari: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected dependent Jira Issue OCPBUGSM-47294 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Done (Done) 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.

Details

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.

@sinnykumari
Copy link
Contributor Author

fun, this PR is seeing edges of both bugzilla and Jira world

@sinnykumari
Copy link
Contributor Author

/assign @rioliu-rh

@sdodson
Copy link
Member

sdodson commented Aug 18, 2022

/jira refresh

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 18, 2022

@sdodson: This pull request references [Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197), which is invalid:

  • expected dependent Jira Issue OCPBUGSM-47294 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Done (Done) 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.

Details

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.

@sdodson sdodson added 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. bugzilla/valid-bug Indicates that a referenced Bugzilla 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 Aug 18, 2022
@openshift-merge-robot openshift-merge-robot merged commit 54a105e into openshift:release-4.11 Aug 18, 2022
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 18, 2022

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

[Jira Issue OCPBUGS-197](https://issues.redhat.com//browse/OCPBUGS-197) has been moved to the MODIFIED state.

Details

In response to this:

systemd's implementation of InaccessiblePaths has
quadratic behavior in number of mounts.
The fix to rpm-ostree is inbound. But...adding this workaround which
has the MCD dynamically reconfigure the system to drop that config will
help unstick clusters so they can get the real fix.

Manual backport of PR #329

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

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants