I'm testing the 1.8.0 release and encountered my first bug, or anomaly.
I'd like confirmation that I'm not the only one before submitting a bug
report.
The problem: When I attempt to provision a "discovered" host using the
discovery 3.0 plugin and the 2.1 discovery image, and I select the host
group, the "Puppet CA" and "Puppet Master" fields do not auto-populate.
the Environment field however does auto-populate, so I'm not convinced its
a javascript or browser issue. I have double-checked my "host groups"
config and can confirm that these two fields are pre-filled.
Questions:
Is this now expected behavior on the discovery plugin?
if this is not expected behavior, please coach me on gathering logs and
to which bucket the issue should be submitted: Foreman? or Discovery?
Seems unexpected to me. Mattias Giese filed it against Discovery here,
I've just changed the status as it hasn't been followed up: http://projects.theforeman.org/issues/9784
/var/log/foreman/production.log may be useful from when you view the
form and change the host group.
···
On 28/04/15 19:47, lawre wrote:
> I'm testing the 1.8.0 release and encountered my first bug, or anomaly.
> I'd like confirmation that I'm not the only one before submitting a bug
> report.
>
> The problem: When I attempt to provision a "discovered" host using the
> discovery 3.0 plugin and the 2.1 discovery image, and I select the host
> group, the "Puppet CA" and "Puppet Master" fields do not auto-populate.
> the Environment field however does auto-populate, so I'm not convinced
> its a javascript or browser issue. I have double-checked my "host
> groups" config and can confirm that these two fields are pre-filled.
>
> Questions:
> 1. Is this now expected behavior on the discovery plugin?
>
> 2. if this is not expected behavior, please coach me on gathering logs
> and to which bucket the issue should be submitted: Foreman? or Discovery?
