Comment 18 for bug 506332

We workarounded the issue in ec2-init by supporting both formats. The issue still stands in eucalyptus, but it's no longer blocking for us (so set to importance Low). It's more about other tools that might query the metadata service and could run into the same issue as we did. Even if it's not written into any EC2 spec, it's still something where Eucalyptus output differs from EC2's one.