Try To install 1.12 foreman could be related to the version of
foreman+puppet that is not compatible
On Sunday, September 4, 2016 at 5:35:31 PM UTC+2, Arun Coder wrote:
>
> I am trying to install foreman/puppet-enterprise for almost 7 days now
> without success. Why am I getting the below error?
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 <%
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 directo
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
o
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
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 Googl
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, a
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 min
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
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 ar
attribute sn
Email address attribute mail mail
Let me know if you have any issues
Kind Regards
Mario Gamboa
On Thursday, May 25, 2017 at 2:30:57 PM UTC+2, Xabi Martí wrote:
>
> Hi! I'm having a problem with the Active Directory connection, the test is
> working but the user
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
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 ?
>
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
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:
Hi there i just trigger this issue can i ask what kind of soft did you use
for make the vpn ?
and if you have a instruction or manual of how to do that would be nice
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this gro
I have same issue and apparently we can't upgrade directly from 2.4 version
to the latest one you need first upgrade to 3.0
https://theforeman.org/plugins/katello/3.0/upgrade/index.html and after
that upgrade to 3.1 3.2 up to 3.4 for me was the only way to get the latest
version and works fine
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
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
> suppo
19 matches
Mail list logo
