Known issues¶

[35146] [Queens, Pike] The novav21 state fails to update aggregates¶

^{Fixed in 2019.2.10}

While creating an aggregate, the novav21.aggregate_present state outputs IndexError: tuple index out of range. Although an aggregate is created, it is ignored by the Nova state and is never updated.

Identify whether your deployment is affected by the issue:

• New deployments without aggregates are not affected.
• New deployments with defined aggregates are affected and fail to create aggregates. No workaround is currently available for this use case.
• Existing deployments with aggregates fail to update aggregates. The workaround is to create and update aggregates manually using Nova CLI. For details, see OpenStack documentation.

[35330] Salesforce-related services unavailability¶

^{Fixed in 2019.2.10}

The following Salesforce-related services may be unavailable due to inability to authenticate to Salesforce:

• Salesforce notifier for both encrypted and non-encrypted pillar
• Salesforce reporter (Gainsight) for an encrypted pillar

Workaround:

1. Open your Git project repository with the Reclass model on the cluster level.

2. In classes/cluster/<cluster_name>/stacklight/client.yml, add the following pillar to the parameters section:

   parameters:
     docker:
       client:
         stack:
           monitoring:
             service:
               sf_notifier:
                 ~environment:
                   SF_NOTIFIER_WORKERS: ${_param:sf_notifier_workers}
                   SF_NOTIFIER_BUFFER_SIZE: ${_param:sf_notifier_buffer_size}
                   SF_NOTIFIER_APP_PORT: ${prometheus:sf_notifier:uwsgi:bind_port}
                   SF_NOTIFIER_ALERT_ID_HASH_FUNC: ${_param:sf_notifier_alert_id_hash_func}
                   SFDC_AUTH_URL: "${_param:sf_notifier_sfdc_auth_url}"
                   SFDC_USERNAME: "${_param:sf_notifier_sfdc_username}"
                   SFDC_PASSWORD: "${_param:sf_notifier_sfdc_password}"
                   SFDC_ORGANIZATION_ID: "${_param:sf_notifier_sfdc_organization_id}"
                   SFDC_ENVIRONMENT_ID: "${_param:sf_notifier_sfdc_environment_id}"
                   SFDC_SANDBOX_ENABLED: "${_param:sf_notifier_sfdc_sandbox_enabled}"
               gainsight:
                 ~environment:
                   CLUSTER_ID: "${_param:gainsight_cluster_id}"
                   PROMETHEUS_URL: "${_param:gainsight_prometheus_url}"
                   CONFIG_PATH: "${_param:gainsight_config_path}"
                   SFDC_AUTH_URL: "${_param:gainsight_sfdc_auth_url}"
                   SFDC_USERNAME: "${_param:gainsight_sfdc_username}"
                   SFDC_PASSWORD: "${_param:gainsight_sfdc_password}"
                   SFDC_ORGANIZATION_ID: "${_param:gainsight_sfdc_organization_id}"
                   SFDC_ENVIRONMENT_ID: "${_param:gainsight_sfdc_environment_id}"
                   SFDC_SANDBOX_ENABLED: "${_param:gainsight_sfdc_sandbox_enabled}"
   

3. Log in to the Salt Master node.

4. Verify that the changes render properly:

   salt 'mon*' state.sls docker.client test=True
   

5. Apply the changes:

   salt 'mon*' state.sls docker.client