Skip to content

6.6.0 Yellowbrick Release Notes

Date: September 19, 2023

Yellowbrick Version 6.6.0 Release Notes

Yellowbrick Data Warehouse Version 6.6.0 is supported for AWS and Microsoft Azure cloud deployments. This version of Yellowbrick Data Warehouse is installed on Cloud Data Warehouse Manager (CDWM) Version 3.66

Cloud ProviderCDWM VersionYellowbrick Data Warehouse VersionKubernetes Version
AWS3.66.0-731.6a00da136.6.0-5214.f016cdb1EKS 1.24
Azure3.66.0-731.6a00da136.6.0-5214.f016cdb1AKS 1.25

Upgrade Requirements

Read the following information before beginning an upgrade to Version 6.6.0.

  1. Contact Customer Support to review the process and schedule the upgrade.
  2. Only upgrades from Version 6.5.x to 6.6.0 are supported. These upgrades apply to both CDWM and data warehouse instances.
  3. YBD Instances and cluster must be running and not suspended before being upgraded.
  4. Version 6.6.0 requires EKS 1.24. Please use the EKS migration tool to upgrade to version 1.24 before upgrading to Version 6.6.0.
  5. Only use offline install with a new install.

Note: Before attempting to upgrade data warehouse instances, make sure they are running. You cannot upgrade suspended instances.

AWS Upgrades from Version 6.5.x

Version 6.6.0 requires EKS 1.24. Please use the EKS migration tool to upgrade to version 1.24 before upgrading to Version 6.6.0.

  1. Push the 3.65.13-637.1d0e1c0b  installer to the AWS ECR and check that the required files are in the S3 bucket.

  2. In AWS CloudFormation > Stacks, search for your root stack for your env; click update and then

    Select Replace current template and update the Amazon S3 URL to point to the location of the yb-cdw.template.yaml file for the 3.65.13-637.1d0e1c0b build.

  3. Update and verify information on stack details page.

  4. In the Yellowbrick software section, the URL for the chart repository and CloudFormation S3 key prefix must be updated. In 3.65 the URL includes a version in the path.

    On the final review page, confirm that the only changes/overrides will be to the CFS3KeyPrefix and ChartRepository values. All other key values remain the same.

  5. Submit to start the deployment process and once it completes verify that the CDWM is reporting the correct version of 3.65.13-637.1d0e1c0b.

  6. Repeat steps from 1-5 to upgrade to CDWM version 3.66.0-731.6a00da13.

  7. Once the upgrade to 3.66.0- is completed; verify that the YBD instances were all resumed and each upgraded to 6.6.0-5214.f016cdb1.

Azure Upgrades from Version 6.5.x

You have to upgrade from 6.5.x to 6.6.0, upgrade from prior versions are not allowed.

You can upgrade directly from 6.5.x to Version 6.6.0. Note that Version 6.6.0 requires AKS version 1.25, but this version is supplied as part of the Yellowbrick upgrade.

From az cli; run the following commands or script to push the Azure deployment scripts to target environment. Note the name of the templateSpec used in the script.

NOTE: Please updates variables and settings for your environment including URL to the files

  1. Before beginning the CDWM upgrade, suspend all instances managed by the CDWM.
  2. Push the installer files using below script (this is needed only if the customer needs the additional CVE fixes.)
!/bin/bash

templateSpec=yb-az-install
cdwmVersion=3-65-12-527-06079e02
resourceGroup=<resource_group>
subscription=<az_subscription>
region=<region>

curl https://<container_registry_path>/3-65-12-527-06079e02/installer-scripts/formDefinition.json -o formDefinition.json;
curl https://<container_registry_path>/3-65-12-527-06079e02/installer-scripts/yb-cdw.json -o yb-cdw.json;

az ts create --name "${templateSpec}" --version "${cdwmVersion}" --resource-group "${resourceGroup}" --subscription "${subscription}" --location "${region}" --temp
  1. From Azure portal, select the template spec used; click Deploy button and select the subscription and resource group for your environment. Enter in the exact name of the Cluster name (Kubernetes service) for your environment.
  2. Follow prompts for steps, ensuring fields are updated according to your environment including Azure AD tenant ID and Azure AD admin group IDs for your environment. Update allowed CIDRs for your environment. Once all the fields are verified; click Create button to start the upgrade process.
  3. Once the upgrade process completes, check that the CDWM is reporting the correct version of  3.66.0-731.6a00da13 and YBD version 6.6.0-5214.f016cdb1.

Offline Installer

This provides an installer that allows customers installing into networks with no public internet access.

Commands

load

This command must first be ran to load all the container images into the local docker registry from the images.tgz file.

./ybdsw load

This should result in all containers in images.tgz to be loaded into local docker registry.

push

This command will push the resources into the specified customer locations ready for install

Options

AWS
-a auto create the s3 bucket
-c aws ecr s3-bucket region
./ybdsw push -a -c aws 123456789.dkr.ecr.us-east-2.amazonaws.com ybd-data us-east-2

Azure
-a auto create the storage account
-c azure acr storage-container region resource-group
./ybdsw push -a -c azure 123456789.azurecr.io ybd-data eastus my-resource-group

Example

The result of this would appear as:

S3 Bucket contents:
2023-08-23 20:26:45 11350 cdw/3-65-12-527-06079e02/functions/LICENSE.txt
2023-08-23 20:26:45 549 cdw/3-65-12-527-06079e02/functions/NOTICE.txt
2023-08-28 17:16:28 503 cdw/3-65-12-527-06079e02/functions/packages/CleanupLambdas/lambda.zip
2023-08-28 17:16:29 1797 cdw/3-65-12-527-06079e02/functions/packages/CleanupLoadBalancers/lambda.zip
2023-08-28 17:16:29 1209 cdw/3-65-12-527-06079e02/functions/packages/CleanupSecurityGroupDependencies/lambda.zip
2023-08-28 17:16:31 17003610 cdw/3-65-12-527-06079e02/functions/packages/awscliLayer/lambda.zip
.
.
.
Repositories:
"repositoryUri": "123456789.dkr.ecr.us-east-2.amazonaws.com/yellowbrick/ybd-worker",
"repositoryUri": "123456789.dkr.ecr.us-east-2.amazonaws.com/grafana/loki",
"repositoryUri": "123456789.dkr.ecr.us-east-2.amazonaws.com/yellowbrick/ybd-mgr",
.
.
.
"repositoryUri": "123456789.dkr.ecr.us-east-2.amazonaws.com/csi-secrets-store/driver",
"repositoryUri": "123456789.dkr.ecr.us-east-2.amazonaws.com/kiwigrid/k8s-sidecar",

Use the http URL for the cdw/3-65-12-527-06079e02/templates/yb-cdw.template.yaml in the Cloud Formation install

Changes in Behavior and Compatibility

ybtools Compatibility

Yellowbrick recommends that you always upgrade ybtools to match the Yellowbrick server version you are running (for example, upgrade to ybtools Version 6.6 before connecting to a Version 6.6 database). In most cases, using an older version of ybtools, such as 6.5, to connect to a Version 6.6 database will work but is not recommended.

Using Version 6.6 of ybtools with an older server version (such as Version 6.5) may result in error messages for some commands or a mismatch between client and server features.

The Version 5.2 and 5.4 ybtools packages install two sets of backup and restore tools: legacy tools (BAR1) and current versions of the tools (BAR2). The legacy tools are deprecated and have been removed from the 6.x releases.

BAR2 and Replication Compatibility

Important: The source and target systems used for database backup and restore (BAR2) and database replication must be compatible. To support full functionality, the source and target systems should both be running a 6.6 version of Yellowbrick software.

Nonetheless, you can back up and restore a database, or replicate a database, from:

  • 5.2.x to 6.5.x
  • 5.4.3 or later to 6.5.x
  • 6.1.x to 6.5.x
  • 6.2.x to 6.5.x
  • 6.3.x to 6.5.x
  • 6.4.x to 6.5.x

Although you can start replication from a 5.2, 5.4, 6.1, 6.2... or 6.5 source to a 6.6 target, and you can fail over to the 6.6 target, you cannot fail back to the 5.2, 5.4, 6.1, 6.2, 6.3,6.4 or 6.5 source. In general, you cannot fail back to a Yellowbrick version with a catalog version that is earlier than the current catalog version.

What is new is Version 6.6.0

Version 6.6.0 provides critical bug fixes for issues reported by customers. See Issues Fixed in Version 6.6.0.

  1. AWS installation with service role as EKS manager (non-admin) is now available.
  2. Only use offline install with a new install, please see upgrade requirements for upgrading existing installations.

Known issues in 6.6.0

You may encounter the following issues in Version 6.6.0. Contact Customer Support for additional information.

ReleaseIssueDescription
6.6.033739When using the Cloudformation installer to create a VPC network, the option CreateNATGateways must be set to “true” under all network conditions.
6.6.033799Azure installation on full private/ UDR fails AKS 1.25 creation due to node count limit. Cluster's upper limit node count is 452 which exceeds the limit for Kubenet 400. If Autoscaler is enabled, the max-count from each node pool is counted towards this total.

Issues Fixed in Version 6.6.0

The following issues are fixed in Version 6.6.0.

ReleaseIssueDescription
6.6.022160Upgraded server side log4j.jar file to version 2.17.1
6.6.033592Upgrade without administrative privileges

CVE addressed in Version 6.6.0

The following CVEs were addressed Yellowbrick Version 6.6.0:

CVESummary
CVE-2023-2650Possible DoS translating ASN.1 object identifiers
CVE-2023-2975AES-SIV implementation ignores empty associated data entries
CVE-2023-3446Excessive time spent checking DH keys and parameters
CVE-2023-3817Excessive time spent checking DH q parameter value
CVE-2023-35945Envoy vulnerable to HTTP/2 memory leak in nghttp2 codec
CVE-2022-29458ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.
CVE-2022-3715A flaw was found in the bash package, where a heap-buffer overflow can occur in valid parameter_transform. This issue may lead to memory problems.
CVE-2022-41409Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
CVE-2022-4899A vulnerability was found in zstd v1.4.10, where an attacker can supply empty string as an argument to the command line tool to cause buffer overrun.
CVE-2016-1585In all versions of AppArmor mount rules are accidentally widened when compiled.
CVE-2016-2568pkexec, when used with --user nonpriv, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
CVE-2023-34969D-Bus before 1.15.6 sometimes allows unprivileged users to crash dbus-daemon.