Bug #38328
closed"Caught signal (Aborted) thread_name:radosgw" in ceph dashboard tests Jenkins job
0%
Description
When running the "run-frontend-e2e-tests.sh" [1] script from within Jenkins with the following options: "MGR=2 RGW=1 ../src/vstart.sh -n -d"
Rados Gateway is not running anymore when the actual end-to-end tests are being executed.
I was able to reproduce it with different Jenkins job builds [2] / different PRs that have been tested and were unrelated to any RGW changes.
I attached the full RGW log as well as the ceph.conf.
[1] https://github.com/ceph/ceph/blob/master/src/pybind/mgr/dashboard/run-frontend-e2e-tests.sh
[2] https://jenkins.ceph.com/job/ceph-dashboard-pull-requests/
Files
Updated by Laura Paduano about 5 years ago
Note: The Jenkins job system is based on CentOS 7. I was not able to reproduce it on my local dev environment (Tumbleweed).
Updated by Laura Paduano about 5 years ago
Due to this issue we can't merge https://github.com/ceph/ceph/pull/25451
Updated by Casey Bodley about 5 years ago
- Status changed from New to 12
- Priority changed from Normal to High
Updated by Casey Bodley about 5 years ago
- Status changed from 12 to Fix Under Review
- Pull request ID set to 26998
Updated by Casey Bodley about 5 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to luminous mimic nautilus
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38919: mimic: "Caught signal (Aborted) thread_name:radosgw" in ceph dashboard tests Jenkins job added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38920: luminous: "Caught signal (Aborted) thread_name:radosgw" in ceph dashboard tests Jenkins job added
Updated by Nathan Cutler about 5 years ago
- Copied to Backport #38921: nautilus: "Caught signal (Aborted) thread_name:radosgw" in ceph dashboard tests Jenkins job added
Updated by Nathan Cutler almost 5 years ago
- Status changed from Pending Backport to Resolved