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.

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

luminous: RGWCrashError: RGW will crash if a putting lc config request does not include an ID tag in the request xml #18765

Merged
merged 3 commits into from
Jan 19, 2018

Conversation

smithfarm
Copy link
Contributor

@smithfarm smithfarm commented Nov 6, 2017

According to AWS S3, this header must be used
as a message integrity check to verify that
the request body was not corrupted in transit.

Content-MD5 is the base64-encoded 128-bit MD5
digest of the data

Signed-off-by: Enming Zhang <enming.zhang@umcloud.com>
(cherry picked from commit 9c0abe6)
When a putting lc config request does not include an ID tag in lc
configuration xml, RGW should generate a random ID for the lc
configuration.

At present RGW will crash when generate a random ID for
lc configuration.

Fixes: http://tracker.ceph.com/issues/21980

Signed-off-by: Enming Zhang <enming.zhang@umcloud.com>
(cherry picked from commit 3d2f63d)
@smithfarm smithfarm self-assigned this Nov 6, 2017
@smithfarm smithfarm added this to the luminous milestone Nov 6, 2017
@theanalyst
Copy link
Member

The crash itself will not manifest in Luminous yet, as far as the random changes also are not backported to Luminous, but shouldn't hurt backporting this patch if we have a clean rgw run

When generating random bucket name and object name during
loadgen processing, RGW will crash. The reason is calling
"gen_rand_alphanumeric" with "cct = NULL".

Fixes: http://tracker.ceph.com/issues/22006

Signed-off-by: Enming Zhang <enming.zhang@umcloud.com>
(cherry picked from commit 7d02178)
@smithfarm
Copy link
Contributor Author

@theanalyst I cherry-picked #18536 into this PR - is that what you're referring to?

@smithfarm
Copy link
Contributor Author

smithfarm commented Nov 6, 2017

@theanalyst Nevermind, now I see it's #17972 and that itself depends on other major changes, so I'm beginning to doubt whether it will ever be backported?

@theanalyst
Copy link
Member

@smithfarm yeah, having said that this patch by itself isn't harmful, only that the crash itself wouldn't occur until the random changes, if we see clean rgw runs shouldn't hurt to have this in.

@ZVampirEM77
Copy link
Contributor

@smithfarm @theanalyst Thank you~

@ZVampirEM77
Copy link
Contributor

Jenkins, retest this please.

@yuriw
Copy link
Contributor

yuriw commented Jan 18, 2018

@yuriw
Copy link
Contributor

yuriw commented Jan 19, 2018

@smithfarm @theanalyst @cbodley ready for merge

@cbodley cbodley merged commit c143de4 into ceph:luminous Jan 19, 2018
@smithfarm smithfarm deleted the wip-22024-luminous branch January 20, 2018 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants