Hi Arun,
Not too sure about the port thing (I'll look into that when I have a
chance) but it does look like a bug with bootstrapping with the
'--no-minimize-config' flag. I opened a tracker issue for it
https://tracker.ceph.com/issues/54141.
Thanks for helping find this bug,
- Adam King
On
Hi Adam,
Found the culprit here. It was the flag '--no-minimize-config' like
you said.
When I bootstrapped the cluster without the flag -'-no-minimize-config',
all daemons were created using the image specified through the '--image'
flag.
So, when the '--no--minimize-config' was provided,
Hi Arun,
A couple questions. First, from where did you pull your cephadm binary from
(the python file used for bootstrap). I know we swapped everything over to
quay quite a bit ago (
https://github.com/ceph/ceph/commit/b291aa47825ece9fcfe9831546e1d8355b3202e4)
so I want to make sure if I try to
Hi Adam,
Thanks for the update. In that case this looks like a bug like you
mentioned.
Here are the contents of the config file used for bootstrapping.
[global]
osd pool default size = 2
osd pool default min size = 1
osd pool default pg num = 8
osd pool default pgp num = 8
osd recovery
>
> But, even if I gave --image flag with bootstrap the daemons created by mgr
> module are using the daemon-base image, in our case its '
> docker.io/ceph/daemon-base:latest-pacific-devel'.
> Which I guess is because, mgr daemon takes into consideration the
> configuration parameter
Hi Adam,
Thanks for reviewing the long output.
Like you said, it makes total sense now since the first mon and mgr are
created by cephamd bootstrap and the rest of the dameons by the mgr module.
But, even if I gave --image flag with bootstrap the daemons created by mgr
module are using the
Hi Arun,
As you pointed out in your message, those containers whose image name is
using a container digest are the same container as the two using the tag
(you know for sure because the image ids in "ceph orch ps" don't differ for
those daemons). The reason for this difference is that the first
Hi Adam,
Big Thanks for the responses and clarifying the global usage of the --image
parameter. Eventhough, I gave --image during bootstrap only mgr & mon
daemons on the bootstrap host are getting created with that image and the
rest of the demons are created on the image daemon-base as I
Hi Adam,
Thanks for replying.
I have tried the "ceph orch upgrade start " as a workaround and
it works as expected. All the daemons are recreated with the stable version
of the image. However, it still requires an initial fetch of the
latest-pacific-devel image and creation of daemons with that.
Hi Arun,
Not sure exactly how things got this way. When you provide "--image
" when bootstrapping that should set the image to be used for
all ceph containers. I've never seen just the bootstrap mgr/mon get a
totally different image. Would be interesting to maybe see the full
bootstrap output
10 matches
Mail list logo
