Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Newer documentation is now live.You are currently reading an older version.

Switch to latest✕

Enable debug logs for the Tungsten Fabric services

To enable debug logging for the Tungsten Fabric (TF) services:

API v2 Available since MOSK 24.1

1. Open the TF custom resource for modification:

   kubectl -n tf edit tfoperators.tf.mirantis.com openstack-tf
   

2. Set the logLevel variable to the SYS_DEBUG value for the required TF service. For example, for the config-api service:

   spec:
     services:
       config:
         tf:
           logging:
              api:
                logLevel: SYS_DEBUG
   

API v1alpha1 Removed in MOSK 25.1

1. Open the TF custom resource for modification:

   kubectl -n tf edit tfoperators.operator.tf.mirantis.com openstack-tf
   

2. Set the LOG_LEVEL variable to the SYS_DEBUG value for the required TF service. For example, for the config-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.