dsccommunity / dsccommunity/NetworkingDsc
NetAdapterAdvancedProperty Constantly Re-Running
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 235
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Details of the scenario you tried and the problem that is occurring
I'm using puppet 7, to apply a dsc_netadapteradvancedproperty.
dsc_netadapteradvancedproperty{"Nic_V_IntraClusterManagement_Adv_Prop_FlowControl":
dsc_networkadaptername => 'V-IntraClusterManagement',
dsc_registrykeyword => '*FlowControl',
dsc_registryvalue => '3',
}
It keeps running over and over again saying that
Verbose logs showing the problem
Notice: /Stage[main]/Profiles::myprofile/Dsc_netadapteradvancedproperty[Nic_V_IntraClusterManagement_Adv_Prop_FlowControl]/dsc_registryvalue: dsc_registryvalue changed 'System.String[]' to '3'
Suggested solution to the issue
It seems to either not be passing the test-result back properly, or that it's in a wrong format. Does the module need to be fixed, or something with puppet's implementation?
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Not available
The operating system the target node is running
OsName : Microsoft Windows Server 2016 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture : 64-bit
WindowsBuildLabEx : 14393.4583.amd64fre.rs1_release.210730-1850
OsLanguage : en-US
OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
Name Value
---- -----
PSVersion 5.1.14393.4583
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.4583
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dsc_netadapteradvancedproperty resource and reproduce the Puppet 7 manifest on the stated Windows and PowerShell versions. Inspect the value returned during the test and compare the reported System.String[] with the configured 3; done means a second run is idempotent and no longer reports dsc_registryvalue as changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100