Bug #38927
closedshould print min_mon_release correctly
0%
Description
dzafman-2019-03-20_19:53:02-rados-wip-zafman-testing-distro-basic-smithi/3754307
rados/upgrade/luminous-x-singleton/{0-cluster/{openstack.yaml start.yaml} 1-install/luminous.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-nautilus.yaml 8-workload/{rbd-python.yaml rgw-swift.yaml snaps-many-objects.yaml}
2019-03-21T09:22:09.856 INFO:tasks.ceph.mon.a.smithi060.stderr:2019-03-21 09:22:09.859 7f6f9d881ec0 -1 mon.a@-1(probing) e1 current monmap has min_mon_release 15 (luminous) which is >2 releases older than me 15 (octopus), stopping.
Updated by Kefu Chai about 5 years ago
- Copied from Bug #38845: mon.a@-1(probing) e1 current monmap has min_mon_release 15 (luminous) which is >2 releases older than me 15 (octopus), stopping. added
Updated by Kefu Chai about 5 years ago
- Status changed from New to Pending Backport
Updated by Kefu Chai about 5 years ago
Brad Hubbard wrote:
15 - 15 !> 2 ?https://github.com/ceph/ceph/pull/27107 should fix this.
Updated by Sage Weil about 5 years ago
- Status changed from Pending Backport to Resolved