HADOOP-19398: Upgrade Dockerfile base to jammy
Description of PR
Upgrade the base image of the Ubuntu Dockerfiles used for CI and local development.
How was this patch tested?
- Created and started the build env:
./start-build-env.sh - Built native profile (within the container):
mvn clean install -Pnative -DskipTests
For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
- [ ] If applicable, have you updated the
LICENSE,LICENSE-binary,NOTICE-binaryfiles?
(!) A patch to the testing environment has been detected. Re-executing against the patched versions to perform further tests. The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/1/console in case of problems.
:broken_heart: -1 overall
| Vote | Subsystem | Runtime | Logfile | Comment |
|---|---|---|---|---|
| +0 :ok: | reexec | 38m 50s | Docker mode activated. | |
| _ Prechecks _ | ||||
| +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | |
| +0 :ok: | codespell | 0m 0s | codespell was not available. | |
| +0 :ok: | detsecrets | 0m 0s | detect-secrets was not available. | |
| +0 :ok: | shellcheck | 0m 0s | Shellcheck was not available. | |
| +0 :ok: | shelldocs | 0m 0s | Shelldocs was not available. | |
| +0 :ok: | hadolint | 0m 0s | hadolint was not available. | |
| +0 :ok: | jsonlint | 0m 0s | jsonlint was not available. | |
| +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | |
| -1 :x: | test4tests | 0m 0s | The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. | |
| _ trunk Compile Tests _ | ||||
| -1 :x: | mvninstall | 37m 3s | /branch-mvninstall-root.txt | root in trunk failed. |
| -1 :x: | mvnsite | 4m 20s | /branch-mvnsite-root.txt | root in trunk failed. |
| +1 :green_heart: | shadedclient | 74m 22s | branch has no errors when building and testing our client artifacts. | |
| _ Patch Compile Tests _ | ||||
| -1 :x: | mvninstall | 30m 39s | /patch-mvninstall-root.txt | root in the patch failed. |
| +1 :green_heart: | blanks | 0m 0s | The patch has no blanks issues. | |
| -1 :x: | mvnsite | 4m 21s | /patch-mvnsite-root.txt | root in the patch failed. |
| +1 :green_heart: | shadedclient | 37m 15s | patch has no errors when building and testing our client artifacts. | |
| _ Other Tests _ | ||||
| -1 :x: | unit | 13m 32s | /patch-unit-root.txt | root in the patch failed. |
| +1 :green_heart: | asflicense | 1m 5s | The patch does not generate ASF License warnings. | |
| 197m 33s |
| Subsystem | Report/Notes |
|---|---|
| Docker | ClientAPI=1.48 ServerAPI=1.48 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/1/artifact/out/Dockerfile |
| GITHUB PR | https://github.com/apache/hadoop/pull/7532 |
| Optional Tests | dupname asflicense codespell detsecrets shellcheck shelldocs hadolint jsonlint mvnsite unit |
| uname | Linux 323543cbb1c1 5.15.0-130-generic #140-Ubuntu SMP Wed Dec 18 17:59:53 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/bin/hadoop.sh |
| git revision | trunk / 65611678129d6bd84b9494b8f18ff342f7997a5f |
| Test Results | https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/1/testReport/ |
| Max. process+thread count | 625 (vs. ulimit of 5500) |
| modules | C: . U: . |
| Console output | https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/1/console |
| versions | git=2.9.5 maven=3.6.3 |
| Powered by | Apache Yetus 0.14.0 https://yetus.apache.org |
This message was automatically generated.
I see the only failure is the same one related to the CentOS-7 issue (HADOOP-19489, also mentioned in #7499) - can anyone suggest how should this be resolved?
I see the only failure is the same one related to the CentOS-7 issue (HADOOP-19489, also mentioned in #7499) - can anyone suggest how should this be resolved?
I see that CentOS 7 and 8 are EOL. I would recommend to remove these altogether and may be replace with an alternative RHEL based OS (Rockylinux?).
Similarly Debian 10 is also EOL. I would recommend to update to Debian 11 or (even better 12).
(!) A patch to the testing environment has been detected. Re-executing against the patched versions to perform further tests. The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/2/console in case of problems.
:broken_heart: -1 overall
| Vote | Subsystem | Runtime | Logfile | Comment |
|---|---|---|---|---|
| +0 :ok: | reexec | 38m 29s | Docker mode activated. | |
| _ Prechecks _ | ||||
| +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | |
| +0 :ok: | codespell | 0m 0s | codespell was not available. | |
| +0 :ok: | detsecrets | 0m 0s | detect-secrets was not available. | |
| +0 :ok: | shellcheck | 0m 0s | Shellcheck was not available. | |
| +0 :ok: | shelldocs | 0m 0s | Shelldocs was not available. | |
| +0 :ok: | hadolint | 0m 0s | hadolint was not available. | |
| +0 :ok: | jsonlint | 0m 0s | jsonlint was not available. | |
| +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | |
| -1 :x: | test4tests | 0m 0s | The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. | |
| _ trunk Compile Tests _ | ||||
| -1 :x: | mvninstall | 36m 33s | /branch-mvninstall-root.txt | root in trunk failed. |
| -1 :x: | mvnsite | 4m 24s | /branch-mvnsite-root.txt | root in trunk failed. |
| +1 :green_heart: | shadedclient | 73m 54s | branch has no errors when building and testing our client artifacts. | |
| -0 :warning: | patch | 74m 15s | Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary. | |
| _ Patch Compile Tests _ | ||||
| -1 :x: | mvninstall | 30m 12s | /patch-mvninstall-root.txt | root in the patch failed. |
| +1 :green_heart: | blanks | 0m 0s | The patch has no blanks issues. | |
| -1 :x: | mvnsite | 4m 27s | /patch-mvnsite-root.txt | root in the patch failed. |
| +1 :green_heart: | shadedclient | 37m 4s | patch has no errors when building and testing our client artifacts. | |
| _ Other Tests _ | ||||
| -1 :x: | unit | 13m 29s | /patch-unit-root.txt | root in the patch failed. |
| +1 :green_heart: | asflicense | 1m 4s | The patch does not generate ASF License warnings. | |
| 196m 2s |
| Subsystem | Report/Notes |
|---|---|
| Docker | ClientAPI=1.48 ServerAPI=1.48 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/2/artifact/out/Dockerfile |
| GITHUB PR | https://github.com/apache/hadoop/pull/7532 |
| Optional Tests | dupname asflicense codespell detsecrets shellcheck shelldocs hadolint jsonlint mvnsite unit |
| uname | Linux 6db47e6ea459 5.15.0-130-generic #140-Ubuntu SMP Wed Dec 18 17:59:53 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/bin/hadoop.sh |
| git revision | trunk / 5446fbd35809dd5212db3f7a342b2363df8a2e8f |
| Test Results | https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/2/testReport/ |
| Max. process+thread count | 551 (vs. ulimit of 5500) |
| modules | C: . U: . |
| Console output | https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7532/2/console |
| versions | git=2.9.5 maven=3.6.3 |
| Powered by | Apache Yetus 0.14.0 https://yetus.apache.org |
This message was automatically generated.
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again. Thanks all for your contribution.