release 27.0.0 job checksum error

[ywei2017]

I got the following error during the deployment. I had the following observations with 2 deployments using the release.

• In one deployment (we do not use concourse_dashboards) there is no error or complaint
• But we got the following error in another deployment (we DO use concourse_dashboards).

So I guess the jobs signature is only checked if that job is used for the deployment.

I was able to do a workaround by downloading the source, and create a release myself.

Can you issue a release to correct the issue? I don't mind to contribute if somebody kindly share directions of "how".

Thanks

  releases:
  - name: prometheus
-   version: 26.6.0
+   version: 27.0.0
Task 3850533

Task 3850533 | 00:36:16 | Preparing deployment: Preparing deployment (00:00:00)
Task 3850533 | 00:36:16 | Preparing deployment: Rendering templates (00:00:01)
                        L Error: Unable to render instance groups for deployment. Errors are:
  Expected stream to have digest 'sha256:5d7f029721d72c33266d41d1269731451bf47f13e4aadd823a3b0ebc534222b7' but was 'sha256:ad770c23f358feb88ee8b3ae322ad3525dfc4667f7103e8e409ca567c6e2b241'
Task 3850533 | 00:36:17 | Error: Unable to render instance groups for deployment. Errors are:
  Expected stream to have digest 'sha256:5d7f029721d72c33266d41d1269731451bf47f13e4aadd823a3b0ebc534222b7' but was 'sha256:ad770c23f358feb88ee8b3ae322ad3525dfc4667f7103e8e409ca567c6e2b241'

Task 3850533 Started  Tue Mar  1 00:36:16 UTC 2022
Task 3850533 Finished Tue Mar  1 00:36:17 UTC 2022
Task 3850533 Duration 00:00:01
Task 3850533 error

[benjaminguttmann-avtq]

We are using the release in multiple environment not having that issue, can you maybe share the releases section of your manifest ?

[ywei2017]

@benjaminguttmann-avtq I think the issue is with this specific release since we don't have the same issue with earlier releases. We also deploy it in multiple environments without issues. But the problematic environment is the only one using the concourse_dashboard release, which has issue. I think the checksum is wrong.

[benjaminguttmann-avtq]

Hi @ywei2017 ,

thank you for that hint. So I checked the sha for the version that is currently in use on your side and saw that that release has been created using sha1 instead of sha256 (like all the others before and afterwards). So I would expect that you have issues with that sha in all versions beside the one you are using.

Can you let me know the BOSH director version + BOSH CLI version you are using?

[benjaminguttmann-avtq]

Closing due to inactivity; Fell free to re-open if issue persists;