Bug 2183466
| Summary: | User cannot determine cluster time zone | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Simon Foucek <sfoucek> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED MIGRATED | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9.2 | CC: | cluster-maint, nwahl |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-22 20:07:41 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Simon Foucek
2023-03-31 09:18:55 UTC
The DC (designated controller) node runs the scheduler and evaluates the rules. The evaluation of date-based rules is based on the time on the DC. It looks as if the time used for evaluation is relative to the system's configured time zone, rather than based on UTC. I suspect this was chosen for convenience: many users will find it less error-prone to configure rules based on their local time zone. So the result of the evaluation depends on which node is DC. There is no persistent "cluster-wide" time -- to the extent that there is such a thing, it's the time of the current DC. One possible solution might be to add a new "time_zone" field to rules. Another might be to have a cluster-wide time zone property that overrides the system's time zone (via pe_working_set_t:now). If I understand the logic you describe, it would be best to add the possibility to set the TZ for DC, so it would not change when moving between nodes. The user could also see which TZ is set up for the cluster. (In reply to Simon Foucek from comment #2) > If I understand the logic you describe, it would be best to add the > possibility to set the TZ for DC, so it would not change when moving between > nodes. The user could also see which TZ is set up for the cluster. The way I'm thinking about it, the property would set the time zone for the whole cluster, not just for the DC. It wouldn't have to affect the system time -- only the time that Pacemaker uses. That's probably also a lot easier to implement than another approach. That seems like a fine solution for me. I would also add the possibility of checking the property's current value. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |