Skip to content

NTP / Chronyd do not restart on failure. #91

@Jeremy-Boyle

Description

@Jeremy-Boyle

What steps did you take and what happened:
Ticket opened with Broadcom support #36066818

What did you expect to happen:
NTP Should be resilient to failures and should restart automatically like VMtools for ubuntu and photon images. The issue is that the systemctl service file does not have restart always.

Is there anything else you would like to add?
This can be fixed by creating a custom cluster class on vCenter 8 to fix the images, however, this is not possible with vCenter 7 using the Tanzu TKGS Supervisor with the default cluster class, and TKC Resources. Fixing it at the image level would be the best fix for backwards compatibility. Also, NTP is on by default with TKGS, and will automatically enable NTP based on the NTP service that the supervisor is using and it is difficult to monitor and can cause issues. Please see internal ticket for more information.

Please tell us about your environment.
vCenter 7, vCenter 8

This effects all current and previous images.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions