knife cluster kill --kill-bogus doesn't kill node_without_client as instructed

[temujin9]

If I

kc launch t9-simple

and

knife client delete t9-simple-0 -y

and then try to

kc kill t9-simple --yes --kill-bogus

I get

Inventorying servers in t9 cluster, simple facet, all servers
  t9:                   Loading chef
  t9:                   Loading ec2
  t9:                   Reconciling DSL and provider information
  +-------------+-------+---------+----------+------------+-------------+------------+---------------+---------------+------------+---------------------+-----------+
  | Name        | Chef? | State   | Flavor   | AZ         | Env         | MachineID  | Public IP     | Private IP    | Created On | Bogus               | relevant? |
  +-------------+-------+---------+----------+------------+-------------+------------+---------------+---------------+------------+---------------------+-----------+
  | t9-simple-0 | yes   | running | m1.small | us-east-1d | development | i-2b3d6a44 | 174.129.52.27 | 10.108.29.129 | 2013-04-16 | node_without_client | -         |
  +-------------+-------+---------+----------+------------+-------------+------------+---------------+---------------+------------+---------------------+-----------+
  Bogus servers detected: ["t9-simple-0"]

WARNING: No computers to kill

That instance should get selected and killed.

[moogoos]

Is there a workaround for this? I can't force launch either as it says:

WARNING: All computers are running -- not launching any.

I see no instances in my console either so this cluster, facet is stuck. Not sure how to clear it.

[temujin9]

knife node delete [nodename] -y; knife client delete [nodename] -y should clear the stale node and client information from the Chef server.

[moogoos]

I'll give this a go next time. I just deleted it manually from the chef server. Didn't know that was the reason for the odd state til I saw it in my node list. Learn something new each day. Love Ironfan.