Actions
Bug #21071
closedqa: test_misc creates metadata pool with dummy object resulting in WRN: POOL_APP_NOT_ENABLED
% Done:
0%
Source:
Q/A
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
fs
Component(FS):
qa-suite
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2017-08-23 02:19:50.363035 mon.a mon.0 172.21.15.141:6789/0 296 : cluster [WRN] Health check failed: application not enabled on 1 pool(s) (POOL_APP_NOT_ENABLED)
From: /ceph/teuthology-archive/pdonnell-2017-08-23_01:47:26-fs-wip-pdonnell-testing-20170822b-distro-basic-smithi/1551815/remote/smithi141/log/ceph.log.gz
Relevant part of test: https://github.com/ceph/ceph/blob/2476469074c1d8647270d23a6c5345bb44c1f460/qa/tasks/cephfs/test_misc.py#L57-L63
Setting the metadata on the pool might not be what we want because the intent of the test is to prevent creating a file system on a pool with objects. If "fs new" fails because the metadata is set on the pool, then we are no longer exercising that failure.
Updated by Patrick Donnelly over 6 years ago
- Assignee set to Douglas Fuller
Doug, please take this one.
Updated by Douglas Fuller over 6 years ago
I think we should just whitelist this, then. It's an intentionally pathological case, and this error should not be triggered by anything else in that test.
Updated by Douglas Fuller over 6 years ago
- Status changed from New to Fix Under Review
Updated by Patrick Donnelly over 6 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 6 years ago
- Copied to Backport #21449: luminous: qa: test_misc creates metadata pool with dummy object resulting in WRN: POOL_APP_NOT_ENABLED added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions