We realized that check jobs we are running in rdo sf are launched in "rdo-cloud" nodepool provider and not "rdo-cloud-tripleo"
for example this job
https://logs.rdoproject.org/19/570719/22/openstack-check/legacy-tripleo-ci-centos-7-multinode-1ctlr-featureset037-updates-master/d321bb4/
runs in "rdo-cloud" as shown from the zuul inventory variables
https://logs.rdoproject.org/19/570719/22/openstack-check/legacy-tripleo-ci-centos-7-multinode-1ctlr-featureset037-updates-master/d321bb4/zuul-info/inventory.yaml
In our workflow we are baseing some variables inclusion on the nodepool name (for example we are including multinode-rdocloud.yaml). If the jobs are running in "rdo-cloud" a set of variables is not included (for example the whole influxdb_* namespace) and part of the job fails silently.
We need to understand if we have to add another conditional for the inclusion of this variable or if all the jobs should run in "rdo-cloud-tripleo"
We have the upstream-centos-7 label defined in both the rdo-cloud and rdo-cloud-tripleo tenants [1]. I think this should not be the case, and proposed [2] with a fix.
[1] - https:/ /softwarefactor y-project. io/r/gitweb? p=config. git;a=blob; f=nodepool/ rdo-cloud. yaml;h= 2d94ac6b3f2b37b 747a6216a29df28 4f0cae0f80; hb=e3fd510f2846 b4320598cd62e7d 1e36563b6bae9# l201 /softwarefactor y-project. io/r/13329
[2] - https:/