Chart never sets EXECUTION_ENGINE for ui_react, so a deployed React UI submits runs to the wrong engine #150

Activity

1. mosoriob

   added

   wayfinder:taskWayfinder ticket: manual work that unblocks a decisionWayfinder ticket: manual work that unblocks a decision

   on Aug 30, 2026
2. mosoriob

   added a parent issue on Aug 30, 2026

   • Wayfinder: close out the SUBSIDE UI SOW — TACC signs off on ui-react at mint.tacc.utexas.edu #79
3. mosoriob

   marked this as blocking on Aug 30, 2026

   • Flip mint.tacc.utexas.edu to ui-react #77
4. mosoriob

   self-assigned this

   on Aug 30, 2026
5. mosoriob commented on Aug 30, 2026

   

   mosoriob

   on Aug 30, 2026

   ContributorAuthor

   More actions

   Fixed, and verified as a browser sees it — both UIs now say tapis. The chart derives
   EXECUTION_ENGINE from components.ensemble_manager.config.execution_engine.type, the same value
   ui-config.yaml gives the legacy UI, so the two UIs cannot disagree about the deployment they are
   in. components.ui_react.config.execution_engine overrides it. Chart in
   mintproject/mint#108, version 9.0.0-beta.6.
   No client change: ui-react already honours the value (#88).

   The measurement was re-checked before the fix and held. mint-ui-config-map carried
   REACT_APP_EXECUTION_ENGINE = "tapis"; mint-ui-react-config-map carried no such key.

   Verified live, not by template. That distinction is the point of this ticket, so the check was
   run the way the ticket says it must be: helm upgrade on the dev cluster with its own values, then
   the served file over the ingress —

   $ curl http://mint.local/env-config.js
   "EXECUTION_ENGINE": "tapis",
   $ curl http://legacy.mint.local/config.js
   window.REACT_APP_EXECUTION_ENGINE = "tapis";
   

   Six controls on the rendered template: chart defaults give localex; an explicit
   execution_engine overrides the Ensemble Manager; an explicit data_catalog_api beats external
   CKAN; with CKAN disabled and data_catalog enabled the component ingress is used; a missing
   Ensemble Manager config omits the key rather than failing the render; an empty client_id still
   fails.

   The "also worth knowing" was real, and it is fixed in the same PR. DATA_CATALOG_API was
   derived from components.data_catalog only — which a deployment using external_services.ckan
   does not enable — so the key was omitted and the app fell back to a compiled-in default. It now
   reads external_services.ckan.url, as ui-config.yaml does. The dev cluster's map went from no
   key to https://ckan.tacc.utexas.edu, derived rather than lucky. That was one of the three chart
   cleanups #75 landed on #77; the other two landed with it — MODEL_CATALOG_API is no longer
   emitted and its override key is gone, and the client_id text no longer claims the React UI needs
   a client distinct from the legacy UI's. #77 has no chart cleanups left.

   Two things outlive this ticket.

   1. helm upgrade does not restart pods when only a config map changes #123 does not bite ui_react. Its deployment carries a checksum/config pod-template
      annotation, so a config-map-only change does roll the pod — the upgrade above rolled it, and
      that is how the new file reached the browser. mint-ui and mint-ensemble-manager carry no such
      annotation. Landed on #123.
   2. 9.0.0-beta.6 is not installable from the chart repo. beta.4 and beta.5 were version
      bumps in Chart.yaml that were never packaged, so releases/ and index.yaml still stop at
      9.0.0-beta.3. The dev cluster runs the chart from a local path. Flip mint.tacc.utexas.edu to ui-react #77 must either package a
      release or deploy from a checkout — landed there.

   The dev cluster is on the branch chart, release mint revision 68. Rollback is
   helm rollback mint 67.
6. mosoriob

   closed this as completedon Aug 30, 2026
7. mosoriob

   added a commit that references this issue on Aug 30, 2026

   fix(ui-react): derive EXECUTION_ENGINE from the Ensemble Manager (#108)

   ...

   69495af