Activation keys are only applied at "subscription-manager register" time.
Changes later do not modify previously registered hosts.
On Mon, Mar 6, 2017 at 9:38 PM, Lachlan Musicman wrote:
> When I update the subscriptions in an Activation Key, how do I get that
> change pushed
Any update on this ?
Op dinsdag 28 februari 2017 23:50:31 UTC+1 schreef Matt:
>
> Yes I did, the same machine is also doing DHCP fine with it.
>
> Op dinsdag 28 februari 2017 12:04:06 UTC+1 schreef Daniel Lobato:
>>
>> Have you copied the keytab to the proxy as the manual mentions?
>>
>>
No unfortunately, we are tracking this RFE as:
http://projects.theforeman.org/issues/13847
It has many votes already, upvote. It's one of the most demanded
features for Foreman. Patches welcomed :-)
LZ
On Tue, Mar 7, 2017 at 5:20 PM, wrote:
> Hello
>
> is there a way
Hello
is there a way with Foreman and the autodiscovery plugin to preconfigure
NICs before provisioning the discovered bare metal server?
I want to provision directly with bonded interfaces and right now I've to
do it manually, and I cannot find a way to control this with the
autodiscovery
Hi
I backed up the Postgresql DB on our active server and restored on the new
RHEL 7 server using the instructions in the Foreman manual
(https://theforeman.org/manuals/1.14/index.html#5.5Backup,RecoveryandMigration),
however i receive the following errors:
[root@test ~]# foreman-rake
Hi,
Was there any solution to this problem.
I don't see POST /api/hosts/facts in foreman/production.log even for those
machines where facts are uploaded.
Following are two scenarios where i don't see facts:
1. Installed puppet agent on windows server 2012.
2. Installed puppet agent on
Thanks Josh, what is the best way to migrate all the puppet modules?
On Monday, March 6, 2017 at 12:56:14 PM UTC, Josh wrote:
>
> The easiest way to do this is to simply take a backup of your Foreman
> database and re-import it into your new Foreman instance.
>
> On Mon, Mar 6, 2017 at 5:35 AM,