Skip to content

Commit

Permalink
Merge pull request #51 from SUSE-Enceladus/supportconfiginfo
Browse files Browse the repository at this point in the history
Provide additional around the base product in support config
  • Loading branch information
guangyee authored Mar 28, 2024
2 parents 7f0ba01 + 6e6acc7 commit c848b6c
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 0 deletions.
7 changes: 7 additions & 0 deletions content/rancher-prime/aws/contents.lr
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
9 changes: 9 additions & 0 deletions content/rancher-prime/azure/contents.lr
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit c848b6c

Please sign in to comment.