Unsolved
18 Posts
0
1846
November 19th, 2019 06:00
OMIVV system profile deployments reboots hosts without going to MM first
Hi!
We are using omivv5 with vcenter 6.7u3
I'm testing the system profile deployments / drift detection feature.
I've made my golden system profile, changed some settings for hosts to become 'uncompliant" and tried to remediate the drift.
When going to "deploy > system profile > golden profile" and following the wizard i'm able to successfully schedule a system-profile-remediation job and can see that it get's applied to the server ok.
Now i'm seeing some strange behavior. The hosts are already provisioned and in my vcenter server. When the system-profile-deploy job runs i can see that the host get's rebooted without going to maintenance mode first. This creates all sorts of issues for us, it triggers VMware-HA for VMs that where running on the hosts, effectively resetting them, it doesn't respect VSAN as multiple copies of components might become offline.
Does anyone in here have experience with this specific feature and can tell me their findings?, am i doing something wrong or am i hitting a bug?
Thanks,
Peter
I can 100% reproduce the issue
Dell-Vineeth
39 Posts
0
November 20th, 2019 03:00
Hi Peter,
If I understood your environment correctly from mentioned details, OMIVV is managing the hosts added to vCenter through created host credentials profile and iDRAC of same host is added as Bare Metal server. Correct me if I am wrong.
It is recommended to manage hosts either through host credentials profile or iDRAC of the host as Bare Metal Server, not both (Though adding iDRAC of managed host as bare metal is not blocked as of now).
OMIVV facilitate remediation for Firmware and Driver (for vSAN cluster) but not system profile (Hardware configuration).
System profile deploy job on iDRAC (Bare Metal Server) need a host reboot for successfully completion of the job and so the mentioned host reboot behavior is seen.
Thank You,
Vineeth
pbknl
18 Posts
0
November 20th, 2019 23:00
Hi Vineeth
Thanks for the quick reply!, i'm not sure if i understand this correctly.
So in a cluster-profile i'm able to select a system-profile.
Am i understanding you correct that your saying that the cluster-profile / system-profile integration only allows me to view the drift (compliance > configuration compliance > view drift), but there's currently no workflow in omivv that can remediate the drift while still respecting vmware. (Respecting like the firmware/driver update process)
And am i also understanding you correct that your saying i am able to fix the drift by leveraging the bare metal deployment workflows and applying the system-profile that way, but that the bm-deploy wizard is by design not respecting vmware boundaries?
Thanks,
Peter
Dell-Vineeth
39 Posts
0
November 21st, 2019 03:00
Hi Peter,
Yes, Currently no workflow in OMIVV that can remediate the cluster-profile / system-profile drift.
You are right, bare metal deployment workflows can be used to apply system-profile but that the bare metal-deploy wizard is by design is not aware of VMware boundaries.
Thank You,
Vineeth
pbknl
18 Posts
0
November 21st, 2019 05:00
Thanks for that, any idea if this is a feature on the roadmap of omivv? As the workflows for respecting vmware are already in place with firmware/driver updates this seems like a low-hanging fruit to develop.
Dell-Vineeth
39 Posts
0
December 2nd, 2019 20:00
Hi Peter,
Yes, this is part of feature list for future release. But release version this to be part is not frozen yet.
Thank You,
Vineeth