[ https://issues.jboss.org/browse/JBDS-4422?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4422: ---------------------------------- After a couple updates, including one where I remove the rh-eclipse46.repo file entirely [1], I'm still not getting the new rh-eclipse47-build.repo file onto the slaves. [1] https://gitlab.mw.lab.eng.bos.redhat.com/nboldt/mwqa-cloud-slaves/commit/... https://dev-platform-jenkins-rhel7.rhev-ci-vms.eng.rdu2.redhat.com/view/C... -> https://dev-platform-jenkins-rhel7.rhev-ci-vms.eng.rdu2.redhat.com/view/D... -> {code} + ls -la /etc/yum.repos.d/ total 40 drwxr-xr-x. 2 root root 132 May 3 01:15 . drwxr-xr-x. 136 root root 12288 Jun 22 14:59 .. -rw-r--r--. 1 root root 525 May 17 2016 avocado-el.repo -rw-r--r--. 1 root root 957 Dec 27 12:37 epel.repo -rw-r--r--. 1 root root 1056 Dec 27 12:37 epel-testing.repo -rw-r--r--. 1 root root 1797 May 3 01:07 pulp.repo -rw-r--r--. 1 root root 358 May 2 09:04 redhat.repo -rw-rw-r--. 1 hudson hudson 182 May 3 00:52 rh-eclipse46.repo {code} So as a result the rpm builds will be broken too. {code} 18:30:17 Your system is not configured to resolve rh-eclipse47 packages! 18:30:17 Configure with: 18:30:17 $ su -c 'cp rh-eclipse47-build.repo /etc/yum.repos.d/rh-eclipse47-build.repo' {code} -- https://dev-platform-jenkins-rhel7.rhev-ci-vms.eng.rdu2.redhat.com/view/D... So... somehow the new configuration is not being used when we spin up new *rhel7-devstudio-releng* slaves in RHEL7 jenkins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)