Project

General

Profile

Bug #48930

when removing the iscsi service, the gateway config object remains

Added by Paul Cuzner about 1 month ago. Updated 9 days ago.

Status:
New
Priority:
Normal
Category:
cephadm/services
Target version:
% Done:

0%

Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

When the first rbd-target-api daemon starts it creates a gateway.conf object. When the iscsi service is removed via "orch rm", this object remains in the pool and in theory could be used erroneously by a subsequent iscsi deployment.


Related issues

Blocked by Orchestrator - Bug #48597: pybind/mgr/cephadm: mds_join_fs not cleaned up Pending Backport

History

#1 Updated by Sebastian Wagner about 1 month ago

  • Category changed from orchestrator to cephadm/services

#3 Updated by Sebastian Wagner 23 days ago

  • Blocked by Bug #48597: pybind/mgr/cephadm: mds_join_fs not cleaned up added

#4 Updated by Sebastian Wagner 9 days ago

who's creating the gateway.conf object? I can't find it in https://github.com/ceph/ceph/blob/master/src/pybind/mgr/cephadm/services/iscsi.py

#5 Updated by Juan Miguel Olmo Martínez 9 days ago

Sebastian Wagner wrote:

who's creating the gateway.conf object? I can't find it in https://github.com/ceph/ceph/blob/master/src/pybind/mgr/cephadm/services/iscsi.py

you can get it directly from CLI with:
  1. rados -p iscsi ls

#6 Updated by Sebastian Wagner 9 days ago

but who is creating the object in the first place?

Also available in: Atom PDF