[
https://issues.apache.org/jira/browse/CLOUDSTACK-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan closed CLOUDSTACK-4484.
-------------------------------------------
Tested with latest build from 4.2-forward.
We are able to fetch user data successfully from guest Vms.
> Vmware - Not able to fetch userdata from guest Vms using
> http://<router-address>/latest/user-data
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4484
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0, 4.2.1
> Environment: Build from 4.2-forward
> Reporter: Sangeetha Hariharan
> Assignee: frank zhang
> Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> Not able to fetch userdata from guest Vms using
> http://<router-address>/latest/user-data
> Set up:
> Advanced zone set up with vmware host.
> Steps to reproduce the problem:
> Deploy Vm using user data.
> Vm deployment succeeds.
> From with in the guest Vm , try to access the user data using
> http://<router-address>/latest/user-data.
> [root@dd-1 ~]# wget http://10.1.1.1/latest/user-data
> --19:58:29-- http://10.1.1.1/latest/user-data
> Connecting to 10.1.1.1:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 19:58:29 ERROR 404: Not Found.
> [root@dd-1 ~]#
> On the router , we do not see /var/www/html/userdata/<guest ip address> file.
> In my case guest ip address is 10.1.1.45.
> Note- For all instances which were deployed with no userdata , i see
> /var/www/html/userdata/<guest ip address>/user-data which are empty. In case
> of Vms deployed with userdata , this file is not being created.
> deployVirtualMachine() api call used:
> 2013-08-23 15:26:07,078 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
> ===START=== 10.215.3.28 -- GET
> command=deployVirtualMachine&zoneId=93368e7c-db1b-4344-8777-2a6e0507c2ba&templateId=dd5c6bb5-602a-4cc4-9328-a26096294cf7&hypervisor=XenServer&serviceOfferingId=e83c2f9a-cbdc-46dc-8743-c76f3c270e99&networkIds=95528f66-22f8-4932-86b6-96b1183d5693&response=json&name=dd-1&displayName=dd-1&userdata=aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8=&apiKey=2aLe3o6TVY7286zbAJSCqbmhHlhaKU4at9HqUGbLoImE9SzR6Ys6tyWEbkCcDJDH-_Z5RlutsOYhMql2kixZpw&signature=s6Dvwr%2F8vEvqONyJKGmQKETcDVo%3D
> Management server log indicating that the user-data progarmming succeeds:
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-162:10.223.58.66) Use router's private IP for SSH control.
> IP : 10.223.58.70
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-162:10.223.58.66) Run vm_data command on domain router 10.2
> 23.58.70, data: routerIP
> 10.223.58.70
> vmIP
> 10.1.1.45
> userdata,user-data
> aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8
> metadata,service-offering
> tiny1
> metadata,availability-zone
> zone1
> metadata,local-ipv4
> 10.1.1.45
> metadata,local-hostname
> dd-1
> metadata,public-ipv4
> 10.223.138.68
> metadata,public-hostname
> 10.223.138.68
> metadata,instance-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,vm-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,public-keys
> none
> metadata,cloud-identifier
> CloudStack-{c9bcecaa-a61a-4192-9df2-4b7c8a9d1294}
> 2013-08-23 15:26:09,983 INFO [vmware.resource.VmwareResource]
> (DirectAgent-162:10.223.58.66) vm_data command on domain router 10.223.58.70
> completed
--
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
