Bug 1814019 - Instructions misleading in how to configure chronyd on OCP4
Summary: Instructions misleading in how to configure chronyd on OCP4
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
Depends On:
TreeView+ depends on / blocked
Reported: 2020-03-16 18:41 UTC by Rob Gregory
Modified: 2020-11-02 01:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-02 01:28:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Rob Gregory 2020-03-16 18:41:51 UTC
>Document URL: 


>Section Number and Name: 

Configuring chrony time service
Section 2.

>Describe the issue: 

Existing text: "You can change it to worker or make an additional MachineConfig for the worker role:"

If you change the machineconfig, it only takes the most recently changed role. You need to create a new machineconfig file to apply the change to multiple node roles.

>Suggestions for improvement: 

Docs should specify that if you want the change applied to multiple roles, then multiple machineconfig files need to be created. The wording suggests you can just change the role and re-apply the same machineconfig, which is not the case. 

>Additional information: 

Hi docs team :) thank you!

Comment 2 Vikram Goyal 2020-11-02 01:28:50 UTC
OCP 4.2 and 4.3 are EOL after OCP 4.5 and 4.6 GA respectively.

This is a notification that this bug is being CLOSED as EOL as per the previous comment on this bug.

See my announcement email sent a week ago here [2].

If you have a customer case with a support exception or if you think this issue still applies on 4.4+, please reopen and include those details. When reopening, please change the reported version to 4.4+.

[1]: https://access.redhat.com/support/policy/updates/openshift
[2]: http://post-office.corp.redhat.com/archives/openshift-sme/2020-October/msg00826.html

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