cberger77
Enthusiast
Enthusiast

Instant clone : parent and replica not created after exit maintenance for updates

Jump to solution

I'm running vCenter 6.7 U3, and have 4 ESXi hosts also running 6.7.

These hosts are hosting horizon VMs, based on instant clone (Horizon 7.10).

To patch the first host, I put it in maintenance mode, the horizon VMs have been moved, and the parent & replica deleted.

After patching, the host rebooted, I left maintenance mode, but the parent & replica VMs are not created again 😕

Any idea ?

0 Kudos
1 Solution

Accepted Solutions
cberger77
Enthusiast
Enthusiast

Ok, so after digging the web, I finally found an explanation :

I found this KB : VMware Knowledge Base

It's about changing a custom attribute value : InstantClone.Maintenance

1 when going to maintenance, then it's automatically updated to 2.

And after have left the mnaintenance clear this value.

BTW it's not needed anymore in the recent versions.

As soon as the Pool will send a new VM creation, the parent VM will be created again.

View solution in original post

0 Kudos
2 Replies
cberger77
Enthusiast
Enthusiast

Ok, so after digging the web, I finally found an explanation :

I found this KB : VMware Knowledge Base

It's about changing a custom attribute value : InstantClone.Maintenance

1 when going to maintenance, then it's automatically updated to 2.

And after have left the mnaintenance clear this value.

BTW it's not needed anymore in the recent versions.

As soon as the Pool will send a new VM creation, the parent VM will be created again.

View solution in original post

0 Kudos
scott28tt
VMware Employee
VMware Employee

Moderator: Moved to Horizon


-------------------------------------------------------------------------------------------------------------------------------------------------------------
VMware Training & Certification blog
0 Kudos