eclipse-tractusx / eclipse-tractusx/sig-release
bpdm-gate failing while upgrade
- Dominant language
- Go
- Stars
- 12
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
## Description
2024-07-16 07:17:31.469 ERROR [System ] [No Request] [main ] o.s.boot.SpringApplication : Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'goldenRecordTaskConfiguration' defined in URL [jar:nested:/usr/local/lib/bpdm/app.jar/!BOOT-INF/classes/!/org/eclipse/tractusx/bpdm/gate/config/GoldenRecordTaskConfiguration.class]: Unsatisfied dependency expressed through constructor parameter 2: Error creating bean with name 'goldenRecordTaskService' defined in URL [jar:nested:/usr/local/lib/bpdm/app.jar/!BOOT-INF/classes/!/org/eclipse/tractusx/bpdm/gate/service/GoldenRecordTaskService.class]: Unsatisfied dependency expressed through constructor parameter 5: Error creating bean with name 'orchestratorClient' defined in class path resource [org/eclipse/tractusx/bpdm/gate/config/OrchestratorClientConfiguration.class]: Unsatisfied dependency expressed through method 'orchestratorClient' parameter 1: Error creating bean with name 'bpdmWebClientProvider' defined in class path resource [org/eclipse/tractusx/bpdm/common/config/BpdmWebClientProviderConfig.class]: Unsatisfied dependency expressed through method 'bpdmWebClientProvider' parameter 0: Error creating bean with name 'clientRegistrationRepository' defined in class path resource [org/eclipse/tractusx/bpdm/common/config/BpdmOAuth2ClientRegistrationConfig.class]: Failed to instantiate [org.springframework.security.oauth2.client.registration.InMemoryClientRegistrationRepository]: Factory method 'clientRegistrationRepository' threw exception with message: Provider ID must be specified for client registration 'pool-client'
## Expected behavior
it should update
## How to reproduce
Contributor guide
Research direction
Start by examining BpdmOAuth2ClientRegistrationConfig and the client registration for `pool-client`, then reproduce the upgrade startup failure using the logged exception. Trace why the provider ID is missing and verify that the application starts successfully and updates as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100