Fix incorrect assumption for bootstrap.iso path#1882
Fix incorrect assumption for bootstrap.iso path#1882caglar10ur merged 1 commit intovmware:masterfrom caglar10ur:iso
Conversation
The ISO path that's generated is based off the display name, not the actual VM folder path. This pr fixes that also removes the hardcoded appliance.iso file name. Fixes #1351 2nd time
|
Created #1883 for the integration test part |
|
LGTM |
|
| return nil, err | ||
| } | ||
| cdrom = devices.InsertIso(cdrom, fmt.Sprintf("[%s] %s/appliance.iso", conf.ImageStores[0].Host, d.vmPathName)) | ||
| cdrom = devices.InsertIso(cdrom, fmt.Sprintf("[%s] %s/%s", conf.ImageStores[0].Host, d.vmPathName, settings.ApplianceISO)) |
There was a problem hiding this comment.
Should we be using the actual path of the appliance VM rather than composing in this fashion. It'll currently work because we use ImageStores[0] as the applianceVM datastore, but if that ever changes then this will break.
There was a problem hiding this comment.
conf.ImageStores[0] used everywhere in the vic-machine code so will open a issue to address that if needed
|
LGTM other than future proofing. |
|
Caglar, this change is good. |
The ISO path that's generated is based off the display name, not the
actual VM folder path. This pr fixes that also removes the hardcoded
appliance.iso file name.
Fixes #1351 2nd time