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-44882: Add NTP sources to generated install-config.yaml #7028

Conversation

jhernand
Copy link
Contributor

In OpenShift 4.18 a new additionalNTPServers field was added to the baremetal platform section of the install-config.yaml file . This needs to be populated with the NTP sources provided by the user in order to correctly set time before installation of new nodes using the baremetal provisioning flow.

List all the issues related to this PR

https://issues.redhat.com/browse/OCPBUGS-44882

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Tested creating a baremetal cluster and checking the generated installer configuration file.

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

@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/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Nov 26, 2024
@openshift-ci-robot
Copy link

@jhernand: This pull request references Jira Issue OCPBUGS-44882, which is invalid:

  • expected the bug to target the "4.19.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:

In OpenShift 4.18 a new additionalNTPServers field was added to the baremetal platform section of the install-config.yaml file . This needs to be populated with the NTP sources provided by the user in order to correctly set time before installation of new nodes using the baremetal provisioning flow.

List all the issues related to this PR

https://issues.redhat.com/browse/OCPBUGS-44882

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Tested creating a baremetal cluster and checking the generated installer configuration file.

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 26, 2024
@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 26, 2024
Copy link

openshift-ci bot commented Nov 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhernand

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 Nov 26, 2024
@zaneb
Copy link
Member

zaneb commented Nov 26, 2024

/lgtm

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

zaneb commented Nov 26, 2024

/jira refresh
/cherry-pick release-4.18

@openshift-cherrypick-robot

@zaneb: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/jira refresh
/cherry-pick release-4.18

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-sigs/prow repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 26, 2024
@openshift-ci-robot
Copy link

@zaneb: This pull request references Jira Issue OCPBUGS-44882, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh
/cherry-pick release-4.18

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 removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 26, 2024
Copy link

codecov bot commented Nov 26, 2024

Codecov Report

Attention: Patch coverage is 86.36364% with 3 lines in your changes missing coverage. Please review.

Project coverage is 68.80%. Comparing base (8dc67a1) to head (234490f).
Report is 7 commits behind head on master.

Files with missing lines Patch % Lines
internal/provider/external/base.go 0.00% 1 Missing ⚠️
internal/provider/nutanix/installConfig.go 0.00% 1 Missing ⚠️
internal/provider/vsphere/installConfig.go 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #7028      +/-   ##
==========================================
+ Coverage   68.22%   68.80%   +0.58%     
==========================================
  Files         273      279       +6     
  Lines       39079    40187    +1108     
==========================================
+ Hits        26660    27652     +992     
- Misses      10007    10093      +86     
- Partials     2412     2442      +30     
Files with missing lines Coverage Δ
internal/installcfg/builder/builder.go 79.59% <100.00%> (ø)
internal/provider/baremetal/installConfig.go 42.85% <100.00%> (ø)
internal/provider/registry/registry.go 63.51% <100.00%> (ø)
internal/provider/external/base.go 0.00% <0.00%> (ø)
internal/provider/nutanix/installConfig.go 0.00% <0.00%> (ø)
internal/provider/vsphere/installConfig.go 0.00% <0.00%> (ø)

... and 19 files with indirect coverage changes

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8dc67a1 and 2 for PR HEAD a5ab953 in total

@jhernand
Copy link
Contributor Author

/hold

I need to verify if we should take the NTP servers from the cluster or from the infrastructure environment.

@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 Nov 26, 2024
@zaneb
Copy link
Member

zaneb commented Nov 26, 2024

I need to verify if we should take the NTP servers from the cluster or from the infrastructure environment.

FWIW in ABI we pass them in the InfraEnv, so for ABI purposes that needs to make it all the way through to here. I'm not clear on whether the Cluster inherits the additionalNTPSources from its InfraEnv(s).

/lgtm cancel

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 26, 2024
In OpenShift 4.18 a new `additionalNTPServers` field was added to the
baremetal platform section of the `install-config.yaml` file . This
needs to be populated with the NTP sources provided by the user in order
to correctly set time before installation of new nodes using the
baremetal provisioning flow.

