backstage: Sonarqube Backstage Integration Issue : Getting 404 Error

πŸ“œ Description

I have deployed a backstage application in on premise kubernetes cluster. It is up and running successfully. While I tried to Integrate backstage with our sonarqube instance getting 404 Error

App-config configuration in backstage :

sonarqube:
  baseUrl: http://sonarqube.********************.com
  apiKey: 42*************************************cef

Catalog.yaml :

apiVersion: backstage.io/v1alpha1`
kind: Component
metadata:
  annotations:
    sonarqube.org/project-key: 'sonarqube.************.com/Central-idp

Central-idp is the project key i got it from the administration tab in Sonarqube UI

Followed this particular document for backend and frontend sonarqube plugin installation : https://github.com/backstage/backstage/blob/master/plugins/sonarqube-backend/README.md https://github.com/backstage/backstage/blob/master/plugins/sonarqube/README.md

πŸ‘ Expected behavior

The Sonarqube plugin needs to show data from sonarqube instance

sonar-card

πŸ‘Ž Actual Behavior with Screenshots

image

Error message from log :

{"level":"info","message":"::ffff:10.233.76.29 - - [23/Aug/2023:06:19:44 +0000] \"GET /api/sonarqube/instanceUrl?instanceKey=sonarqube.**********.com HTTP/1.1\" 404 - \"-\" \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36\"","service":"backstage","type":"incomingRequest"}

πŸ‘Ÿ Reproduction steps

  • Build the backstage application with sonarqube plugin

  • Using the catalog.yaml registered the component

  • After successfully registering the component scroll to the Code Quality

  • Similar error will be there image

πŸ“ƒ Provide the context for the Bug.

No response

πŸ–₯️ Your Environment

$ yarn backstage-cli info yarn run v1.22.19 OS: Windows_NT 10.0.19045 - win32/x64 node: v16.20.1 yarn: 1.22.19 cli: 0.22.10 (installed) backstage: 1.17.0

Dependencies: @backstage/app-defaults 1.4.2 @backstage/backend-app-api 0.4.3, 0.5.0, 0.5.1 @backstage/backend-common 0.18.5, 0.19.2, 0.19.3 @backstage/backend-dev-utils 0.1.1 @backstage/backend-openapi-utils 0.0.3 @backstage/backend-plugin-api 0.5.2, 0.6.0, 0.6.1 @backstage/backend-tasks 0.5.2, 0.5.5, 0.5.6 @backstage/catalog-client 1.4.1, 1.4.3 @backstage/catalog-model 1.4.1, 1.3.0 @backstage/cli-common 0.1.12 @backstage/cli-node 0.1.3 @backstage/cli 0.22.10 @backstage/config-loader 1.3.0, 1.4.0 @backstage/config 1.0.8, 1.0.7 @backstage/core-app-api 1.8.0, 1.9.1 @backstage/core-components 0.12.5, 0.13.4 @backstage/core-plugin-api 1.5.3, 1.5.1 @backstage/errors 1.1.5, 1.2.1 @backstage/eslint-plugin 0.1.3 @backstage/integration-aws-node 0.1.3, 0.1.5 @backstage/integration-react 1.1.16 @backstage/integration 1.4.5, 1.6.0, 1.6.1 @backstage/plugin-api-docs 0.9.7 @backstage/plugin-app-backend 0.3.48 @backstage/plugin-app-node 0.1.0 @backstage/plugin-auth-backend 0.18.6 @backstage/plugin-auth-node 0.2.14, 0.2.17, 0.2.18 @backstage/plugin-catalog-backend 1.12.0, 1.9.1 @backstage/plugin-catalog-common 1.0.15, 1.0.13 @backstage/plugin-catalog-graph 0.2.33 @backstage/plugin-catalog-import 0.9.11 @backstage/plugin-catalog-node 1.3.6, 1.4.1 @backstage/plugin-catalog-react 1.8.2, 1.8.1 @backstage/plugin-catalog 1.12.1 @backstage/plugin-events-node 0.2.9 @backstage/plugin-github-actions 0.6.2 @backstage/plugin-org 0.6.11 @backstage/plugin-permission-common 0.7.5, 0.7.7 @backstage/plugin-permission-node 0.7.11, 0.7.12, 0.7.8 @backstage/plugin-permission-react 0.4.14 @backstage/plugin-proxy-backend 0.3.0 @backstage/plugin-scaffolder-backend 1.14.0, 1.16.0 @backstage/plugin-scaffolder-common 1.3.0, 1.4.0 @backstage/plugin-scaffolder-node 0.1.3, 0.2.0 @backstage/plugin-scaffolder-react 1.5.2 @backstage/plugin-scaffolder 1.14.2 @backstage/plugin-search-backend-module-catalog 0.1.1, 0.1.4 @backstage/plugin-search-backend-module-pg 0.5.9 @backstage/plugin-search-backend-module-techdocs 0.1.4 @backstage/plugin-search-backend-node 1.2.1, 1.2.4 @backstage/plugin-search-backend 1.4.0 @backstage/plugin-search-common 1.2.3, 1.2.5 @backstage/plugin-search-react 1.6.4 @backstage/plugin-search 1.3.4 @backstage/plugin-sonarqube-backend 0.2.3 @backstage/plugin-sonarqube-react 0.1.7 @backstage/plugin-sonarqube 0.7.3 @backstage/plugin-tech-radar 0.6.7 @backstage/plugin-techdocs-backend 1.6.5 @backstage/plugin-techdocs-module-addons-contrib 1.0.16 @backstage/plugin-techdocs-node 1.7.4 @backstage/plugin-techdocs-react 1.1.9 @backstage/plugin-techdocs 1.6.6 @backstage/plugin-user-settings 0.7.6 @backstage/release-manifests 0.0.9 @backstage/test-utils 1.4.2 @backstage/theme 0.2.19, 0.4.1 @backstage/types 1.0.2, 1.1.0 @backstage/version-bridge 1.0.4 Done in 1.70s.

πŸ‘€ Have you spent some time to check if this bug has been raised before?

  • I checked and didn’t find similar issue

🏒 Have you read the Code of Conduct?

Are you willing to submit PR?

None

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 25 (12 by maintainers)

Most upvoted comments

Didn’t quite understand, can you give me more context on what you changed?

@vjanz when you issue the SonarQube token, choose the one labeled β€œuser”: image

Can I trouble you to ask how you got the extra debugging information? That’s what I wanted (printing the response from Sonarqube) but didn’t find any easy way to do that and had to park it.

@m0un10 I have mitmproxy enabled on my local env, which shows outbound API requests. I copied the request to postman to get the SQ response.

@backstage/sda-se-reviewers do you have any input here πŸ™