CLI shows expiration in the past for backups which have not yet executed because operations were stalled

What steps did you take and what happened: Retrieved backup info with velero get backups for a backup that had been stalled in New state for a long period of time

$ velero get backups | grep -e 202101281237 -e NAME
NAME                           STATUS       ERRORS   WARNINGS   CREATED                         EXPIRES   STORAGE LOCATION   SELECTOR
clusterstate-20210128123759    New          0        0          <nil>                           10d ago                      <none>

Backup, which hasn't executed yet, is shown as expiring in the past.

What did you expect to happen: The output should have shown either "N/A" because the backup is not eligible for GC since it hasn't started yet, or at least a date in the future.

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.

• :+1: for "I would like to see this bug fixed as soon as possible"
• :-1: for "There are more important bugs to focus on right now"