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

xVMSwitch test fails if BandwidthReservationMode is not specified #48

Closed
iainbrighton opened this issue Feb 20, 2016 · 1 comment
Closed

Comments

@iainbrighton
Copy link
Contributor

In the latest release, if the BandwidthReservationMode is not specified, the Test method always fails. This appears to be due to the Get method returning the value, which by default (on a Win 10 host for me at least) actually happens to be 'Absolute' and not 'NA'.

PS C:\> Get-TargetResource -Name Internet -Type Internal -Verbose

Name                           Value
----                           -----
AllowManagementOS              True
BandwidthReservationMode       Absolute
Id                             71d7a9fb-a501-41a4-861d-199175b95bd8
Name                           Internet
Type                           Internal
Ensure                         Present
NetAdapterInterfaceDescription
NetAdapterName

PS C:\> Test-TargetResource -Name Internet -Type Internal -Verbose
VERBOSE: Checking if Switch Internet is Present ...
VERBOSE: Switch Internet is Present
VERBOSE: Checking if Switch Internet has correct BandwidthReservationMode ...
False

This might cause a few problems in production. I'll add a test and update the code...

iainbrighton added a commit to iainbrighton/xHyper-V that referenced this issue Feb 20, 2016
@TheBlackMini
Copy link

So, a little more light on this issue...
Windows 10 / Server 2016 default value is 'Absolute' for 'MinimumBandwidthMode'
Windows 8 & 8.1 / Server 2012 & R2 default value is 'Weight' for 'MinimumBandwidthMode'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants