From 6e6acc724815685b352f3b130e52a08b0ffe05ef Mon Sep 17 00:00:00 2001 From: Meera Belur Date: Mon, 18 Mar 2024 09:21:59 -0700 Subject: [PATCH] Provide additional around the base product in support config --- content/rancher-prime/aws/contents.lr | 7 +++++++ content/rancher-prime/azure/contents.lr | 9 +++++++++ 2 files changed, 16 insertions(+) diff --git a/content/rancher-prime/aws/contents.lr b/content/rancher-prime/aws/contents.lr index ca04c9d..7891666 100644 --- a/content/rancher-prime/aws/contents.lr +++ b/content/rancher-prime/aws/contents.lr @@ -276,6 +276,13 @@ kubectl get cm -n cattle-csp-billing-adapter-system csp-config -o yaml if a configuration is not listed, you can debug into the root cause by checking the pod status and log (Refer Jobs and Pods section). +### Support configuration does not display the rancher product information or the upgraded product version + +Once the rancher-cloud components are installed, the support configuration takes approximately an hour to show the +product information. In an upgrade scenario, the support config might still have base_product field reference to +the pre-upgrade version but after the next usage update (approximately in an hour), the support config should reflect the +upgraded version. + ## Known Issues 1. Uninstalling Rancher Prime: diff --git a/content/rancher-prime/azure/contents.lr b/content/rancher-prime/azure/contents.lr index 7a6364e..03550cb 100644 --- a/content/rancher-prime/azure/contents.lr +++ b/content/rancher-prime/azure/contents.lr @@ -279,6 +279,15 @@ Solution: AKS cluster already has the extension. Uninstall the extension as it suggested in the Error by deleting the resource via the kubectl command. or Uninstall the extension in Azure Console and re-deploy with the same cluster. + +### Support configuration does not display the rancher product information or the upgraded product version + +Once the rancher-cloud components are installed, the support configuration takes approximately an hour to show the +product information. In an upgrade scenario, the support config might still have base_product field reference to +the pre-upgrade version but after the next usage update (approximately in an hour), the support config should reflect the +upgraded version. + + ## Known Issues 1. When migrating Rancher to a different AKS cluster by following the steps