Project

General

Profile

Actions

Bug #47405

closed

[test] rbd_snaps_ops will fail attempting to create pool

Added by Jason Dillaman over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2020-09-10T23:44:33.590 INFO:tasks.workunit.client.0.smithi051.stderr:pool 'test' does not exist
2020-09-10T23:44:33.599 INFO:tasks.workunit.client.0.smithi051.stdout:[1] ceph osd pool create test 256 256
2020-09-10T23:44:33.870 INFO:tasks.workunit.client.0.smithi051.stderr:Error EPERM: For better initial performance on pools expected to store a large number of objects, consider supplying the expected_num_objects parameter when creating the pool. Pass --yes-i-really-mean-it to ignore it
2020-09-10T23:44:33.871 INFO:tasks.workunit.client.0.smithi051.stdout:[1] unexpected return '1', expected '0'

Related issues 2 (0 open2 closed)

Copied to rbd - Backport #47459: nautilus: [test] rbd_snaps_ops will fail attempting to create poolResolvedNathan CutlerActions
Copied to rbd - Backport #47460: octopus: [test] rbd_snaps_ops will fail attempting to create poolResolvedNathan CutlerActions
Actions #1

Updated by Jason Dillaman over 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 37107
Actions #2

Updated by Jason Dillaman over 3 years ago

  • Backport set to nautilus,octopus
Actions #3

Updated by Mykola Golub over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47459: nautilus: [test] rbd_snaps_ops will fail attempting to create pool added
Actions #5

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47460: octopus: [test] rbd_snaps_ops will fail attempting to create pool added
Actions #6

Updated by Nathan Cutler over 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF