[
https://issues.apache.org/jira/browse/CLOUDSTACK-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218008#comment-15218008
]
ASF GitHub Bot commented on CLOUDSTACK-9330:
--------------------------------------------
Github user hogniRunar commented on the pull request:
https://github.com/apache/cloudstack/pull/1456#issuecomment-203448721
To reproduce it you just need to set up a basic baremetal zone, start an
instance and on the bootserver for baremetal you can look at
/var/www/html/metadata/<IP of instance>/meta-data. As for testing I am not sure
what would be the best way other than looking at that same file once the fix
has been implemented.
Ticket:
https://issues.apache.org/jira/browse/CLOUDSTACK-9330
> Cloudstack creates a malformed meta-data file for baremetal instances
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-9330
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9330
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Baremetal
> Affects Versions: 4.2.0, 4.7.0
> Reporter: Hogni Ingimarsson
>
> When cloudstack creates the meta-data file for a baremetal instance it parses
> the filename wrong which results in a file looking like this
> root@baremetal-bootserver:~# cat /var/www/html/metadata/<IP>/meta-data
> s
> e
> r
> v
> i
> c
> -
> o
> f
> n
> g
> a
> l
> b
> t
> y
> z
> p
> 4
> h
> m
> u
> d
> k
> This is due to a bug located here:
> https://github.com/apache/cloudstack/blob/4.7/scripts/network/ping/baremetal_user_data.py#L96
> Where the function writeIfNotHere expects an array of strings and not just a
> single string.
> Github pull request: https://github.com/apache/cloudstack/pull/1456
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
