Partial deployment (-m) does not update MTA version metadata and leaves stale build records causing 500 errors
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Java
- Sterne
- 65
- Forks
- 41
- Ø Merge
- 1 T. 12 Min.
- Gemergte PRs (30 T.)
- 7
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus cloudfoundry/multiapps-controller
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 53/100
cloudfoundry/multiapps-controller#1945 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
cloudfoundry/multiapps-controller#1944 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[FEATURE REQUEST] Add additional authentication methods for async file upload from secured remoteOffenenhancement
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
cloudfoundry/multiapps-controller#1594 · 4 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
cloudfoundry/multiapps-controller#1409 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 42/100
cloudfoundry/multiapps-controller#1365 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in cloudfoundry/multiapps-controller
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
apache/skywalking#14239 ·
Maintainer antworten meist innerhalb von 1 Tag
-
account bug exercise lecture modeling programming
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 64/100
Maintainer antworten meist innerhalb von 1 Tag
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Evtl. vergeben @dbusche hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
h2database/h2database#4580 ·
Maintainer antworten meist innerhalb von 1 Tag
-
vips-drift
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
Stirling-Tools/JPDFium#300 ·
Maintainer antworten meist innerhalb von 1 Tag
-
hermes-queue
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Maintainer antworten meist innerhalb von 1 Tag