[foreman-users] Re: Install on Fedora 26 failed

[Mario Gamboa]

Who knows if going to be supported but why you are not using CentOS is 
supported and you not going to have any issues

On Saturday, October 14, 2017 at 5:34:56 PM UTC+2, 
c.j...@graphique-alliance.com wrote:
>
> Hi,
>
> Fedora 24 is in EOL status since August, 2017. Are there any plans on 
> supporting Fedora 26 soon ?
>
> I'm trying to install foreman on a fresh setup of Fedora 26. (ok it's not 
> officialy supported but ...)
>
> Just running foreman-installer give me this output (attached file). It 
> seems to fail while choosing the good postgresql package.
>
> Should i downgrade to Fedora 24 ? or maybe Fedora 25 as i prefer not to 
> install EOL distros ? 
>
> If you need more informations, if you need beta testing or anything else, 
> please let me know as I would be really happy to help you.
>
> Best regards,
>
> Claude
>
>
>
>

-- 
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.

Re: [foreman-users] Re: Katello 3.4.4 Released

[Mario Gamboa]

i have same issue

no redhat repos and no access to them neither

On Wednesday, August 9, 2017 at 1:54:04 PM UTC+2, Eric Helms wrote:
>
> Few questions to help us debug:
>
>  1) Are all repos missing from the UI? Just custom? Just red hat repos?
>  2) Do clients have repo access still?
>
> On Aug 9, 2017 3:31 AM, "'Denis Müller' via Foreman users" <
> forema...@googlegroups.com > wrote:
>
>> Hello and thank you for the release. But after i did the update to the 
>> latest version, i can't see and access any repos anymore. I can see the 
>> product but no repos.
>>
>> Am Mittwoch, 2. August 2017 17:51:15 UTC+2 schrieb Eric Helms:
>>>
>>> We are happy to announce the GA of Katello 3.4.4. This release contains 
>>> a large number of bug fixes for both small UI issues, user issues found 
>>> while using 3.4.4 and developer found issues that we felt would bring more 
>>> stability to users.
>>>
>>> The highlights are too numerous to outline here, so I would recommend to 
>>> please look at the changelog for a full list of changes:
>>>
>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>>>
>>> Installation:
>>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>>
>>> Upgrade:
>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>>
>>>
>>> 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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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: Missing registered smart proxy foreman.domain, please ensure it is registered

[Mario Gamboa]

That's correct if you want to provisioning or distribute repos you can use 
the smartproxy  but if you want to provisioning in the same foreman network 
you need the smart proxy because the proxy host the services of dhcp tftp  
dns plus any plugin you want to have
 

On Monday, June 12, 2017 at 6:36:57 PM UTC+2, marian...@gmail.com wrote:
>
> Hello,
>
>
> I have the following setup:
>
> Host1: mysql/maria DB
> Host2: foreman
> Host3: smart proxy + puppetmaster
> Host4: smart proxy + puppet ca
>
> I added/registered both smart proxies (host 3 and 4) to foreman. They show 
> up below "Infrastructure->Smart proxies". 
>
> in foreman UI in Provisioning setup ("Infrastructure->Provisioning setup") 
> foreman insists on the following prerequisite:
> 1.) ... 
> 2.) Missing registered smart proxy foreman.domain (== host 2), please 
> ensure it is registered
> 3.) ...
>
> As far as I understand, I dont need smart proxy on foreman. Is that 
> correct ?
>
> I am using centos 7.3, foreman 1.15, puppet 4.10.1, puppet server 2.7.2
>
> Regards,
> Marian
>
>

-- 
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] Capsule upgrade missing parameters can't upgrade

[Mario Gamboa]

Hi

I following the instruction to upgrade a capsule server from 3.1 to 3.4 but in 
the instructions show this

foreman-installer --scenario foreman-proxy-content --upgrade\
  --foreman-proxy-content-certs-tar 
~/myproxy.example.com-certs.tar\
  --certs-update-all --certs-regenerate --certs-deploy

Foreman installer response that --certs-regenerate --certs-deploy are no a 
valid parameters so what are the current instructions for upgrade the capsule 
server

-- 
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.

Re: [foreman-users] Impossible to add a new Provisionning on an other network

[Mario Gamboa]

i have the same issue before i check if y
the dhcp configuration in the proxy was enable also check if the url on the 
foreman-proxy and the trusted hosts are correct 
On Monday, May 29, 2017 at 10:44:13 AM UTC+2, Quentin lenglet wrote:
>
> Hi,
>
>
> Somebody has been already in this situation ?
>
> Thx for any answers
>
> Cheer
>
> Quentin Lenglet
>

-- 
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.

Re: [foreman-users] Foreman installation fails

[Mario Gamboa]

Check  you foreman configuration

/etc/puppet/foreman.yaml
:url: "https://katellomain.example.com; 
in my case  the url was empty try to verify is have you proxy fqdn and 
restart katello-services 

On Monday, May 29, 2017 at 4:30:54 PM UTC+2, bijith nair wrote:
>
> Thanks Dominic, Removing proxy fixed the issue.
>
> Also when i am trying to run puppet --agent test, It fails with permission 
> error:-
>
> Note: I am running it at root
>
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
> Error: Could not send report: Error 403 on SERVER:  "-//IETF//DTD HTML 2.0//EN">
> 
> 403 Forbidden
> 
> Forbidden
> You don't have permission to access 
> /production/report/foremanprodpoc.testlab.local
> on this server.
> 
>
>
> On Friday, 26 May 2017 13:19:37 UTC+5:30, Dominic Cleal wrote:
>>
>> On 26/05/17 08:26, bijith nair wrote: 
>> > Everytime i perform installation it fails with below error.. 
>> > 
>> > 
>>  
>> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foremanprodpoc.testlab.local]:
>>  
>>
>> > Could not evaluate: Exception 502 "Proxy Error ( Try the request again. 
>> >  )" in get request to: 
>> > 
>> https://foremanprodpoc.testlab.local/api/v2/smart_proxies?search=name=%22foremanprodpoc.testlab.local%22
>>  
>>
>> As the message says, an [HTTP] proxy is returning a 502 error. If you 
>> have an http_proxy (or similar) environment variable set, try unsetting 
>> it. Else make sure the proxy can connect to foremanprodpoc.testlab.local. 
>>
>> -- 
>> Dominic Cleal 
>> dom...@cleal.org 
>>
>

-- 
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: is gutterball used with foreman/katello?

[Mario Gamboa]

In not using anymore :)

On Friday, March 24, 2017 at 5:48:20 PM UTC+1, Cristian Falcas wrote:
>
> Hello,
>
> Is gutterball still used? I see that the puppet modules have a warning 
> that the module is UNMAINTAINED.
>
> Thank you,
> Cristian Falcas
>
>

-- 
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: theforeman 1.10 -> 1.11 upgrade (with katello 2.4 -> 3.0) fails at db:seed.

[Mario Gamboa]

I have same issue and my solution was upgrade from 2.4 to 3.1 and the 
issues gone i don't know if possible works for you 

On Friday, February 24, 2017 at 5:13:35 PM UTC+1, Cristóbal Palmer wrote:
>
> Greetings,
>
> I've got a rather old install that I'm trying to step forward one release 
> at a time from 1.10.x to current. I got stuck at the first upgrade, sadly.
>
> I was following this: 
> https://theforeman.org/manuals/1.11/index.html#3.6Upgrade
>
> The package updates installed fine (with a gotcha! -- the first time I 
> failed out because I had repositories for katello 2.4 configured. 
> Configuring the 3.0 repos and then retrying the 1.10 -> 1.11 package 
> updates worked... but there was an additional gotcha on the gotcha: I ALSO 
> tried upgrading katello from 2.4 to 3.0 following 
> https://theforeman.org/plugins/katello/3.0/upgrade/index.html before 
> upgrading foreman... and the first time that failed at the yum update step 
> saying that the installed foreman was too old. Turns out that "yum upgrade 
> tfm\* ruby\* foreman\*" step on the foreman instructions was important!).
>
> Anyway, I finally got to where this runs mostly without error:
>   foreman-installer --scenario katello --upgrade
>
> The errors:
>
>   Upgrade Step: Running installer...
>   
> /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
>  
> Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead 
> of one of [0]
>   
> /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
>  
> /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
>   Installing Done [100%] 
> [...]
>   Something went wrong! Check the log for ERROR-level output
>   The full log is at /var/log/foreman-installer/katello.log
>
> Rerunning the failing step gives me: 
> https://gist.github.com/anonymous/202564d5de17d948ec0772c6d6a446aa
>
> Suggestions most welcome.
>
> --
> CMP
>

-- 
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: Katello and Errata updates

[Mario Gamboa]

yes you can the increment in version only reflect the current repo with all 
you current erratas and bugfix you can see which one is the current 
depending of the environment 





Am Donnerstag, 2. März 2017 23:17:00 UTC+1 schrieb Lachlan Musicman:
>
> Hola,
>
> When one ticks off an Errata, a minor version of the Content View is 
> created (see att image).
>
> How are they stored on the filesystem? Is it ok to delete any of the 
> versions an just keep the most recent?
>
> For eg, if I make version 3.0 and then over a month there are 4 errata 
> updates, taking us to 3.4.
>
> Can I delete the versions 3.1, 3.2 and 3.3? Can I delete version 3.0?
>
> Are minor versions stored as a diff or as a snapshot of the whole CV?
>
> 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: REALM > Insufficient 'add' privilege to the 'userPassword' attribute

[Mario Gamboa]

did you first join the satellite to the freeipa and create the user with 
the necessary permissions to execute the modifications on the ipa server?


Normally just need to run
 foreman-prepare-realm
 
as per instructions as i said your Smart Proxy must be registered to the 
FreeIPA realm already, and have the ipa-admintools package installed.

Am Samstag, 25. Februar 2017 00:48:54 UTC+1 schrieb Matt:
>
> Hi Guys, 
>
> Following the docs I tried to setup the IPA Realm part for the proxy 
> and I get this error: 
>
>
> D, [2017-02-25T00:41:25.038075 #12948] DEBUG -- : Kerberos credential 
> cache initialised with principal: 
> foreman-proxy/host.domain@domain.tld 
> E, [2017-02-25T00:41:25.526166 #12948] ERROR -- : Insufficient access: 
> Insufficient 'add' privilege to the 'userPassword' attribute 
> D, [2017-02-25T00:41:25.526568 #12948] DEBUG -- : Insufficient access: 
> Insufficient 'add' privilege to the 'userPassword' attribute 
> (XMLRPC::FaultException) 
>
> I have checked the attribute and the add privilege exists, so what 
> could be wrong ? 
>
> Thanks, 
>
> Matt 
>

-- 
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: Puppet upgrade from 3.x to 4.x fails

[Mario Gamboa]

Any solution ?

Same  issues here the thing that is amazing the katello and foreman team 
they are planning to no support anymore puppet 3 on 1.15 foreman but how we 
are going to upgrade our current puppet 3 to 4 is ridiculous 

-- 
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: Katello 3.1 DNS capsule certificate error

[Mario Gamboa]

Hi there 

Did you have all the port needed open from  Katello server to you capsule 
and reverse?

Katello to Capsule ports 
8443/tcp
443/tcp
9090/tcp
5647/tcp

Capsule to Katello Ports
443/tcp
5646/tcp

Also try without firewall enable on the machines and selinux disable this 
normally indicate a firewall issue

On Friday, February 10, 2017 at 5:40:45 PHM UTC+1, Edson Manners wrote:
>
> I'm trying to add a DNS/DHCP capsule/proxy to a Katello 3.1 instance with 
> custom web certs. I've tried using these instructions but they don't seem 
> to help.
>
> http://projects.theforeman.org/issues/16620
>
> Definitey seems like a cert issue becasue of the custom Web Cert that 
> we're running but I can't seem to get the proxy to connect. Any help 
> pointing me int he right direction is appreciated.
>
> Here's what I do:
> ===
> 1. yum -y localinstall 
> http://katello3.xxx.xxx.xxx/pub/katello-ca-consumer-latest.noarch.rpm
> 2. subscription-manager register --org "XXX" --environment 
> "production/centos7"
>
>
> 3. foreman-installer --scenario capsule\
> --capsule-parent-fqdn 
> "katello3.xxx.xxx.xxx"\
> --foreman-proxy-register-in-foreman   "true"\
> --foreman-proxy-foreman-base-url  "
> https://katello3.xxx.xxx.xxx"\
> --foreman-proxy-trusted-hosts 
> "katello3.xxx.xxx.xxx"\
> --foreman-proxy-oauth-consumer-key   
>  "WNhk9x8zxdxhxRUsagocAkmdTRtAD8Q"\
> --foreman-proxy-oauth-consumer-secret 
> "LqiNeGEbhxgxrex8AV6kqxXeiNCsyz7um"\
> --capsule-pulp-oauth-secret   
> "5rdFmrpSsxHXxsxdxJXacjyn9NCcAKi"\
> --capsule-certs-tar   
> "/root/capsule.dns1.xx.xxx.xxx-certs.tar"\
> --foreman-proxy-puppetca  "false"\
> --foreman-proxy-puppet"false"\
> --foreman-proxy-http  "false"\
> --foreman-proxy-templates "false"\
> --foreman-proxy-plugin-pulp-pulpnode-enabled  "false"\
> --foreman-proxy-dhcp  "true"\
> --foreman-proxy-dhcp-interface"ens3"\
> --foreman-proxy-dns   "true"\
> --foreman-proxy-dns-interface "ens3"
> === 
>
> Here is the error:
>  Proxy dns1.yyy.yyy.yyy cannot be registered: Unable to communicate with 
> the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features 
> ([RestClient::SSLCertificateNotVerified]: SSL_connect returned=1 errno=0 
> state=SSLv3 read server certificate B: certificate verif...) for proxy 
> https://dns1.yyy.yyy.yyy:9090/features Please check the proxy is 
> configured and running on the host.
>  
> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[dns1.yyy.yyy.yyy]/ensure:
>  
> change from absent to present failed: Proxy dns1.yyy.yyy.yyy cannot be 
> registered: Unable to communicate with the proxy: ERF12-2530 
> [ProxyAPI::ProxyException]: Unable to detect features 
> ([RestClient::SSLCertificateNotVerified]: SSL_connect returned=1 errno=0 
> state=SSLv3 read server certificate B: certificate verif...) for proxy 
> https://dns1.yyy.yyy.yyy:9090/features Please check the proxy is 
> configured and running on the host.
> Installing Done   
> [100%] [...]
>   Something went wrong! Check the log for ERROR-level output
>   The full log is at /var/log/foreman-installer/capsule.log
>
>
> Here is the proxy status:
> [root@dns1 named]# systemctl status foreman-proxy
> ● foreman-proxy.service - Foreman Proxy
>Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled; 
> vendor preset: disabled)
>Active: active (running) since Wed 2017-02-08 16:33:31 EST; 1 day 18h 
> ago
> ...
>
> Here is the proxy showing the correct features:
> [root@katello3 foreman-proxy]# wget https://dns1.xxx.xxx.xxx:9090/features
> ...
> Saving to: ‘features’
> ...
> [root@katello3 foreman-proxy]# cat features
> ["dhcp","dns"]
>

-- 
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.

Re: [foreman-users] Re: RHEL installation media path in Satellite 6

[Mario Gamboa]

try to change to any organization and any location after that try to check
if you can see in the manage organization the installation media of rhel if
there just go now to the location and try to check if the installation
media is on it also normally you need to check if the media is added on the
organization and location to appear as expected

On Wed, Dec 7, 2016 at 4:21 PM, Eric Martin  wrote:

> I've using Katello 3.2/foreman 1.13 and I'm adding redhat repositories.
> This works fine. Products are created automatically. But not the
> installation medias.
> Any idea?
>
> In Content --> Products I have "Red Hat Enterprise Linux Server" product
> with the following repos:
> Red Hat Enterprise Linux 7 Server RPMs x86_64 7.3
> Red Hat Enterprise Linux 7 Server - RH Common RPMs x86_64 7.3
> Red Hat Enterprise Linux 7 Server Kickstart x86_64 7.3
> I was expecting the installation media RedHat 7 to be created under Host
> --> Installation Media. But it's not the case.
> I also sync'ed the RHEL 6 repos as mentioned in this post. Also no luck,
>
> Thanks!
> Eric
>
>
> On Wednesday, January 7, 2015 at 11:52:55 AM UTC+1, David Evans wrote:
>>
>> Hi,
>>
>> Can anyone advise me of the correct (best practice?) way to configure
>> installation media?
>>
>> I’m using Satellite 6 and I’ve synced the various repos so that I have
>> ISOs, Kickstart and RPMs for RHEL 6server, 6.4, 6.5 and 6.6.  Presumably it
>> would be a good idea to use the objects that I’ve synced, but I don’t know
>> the correct path to use to achieve that.  This the path I’m currently using:
>>
>> http://satellite/pulp/repos/Company/Library/content/dist/rhe
>> l/server/$major/$major.$minor/$arch
>>
>> That seems to basically work, but I hit problems later in the build and
>> so I'd like to have it confirmed that the path I'm using is not part of the
>> problem.  (The documentation I'm working from doesn't make it clear.)
>>
>> Thanks in advance for any assistance.
>>
>> Rotty
>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-users/9BHZcyiaKLU/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>

-- 
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] After upgrade to RHEL 7.3 Katello have some issues

[Mario Gamboa]

Well after the upgrade of RHEL have some issues 

The upgrade make the package httpd to install a ssl.conf inside of httpd 
conf.d directory this make the service httpd doesn't start also for some 
strange reason postfix also stop working the solution of it was mv the 
ssl.conf to any other directory and for postfix the problem was can't found 
localhost i found for some strange reason with the new upgrade all the 
hostnames are pointing to 127.0.0.1 but because the first one is pointing 
to the hostname to my katello.example.com i just move the 
katello.example.com again to ip and localhost only pointing to 127.0.0.1

i just checking all looks ok until i try provisioning the dhcp just gone 
from the smart proxy and is no working anymore the quick fix was run again 
the foreman-installer with the option of install dhcp and apparently some 
files change like squid.conf  after finish the script still not working 
need to restart all the services with katello-service restart and boom is 
back and running 

i just let you know if someone else have the same issues right now

-- 
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: Automate puppet agent install?

[Mario Gamboa]

Did you try this add it into you kickstart

echo "Configuring puppet"
cat > /etc/puppet/puppet.conf << EOF
<%= snippet 'puppet.conf' %>
EOF

# Setup puppet to run on system reboot
/sbin/chkconfig --level 345 puppet on

/usr/bin/puppet agent --config /etc/puppet/puppet.conf -o --tags 
no_such_tag <%= @host.puppetmaster.blank? ? '' : "--server 
#{@host.puppetmaster}" %> --no-daemonize
<% end -%>


Create a snippet of puppet.conf
%#
kind: snippet
name: puppet.conf
%>
<%
  if @host.param_true?('enable-puppetlabs-pc1-repo') && 
(@host.operatingsystem.family == 'Debian' || @host.operatingsystem.family 
== 'Redhat')
var_dir = '/opt/puppetlabs/puppet/cache'
log_dir = '/var/log/puppetlabs/puppet'
run_dir = '/var/run/puppetlabs'
ssl_dir = '/etc/puppetlabs/puppet/ssl'
  else
if @host.operatingsystem.family == 'Freebsd'
  var_dir = '/var/puppet'
else
  var_dir = '/var/lib/puppet'
end
log_dir = '/var/log/puppet'
run_dir = '/var/run/puppet'
ssl_dir = '\$vardir/ssl'
  end
%>
[main]
vardir = <%= var_dir %>
logdir = <%= log_dir %>
rundir = <%= run_dir %>
ssldir = <%= ssl_dir %>

[agent]
pluginsync  = true
report  = true
ignoreschedules = true
<%- if @host.puppet_ca_server.strip -%>
ca_server   = <%= @host.puppet_ca_server %>
<%- end -%>
certname= <%= @host.certname %>
environment = <%= @host.environment %>
server  = <%= @host.puppetmaster %>

-- 
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.