Figured it out. I needed to use the template option "unsafe_writes: yes"
On Monday, July 29, 2019 at 4:29:22 PM UTC-4, Joe Langdon wrote:
>
> Hello,
>
> I am using an Ansible Role to copy a template file. It is not allowing me
> saying...... "The destination directory (/sys/module/nvme_core/parameters)
> is not writable by the current user"
>
>
> *Here is the execution of the play*
>
> [root@ip-172-29-100-198 roles]# *ansible-playbook -u root --ask-pass
> storage_timeout.yml*
> SSH password:
>
> PLAY [172.29.100.194]
> *********************************************************************************************************************************************************************************
>
> TASK [storage_timeout_aws : template]
> *****************************************************************************************************************************************************************
> An exception occurred during task execution. To see the full traceback,
> use -vvv. The error was: OSError: [Errno 2] No such file or directory:
> '/sys/module/nvme_core/parameters/.ansible_tmpxo2cR0io_timeout'
> fatal: [172.29.100.194]: FAILED! => {"changed": false, "checksum":
> "e431bd404db55f2205c3ae4074e3f6de2fb2eb71", "msg": "The destination
> directory (/sys/module/nvme_core/parameters) is not writable by the current
> user. Error was: [Errno 2] No such file or directory:
> '/sys/module/nvme_core/parameters/.ansible_tmpxo2cR0io_timeout'"}
>
>
>
> *Here is the template. Very simple *
>
> [root@ip-172-29-100-198 roles]#* cat
> storage_timeout_aws/templates/io_timeout*
> 255
>
> - The current value is 30
>
>
>
> *Here is the Task*
>
> [root@ip-172-29-100-198 roles]#* cat storage_timeout_aws/tasks/main.yml*
> ---
> # tasks file for /etc/ansible/roles/storage_timeout_aws
> # Works with just root folder
>
> - template:
> src: io_timeout
> dest: /sys/module/nvme_core/parameters/io_timeout
>
>
>
>
> Thoughts
>
> - Not sure it matters but this is to update NVME keep alive timeout.
> Sometimes Linux can't find EBS volume in AWS and the filesystem goes read
> only
> - I am logging in as root
> - I have also tried using "become: yes"
> - I AM able to write the io_timeout file directly to the /root directory
> with same credentials
> - I do have the path correct
>
> [root@elastic140 ~]# *cat /sys/module/nvme_core/parameters/io_timeout*
> 30
>
>
> I am not sure how to proceed at this point. I have close to 100 servers
> with this issue and it is causing some intermittent outages (apparently
> this is a known issue with AWS NVME) Thanks for your thoughts in advance
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/044dc461-95c4-45ab-999b-295c64730dcf%40googlegroups.com.
