Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provider/vSphere: Fixes the hasBootableVmdk flag when attaching multiple disks #7804

Merged
merged 1 commit into from
Jul 26, 2016

Conversation

dkalleg
Copy link
Contributor

@dkalleg dkalleg commented Jul 25, 2016

The hasBootableFlag logic had a bug where it would only be set properly
if the bootable disk was the last specified. Adding some bool logic
resolves the issue. Also cleaning up a redundant var.

@dkalleg dkalleg force-pushed the hasBootableDiskFix branch 2 times, most recently from 104e803 to 49b4c18 Compare July 25, 2016 22:36
@dkalleg dkalleg changed the title Fixes the hasBootableVmdk flag when attaching multiple disks provider/vSphere Fixes the hasBootableVmdk flag when attaching multiple disks Jul 25, 2016
@dkalleg dkalleg changed the title provider/vSphere Fixes the hasBootableVmdk flag when attaching multiple disks provider/vSphere: Fixes the hasBootableVmdk flag when attaching multiple disks Jul 25, 2016
@@ -799,10 +798,10 @@ func resourceVSphereVirtualMachineCreate(d *schema.ResourceData, meta interface{
return fmt.Errorf("Cannot specify name of a template")
}
vm.template = v
if hasBootableDisk {
if vm.hasBootableVmdk {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this check include checking for multiple non-template disks with bootable?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

The hasBootableFlag logic had a bug where it would only be set properly
if the bootable disk was the last specified.  Adding some bool logic
resolves the issue.  Also adding check to ensure only one bootable disk
is given, and cleaning up a redundant var.
@dkalleg
Copy link
Contributor Author

dkalleg commented Jul 26, 2016

@stack72 Is there going to be an 0.7.0 rc4? If so, any idea when it might be created? If so, any chance this can make it in? This bug has some pretty bad effects on multiple disk vms.

@stack72
Copy link
Contributor

stack72 commented Jul 26, 2016

@dkalleg are we good with this one? Have you ran the tests?

P.

@dkalleg
Copy link
Contributor Author

dkalleg commented Jul 26, 2016

Hey @stack72, they're passing on my end. And I'm good calling this the final version, depending on any further comments.

@stack72
Copy link
Contributor

stack72 commented Jul 26, 2016

ok, I'm going to merge this - if possible, please drop the test results in so people can see them if they look :)

@stack72 stack72 merged commit 4b9b42d into hashicorp:master Jul 26, 2016
@dkalleg
Copy link
Contributor Author

dkalleg commented Jul 26, 2016

Thanks @stack72 !

@dkalleg dkalleg deleted the hasBootableDiskFix branch July 26, 2016 23:33
@ghost
Copy link

ghost commented Apr 24, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants