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

Bug 2213552: Modified to a standard time format in DR pages #940

Merged

Conversation

GowthamShanmugam
Copy link
Contributor

Signed-off-by: Gowtham Shanmugasundaram <[email protected]>
@SanjalKatiyar
Copy link
Collaborator

/retitle Bug 2213552: Modified to a standard time format in DR pages

@openshift-ci openshift-ci bot changed the title Modified to a standard time format in DR pages Bug 2213552: Modified to a standard time format in DR pages Jul 27, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 27, 2023

@GowthamShanmugam: This pull request references Bugzilla bug 2213552, which is valid.

No validations were run on this bug

Requesting review from QA contact:
/cc @PrasadDesala

In response to this:

Bug 2213552: Modified to a standard time format in DR pages

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 27, 2023

@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: PrasadDesala.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@GowthamShanmugam: This pull request references Bugzilla bug 2213552, which is valid.

No validations were run on this bug

Requesting review from QA contact:
/cc @PrasadDesala

In response to this:

Bug 2213552: Modified to a standard time format in DR pages

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/test-infra repository.

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/test-infra repository.

@SanjalKatiyar
Copy link
Collaborator

SanjalKatiyar commented Jul 27, 2023

@GowthamShanmugam I have a doubt here (no need to make any changes in this PR)... but everywhere in ODF and now MCO while formatting time we are considering it as UTC timezone, is that alright to always convert to UTC... cluster can be in other timezones as well...
need to check how OCP does it...

@GowthamShanmugam
Copy link
Contributor Author

@GowthamShanmugam I have a doubt here (no need to make any changes in this PR)... but everywhere in ODF and now MCO while formatting time we are considering it as UTC timezone, is it all alright to always convert to UTC... cluster can be in other timezones as well... need to check how OCP does it...

Yes, clusters can be deployed in different zones, To resolve this time format issue, OCP is following UTC as a common time zone. Everywhere on the list page, they are using local time to display but popover UTC is used as a common timezone.

@SanjalKatiyar
Copy link
Collaborator

SanjalKatiyar commented Jul 27, 2023

@GowthamShanmugam I have a doubt here (no need to make any changes in this PR)... but everywhere in ODF and now MCO while formatting time we are considering it as UTC timezone, is it all alright to always convert to UTC... cluster can be in other timezones as well... need to check how OCP does it...

Yes, clusters can be deployed in different zones, To resolve this time format issue, OCP is following UTC as a common time zone. Everywhere on the list page, they are using local time to display but popover UTC is used as a common timezone.

so if OCP is using local time for list page, it means we are doing it wrong in ODF ?? I think in ODF we always use UTC (for list as well as popover) right ??

@GowthamShanmugam
Copy link
Contributor Author

@GowthamShanmugam I have a doubt here (no need to make any changes in this PR)... but everywhere in ODF and now MCO while formatting time we are considering it as UTC timezone, is it all alright to always convert to UTC... cluster can be in other timezones as well... need to check how OCP does it...

Yes, clusters can be deployed in different zones, To resolve this time format issue, OCP is following UTC as a common time zone. Everywhere on the list page, they are using local time to display but popover UTC is used as a common timezone.

so if OCP is using local time for the list page, it means we are doing it wrong in ODF ?? I think in ODF we always use UTC (for list as well as popover) right ??

OCP is using UTC + local time. LocalTime to display text and UTC as a tooltip popover text. I think the place we can't provide popover its is correct to use UTC.

@SanjalKatiyar
Copy link
Collaborator

OCP is using UTC + local time. LocalTime to display text and UTC as a tooltip popover text. I think the place we can't provide popover its is correct to use UTC.

I meant in ODF/MCO list pages as well we are using UTC instead of local time... anyway that's not related to this PR...

@SanjalKatiyar
Copy link
Collaborator

/approve
/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 31, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GowthamShanmugam, SanjalKatiyar

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-merge-robot openshift-merge-robot merged commit 291c1b3 into red-hat-storage:master Jul 31, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants