Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-17 Thread Lachlan Musicman
It was the first thing I did after sending that email. http://projects.theforeman.org/issues/18548 Let me know if you need any more information. cheers L. -- The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 18 February 2017 at 13:44, Eric D

Re: [foreman-users] Re: DHCP failover

2017-02-17 Thread Alvin Starr
I actually hacked up a wrapper to the /usr/bin/omshell that would write data to multiple DHCP servers. It worked and past my initial testing but I never got much of a chance to implement it. The requirement on my end for failover got eclipsed by other more pressing problems. I did post the

Re: [foreman-users] katello centos-base repo not syncing

2017-02-17 Thread Eric D Helms
Does the sync task itself fail? If so, what do you see on the errors tab of the task? Is Pulp throwing an error? Thanks Eric On Feb 16, 2017 10:07 PM, "Edson Manners" wrote: Hate to bump the thread but I have the same issue. Katello 3.1. The sync worked in this repo: http://vault.centos.org/7.

Re: [foreman-users] Re: Puppet upgrade from 3.x to 4.x fails

2017-02-17 Thread Eric D Helms
Could you please file a bug report with this information including your fix or add it to an existing report so that we can look at getting this fixed in the upcoming 3.3 release? Thanks Eric On Feb 16, 2017 11:58 PM, "Lachlan Musicman" wrote: GOT IT. GADDAM. Edited /usr/share/katello-install

Re: [foreman-users] [Katello] Pulp SSL error after upgrade 3.2 -> 3.3

2017-02-17 Thread Eric D Helms
Hi Edgars, Can you check your /etc/foreman/plugins/katello.yaml settings file to see if the :pulp section of the config has an entry for the CA cert? Eric On Feb 17, 2017 6:40 AM, "Edgars M." wrote: Hi I upgraded Katello from 3.2 to 3.3. Upgrade went fine, without any errors. However after u

[foreman-users] Re: PXE-Less from remote network

2017-02-17 Thread ZS-Man
Hi, in log on discovered node is only this: Feb 17 14:00:53 fdi /usr/bin/discovery-menu[834]: Entering screen_facts Feb 17 14:00:53 fdi /usr/bin/discovery-menu[834]: TUI executing: kexec --version Feb 17 14:01:07 fdi /usr/bin/discovery-menu[834]: Registering host at ( https://172.17.129.51:8443)

[foreman-users] [Katello] Pulp SSL error after upgrade 3.2 -> 3.3

2017-02-17 Thread Edgars M.
Hi I upgraded Katello from 3.2 to 3.3. Upgrade went fine, without any errors. However after upgrade Pulp does not work anymore and I can't sync any repos: ==> /var/log/foreman/production.log <== 2017-02-17 11:47:23 [app] [W] SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B

Re: [foreman-users] unable to remove discovered host that failed provisioning

2017-02-17 Thread Fran Terry
The same as the other poster on this thread, version 1.13.4. Have created a ticket for this: http://projects.theforeman.org/issues/18550 I did assign to yourself, however have changed it Thanks Fran On Wednesday, 15 February 2017 12:09:28 UTC, Lukas Zapletal wrote: > > Which error do you see