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.

Sign up for GitHub

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

Jump to bottom

oadp-1.3: Velero Args yaml does not accept time as string #1308

Closed
Tracked by #1307
kaovilai opened this issue Feb 1, 2024 · 3 comments
Closed
Tracked by #1307

oadp-1.3: Velero Args yaml does not accept time as string #1308

kaovilai opened this issue Feb 1, 2024 · 3 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@kaovilai
Copy link
Member

kaovilai commented Feb 1, 2024

No description provided.

This was referenced Feb 1, 2024
Closed
Closed
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kaovilai
Copy link
Member Author

kaovilai commented May 2, 2024

/lifecycle frozen

@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 2, 2024
@kaovilai
Copy link
Member Author

Fixed via #1430

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@openshift-bot @kaovilai