10 Jul
2020
10 Jul
'20
1:41 a.m.
Hello. I'm trying to upgrade to ceph 15.2.4 from 15.2.3. The upgrade is
almost finished, but it has entered in a service start/stop loop. I'm using
a container deployment over Debian 10 with 4 nodes. The problem is with a
service named literally "mds.label:mds". It has the colon character, which
is of special use in docker. This character can't appear in the name of the
container and also breaks the volumen binding syntax.
I have seen in the /var/lib/ceph/UUID/ the files for this service:
root@ceph-admin:/var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca# ls -la
total 48
drwx------ 12 167 167 4096 jul 10 02:54 .
drwxr-x--- 3 ceph ceph 4096 jun 24 16:36 ..
drwx------ 3 nobody nogroup 4096 jun 24 16:37 alertmanager.ceph-admin
drwx------ 3 167 167 4096 jun 24 16:36 crash
drwx------ 2 167 167 4096 jul 10 01:35 crash.ceph-admin
drwx------ 4 998 996 4096 jun 24 16:38 grafana.ceph-admin
drwx------ 2 167 167 4096 jul 10 02:55
mds.label:mds.ceph-admin.rwmtkr
drwx------ 2 167 167 4096 jul 10 01:33 mgr.ceph-admin.doljkl
drwx------ 3 167 167 4096 jul 10 01:34 mon.ceph-admin
drwx------ 2 nobody nogroup 4096 jun 24 16:38 node-exporter.ceph-admin
drwx------ 4 nobody nogroup 4096 jun 24 16:38 prometheus.ceph-admin
drwx------ 4 root root 4096 jul 3 02:43 removed
root@ceph-admin:/var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca/mds.label:mds.ceph-admin.rwmtkr#
ls -la
total 32
drwx------ 2 167 167 4096 jul 10 02:55 .
drwx------ 12 167 167 4096 jul 10 02:54 ..
-rw------- 1 167 167 295 jul 10 02:55 config
-rw------- 1 167 167 152 jul 10 02:55 keyring
-rw------- 1 167 167 38 jul 10 02:55 unit.configured
-rw------- 1 167 167 48 jul 10 02:54 unit.created
-rw------- 1 root root 24 jul 10 02:55 unit.image
-rw------- 1 root root 0 jul 10 02:55 unit.poststop
-rw------- 1 root root 981 jul 10 02:55 unit.run
root@ceph-admin:/var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca/mds.label:mds.ceph-admin.rwmtkr#
cat unit.run
/usr/bin/install -d -m0770 -o 167 -g 167
/var/run/ceph/0ce93550-b628-11ea-9484-f6dc192416ca
/usr/bin/docker run --rm --net=host --ipc=host --name
ceph-0ce93550-b628-11ea-9484-f6dc192416ca-mds.label:mds.ceph-admin.rwmtkr
-e CONTAINER_IMAGE=docker.io/ceph/ceph:v15 -e NODE_NAME=ceph-admin -v
/var/ru
n/ceph/0ce93550-b628-11ea-9484-f6dc192416ca:/var/run/ceph:z -v
/var/log/ceph/0ce93550-b628-11ea-9484-f6dc192416ca:/var/log/ceph:z -v
/var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca/crash:/var/lib/ceph/c
rash:z -v
/var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca/mds.label:mds.ceph-admin.rwmtkr:/var/lib/ceph/mds/ceph-label:mds.ceph-admin.rwmtkr:z
-v /var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca/mds.l
abel:mds.ceph-admin.rwmtkr/config:/etc/ceph/ceph.conf:z --entrypoint
/usr/bin/ceph-mds docker.io/ceph/ceph:v15 -n
mds.label:mds.ceph-admin.rwmtkr -f --setuser ceph --setgroup ceph
--default-log-to-file=fal
se --default-log-to-stderr=true --default-log-stderr-prefix="debug "
If I try to manually run the docker command, this is the error:
docker: Error response from daemon: Invalid container name
(ceph-0ce93550-b628-11ea-9484-f6dc192416ca-mds.label:mds.ceph-admin.rwmtkr),
only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed.
If I try with a different container name, then the volume binding error
rises:
docker: Error response from daemon: invalid volume specification:
'/var/lib/ceph/0ce93550-b628-11ea-9484-f6dc192416ca/mds.label:mds.ceph-admin.rwmtkr:/var/lib/ceph/mds/ceph-label:mds.ceph-admin.rwmtkr:z'.
This mds is not needed and I would be happy simply removing it, but I don't
know how to do it. The documentation says how to do it for "normal"
services, but my installation is a container deployment. I have tried to
remove the directory and restart the upgrading process but then the
directory with this service appears again.
Please, how can I remove or rename this service so I can complete the
upgrading?
Also, I think it's a bug to allow docker-forbidden characters in the
service names when using container deployment and it should be checked.
Thank you very much.
--
*Mario J. Barchéin Molina*
*Departamento de I+D+i*
mario(a)intelligenia.com
Madrid: +34 911 86 35 46
US: +1 (918) 856 - 3838
Granada: +34 958 07 70 70
――
intelligenia · Intelligent Engineering · Web & APP & Intranet
www.intelligenia.com · @intelligenia <http://twitter.com/intelligenia> ·
fb.com/intelligenia · blog.intelligenia.com
Madrid · C/ de la Alameda 22, 28014, Madrid, Spain
<https://maps.google.com/?q=C/+de+la+Alameda+22,+28014,+Madrid,+Spain&entry=gmail&source=g>
Miami · 2153 Coral Way #400, Miami, FL, US, 33145
<https://www.google.es/maps/place/2153+Coral+Way+%23400,+Miami,+FL+33145/@25.7508071,-80.2315787,17z/data=!3m1!4b1!4m5!3m4!1s0x88d9b653aaafc4b5:0x6d8501a7341ef2fc!8m2!3d25.7508023!4d-80.22939>
Granada · C/ Luis Amador nº 24, 18014, Granada, Spain
<https://www.google.es/maps/place/intelligenia/@37.1947393,-3.6170297,17z/data=!3m1!4b1!4m5!3m4!1s0xd71fcfb965048e9:0x6849e1627f5b17fd!8m2!3d37.194735!4d-3.614841>
*PROTECCIÓN DE DATOS*: le informamos que los datos personales y dirección
de correo electrónico, recabados del propio interesado, serán tratados bajo
la responsabilidad de Intelligenia Soluciones Informáticas, S.L. para el
envío de comunicaciones sobre nuestros servicios y se conservarán mientras
exista un interés mutuo para ello. Los datos no serán comunicados a
terceros, salvo obligación legal. Le informamos que puede ejercer los
derechos de acceso, rectificación, portabilidad y supresión de sus datos y
los de limitación y oposición a su tratamiento dirigiéndose a C/ Luis
Amador (Centro de negocios Cámara) 24 , 18014 Granada. Si considera que el
tratamiento no se ajusta a la normativa vigente, podrá presentar una
reclamación ante la autoridad de control en aepd.es.
En cumplimiento de lo previsto en el artículo 21 de la Ley 34/2002 de
Servicios de la Sociedad de la Información y Comercio Electrónico (LSSICE),
si usted no desea recibir más información sobre nuestros servicios, puede
darse de baja enviando un correo electrónico a info(a)intelligenia.com indicando
en el *Asunto *"*BAJA*" o "*NO ENVIAR*".