Configuring IDM_REALM unsuccessful about robottelo-ci

[pondrejk]

Looking at robottelo/tests/foreman/ui/test_ldap_authentication.py it seems that it does the same idm configuration in https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/ui/test_ldap_authentication.py#L212

I suppose this wouldn'ŧ be necessary if product_install() executed idm enroll properly

[lpramuk]

It's true by default in provisioning job:
https://github.com/SatelliteQE/robottelo-ci/blob/master/jobs/parameters/satellite6_authentication_parameters.yaml#L20

but trigger job passes its environment to provisioning job and this seem to be broken

[pondrejk]

The IDM_REALM is the only boolean parameter that is passed from trigger and the only one that misbehaves:

robottelo-ci/workflows/qe/satellite6-automation/satellite6-trigger.groovy

Line 103 in fd789c4

booleanParam(name: 'IDM_REALM', defaultValue: true),

The same problem occurs in satellite6-sanity-check-6.7 job that also receives IDM_REALM boolean.
There was a simmilar bug reported in https://issues.jenkins-ci.org/browse/JENKINS-43486 though supposedly fixed in pipeline-model-definition-plugin 1.1.3

[pondrejk]

note to self: if #1776 ineffective, alternate solution would be to remove passdown of IDM_REAL entirely from trigger. Presumably the provisioning job would then use it's default. This would remove the possibility to set the value from the trigger, though this didn't happen anyway with hard setting to true