Project

General

Profile

Bug #57272

OSD=3 MON=3 RGW=1 ../src/vstart.sh command does not work!

Added by Vikhyat Umrao 6 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Source:
Tags:
low-hanging-fruit
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

[root@478abe7a82be build]# OSD=3 MON=3 RGW=1 ../src/vstart.sh
rm -f core* 
hostname container
ip 10.0.2.100
port 40908
/home/vikhyat/cephssdbuild/ceph/build/bin/ceph-mon -i a -c /home/vikhyat/cephssdbuild/ceph/build/ceph.conf 
2022-08-23T22:51:50.051+0000 7f9d535a0900 -1 monitor data directory at '/var/lib/ceph/mon/ceph-a' does not exist: have you run 'mkfs'?

History

#1 Updated by Vikhyat Umrao 6 months ago

- The following command fixes it:

OSD=3 MON=3 RGW=1 ../src/vstart.sh --debug --new -x --localhost --bluestore

- So looks like the key here is with first-time deployment after the fresh build directory we have to have this `--new` flag in the command like.

Looks like we need to update this doc - https://docs.ceph.com/en/quincy/dev/dev_cluster_deployement/#environment-variables

#2 Updated by Vikhyat Umrao 6 months ago

Once you have run it the first time with `--new` then the follow-up runs with stop.sh then vstart.sh does not need `--new`.

#3 Updated by Vikhyat Umrao 6 months ago

Laura and I had a discussion and we figured from the document - https://docs.ceph.com/en/quincy/dev/dev_cluster_deployement/#options

-n, --new
Create a new cluster.

-N, --not-new
Reuse existing cluster config (default).

The default is `--not-new` and if you run it for the first time you need to use `--new`. I think we should change our default to `--new` because most of the time we use a new cluster in vstart, thoughts?

#4 Updated by Laura Flores 6 months ago

  • Tags set to low-hanging-fruit

Also available in: Atom PDF