Bug 1963949 - [master] Assisted installer chrony manifests missing index numberring
Summary: [master] Assisted installer chrony manifests missing index numberring
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Ori Amizur
QA Contact: Udi Kalifon
URL:
Whiteboard: AI-Team-Core KNI-EDGE-4.8
Depends On:
Blocks: 1967902
TreeView+ depends on / blocked
 
Reported: 2021-05-24 13:12 UTC by William Caban
Modified: 2022-08-28 08:45 UTC (History)
4 users (show)

Fixed In Version: OCP-Metal-v1.0.21.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1967902 (view as bug list)
Environment:
Last Closed: 2022-08-28 08:45:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift assisted-service pull 1906 0 None closed OCPBUGSM-29525 Assisted installer chrony manifests missing index numbering 2021-06-08 09:16:42 UTC

Internal Links: 1967902

Description William Caban 2021-05-24 13:12:55 UTC
Description of problem:

When deploying with assisted installer, the `masters-chrony-configuration` and `workers-chrony-configuration` MachineConfig are created. These artifact do not have an index number hence the alphanumeric sort put them at the end of the rendered manifest preventing documented customization (https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#installation-sp[…]iguration-tasks) from working.

As per discussion with engineering, the code is this:

https://github.com/openshift/assisted-service/blob/6c8d2aaef8599c4f4729cca4d6e016c7af2dfe2f/internal/network/manifests_generator.go#L184 

A similar caveat happens with the tunnel offload manifest generated by the same code

Comment 5 Udi Kalifon 2021-06-08 08:37:06 UTC
Machine configs now have an index number: 50
Verified in v1.0.21.3


Note You need to log in before you can comment on or make changes to this bug.