It's not a bug, resolvconf is just letting you know that it won't update the file as it's not a symlink, nothing wrong there.
I might agree that showing "Error" might be a bit excessive and that we might want to replace that by "Warning".
The problem, if we can consider it to be one is that one of the cloud image tools is replacing the /etc/resolv.conf symlink by a static file instead of updating /etc/network/interface with the DNS information. That's certainly allowed and is the right way of disabling resolvconf, but I don't think it's a good idea for the official Ubuntu images to do that, we should instead make sure the cloud scripts use the right resolvconf hook to provide their configuration.
It's not a bug, resolvconf is just letting you know that it won't update the file as it's not a symlink, nothing wrong there.
I might agree that showing "Error" might be a bit excessive and that we might want to replace that by "Warning".
The problem, if we can consider it to be one is that one of the cloud image tools is replacing the /etc/resolv.conf symlink by a static file instead of updating /etc/network/ interface with the DNS information. That's certainly allowed and is the right way of disabling resolvconf, but I don't think it's a good idea for the official Ubuntu images to do that, we should instead make sure the cloud scripts use the right resolvconf hook to provide their configuration.