ation, but foreman does not show any change in its behavior.
> Any hint?
>
> Thanks
> Monica
>
>
> Il giorno martedì 7 febbraio 2017 21:43:30 UTC+1, Anthony Chevalet ha
> scritto:
>>
>> Hey,
>> In case your are still interested, I've proposed a patc
Hi, should I open a bug for this one? Thanks
2017-08-06 14:01 GMT+02:00 Anthony Chevalet <anthony.cheva...@gmail.com>:
> 1) No, default certificates generated by foreman-installer
> 2) yum: python-requests-2.6.0-1.el7_1.noarch - pip: requests (2.18.2)
>
> 2017-08-04 21:47 GMT+
tes?
> 2) What version of python-requests is on the box? Both from yum and pip's
> perspective?
>
> On Fri, Aug 4, 2017 at 9:11 AM, Anthony Chevalet <
> anthony.cheva...@gmail.com> wrote:
>
>> ps: Initially it was working fine, I suspect it stopped working since
>> I
I had the same problem but finally I was able to sync it with those
settings:
Content Type: yum
Checksum Type: sha256
Mirror on Sync: yes
URL:https://pkg.jenkins-ci.org/redhat-stable/
Publish Via HTTP: yes
Download Policy:immediate
Le vendredi 28 juillet
ps: Initially it was working fine, I suspect it stopped working since I've
created a proxy content.
2017-08-04 12:58 GMT+02:00 Anthony Chevalet <anthony.cheva...@gmail.com>:
> Hi Eric,
>
> When syncing on schedule, there is no task in Foreman. I can see the tasks
> on
u can
> find this in /etc/foreman/plugins/katello.yaml.
>
> We need to figure out if Pulp is hitting Katello and the errors like there
> or if Pulp is not configured to http notify.
>
> On Aug 3, 2017 9:13 AM, "Anthony Chevalet" <anthony.cheva...@gmail.com>
> wrote:
Hello,
Any news on this? Bug report?
I have the same behavior for ages (katello 3.0?), and it's still there with
foreman 1.15.2/Katello 3.4.3.
Thanks,
Anthony
Le vendredi 31 mars 2017 22:41:46 UTC+2, Alan Evans a écrit :
>
> Hello,
>
> I am using Katello 3.3/Foreman 1.14.2. I have a fresh
Same issue with Katello 3.4.3-1.
GPG key was initially set, but after unset, it does not update the
redhat.repo (gpgcheck=1 remains)
I had to *delete the redhat.repo *file and run *subscription-manager
refresh* to correct it.
--
You received this message because you are subscribed to the
Bug created: Bug #20062: Host parameter not working in provisioning
template <http://projects.theforeman.org/issues/20062>
2017-06-20 14:57 GMT+02:00 Anthony Chevalet <anthony.cheva...@gmail.com>:
> ps: output of <%= @host.params %> does not show host params but only
&g
ps: output of <%= @host.params %> does not show host params but only params
from hostgroup, subnet, domain..
--
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
Hello,
I'm running Foreman 1.14 and have an issue with host parameters not
available in user_data template.
In the template I have:
<%= @host.params['myparam'] %>
On the host creation page, in the parameter tab, I add a host param
'myparam' with value 'test'.
Once created, the 'Preview'
11 matches
Mail list logo
