-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
velero backup create --from-schedule
labels backup in local time
#4279
Labels
Bug
Good first issue
Looking to contribute to Velero? Issues with this label might be a great place to start!
Comments
Workaround: TZ=UTC velero backup create --from-schedule xxx |
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 15, 2021
…mezone. fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Singed-off-by: Xun Jiang <[email protected]> Signed-off-by: jxun <[email protected]>
3 tasks
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 16, 2021
…mezone. fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Singed-off-by: Xun Jiang <[email protected]>
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 16, 2021
…mezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]>
3 tasks
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 16, 2021
…mezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]>
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 16, 2021
…mezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]>
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 16, 2021
…mezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]>
blackpiglet
pushed a commit
to blackpiglet/velero
that referenced
this issue
Nov 16, 2021
…mezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]>
zubron
pushed a commit
that referenced
this issue
Nov 17, 2021
#4353) * fix: modify generated from schedule's backup name timestamp to UTC timezone fix #4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix #4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix #4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * modify changelog description Reword the changelog description according to comments. Signed-off-by: Xun Jiang <[email protected]> Co-authored-by: jxun <[email protected]> Co-authored-by: Xun Jiang <[email protected]>
qiuming-best
pushed a commit
to qiuming-best/velero
that referenced
this issue
Nov 22, 2021
vmware-tanzu#4353) * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * modify changelog description Reword the changelog description according to comments. Signed-off-by: Xun Jiang <[email protected]> Co-authored-by: jxun <[email protected]> Co-authored-by: Xun Jiang <[email protected]>
qiuming-best
pushed a commit
to qiuming-best/velero
that referenced
this issue
Nov 22, 2021
vmware-tanzu#4353) * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * modify changelog description Reword the changelog description according to comments. Signed-off-by: Xun Jiang <[email protected]> Co-authored-by: jxun <[email protected]> Co-authored-by: Xun Jiang <[email protected]>
danfengliu
pushed a commit
to danfengliu/velero
that referenced
this issue
Jan 25, 2022
vmware-tanzu#4353) * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * modify changelog description Reword the changelog description according to comments. Signed-off-by: Xun Jiang <[email protected]> Co-authored-by: jxun <[email protected]> Co-authored-by: Xun Jiang <[email protected]>
gyaozhou
pushed a commit
to gyaozhou/velero-read
that referenced
this issue
May 14, 2022
vmware-tanzu#4353) * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * fix: modify generated from schedule's backup name timestamp to UTC timezone fix vmware-tanzu#4279 When backup is created from schedule, and the backup name is not specified, a containing-timestamp generated name will be used. Due to velero client not set timezone to UTC, a local timezone will be used for the generated name. Signed-off-by: Xun Jiang <[email protected]> * modify changelog description Reword the changelog description according to comments. Signed-off-by: Xun Jiang <[email protected]> Co-authored-by: jxun <[email protected]> Co-authored-by: Xun Jiang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Good first issue
Looking to contribute to Velero? Issues with this label might be a great place to start!
What steps did you take:
What did you expect to happen:
To see a list of backups with the newly manually scheduled backup at the top, all with
name
s based on UTC time of backup creation.What happened instead:
You can see that the in-progress backup I just made is given a
name
based on the local time on my computer, whereas the regular backups made by the server process are labeled in UTC. Thus the manually created backup is displayed in an unnatural sort order.Environment:
Client v1.7.0; server locally patched but recent (from #4242). EKS v1.21.2.
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: