Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to set execute bit on remote files #146

Open
FatmanUK opened this issue Mar 4, 2024 · 11 comments
Open

Failed to set execute bit on remote files #146

FatmanUK opened this issue Mar 4, 2024 · 11 comments
Labels
high Urgent phase:bootstrap stale Neglected so long the issue went away triage Not immediately obvious what to label this why:mystery

Comments

@FatmanUK
Copy link
Owner

FatmanUK commented Mar 4, 2024

TASK [k3s_reboot_slow : Wait for all nodes to exist]
 ***************************
fatal: [k3s-mother-01]: FAILED! => {"msg": "Failed to
 set execute bit on remote files (rc: 1, err:
 mux_client_request_session: session request failed:
 Session open refused by peer\r\nWarning:
 Permanently added '10.11.0.1' (ECDSA) to the list
 of known hosts.\r\nControlSocket
 /home/fatman/.ansible/cp/9b11b6834e already
 exists, disabling multiplexing\r\nX11 forwarding
 request failed on channel 0\r\nserver exited
 unexpectedly\n)"}
@FatmanUK FatmanUK added bug Something isn't working site:home Observed at home site os:void Observed in Void Linux labels Mar 4, 2024
@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 4, 2024

[WARNING]: Error deleting remote temporary files
 (rc: 1, stderr: X11 forwarding

Related?

@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 4, 2024

fatal: [k3s-child-06 -> k3s-mother-01]:
 UNREACHABLE! => {"changed": false, "msg": "Failed
 to create temporary directory. In some cases, you
 may have been able to authenticate and did not
 have permissions on the target directory. Consider
 changing the remote tmp path in ansible.cfg to a
 path rooted in \"/tmp\", for more error information
 use -vvv. Failed command was: ( umask 77 &&
 mkdir -p \"` echo /tmp `\"&& mkdir \"` echo
 /tmp/ansible-tmp-1709590387.7094378-21535-2
5183337048722 `\" && echo ansible-
tmp-1709590387.7094378-21535-25183337048722=
\"` echo /tmp/ansible-tmp-1709590387.7094378-2153
5-25183337048722 `\" ), exited with result 1",
 "unreachable": true}

Related?

@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 4, 2024

fatal: [k3s-child-01 -> k3s-mother-01({{ network
 | ipv4(ip_fourth_byte) | ipv4("address") }})]:
 FAILED! => {"attempts": 60, "changed": true, "cmd":
 ["/usr/local/bin/kubectl", "get", "node",
 "k3s-child-01.dreamtrack.test"], "delta":
 "0:00:00.123127", "end": "2024-03-04 22:20:27.
834238", "msg": "non-zero return code", "rc": 1,
 "start": "2024-03-04 22:20:27.711111", "stderr":
 "Error from server (NotFound): nodes
 \"k3s-child-01.dreamtrack.test\" not found",
 "stderr_lines": ["Error from server (NotFound):
 nodes \"k3s-child-01.dreamtrack.test\" not
 found"], "stdout": "", "stdout_lines": []}

Related?

@athajaerel
Copy link
Collaborator

athajaerel commented Mar 5, 2024

TASK [k3s_reboot_slow : Wait for all nodes to exist]
 ******************************
fatal: [k3s-mother-02 -> k3s-mother-01]: UNREACHABLE!
 => {"changed": false, "msg": "Failed to create temporary
 directory. In some cases, you may have been able to
 authenticate and did not have permissions on the target directory.
 Consider changing the remote tmp path in ansible.cfg to a path
 rooted in \"/tmp\", for more error information use -vvv. Failed
 command was: ( umask 77 && mkdir -p \"` echo /tmp `\"&&
 mkdir \"` echo /tmp/ansible-tmp-1709631714.6867297-1921279
-155302194164978 `\" && echo ansible-tmp-1709631714.6867297
-1921279-155302194164978=\"` echo /tmp/ansible-tmp
-1709631714.6867297-1921279-155302194164978 `\" ), exited
 with result 1", "unreachable": true}

At work site. Interesting.

@athajaerel athajaerel added os:rhel Observed in Red Hat Enterprise Linux site:work Observed at work site high Urgent effect:stability:improve triage Not immediately obvious what to label this and removed bug Something isn't working labels Mar 5, 2024
@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 6, 2024

TASK [k3s_reboot_slow : Wait for all nodes to exist]
 ***************************
fatal: [k3s-child-03 -> k3s-mother-01]: FAILED! =>
 {"msg": "Failed to set execute bit on remote files
 (rc: 1, err: X11 forwarding request failed\r\nserver
 exited unexpectedly\n)"}
...
fatal: [k3s-child-04 -> k3s-mother-01]: FAILED! =>
 {"msg": "Failed to set execute bit on remote files
 (rc: 1, err: X11 forwarding request failed\r\nserver
 exited unexpectedly\n)"}

@FatmanUK FatmanUK added phase:bootstrap and removed os:rhel Observed in Red Hat Enterprise Linux os:void Observed in Void Linux effect:stability:improve labels Mar 6, 2024
@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 8, 2024

For tasks that wait or run for a long time without producing output, I found it necessary to add -o ServerAliveInterval=50 to ssh parameters to enable keepalives.

@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 8, 2024

pipelining

@FatmanUK
Copy link
Owner Author

FatmanUK commented Mar 8, 2024

Reboot task might be "racy": ostreedev/ostree#1548

@FatmanUK FatmanUK removed site:work Observed at work site site:home Observed at home site labels Mar 8, 2024
@athajaerel
Copy link
Collaborator

athajaerel commented Mar 11, 2024

Can't be the reboot module --- it's the "wait for nodes" task which is a command.

- name: 'Wait for all nodes to exist'
  register: 'reg_nodes'
  retries: 120
  delay: 20
  until: 'reg_nodes is success'
  delegate_to: '{{ groups.k3s_primary_masters | first }}'
  command:
    argv:
      - '{{ k3s_binary_dir }}/kubectl'
      - 'get'
      - 'node'
      - '{{ fqdn }}'

Would be fixed by #175 , most likely.

@athajaerel
Copy link
Collaborator

Not forgetting to fork off a ticket for the outputs which don't fit...

@athajaerel athajaerel added the stale Neglected so long the issue went away label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high Urgent phase:bootstrap stale Neglected so long the issue went away triage Not immediately obvious what to label this why:mystery
Projects
None yet
Development

No branches or pull requests

2 participants