Comment 7 for bug 1884071

Hey Scott,

Wow thanks so much for the many responses and looking closely into this. You are correct that it expects utf-8 for the string for user-data.

In my opinion, your first solution seems like the best path to take because it has no implications from provider to provider I imagine. I see no negatives in detecting the gzip data then extracting since if it isn't gzip data then it would just run same as before.

As for this:

> If you submit user-data to the API, and then cloud-init correctly
> gets the cloud-config-archive, then it should work.
>
> If you have submitted such data, please run 'cloud-init collect-logs' and
> attach the output.

When I tried with the "text/cloud-config-archive" MIME type it was the same exact error message as before because the only way I could submit it was with gzipped base64 due to how hetzner cloud allows one to submit the user-data.

I did open a ticket with hetzner to ask them how they handle it and maybe they will do something from their end, but I haven't gotten any solid response yet after giving them log data.

Either way, thanks so much for your hard work so far on this!