-
Notifications
You must be signed in to change notification settings - Fork 34
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
DhcpServerOptionValue: DNS Option Fails due to no 'Force' attribute #56
Comments
Sorry to bug you, but I was just curious how hard it would be to implement this issue request. I would work on it, but I am not familiar enough with the setup of a DSC resource to know the best way to implement this. If either of you have time to look at this, I would be very grateful! :) |
I think you need to do this - rough list
Note that the helper updates all the *option* resources so you might need to make sure the new parameter work in all of those as well. If you have any problems along the way, then please ask away here. We are happy to help. |
This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close. |
I'm running into something similar on a fresh Azure 2016 server I'm using for testing.
Starts failing for all of the DHCPScopeOptionValues:
Repeat for option 6, option 15. |
I think the default action on this should to ALWAYS call force. If you are asserting a value with DSC server side validation should not be going on. Configuration should be applied as defined in config, even if it's wrong. |
Update CHANGELOG for resolution to issue dsccommunity#56
According to the documentation the Force parameter is only applicable when the DnsServer parameter is specified.
|
Has someone verified that adding |
I'm running into this same issue and would love to see the As the request here is for more information, I went in an tested the I also tested a DHCP configuration file on a server with the code changes mentioned with PR #78. This resulted in a successful update of the settings that were previously failing. Nothing new failed as a result of this either. Hope this helps with the needs more information tag. Happy to help some more if necessary. |
Details of the scenario you tried and the problem that is occurring
When using the DhcpServerOptionValue resource to install DNS servers for the whole DHCP server, it fails when the DNS servers are not resolvable.
Just as when installing DNS servers via the GUI, it checks for the IP addresses to be resolvable. But due to different test scenarios or other scenarios where the DNS servers wouldn't be accessible, it fails when it cannot resolve the IP's.
Verbose logs showing the problem
PowerShell Cmdlet failed: 10.1.1.1 is not a valid DNS server.
+ CategoryInfo : InvalidArgument: (ZADHCP003:) [], CimException
+ FullyQualifiedErrorId : WIN32 87,Set-DhcpServerv4OptionValue
+ PSComputerName : localhost
Suggested solution to the issue
Add an optional -Force setting to allow for forcing the setting when the option isn't valid at this time.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows Server 2016 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture : 64-bit
WindowsBuildLabEx : 14393.2665.amd64fre.rs1_release.181203-1755
OsLanguage : en-US
OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
PSVersion 5.1.14393.2636
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.2636
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used ('dev' if using current dev branch)
2.0.0.0
The text was updated successfully, but these errors were encountered: