spring-boot: spring-cloud-bindings download returning 404 when running spring buildpack
I have been getting a 404 this morning when attempting to build my docker container using the Spring Boot Build Pack with the information below. I had a build running last night that successfully resolved the jar, so my guess something must have happened last night to the repo. Please let me know if more information is required to hunt this down, Thanks!
[creator] Paketo Spring Boot Buildpack 5.13.0
[creator] https://github.com/paketo-buildpacks/spring-boot
[creator] Build Configuration:
[creator] $BP_SPRING_CLOUD_BINDINGS_DISABLED false whether to contribute Spring Boot cloud bindings support
[creator] Launch Configuration:
[creator] $BPL_SPRING_CLOUD_BINDINGS_DISABLED false whether to auto-configure Spring Boot environment properties from bindings
[creator] $BPL_SPRING_CLOUD_BINDINGS_ENABLED true Deprecated - whether to auto-configure Spring Boot environment properties from bindings
[creator] Creating slices from layers index
[creator] dependencies (63.9 MB)
[creator] spring-boot-loader (281.8 KB)
[creator] snapshot-dependencies (0.0 B)
[creator] application (217.2 KB)
[creator] Launch Helper: Contributing to layer
[creator] Creating /layers/paketo-buildpacks_spring-boot/helper/exec.d/spring-cloud-bindings
[creator] Spring Cloud Bindings 1.10.0: Contributing to layer
[creator] Downloading from https://repo.spring.io/release/org/springframework/cloud/spring-cloud-bindings/1.10.0/spring-cloud-bindings-1.10.0.jar
[creator] unable to invoke layer creator
[creator] unable to contribute spring-cloud-bindings layer
[creator] unable to get dependency spring-cloud-bindings
[creator] unable to download https://repo.spring.io/release/org/springframework/cloud/spring-cloud-bindings/1.10.0/spring-cloud-bindings-1.10.0.jar
[creator] could not download https://repo.spring.io/release/org/springframework/cloud/spring-cloud-bindings/1.10.0/spring-cloud-bindings-1.10.0.jar: 404
[creator] ERROR: failed to build: exit status 1
Expected Behavior
Spring cloud binding should not return a 404
Current Behavior
It appears that the buildpack cant find the bindings jar
Steps to Reproduce
- Run
./gradlew bootBuildImageon a spring boot project - Observe failure when trying to resolve the spring-cloud-bindings jar
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 25 (8 by maintainers)
Yes, it should be resolved now, just got an update from the vendor & it’s working for me.
@TomBeckett This is what I can share, and all I know honestly.
The Spring Infra team put in a request to renew the certificate on our instance, which includes a redeploy. This should be a non-event, however, while doing this the vendor did something which caused traffic to repo.spring.io to go to repo.pivotal.io. This had happened before & we explicitly put notes in the service request to the vendor to try to prevent this from happening, but despite reminding the vendor it still happened.
We’ve had an open issue to publish Spring Cloud Bindings to Maven Central, and given what has happened today, we’ll bump up the priority on that. When done, we won’t need to worry about this going forward.
Please standby. I’m seeing reports of a problem with Artifactory/repo.spring.io. I will update this thread when I have more info.
Update on the problem. JFrog was doing a cert rotation and incorrectly redirected traffic to the wrong place. They are aware of the specific problem & we are awaiting a fix. Hopefully, it won’t be long now. Thanks for everyone’s patience.
The issue is back. I am getting 404 for the below link. https://repo.spring.io/release/org/springframework/cloud/spring-cloud-bindings/1.10.0/spring-cloud-bindings-1.10.0.jar
Any permanent solution for this?
This addition to
build.gradleworked for me:There’s a ticket open with the vendor, so it’s being worked on.
You can tell the buildpack to not install it by setting
BP_SPRING_CLOUD_BINDINGS_DISABLED=truewhen you build. That will remove the dependency though, so if you need the bindings support in your app it won’t be there.The other option is to use a dependency mapping. You’ll need a copy of the JAR file to do this though, since it’s not available at the published link.
Instruction here: https://paketo.io/docs/howto/configuration/#dependency-mappings
Now working fine…
@kshkrao3’s solution works for spring-boot 2.7.1 and maven builds.
Looks like the issue has been resolved (for all who subscribed)
I’ll share whatever info I have. The service behind repo.spring.io is a managed service from JFrog, so I only know what they share with us about the incident.
@dmikusa-pivotal Will there be a post mortem?
Not asking to be a bad guy. Just curious to understand the background for what occurred for our own post mortem.