Partial deployment (-m) does not update MTA version metadata and leaves stale build records causing 500 errors

Abierto
#1,943 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
backend, devops

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
65
Forks
41
Merge medio
1 d 12 min
PR fusionados (30 d)
7

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cloudfoundry/multiapps-controller

Todos los issues de cloudfoundry/multiapps-controller

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.