mgr/snap_schedule: restore yearly spec to lowercase y#56732
Conversation
3f7cc0d to
c2cf05b
Compare
c2cf05b to
3cb7111
Compare
3cb7111 to
2685bc0
Compare
|
@mchangir what happens to existing shedules (iff |
haven't explicitly tested this aspect
All of this also depends on the start time from which the year starts. With no explicit start time, the yearly snapshot would fall on Jan 01 00:00 of every year. |
So, if the mgr is updated and a spec using |
that's right |
Did that change make it to a release? We have to do something about it if the change made it to a release. |
yes, the change has made it to:
|
|
The change has been backported to quincy as well, but so far there's been no quincy release with the change. |
We can fix squid as it's still RC. We need a to get this fixed in reef. |
IMO this PR along with relevant Release Notes to bring this to users' attention and requesting users to abstain from using 'Y' and instead reverting to use 'y' if it has been used in active retention spec would be sufficient. |
There was a problem hiding this comment.
Don't forget to change formatting for year here
and
ceph/src/pybind/mgr/snap_schedule/fs/schedule.py
Lines 413 to 415 in 2685bc0
There was a problem hiding this comment.
There was a problem hiding this comment.
@neesingh-rh thanks .. this is fixed now
2685bc0 to
e3fce09
Compare
rishabh-d-dave
left a comment
There was a problem hiding this comment.
This PR branch has been merged in the testing branch now.
Introduced-by: ceph#53070 Fixes: https://tracker.ceph.com/issues/65350 Signed-off-by: Milind Changire <mchangir@redhat.com>
e3fce09 to
7151415
Compare
There was a problem hiding this comment.
QA run was successful for this PR. QA run tooks some time due infra issues (specifically CentOS 9 issue) that were persistent in Sepia lab. Besides, there were new failues in the QA run, both related and unrelated to PRs on the testing branch.
However, since this PR has gone through change since it was merged in testing branch, it needs to be tested again.
I have collected few PRs and will start next QA in little time. @mchangir If current changes are final, shall I add this one to it right away?
|
I've applied my other label, let me know if it shouldn't be put through testing. |
* refs/pull/56732/head: mgr/snap_schedule: restore yearly spec to lowercase y Reviewed-by: Jos Collin <jcollin@redhat.com> Reviewed-by: Venky Shankar <vshankar@redhat.com> Reviewed-by: Rishabh Dave <ridave@redhat.com>
There was a problem hiding this comment.
QA run was successful - https://tracker.ceph.com/projects/cephfs/wiki/main#3-May-2024.
Testing took more time than expected because there were 25-30 new failures. Most of them caused by a PR in the testing branch but these were resolved on removing that PR.
|
|
|
jenkins test make check |
|
Waiting for |
|
|
Fixes: https://tracker.ceph.com/issues/65350
Signed-off-by: Milind Changire mchangir@redhat.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e