You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2012/11/14 14:08:11 UTC
[jira] [Created] (CLOUDSTACK-479) UpdateVirtualMachine api fails to
propagate userdata to domr
Rohit Yadav created CLOUDSTACK-479:
--------------------------------------
Summary: UpdateVirtualMachine api fails to propagate userdata to domr
Key: CLOUDSTACK-479
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-479
Project: CloudStack
Issue Type: Bug
Components: API
Affects Versions: 4.0.0
Reporter: Rohit Yadav
Assignee: Rohit Yadav
Fix For: 4.1.0
If we pass base64 encoded userdata to updateVirtualMachine api, it fails to propagate the decoded data on to its /var/www/html/userdata/<user-vm-ip>/user-data. This data can be useful while mass deploying vms that take conf. from domr, use cases can be chef/puppet controlled deployments etc.
On cloudmonkey cli, for some test vm id:
$ update virtualmachine id=903e3b3f-37e4-4263-ba26-ceb9f06da19f displayname="myvm 123" userdata=QSBxdWljayBicm93biBmb3gganVtcHMgb3ZlciBhIGxhenkgZG9nCg==
After successful execution, one should be able to GET the data from <domr-ip>/userdata/10.147.28.237/user-data which is the decoded data:
A quick brown fox jumps over a lazy dog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-479) UpdateVirtualMachine api fails to
propagate userdata to domr
Posted by "Rohit Yadav (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Yadav closed CLOUDSTACK-479.
----------------------------------
Closing as it's a duplicate issue.
> UpdateVirtualMachine api fails to propagate userdata to domr
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-479
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-479
> Project: CloudStack
> Issue Type: Bug
> Components: API
> Affects Versions: 4.0.0
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
>
> If we pass base64 encoded userdata to updateVirtualMachine api, it fails to propagate the decoded data on to its /var/www/html/userdata/<user-vm-ip>/user-data. This data can be useful while mass deploying vms that take conf. from domr, use cases can be chef/puppet controlled deployments etc.
> On cloudmonkey cli, for some test vm id:
> $ update virtualmachine id=903e3b3f-37e4-4263-ba26-ceb9f06da19f displayname="myvm 123" userdata=QSBxdWljayBicm93biBmb3gganVtcHMgb3ZlciBhIGxhenkgZG9nCg==
> After successful execution, one should be able to GET the data from <domr-ip>/userdata/10.147.28.237/user-data which is the decoded data:
> A quick brown fox jumps over a lazy dog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-479) UpdateVirtualMachine api fails
to propagate userdata to domr
Posted by "Rohit Yadav (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Yadav resolved CLOUDSTACK-479.
------------------------------------
Resolution: Duplicate
Duplicate of:
https://issues.apache.org/jira/browse/CLOUDSTACK-424
> UpdateVirtualMachine api fails to propagate userdata to domr
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-479
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-479
> Project: CloudStack
> Issue Type: Bug
> Components: API
> Affects Versions: 4.0.0
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
>
> If we pass base64 encoded userdata to updateVirtualMachine api, it fails to propagate the decoded data on to its /var/www/html/userdata/<user-vm-ip>/user-data. This data can be useful while mass deploying vms that take conf. from domr, use cases can be chef/puppet controlled deployments etc.
> On cloudmonkey cli, for some test vm id:
> $ update virtualmachine id=903e3b3f-37e4-4263-ba26-ceb9f06da19f displayname="myvm 123" userdata=QSBxdWljayBicm93biBmb3gganVtcHMgb3ZlciBhIGxhenkgZG9nCg==
> After successful execution, one should be able to GET the data from <domr-ip>/userdata/10.147.28.237/user-data which is the decoded data:
> A quick brown fox jumps over a lazy dog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira