Project

General

Profile

Bug #40647

OP_CREATE issued to nautilus OSD

Added by Sage Weil over 1 year ago. Updated 10 months ago.

Status:
Can't reproduce
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

   -88> 2019-07-02 21:06:37.811 7fa58927a700  0 _dump_transaction transaction dump:
{
    "ops": [
        {
            "op_num": 0,
            "op_name": "unknown",
            "op_code": 7
        }
    ]
}
   -10> 2019-07-02 21:06:37.815 7fa58927a700 -1 /build/ceph-14.2.1-602-g51abe8f/src/os/bluestore/BlueStore.cc: In function 'void BlueStore::_txc_add_transaction(BlueStore::TransContext*, ObjectStore::Transaction*)' thread 7fa58927a700 time 2019-07-02 21:06:37.813371
/build/ceph-14.2.1-602-g51abe8f/src/os/bluestore/BlueStore.cc: 11452: ceph_abort_msg("unexpected error")

 ceph version 14.2.1-602-g51abe8f (51abe8f00e1a8f0b4408d67a6a6c08437c159de9) nautilus (stable)
 1: (ceph::__ceph_abort(char const*, int, char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+0xdf) [0x5638bd042aaa]
 2: (BlueStore::_txc_add_transaction(BlueStore::TransContext*, ObjectStore::Transaction*)+0xc4d) [0x5638bd6406dd]
 3: (BlueStore::queue_transactions(boost::intrusive_ptr<ObjectStore::CollectionImpl>&, std::vector<ObjectStore::Transaction, std::allocator<ObjectStore::Transaction> >&, boost::intrusive_ptr<TrackedOp>, ThreadPool::TPHandle*)+0x5e6) [0x5638bd646956]
 4: (non-virtual thunk to PrimaryLogPG::queue_transactions(std::vector<ObjectStore::Transaction, std::allocator<ObjectStore::Transaction> >&, boost::intrusive_ptr<OpRequest>)+0x54) [0x5638bd391f84]
 5: (ReplicatedBackend::do_repop(boost::intrusive_ptr<OpRequest>)+0xb09) [0x5638bd492409]
 6: (ReplicatedBackend::_handle_message(boost::intrusive_ptr<OpRequest>)+0x1a7) [0x5638bd4a0617]
 7: (PGBackend::handle_message(boost::intrusive_ptr<OpRequest>)+0x97) [0x5638bd3a4f27]
 8: (PrimaryLogPG::do_request(boost::intrusive_ptr<OpRequest>&, ThreadPool::TPHandle&)+0x705) [0x5638bd354095]
 9: (OSD::dequeue_op(boost::intrusive_ptr<PG>, boost::intrusive_ptr<OpRequest>, ThreadPool::TPHandle&)+0x1b3) [0x5638bd178963]
 10: (PGOpItem::run(OSD*, OSDShard*, boost::intrusive_ptr<PG>&, ThreadPool::TPHandle&)+0x62) [0x5638bd42b362]
 11: (OSD::ShardedOpWQ::_process(unsigned int, ceph::heartbeat_handle_d*)+0xbf5) [0x5638bd196745]
 12: (ShardedThreadPool::shardedthreadpool_worker(unsigned int)+0x4ac) [0x5638bd7bfe2c]

/a/sage-2019-07-02_17:58:21-rados-wip-sage-testing-2019-07-02-1056-distro-basic-smithi/4087782

this is an upgrade test,

description: rados/upgrade/nautilus-x-singleton/{0-cluster/{openstack.yaml start.yaml} 1-install/nautilus.yaml 2-partial-upgrade/firsthalf.yaml 3-thrash/default.yaml 4-workload/{rbd-cls.yaml rbd-import-export.yaml readwrite.yaml snaps-few-objects.yaml} 5-workload/{radosbench.yaml rbd_api.yaml} 6-finish-upgrade.yaml 7-octopus.yaml 8-workload/{rbd-python.yaml rgw-swift.yaml snaps-many-objects.yaml} bluestore-bitmap.yaml supported-random-distro$/{ubuntu_latest.yaml} thrashosds-health.yaml}


Related issues

Duplicated by RADOS - Bug #40718: touch in txn on (old) nautilus osd Duplicate 07/10/2019

History

#1 Updated by jianpeng ma over 1 year ago

Is there a method which got peer-osd version? Or is there example we can reference?

#2 Updated by Josh Durgin over 1 year ago

It should be testing for required_osd_release >= ceph_release_t::octopus rather than nautilus, since the op does not exist in nautilus.

#3 Updated by Josh Durgin over 1 year ago

  • Duplicated by Bug #40718: touch in txn on (old) nautilus osd added

#4 Updated by David Zafman over 1 year ago

Also seen today:

dzafman-2019-07-26_13:06:48-rados-wip-zafman-testing-distro-basic-smithi/4154925

#5 Updated by Patrick Donnelly 12 months ago

  • Status changed from 12 to New

#6 Updated by Sage Weil 10 months ago

  • Target version set to v15.0.0

#7 Updated by Sage Weil 10 months ago

  • Status changed from New to Can't reproduce

I think this got fixed.. we haven't seen it in 6 months.

Also available in: Atom PDF