# Property \_ansible\_selinux\_special\_fs in resource xADDomain is not a valid property **URL:** \ **Category:** Ansible Project\ **Created:** [May 18, 2016, 6:45am UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467 "2016-05-18T06:45:08Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Phyo\_Shwe](https://avatars.discourse-cdn.com/v4/letter/p/73ab20/32.png) [@Phyo\_Shwe](https://forum.ansible.com/u/Phyo_Shwe)\ **Post date:** [May 18, 2016, 6:45am UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/1 "2016-05-18T06:45:08Z")
Hi, I am testing out ansible win\_dsc module that Trond wrote. Everything worked great except when I start using the xActiveDirectory modules. I used Trond’s ansible module generator to get the modules. I didn’t get any error and I see all the modules exported. When I run the play book I get the error “Property \_ansible\_selinux\_special\_fs in resource xADDomain is not a valid property.” I searched around the web but couldn’t really find much about this error. Please help! `fatal: [10.255.10.20]: FAILED! => {"Attributes": ["DomainAdministratorCredential_password", "DomainAdministratorCredential_username", "DomainName", "DomainNetbiosName", "SafemodeAdministratorPassword_password", "SafemodeAdministratorPassword_username", "_ansible_check_mode", "_ansible_debug", "_ansible_diff", "_ansible_no_log", "_ansible_selinux_special_fs", "_ansible_syslog_facility", "_ansible_verbosity", "_ansible_version"], "DomainAdministratorCredential_password": "vagrant", "DomainAdministratorCredential_username": "vagrant", "DomainName": "dc01.testrealm.com", "DomainNetbiosName": "dc01", "SafemodeAdministratorPassword_password": "vagrant", "SafemodeAdministratorPassword_username": "vagrant", "changed": false, "failed": true, "invocation": {"module_name": "win_ad_xaddomain"}, "msg": "Property _ansible_selinux_special_fs in resource xADDomain is not a valid property", "resource_name": "xADDomain"} .` And here is my playbook ` ---
**Author:** ![Phyo\_Shwe](https://avatars.discourse-cdn.com/v4/letter/p/73ab20/32.png) [@Phyo\_Shwe](https://forum.ansible.com/u/Phyo_Shwe)\ **Post date:** [May 18, 2016, 9:45pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/2 "2016-05-18T21:45:47Z")
Turns out I was using the devel version of ansbile and that was causing the error. Now I am on Ansible 2.0.2 and get a new error. ` TASK [Init Domain] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* fatal: [10.255.10.20]: FAILED! =\> {“Attributes”: [“DomainAdministratorCredential\_password”, “DomainAdministratorCredential\_username”, “DomainName”, “DomainNetbiosName”, “SafemodeAdministratorPassword\_password”, “SafemodeAdministratorPassword\_username”, “\_ansible\_check\_mode”, “\_ansible\_debug”, “\_ansible\_diff”, “\_ansible\_no\_log”, “\_ansible\_verbosity”], “DomainAdministratorCredential\_password”: “vagrant”, “DomainAdministratorCredential\_username”: “vagrant”, “DomainName”: “[dc01.testrealm.com](http://dc01.testrealm.com)”, “DomainNetbiosName”: “dc01”, “SafemodeAdministratorPassword\_password”: “vagrant”, “SafemodeAdministratorPassword\_username”: “vagrant”, “changed”: false, “failed”: true, “msg”: “Property \_ansible\_debug in resource xADDomain is not a valid property”, “resource\_name”: “xADDomain”} ` Could it be that ansible is passing these attributes into the powershell modules but ps isn’t doing accepting it? Thanks Phyo ---
**Author:** ![Matt\_Davis](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@Matt\_Davis](https://forum.ansible.com/u/Matt_Davis)\ **Post date:** [May 18, 2016, 10:38pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/3 "2016-05-18T22:38:51Z")
Yeah, looks like those modules aren’t properly handling \_ansible\_X internal module args. ---
**Author:** ![Phyo\_Shwe](https://avatars.discourse-cdn.com/v4/letter/p/73ab20/32.png) [@Phyo\_Shwe](https://forum.ansible.com/u/Phyo_Shwe)\ **Post date:** [May 18, 2016, 11:47pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/4 "2016-05-18T23:47:05Z")
Yea I just read the win\_xaddomain.ps1 and found out why it’s causing the error. I think Trond win\_dsc5 module generator is expecting the keys and values of old ansible version and you guys added these new value or something and failing it. I comment out the line below and now the script just hanged. I am going to create an issue on the git instead. ` # Fail-Json -obj $result -message “Property $key in resource $dscresourcename is not a valid property” ` Thanks for the help again! ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [May 23, 2016, 11:16am UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/5 "2016-05-23T11:16:25Z")
Hmm, might be time for me to update the generator scripts. I’ll look into it and get back to you! ---
**Author:** ![Christoph\_Wegener](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Christoph\_Wegener](https://forum.ansible.com/u/Christoph_Wegener)\ **Post date:** [May 23, 2016, 12:44pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/6 "2016-05-23T12:44:29Z")
Dang! Perfect timing. I ran into the internal ansible variable handling issue in win\_dsc5 literally just now! (Trying to use ‘Group’ DSC resource in WMF5 with ansible ‘devel’ branch - msg: “Property \_ansible\_debug in resource Group is not a valid property” ) ---
**Author:** ![Christoph\_Wegener](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Christoph\_Wegener](https://forum.ansible.com/u/Christoph_Wegener)\ **Post date:** [May 23, 2016, 3:13pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/7 "2016-05-23T15:13:05Z")
Fixed in win\_dsc5: [https://github.com/trondhindenes/Ansible-win\_dsc/pull/6](https://github.com/trondhindenes/Ansible-win_dsc/pull/6) ---
**Author:** ![Phyo\_Shwe](https://avatars.discourse-cdn.com/v4/letter/p/73ab20/32.png) [@Phyo\_Shwe](https://forum.ansible.com/u/Phyo_Shwe)\ **Post date:** [May 23, 2016, 3:30pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/8 "2016-05-23T15:30:33Z")
Thanks so much. For now I just commented out line 70 in **powershell3\_dscparser.ps1** then generated the modules that I need. ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [May 23, 2016, 9:04pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/9 "2016-05-23T21:04:33Z")
Thanks Christoph, merged! As for the module generator, i’m fixing that now. ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [May 23, 2016, 10:14pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/10 "2016-05-23T22:14:00Z")
As for the AnsibleDscModuleGenerator, I’ve implemented a similar fix there (simply disregarding all options beginning with “\_ansible”. We’re probably gonna use the “check-mode” option later since we can do that natively with DSC, but for now this should work: [![](https://lh3.googleusercontent.com/-gS_20xtLytY/V0OAlxzk5rI/AAAAAAAAGAA/usW_25fX-ikJfDWxWLIs4hcU2xQe6u49ACLcB/s1600/2016-05-24%2B00_05_06-Cmder.png)](https://lh3.googleusercontent.com/-gS_20xtLytY/V0OAlxzk5rI/AAAAAAAAGAA/usW_25fX-ikJfDWxWLIs4hcU2xQe6u49ACLcB/s1600/2016-05-24%2B00_05_06-Cmder.png) ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [May 23, 2016, 10:16pm UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/11 "2016-05-23T22:16:07Z")
@Phyo, could you git pull and try again whenever you have a minute? While your method works I really want to retain the checking of options into the module (before the DSC parser gets them) just to be a good Ansible citizen. -Trond ---
**Author:** ![Phyo\_Shwe](https://avatars.discourse-cdn.com/v4/letter/p/73ab20/32.png) [@Phyo\_Shwe](https://forum.ansible.com/u/Phyo_Shwe)\ **Post date:** [May 24, 2016, 1:42am UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/12 "2016-05-24T01:42:03Z")
You are awesome!! Thanks so much. I just generated all the modules with your fix and ran my playbook. No more error now. ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [May 24, 2016, 10:22am UTC](https://forum.ansible.com/t/property-ansible-selinux-special-fs-in-resource-xaddomain-is-not-a-valid-property/21467/13 "2016-05-24T10:22:40Z")
Great! Glad to hear you got it working -Trond