Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Could you share the roles/permissions of the user who logged in via LDAP? Is it an administrator? Does it have any orgs/locs assigned to it? 

It looks like the user is choosing a Organization that does not contain the hosts it's trying to run the job on. 

Please check https://bugzilla.redhat.com/show_bug.cgi?id=1397185#c7 for more information.

Hi Daniel,

Please find attached screenshot to get LDAP user details.

Preetesh

This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1397185 . 

Preetesh, can you verify if you get this error when running a remote execution job and:

- Organization/Location are set to something in the top-left corner selector
- Organization/Location are set to Any context

The 2nd case is known to fail as per the BZ I've linked, the 1st case shouldn't fail and I can't really reproduce it.

I'm closing this BZ as duplicate, as it's most probably describing the same issue as 1397185

*** This bug has been marked as a duplicate of bug 1397185 ***

Clearing needinfo