I'm experiencing a couple of issues with 1.4, recently upgraded from 1.2:
-
Provisioning templates seem to have multiple "versions". For example, I
have "server-1" and it uses "template-1". When I update "template-1" from
https://foreman-server/config_templates, the changes appear to save but
"server-1" still uses an older version of the template. I can confirm this
by going to the "server-1" host page, template tab, and clicking review
template. I see an older template. However, if I click edit "template-1"
from "server-1"'s host page, I can make changes and they save correctly and
the host uses the correct template. I'm thinking, that if the host already
exists its locked to the template which it was originally created with. I
don't remember this happening on 1.2 though.
-
All compute profiles show up regardless of which compute resource is
selected. I have compute profiles which are only configured for one
compute resource, yet I see them when I select a compute resource they
aren't configured for. This can confuse users since we have "production"
and "qa" compute profiles and they are only applicable to the production
and qa compute resources respectively. Is this working as intended?
I can provide logs if and submit bug tickets if necessary.
Thanks,
Dylan
> I'm experiencing a couple of issues with 1.4, recently upgraded from 1.2:
>
> 1) Provisioning templates seem to have multiple "versions". For
> example, I have "server-1" and it uses "template-1". When I update
> "template-1" from https://foreman-server/config_templates, the changes
> appear to save but "server-1" still uses an older version of the
> template. I can confirm this by going to the "server-1" host page,
> template tab, and clicking review template. I see an older template.
> However, if I click edit "template-1" from "server-1"'s host page, I can
> make changes and they save correctly and the host uses the correct
> template. I'm thinking, that if the host already exists its locked to
> the template which it was originally created with. I don't remember
> this happening on 1.2 though.
That's not meant to happen, and I can't think how it would. Can you
perhaps compare the URLs when you're editing the template via the
templates page and via the host page? The URL contains the database ID
of the template, so it's possible they're actually two different templates.
Open both edit links in new tabs and you should see something like:
https://foreman.example.com/config_templates/4-kickstart-default/edit
The "4" is the ID of that template.
> 2) All compute profiles show up regardless of which compute resource is
> selected. I have compute profiles which are only configured for one
> compute resource, yet I see them when I select a compute resource they
> aren't configured for. This can confuse users since we have
> "production" and "qa" compute profiles and they are only applicable to
> the production and qa compute resources respectively. Is this working
> as intended?
>
> I can provide logs if and submit bug tickets if necessary.
I think it's worth filing a bug or feature request for this one. The
code doesn't support filtering them at the moment when the compute
resource is selected, but it seems like a good idea to me.
···
On 05/03/14 20:00, Dylan Charleston wrote:
–
Dominic Cleal
Red Hat Engineering
