yahoo-eng-team team mailing list archive

[Wayne Witzel III <wayne.witzel@xxxxxxxxxxxxx>]

Public bug reported:

While implementing the GCE provider for Juju we found that the metadata
API breaks when trying to retrieve certain binary formats. In our case
the gz of user-data. The API only streams out the first 5 bytes,
encounters what it preceives as a EOF/nil character and truncates the
rest of the request.

We've opened an issue with Google directly, but in the meantime a work
around is to allow an explicit encoding to be set for the user-data
field of the GCE metadata. This will allow use to base64 encode the
binary blob, which the API returns the entire contents of without issue.

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Branch linked: lp:~wwitzel3/cloud-init/gce

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1404311

Title:
  gce metadata api doesn't properly stream binary data

Status in Init scripts for use on cloud images:
  New

Bug description:
  While implementing the GCE provider for Juju we found that the
  metadata API breaks when trying to retrieve certain binary formats. In
  our case the gz of user-data. The API only streams out the first 5
  bytes, encounters what it preceives as a EOF/nil character and
  truncates the rest of the request.

  We've opened an issue with Google directly, but in the meantime a work
  around is to allow an explicit encoding to be set for the user-data
  field of the GCE metadata. This will allow use to base64 encode the
  binary blob, which the API returns the entire contents of without
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1404311/+subscriptions