GitHub user weizhouapache added a comment to the discussion: Ubuntu 20.04 Template Problem
> Well, iSCSI is definitely not comparable. > > ESXi build doesn't matter, i tried old ones, as well as last one 25067014. > > We have enterprise setup: HPE servers, Cisco SAN and FC storage from HPE > and/or DELL. This is reliable and trusted setup for many years with no issues > with some custom vibs, etc. I have same results on different storage devices. > > You have sporadic problem with accessing files during VM PowerOn. I have > problem with accessing file during template creation EVERY TIME i'm deploying > new template. This is not during power on. This is when you deploying first > instance from new ACS Template, ACS is calling VMware and creating multiple > VMware templates (c935dc91d4013091a603258617947536). During this process > there is multiple errors with accessing vmdk file, because is locked. That's > why I think there is a problem with corrupted filesystem. > > This should be fixed here: #12335 I wish i could test it. > > When i deploy instance from the same template on cluster with 8.0.0, there is > no such error and no filesystem corruption. @rastopato all these issues (image is corrupted, file is locked, power on failed, etc) appeared in VMware 8.0.1 we have put many efforts on the root cause diagnosis, but could not find . for the 2nd and 3rd issues, we added the retry mechanism which seems to reduce the impact. for the 1st issue, the root cause is still unknown. we have fixed the systemvm templates by "depmod -a". However, for existing user templates, we have no clue. GitHub link: https://github.com/apache/cloudstack/discussions/12610#discussioncomment-15760801 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
