Critical Guidance Regarding Clarity v16.0.0.1 and v16.0.1

On April 18th, Broadcom released Clarity v16.0.1.1, which corrected the issues noted below. This article will be retained for archival purposes. Rego customers are welcome to submit requests to upgrade Clarity to v16.0.1.1.

Broadcom has identified a critical blocker defect in Clarity v16.0.0.1, described here: https://knowledge.broadcom.com/external/article?articleId=234750

Broadcom has identified a critical blocker defect in Clarity v16.0.1, described here: https://knowledge.broadcom.com/external/article/235142

There is currently no available patch for these defect, both of these critical defects are expected to be addressed in v16.0.1.1, estimated for April release. This Rego Knowledgebase article will be updated when a patch is available for Rego to schedule deployments. Rego is urging customers to exercise caution when requesting an upgrade to v16.0.0.1 and v16.0.1 until a fully QA’d fix is released by Broadcom. The impact of this defect is substantial, as such, Rego provides specific guidance below.

Once a fully-tested permanent solution is achieved, Rego will proactively notify all affected customers. The current fix from Broadcom is expected in v16.0.1.1 which is expected in April 2022.

Guidance from Rego:

1. Rego has strong confidence of highly performing and stable upgrades to Clarity v15.9.3.3. Customers with restricted windows of time to execute an annual upgrade should consider the proven stability of v15.9.3.3, which may be scheduled with Rego anytime convenient.

2. Although it is not recommended, Rego will schedule non-production upgrades to v16.0.0.1 or v16.0.1 with certain expectations of customers.

   1. No tickets may be submitted to Rego regarding Data Warehouse issues or failures in the non-production environment.

   2. Customers must remove all Parameterized Lookups in an environment before Rego will schedule the upgrade. Customers must provide confirmation that lookups have been removed and will not be added back until a permanent fix is deployed.

3. Under very specific circumstances, Rego will schedule production upgrades to v16.0.0.1 or v16.0.1 with certain expectations of customers.

   1. No tickets may be submitted to Rego regarding Data Warehouse issues or failures in the Production environment. P1 issues will not be accepted by Rego. Customers must assume support for any issues that may be encountered in the Data Warehouse.

   2. Customers must remove all Parameterized Lookups in the production environment before Rego will schedule the upgrade. Customers must provide confirmation that lookups have been removed and will not be added back until a permanent fix is deployed.

   3. No production rollbacks are possible if the production upgrade is not acceptable. Once a production environment is upgraded to v16.0.0.1 or v16.0.1, it cannot be rolled back.

   4. Customers must explicitly confirm they accept the terms of this guidance within a support ticket.