Foremanctl Upload package profile for a host not working

Support
1

Problem:

Expected outcome: Upload package profile for a host is working

Foreman and Proxy versions: foremanctl-3.0.0.develop-4.20260806191135884226

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data: Rocky Linux release 10.2

Hi everyone,
After pulling the latest images using foremanctl pull-images and subsequently running foremanctl deploy --add-feature foreman-proxy --add-feature remote-execution --add-feature hammer, the “Upload package profile for a host” function no longer works. I only see the following message:
1: Error initializing command: RuntimeError - No such file or directory -sshpass
2: Exit status: EXCEPTION
3: StandardError: Job execution failed

It fails regardless of which host I select. And sshpass is installed on the respective hosts.
I noticed that sshpass is active within the Foreman container but is missing from the Foreman-Proxy container.
I would expect sshpass to be present in the Foreman-Proxy container, though please correct me if I am mistaken.
Does anyone know where the problem might lie?

Best regards,
Dirk

2

I am guessing the problem is not just with this individual job, but with any remote execution job.

Have you also run foremanctl deploy with --add-feature remote-execution ?

3

Hello Jeremy,

I tried bootc, commands, and katello from the “Job category,” but none of them worked.
Yes, after running foremanctl pull-images, I always ran the following command: foremanctl deploy --add-feature foreman-proxy --add-feature remote-execution --add-feature hammer—which, until now, had always yielded the desired result.

4

Are you using ssh passwords instead of keys to login to your systems?

5

I’ve opened install sshpass in proxy container by evgeni · Pull Request #82 · theforeman/foreman-oci-images · GitHub
You can try the image at quay.io/foreman/stage/foreman-proxy:pull-request-82

6

Yes, i am using ssh passwords, no keys. Is that a problem?

7

Thanks for the info. I’ll give it a try and get back to you with the result.

8

It’s not a problem per-se, just something we didn’t test when doing that feature and thus failed to add that dependency correctly.

9

With this image everthing is working fine right now, thx evgeni :grinning_face:

10

Great. We did end up injecting the package differently (via a packaging dependency, not an explicit installation in the Containerfile), but the result will be the same.

Thanks for finding this and telling us!