The .repo files deployed by foreman on the hosts seems t be deleted randomly on many host. As a result I need to redeploy them again and again on many servers. Dont know what causes this . any idea or options that does this in foreman settings?
.repo files not to be deleted once deployed
Foreman and Proxy versions:
Foreman and Proxy plugin versions:
Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)
@abraham1986: Thanks for sharing this.
Few questions: Is the redhat.repo file getting deleted on the hosts? Afaik the redhat.repo file is managed by subscription manager so that output is expected. Does the host stay registered after you see the redhat.repo file deleted? I don’t understand this line:
yes, the redhat.repo file is being deleted on the hosts. So each time, I need to redeploy them again but buy doing the following steps.
rpm -Uvh http://10.231.12.88/pub/katello-ca-consumer-latest.noarch.rpm
subscription-manager register --org=“BigDataCC” --activationkey=""
subscription-manager register --org=“BigDataCC” --force --activationkey=" "
For you comment “redhat.repo file is managed by subscription manager so that output is expected”
Do you mean the redhat.repo file is supposed to be deleted or renamed as redhat.repo.dis.**** ?
Does the host stay registered after you see the redhat.repo file deleted?
Yes, i dont know on what time interval it changes renamed or deleted. The server will be listed in Host lists in foreman webui, but actually the redhat.repo file will be missing and when I run the "subscription-manager repos --list " it will say, not attached to any repos.
For my comment “.repo files not to be deleted once deployed”
I expect this file to be present on the server as long as the server is registered with a Activation Key.
NOTE: We have only installed Katello Agents on te servers and no puppet agents are installed as we use chef in our platform.