Ujjwaljain16 commented on issue #44220:
URL: https://github.com/apache/superset/issues/44220#issuecomment-5664955155

   I dug into this and was able to reproduce the failure against the exact 
`6.1.0` release commit.
   
   The root cause is a release/workflow revision mismatch:
   
   * PR #44100 added the `superset` Dockerfile stage and made the `superset` 
preset responsible for the plain image tags (`latest`, `<version>`, per-SHA).
   * The scheduled refresh workflow, however, checks out the **release tag 
being refreshed** (`6.1.0` → `c83fb2bb...`) while using the current `master` 
version of the workflow tooling / `supersetbot`.
   * The `6.1.0` Dockerfile predates #44100 and has no `superset` stage; its 
production image is built from the `lean` stage.
   * Consequently, current `supersetbot` resolves the `superset` preset to 
`--target superset`, which fails immediately with `target stage "superset" 
could not be found`.
   
   I reproduced the exact failure locally with:
   
   ```bash
   docker buildx build \
     --target superset \
     --build-arg PY_VER=3.10-slim-bookworm \
     --platform linux/amd64 .
   ```
   
   against the `6.1.0` Dockerfile.
   
   The fix I’m testing is to make the scheduled refresh check the target 
resolved by `supersetbot` against the Dockerfile actually checked out for the 
release. For the known pre-#44100 case, the `superset` preset falls back to the 
existing `lean` stage while preserving the plain-tag semantics; unexpected 
target/stage mismatches still fail loudly.
   
   This is broader than `6.1.0`: older published releases also predate the 
`superset` stage, so a release-specific hardcode would not be sufficient.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to