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.

StackLight known issues¶

This section lists the StackLight known issues with workarounds for the Mirantis OpenStack for Kubernetes release 21.4.

[17045] fluentd-notifications does not track RabbitMQ credentials updates
[17573] OpenStack notifications missing in Elasticsearch and Kibana

[17045] fluentd-notifications does not track RabbitMQ credentials updates¶

^{Fixed in MOS 21.5}

The fluentd-notifications pod fails to track the RabbitMQ credentials updates in the Secret object. In this case, the fluentd-notifications pods in the StackLight namespace are being restarted too often with the following error message present in logs:

Authentication with RabbitMQ failed. Please check your connection settings.

Workaround:

Delete the affected fluentd-notifications pod. For example:

kubectl delete pod fluentd-notifications-cfcf77f9-h2wd7 -n stacklight

Once done, a new pod will be created automatically and will read the valid credentials from the Secret object.

If the issue still persists, apply the workaround described in [17573] OpenStack notifications missing in Elasticsearch and Kibana.

[17573] OpenStack notifications missing in Elasticsearch and Kibana¶

^{Fixed in MOS 21.5}

OpenStack notifications may be missing in Elasticsearch and the Kibana notification-* index may be empty. In this case, error messages similar to the following one may be present in the fluentd-notifications logs:

kubectl logs -l release=fluentd-notifications -n stacklight
2021-09-08 11:02:49 +0000 [error]: #0 unexpected error error_class=Bunny::
# AuthenticationFailureError error="Authentication with RabbitMQ failed.
# Please check your connection settings. Username: stacklight5BwVEEwd4s,
# vhost: openstack, password length: 10"

Workaround:

Apply the workaround described in [17045] fluentd-notifications does not track RabbitMQ credentials updates. If the issue still persists, perform the following steps:

On the affected managed cluster, obtain the proper user name and password from the rabbitmq-creds Secret in the openstack-lma-shared namespace (strip b' prefix and ' suffix):

kubectl get secret -n openstack-lma-shared rabbitmq-creds -o jsonpath="{.data.password}" | base64 -d
b'81g4B0wvEJ0rB2LWdAQcMBANf3E2DaEa'
kubectl get secret -n openstack-lma-shared rabbitmq-creds -o jsonpath="{.data.username}" | base64 -d
b'stacklightN7MAuk4LVd'

On the related management cluster, modify the affected Cluster object by specifying the obtained user name and password.

kubectl edit cluster <affectedManagedClusterName> -n <affectedManagedClusterProjectName>

For example:

spec:
  ...
  providerSpec:
    ...
    value:
      ...
      helmReleases:
        ...
        - name: stacklight
          values:
            ...
            openstack:
              rabbitmq:
                credentialsDiscovery:
                  enabled: false
                credentialsConfig:
                  username: stacklightN7MAuk4LVd
                  password: 81g4B0wvEJ0rB2LWdAQcMBANf3E2DaEa