Project

General

Profile

Bug #51111

Pacific: CEPHADM_STRAY_DAEMON after deploying iSCSI gateway with cephadm due to tcmu-runner

Added by Paul Giralt 13 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/monitoring
Target version:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Deploy iscsi gateways with the command 'ceph orch apply iscsi.yaml' with the following YAML file (hostname / IP / password have been changed for privacy reasons),

service_type: iscsi
service_id: iscsi
placement:
hosts:
- host1.domain.com
- host2.domain.com
- host3.domain.com
- host4.domain.com
spec:
pool: iscsi-config
trusted_ip_list: "10.10.10.10,10.10.10.11,10.10.10.12,10.10.10.10.13,10.10.10.14"
api_user: admin
api_password: password_removed
api_secure: false

All services will work properly, however the cluster health will indicate a warning whenever an image is added to a target - one for each image on each gateway (so total number of warnings will be number of gateways x number of images).

  1. ceph health detail
    HEALTH_WARN 16 stray daemon(s) not managed by cephadm
    [WRN] CEPHADM_STRAY_DAEMON: 16 stray daemon(s) not managed by cephadm
    stray daemon tcmu-runner.host2.domain.com:iscsi-pool-0001/iscsi-p0001-img-01 on host host2.domain.com not managed by cephadm
    stray daemon tcmu-runner.host2.domain.com:iscsi-pool-0002/iscsi-p0002-img-01 on host host2.domain.com not managed by cephadm
    stray daemon tcmu-runner.host2.domain.com:iscsi-pool-0003/iscsi-p0003-img-01 on host host2.domain.com not managed by cephadm
    stray daemon tcmu-runner.host2.domain.com:iscsi-pool-0004/iscsi-p0004-img-01 on host host2.domain.com not managed by cephadm
    stray daemon tcmu-runner.host3.domain.com:iscsi-pool-0001/iscsi-p0001-img-01 on host host3.domain.com not managed by cephadm
    stray daemon tcmu-runner.host3.domain.com:iscsi-pool-0002/iscsi-p0002-img-01 on host host3.domain.com not managed by cephadm
    stray daemon tcmu-runner.host3.domain.com:iscsi-pool-0003/iscsi-p0003-img-01 on host host3.domain.com not managed by cephadm
    stray daemon tcmu-runner.host3.domain.com:iscsi-pool-0004/iscsi-p0004-img-01 on host host3.domain.com not managed by cephadm
    stray daemon tcmu-runner.host4.domain.com:iscsi-pool-0001/iscsi-p0001-img-01 on host host4.domain.com not managed by cephadm
    stray daemon tcmu-runner.host4.domain.com:iscsi-pool-0002/iscsi-p0002-img-01 on host host4.domain.com not managed by cephadm
    stray daemon tcmu-runner.host4.domain.com:iscsi-pool-0003/iscsi-p0003-img-01 on host host4.domain.com not managed by cephadm
    stray daemon tcmu-runner.host4.domain.com:iscsi-pool-0004/iscsi-p0004-img-01 on host host4.domain.com not managed by cephadm
    stray daemon tcmu-runner.host5.domain.com:iscsi-pool-0001/iscsi-p0001-img-01 on host host5.domain.com not managed by cephadm
    stray daemon tcmu-runner.host5.domain.com:iscsi-pool-0002/iscsi-p0002-img-01 on host host5.domain.com not managed by cephadm
    stray daemon tcmu-runner.host5.domain.com:iscsi-pool-0003/iscsi-p0003-img-01 on host host5.domain.com not managed by cephadm
    stray daemon tcmu-runner.host5.domain.com:iscsi-pool-0004/iscsi-p0004-img-01 on host host5.domain.com not managed by cephadm

I've reproduced this twice on fresh Pacific 16.2.4 installations and I suspect it might have something to do with using FQDN.

Also available in: Atom PDF