[
https://issues.apache.org/jira/browse/JCLOUDS-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869663#comment-15869663
]
ASF subversion and git services commented on JCLOUDS-1239:
----------------------------------------------------------
Commit e26146c6c17c11200f7d186f01c76155423424b0 in jclouds's branch
refs/heads/master from [~felfert]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=e26146c ]
JCLOUDS-1239: Handle gzipped userdata in logging
> Gzipped userdata not handled in openstack-nova debug logging
> ------------------------------------------------------------
>
> Key: JCLOUDS-1239
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1239
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-compute
> Affects Versions: 2.0.0
> Reporter: Fritz Elfert
> Priority: Minor
> Labels: openstack-nova
>
> It is very common to gzip userdata on openstack to preserve space (when using
> cloud-init for example).
> If debug logging is enabled, then this binary data is shown as is which
> disrupts the log.
> Example output:
> {noformat}
> >> creating new server region(RegionOne) name(foo-f2e)
> >> image(41c50bca-cb94-4dc4-b4ce-6c98242eaaa6)
> >> flavor(08fbed24-7fcf-42e3-bc5a-cdd7a701ef0c)
> >> options(CreateServerOptions{keyName=null, securityGroupNames=[default],
> >> metadata={Name=foo, jclouds-group=foo}, userData=*lots of "garbage"*,
> >> networks=[73cbec8a-f53d-41af-843b-1cd4a6afc025], availabilityZone=null,
> >> configDrive=false})
> {noformat}
> See https://github.com/jclouds/jclouds/pull/1061 (master) and
> https://github.com/jclouds/jclouds/pull/1062 (2.0.x branch)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
