Project

General

Profile

Actions

Bug #52906

closed

cephadm rm-daemon is not closing any tcp ports that were opened for the daemon during the removal process

Added by Paul Cuzner over 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Category:
orchestrator
Target version:
% Done:

0%

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

Description

Deploying a daemon handles opening a port to make the daemon accessing, but when you remove a daemon the port that it was using is not removed from the firewall configuration and remains open.

Perhaps since the service has the port defined, when the orchestrator invokes the rm-daemon it could pass the port(s) to close as a parameter to the rm-daemon primitive?


Related issues 2 (0 open2 closed)

Copied to Orchestrator - Backport #55962: quincy: cephadm rm-daemon is not closing any tcp ports that were opened for the daemon during the removal processResolvedActions
Copied to Orchestrator - Backport #55963: pacific: cephadm rm-daemon is not closing any tcp ports that were opened for the daemon during the removal processResolvedAdam KingActions
Actions

Also available in: Atom PDF