Actions
Bug #52040
closedduring an apply the host must be online otherwise the apply fails with a traceback
Status:
Resolved
Priority:
Normal
Assignee:
Category:
cephadm/services
Target version:
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If a host is offline during an apply, the process stops with a traceback instead of continuing to the next host.
from a UX perspective, the exception should be caught cleanly and an event in the service generated so the admin can follow up with any issues.
Updated by Sebastian Wagner over 2 years ago
- Status changed from New to In Progress
- Assignee set to Daniel Pivonka
Updated by Daniel Pivonka over 2 years ago
more info: When deploying make sure your hosts are all online. If host listed is not reachable, you’ll get traceback like this, and the deployment will stop even if the next host to access is online and available
Adding ssh key to cs8-2 Non-zero exit code 1 from sudo -u root ssh-copy-id -f -i /etc/ceph/ceph.pub -o StrictHostKeyChecking=no root@cs8-2 sudo: stderr /bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/etc/ceph/ceph.pub" sudo: stderr ssh: connect to host cs8-2 port 22: No route to host Traceback (most recent call last): File "/usr/local/bin/cephadm", line 8230, in <module> main() File "/usr/local/bin/cephadm", line 8218, in main r = ctx.func(ctx) File "/usr/local/bin/cephadm", line 1759, in _default_image return func(ctx) File "/usr/local/bin/cephadm", line 4197, in command_bootstrap out, err, code = call_throws(ctx, ['sudo', '-u', ctx.ssh_user, 'ssh-copy-id', '-f', '-i', ssh_key, '-o StrictHostKeyChecking=no', '%s@%s' % (ctx.ssh_user, split[1])]) File "/usr/local/bin/cephadm", line 1453, in call_throws raise RuntimeError('Failed command: %s' % ' '.join(command)) RuntimeError: Failed command: sudo -u root ssh-copy-id -f -i /etc/ceph/ceph.pub -o StrictHostKeyChecking=no root@cs8-2
Updated by Daniel Pivonka over 2 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 42838
Updated by Sebastian Wagner over 2 years ago
- Status changed from Fix Under Review to Resolved
Actions