My template has two disks configured (C and D) in the template. When provisioning I look at the storage tab and I can see the 60GB listed as disk 0 which it should be. I have the option to add two additional disks which I did for testing purposes. Machine builds and I look in vCenter and find three drives however the request for Disk ID 1 was overwritten by the second disk in the template. If I create a blueprint with component profiles enabled I do not see the default Disk 0 at all. When I attempt to add additional disk it gets overwritten by Disk 0 in the template. I would like to adjust the disk number additional storage starts at to 3. This will leave Disk 0 and Disk 1 for the blueprint. Ive been asked to create a second template with three disks in so I also need to reserve Disk 2.
Can this be done?
It is showing as the D drive in Windows. This is a separate disk entirely.
I did try to add the C and D disks on the blueprint under storage however that doesn't work either. It actually causes more issues. The odd thing is that on some of my builds I manually create a new disk with PowerCLI, format and assign it a drive letter with no issue. The only time the BP's fail is if I try to add a disk as part of the request.
No, I meant if you have two vdisks in your template (volumes C and D), and you run a data collection, you should see two disk IDs (0 and 1) in your machine element before you even begin creating other disks. Are you seeing that or not?
Sorry for the confusion. I have two separate disks in the template. If I use component profiles I do not see any disks under the storage tab. If I use a basic BP then I only see C under storage.
It's working for me.
I added a new drive of 1 GB in size, converted back to a template, ran a full battery of data collections, and edited an existing blueprint to add a new vSphere machine component selecting this template. I can see the new drive with the proper ID show up. So you might want to try to create a new blueprint and see if your template that has two disks is actually showing both.
I did create a new BP and had the same issue. We are having another issue with the vSphere GUID. In June we did a lift and replace upgrade from vSphere 6.0 to 6.5. I added the new vSphere endpoint and eventually removed the old one once the migration was over. We still have the old vSphere GUID in the databases for some reason. VMW R&D is currently working on the issue and a fix. Since that is impacting parts of vRA I have to wonder if that might be part of the issue.
I started on VMFS and when we moved to 6.5 the templates were moved to vVol on flash storage. No issues so far. I'll go ahead and move it back to DFS and see if that makes any difference.
Removing the old vCenter seems to have helped quite a bit. I'm seeing the second disk and vRB looks like it is finally pumping out the right data. Once I get rid of this error I will know for sure.
Request [ced8f7a6-ff37-48fe-82ad-552bc1a6261e]: System exception.; HTTP/1.1 404 Not Found : <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="en-US">Resource not found for the segment 'VirtualMachineExts'.</m:message></m:error>