topic Re: Update to New Version in Administration and Deployment

Update to New Version

omperez — Fri, 16 May 2025 16:06:21 GMT

I'm trying to update from 2023.10 to 2424.03

When I ran de deployment gives me the message:

Failed to find release '20240504.1714808422601' for the cadence 'lts' and version '2024.03'

Re: Update to New Version

gwootton — Fri, 16 May 2025 17:40:56 GMT

How are you performing the update? Where do you see that message?

Re: Update to New Version

omperez — Fri, 16 May 2025 17:47:01 GMT

I'm using deployment operator. The message is from deployment operator logs.

Re: Update to New Version

gwootton — Fri, 16 May 2025 17:53:54 GMT

The message seems to be saying it can't find that specific release number when checking the repository warehouse. Are you supplying that release when building the deployment custom resource? Are you using an internal repository warehouse?

Re: Update to New Version

omperez — Fri, 16 May 2025 18:09:22 GMT

Yes, it is internal repository. I ran this command to create de deployment:

docker run --rm \
  -v $(pwd):mount-for-working-directory-inside-container \
  sas-orchestration \
  create sas-deployment-cr \
  --deployment-data new-certificates-information \
  --license new-license-information \
  --user-content location-of-deployment-files \
  --cadence-name stable-or-lts \
  --cadence-version new-cadence-version-number \
  --cadence-release new-cadence-release-number-or-double-quotation-marks \
> $deploy-sasdeployment.yaml

from mysas portal I've downloaded the assets with the certificates and license information.

Re: Update to New Version

gwootton — Fri, 16 May 2025 19:16:52 GMT

The Deployment Operator calls ses.sas.download to pull the cadence release file when deploying. If you have modified this to use an internal repository warehouse (not a mirror registry) you would need to update the files in your repository warehouse for the new version you are trying to deploy. These would have been pulled down when you run mirrormgr.