Known issues

Contents

1. SSH Error: Host key verification failed
2. lookup plugin (task_src) not found

Known issues

This page lists all known issues that you might encounter while using DebOps. If you run into any errors, you should run the debops command again with -vvvv added at the end. It should look something like this:

$ debops -u root -vvvv

This'll make the output from DebOps more detailed. It's possible that you won't see the proper error message without it. So if you don't see the error mentioned here, make sure to try this first.

If you still don't see an explanation for your error here, please create an issue for it.

SSH Error: Host key verification failed

This error appears when a server you've connected to with SSH before has changed. It's often because you recreated the server and are trying to reconfigure it again. The issue is that recreating the server erases the SSH key saved on your computer. SSH doesn't like that.

To fix it, you'll need to remove the old key you'd saved on your computer. You can remove it using this command. You should replace wordpress.example.com with the address of your server in your hosts file.

$ ssh-keygen -R wordpress.example.com
# Host wordpress.example.com found: line 35 type RSA

You should run your DebOps command again afterwards. DebOps will ask you to confirm that you want to connect to the server once again.

PLAY [Gather default and custom facts] ****************************************

GATHERING FACTS ***************************************************************
The authenticity of host '123.456.78.90 (123.456.78.90)' can't be established.
RSA key fingerprint is 11:eb:57:f3:a5:c3:e0:77:47:c4:15:3a:3c:df:6c:d2.
Are you sure you want to continue connecting (yes/no)?

Type yes and Enter and everything should be working like before.

lookup plugin (task_src) not found

This error is due to an Ansible bug. It only appears for Mac OS X users. To solve it, you'll need to move your DebOps installation. Just follow the steps outlined below.

Create a symlink to your DebOps directory. This will allow DebOps to exist in two locations at once.

$ sudo ln -s ~/Library/Application\ Support/debops /usr/local/share/debops

Now that you've created a new location for DebOps, you'll need to point to it. That's done by setting the data-home variable to /usr/local/share/debops in your .debops.cfg. You can find your .debops.cfg at the root of your project.

# .debops.cfg

[paths]
data-home: /usr/local/share/debops

After that's done, you should no longer get this error.