Reply

Bug(?) in Ansible 2.8 with options in nios_fixed_address

Authority
Posts: 15
164     0

Hello,

 

I noticed some strange behavior in the nios_fixed_address module of Ansible 2.8.6

I try to create a fixed address and want to supply the host-name option. This is done with:

 

[snip]

- options:

  - name: host-name

    value: "the_hostname_I_want_to_set"

[snip]

 

Ansible fails with:

fatal: [localhost]: FAILED! => {"changed": false, "code": "Client.Ibap.Proto", "msg": "Option host-name can not have a use_option flag", "operation": "create_object", "type": "AdmConProtoError"} 

 

I did not set use_options at all!

And when I try to add "use_options" with either true or false or yes or no, this will produce the same error message.

The documentations say that use_option defaults to "yes". But when this is really the case this means that no options without "use_options" can be set. And this is a bug.

 

I also tried with "num: 12" instead of "name: host-name". This produces the same results.

 

Do you know a workaround? How can I set the host-name options with Ansible?

Who can fix this bug (if it is one) in Ansible?

 

Re: Bug(?) in Ansible 2.8 with options in nios_fixed_address

Authority
Posts: 15
165     0

I created an issue on github for this:

https://github.com/ansible/ansible/issues/64034

 

Showing results for 
Search instead for 
Do you mean 

Recommended for You