-
Notifications
You must be signed in to change notification settings - Fork 514
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
[DO NOT MERGE] Backport some fixes from master
to ozone-1.4
#6096
[DO NOT MERGE] Backport some fixes from master
to ozone-1.4
#6096
Conversation
…ile until loading all volumes. (apache#5757) (cherry picked from commit 027febe)
…ient (apache#5789) (cherry picked from commit c990899)
(cherry picked from commit 0112a71)
(cherry picked from commit 4cda788)
(cherry picked from commit 25886f3)
…is-replicated (apache#5726) (cherry picked from commit f3872a7)
…pache#5890) (cherry picked from commit 6d41b87)
(cherry picked from commit 0c2e2a6)
…origins should be handled during decommission (apache#5984) (cherry picked from commit 46b6f3d)
(cherry picked from commit 48d547c)
…apache#6015) (cherry picked from commit abc3e1f)
(cherry picked from commit b13f01c)
(cherry picked from commit 9018728)
/pending DO NOT MERGE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking this issue as un-mergeable as requested.
Please use /ready
comment when it's resolved.
Please note that the PR will be closed after 21 days of inactivity from now. (But can be re-opened anytime later...)
DO NOT MERGE
…ket owner (apache#5816) (cherry picked from commit 077e09b)
@ashishkumar50 @duongkame @hemantk-12 @ivandika3 @siddhantsangwan @sumitagrawl @whbing @xBis7 @xichen01 please take a look at your commit(s) |
@adoroszlai Thanks for the work on this. LGTM! |
Thanks @adoroszlai. Can we back port these jiras as well? |
This PR is not a comprehensive list of Jiras to be backported, just an initial batch. I thought one PR per commit would be too much overhead now, as more than a month has passed since the branch was cut. Once this is completed, we can follow-up with another batch. If we catch up, we may start backporting each fix right after it is merged to We don't have a timeline for release yet. The idea is to try to keep |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@adoroszlai Thanks for working on this. LGTM +1 for my patch. |
@adoroszlai Thanks ! LGTM +1 for my patch. |
LGTM +1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adoroszlai Thanks for this, LGTM for my patch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your continued efforts in backporting @adoroszlai. LGTM+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. @adoroszlai thanks for your efforts!
Thanks everyone for the review. FYI, I pushed this via CLI as:
GitHub seems to recognize that as a "merge" of the PR, which is good. |
What changes were proposed in this pull request?
Backport the following fixes from
master
toozone-1.4
for 1.4.1.If approved, I'll push to the
ozone-1.4
branch directly.How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/7657035459