Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REGRESSION]: PackerBuild task fails with: unknown configuration key: "client_jwt" #19904

Closed
4 of 7 tasks
tomasr opened this issue May 23, 2024 · 4 comments
Closed
4 of 7 tasks
Labels
Area: Release Area:RM RM task team bug regression This used to work, but a change in the service/tasks broke it. triage

Comments

@tomasr
Copy link

tomasr commented May 23, 2024

New issue checklist

Task name

PackerBuild@1

Breaking task version

1.239.1

Last working task version

1.238.1

Regression Description

We have existing pipelines that used to work and now fail with unknown configuration key: "client_jwt".

I am almost sure this broke due to this change to add support for Workload Identity Federation: 8947d18

I am not sure if the task version is completely broken, or it's just that it now only works if the azure credentials use WIF.

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows Server 2022

Relevant log output

Resolving deploy package path.
Resolved deploy package path: C:\dva\_work\21\b\deploy.
Resolving deploy script path.
Resolved deploy script path: Setup-DriverVM.ps1.
Parsing additional builder parameters json.
Current installed packer version is null.
Either packer is not installed or its version is less than 1.2.4. Version 1.2.4 will be downloaded and installed for running task.
Created staging directory for keeping packer binary and templates: C:\dva\_work\_temp\1716481238825.
Packer installer downloaded successfully at path: C:\dva\_work\_temp\1716481238825\packer.zip.
Packer extracted successfully at path: C:\dva\_work\_temp\1716481238825\packer\packer.exe.
C:\dva\_work\_temp\1716481238825\packer\packer.exe --version
1.2.4

...

Running packer validate command to ensure template is valid
C:\dva\_work\_temp\1716481238825\packer\packer.exe validate -var-file=C:\dva\_work\_temp\1slnxdvoieo.json -var-file=C:\dva\_work\_temp\gixwumfjwme.json C:\dva\_work\_temp\1716481238825\default.managed.windows.template-builderUpdated-fixed.json
Template validation failed. Errors are shown below.

Errors validating build 'azure-arm'. 1 error(s) occurred:

* unknown configuration key: "client_jwt"
##[error]Packer validate command failed. This could happen if task does not support packer version.

Full task logs with system.debug enabled

UNSUCCESSFUL RUN
 [REPLACE THIS WITH YOUR INFORMATION] 
SUCCESSFUL RUN
 [REPLACE THIS WITH YOUR INFORMATION] 

Repro steps

No response

@tomasr tomasr added bug regression This used to work, but a change in the service/tasks broke it. labels May 23, 2024
@ghost
Copy link

ghost commented May 23, 2024

Facing the same issue which has broken down our multiple pipelines, which were running fine before. This is having a major impact on our upcoming releases.

@tomasr
Copy link
Author

tomasr commented May 23, 2024

@KenAdam2024 For now I have just reverted to running the previous release on my pipelines, like this:

  - task: PackerBuild@1.238.1

Maybe useful.

@v-schhabra
Copy link
Contributor

Hi @KenAdam2024 @tomasr
Thanks for reporting the issue. As a temporary fix we reverted the task version from 1.239.1 to 1.238.1
We are just working on the permanent fix. Could you pls check if you can see task version 1.238.1 in your pipelines.
Thank you.

@v-schhabra
Copy link
Contributor

@tomasr Could you please share the failed detail logs of the pipeline by adding variable system.debug to "true"

@v-schhabra v-schhabra added awaiting deployment Related changes are waiting for deployment to be completed Area:RM RM task team labels May 31, 2024
@v-schhabra v-schhabra removed the awaiting deployment Related changes are waiting for deployment to be completed label Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Release Area:RM RM task team bug regression This used to work, but a change in the service/tasks broke it. triage
Projects
None yet
Development

No branches or pull requests

2 participants