Bug 2159300

Summary:	Effective user not applied for pull-mqtt jobs
Product:	Red Hat Satellite	Reporter:	Peter Ondrejka <pondrejk>
Component:	Remote Execution	Assignee:	Patrick Creech <pcreech>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	aruzicka, pcreech, zhunting
Target Milestone:	6.13.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman_ygg_worker-0.2.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:12:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Ondrejka 2023-01-09 11:06:59 UTC

Description of problem:
Effective user is not honored for pull-mqtt jobs

Version-Release number of selected component (if applicable):
6.13 snap 5

How reproducible:
always

Steps to Reproduce:
1. Have satellite with pull-mqtt rex enabled
2. Have an yggdrasil host with a "tester" user created
3. Run script command job with "whoami" against the host, set tester as an effective user either globally or per job.

Actual results:
whoami returns root

Expected results:
The selected effective user should be applied

Additional info:
Trying the same with ansible rex succeeded as expected

Comment 1 Adam Ruzicka 2023-01-09 12:24:11 UTC

What version of foreman-ygg-worker do you have?

Comment 2 Peter Ondrejka 2023-01-12 10:16:51 UTC

Hello, it's foreman_ygg_worker-0.1.1-2.el9sat.x86_64

Comment 3 Adam Ruzicka 2023-01-12 10:30:10 UTC

@pcreech IIRC we talked about this some time ago on irc. I know foreman_ygg_worker lives in the client repos so it gets delivered out of sync from snaps, but is there any eta on when we might get the new bits?

Comment 4 Peter Ondrejka 2023-02-06 16:58:22 UTC

Verified on Satellite 6.13 snap 9

Comment 7 errata-xmlrpc 2023-05-03 13:12:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6 Client Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2095