8 Posts
0
535
March 2nd, 2021 13:00
Template deployment changed its logic in 3.5.0
Hi, we are having some issues with OME 3.5.0 and template deployments.
We have some configuration templates that we use to set the parameters we want about authentication, power settings, boot options and such, but we configured it to re-create the raid array when we execute this action. So we are using this for new servers and for repurposing the decommissioned ones.
For some reason in 3.5.0, after we do a deployment, those servers are greyed out and no longer are elegible for the template deployment.
We have seen that you introduced a new warning about production or no new servers should go through configuration compliance, but this will break the automations we already have.
Is this known? Is there any option to disable this failsafe measure?
Dell-DylanJ
4 Operator
•
2.9K Posts
0
March 3rd, 2021 12:00
Hello,
I think it changed in 3.4, but at any rate, under "Configuration," there is a section for templates and another for profiles. When a template is deployed it creates a profile and assigns it to a server, and additional templates cannot be deployed until they are removed from that profile. You might check these sections to see if this is the issue.
DELL-Joey C
Moderator
•
4.1K Posts
0
March 2nd, 2021 19:00
Hi,
Can you let me know more about how you use the template deployment, is it Page 67 : https://dell.to/2NWoT2D;
Do you have a screenshot of the mentioned warning?
gatoken
8 Posts
0
March 3rd, 2021 10:00
We have both types of templates, some of them created from model devices, and some others created from XML file. All of them worked fine until 3.3.1
Now when we select Deploy Template in 3.5.0, there is a warning message saying "For production devices, use the template compliance remediation workflow"
In the case of our test servers, when we try to deploy the template the servers are greyed out, and we cannot select them.
gatoken
8 Posts
0
March 4th, 2021 12:00
FInally!, as you say there are some profiles created, as soon as I unassigned those I was ready to deploy my templates again...
I am not happy about this feature, but I guess that we will need to adapt our automation tools for this...
Thanks for your time Dylan, you are a rockstar!