Also i see that
Dependencies Resolved
===
Package
Also, i check, rpeos are ok, but system force me to install nightly.
[root@prd-sat-01 yum.repos.d]# rpm -qa | grep foreman-release
*foreman-release-scl-3-1.el7.noarch*
*foreman-release-1.15.6-1.el7.noarch*
[root@prd-sat-01 yum.repos.d]# rpm -qa | grep katello-release
[root@prd-sat-01 yum.repos.d]#
I have to admit I haven't done much testing with discourse but so far I
like what I see.
The one thing I can say in favor of the mailing list is that I see the
numbers go up in my inbox and that reminds me to go and check and stay
updated.
I can achieve the same by using discourse in mailing list
On Wed, Nov 22, 2017 at 1:42 PM, Marek Hulán wrote:
> Dne středa 22. listopadu 2017 11:59:16 CET, Greg Sutcliffe napsal(a):
> > Heya!
> >
> > Answers in-line, but I wanted to put a quick summary here for folks in a
> > hurry. Most, if not all, of these questions are *technical* in nature -
> > th
In case you missed it, this was recorded last week. In this community demo,
we covered ui changes, updates in the installer, an intro to discourse,
updates to foreman-maintenance and more.
Sections in this demo:
* Intro (orabin) - https://youtu.be/QHzNIFjMpTM?t=0
* HTTP Proxies (jsherrill) - https
Thanks for answers, as long as you will keep pushing changes upstream
and try to solve some of my concerns, that'd be fine. The most
annoying is the big blue button for me, I'd prefer some small
light-gray link instead (if any). I understand that's only my personal
preference, you could possibly pu
On 23/11/17 14:16, Lukas Zapletal wrote:
> Thanks for answers, as long as you will keep pushing changes upstream
> and try to solve some of my concerns, that'd be fine.
Thanks for being understanding, nothing is going to be perfect for
everyone. Of course we'll do our best to get changes where we
On 22/11/17 11:42, Marek Hulán wrote:>
> Yes please, editing feature feels odd to me. When you read the thread
> later, it can be very confusing. Especially if we don't get email
> notifications about the edit.
Done.
> Just to minimize the risk this could happen, I think it would be
> reasonable
Hi,
I just went over the installation steps at [1]. I executed on a clean
CentOS 7:
yum -y localinstall
http://fedorapeople.org/groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-repos-latest.rpm
yum -y localinstall
http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm
yum
Hello guys
Sorry but I need some help installing foreman for the first time,
reading the docs there are too many option which is good but Im confused
I have a puppet server 5 already running, puppetdb is already running on
the same server also, so I want to install foreman on it, do you know
Hi, im running into this issue with foreman 1.15 and an external rds mysql
database
the installation from a fresh new ami:
foreman-installer \
--foreman-db-type=mysql \
--foreman-db-host=host.us-west-2.rds.amazonaws.com \
--foreman-db-database=foreman \
--foreman-db-username=foreman \
Hi there,
after using Foreman successful on our clusters for more than a year. I'd
like to reinstall a 90 node cluster with Centos 7.4. It's now running on
Centos 7.3 . I'm not able to just update to 7.4 because of zfsonlinux
dependencies and well - some nodes died and had to bare metal instal
On 24 November 2017 at 03:23, Ondrej Prazak wrote:
> Hi,
> I just went over the installation steps at [1]. I executed on a clean
> CentOS 7:
>
> yum -y localinstall
> http://fedorapeople.org/groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-repos-latest.rpm
> yum -y localinstall
> http
Seeing the facts, that the connection seems to work from scripts but not
from the service,
I would recommend trying `setenforce 0` for start to rule out SELinux could
be the case here
-- Ivan
čt 23. 11. 2017 v 20:57 odesílatel napsal:
> Hi, im running into this issue with foreman 1.15 and an ex
14 matches
Mail list logo
