Bug #36136
closed
"TypeError: string.split is not a function" when accessing ansible variables on a host
Added by Ron Lavi over 1 year ago.
Updated over 1 year ago.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2170727
Description of problem:
Checking Ansible variables on a host hit:
TypeError: string.split is not a function
in O
in a
in f
in div
in s
in t
in t
in f
in l
in d
in s
in d
in C
in t
in t
in t
in t
in d
in section
in PageSection
in M
in t
in t
in u
in f
in d
in div
in c
in p
in y
in t
in n
in a
in C
in s
in div
in b
in IntlProvider
in I18nProviderWrapper(b)
in d
in StoreProvider(I18nProviderWrapper(b))
in DataProvider(StoreProvider(I18nProviderWrapper(b)))
How reproducible:
Easy
Steps to Reproduce:
1. create a new Ansible variable with array type. Default value is ["test"]
2. enable both 'Merge Overrides' and 'Merge Default'
3. add the variable to a role
4. attach the role to a host
5. check the ansible variables on the host
Actual results:
TypeError: string.split is not a function, in O in a in f in div in s in t in t in f in l in d in
Expected results:
should no error
Additional info:
the error only happens when both 'Merge Overrides' and 'Merge Default' are on
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_ansible/pull/600 added
- Fixed in Releases foreman_ansible-11.1.0 added
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/foreman_ansible/pull/601 added
- Pull request https://github.com/theforeman/foreman_ansible/pull/602 added
- Fixed in Releases foreman_ansible-7.1.1 added
- Fixed in Releases foreman_ansible-10.0.0 added
- Subject changed from "TypeError: string.split is not a function" when accessing ansible variables on a host
to "TypeError: string.split is not a function" when accessing ansible variables on a host
- Fixed in Releases foreman_ansible-11.1.1 added
- Fixed in Releases deleted (
foreman_ansible-10.0.0, foreman_ansible-11.1.0, foreman_ansible-7.1.1)
- Fixed in Releases foreman_ansible-10.4.1, foreman_ansible-7.1.5 added
- Pull request https://github.com/theforeman/foreman_ansible/pull/635 added
- Pull request https://github.com/theforeman/foreman_ansible/pull/636 added
- Pull request https://github.com/theforeman/foreman_ansible/pull/641 added
- Pull request deleted (
https://github.com/theforeman/foreman_ansible/pull/636, https://github.com/theforeman/foreman_ansible/pull/635)
- Assignee changed from Ron Lavi to Nofar Alfassi
- Pull request deleted (
https://github.com/theforeman/foreman_ansible/pull/641)
- Pull request https://github.com/theforeman/foreman_ansible/pull/649 added
- Status changed from Closed to Ready For Testing
- Fixed in Releases foreman_ansible-12.0.5 added
- Status changed from Ready For Testing to Closed
- Fixed in Releases foreman_ansible-12.0.6 added
- Fixed in Releases deleted (
foreman_ansible-12.0.5)
- Pull request https://github.com/theforeman/foreman_ansible/pull/654 added
- Pull request https://github.com/theforeman/foreman_ansible/pull/655 added
- Fixed in Releases foreman_ansible-7.1.7 added
- Fixed in Releases foreman_ansible-7.1.8 added
- Fixed in Releases deleted (
foreman_ansible-7.1.5, foreman_ansible-7.1.7)
- Fixed in Releases foreman_ansible-10.0.0 added
- Fixed in Releases foreman_ansible-10.4.4 added
- Fixed in Releases deleted (
foreman_ansible-10.0.0, foreman_ansible-10.4.1)
Also available in: Atom
PDF