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-24030: add uncordon to mcn #4065

Merged
merged 1 commit into from Dec 13, 2023

Conversation

cdoern
Copy link
Contributor

@cdoern cdoern commented Dec 7, 2023

we were using cordon to describe both cordon and uncordon in the MCN status

@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 Dec 7, 2023
@openshift-ci-robot
Copy link
Contributor

@cdoern: This pull request references Jira Issue OCPBUGS-24030, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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.

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

In response to this:

we were using cordon to describe both cordon and uncordon in the MCN status

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 Dec 7, 2023
@rioliu-rh
Copy link

/hold for verification

@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 Dec 8, 2023
@rioliu-rh
Copy link

rioliu-rh commented Dec 8, 2023

@cdoern when I try to list additional fields I cannot see Uncordoned, but I can find it in conditions

$ oc get machineconfignode ip-10-0-117-1.us-east-2.compute.internal -o yaml | yq '.status.conditions[].type'
"Resumed"
"UpdatePrepared"
"UpdateExecuted"
"UpdatePostActionComplete"
"UpdateComplete"
"UpdateCompatible"
"Drained"
"AppliedFilesAndOS"
"Cordoned"
"RebootedNode"
"ReloadedCRIO"
"Updated"
"Uncordoned"

$ oc get machineconfignode ip-10-0-117-1.us-east-2.compute.internal -o wide
NAME                                       UPDATED   UPDATEPREPARED   UPDATEEXECUTED   UPDATEPOSTACTIONCOMPLETE   UPDATECOMPLETE   RESUMED   UPDATECOMPATIBLE   UPDATEDFILESANDOS   CORDONEDNODE   DRAINEDNODE   REBOOTEDNODE   RELOADEDCRIO
ip-10-0-117-1.us-east-2.compute.internal   True      False            False            False                      False            False     False              False               False          False         False          False

I can find it in https://github.com/openshift/api/blob/master/machineconfiguration/v1alpha1/0000_80_machineconfignode-TechPreviewNoUpgrade.crd.yaml, is there anything I missed?

create a MC, monitor the condition, it can be updated.

{"lastTransitionTime":"2023-12-08T10:31:08Z","message":"UnCordoned node. The node is reporting Unschedulable = false","reason":"UpdateCompleteUncordoned","status":"True","type":"Uncordoned"}

@cdoern
Copy link
Contributor Author

cdoern commented Dec 8, 2023

@rioliu-rh I think I forgot to update the CRD in the manifests Dir. I will push changes with that now.

we were using cordon to describe both cordon and uncordon in the MCN status

Signed-off-by: Charlie Doern <cdoern@redhat.com>
@rioliu-rh
Copy link

verify with latest code
now I can see column UNCORDONEDNODE in output of oc get machineconfignode -o wide
the condition can be updated

$ mcn ip-10-0-15-42.us-east-2.compute.internal -o wide -w
NAME                                       UPDATED   UPDATEPREPARED   UPDATEEXECUTED   UPDATEPOSTACTIONCOMPLETE   UPDATECOMPLETE   RESUMED   UPDATECOMPATIBLE   UPDATEDFILESANDOS   CORDONEDNODE   DRAINEDNODE   REBOOTEDNODE   RELOADEDCRIO   UNCORDONEDNODE
ip-10-0-15-42.us-east-2.compute.internal   False     True             Unknown          False                      False            False     True               False               True           Unknown       False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             Unknown          False                      False            False     True               False               True           True          False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             Unknown          False                      False            False     True               False               True           True          False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             Unknown          False                      False            False     True               False               True           Unknown       False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             Unknown          False                      False            False     True               False               True           True          False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             Unknown          False                      False            False     True               Unknown             True           True          False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             True             False                      False            False     True               True                True           True          False          False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             True             Unknown                    False            False     True               True                True           True          Unknown        False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             True             True                       False            False     True               True                True           True          True           False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             True             True                       False            True      True               True                True           True          True           False          False
ip-10-0-15-42.us-east-2.compute.internal   False     True             True             True                       True             True      True               True                True           True          True           False          True
ip-10-0-15-42.us-east-2.compute.internal   False     True             True             True                       True             True      True               True                True           True          True           False          True
ip-10-0-15-42.us-east-2.compute.internal   True      False            False            False                      False            False     False              False               False          False         False          False          False

@rioliu-rh
Copy link

/label qe-approved
/unhold

@openshift-ci openshift-ci bot added qe-approved Signifies that QE has signed off on this PR and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 11, 2023
@openshift-ci-robot
Copy link
Contributor

@cdoern: This pull request references Jira Issue OCPBUGS-24030, which is invalid:

  • expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.15.0" 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.

In response to this:

we were using cordon to describe both cordon and uncordon in the MCN status

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.

@cdoern
Copy link
Contributor Author

cdoern commented Dec 11, 2023

/test all

@cdoern
Copy link
Contributor Author

cdoern commented Dec 12, 2023

/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 Dec 12, 2023
@openshift-ci-robot
Copy link
Contributor

@cdoern: This pull request references Jira Issue OCPBUGS-24030, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rioliu-rh

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.

@@ -31,6 +31,7 @@ contents:
AzureWorkloadIdentity: true
BuildCSIVolumes: true
CloudDualStackNodeIPs: true
DisableKubeletCloudCredentialProviders: false
Copy link
Contributor

Choose a reason for hiding this comment

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

overall lgtm from me! Just one minor thing: what does this template change do exactly?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is to bring in some of the new featuregates that have been added to the default list

Copy link
Contributor

Choose a reason for hiding this comment

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

ack, sorry didn't catch that!

@djoshy
Copy link
Contributor

djoshy commented Dec 13, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 13, 2023
Copy link
Contributor

openshift-ci bot commented Dec 13, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cdoern, djoshy

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

/retest-required

Remaining retests: 0 against base HEAD 8477a99 and 2 for PR HEAD 4f000c9 in total

Copy link
Contributor

openshift-ci bot commented Dec 13, 2023

@cdoern: all tests passed!

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 fe00a11 into openshift:master Dec 13, 2023
14 checks passed
@openshift-ci-robot
Copy link
Contributor

@cdoern: Jira Issue OCPBUGS-24030: All pull requests linked via external trackers have merged:

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

In response to this:

we were using cordon to describe both cordon and uncordon in the MCN status

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 openshift-proxy-pull-test-container-v4.16.0-202312140031.p0.gfe00a11.assembly.stream for distgit openshift-proxy-pull-test.
All builds following this will include this PR.

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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants