Very useful, thanks for sharing!
On Mon, May 29, 2017 at 9:50 PM, Lachlan Musicman wrote:
> On 30 May 2017 at 11:40, Lachlan Musicman wrote:
>
>> Great, thanks.
>>
>> I am seeing another issue:
>>
>> - add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
>> to the Katello Con
On 30 May 2017 at 11:40, Lachlan Musicman wrote:
> Great, thanks.
>
> I am seeing another issue:
>
> - add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
> to the Katello Content View (with or without removing pulp-3.3,
> katello-3.3, foreman-1.14) via (in UI) Yum Content, Re
Great, thanks.
I am seeing another issue:
- add the various new products (pulp-3.4, katello-3.4, foreman-1.15 etc)
to the Katello Content View (with or without removing pulp-3.3,
katello-3.3, foreman-1.14) via (in UI) Yum Content, Repository Selection
- publish a new version of the Katello CV
The foreman-release-scl ensures that the necessary SCL epositories are
setup and configured for a typical installation. If you are importing all
the necessary repositories into Katello and using that yourself then I
wouldn't worry about it.
Eric
On Mon, May 29, 2017 at 8:51 PM, Lachlan Musicman
Thanks for all the hard work.
I'd like to ask a question about the upgrade instructions.
In step 3, what does the line
yum update -y foreman-release-scl
do?
The other two lines make sense. This one, I don't quite understand.
We host Katello on katello, so there is some jiggery-pokery with
m
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 ?
>
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
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
update when I use the foreman-installer without Katello I can add my DHCP
proxy without problems:
foreman-installer --scenario foreman --foreman-admin-password test
Le mercredi 24 mai 2017 15:12:11 UTC+2, Vincenzo Z a écrit :
>
> Hello,
>
>
> I'm trying to install katello/foreman with a DHCP s
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+u
Hi David,
thanks a lot for your reply and the issue ticket.
Mh, that looks actually pretty much like the things I did. Additionally
I was setting some values in the administrationnal section of Foreman.
However I will try with a fresh install and try to redo it.
Bests,
Bernhard
On 05/28/2
11 matches
Mail list logo
