I can confirm that the hotpatch did not work on my home built Ansible appliance. For me, the offending key contained the string, 'root@tkldev-wheezy-amd64', which comes from the hostname of my build host. I chose to setup four vm's for tkldev so that I could build 32 & 64 bit iso's for both squeeze and wheezy. I changed the hostname from the default of 'tkldev' so that I could always tell which host I was working on.
Since you can't rely on always finding either 'fab-dev' or 'tkldev', the only test I can think of would be a mis-match between the key and the hostname. My other keys contain 'root@ansible' so they are presumably okay.
Information is free, knowledge is acquired, but wisdom is earned.
Confirmed
I can confirm that the hotpatch did not work on my home built Ansible appliance. For me, the offending key contained the string, 'root@tkldev-wheezy-amd64', which comes from the hostname of my build host. I chose to setup four vm's for tkldev so that I could build 32 & 64 bit iso's for both squeeze and wheezy. I changed the hostname from the default of 'tkldev' so that I could always tell which host I was working on.
Since you can't rely on always finding either 'fab-dev' or 'tkldev', the only test I can think of would be a mis-match between the key and the hostname. My other keys contain 'root@ansible' so they are presumably okay.
Information is free, knowledge is acquired, but wisdom is earned.