Related: https://issues.redhat.com/browse/OCPBUGS-44882
Signed-off-by: Juan Hernandez <[email protected]>
@jhernand jhernand force-pushed the add_npt_sources_to_generated_install_config branch from a5ab953 to 234490f Compare November 26, 2024 22:32
@jhernand
Copy link
Contributor Author

FWIW in ABI we pass them in the InfraEnv, so for ABI purposes that needs to make it all the way through to here. I'm not clear on whether the Cluster inherits the additionalNTPSources from its InfraEnv(s).

Yes, the new version of the patch uses the NTP sources for the cluster first, and if that is empty then it uses the ones from the infrastructure environments.

@zaneb
Copy link
Member

zaneb commented Nov 27, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 27, 2024
@jhernand
Copy link
Contributor Author

/retest

@gamli75
Copy link
Contributor

gamli75 commented Nov 27, 2024

@jhernand After it will be merged, please backport it to release-4.18 and release-ocm-2.12 branches

@jhernand
Copy link
Contributor Author

/retest

Copy link

openshift-ci bot commented Nov 27, 2024

@jhernand: 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/edge-e2e-oci-assisted 234490f link false /test edge-e2e-oci-assisted
ci/prow/edge-e2e-nutanix-assisted-4-14 234490f link false /test edge-e2e-nutanix-assisted-4-14
ci/prow/edge-e2e-nutanix-assisted 234490f link false /test edge-e2e-nutanix-assisted
ci/prow/edge-e2e-oci-assisted-4-14 234490f link false /test edge-e2e-oci-assisted-4-14

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-sigs/prow repository. I understand the commands that are listed here.

@jhernand
Copy link
Contributor Author

/retest

@gamli75
Copy link
Contributor

gamli75 commented Nov 28, 2024

@jhernand nutanix jobs are broken https://issues.redhat.com/browse/MGMT-19170
you can override it.
@adriengentil can you check the OCI tests? it looks broken as well

@jhernand
Copy link
Contributor Author

Thanks @gamli75 . I don't have permisson to override jobs. Do you?

@jhernand
Copy link
Contributor Author

/unhold

@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 Nov 28, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 160a229 into openshift:master Nov 28, 2024
18 of 22 checks passed
@openshift-ci-robot
Copy link

@jhernand: Jira Issue OCPBUGS-44882: All pull requests linked via external trackers have merged:

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

In response to this:

In OpenShift 4.18 a new additionalNTPServers field was added to the baremetal platform section of the install-config.yaml file . This needs to be populated with the NTP sources provided by the user in order to correctly set time before installation of new nodes using the baremetal provisioning flow.

List all the issues related to this PR

https://issues.redhat.com/browse/OCPBUGS-44882

  • New Feature
  • Enhancement
  • Bug fix
  • Tests
  • Documentation
  • CI/CD

What environments does this code impact?

  • Automation (CI, tools, etc)
  • Cloud
  • Operator Managed Deployments
  • None

How was this code tested?

  • assisted-test-infra environment
  • dev-scripts environment
  • Reviewer's test appreciated
  • Waiting for CI to do a full test run
  • Manual (Elaborate on how it was tested)
  • No tests needed

Tested creating a baremetal cluster and checking the generated installer configuration file.

Checklist

  • Title and description added to both, commit and PR.
  • Relevant issues have been associated (see CONTRIBUTING guide)
  • This change does not require a documentation update (docstring, docs, README, etc)
  • Does this change include unit-tests (note that code changes require unit-tests)

Reviewers Checklist

  • Are the title and description (in both PR and commit) meaningful and clear?
  • Is there a bug required (and linked) for this change?
  • Should this PR be backported?

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-cherrypick-robot

@zaneb: new pull request created: #7037

In response to this:

/jira refresh
/cherry-pick release-4.18

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-sigs/prow repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-agent-installer-api-server
This PR has been included in build ose-agent-installer-api-server-container-v4.19.0-202411282238.p0.g160a229.assembly.stream.el9.
All builds following this will include this PR.

@jhernand
Copy link
Contributor Author

/cherry-pick release-ocm-2.12

@openshift-cherrypick-robot

@jhernand: new pull request created: #7038

In response to this:

/cherry-pick release-ocm-2.12

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-sigs/prow 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. jira/severity-moderate Referenced Jira bug's severity is moderate 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. 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants