In the past this would usually occur when the restjavad daemon had
crashed on the box. Does this happen with other modules? Can you run
`bigstart restart restjavad` and try again? The other thing I can
think of is that in the process of taking the UCS file, the restjavad
daemon is restarting or crashing and this is resulting in an error
being bubbled up to the apache frontend and sent back to the module.
In this case the module should probably handle *some* of these cases,
but I wouldn't know without further looking.
Suggest that if the aforementioned does not help that you consider
opening an issue on the F5Networks/f5-ansible github repo
https://github.com/F5Networks/f5-ansible
My former colleague Wojciech, who maintains these modules today, may
be able to assist further.
-tim
> --
> You received this message because you are subscribed to the Google Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
ansible-proje...@googlegroups.com.
> To post to this group, send email to
ansible...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/fd88ade6-434c-4abf-80a2-edb4503bedf4%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.