[foreman-users] Filesystem changes for repositories after update?
Hi, We recently (3 months ago?) updated from one version of Katello to the next (Foreman 1.12 to 1.13; Katello 3.1 to 3.2). During that process I also changed the structure of our Content Views and Composite Content Views to better reflect our structures. Last week we started to run out of room on the server in question and I started to look around for what was using the space. I noticed that there was a directory that contained a lot of data about CVs that no longer existed. /var/lib/pulp/published/yum/master has a lot of old data in it, and /var/lib/pulp/published/yum/master/yum_distributor seems to have all the newer data in it. Since the CVs in question have been "deleted" from Katello, there is no obvious way to clean this data up. Is this a known change and can I delete the old data from this directory (except from yum_distributor) or is there associated meta data stuck somewhere that requires I use another method? cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: Deep Dive - Monitoring with Foreman, 4pm CEST Thu 27th Apr
Sadly we had to push this back by a week - the new date is Thu May 4th, same time. See you then! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Katello 3.4 RC2 Available for Testing
In conjunction with the release for Foreman 1.15 RC2, Katello 3.4 RC2 is now available for testing. Please help by testing and filing any issues that you find so that we may address them before the final release. Installation: https://theforeman.org/plugins/katello/3.4/installation/index.html Upgrade: https://theforeman.org/plugins/katello/3.4/upgrade/index.html See the preliminary changelog for detailed information: https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md Bug reporting = If you come across a bug in your testing, please file it and note the version of Katello or Foreman that you're using in the report. http://projects.theforeman.org/projects/katello/issues/new -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: What do I need to backup if capsule needs to be reinstalled?
The answer I got to the same question from RH support is that capsule doesn't need to be backedup. You just reinstall it using the same ip. On Wednesday, April 26, 2017 at 12:42:45 AM UTC+2, George Lim wrote: > > What if I need to reinstall Capsule for some reason? What do I need to > backup so I can restore after the re-installation? > > 1. I don't care about the pulp contents since I can re-sync it back. > 2. There are clients connected to capsule. If I re-install, would the cert > change and affect the clients? The clients are already placed in their > hostgroups and host-collection and I don't want to lose the configuration. > 3. Is there anything else to backup and restore? > > > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: nsupdate on foreman-proxy doesn't work anymore
deleting foreman-proxy-files in /tmp folder did help.
Am Mittwoch, 26. April 2017 13:40:25 UTC+2 schrieb Denis Müller:
>
> Hello guys,
>
> since i justed updated and restart foreman-proxy on a centos 6 machine, i
> can't assign new ip addresses anymore. Foreman-proxy debug shows me:
>
> *trying to find an ip address, we got {:to=>nil, :from=>nil}*
>
> Configuration didn't change. I restarted foreman-proxy and dhcpd couple of
> times but no luck. What is wrong with that ?
>
>
> *foreman-proxy-1.12.4-1.el6.noarch*
>
> *and we have foreman-server in version 1.14.3*
>
> Can somebody help me?
>
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: Foreman deleting host leaves certificate on puppetserver intact
Problem is solved. I forgot: edit host -> and then set to managed :) -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
