mattcasters opened a new pull request, #8924:
URL: https://github.com/apache/hop/pull/8924

   Jenkins build 
[2344](https://ci-builds.apache.org/job/Hop/job/Hop-integration-tests/2344/) of 
the nightly integration tests failed on agent `builds44`. The same tests passed 
the day before on `builds22`. Two failures:
   
   **MongoDB.** `builds44` does not advertise AVX. Official `mongo:8` and 
`mongodb/mongodb-atlas-local` are built with AVX, so `mongod` dies with SIGILL 
(exit 132) and `mongo.environment_setup` never starts. The integration images 
keep those binaries and run `mongod` under `qemu-user` only when AVX is 
missing. Hosts that have AVX still run it natively. `HOP_MONGO_FORCE_QEMU=1` 
forces emulation. Healthcheck grace is longer so a qemu init can finish. A 
native start is still marked healthy as soon as the check passes.
   
   **SSH private key.** `hadoop-common` 3.4.2 depends on `com.jcraft:jsch` 
0.1.55. The Beam assembly unpacked that jar into `lib/core` next to mwiede JSch 
2.28.6. The launcher loads whichever jar the filesystem lists first. 0.1.55 
only signs deprecated `ssh-rsa`, which OpenSSH 9 rejects, so 
`ssh.0002-ssh-command-private-key` failed with `Auth fail`. The password test 
does not need that signature. The Beam `lib/core` set now excludes 
`com.jcraft:jsch`. mwiede JSch, packaged by `hop-core`, stays.
   
   Verified locally:
   
   - With emulation forced, both Mongo containers became healthy and an 
authenticated insert succeeded on each. On this AVX machine, `mongod --version` 
without the force flag does not start qemu.
   - `dependency:tree` shows `com.jcraft:jsch` only through Beam's 
`hadoop-common`. The Spark engine and the Google plugin do not pull it. The 
packaged Beam zip contains no `jsch` jar.
   - Against the integration SSH server, mwiede 2.28.6 authenticates with the 
test key and JCraft 0.1.55 fails with `Auth fail`.
   
   The nightly Docker suite was not rerun.
   
   fixes #8923
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [x] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


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