Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs #11346
-
|
Hello team, |
Beta Was this translation helpful? Give feedback.
Replies: 15 comments 1 reply
-
|
@alsko-icom , the logs are not visible. |
Beta Was this translation helpful? Give feedback.
-
|
cloudstack4.20.1.alsko.txt reuploaded file with txt extension. |
Beta Was this translation helpful? Give feedback.
-
|
it is now zero bytes, @alsko-icom . can you create a gist or use some other upload/ftp service? |
Beta Was this translation helpful? Give feedback.
-
|
added the file to my personal nextcloud server and as a gist too. and the nextcloud |
Beta Was this translation helpful? Give feedback.
-
|
@alsko-icom can you please confirm if the systemvm template has been registered / seeded? |
Beta Was this translation helpful? Give feedback.
-
|
@alsko-icom please checkt the template as @Pearl1594 suggests. Why do you think the mount of the nfs share is the problem? |
Beta Was this translation helpful? Give feedback.
-
|
pasting here screenshot of the seed command for your reference 
The team noticed some errors during deployment regarding NFS SR being unable to mount on the xcp-ng hosts. So if nfs mount failed, there was no way for the hosts to see the system vm template. |
Beta Was this translation helpful? Give feedback.
-
correct. |
Beta Was this translation helpful? Give feedback.
-
|
Excuse my late reply, somehow i missed the notification of your update! Is there a problem that we have all 4 xcp-ng hosts connecting to the nfs? Not sure how to tackle. The NFS is not seen to be provisioned / mounted to the entire server pool of 4 but just to 1 server. So if the mount tries to switch to another server, the new server does not know it. Maybe we should try another approach? Also, when adding servers to the xcp-ng server pool, should they be added to the pool through cloudstack by being previously standalone or is it ok to be already added to the pool through an XO environment and the cloudstack will accept them in? |
Beta Was this translation helpful? Give feedback.
-
|
No @alsko-icom , unless there are some setting on the nfs server preventing it, all servers should be able to share the NFS storage. |
Beta Was this translation helpful? Give feedback.
-
|
ok we will review the nfs behavior a bit more. Regarding the prep, should we add the xcp-ng hosts to the pool through cloudstack or through xen orchestrator at a lower level is fine and will not bother cloudstack? |
Beta Was this translation helpful? Give feedback.
-
|
@alsko-icom , I think you can add it to the pool and add the pool-master. please check though. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding the nfs storage it has been mounted on the xcp hosts 
and during the system vm deployment attempt I get an error Jul 28 15:35:51 hpe-xcp3 xapi: [error||5690380 |SR.probe D:31ab2dcc8c12|backtrace] sm_exec D:13bcbc145ea9 failed with exception Storage_error ([S(Backend_error);[S(SR_BACKEND_FAILURE_73);[S();S(NFS mount error [opterr=mount failed on server attaching the log file /var/log/xensource.log for 1 hour today between 15:00 and 15:59 as the deployment attempt was around 15:30. |
Beta Was this translation helpful? Give feedback.
-
|
@alsko-icom , what type of NFS server are you running and what options are turned on on it? (squash_root, nfs version, …?) |
Beta Was this translation helpful? Give feedback.
-
|
After going in the Netapp NFS configuration with the storage team to check settings you asked me, i witnessed them turning off the v4 and v4.1-4.2 support on the NFS share. So they left only v3 enabled. When enabling the zone in cloudstack, the system VMs where started successfully. There might be some issue with v4.x versions of it. So now it works! |
Beta Was this translation helpful? Give feedback.
-
|
I know there is a configuration option for nfs mounts, but would not know what is wrong in your case, glad it works now. |
Beta Was this translation helpful? Give feedback.
After going in the Netapp NFS configuration with the storage team to check settings you asked me, i witnessed them turning off the v4 and v4.1-4.2 support on the NFS share. So they left only v3 enabled. When enabling the zone in cloudstack, the system VMs where started successfully. There might be some issue with v4.x versions of it. So now it works!