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

MCO-817: API Migration Cleanup: Populate kubelet.yaml template feature gates from featureGateAccessor #4270

Closed
wants to merge 2 commits into from

Conversation

dkhater-redhat
Copy link
Contributor

- What I did
removed the hardcoded values from the kubelet template. Cross verified by looking on the node to see if the featuregates matched.

- How to verify it
oc get featuregate cluster -o yaml

and

❯ oc debug node/ip-10-0-46-151.ec2.internal
sh-4.4# chroot /host
sh-5.1# cat etc/kubernetes/kubelet.conf

verify the feature gates are correctly enabled/disabled on the cluster

- Description for the changelog

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 19, 2024

@dkhater-redhat: This pull request references MCO-817 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

- What I did
removed the hardcoded values from the kubelet template. Cross verified by looking on the node to see if the featuregates matched.

- How to verify it
oc get featuregate cluster -o yaml

and

❯ oc debug node/ip-10-0-46-151.ec2.internal
sh-4.4# chroot /host
sh-5.1# cat etc/kubernetes/kubelet.conf

verify the feature gates are correctly enabled/disabled on the cluster

- Description for the changelog

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 19, 2024
@openshift-ci openshift-ci bot requested review from cdoern and jkyros March 19, 2024 22:17
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2024
@dkhater-redhat
Copy link
Contributor Author

need to fix the feature gate tests for this to pass

Copy link
Contributor

openshift-ci bot commented Mar 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dkhater-redhat

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

@dkhater-redhat
Copy link
Contributor Author

/test e2e-gcp-op-single-node

1 similar comment
@dkhater-redhat
Copy link
Contributor Author

/test e2e-gcp-op-single-node

Copy link
Contributor

openshift-ci bot commented Mar 20, 2024

@dkhater-redhat: 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/okd-scos-e2e-aws-ovn ef7b6d5 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-upgrade-out-of-change ef7b6d5 link false /test e2e-aws-ovn-upgrade-out-of-change

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.

@dkhater-redhat dkhater-redhat marked this pull request as draft March 22, 2024 19:35
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 22, 2024
@dkhater-redhat
Copy link
Contributor Author

I opened this PR to test if i needed to fix the test to make it work without the default gates and ended up integrating this into another PR #4275, closing this one.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 3, 2024

@dkhater-redhat: This pull request references MCO-817 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

- What I did
removed the hardcoded values from the kubelet template. Cross verified by looking on the node to see if the featuregates matched.

- How to verify it
oc get featuregate cluster -o yaml

and

❯ oc debug node/ip-10-0-46-151.ec2.internal
sh-4.4# chroot /host
sh-5.1# cat etc/kubernetes/kubelet.conf

verify the feature gates are correctly enabled/disabled on the cluster

- Description for the changelog

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.

@dkhater-redhat dkhater-redhat marked this pull request as ready for review April 3, 2024 21:28
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 3, 2024
@dkhater-redhat
Copy link
Contributor Author

/payload 4.16 ci blocking

Copy link
Contributor

openshift-ci bot commented Apr 3, 2024

@dkhater-redhat: trigger 5 job(s) of type blocking for the ci release of OCP 4.16

  • periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-azure-sdn-upgrade
  • periodic-ci-openshift-release-master-ci-4.16-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.16-e2e-aws-sdn-serial
  • periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2b37cb70-f201-11ee-8d4a-00a98a9f2bfc-0

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-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants