Partial deployment (-m) does not update MTA version metadata and leaves stale build records causing 500 errors
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
Direção de pesquisa
The issue identifies getBuildsForApplication as a likely source of stale build records, but does not name its file or a test. Start by locating that method and tracing partial deployment cleanup and MTA version metadata updates; the payload provides no test command. Done means partial deploys report the deployed module version and subsequent full or partial deploys avoid the reported 500 error.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
When using cf deploy -m -r for partial deployment, two problems occur:
A. MTA version not updated after partial deploy
After deploying a single module via -m, running cf mta does not correctly reflect the version of the partially deployed module. The MTA metadata appears unchanged, making it impossible to determine which version of a given module is actually running in the space.
Expected behavior: cf mta should update the MTA version on partial deploy, or expose per-module version information so operators can audit the deployed state.
Actual behavior: MTA version metadata remains as it was after the last full deploy, regardless of subsequent partial deploys.
Related: SAP-samples/cf-mta-examples#84 — open since Jan 2024.
B. Stale build records cause 500 on subsequent deploys
After a partial deployment, subsequent cf deploy operations (both full and partial) can fail with:
500 Internal Server Error: UnknownError(10001)
The root cause appears to be getBuildsForApplication finding lingering build records from the prior partial deploy that were not cleaned up.
Expected behavior: The controller should clean up or gracefully handle stale build records from prior partial deployments.
Actual behavior: Deployment fails with 500 until stale records are manually resolved.
Documented in: sap-tutorials/tutorials-ims – MTA deployment troubleshooting
Your environment
MultiApps Controller version — SAP BTP managed (latest)
MultiApps CF CLI Plugin version — latest
which CF vendor is used — SAP BTP Cloud Foundry
which backing services are used — hana / hdi-shared (HDI container)
Steps to reproduce
1. Initial full deploy (succeeds)
mbt build
cf deploy myapp.mtar -f
2. Partial deploy of db module only (succeeds)
cf deploy myapp.mtar -m db-deployer -r hdi-container
3. Check MTA version — still shows version from step 1
cf mta myapp
4. Attempt another full deploy — may fail with 500 due to stale build state
cf deploy myapp.mtar -f
Error: 500 Internal Server Error: UnknownError(10001)
MTA descriptor: standard CAP/HANA Cloud project with hdb module type and com.sap.xs.hdi-container resource.
Additional information
CLI plugin CHANGELOG references prior selective deploy fixes: "Fix selective deployment on Windows", "Fix selective deployment with modules sharing the same binary" — CHANGELOG.md. This suggests selective deployment has been a known problem area.
Using SAP BTP managed controller, so no access to controller application logs. Operation logs via cf dmol available on request if maintainers need them for a specific reproduction.
- Linguagem predominante
- Java
- Estrelas
- 65
- Forks
- 41
- Merge médio
- 1d 12min
- PRs com merge (30d)
- 7
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de cloudfoundry/multiapps-controller
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 53/100
cloudfoundry/multiapps-controller#1945 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 45/100
cloudfoundry/multiapps-controller#1944 ·
Mantenedores costumam responder em até 1 dia
-
[FEATURE REQUEST] Add additional authentication methods for async file upload from secured remoteAbertaenhancement
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
cloudfoundry/multiapps-controller#1594 · 4 comentários ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
cloudfoundry/multiapps-controller#1409 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 42/100
cloudfoundry/multiapps-controller#1365 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de cloudfoundry/multiapps-controller
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
apache/skywalking#14239 ·
Mantenedores costumam responder em até 1 dia
-
account bug exercise lecture modeling programming
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
Mantenedores costumam responder em até 1 dia
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Talvez já em andamento @dbusche assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
h2database/h2database#4580 ·
Mantenedores costumam responder em até 1 dia
-
vips-drift
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
Stirling-Tools/JPDFium#300 ·
Mantenedores costumam responder em até 1 dia
-
hermes-queue
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Mantenedores costumam responder em até 1 dia