The Nozzle for VMware Tanzu for Microsoft Azure Log Analytics fails with Buildpack version error

Products

• VMware Tanzu Application Service

Issue/Introduction

The below error message appears when Apply Changes to the Nozzle for VMware Tanzu for Microsoft Azure Log Analytics Tile with the deploy-all errand selected is triggered.
This issue appears after the TAS Tile upgrade or update made to the Go Buildpack.


The Apply Changes to the Nozzle for VMware Tanzu for Microsoft Azure Log Analytics fails with the following errors.

**WARNING** buildpack version changed from 1.10.22 to 1.10.23 
...
**ERROR** Unable to determine Go version to install: no match found for 1.21.x in [1.22.7 1.23.1]

 

As the error indicates, the Go buildpack version has changed and app deployment fails because of compatibility issues.

Resolution

Solution 1: Manually Change the Default Go Buildpack Version

1. Download the Compatible Buildpack:
   Obtain the cflinuxfs4 Go Buildpack version 1.10.22 from the Broadcom download portal.

2. Update the Go Buildpack:
   Use the Cloud Foundry CLI to update the buildpack, replacing the default version:

   cf update-buildpack go_buildpack -p ./go_buildpack-cached-cflinuxfs4-v1.10.22.zip -s cflinuxfs4

   Note: Ensure the correct buildpack path and name are specified.

Once completed correctly, the Apply Changes should be successful.

Solution 2: Create a New Buildpack and use os-conf

If modifying the default Go Buildpack is not preferred, create a new buildpack and configure os-conf to reference it during errand execution.

1. Download the Compatible Buildpack:
   Obtain the cflinuxfs4 Go Buildpack version 1.10.22 from the Broadcom download portal.

2. Create the New Buildpack:
   Add the new buildpack using the Cloud Foundry CLI with a unique name:

   cf create-buildpack azure-nozzle ./go_buildpack-cached-cflinuxfs4-v1.10.22.zip 10

   Note: The name azure-nozzle is referenced in the os-conf script. If a different name is used, update the os-conf template accordingly.

3. Verify Buildpack Upload:
   Confirm the buildpack is uploaded and correctly named:

   cf buildpacks

4. Apply the os-conf Configuration:
   Create a YAML file (azure_nozzle.yaml) with the following content:
   
   Note: Replace azure-log-analytics-nozzle-a0acd42e6bcc5c268dc4 with your specific Azure Log Analytics Tile deployment name.

   ---
   releases:
     - name: os-conf
       version: 22.3.1
       url: https://bosh.io/d/github.com/cloudfoundry/os-conf-release?v=22.3.1
       sha1: 9276888fc54d22950045a247d348142757ae9129
   addons:
     - name: azure-log-analytics-nozzle-temp-fix-for-v4.0.8
       include:
         deployments:
           - azure-log-analytics-nozzle-a0acd42e6bcc5c268dc4
       jobs:
         - name: pre-start-script
           release: os-conf
           properties:
             description: |-
               Newer Versions of TAS upgrade Go Buildpack causing App deployment failures.
               A manually added compatible Go Buildpack v1.10.22 named azure-nozzle is added
               in /var/vcap/jobs/deploy-all/bin/run file.
             script: |-
               #!/bin/bash
               sudo sed -i 's/cf push ${APP_NAME}/cf push ${APP_NAME} -b azure-nozzle/g' /var/vcap/jobs/deploy-all/bin/run

5. Apply the Runtime Configuration:
   Run the following command to update the BOSH runtime configuration:

   bosh update-runtime-config azure_nozzle.yaml --name=azure-log-analytics-nozzle-temp-fix-for-v4.0.8

6. Deploy Changes:

   • Perform Apply Changes.

   • Ensure the errand is selected during the process.

   The issue should be resolved if the above steps were followed correctly.

7. Clean Up (Post-Upgrade):
   After upgrading the Tile to a fixed version:

   • List existing runtime configurations:

     bosh configs

   • Delete the specific configuration:

     bosh delete-config --type=runtime --name=azure-log-analytics-nozzle-temp-fix-for-v4.0.8

Solution 3: Upgrade the Azure Log Analytics Nozzle Tile

Upgrade the Nozzle for VMware Tanzu for Microsoft Azure Log Analytics Tile to a version above 4.0.9.

Note: Version 4.0.9 introduces a different issue covered in a different Knowledge Base article.