VSTS Publish Quality Gate Result task get notfound error

Template for a good bug report, formatted with Markdown:
we are use VSTS(AzureDevops) agnent version is “2.148.2”, Publish Quality Gate Result task is use 4.* version in Vsts
image

The issue is started in 13 Aug 2019, every build will get the below error:

##[debug]pollingTimeoutSec=300

##[debug]Build.BuildNumber=1.2.0.49

##[debug]Agent.TempDirectory=D:\VSTSAgents\Agent1\_work\_temp

##[debug]defaultRoot: 'D:\VSTSAgents\Agent1\_work\_temp'

##[debug]findOptions.allowBrokenSymbolicLinks: 'false'

##[debug]findOptions.followSpecifiedSymbolicLink: 'true'

##[debug]findOptions.followSymbolicLinks: 'true'

##[debug]matchOptions.debug: 'false'

##[debug]matchOptions.nobrace: 'true'

##[debug]matchOptions.noglobstar: 'false'

##[debug]matchOptions.dot: 'true'

##[debug]matchOptions.noext: 'false'

##[debug]matchOptions.nocase: 'true'

##[debug]matchOptions.nonull: 'false'

##[debug]matchOptions.matchBase: 'false'

##[debug]matchOptions.nocomment: 'false'

##[debug]matchOptions.nonegate: 'false'

##[debug]matchOptions.flipNegate: 'false'

##[debug]pattern: 'sonar\1.2.0.49\**\report-task.txt'

##[debug]findPath: 'D:\VSTSAgents\Agent1\_work\_temp\sonar\1.2.0.49'

##[debug]statOnly: 'false'

##[debug]findPath: 'D:\VSTSAgents\Agent1\_work\_temp\sonar\1.2.0.49'

##[debug]findOptions.allowBrokenSymbolicLinks: 'false'

##[debug]findOptions.followSpecifiedSymbolicLink: 'true'

##[debug]findOptions.followSymbolicLinks: 'true'

##[debug]0 results

##[debug]found 0 paths

##[debug]applying include pattern

##[debug]adjustedPattern: 'D:\VSTSAgents\Agent1\_work\_temp\sonar\1.2.0.49\**\report-task.txt'

##[debug]0 matches

##[debug]0 final results

##[debug][SQ] Searching for sonar\1.2.0.49\**\report-task.txt - found 0 file(s)

##[debug]Number of analyses in this build: 0

##[debug]Overall Quality Gate status: ok

##[debug]System.TeamFoundationCollectionUri=https://crmhsbc.visualstudio.com/

##[debug]System.TeamProjectId=08cfbe1e-ccda-41f6-99bb-8368987af946

##[debug]Build.BuildId=14572

##[debug][{"op":"add","path":"/sonarglobalqualitygate","value":"ok"}]

SYSTEMVSSCONNECTION exists true

##[debug]SYSTEMVSSCONNECTION exists true

##[debug]build.artifactStagingDirectory=D:\VSTSAgents\Agent1\_work\8\a

##[debug][SQ] Summary saved at: D:\VSTSAgents\Agent1\_work\8\a\.sqAnalysis\SonarQubeBuildSummary.md

##[debug][SQ] Uploading build summary from D:\VSTSAgents\Agent1\_work\8\a\.sqAnalysis\SonarQubeBuildSummary.md

##[debug]Processed: ##vso[task.addattachment type=Distributedtask.Core.Summary;name=SonarQube Analysis Report;]D:\VSTSAgents\Agent1\_work\8\a\.sqAnalysis\SonarQubeBuildSummary.md

##[error]Failed to update build properties, error was : {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo","hostname":"*******.visualstudio.com","host":"*******.visualstudio.com","port":443}

##[debug]Processed: ##vso[task.issue type=error;]Failed to update build properties, error was : {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo","hostname":"*******.visualstudio.com","host":"*******.visualstudio.com","port":443}

we are use the same link when we access VSTS, And we had check with MS support that there is not change in this link.

May I know which API this task will call and which link was use in this.

Thanks

hostname”:“ ourorgname.visualstudio.com",“host”:"ourorgname.visualstudio.com”,“port”:443}

HI all, is any one have the same problem ? any one can help on this?

Hi,

We currently have an issue with SonarQube instance < 7.2 following the change of the report-task.txt file location.

We are working on it and a fix should be available soon.

Sorry for the inconvenience.

Mickaël

Thanks let us know that, Mickael.

Hello Muckael

May I know any update on this? any plan to push the release for this?

Actually all our task and every build will get the same error now.

Please let me know if any update about this.

Thanks

May I know aAy one can help on this? Thanks

Hello Team, May I know any update for this, any plan to fix this issue?

Hi,

Version 4.8.0 of the SonarQube extension has been released yesterday, it should normally fix your issue.

Please let me know.

Thanks.

Thanks your response, I will check and back soon