Install plugin via helm chart, curl download error code 23

SonarQube Server / Community Build Plugin Development
1

I tried to deploy sonarqube and install a plugin using helm chart version 10.1.0+628 but it does not successful. The value and configuration in the values.yaml of the chart as:

# List of plugins to install.
# For example:
# plugins:
#  install:
#    - "https://github.com/AmadeusITGroup/sonar-stash/releases/download/1.3.0/sonar-stash-plugin-1.3.0.jar"
#    - "https://github.com/SonarSource/sonar-ldap/releases/download/2.2-RC3/sonar-ldap-plugin-2.2.0.601.jar"
#
plugins:
  install:
    - "https://github.com/insideapp-oss/sonar-flutter/releases/download/0.4.0/sonar-flutter-plugin-0.4.0.jar"

  # For use behind a corporate proxy when downloading plugins
  # httpProxy: ""
  # httpsProxy: ""
  # noProxy: ""

  # image: curlimages/curl:7.76.1
  # resources: {}

  # .netrc secret file with a key "netrc" to use basic auth while downloading plugins
  # netrcCreds: ""

  # Set to true to not validate the server's certificate to download plugin
  noCheckCertificate: false
  securityContext:
    runAsUser: 1000
    runAsGroup: 1000

The pods describe error of sonarqube pod as:

install-plugins:
    Container ID:  docker://627114dff095c5e1bbec7fb40abd4ee3536c5f44cae3d265596c0c86d5ed484c
    Image:         curlimages/curl:7.76.1
    Image ID:      docker-pullable://curlimages/curl@sha256:fa32ef426092b88ee0b569d6f81ab0203ee527692a94ec2e6ceb2fd0b6b2755c
    Port:          <none>
    Host Port:     <none>
    Command:
      sh
      -e
      /tmp/scripts/install_plugins.sh
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    23
      Started:      Tue, 25 Jul 2023 13:05:30 +0700
      Finished:     Tue, 25 Jul 2023 13:05:31 +0700
    Ready:          False
    Restart Count:  1

I checked the error code 23 of curl that about curl can’t write the download file.

I also tried with enable persistence as below but the result still error code 23.

persistence:
  enabled: true
  ## Set annotations on pvc
  annotations: {}

  ## Specify an existing volume claim instead of creating a new one.
  ## When using this option all following options like storageClass, accessMode and size are ignored.
  # existingClaim:

  ## If defined, storageClassName: <storageClass>
  ## If set to "-", storageClassName: "", which disables dynamic provisioning
  ## If undefined (the default) or set to null, no storageClassName spec is
  ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
  ##   GKE, AWS & OpenStack)
  ##
  storageClass: "standard"
  accessMode: ReadWriteOnce
  size: 5Gi
  uid: 1000

Does anyone got the same issue when tried to install plugin with helm chart? Do you have any advise for this issue?

Update: problem by minikube issue, re-create minikube problem solved!

Thanks!

1 Like
2

Thanks for the update!

3

Hey, Im facing the same issue on my kubernetes cluster. Any suggestion ?

4

If @quinguyen’s solution (recreating the minikube) doesn’t help, feel free to raise a new thread with full details instead of resurrecting this old one