Closed dfmateus closed 1 year ago
yes that sounds like an issue with the reboot module, if you have Ansible support I would suggest opening a ticket. if not maybe create an issue in the ansible repo
how often do you see this issue?
how often do you see this issue?
This behavior started just a few days ago, I tried to switch to using ansible.builtin.command shutdown and then wait for connection with the ansible.builtin.wait_for_connection module but the same behavior happened.
How often are you seeing this issue? Every upgrade? 1 out of 10?
How often are you seeing this issue? Every upgrade? 1 out of 10?
It's happening to me every time it gets to the part where it reboots to complete the upgrade in the option RHEL-Upgrade-initramfs
I'm not sure if this is only happening to me. Anyway, I'm going to open a ticket with Red Hat to check if there is any problem with the reboot module.
I have run into this but only like 2% of the time so not sure why it is happening 100% of the time for you. are you running this CLI or on AAP? if CLI are you using navigator or Ansible-playbook? can you give me your ansible-core version or the EE you are using?
I'm running this directly from AAP using ansible-automation-platform-23/ee-supported-rhel8
@dfmateus Can you try using the reboot module and adding vars: ansible_ssh_args: "" as shown below?
ansible.builtin.reboot:
...
vars:
ansible_ssh_args: ""
Thanks!
@dfmateus Can you try using the reboot module and adding vars: ansible_ssh_args: "" as shown below?
ansible.builtin.reboot: ... vars: ansible_ssh_args: ""
Thanks!
Hello, I've made the test and the error happened as:
Failed to connect to the host via ssh: PTY allocation request failed on channel 0
Perhaps you are using other ansible_ssh_args that are needed? I was able to use that option in a lab environment.
Are you continuing to have this issue @dfmateus? What version of Ansible are you using?
Hello guys, thanks for all help, but I've found the issue is related to specific user, I've changed the user and works as expected.
In Task, it does not continue, it waits until the timeout, when I open a new terminal the server is active and operational, what could be happening, a problem with the reboot module?