Skip to content

Bug 1825339: [4.4] crio: manage ns lifecycle#1871

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.4from
haircommander:manage-ns-4.4
Jul 9, 2020
Merged

Bug 1825339: [4.4] crio: manage ns lifecycle#1871
openshift-merge-robot merged 1 commit intoopenshift:release-4.4from
haircommander:manage-ns-4.4

Conversation

@haircommander
Copy link
Copy Markdown
Member

- What I did
change the entry in crio.conf template to manage ns lifecycle
As it is more secure and gives cri-o more control of namespace lifecycle. Also change the outdated config name value

backport of #1689

- How to verify it

- Description for the changelog

CRI-O now manages namespace lifecycle

change the entry in crio.conf template to manage ns lifecycle
As it is more secure and gives cri-o more control of namespace lifecycle. Also change the outdated config name value

Signed-off-by: Peter Hunt <pehunt@redhat.com>
@openshift-ci-robot openshift-ci-robot 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 Jun 24, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.4.z) matches configured target release for branch (4.4.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1820118 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1820118 targets the "4.5.0" release, which is one of the valid target releases: 4.5.0, 4.5.z
  • bug has dependents
Details

In response to this:

Bug 1825339: [4.4] crio: manage ns lifecycle

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.

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

/retest

1 similar comment
@haircommander
Copy link
Copy Markdown
Member Author

/retest

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

/skip

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 25, 2020
@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

/assign @umohnani8 @mtrmac

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

/skip

@haircommander
Copy link
Copy Markdown
Member Author

/test e2e-metal-ipi

@haircommander
Copy link
Copy Markdown
Member Author

we may need some variation of openshift/cluster-network-operator#645

I think we should wait till next week on this

@rphillips
Copy link
Copy Markdown
Contributor

Holding until next week... Feel free to remove.

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 26, 2020
@mtrmac mtrmac removed their assignment Jun 26, 2020
@dulek
Copy link
Copy Markdown

dulek commented Jun 29, 2020

For sure we need openshift/cluster-network-operator#684 to get in before this.

@luis5tb
Copy link
Copy Markdown

luis5tb commented Jul 6, 2020

This got already merged: openshift/cluster-network-operator#684

@haircommander
Copy link
Copy Markdown
Member Author

excellent!

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@haircommander: This pull request references Bugzilla bug 1825339. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Bug 1825339: [4.4] crio: manage ns lifecycle

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.

@haircommander
Copy link
Copy Markdown
Member Author

excellent!

@haircommander haircommander reopened this Jul 6, 2020
@openshift-ci-robot openshift-ci-robot removed the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jul 6, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jul 6, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@haircommander: This pull request references Bugzilla bug 1825339, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (DUPLICATE) instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 1825339: [4.4] crio: manage ns lifecycle

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.

@haircommander
Copy link
Copy Markdown
Member Author

I confused myself, this was not meant to be closed

@haircommander
Copy link
Copy Markdown
Member Author

/bugzilla refresh

@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 Jul 6, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@haircommander: This pull request references Bugzilla bug 1825339, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.4.z) matches configured target release for branch (4.4.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1820118 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1820118 targets the "4.5.0" release, which is one of the valid target releases: 4.5.0, 4.5.z
  • bug has dependents
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.

@openshift-ci-robot openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jul 6, 2020
@haircommander
Copy link
Copy Markdown
Member Author

/test e2e-aws

@umohnani8
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 8, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, kikisdeliveryservice, umohnani8

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 [kikisdeliveryservice]

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

@haircommander
Copy link
Copy Markdown
Member Author

/hold cancel

the dependent PRs have all merged

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 8, 2020
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@kikisdeliveryservice
Copy link
Copy Markdown
Contributor

/skip

@sdodson sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jul 8, 2020
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 1cb23e0 into openshift:release-4.4 Jul 9, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@haircommander: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1871. Bugzilla bug 1825339 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1825339: [4.4] crio: manage ns lifecycle

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. 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.