Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!
Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.
Enable debug logs for the Tungsten Fabric services¶
To enable debug logging for the Tungsten Fabric (TF) services:
Open the TF custom resource for modification:
kubectl -n tf edit tfoperators.tf.mirantis.com openstack-tf
Set the
logLevel
variable to theSYS_DEBUG
value for the required TF service. For example, for theconfig-api
service:spec: services: config: tf: logging: api: logLevel: SYS_DEBUG
Open the TF custom resource for modification:
kubectl -n tf edit tfoperators.operator.tf.mirantis.com openstack-tf
Set the
LOG_LEVEL
variable to theSYS_DEBUG
value for the required TF service. For example, for theconfig-api
service:spec: controllers: tf-config: api: containers: - name: api env: - name: LOG_LEVEL value: SYS_DEBUG
Warning
After the TF custom resource modification, the pods
related to the affected services will be restarted. This rule does not
apply to the tf-vrouter-agent-<XXXXX>
pods as their update strategy
differs. Therefore, if you enable the debug logging for the services in
a tf-vrouter-agent-<XXXXX>
pod, restart this pod manually after you
modify the custom resource.