rangareddy commented on issue #16955:
URL: https://github.com/apache/hudi/issues/16955#issuecomment-5408504121

   **Correcting my earlier comment on this issue: it was wrong. This is fixed, 
and I'm closing it.**
   
   My previous note said the linked merged PR was not the fix and that this 
remained open. That reasoning was based on the linked PR carrying a different 
JIRA key, which was the wrong signal here - because the linked PR is what 
*caused* the inconsistency, and the fix was a later, unlinked revert.
   
   **Current state on `master`.** `azure-pipelines-20230430.yml` declares 
exactly one runner image, at the pool level:
   
   ```yaml
   pool:
     vmImage: 'ubuntu-22.04'
   ```
   
   That is the only `vmImage` declaration in the file - there is no per-job 
override, and the string `ubuntu-24` no longer appears anywhere in the 
pipeline. So every Azure CI job runs on the same linux version, which is what 
this ticket asked for.
   
   **How it got here:**
   
   | commit | PR | date | effect |
   | --- | --- | --- | --- |
   | `a8d1aa2c17d5` | #13124 | 2025-04-09 | forced `UT hudi-hadoop-common & 
Hudi Utilities others` to ubuntu-24 - **introduced** the divergence |
   | `bb41db29c1dc` | #13283 | 2025-05-09 | `[MINOR] Reverting ubuntu version 
override` - **removed** it |
   
   PR #13124's own description called the override "a temporary workaround", 
and #13283 duly reverted it a month later. Confirmed `bb41db29c1dc` is an 
ancestor of current `master`.
   
   So the underlying ubuntu-22.04 kernel problem that prompted the workaround 
was resolved by other means, and the pipeline is back to a single consistent 
image.
   
   Closing as fixed. Worth resolving JIRA HUDI-9287 to match. If the intent was 
broader - pinning the image version explicitly so a future runner-image upgrade 
cannot reintroduce this - that is worth a fresh ticket, since it is a different 
requirement from consistency across jobs.
   


-- 
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]

Reply via email to