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

rgw/sfs: segfault on 's3tests_boto3.functional.test_s3.test_post_object_anonymous_request' #182

Closed
jecluis opened this issue Oct 26, 2022 · 0 comments · Fixed by aquarist-labs/ceph#60
Assignees
Labels
area/rgw-sfs RGW & SFS related kind/bug Something isn't working
Milestone

Comments

@jecluis
Copy link
Contributor

jecluis commented Oct 26, 2022

Easily reproducible with nosetests -v -s s3tests_boto3.functional.test_s3:test_post_object_anonymous_request.

Version under test: s3gw as of 2022-10-26 18:00 UTC (771bbfc8cee56915e58dd2af86b57ae29da7bc45)

     0> 2022-10-26T18:37:53.979+0000 7f5dbc8376c0  -1 *** Caught signal (Segmentation fault) ** in thread 7f5dbc8376c0 thread_name:radosgw

 ceph version 3gw-20220804-71-g771bbfc8cee (771bbfc8cee56915e58dd2af86b57ae29da7bc45) quincy (dev)
 1: /lib64/libc.so.6(+0x3d910) [0x7f5e29ec9910]
 2: (rgw::sal::SFSAtomicWriter::complete(unsigned long, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::chrono::time_point<ceph::real_clock, std::chrono::duration<unsigned long, std::ratio<1l, 1000000000l> > >*, std::chrono::time_point<ceph::real_clock, std::chrono::duration<unsigned long, std::ratio<1l, 1000000000l> > >, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, ceph::buffer::v15_2_0::list, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, ceph::buffer::v15_2_0::list> > >&, std::chrono::time_point<ceph::real_clock, std::chrono::duration<unsigned long, std::ratio<1l, 1000000000l> > >, char const*, char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const*, rgw_zone_set*, bool*, optional_yield)+0x5bb) [0x7f5e2cbb7d9b]
 3: (RGWPostObj::execute(optional_yield)+0x14a9) [0x7f5e2c6c1c09]
 4: (rgw_process_authenticated(RGWHandler_REST*, RGWOp*&, RGWRequest*, req_state*, optional_yield, rgw::sal::Store*, bool)+0xd0a) [0x7f5e2c23f79a]
 5: (process_request(rgw::sal::Store*, RGWREST*, RGWRequest*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, rgw::auth::StrategyRegistry const&, RGWRestfulIO*, OpsLogSink*, optional_yield, rgw::dmclock::Scheduler*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::chrono::duration<unsigned long, std::ratio<1l, 1000000000l> >*, std::shared_ptr<RateLimiter>, int*, rgw::lua::Background*)+0x2414) [0x7f5e2c242554]
 6: /lib64/libradosgw.so.2(+0x8fe28c) [0x7f5e2c19828c]
 7: /lib64/libradosgw.so.2(+0x8fef37) [0x7f5e2c198f37]
 8: make_fcontext()
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
@jecluis jecluis added kind/bug Something isn't working area/rgw-sfs RGW & SFS related labels Oct 26, 2022
@jecluis jecluis added this to S3GW Oct 26, 2022
@jecluis jecluis moved this to Backlog in S3GW Oct 26, 2022
@jecluis jecluis changed the title rgw/sfs: segfault on 's3tests_boto3.functional.test_s3.test_post_object_?' rgw/sfs: segfault on 's3tests_boto3.functional.test_s3.test_post_object_anonymous_request' Oct 26, 2022
@0xavi0 0xavi0 self-assigned this Oct 28, 2022
Repository owner moved this from Backlog to Done ✅ in S3GW Oct 31, 2022
m-ildefons pushed a commit to m-ildefons/s3gw that referenced this issue Feb 6, 2023
Added a script able to update the s3gw's deployment in Kubernetes
@jhmarina jhmarina added this to the v0.8.0 milestone Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rgw-sfs RGW & SFS related kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants