`knife cluster sync` doesn't attach newly specified volumes

[fractaloop]

A machine that was launched without any ebs volumes will not attach new volumes on subsequent runs.

facet(:processing) do
  role                       :zookeeper_server
end

After launching the instance, add a volume to the definition and knife cluster sync

facet(:processing) do
  role                       :zookeeper_server

  volume(:zk) do
    size                16
    keep                true
    device              '/dev/sdf' # note: will appear as /dev/xvdf on modern ubuntus
    mount_point         '/data/zookeeper'
    attachable          :ebs
    snapshot_name       :blank_xfs
    resizable           true
    create_at_launch    true
    tags :zookeeper_data => false, :persistent => true, :local => false, :bulk => true, :fallback => false
  end
end

After the sync, run the Chef client on the instance and the new volume will not attach.

[mrflip]

I don't think(?) iron fan will make the volume for you, only recognize its existence and then specify its creation on launch. I would not be at all surprised to learn @temujin9 added that, though.

If you made the volume by hand you must tag it in the web console; ironfan will pick up from there.

[temujin9]

I think @mrflip is right, and that I was just forgetting that specific. Given my naive expectation (and Logan's), I strongly suspect we should add that capability.

[abhijith]

We had the same problem when we were trying Ironfan. We expected Ironfan to have the ability to add volumes after launch. Initially, we thought it was a bug but later figured out that this feature was not supported.

+1 for adding the feature in!