[jira] [Updated] (CLOUDSTACK-3526) Upload Volumes state is displayed as UploadError with listVolumes when download is inprogress
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3526:
-
Attachment: listvol.png
management-server.log
apilog.log
> Upload Volumes state is displayed as UploadError with listVolumes when
> download is inprogress
> --
>
> Key: CLOUDSTACK-3526
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3526
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Storage Controller
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
> Fix For: 4.2.0
>
> Attachments: apilog.log, listvol.png, management-server.log
>
>
> Steps:
> 1. Configure Adv networking zone with Xen
> 2. Tried add new volume using upload volume.
> 3. Tried to get the state of the volume using listvolumes/UI
> Observation:
> 1. Upload Volumes state is displayed as UploadError with listVolumes when
> download is inprogress
> 2. DB state is uploadop for this volume and even the log says Download is in
> progress
> 3. It is incorrect state.
> mysql> select * from volumes where state='UploadOp'\G;
> *** 1. row ***
> id: 29
> account_id: 6
> domain_id: 1
>pool_id: NULL
> last_pool_id: NULL
>instance_id: NULL
> device_id: NULL
> name: uploadvol1
> uuid: 037c3c4e-5bc1-4574-b0d4-2d91b7d29ea8
> size: 0
> folder: NULL
> path: NULL
> pod_id: NULL
> data_center_id: 1
> iscsi_name: NULL
>host_ip: NULL
>volume_type: DATADISK
> pool_type: NULL
> disk_offering_id: 6
>template_id: NULL
> first_snapshot_backup_uuid: NULL
>recreatable: 0
>created: 2013-07-15 06:21:54
> attached: NULL
>updated: 2013-07-15 06:21:54
>removed: NULL
> state: UploadOp
> chain_info: NULL
> update_count: 1
> disk_type: NULL
> display_volume: 0
> format: VHD
> min_iops: NULL
> max_iops: NULL
> 037c3c4e-5bc1-4574-b0d4-2d91b7d29ea8uploadvol109fd14aa-070b-44ae-a643-486a66dfa289Zone-1DATADISK0UploadErrorsailaja17387d002-e9f5-11e2-9f70-fef34996d384ROOTsharedNonec60ed95b-5589-49a7-86a5-5d20196dd91fCustomCustom
>
> Diskfalsetruefalse
> 2013-07-15 12:12:27,314 DEBUG [agent.transport.Request]
> (DirectAgent-221:null) Seq 1-230817798: Processing: { Ans: , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
> }
> 2013-07-15 12:12:33,315 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-3:null) SeqA 3-43821: Processing Seq 3-43821: { Cmd ,
> MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-07-15 12:12:33,318 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-3:null) SeqA 3-43821: Sending Seq 3-43821: { Ans: ,
> MgmtId: 280320865129348, via: 3, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-07-15 12:12:41,014 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-07-15 12:12:41,019 DEBUG [agent.transport.Request] (Timer-8:null) Seq
> 2-1376587826: Sending { Cmd , MgmtId: 280320865129348, via: 2, Ver: v1,
> Flags: 100011,
> [{"org.apache.cloudstack.storage.command.DownloadProgressCommand":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","request":"GET_STATUS","hvm":false,"maxDownloadSizeInBytes":536870912000,"id":29,"resourceType":"VOLUME","installPath":"volumes/6/29","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/abhinav/xen42-sec","_role":"Image"}},"url":"http://10.147.28.7/templates/393d3550-05ef-330f-9b8c-745b0e699759.vhd","format":"VHD","accountId":6,"name":"uploadvol1","wait":0}}]
> }
> 2013-07-15 12:12:41,084 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 2-1376587826: Processing: { Ans: , MgmtId:
> 280320865129348, via: 2, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"a78618fb-4dc1-4015-8c8
[jira] [Created] (CLOUDSTACK-3527) UI dosent pop up the password new password when the restore VM(reset Vm incase of UI)is called.
Kiran Koneti created CLOUDSTACK-3527:
Summary: UI dosent pop up the password new password when the
restore VM(reset Vm incase of UI)is called.
Key: CLOUDSTACK-3527
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3527
Project: CloudStack
Issue Type: Sub-task
Security Level: Public (Anyone can view this level - this is the default.)
Components: UI
Reporter: Kiran Koneti
Priority: Critical
1)Created a VM using the IS volatile service offering and PasswordEnabled
template.
2)When the VM is created for the first time the Password is popped up in the UI.
3)Then when the VM is rebooted the new disk is created but the new password id
not popped up but we can see the password in the API response when the Firebug
is enabled.
Putting the firebug response
"{ "queryasyncjobresultresponse" :
{"accountid":"d33cb55e-e954-11e2-933a-06ecde18","userid":"d33d3a06-e954-11e2-933a-06ecde18","cmd":"org.apache.cloudstack.api.command.user.vm.RebootVMCmd","jobstatus":1,"jobprocstatus":0,"jobresultcode":0,"jobresulttype":"object","jobresult":{"virtualmachine":{"id":"22ef658d-5f05-40bc-83b5-aae804b2b06b","name":"IS1","displayname":"IS1","account":"admin","domainid":"a5196eba-e954-11e2-933a-06ecde18","domain":"ROOT","created":"2013-07-15T16:51:31+0530","state":"Running","haenable":false,"zoneid":"9259c481-337d-4ade-82c2-223183fd00fb","zonename":"Z1","hostid":"11060949-775c-4767-873c-e3c9ba9e48a9","hostname":"10.147.40.9","templateid":"433cea03-76a2-4d40-9a11-dc9151a04b1e","templatename":"Cetn53PWD","templatedisplaytext":"Cent53PWD","passwordenabled":true,"serviceofferingid":"57892b96-44e2-422a-a545-a7df7a0be53a","serviceofferingname":"ISvolatile","cpunumber":1,"cpuspeed":500,"memory":512,"cpuused":"23%","networkkbsread":0,"networkkbswrite":0,"diskkbsread":0,"diskkbswrite":0,"diskioread":0,"diskiowrite":0,"guestosid":"a53020ba-e954-11e2-933a-06ecde18","rootdeviceid":1,"rootdevicetype":"DATADISK","securitygroup":[],"password":"iF6pnzznb","nic":[{"id":"edeb81c8-df3c-4320-b85c-6138e8a5cd45","networkid":"f23e6e18-92b2-4b4a-abed-798dfadd0152","networkname":"def1","netmask":"255.255.255.0","gateway":"10.1.1.1","ipaddress":"10.1.1.10","isolationuri":"vlan://938","broadcasturi":"vlan://938","traffictype":"Guest","type":"Isolated","isdefault":true,"macaddress":"02:00:52:28:00:08"}],"hypervisor":"VMware","instancename":"i-2-29-VM","tags":[],"affinitygroup":[],"displayvm":true,"isdynamicallyscalable":false,"jobid":"e40d302b-cf70-46d1-8dcf-ea387fc3a11b","jobstatus":0}},"created":"2013-07-15T17:34:10+0530","jobid":"e40d302b-cf70-46d1-8dcf-ea387fc3a11b"}
}"
This should be popped up in the UI which will help the customer know the new
password.
--
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] [Updated] (CLOUDSTACK-3526) Upload Volumes state is displayed as UploadError with listVolumes when download is inprogress
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3526:
-
Fix Version/s: 4.2.0
> Upload Volumes state is displayed as UploadError with listVolumes when
> download is inprogress
> --
>
> Key: CLOUDSTACK-3526
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3526
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Storage Controller
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
> Fix For: 4.2.0
>
>
> Steps:
> 1. Configure Adv networking zone with Xen
> 2. Tried add new volume using upload volume.
> 3. Tried to get the state of the volume using listvolumes/UI
> Observation:
> 1. Upload Volumes state is displayed as UploadError with listVolumes when
> download is inprogress
> 2. DB state is uploadop for this volume and even the log says Download is in
> progress
> 3. It is incorrect state.
> mysql> select * from volumes where state='UploadOp'\G;
> *** 1. row ***
> id: 29
> account_id: 6
> domain_id: 1
>pool_id: NULL
> last_pool_id: NULL
>instance_id: NULL
> device_id: NULL
> name: uploadvol1
> uuid: 037c3c4e-5bc1-4574-b0d4-2d91b7d29ea8
> size: 0
> folder: NULL
> path: NULL
> pod_id: NULL
> data_center_id: 1
> iscsi_name: NULL
>host_ip: NULL
>volume_type: DATADISK
> pool_type: NULL
> disk_offering_id: 6
>template_id: NULL
> first_snapshot_backup_uuid: NULL
>recreatable: 0
>created: 2013-07-15 06:21:54
> attached: NULL
>updated: 2013-07-15 06:21:54
>removed: NULL
> state: UploadOp
> chain_info: NULL
> update_count: 1
> disk_type: NULL
> display_volume: 0
> format: VHD
> min_iops: NULL
> max_iops: NULL
> 2013-07-15 12:12:27,314 DEBUG [agent.transport.Request]
> (DirectAgent-221:null) Seq 1-230817798: Processing: { Ans: , MgmtId:
> 280320865129348, via: 1, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
> }
> 2013-07-15 12:12:33,315 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-3:null) SeqA 3-43821: Processing Seq 3-43821: { Cmd ,
> MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-07-15 12:12:33,318 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-3:null) SeqA 3-43821: Sending Seq 3-43821: { Ans: ,
> MgmtId: 280320865129348, via: 3, Ver: v1, Flags: 100010,
> [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
> 2013-07-15 12:12:41,014 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> 2013-07-15 12:12:41,019 DEBUG [agent.transport.Request] (Timer-8:null) Seq
> 2-1376587826: Sending { Cmd , MgmtId: 280320865129348, via: 2, Ver: v1,
> Flags: 100011,
> [{"org.apache.cloudstack.storage.command.DownloadProgressCommand":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","request":"GET_STATUS","hvm":false,"maxDownloadSizeInBytes":536870912000,"id":29,"resourceType":"VOLUME","installPath":"volumes/6/29","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/abhinav/xen42-sec","_role":"Image"}},"url":"http://10.147.28.7/templates/393d3550-05ef-330f-9b8c-745b0e699759.vhd","format":"VHD","accountId":6,"name":"uploadvol1","wait":0}}]
> }
> 2013-07-15 12:12:41,084 DEBUG [agent.transport.Request]
> (AgentManager-Handler-7:null) Seq 2-1376587826: Processing: { Ans: , MgmtId:
> 280320865129348, via: 2, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","downloadPct":52,"errorString":"
>
> ","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ff05d1cd-034d-3032-9adc-3d7451d838fb/volumes/6/29/dnld7207341898530326980tmp_","installPath":"volumes/6/29","templateSize":0,"templatePhySicalSize":0,"result":true,"details":"
> ","wait":0}}] }
> 2013-07-15 12:12:41,436 DEBUG [cloud.consoleproxy.Consol
[jira] [Updated] (CLOUDSTACK-3526) Upload Volumes state is displayed as UploadError with listVolumes when download is inprogress
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-3526:
-
Description:
Steps:
1. Configure Adv networking zone with Xen
2. Tried add new volume using upload volume.
3. Tried to get the state of the volume using listvolumes/UI
Observation:
1. Upload Volumes state is displayed as UploadError with listVolumes when
download is inprogress
2. DB state is uploadop for this volume and even the log says Download is in
progress
3. It is incorrect state.
mysql> select * from volumes where state='UploadOp'\G;
*** 1. row ***
id: 29
account_id: 6
domain_id: 1
pool_id: NULL
last_pool_id: NULL
instance_id: NULL
device_id: NULL
name: uploadvol1
uuid: 037c3c4e-5bc1-4574-b0d4-2d91b7d29ea8
size: 0
folder: NULL
path: NULL
pod_id: NULL
data_center_id: 1
iscsi_name: NULL
host_ip: NULL
volume_type: DATADISK
pool_type: NULL
disk_offering_id: 6
template_id: NULL
first_snapshot_backup_uuid: NULL
recreatable: 0
created: 2013-07-15 06:21:54
attached: NULL
updated: 2013-07-15 06:21:54
removed: NULL
state: UploadOp
chain_info: NULL
update_count: 1
disk_type: NULL
display_volume: 0
format: VHD
min_iops: NULL
max_iops: NULL
037c3c4e-5bc1-4574-b0d4-2d91b7d29ea8uploadvol109fd14aa-070b-44ae-a643-486a66dfa289Zone-1DATADISK0UploadErrorsailaja17387d002-e9f5-11e2-9f70-fef34996d384ROOTsharedNonec60ed95b-5589-49a7-86a5-5d20196dd91fCustomCustom
Diskfalsetruefalse
2013-07-15 12:12:27,314 DEBUG [agent.transport.Request] (DirectAgent-221:null)
Seq 1-230817798: Processing: { Ans: , MgmtId: 280320865129348, via: 1, Ver:
v1, Flags: 10,
[{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
}
2013-07-15 12:12:33,315 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-3:null) SeqA 3-43821: Processing Seq 3-43821: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2013-07-15 12:12:33,318 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-3:null) SeqA 3-43821: Sending Seq 3-43821: { Ans: ,
MgmtId: 280320865129348, via: 3, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2013-07-15 12:12:41,014 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-07-15 12:12:41,019 DEBUG [agent.transport.Request] (Timer-8:null) Seq
2-1376587826: Sending { Cmd , MgmtId: 280320865129348, via: 2, Ver: v1, Flags:
100011,
[{"org.apache.cloudstack.storage.command.DownloadProgressCommand":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","request":"GET_STATUS","hvm":false,"maxDownloadSizeInBytes":536870912000,"id":29,"resourceType":"VOLUME","installPath":"volumes/6/29","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/abhinav/xen42-sec","_role":"Image"}},"url":"http://10.147.28.7/templates/393d3550-05ef-330f-9b8c-745b0e699759.vhd","format":"VHD","accountId":6,"name":"uploadvol1","wait":0}}]
}
2013-07-15 12:12:41,084 DEBUG [agent.transport.Request]
(AgentManager-Handler-7:null) Seq 2-1376587826: Processing: { Ans: , MgmtId:
280320865129348, via: 2, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","downloadPct":52,"errorString":"
","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ff05d1cd-034d-3032-9adc-3d7451d838fb/volumes/6/29/dnld7207341898530326980tmp_","installPath":"volumes/6/29","templateSize":0,"templatePhySicalSize":0,"result":true,"details":"
","wait":0}}] }
2013-07-15 12:12:41,436 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-07-15 12:12:42,385 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 2 routers to update status.
2013-07-15 12:12:42,386 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-07-15 12:12:42,514 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 2 routers to update s
[jira] [Created] (CLOUDSTACK-3526) Upload Volumes state is displayed as UploadError with listVolumes when download is inprogress
Sailaja Mada created CLOUDSTACK-3526:
Summary: Upload Volumes state is displayed as UploadError with
listVolumes when download is inprogress
Key: CLOUDSTACK-3526
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3526
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API, Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Steps:
1. Configure Adv networking zone with Xen
2. Tried add new volume using upload volume.
3. Tried to get the state of the volume using listvolumes/UI
Observation:
1. Upload Volumes state is displayed as UploadError with listVolumes when
download is inprogress
2. DB state is uploadop for this volume and even the log says Download is in
progress
3. It is incorrect state.
mysql> select * from volumes where state='UploadOp'\G;
*** 1. row ***
id: 29
account_id: 6
domain_id: 1
pool_id: NULL
last_pool_id: NULL
instance_id: NULL
device_id: NULL
name: uploadvol1
uuid: 037c3c4e-5bc1-4574-b0d4-2d91b7d29ea8
size: 0
folder: NULL
path: NULL
pod_id: NULL
data_center_id: 1
iscsi_name: NULL
host_ip: NULL
volume_type: DATADISK
pool_type: NULL
disk_offering_id: 6
template_id: NULL
first_snapshot_backup_uuid: NULL
recreatable: 0
created: 2013-07-15 06:21:54
attached: NULL
updated: 2013-07-15 06:21:54
removed: NULL
state: UploadOp
chain_info: NULL
update_count: 1
disk_type: NULL
display_volume: 0
format: VHD
min_iops: NULL
max_iops: NULL
2013-07-15 12:12:27,314 DEBUG [agent.transport.Request] (DirectAgent-221:null)
Seq 1-230817798: Processing: { Ans: , MgmtId: 280320865129348, via: 1, Ver:
v1, Flags: 10,
[{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":1,"_newStates":{},"_isExecuted":false,"result":true,"wait":0}}]
}
2013-07-15 12:12:33,315 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-3:null) SeqA 3-43821: Processing Seq 3-43821: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2013-07-15 12:12:33,318 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-3:null) SeqA 3-43821: Sending Seq 3-43821: { Ans: ,
MgmtId: 280320865129348, via: 3, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2013-07-15 12:12:41,014 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-07-15 12:12:41,019 DEBUG [agent.transport.Request] (Timer-8:null) Seq
2-1376587826: Sending { Cmd , MgmtId: 280320865129348, via: 2, Ver: v1, Flags:
100011,
[{"org.apache.cloudstack.storage.command.DownloadProgressCommand":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","request":"GET_STATUS","hvm":false,"maxDownloadSizeInBytes":536870912000,"id":29,"resourceType":"VOLUME","installPath":"volumes/6/29","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/abhinav/xen42-sec","_role":"Image"}},"url":"http://10.147.28.7/templates/393d3550-05ef-330f-9b8c-745b0e699759.vhd","format":"VHD","accountId":6,"name":"uploadvol1","wait":0}}]
}
2013-07-15 12:12:41,084 DEBUG [agent.transport.Request]
(AgentManager-Handler-7:null) Seq 2-1376587826: Processing: { Ans: , MgmtId:
280320865129348, via: 2, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.storage.DownloadAnswer":{"jobId":"a78618fb-4dc1-4015-8c8a-0d1180a94c5c","downloadPct":52,"errorString":"
","downloadStatus":"DOWNLOAD_IN_PROGRESS","downloadPath":"/mnt/SecStorage/ff05d1cd-034d-3032-9adc-3d7451d838fb/volumes/6/29/dnld7207341898530326980tmp_","installPath":"volumes/6/29","templateSize":0,"templatePhySicalSize":0,"result":true,"details":"
","wait":0}}] }
2013-07-15 12:12:41,436 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-07-15 12:12:42,385 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 2 routers to update status.
2013-07-15 12:12:42,386 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-07-15 12:12:42,514 DEBUG
[network.rout
[jira] [Commented] (CLOUDSTACK-3497) The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708262#comment-13708262 ] ASF subversion and git services commented on CLOUDSTACK-3497: - Commit f1636203f7f5d90aa0e62540e216cf5be5b2c222 in branch refs/heads/4.2 from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f163620 ] CLOUDSTACK-3497: Updated the hypervisor_capabilities table to include capabilities for xenserver 6.2. Also made a change to update the capabilities for storage motion support based on hypervisor type and version. It was being done based on 'id'. > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > --- > > Key: CLOUDSTACK-3497 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3497 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, XenServer >Affects Versions: 4.2.0 > Environment: xenserver 6.2, CloudStack 4.2 >Reporter: Paul Angus >Assignee: Devdeep Singh > Labels: hypervisor, xenserver > Fix For: 4.2.0 > > > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > Specifically: > A request a request to find Storage Pools suitable for live migration results > in the following messages logged > DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===START=== 10.0.0.33 > -- GET > command=findStoragePoolsForMigration&id=fa1dc489-0414-4f91-9637-9fb05462f0e7&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373621024636 > ERROR [cloud.server.ManagementServerImpl] (catalina-exec-22:null) > Capabilities for host Host[-6-Routing] couldn't be retrieved. -- 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-3497) The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh resolved CLOUDSTACK-3497. --- Resolution: Fixed > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > --- > > Key: CLOUDSTACK-3497 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3497 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, XenServer >Affects Versions: 4.2.0 > Environment: xenserver 6.2, CloudStack 4.2 >Reporter: Paul Angus >Assignee: Devdeep Singh > Labels: hypervisor, xenserver > Fix For: 4.2.0 > > > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > Specifically: > A request a request to find Storage Pools suitable for live migration results > in the following messages logged > DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===START=== 10.0.0.33 > -- GET > command=findStoragePoolsForMigration&id=fa1dc489-0414-4f91-9637-9fb05462f0e7&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373621024636 > ERROR [cloud.server.ManagementServerImpl] (catalina-exec-22:null) > Capabilities for host Host[-6-Routing] couldn't be retrieved. -- 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] [Created] (CLOUDSTACK-3525) Documentation dosent point to the cloud-set-guest-password script link for Linux
Kiran Koneti created CLOUDSTACK-3525: Summary: Documentation dosent point to the cloud-set-guest-password script link for Linux Key: CLOUDSTACK-3525 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3525 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Kiran Koneti Fix For: 4.2.0 The Admin Guide for the Adding Password Management to Your Templates point a link for the cloud-set-guest-password script for Linux.When tried to click on the link it says oops cannot find the page. The link provided in the doc is http://cloudstack.org/dl/cloud-set-guest-password. Please update the correct Link which would help in downloading the script directly. -- 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] [Commented] (CLOUDSTACK-3497) The hypervisor_capabilities table needs to be updated to add capabilities for xenserver 6.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708260#comment-13708260 ] ASF subversion and git services commented on CLOUDSTACK-3497: - Commit 322bc9c5d73bccb79ee39922840fc1f01863384b in branch refs/heads/master from [~devdeep] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=322bc9c ] CLOUDSTACK-3497: Updated the hypervisor_capabilities table to include capabilities for xenserver 6.2. Also made a change to update the capabilities for storage motion support based on hypervisor type and version. It was being done based on 'id'. > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > --- > > Key: CLOUDSTACK-3497 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3497 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, Management Server, XenServer >Affects Versions: 4.2.0 > Environment: xenserver 6.2, CloudStack 4.2 >Reporter: Paul Angus >Assignee: Devdeep Singh > Labels: hypervisor, xenserver > Fix For: 4.2.0 > > > The hypervisor_capabilities table needs to be updated to add capabilities for > xenserver 6.2 > Specifically: > A request a request to find Storage Pools suitable for live migration results > in the following messages logged > DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===START=== 10.0.0.33 > -- GET > command=findStoragePoolsForMigration&id=fa1dc489-0414-4f91-9637-9fb05462f0e7&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373621024636 > ERROR [cloud.server.ManagementServerImpl] (catalina-exec-22:null) > Capabilities for host Host[-6-Routing] couldn't be retrieved. -- 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] [Assigned] (CLOUDSTACK-3473) Copy ISO is failing with CloudRuntimeException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3473:
--
Assignee: Koushik Das
> Copy ISO is failing with CloudRuntimeException
> ---
>
> Key: CLOUDSTACK-3473
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3473
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: ISO
>Affects Versions: 4.2.0
> Environment: 4.2 stable branch
>Reporter: manasaveloori
>Assignee: Koushik Das
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> Steps:
> 1.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS Host-Xen
> 2.Create advanced zone 1 with Primary-LocalStorage Secondary-NFS
> Host-VMware
> 3.Register ISO in zone 1 .
> 4.Copy the ISO to zone2.
> Observation:
> Copy ISO command is failing with following exception:
> 2013-07-11 21:14:27,164 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
> ===START=== 10.252.192.69 -- GET
> command=copyIso&id=80cbf735-48f9-407b-8406-dbc4a6f1e7bb&sourcezoneid=77ba1e4f-6940-4598-9736-0442e48bb622&destzoneid=47f59def-6265-49dc-bd68-8f7742fcad1d&response=json&sessionkey=keOxX86Woh7SzEYT5URKqFORYbM%3D&_=1373538013773
> 2013-07-11 21:14:27,205 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-14:null) submit async job-50, details: AsyncJobVO {id:50,
> userId: 2, accountId: 2, sessionKey: null, instanceType: Template,
> instanceId: 205, cmd: org.apache.cloudstack.api.command.user.iso.CopyIsoCmd,
> cmdOriginator: null, cmdInfo:
> {"response":"json","id":"80cbf735-48f9-407b-8406-dbc4a6f1e7bb","sessionkey":"keOxX86Woh7SzEYT5URKqFORYbM\u003d","destzoneid":"47f59def-6265-49dc-bd68-8f7742fcad1d","cmdEventType":"TEMPLATE.COPY","ctxUserId":"2","httpmethod":"GET","_":"1373538013773","ctxAccountId":"2","sourcezoneid":"77ba1e4f-6940-4598-9736-0442e48bb622","ctxStartEventId":"197"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 6805241462820,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-07-11 21:14:27,209 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null)
> ===END=== 10.252.192.69 -- GET
> command=copyIso&id=80cbf735-48f9-407b-8406-dbc4a6f1e7bb&sourcezoneid=77ba1e4f-6940-4598-9736-0442e48bb622&destzoneid=47f59def-6265-49dc-bd68-8f7742fcad1d&response=json&sessionkey=keOxX86Woh7SzEYT5URKqFORYbM%3D&_=1373538013773
> 2013-07-11 21:14:27,213 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-50:job-50) Executing
> org.apache.cloudstack.api.command.user.iso.CopyIsoCmd for job-50
> 2013-07-11 21:14:27,284 DEBUG [storage.motion.AncientDataMotionStrategy]
> (Job-Executor-50:job-50) copyAsync inspecting src type TEMPLATE copyAsync
> inspecting dest type TEMPLATE
> 2013-07-11 21:14:27,299 DEBUG [agent.transport.Request]
> (Job-Executor-50:job-50) Seq 6-20447500: Sending { Cmd , MgmtId:
> 6805241462820, via: 6, Ver: v1, Flags: 100111,
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/2/205/205-2-649b39cb-b33e-3924-86e9-dc3722c4dc62.iso","origUrl":"http://10.147.28.7/ISO/RHEL/rhel-6.0-install-CD.iso","uuid":"80cbf735-48f9-407b-8406-dbc4a6f1e7bb","id":205,"format":"ISO","accountId":2,"checksum":"5a9cee003ea44992762b7dbf1841caf7","hvm":true,"displayText":"rhelxen","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.147.28.7/export/home/manasa/secondaryxen","_role":"Image"}},"name":"205-2-649b39cb-b33e-3924-86e9-dc3722c4dc62"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/2/205","origUrl":"http://10.147.28.7/ISO/RHEL/rhel-6.0-install-CD.iso","uuid":"80cbf735-48f9-407b-8406-dbc4a6f1e7bb","id":205,"format":"ISO","accountId":2,"checksum":"5a9cee003ea44992762b7dbf1841caf7","hvm":true,"displayText":"rhelxen","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.147.28.7/export/home/manasa/secondaryVMw","_role":"Image"}},"name":"205-2-649b39cb-b33e-3924-86e9-dc3722c4dc62"}},"wait":10800}}]
> }
> 2013-07-11 21:14:27,633 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-3:null) SeqA 5-1273: Processing Seq 5-1273: { Cmd ,
> MgmtId: -1, via: 5, Ver: v1, Flags: 11,
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":7,"_loadInfo":"{\n
> \"connections\": []\n}","wait":0}}] }
> 2013-07-11 21:14:27,643 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-3:null) SeqA 5-1273: Sending Seq 5-1273: { Ans: ,
> MgmtId: 6805241462820, via: 5, Ver: v1, Flags: 100010,
> [{"com.cloud.age
[jira] [Assigned] (CLOUDSTACK-3445) Observing the system alerts "unallocated Local Storage is low in cluster" when Primary storage is Local Storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-3445: -- Assignee: Koushik Das > Observing the system alerts "unallocated Local Storage is low in cluster" > when Primary storage is Local Storage. > > > Key: CLOUDSTACK-3445 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3445 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: Latest Master build >Reporter: manasaveloori >Assignee: Koushik Das >Priority: Critical > Fix For: 4.2.0 > > Attachments: dashboard.jpg, management-server.zip, vmware.jpg, xen.jpg > > > Steps: > 1.Set the global setting "system.vm.use.local.storage" to true. > 2.Now while creating the advanced zone select "Local Storage > enabled:".(System VMs will launch in local storage). > 3.Make the setup complete. > Observation:(Xen and VMware) > Observing system alert System Alert: Remaining unallocated Local Storage is > low in cluster 10.147.60.15/manasa1/clusterVMw pod podVMw of availability > zone zoneVMware. > System Alert: Remaining unallocated Local Storage is low in cluster > clusterxen pod podxen of availability zone zonexen > But in Vcenter /xencenter Free space is still available under storage > Attached is the MS log and screen shots -- 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] [Assigned] (CLOUDSTACK-3435) Parallel deployment - Xenserver - When deploying 30 Vms in parallel, one of the Vms failed to get an ip address/hostname allocation.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3435:
--
Assignee: Jayapal Reddy
> Parallel deployment - Xenserver - When deploying 30 Vms in parallel, one of
> the Vms failed to get an ip address/hostname allocation.
>
>
> Key: CLOUDSTACK-3435
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3435
> 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
> Environment: Build from 4.2
>Reporter: Sangeetha Hariharan
>Assignee: Jayapal Reddy
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: xenparallel.rar
>
>
> Parallel deployment - Xenserver - When deploying 30 Vms in parallel, one of
> the Vms failed to get an ip address/hostname allocation.
> Steps to reproduce the problem:
> Advanced zone set up with Xenserver host.
> Deploy 30 Vms in parallel.
> Out of 30 vms , one of the Vms failed to get an ip address/hostname
> allocation.
> Vm-name = "hello-3" and id is "i-3-6".
> DhcpEntry and startCommand both seem to be succeed. But Vm is not assigned an
> ip address/host name.
> There is no entry for this Vm in the /etc/dhcphost.txt
> Management server log snippet when vm was deployed:
> 2013-07-09 16:29:30,734 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350322: Executing: { Cmd , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 100011, [{"com
> .cloud.agent.api.routing.DhcpEntryCommand":{"vmMac":"02:00:78:0b:00:03","vmIpAddress":"10.1.1.154","vmName":"hello-3","defaultRouter":"10.1.1.1","defaultDns":"10.1.1.1","duid":"00
> :03:00:01:02:00:78:0b:00:03","isDefault":true,"executeInSequence":false,"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.name":"r-4-VM","router
> .ip":"169.254.3.54"},"wait":0}}] }
> 2013-07-09 16:29:32,955 DEBUG [agent.transport.Request] (DirectAgent-42:null)
> Seq 1-729350322: Processing: { Ans: , MgmtId: 7200344900649, via: 1, Ver:
> v1, Flags: 10, [{"com.clou
> d.agent.api.Answer":{"result":true,"wait":0}}] }
> 2013-07-09 16:29:32,955 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350322: Received: { Ans: , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 10, { Answer } }
> 2013-07-09 16:30:09,920 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350375: Sending { Cmd , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 100011, [{"com.cl
> oud.agent.api.StartCommand":{"vm":{"id":6,"name":"i-3-6-VM","bootloader":"PyGrub","type":"User","cpus":1,"minSpeed":100,"maxSpeed":100,"minRam":262144000,"maxRam":262144000,"arch"
> :"x86_64","os":"CentOS 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"2be9ae733de747c7","pa
> rams":{"enable.dynamic.scaling":"false"},"uuid":"1457d848-3931-4c08-abd4-dea36c6ba1c7","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"d9e985f0-c218-4
> 8ff-ac6a-57979c3641e0","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"be66004e-e6d4-3312-8f15-283793aa26d2","id":1,"poolType":"Net
> workFilesystem","host":"10.223.110.232","path":"/export/home/sangeetha/xen/primary","port":2049}},"name":"ROOT-6","size":21474836480,"path":"63420079-fdce-4299-b4e9-549e35d89538",
> "volumeId":5,"vmName":"i-3-6-VM","accountId":3,"format":"VHD","id":5}},"diskSeq":0,"type":"ROOT"},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"IS
> O","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"71bb2293-8644-45c0-8708-975763bd8ed1","ip":"10.1.1.
> 154","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:78:0b:00:03","dns1":"72.52.126.11","dns2":"72.52.126.12","broadcastType":"Vlan","type":"Guest","broadcastUri":"vla
> n://2130","isolationUri":"vlan://2130","isSecurityGroupEnabled":false}]},"hostIp":"10.223.57.3","executeInSequence":false,"wait":0}}]
> }
> 2013-07-09 16:30:09,921 DEBUG [agent.transport.Request]
> (Job-Executor-14:job-14) Seq 1-729350375: Executing: { Cmd , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 100011, [{"com
> .cloud.agent.api.StartCommand":{"vm":{"id":6,"name":"i-3-6-VM","bootloader":"PyGrub","type":"User","cpus":1,"minSpeed":100,"maxSpeed":100,"minRam":262144000,"maxRam":262144000,"ar
> ch":"x86_64","os":"CentOS 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm"
[jira] [Assigned] (CLOUDSTACK-3424) IPV6 - When a Vm is expunged and a new Vm is deployed with the same name , /etc/dhchosts.txt has 2 entries with the same name.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-3424: -- Assignee: Jayapal Reddy > IPV6 - When a Vm is expunged and a new Vm is deployed with the same name , > /etc/dhchosts.txt has 2 entries with the same name. > -- > > Key: CLOUDSTACK-3424 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3424 > 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 > Environment: Build from master-6-17-stable >Reporter: Sangeetha Hariharan >Assignee: Jayapal Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log > > > IPV6 - When a Vm is expunged and a new Vm is deployed with the same name , > /etc/dhchosts.txt has 2 entries with the same name > Steps to reproduce the problem: > Create a ipv6 network. > Deploy a Vm with name - test456. > Destroy this VM. Wait for it to be expunged. > Deploy another Vm with same name - test456. > We see that there are 2 entries in the router with the same name "test456" > resolving to 2 different ipv6 addresses. > root@r-17-VM:~# cat /etc/dhcphosts.txt > id:00:03:00:01:06:4e:de:00:00:2f,[fc00:3:1370::744f],test123,infinite > id:00:03:00:01:06:75:46:00:00:31,[fc00:3:1370::34ed],test456,infinite > id:00:03:00:01:06:e4:ae:00:00:32,[fc00:3:1370::ae4b],testyoyo,infinite > id:00:03:00:01:06:96:aa:00:00:33,[fc00:3:1370::34ed],testyoyo1,infinite > id:00:03:00:01:06:cb:88:00:00:34,[fc00:3:1370::6eb2],test456,infinite > root@r-17-VM:~# > Attaching management server logs: > Have 2 entries for the same name is a problem. > Is it also a problem to have the same ipv6 address associated with 2 > different vms with different Vm names ( 1 expunged and 1 active , in my case > "test456" which is expunged and "testyoyo1" which is active) ? -- 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] [Assigned] (CLOUDSTACK-3009) [VPC][VMware]Unable to execute NetworkUsage command on DomR (10.147.40.181), domR may not be ready yet. failure due to Exception: java.lang.Exception—when VPC/VPC V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-3009: -- Assignee: Kishan Kavala > [VPC][VMware]Unable to execute NetworkUsage command on DomR (10.147.40.181), > domR may not be ready yet. failure due to Exception: java.lang.Exception—when > VPC/VPC VR is rebooted > - > > Key: CLOUDSTACK-3009 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3009 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 >Reporter: manasaveloori >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.zip > > > Steps: > 1.Have a CS with advanced zone and with VMware host. > 2.Create VPC . > 3.Create a private gateway and a static route to it. > 4.Reboot the VPC VR. > 5.After successful reboot of VR, now restart the VPC. >OR > After step 3 Restart the VPC and after successful restart, now reboot VR. > Observation: > Observed the following exception when VPC is restarted/VR is rebooted. > 2013-06-14 20:11:28,390 ERROR [vmware.resource.VmwareResource] > (DirectAgent-142:10.147.40.29) Unable to execute NetworkUsage command on DomR > (10.147.40.184), domR may not be ready yet. failure due to Exception: > java.lang.Exception > Message: vpc network usage get returns empty > java.lang.Exception: vpc network usage get returns empty > at > com.cloud.hypervisor.vmware.resource.VmwareResource.VPCNetworkUsage(VmwareResource.java:676) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:622) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:472) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-06-14 20:11:28,400 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-142:null) Seq 1-519307624: Response Received: > Attaching the MS log. -- 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] [Assigned] (CLOUDSTACK-2427) Host enable maintenance mode result in ErrorInMaintenance mode, guest VMs are not all migrated to other host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2427: -- Assignee: Koushik Das > Host enable maintenance mode result in ErrorInMaintenance mode, guest VMs are > not all migrated to other host > > > Key: CLOUDSTACK-2427 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2427 > 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 > Environment: MS ACS 4.2 pvlanbuild2 host XEN XS 6.1 >Reporter: angeline shen >Assignee: Koushik Das >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.log.gz > > > MS ACS 4.2 pvlanbuild2 host XEN XS 6.1 > 1. create advance zone, pvlan, 2 hosts. create network > 2. create guest VMs on host 1. host 2 has no guest VMs > 3. Put host1 in maintenance mode, which results in ErrorInMaintenance mode. >Only 1 guest VM was migrated to host 2. Second guest VM remained on host > 1. > 4. Put host2 in maintenance mode, which results in ErrorInMaintenance mode. > Guest VM on host 2 did not migrate to host 1. -- 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] [Assigned] (CLOUDSTACK-2990) After scaling up ,increased memory and cpu is not getting registered in guest OS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2990: -- Assignee: Harikrishna Patnala > After scaling up ,increased memory and cpu is not getting registered in > guest OS > --- > > Key: CLOUDSTACK-2990 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2990 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware >Affects Versions: 4.2.0 > Environment: Hypervisor Esxi 5.1 >Reporter: prashant kumar mishra >Assignee: Harikrishna Patnala >Priority: Critical > Fix For: 4.2.0 > > > Guest OS :"CentOS 5.3(64-bit) no GUI (vSphere)" Default template. > Steps to reproduce > - > 1-Deploy a vm with SO small ( RAM :512 MB,CPU 500MHz) > 2-Scale up to SO medium (RAM:1024MB,CPU 1000MHz) > Expected > -- > Guest OS should be able to use increased memory and cpu > Actual > --- > Guest OS still shows old( before scale up) memory and cpu values > My observation > --- > -On xen server increased memory and cpu is getting registered in Guest OS > after scale up -- 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] [Assigned] (CLOUDSTACK-3489) Failed to start VR due to error in finalizeStart with KVM hypervisor
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3489:
--
Assignee: Kishan Kavala
> Failed to start VR due to error in finalizeStart with KVM hypervisor
>
>
> Key: CLOUDSTACK-3489
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3489
> 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
> Environment: Latest build from ACS 4.2 branch.
> Zone: Advanced with KVM cluster
> Stoarage: S3 and Local storage
>Reporter: Sanjeev N
>Assignee: Kishan Kavala
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> Failed to start VR due to error in finalizeStart with KVM hypervisor:
> KVM routing template being used:
> systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2
> Steps to Reproduce:
>
> 1.Bring up CS in advanced zone with KVM cluster
> 2.Use s3 as the secondary storage and Local storage as the primary storage
> 3.Use default cent os template to deploy guest vm
> Observations:
> ===
> VR was started as part of vm deployment process and it remained in starting
> state for a while. However later it was stopped with following exceptions:
> com.cloud.exception.AgentUnavailableException: Resource [Host:4] is
> unreachable: Host 4: Unable to start instance due to Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:944)
> at
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3124)
> at
> com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouter(VirtualNetworkApplianceManagerImpl.java:3074)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.admin.router.StartRouterCmd.execute(StartRouterCmd.java:110)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: com.cloud.utils.exception.ExecutionException: Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:911)
> ... 19 more
> 2013-07-12 02:38:24,430 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-8:job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ]) Complete
> async job-32 = [ c1b6d349-4797-484e-a2e0-dfacce3c6209 ], jobStatus: 2,
> resultCode: 530, result: Error Code: 530 Error text: Resource [Host:4] is
> unreachable: Host 4: Unable to start instance due to Unable to start
> VM[DomainRouter|r-13-VM] due to error in finalizeStart, not retrying
> Few more log snippets from mgmt server log file:
> 2013-07-12 02:36:21,128 DEBUG [agent.transport.Request]
> (AgentManager-Handler-4:null) Seq 4-691668978: Processing: { Ans: , MgmtId:
> 6615759585382, via: 4, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":13,"name":"r-13-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
> GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP name=r-13-VM
> eth2ip=10.147.48.5 eth2mask=255.255.255.0 gateway=10.147.48.1 eth0ip=10.1.1.1
> eth0mask=255.255.255.0 domain=cs2cloud.internal dhcprange=10.1.1.1
> eth1ip=169.254.1.161 eth1mask=255.255.0.0 type=router disable_rp_filter=true
> dns1=10.103.128.16","rebootOnCrash":false,"enableHA":true,"limitCpuUse":false,"enableDyna
[jira] [Assigned] (CLOUDSTACK-3513) [Automation] Failed to copy iso and template between zones
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-3513:
--
Assignee: Jayapal Reddy
> [Automation] Failed to copy iso and template between zones
> --
>
> Key: CLOUDSTACK-3513
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3513
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation, ISO, Template
>Affects Versions: 4.2.0
> Environment: 4.2
> Automation
>Reporter: Rayees Namathponnan
>Assignee: Jayapal Reddy
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-3513.rar
>
>
> bvt test cases failed
> 1) integration.smoke.test_templates.TestTemplates.test_06_copy_template
> 2) integration.smoke.test_iso.TestISO.test_06_copy_iso
> Steps to reproduce
> 1) Register ISO
> 2) copy ISO to another zone
> 3) iso not getting copied to second zone,
> i didnt observe any error in ms log, please see the attached log.
> Job 220
> i didnt see any response (job 220) even after 5 minute
> 2013-07-13 02:52:00,982 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ])
> Executing org.apache.cloudstack.api.command.user.iso.Cop
> yIsoCmd for job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]
> 2013-07-13 02:52:00,985 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-9:null) submit async job-220 = [
> ccea3738-731d-4745-bdd0-5d81bbf126b6 ], details: AsyncJobVO {id:220, userId: 2
> , accountId: 2, sessionKey: null, instanceType: Template, instanceId: 209,
> cmd: org.apache.cloudstack.api.command.user.iso.CopyIsoCmd, cmdOriginator:
> null, cmdInfo: {"id":"b1106f0c-d183-4c75
> -99ae-02993d3a91c7","response":"json","sessionkey":"blwF0jxkh/BXBlAaOW4fzjITizc\u003d","destzoneid":"cfd13d3f-38dd-4ccf-baea-dc5d859dbdea","cmdEventType":"TEMPLATE.COPY","ctxUserId":"2","htt
> pmethod":"GET","_":"1373698373159","ctxAccountId":"2","sourcezoneid":"b76325a6-71dc-486d-98cd-346ea1c3a511","ctxStartEventId":"915"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, s
> tatus: 0, processStatus: 0, resultCode: 0, result: null, initMsid:
> 29066118877352, completeMsid: null, lastUpdated: null, lastPolled: null,
> created: null}
> 2013-07-13 02:52:00,988 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
> ===END=== 10.216.51.171 -- GET
> command=copyIso&id=b1106f0c-d183-4c75-99ae-02993d3a91c7&sourcezoneid=b76325a6-71d
> c-486d-98cd-346ea1c3a511&destzoneid=cfd13d3f-38dd-4ccf-baea-dc5d859dbdea&response=json&sessionkey=blwF0jxkh%2FBXBlAaOW4fzjITizc%3D&_=1373698373159
> 2013-07-13 02:52:01,010 DEBUG [storage.image.TemplateDataFactoryImpl]
> (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ])
> template 209 is not in store:2, type:Image
> 2013-07-13 02:52:01,035 DEBUG [agent.transport.Request]
> (Job-Executor-108:job-220 = [ ccea3738-731d-4745-bdd0-5d81bbf126b6 ]) Seq
> 10-544932010: Sending { Cmd , MgmtId: 29066118877352, via: 10, Ver: v1,
> Flags: 100011,
> [{"org.apache.cloudstack.storage.command.DownloadCommand":{"hvm":true,"description":"test","checksum":"b11099d68763f87ee90eab7af1d4dd1e","maxDownloadSizeInBytes":53687091200,"id":209,"resourceType":"TEMPLATE","installPath":"template/tmpl/2/209","_store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary3","_role":"Image"}},"url":"http://people.apache.org/~tsp/dummy.iso","format":"ISO","accountId":2,"name":"209-2-f327a840-fc0b-3784-b292-b04cf483c01e","secUrl":"nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary3","wait":0}}]
> }
--
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] [Updated] (CLOUDSTACK-3524) NPE while trying to start the router which is in stopped state while creating volume with ZWPS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3524: - Fix Version/s: 4.2.0 > NPE while trying to start the router which is in stopped state while creating > volume with ZWPS > -- > > Key: CLOUDSTACK-3524 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3524 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Priority: Critical > Fix For: 4.2.0 > > > Steps: > 1. Configure Advanced networking zone with VMWARE with Zone wide primary > storage > 2. Tried to start a Router which is in stopped state. > Observation: > NPE while trying to start the router which is in stopped state > 2013-07-15 10:51:32,703 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Checking > if we need to prepare 1 volumes for VM[DomainRouter|r-4-VM] > 2013-07-15 10:51:32,705 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Volume > Vol[14|vm=4|ROOT] will be recreated on storage pool Pool[1|NetworkFilesystem] > assigned by deploymentPlanner > 2013-07-15 10:51:32,717 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Created > new volume Vol[15|vm=4|ROOT] for old volume Vol[14|vm=4|ROOT] > 2013-07-15 10:51:32,799 DEBUG [storage.motion.AncientDataMotionStrategy] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) copyAsync > inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME > 2013-07-15 10:51:32,806 DEBUG [storage.motion.AncientDataMotionStrategy] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Failed to > send to storage pool > java.lang.NullPointerException > at > org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.cloneVolume(AncientDataMotionStrategy.java:264) > at > org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:343) > at > org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromBaseImageAsync(VolumeServiceImpl.java:457) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:494) > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2485) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2542) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:851) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1967) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1945) > at > com.cloud.network.element.VirtualRouterElement.implement(VirtualRouterElement.java:203) > at > com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1964) > at > com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1869) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2046) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:849) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3327) > at > com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmMan
[jira] [Assigned] (CLOUDSTACK-2168) configured LDAP values not shown in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-2168:
--
Assignee: Harikrishna Patnala (was: Abhinandan Prateek)
> configured LDAP values not shown in UI
> --
>
> Key: CLOUDSTACK-2168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2168
> 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
>Reporter: sadhu suresh
>Assignee: Harikrishna Patnala
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloudstack-2168.patch, screenshot_ldap.jpg
>
>
> Steps:
> 1.Configured the LDAP through API
> http://10.147.59.83:8096/client/api?command=ldapConfig&hostname=10.147.38.163&searchbase=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcom&queryfilter=%28%26%28mail%3D%25e%29%29&port=389&response=json
> 2.Open the CS web console and navigate to LDAP configuration section
> 3.check the displayed LDAP configured values
> Actual result:
> Even though LDAP configuration happens successfully but UI fail to display
> the Values.
> even firebug response shows the configured ldap values but UI fail to display
> the values.
> UI:
> ---
> Hostname Query FilterSearch Base LDAP Port SSL
> Quickview
> No data to show
> firebug response:
>
> http://10.147.59.83:8080/client/api?command=ldapConfig&listall=true&response=json&sessionkey=2G5uy2a4z%2F31Mi3yaVKmvXc10a4%3D&listAll=true&page=1&pagesize=20&_=1366791925255
> { "ldapconfigresponse" : { "ldapconfig" :
> {"hostname":"10.147.38.163","port":"389","ssl":"false","searchbase":"CN=Users,DC=hyd-qa,DC=com","queryfilter":"(&(mail=%e))","binddn":""}
> } }
--
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] [Updated] (CLOUDSTACK-3482) primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and try to detach volume when VM is running state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sadhu suresh updated CLOUDSTACK-3482:
-
Fix Version/s: 4.2.0
> primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and
> try to detach volume when VM is running state
> ---
>
> Key: CLOUDSTACK-3482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.rar
>
>
> detachvolume is failed when we attach voulme on stopped vm and try to detach
> volume when VM is running state
> steps:
> 1. deploy a vm1
> 2. perform snapshot on root volume
> 3.create a volume from snapshot i,e vol1
> 4.deploy another vm2
> 5.attach/detach a volume created in step3
> 6 volume was successfully attached and detach and then .stop the vm2
> 7.attach the volume "vol1" to vm2
> 8.start the VM2
> 9 try to detach "vol1" from vm2
> Actual result:
> fail to detach the volume from vm and throws below error when we first try to
> detach the volume.
> and later if we try to detach volume again and its failing with "failed
> dettach volume: 960eba57-279b-48a6-b94d-44ef75fe134b, due to
> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed
> out"
> ** 49. row ***
> id: 67
>user_id: 2
> account_id: 2
>session_key: NULL
> instance_type: NULL
>instance_id: NULL
>job_cmd:
> org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
> job_cmd_originator: NULL
> job_cmd_info:
> {"response":"json","id":"dbf2306a-91e9-4980-b773-eac0523ef290","sessionkey":"MHeSvVY9VxbxczPiN/S443FWzw0\u003d","cmdEventType":"VOLUME.DETACH","ctxUserId":"2","httpmethod":"GET","_":"1373548167660","ctxAccountId":"2","ctxStartEventId":"261"}
>job_cmd_ver: 0
> callback_type: 0
> callback_address: NULL
> job_status: 2
> job_process_status: 0
>job_result_code: 530
> job_result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to detach volume: xx from VM: vm3; Failed dettach volume:
> 6a5d2542-2333-4855-bd87-675c7ead26b5, due to The VM rejected the attempt to
> detach the device."}
> job_init_msid: 7321476399279
> job_complete_msid: 7321476399279
>created: 2013-07-11 18:37:52
> last_updated: 2013-07-11 18:37:53
>last_polled: NULL
>removed: NULL
> uuid: e36c7928-3b6b-4cb5-90fb-44dc9378e740
>id: 68
>user_id: 2
> account_id: 2
>session_key: NULL
> instance_type: NULL
>instance_id: NULL
>job_cmd:
> org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd
> job_cmd_originator: NULL
> job_cmd_info:
> {"response":"json","id":"dbf2306a-91e9-4980-b773-eac0523ef290","sessionkey":"MHeSvVY9VxbxczPiN/S443FWzw0\u003d","cmdEventType":"VOLUME.DETACH","ctxUserId":"2","httpmethod":"GET","_":"1373548256841","ctxAccountId":"2","ctxStartEventId":"264"}
>job_cmd_ver: 0
> callback_type: 0
> callback_address: NULL
> job_status: 2
> job_process_status: 0
>job_result_code: 530
> job_result:
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed
> to detach volume: xx from VM: vm3; Failed dettach volume:
> 6a5d2542-2333-4855-bd87-675c7ead26b5, due to
> org.apache.xmlrpc.XmlRpcException: Failed to create input stream: Read timed
> out"}
> job_init_msid: 7321476399279
> job_complete_msid: 7321476399279
>created: 2013-07-11 18:39:22
> last_updated: 2013-07-11 18:49:22
>last_polled: 2013-07-11 18:49:19
>removed: NULL
--
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] [Created] (CLOUDSTACK-3524) NPE while trying to start the router which is in stopped state
Sailaja Mada created CLOUDSTACK-3524: Summary: NPE while trying to start the router which is in stopped state Key: CLOUDSTACK-3524 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3524 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.2.0 Reporter: Sailaja Mada Priority: Critical Steps: 1. Configure Advanced networking zone with VMWARE 2. Tried to start a Router which is in stopped state. Observation: NPE while trying to start the router which is in stopped state 2013-07-15 10:51:32,703 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Checking if we need to prepare 1 volumes for VM[DomainRouter|r-4-VM] 2013-07-15 10:51:32,705 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Volume Vol[14|vm=4|ROOT] will be recreated on storage pool Pool[1|NetworkFilesystem] assigned by deploymentPlanner 2013-07-15 10:51:32,717 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Created new volume Vol[15|vm=4|ROOT] for old volume Vol[14|vm=4|ROOT] 2013-07-15 10:51:32,799 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) copyAsync inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME 2013-07-15 10:51:32,806 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Failed to send to storage pool java.lang.NullPointerException at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.cloneVolume(AncientDataMotionStrategy.java:264) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:343) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromBaseImageAsync(VolumeServiceImpl.java:457) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:494) at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2485) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2542) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:851) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1967) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1945) at com.cloud.network.element.VirtualRouterElement.implement(VirtualRouterElement.java:203) at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1964) at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1869) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2046) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:849) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3327) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2887) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2873) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(A
[jira] [Updated] (CLOUDSTACK-3478) primary:iscsi:cleanupvolumes fail with runtime exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-3478: - Fix Version/s: 4.2.0 > primary:iscsi:cleanupvolumes fail with runtime exception > > > Key: CLOUDSTACK-3478 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3478 > 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 >Reporter: sadhu suresh >Priority: Critical > Fix For: 4.2.0 > > Attachments: management-server.rar > > > steps: > 1.configured the basic zone with network offering"defaultsharednetscalar > eip&elb n/w offering and with xen6.02 hyper-visor ,primary storage type iscsi > 2.deploy few vms > 3.added one more iscsi based primary storage > 4deployed few more deploys > 5.destroy the few vms > Actual result: > during expunging vms ,cleannup of volumes failed with runtime exception. > 2013-07-11 22:37:24,974 DEBUG [db.Transaction.Transaction] > (UserVm-Scavenger-1:null) Rolling back the transaction: Time = 7 Name = > cleanupVolumes; called by > -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-VirtualMachineManagerImpl.advanceExpunge:464-UserVmManagerImpl.expunge:1514-UserVmManagerImpl$ExpungeTask.run:1683-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165 > 2013-07-11 22:37:24,975 WARN [cloud.vm.UserVmManagerImpl] > (UserVm-Scavenger-1:null) Unable to expunge VM[User|sg1] > com.cloud.utils.exception.CloudRuntimeException: Failed to update > state:com.cloud.utils.exception.CloudRuntimeException: Failed to transit > volume: 7, due to: com.cloud.utils.fsm.NoTransitionException: Unable to > transition to a new state from Expunging via DestroyRequested > at > org.apache.cloudstack.storage.volume.VolumeObject.processEvent(VolumeObject.java:292) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.destroyVolume(VolumeServiceImpl.java:503) > at > com.cloud.storage.VolumeManagerImpl.cleanupVolumes(VolumeManagerImpl.java:2095) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceExpunge(VirtualMachineManagerImpl.java:464) > at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:1514) > at > com.cloud.vm.UserVmManagerImpl$ExpungeTask.run(UserVmManagerImpl.java:1683) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-07-11 22:37:24,976 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (UserVm-Scavenger-1:null) Stopped called on VM[User|sg2] but the state is > Expunging > 2013-07-11 22:37:24,985 DEBUG [cloud.capacity.CapacityManagerImpl] > (UserVm-Scavenger-1:null) VM state transitted from :Expunging to Expunging > with event: ExpungeOperationvm's original host id: 2 new host id: null host > id before state transition: null > 2013-07-11 22:37:24,985 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (UserVm-Scavenger-1:null) Destroying vm VM[User|sg2] > 2013-07-11 22:37:24,985 DEBUG [cloud.vm.VirtualMachineManagerImpl] > (UserVm-Scavenger-1:null) Cleaning up NICS > 2013-07-11 22:37:24,985 DEBUG [cloud.network.NetworkManagerImpl] > (UserVm-Scavenger-1:null) Cleaning network for vm: 8 > 2013-07-11 22:37:24,990 DEBUG [cloud.storage.VolumeManagerImpl] > (UserVm-Scavenger-1:null) Cleaning storage for vm: 8 > 2013-07-11 22:37:24,999 DEBUG [storage.volume.VolumeObject] > (UserVm-Scavenger-1:null) Failed to transit volume: 8, due to: > com.cloud.utils.fsm.NoTransitionException: Unable to transition to a new > state from Expunging via DestroyRequested > 2013-07-11 22:37:24,999 DEBUG [storage.volume.VolumeObject] > (UserVm-
[jira] [Updated] (CLOUDSTACK-3524) NPE while trying to start the router which is in stopped state while creating volume with ZWPS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3524: - Summary: NPE while trying to start the router which is in stopped state while creating volume with ZWPS (was: NPE while trying to start the router which is in stopped state) > NPE while trying to start the router which is in stopped state while creating > volume with ZWPS > -- > > Key: CLOUDSTACK-3524 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3524 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Sailaja Mada >Priority: Critical > > Steps: > 1. Configure Advanced networking zone with VMWARE with Zone wide primary > storage > 2. Tried to start a Router which is in stopped state. > Observation: > NPE while trying to start the router which is in stopped state > 2013-07-15 10:51:32,703 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Checking > if we need to prepare 1 volumes for VM[DomainRouter|r-4-VM] > 2013-07-15 10:51:32,705 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Volume > Vol[14|vm=4|ROOT] will be recreated on storage pool Pool[1|NetworkFilesystem] > assigned by deploymentPlanner > 2013-07-15 10:51:32,717 DEBUG [cloud.storage.VolumeManagerImpl] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Created > new volume Vol[15|vm=4|ROOT] for old volume Vol[14|vm=4|ROOT] > 2013-07-15 10:51:32,799 DEBUG [storage.motion.AncientDataMotionStrategy] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) copyAsync > inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME > 2013-07-15 10:51:32,806 DEBUG [storage.motion.AncientDataMotionStrategy] > (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Failed to > send to storage pool > java.lang.NullPointerException > at > org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.cloneVolume(AncientDataMotionStrategy.java:264) > at > org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:343) > at > org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromBaseImageAsync(VolumeServiceImpl.java:457) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:494) > at > com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2485) > at > com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2542) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:851) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1967) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1945) > at > com.cloud.network.element.VirtualRouterElement.implement(VirtualRouterElement.java:203) > at > com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1964) > at > com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1869) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2046) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:849) > at > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) > at > org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) > at > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) > at > com.cloud.vm.UserVmManagerImpl.
[jira] [Updated] (CLOUDSTACK-3524) NPE while trying to start the router which is in stopped state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-3524: - Description: Steps: 1. Configure Advanced networking zone with VMWARE with Zone wide primary storage 2. Tried to start a Router which is in stopped state. Observation: NPE while trying to start the router which is in stopped state 2013-07-15 10:51:32,703 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Checking if we need to prepare 1 volumes for VM[DomainRouter|r-4-VM] 2013-07-15 10:51:32,705 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Volume Vol[14|vm=4|ROOT] will be recreated on storage pool Pool[1|NetworkFilesystem] assigned by deploymentPlanner 2013-07-15 10:51:32,717 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Created new volume Vol[15|vm=4|ROOT] for old volume Vol[14|vm=4|ROOT] 2013-07-15 10:51:32,799 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) copyAsync inspecting src type TEMPLATE copyAsync inspecting dest type VOLUME 2013-07-15 10:51:32,806 DEBUG [storage.motion.AncientDataMotionStrategy] (Job-Executor-24:job-24 = [ a8d8b93b-4a29-445a-844a-e75d34cc5346 ]) Failed to send to storage pool java.lang.NullPointerException at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.cloneVolume(AncientDataMotionStrategy.java:264) at org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:343) at org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:55) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromBaseImageAsync(VolumeServiceImpl.java:457) at org.apache.cloudstack.storage.volume.VolumeServiceImpl.createVolumeFromTemplateAsync(VolumeServiceImpl.java:494) at com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2485) at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2542) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:851) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2727) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1867) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1967) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1945) at com.cloud.network.element.VirtualRouterElement.implement(VirtualRouterElement.java:203) at com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources(NetworkManagerImpl.java:1964) at com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.java:1869) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2046) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:849) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:557) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3327) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2887) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2873) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.Thread
[jira] [Assigned] (CLOUDSTACK-2168) configured LDAP values not shown in UI
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-2168:
--
Assignee: Abhinandan Prateek
> configured LDAP values not shown in UI
> --
>
> Key: CLOUDSTACK-2168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2168
> 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
>Reporter: sadhu suresh
>Assignee: Abhinandan Prateek
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloudstack-2168.patch, screenshot_ldap.jpg
>
>
> Steps:
> 1.Configured the LDAP through API
> http://10.147.59.83:8096/client/api?command=ldapConfig&hostname=10.147.38.163&searchbase=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcom&queryfilter=%28%26%28mail%3D%25e%29%29&port=389&response=json
> 2.Open the CS web console and navigate to LDAP configuration section
> 3.check the displayed LDAP configured values
> Actual result:
> Even though LDAP configuration happens successfully but UI fail to display
> the Values.
> even firebug response shows the configured ldap values but UI fail to display
> the values.
> UI:
> ---
> Hostname Query FilterSearch Base LDAP Port SSL
> Quickview
> No data to show
> firebug response:
>
> http://10.147.59.83:8080/client/api?command=ldapConfig&listall=true&response=json&sessionkey=2G5uy2a4z%2F31Mi3yaVKmvXc10a4%3D&listAll=true&page=1&pagesize=20&_=1366791925255
> { "ldapconfigresponse" : { "ldapconfig" :
> {"hostname":"10.147.38.163","port":"389","ssl":"false","searchbase":"CN=Users,DC=hyd-qa,DC=com","queryfilter":"(&(mail=%e))","binddn":""}
> } }
--
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] [Assigned] (CLOUDSTACK-3502) CloudStack will not allow migration of volumes of stopped VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-3502: - Assignee: Devdeep Singh > CloudStack will not allow migration of volumes of stopped VMs > - > > Key: CLOUDSTACK-3502 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3502 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: XenServer >Affects Versions: 4.2.0 > Environment: XenServer 6.1 and XenServer 6.2 >Reporter: Paul Angus >Assignee: Devdeep Singh > Labels: management, storage, xenserver > Fix For: 4.2.0 > > > CloudStack will not allow migration of volumes of stopped VMs. The following > error is logged i > DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) ===START=== 10.0.0.33 > -- GET > command=findStoragePoolsForMigration&id=88249ba7-7efc-458d-a5fb-dfe509f3be94&response=json&sessionkey=f1fhBLP6fTlE5Wun%2FBDzzbkAH4k%3D&_=1373630022341 > INFO [cloud.server.ManagementServerImpl] (catalina-exec-18:null) Volume > Vol[20|vm=20|ROOT] isn't attached to any running vm. Only volumes attached to > a running VM can be migrated. > DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===START=== 10.0.0.33 > -- GET > command=findStoragePoolsForMigration&id=0a3704cf-6a23-4c18-bf90-9fd701da2223&response=json&sessionkey=RKyZ0iBJcDk11IUG7pLJs57wgTE%3D&_=1373620893684 > INFO [cloud.server.ManagementServerImpl] (catalina-exec-10:null) Volume > Vol[16|vm=16|ROOT] isn't attached to any running vm. Only volumes attached to > a running VM can be migrated. -- 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] [Updated] (CLOUDSTACK-2757) Category not persisted when added config items
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-2757: --- Component/s: Management Server Affects Version/s: 4.2.0 > Category not persisted when added config items > -- > > Key: CLOUDSTACK-2757 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2757 > 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 >Reporter: Kishan Kavala >Assignee: Likitha Shetty > Fix For: 4.2.0 > > > Category is persisted when adding config items in > ConfigurationDaoImpl.getValueAndInitIfNotExist. > It is always set to "Advanced". > This can cause encryption failures. > It'll be good to cleanup the SQL and use VO/DAO instead -- 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-1453) support restore for VM created from ISO
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-1453. Now the Support for the ISO is also added in the latest Builds, hence closing the defect. > support restore for VM created from ISO > --- > > Key: CLOUDSTACK-1453 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1453 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.2.0 > > -- 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-2704) [Shared Nework] Allow Egress traffic for shared network by default
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy closed CLOUDSTACK-2704. - > [Shared Nework] Allow Egress traffic for shared network by default > -- > > Key: CLOUDSTACK-2704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2704 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Network Devices >Affects Versions: 4.1.0, 4.2.0 >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Fix For: 4.2.0 > > > 1. Egress rules blocks the guest traffic to public side by default. > 2. Egress is not supported for shared networks so by default we should allow > egress. > 3. This issue can be handled when CLOUDSTACK-1578 is fixed. > WorkAround: > 1. In router execute the below command > iptables -A FW_OUTBOUND -j ACCEPT > 2. To persist in router reboot add the below entry in iptables-router file > after '-I FW_OUTBOUND -m state --state RELATED,ESTABLISHED -j ACCEPT' entry > -A FW_OUTBOUND -j ACCPET -- 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-3463) [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-3463. -- Resolution: Fixed > [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP > --- > > Key: CLOUDSTACK-3463 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3463 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have latest CloudStack setup with EIP / ELB enabled zone using the default > EIP/ELB network offering. > 2. Deploy a VM. > 3. By default VM is associated with is_system=1 public ip address > 4. Acquire a portable IP and enable static NAT on the portable IP > Observations: > (i) the default is_system=1 public ip address was released and static nat > enabled on the new portable IP and everything is fine as expected. > 5. Disassociate the portable IP that was acquired in step : 4 > Observations: > (ii) Portable IP got released without any issue but, didn't see any > is_system=1 public IP associated with user VM. > 2013-07-11 10:21:55,044 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-43:job-216) Schedule queued job-216 > 2013-07-11 10:21:55,075 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-43:job-216) There is a pending process in sync queue(id: 80) > 2013-07-11 10:21:55,076 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-44:job-216) Executing > org.apache.cloudstack.api.command.user.address.DisassociateIPAddrCmd for > job-216 > 2013-07-11 10:21:55,102 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-44:job-216) Access to Ip[10.147.45.223-3] granted to > Acct[9-dom1Acc5] by DomainChecker_EnhancerByCloudStack_9ffe9015 > 2013-07-11 10:21:55,104 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-44:job-216) Revoking all Firewallrules as a part of public IP > id=217 release... > 2013-07-11 10:21:55,106 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) Releasing 0 firewall rules for ip id=217 > 2013-07-11 10:21:55,108 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) There are no firewall rules to apply > 2013-07-11 10:21:55,110 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) Successfully released firewall rules for ip id=217 > and # of rules now = 0 > 2013-07-11 10:21:55,110 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-44:job-216) Revoking all PortForwarding/StaticNat rules as a > part of public IP id=217 release... > (iii) at this moment user VM is neither associated with any EIP nor with any > portable IP. > Attaching all the required logs along with db dump. -- 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] [Commented] (CLOUDSTACK-3463) [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708230#comment-13708230 ] ASF subversion and git services commented on CLOUDSTACK-3463: - Commit feeffeaf10d845f0493c353fbc609e994483759a in branch refs/heads/4.2 from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=feeffea ] CLOUDSTACK-3463: [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP fix ensures that, on release of portable IP associated with 'EIP enabled' basic zone vm, a new system public IP is allocated and associated with the VM > [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP > --- > > Key: CLOUDSTACK-3463 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3463 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have latest CloudStack setup with EIP / ELB enabled zone using the default > EIP/ELB network offering. > 2. Deploy a VM. > 3. By default VM is associated with is_system=1 public ip address > 4. Acquire a portable IP and enable static NAT on the portable IP > Observations: > (i) the default is_system=1 public ip address was released and static nat > enabled on the new portable IP and everything is fine as expected. > 5. Disassociate the portable IP that was acquired in step : 4 > Observations: > (ii) Portable IP got released without any issue but, didn't see any > is_system=1 public IP associated with user VM. > 2013-07-11 10:21:55,044 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-43:job-216) Schedule queued job-216 > 2013-07-11 10:21:55,075 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-43:job-216) There is a pending process in sync queue(id: 80) > 2013-07-11 10:21:55,076 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-44:job-216) Executing > org.apache.cloudstack.api.command.user.address.DisassociateIPAddrCmd for > job-216 > 2013-07-11 10:21:55,102 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-44:job-216) Access to Ip[10.147.45.223-3] granted to > Acct[9-dom1Acc5] by DomainChecker_EnhancerByCloudStack_9ffe9015 > 2013-07-11 10:21:55,104 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-44:job-216) Revoking all Firewallrules as a part of public IP > id=217 release... > 2013-07-11 10:21:55,106 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) Releasing 0 firewall rules for ip id=217 > 2013-07-11 10:21:55,108 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) There are no firewall rules to apply > 2013-07-11 10:21:55,110 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) Successfully released firewall rules for ip id=217 > and # of rules now = 0 > 2013-07-11 10:21:55,110 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-44:job-216) Revoking all PortForwarding/StaticNat rules as a > part of public IP id=217 release... > (iii) at this moment user VM is neither associated with any EIP nor with any > portable IP. > Attaching all the required logs along with db dump. -- 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] [Commented] (CLOUDSTACK-3463) [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708229#comment-13708229 ] ASF subversion and git services commented on CLOUDSTACK-3463: - Commit 0c32466a758ed7be643488d5cc7ec6d6e267da30 in branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0c32466 ] CLOUDSTACK-3463: [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP fix ensures that, on release of portable IP associated with 'EIP enabled' basic zone vm, a new system public IP is allocated and associated with the VM > [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP > --- > > Key: CLOUDSTACK-3463 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3463 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have latest CloudStack setup with EIP / ELB enabled zone using the default > EIP/ELB network offering. > 2. Deploy a VM. > 3. By default VM is associated with is_system=1 public ip address > 4. Acquire a portable IP and enable static NAT on the portable IP > Observations: > (i) the default is_system=1 public ip address was released and static nat > enabled on the new portable IP and everything is fine as expected. > 5. Disassociate the portable IP that was acquired in step : 4 > Observations: > (ii) Portable IP got released without any issue but, didn't see any > is_system=1 public IP associated with user VM. > 2013-07-11 10:21:55,044 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-43:job-216) Schedule queued job-216 > 2013-07-11 10:21:55,075 DEBUG [cloud.async.SyncQueueManagerImpl] > (Job-Executor-43:job-216) There is a pending process in sync queue(id: 80) > 2013-07-11 10:21:55,076 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-44:job-216) Executing > org.apache.cloudstack.api.command.user.address.DisassociateIPAddrCmd for > job-216 > 2013-07-11 10:21:55,102 DEBUG [cloud.user.AccountManagerImpl] > (Job-Executor-44:job-216) Access to Ip[10.147.45.223-3] granted to > Acct[9-dom1Acc5] by DomainChecker_EnhancerByCloudStack_9ffe9015 > 2013-07-11 10:21:55,104 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-44:job-216) Revoking all Firewallrules as a part of public IP > id=217 release... > 2013-07-11 10:21:55,106 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) Releasing 0 firewall rules for ip id=217 > 2013-07-11 10:21:55,108 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) There are no firewall rules to apply > 2013-07-11 10:21:55,110 DEBUG [network.firewall.FirewallManagerImpl] > (Job-Executor-44:job-216) Successfully released firewall rules for ip id=217 > and # of rules now = 0 > 2013-07-11 10:21:55,110 DEBUG [cloud.network.NetworkManagerImpl] > (Job-Executor-44:job-216) Revoking all PortForwarding/StaticNat rules as a > part of public IP id=217 release... > (iii) at this moment user VM is neither associated with any EIP nor with any > portable IP. > Attaching all the required logs along with db dump. -- 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-3465) [Portable IP] [EIP/ELB Zone] NetworkId of the acquired portable IP is showing "Control Network"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-3465. -- Resolution: Fixed Network id was being set wrongly. As part of the fix for CLOUDSTACK-3444 (which is agin result of network id not being set to public network) this issue is addressed. Below is the commit details for 3444 Commit 44664924840a540db3727291bfcc08ae519c0055 in branch refs/heads/master CLOUDSTACK-3444: Unable to transfer portalbe IP between ISOLATED network and VPC Tiered Network When portable IP is transferred across the zones, we emulate portable IP as provisioned in new zone's physical network carrying public traffic and logical public network. network Id, and physical network id both were bieng set to same physical network id resulting in IP association to fail. This fix ensures both network and physcial network are set appropriatley. > [Portable IP] [EIP/ELB Zone] NetworkId of the acquired portable IP is showing > "Control Network" > --- > > Key: CLOUDSTACK-3465 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3465 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy > Fix For: 4.2.0 > > Attachments: logs.tgz, Screen Shot 2013-07-11 at 4.28.23 PM.png > > > Steps to reproduce: > 1. Have latest CloudStack setup with EIP / ELB enabled zone using the default > EIP/ELB network offering. > 2. Deploy a VM. > 3. By default VM is associated with is_system=1 public ip address > 4. Acquire a portable IP and enable static NAT on the portable IP > 5. Click on the acquired portable IP and check the network ID of it. > Observations: > (i) It shows the network id as the uuid of "Control network" instead of > showing the public network uuid. > mysql> select * from networks where id=202\G > *** 1. row *** >id: 202 > name: NULL > uuid: 60e08bb1-2f94-45d6-93b6-f7754f9ad78e > display_text: NULL > traffic_type: Control > broadcast_domain_type: LinkLocal > broadcast_uri: NULL > gateway: 169.254.0.1 > cidr: 169.254.0.0/16 > mode: Static > network_offering_id: 3 > physical_network_id: NULL >data_center_id: 1 > guru_name: ControlNetworkGuru > state: Setup > related: 202 > domain_id: 1 >account_id: 1 > dns1: NULL > dns2: NULL > guru_data: NULL >set_fields: 0 > acl_type: NULL >network_domain: NULL >reservation_id: NULL >guest_type: NULL > restart_required: 0 > created: 2013-07-04 04:12:14 > removed: NULL > specify_ip_ranges: 0 >vpc_id: NULL > ip6_gateway: NULL > ip6_cidr: NULL > network_cidr: NULL > display_network: 1 >network_acl_id: NULL > Attaching the screenshot of the same. > attaching all the required logs along with db dump to the bug. -- 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-3444) [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC Tiered Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy resolved CLOUDSTACK-3444. -- Resolution: Fixed > [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC > Tiered Network > - > > Key: CLOUDSTACK-3444 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3444 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have latest CloudStack setup with at least 2 advanced zones (Zone1, Zone2) > 2. Create a VPC in one of the zone (Zone2) > 3. Create at least 1 Tier in the above created VPC > 4. Have at least one ISOLATED network in Zone1 > 5. Acquire at least one portable IP and associate it to the above network > created in step: 4 > 6. enable static NAT on the portable IP acquired in Step:5 to a VM that is > running in Zone2 VPC Tier1 > enable staticnat ipaddressid=4057b22d-f78b-4a34-8548-c745355b01d4 > virtualmachineid=9f8ad68a-a8f4-4685-8a38-a4daf4896fce > networkid=921b86ef-4c82-4b49-8bf8-d6f2b93a5963 > HTTP Error 530: > Observations: > (i) It fails with the following error in the management server logs. > 2013-07-10 12:47:42,468 ERROR [cloud.api.ApiServer] (catalina-exec-7:null) > unhandled exception executing api command: enableStaticNat > com.cloud.utils.exception.CloudRuntimeException: Unable to find the nic in > network 222 to apply the ip address 10.147.49.224 for > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl$1.execute(VpcVirtualNetworkApplianceManagerImpl.java:646) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3769) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.associatePublicIP(VpcVirtualNetworkApplianceManagerImpl.java:632) > at > com.cloud.network.element.VpcVirtualRouterElement.applyIps(VpcVirtualRouterElement.java:400) > at > com.cloud.network.NetworkManagerImpl.applyIpAssociations(NetworkManagerImpl.java:694) > at > com.cloud.network.NetworkManagerImpl.applyStaticNats(NetworkManagerImpl.java:3557) > at > com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1310) > at > com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:582) > at > com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:431) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.nat.EnableStaticNatCmd.execute(EnableStaticNatCmd.java:129) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > at > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > at > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) > at > java.ut
[jira] [Commented] (CLOUDSTACK-3444) [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC Tiered Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708220#comment-13708220 ] ASF subversion and git services commented on CLOUDSTACK-3444: - Commit 44664924840a540db3727291bfcc08ae519c0055 in branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4466492 ] CLOUDSTACK-3444: Unable to transfer portalbe IP between ISOLATED network and VPC Tiered Network When portable IP is transferred across the zones, we emulate portable IP as provisioned in new zone's physical network carrying public traffic and logical public network. network Id, and physical network id both were bieng set to same physical network id resulting in IP association to fail. This fix ensures both network and physcial network are set appropriatley. > [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC > Tiered Network > - > > Key: CLOUDSTACK-3444 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3444 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have latest CloudStack setup with at least 2 advanced zones (Zone1, Zone2) > 2. Create a VPC in one of the zone (Zone2) > 3. Create at least 1 Tier in the above created VPC > 4. Have at least one ISOLATED network in Zone1 > 5. Acquire at least one portable IP and associate it to the above network > created in step: 4 > 6. enable static NAT on the portable IP acquired in Step:5 to a VM that is > running in Zone2 VPC Tier1 > enable staticnat ipaddressid=4057b22d-f78b-4a34-8548-c745355b01d4 > virtualmachineid=9f8ad68a-a8f4-4685-8a38-a4daf4896fce > networkid=921b86ef-4c82-4b49-8bf8-d6f2b93a5963 > HTTP Error 530: > Observations: > (i) It fails with the following error in the management server logs. > 2013-07-10 12:47:42,468 ERROR [cloud.api.ApiServer] (catalina-exec-7:null) > unhandled exception executing api command: enableStaticNat > com.cloud.utils.exception.CloudRuntimeException: Unable to find the nic in > network 222 to apply the ip address 10.147.49.224 for > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl$1.execute(VpcVirtualNetworkApplianceManagerImpl.java:646) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3769) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.associatePublicIP(VpcVirtualNetworkApplianceManagerImpl.java:632) > at > com.cloud.network.element.VpcVirtualRouterElement.applyIps(VpcVirtualRouterElement.java:400) > at > com.cloud.network.NetworkManagerImpl.applyIpAssociations(NetworkManagerImpl.java:694) > at > com.cloud.network.NetworkManagerImpl.applyStaticNats(NetworkManagerImpl.java:3557) > at > com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1310) > at > com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:582) > at > com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:431) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.nat.EnableStaticNatCmd.execute(EnableStaticNatCmd.java:129) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(Stan
[jira] [Commented] (CLOUDSTACK-3444) [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC Tiered Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708222#comment-13708222 ] ASF subversion and git services commented on CLOUDSTACK-3444: - Commit 8de3b4f461ab67ccd5bb3d4d0793619c9e5034e0 in branch refs/heads/4.2 from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8de3b4f ] CLOUDSTACK-3444: Unable to transfer portalbe IP between ISOLATED network and VPC Tiered Network When portable IP is transferred across the zones, we emulate portable IP as provisioned in new zone's physical network carrying public traffic and logical public network. network Id, and physical network id both were bieng set to same physical network id resulting in IP association to fail. This fix ensures both network and physcial network are set appropriatley. > [Portable IP] [VPC] Unable to transfer IP between ISOLATED network and VPC > Tiered Network > - > > Key: CLOUDSTACK-3444 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3444 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 > Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0 >Reporter: venkata swamybabu budumuru >Assignee: Murali Reddy >Priority: Critical > Fix For: 4.2.0 > > Attachments: logs.tgz > > > Steps to reproduce: > 1. Have latest CloudStack setup with at least 2 advanced zones (Zone1, Zone2) > 2. Create a VPC in one of the zone (Zone2) > 3. Create at least 1 Tier in the above created VPC > 4. Have at least one ISOLATED network in Zone1 > 5. Acquire at least one portable IP and associate it to the above network > created in step: 4 > 6. enable static NAT on the portable IP acquired in Step:5 to a VM that is > running in Zone2 VPC Tier1 > enable staticnat ipaddressid=4057b22d-f78b-4a34-8548-c745355b01d4 > virtualmachineid=9f8ad68a-a8f4-4685-8a38-a4daf4896fce > networkid=921b86ef-4c82-4b49-8bf8-d6f2b93a5963 > HTTP Error 530: > Observations: > (i) It fails with the following error in the management server logs. > 2013-07-10 12:47:42,468 ERROR [cloud.api.ApiServer] (catalina-exec-7:null) > unhandled exception executing api command: enableStaticNat > com.cloud.utils.exception.CloudRuntimeException: Unable to find the nic in > network 222 to apply the ip address 10.147.49.224 for > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl$1.execute(VpcVirtualNetworkApplianceManagerImpl.java:646) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3769) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.associatePublicIP(VpcVirtualNetworkApplianceManagerImpl.java:632) > at > com.cloud.network.element.VpcVirtualRouterElement.applyIps(VpcVirtualRouterElement.java:400) > at > com.cloud.network.NetworkManagerImpl.applyIpAssociations(NetworkManagerImpl.java:694) > at > com.cloud.network.NetworkManagerImpl.applyStaticNats(NetworkManagerImpl.java:3557) > at > com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1310) > at > com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:582) > at > com.cloud.network.rules.RulesManagerImpl.enableStaticNat(RulesManagerImpl.java:431) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.nat.EnableStaticNatCmd.execute(EnableStaticNatCmd.java:129) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) > at > org.apache.catalina.core.StandardHostValve.invoke(Standar
[jira] [Updated] (CLOUDSTACK-3523) G11n: JA,SC: Un translation issue occurred on the strings of different popup messages.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3523: Attachment: SC-6.Popup msg.zip 6.Popup msg_Templates_Templates_SC_038.jpg 6.Popup msg_Account_SC_060.jpg JA-6.Popup msg.zip 6.Popup msg_Templates_Templates_JA_038.jpg 6.Popup msg_Account_JA_060.jpg > G11n: JA,SC: Un translation issue occurred on the strings of different popup > messages. > --- > > Key: CLOUDSTACK-3523 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3523 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#G11n-56/G11n-57 > (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS & CS-Mgr Servers > Win7Entx64SP1 for Client machine >Reporter: Minying Bao > Fix For: 4.2.0 > > Attachments: 6.Popup msg_Account_JA_060.jpg, 6.Popup > msg_Account_SC_060.jpg, 6.Popup msg_Templates_Templates_JA_038.jpg, 6.Popup > msg_Templates_Templates_SC_038.jpg, JA-6.Popup msg.zip, SC-6.Popup msg.zip > > > Repro Steps > Setup Basic environments. > Login Web Portal with Japanese/Simplified Chinese as default. Check all the > strings of different popup messages. > Expected Result > All the strings should be translated to Japanese/Simplified Chinese. > Actual Result > A lot of un-translated strings display. > (Please refer to the more screenshots as below location: > Pactera WUXI FTP: 172.16.45.222 > /Temp/CloudPlatform/Campo/Un Translations issues) > Regression Info. > Build#G11n-56 -> Fail > Build#G11n-57 -> Fail -- 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] [Created] (CLOUDSTACK-3523) G11n: JA,SC: Un translation issue occurred on the strings of different popup messages.
Minying Bao created CLOUDSTACK-3523: --- Summary: G11n: JA,SC: Un translation issue occurred on the strings of different popup messages. Key: CLOUDSTACK-3523 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3523 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Build No.#G11n-56/G11n-57 (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) XenServer6.1 for Host Server CentOS6.3 for NFS & CS-Mgr Servers Win7Entx64SP1 for Client machine Reporter: Minying Bao Fix For: 4.2.0 Attachments: 6.Popup msg_Account_JA_060.jpg, 6.Popup msg_Account_SC_060.jpg, 6.Popup msg_Templates_Templates_JA_038.jpg, 6.Popup msg_Templates_Templates_SC_038.jpg, JA-6.Popup msg.zip, SC-6.Popup msg.zip Repro Steps Setup Basic environments. Login Web Portal with Japanese/Simplified Chinese as default. Check all the strings of different popup messages. Expected Result All the strings should be translated to Japanese/Simplified Chinese. Actual Result A lot of un-translated strings display. (Please refer to the more screenshots as below location: Pactera WUXI FTP: 172.16.45.222 /Temp/CloudPlatform/Campo/Un Translations issues) Regression Info. Build#G11n-56 -> Fail Build#G11n-57 -> Fail -- 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] [Created] (CLOUDSTACK-3522) G11n: JA,SC: Un translation issue occurred on the strings of different buttons.
Minying Bao created CLOUDSTACK-3522: --- Summary: G11n: JA,SC: Un translation issue occurred on the strings of different buttons. Key: CLOUDSTACK-3522 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3522 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Build No.#G11n-56/G11n-57 (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) XenServer6.1 for Host Server CentOS6.3 for NFS & CS-Mgr Servers Win7Entx64SP1 for Client machine Reporter: Minying Bao Fix For: 4.2.0 Attachments: 5.Button_Events_JA_011.jpg, 5.Button_Events_SC_011.jpg, 5.Button_Templates_Templates_JA_027-1.jpg, 5.Button_Templates_Templates_SC_027-1.jpg, JA-5.Button.zip, SC-5.Button.zip Repro Steps Setup Basic environments. Login Web Portal with Japanese/Simplified Chinese as default. Check all the strings of different buttons. Expected Result All the strings should be translated to Japanese/Simplified Chinese. Actual Result A lot of un-translated strings display. (Please refer to the more screenshots as below location: Pactera WUXI FTP: 172.16.45.222 /Temp/CloudPlatform/Campo/Un Translations issues) Regression Info. Build#G11n-56 -> Fail Build#G11n-57 -> Fail -- 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] [Updated] (CLOUDSTACK-3522) G11n: JA,SC: Un translation issue occurred on the strings of different buttons.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3522: Attachment: JA-5.Button.zip 5.Button_Templates_Templates_JA_027-1.jpg 5.Button_Events_JA_011.jpg SC-5.Button.zip 5.Button_Templates_Templates_SC_027-1.jpg 5.Button_Events_SC_011.jpg > G11n: JA,SC: Un translation issue occurred on the strings of different > buttons. > > > Key: CLOUDSTACK-3522 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3522 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#G11n-56/G11n-57 > (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS & CS-Mgr Servers > Win7Entx64SP1 for Client machine >Reporter: Minying Bao > Fix For: 4.2.0 > > Attachments: 5.Button_Events_JA_011.jpg, 5.Button_Events_SC_011.jpg, > 5.Button_Templates_Templates_JA_027-1.jpg, > 5.Button_Templates_Templates_SC_027-1.jpg, JA-5.Button.zip, SC-5.Button.zip > > > Repro Steps > Setup Basic environments. > Login Web Portal with Japanese/Simplified Chinese as default. Check all the > strings of different buttons. > Expected Result > All the strings should be translated to Japanese/Simplified Chinese. > Actual Result > A lot of un-translated strings display. > (Please refer to the more screenshots as below location: > Pactera WUXI FTP: 172.16.45.222 > /Temp/CloudPlatform/Campo/Un Translations issues) > Regression Info. > Build#G11n-56 -> Fail > Build#G11n-57 -> Fail -- 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] [Created] (CLOUDSTACK-3521) G11n: JA,SC: Un translation issue occurred on the strings of different tooltips.
Minying Bao created CLOUDSTACK-3521: --- Summary: G11n: JA,SC: Un translation issue occurred on the strings of different tooltips. Key: CLOUDSTACK-3521 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3521 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Build No.#G11n-56/G11n-57 (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) XenServer6.1 for Host Server CentOS6.3 for NFS & CS-Mgr Servers Win7Entx64SP1 for Client machine Reporter: Minying Bao Fix For: 4.2.0 Attachments: 4.Tooltip_Account_JA_004.jpg, 4.Tooltip_Account_SC_004.jpg, 4.Tooltip_Events_JA_005.jpg, 4.Tooltip_Events_SC_005.jpg, JA-4.Tooltip-Part1.zip, JA-4.Tooltip-Part2.zip, JA-4.Tooltip-Part3.zip, SC-4.Tooltip-Part1.zip, SC-4.Tooltip-Part2.zip, SC-4.Tooltip-Part3.zip Repro Steps Setup Basic environments. Login Web Portal with Japanese/Simplified Chinese as default. Check all the strings of different tooltips. Expected Result All the strings should be translated to Japanese/Simplified Chinese. Actual Result A lot of un-translated strings display. (Please refer to the more screenshots as below location: Pactera WUXI FTP: 172.16.45.222 /Temp/CloudPlatform/Campo/Un Translations issues) Regression Info. Build#G11n-56 -> Fail Build#G11n-57 -> Fail -- 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] [Updated] (CLOUDSTACK-3521) G11n: JA,SC: Un translation issue occurred on the strings of different tooltips.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3521: Attachment: SC-4.Tooltip-Part3.zip SC-4.Tooltip-Part2.zip SC-4.Tooltip-Part1.zip 4.Tooltip_Events_SC_005.jpg 4.Tooltip_Account_SC_004.jpg JA-4.Tooltip-Part3.zip JA-4.Tooltip-Part2.zip JA-4.Tooltip-Part1.zip 4.Tooltip_Events_JA_005.jpg 4.Tooltip_Account_JA_004.jpg > G11n: JA,SC: Un translation issue occurred on the strings of different > tooltips. > - > > Key: CLOUDSTACK-3521 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3521 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#G11n-56/G11n-57 > (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS & CS-Mgr Servers > Win7Entx64SP1 for Client machine >Reporter: Minying Bao > Fix For: 4.2.0 > > Attachments: 4.Tooltip_Account_JA_004.jpg, > 4.Tooltip_Account_SC_004.jpg, 4.Tooltip_Events_JA_005.jpg, > 4.Tooltip_Events_SC_005.jpg, JA-4.Tooltip-Part1.zip, JA-4.Tooltip-Part2.zip, > JA-4.Tooltip-Part3.zip, SC-4.Tooltip-Part1.zip, SC-4.Tooltip-Part2.zip, > SC-4.Tooltip-Part3.zip > > > Repro Steps > Setup Basic environments. > Login Web Portal with Japanese/Simplified Chinese as default. Check all the > strings of different tooltips. > Expected Result > All the strings should be translated to Japanese/Simplified Chinese. > Actual Result > A lot of un-translated strings display. > (Please refer to the more screenshots as below location: > Pactera WUXI FTP: 172.16.45.222 > /Temp/CloudPlatform/Campo/Un Translations issues) > Regression Info. > Build#G11n-56 -> Fail > Build#G11n-57 -> Fail -- 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] [Updated] (CLOUDSTACK-3520) G11n: JA,SC: Un translation issue occurred on the strings of different error/warning/information messages.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3520: Attachment: JA-3.Error,Warning,Info msg.zip 3.Error,Warning,Info msg_AffinityGroups_JA_009.jpg 3.Error,Warning,Info msg_Account_JA_043.jpg SC-3.Error,Warning,Info msg.zip 3.Error,Warning,Info msg_AffinityGroups_SC_009.jpg 3.Error,Warning,Info msg_Account_SC_043.jpg > G11n: JA,SC: Un translation issue occurred on the strings of different > error/warning/information messages. > --- > > Key: CLOUDSTACK-3520 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3520 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#G11n-56/G11n-57 > (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS & CS-Mgr Servers > Win7Entx64SP1 for Client machine >Reporter: Minying Bao > Fix For: 4.2.0 > > Attachments: 3.Error,Warning,Info msg_Account_JA_043.jpg, > 3.Error,Warning,Info msg_Account_SC_043.jpg, 3.Error,Warning,Info > msg_AffinityGroups_JA_009.jpg, 3.Error,Warning,Info > msg_AffinityGroups_SC_009.jpg, JA-3.Error,Warning,Info msg.zip, > SC-3.Error,Warning,Info msg.zip > > > Repro Steps > Setup Basic environments. > Login Web Portal with Japanese/Simplified Chinese as default. Check all the > strings of different error/warning/information messages. > Expected Result > All the strings should be translated to Japanese/Simplified Chinese. > Actual Result > A lot of un-translated strings display. > (Please refer to the more screenshots as below location: > Pactera WUXI FTP: 172.16.45.222 > /Temp/CloudPlatform/Campo/Un Translations issues) > Regression Info. > Build#G11n-56 -> Fail > Build#G11n-57 -> Fail -- 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] [Created] (CLOUDSTACK-3520) G11n: JA,SC: Un translation issue occurred on the strings of different error/warning/information messages.
Minying Bao created CLOUDSTACK-3520: --- Summary: G11n: JA,SC: Un translation issue occurred on the strings of different error/warning/information messages. Key: CLOUDSTACK-3520 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3520 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Build No.#G11n-56/G11n-57 (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) XenServer6.1 for Host Server CentOS6.3 for NFS & CS-Mgr Servers Win7Entx64SP1 for Client machine Reporter: Minying Bao Fix For: 4.2.0 Attachments: 3.Error,Warning,Info msg_Account_JA_043.jpg, 3.Error,Warning,Info msg_Account_SC_043.jpg, 3.Error,Warning,Info msg_AffinityGroups_JA_009.jpg, 3.Error,Warning,Info msg_AffinityGroups_SC_009.jpg, JA-3.Error,Warning,Info msg.zip, SC-3.Error,Warning,Info msg.zip Repro Steps Setup Basic environments. Login Web Portal with Japanese/Simplified Chinese as default. Check all the strings of different error/warning/information messages. Expected Result All the strings should be translated to Japanese/Simplified Chinese. Actual Result A lot of un-translated strings display. (Please refer to the more screenshots as below location: Pactera WUXI FTP: 172.16.45.222 /Temp/CloudPlatform/Campo/Un Translations issues) Regression Info. Build#G11n-56 -> Fail Build#G11n-57 -> Fail -- 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] [Updated] (CLOUDSTACK-3519) G11n: JA,SC: Un translation issue occurred on the strings of different dropdown lists.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3519: Attachment: SC-2.Dropdown.zip 2.Dropdown_Dashboard_SC_039.jpg 2.Dropdown_Account_SC_014.jpg JA-2.Dropdown.zip 2.Dropdown_Dashboard_JA_039.jpg 2.Dropdown_Account_JA_014.jpg > G11n: JA,SC: Un translation issue occurred on the strings of different > dropdown lists. > --- > > Key: CLOUDSTACK-3519 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3519 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#G11n-56/G11n-57 > (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS & CS-Mgr Servers > Win7Entx64SP1 for Client machine >Reporter: Minying Bao > Fix For: 4.2.0 > > Attachments: 2.Dropdown_Account_JA_014.jpg, > 2.Dropdown_Account_SC_014.jpg, 2.Dropdown_Dashboard_JA_039.jpg, > 2.Dropdown_Dashboard_SC_039.jpg, JA-2.Dropdown.zip, SC-2.Dropdown.zip > > > Repro Steps > Setup Basic environments. > Login Web Portal with Japanese/Simplified Chinese as default. Check all the > strings of different dropdown lists. > Expected Result > All the strings should be translated to Japanese/Simplified Chinese. > Actual Result > A lot of un-translated strings display. > (Please refer to the more screenshots as below location: > Pactera WUXI FTP: 172.16.45.222 > /Temp/CloudPlatform/Campo/Un Translations issues) > Regression Info. > Build#G11n-56 -> Fail > Build#G11n-57 -> Fail -- 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] [Created] (CLOUDSTACK-3519) G11n: JA,SC: Un translation issue occurred on the strings of different dropdown lists.
Minying Bao created CLOUDSTACK-3519: --- Summary: G11n: JA,SC: Un translation issue occurred on the strings of different dropdown lists. Key: CLOUDSTACK-3519 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3519 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Build No.#G11n-56/G11n-57 (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) XenServer6.1 for Host Server CentOS6.3 for NFS & CS-Mgr Servers Win7Entx64SP1 for Client machine Reporter: Minying Bao Fix For: 4.2.0 Repro Steps Setup Basic environments. Login Web Portal with Japanese/Simplified Chinese as default. Check all the strings of different dropdown lists. Expected Result All the strings should be translated to Japanese/Simplified Chinese. Actual Result A lot of un-translated strings display. (Please refer to the more screenshots as below location: Pactera WUXI FTP: 172.16.45.222 /Temp/CloudPlatform/Campo/Un Translations issues) Regression Info. Build#G11n-56 -> Fail Build#G11n-57 -> Fail -- 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] [Updated] (CLOUDSTACK-3518) G11n: JA,SC: Un translation issue occurred on the strings of different UI Specifics.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minying Bao updated CLOUDSTACK-3518: Attachment: 1.UI Specific_Infrastructure_SecondaryStorage_JA_005.jpg 1.UI Specific_Dashboard_JA_003.jpg 1.UI Specific_Infrastructure_SecondaryStorage_SC_005.jpg 1.UI Specific_Dashboard_SC_003.jpg SC-1.UI Specific.zip JA-1.UI Specific.zip > G11n: JA,SC: Un translation issue occurred on the strings of different UI > Specifics. > - > > Key: CLOUDSTACK-3518 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3518 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Build No.#G11n-56/G11n-57 > (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) > XenServer6.1 for Host Server > CentOS6.3 for NFS & CS-Mgr Servers > Win7Entx64SP1 for Client machine >Reporter: Minying Bao > Fix For: 4.2.0 > > Attachments: 1.UI Specific_Dashboard_JA_003.jpg, 1.UI > Specific_Dashboard_SC_003.jpg, 1.UI > Specific_Infrastructure_SecondaryStorage_JA_005.jpg, 1.UI > Specific_Infrastructure_SecondaryStorage_SC_005.jpg, JA-1.UI Specific.zip, > SC-1.UI Specific.zip > > > Repro Steps > Setup Basic environments. > Login Web Portal with Japanese/Simplified Chinese as default. Check all the > strings of different UI Specifics. > Expected Result > All the strings should be translated to Japanese/Simplified Chinese. > Actual Result > A lot of un-translated strings display. > (Please refer to the more screenshots as below location: > Pactera WUXI FTP: 172.16.45.222 > /Temp/CloudPlatform/Campo/Un Translations issues) > Regression Info. > Build#G11n-56 -> Fail > Build#G11n-57 -> Fail -- 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] [Created] (CLOUDSTACK-3518) G11n: JA,SC: Un translation issue occurred on the strings of different UI Specifics.
Minying Bao created CLOUDSTACK-3518: --- Summary: G11n: JA,SC: Un translation issue occurred on the strings of different UI Specifics. Key: CLOUDSTACK-3518 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3518 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Build No.#G11n-56/G11n-57 (CloudStack-non-OSS-cloudstack-globalization-56-rhel6.3.tar.gz) XenServer6.1 for Host Server CentOS6.3 for NFS & CS-Mgr Servers Win7Entx64SP1 for Client machine Reporter: Minying Bao Fix For: 4.2.0 Repro Steps Setup Basic environments. Login Web Portal with Japanese/Simplified Chinese as default. Check all the strings of different UI Specifics. Expected Result All the strings should be translated to Japanese/Simplified Chinese. Actual Result A lot of un-translated strings display. (Please refer to the more screenshots as below location: Pactera WUXI FTP: 172.16.45.222 /Temp/CloudPlatform/Campo/Un Translations issues) Regression Info. Build#G11n-56 -> Fail Build#G11n-57 -> Fail -- 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] [Updated] (CLOUDSTACK-3516) [integrating an open-source SDN controller] design HTTP request using HttpClient package
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna updated CLOUDSTACK-3516: - Due Date: 17/Jul/13 > [integrating an open-source SDN controller] design HTTP request using > HttpClient package > > > Key: CLOUDSTACK-3516 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3516 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > > Making http request to Openflow controller -- 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] [Created] (CLOUDSTACK-3517) [integrating an open-source SDN controller] Using OF Controller like a VM
tuna created CLOUDSTACK-3517: Summary: [integrating an open-source SDN controller] Using OF Controller like a VM Key: CLOUDSTACK-3517 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3517 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna -- 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] [Created] (CLOUDSTACK-3516) [integrating an open-source SDN controller] design HTTP request using HttpClient package
tuna created CLOUDSTACK-3516: Summary: [integrating an open-source SDN controller] design HTTP request using HttpClient package Key: CLOUDSTACK-3516 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3516 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna Making http request to Openflow controller -- 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-3517) [integrating an open-source SDN controller] Using OF Controller like a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tuna resolved CLOUDSTACK-3517. -- Resolution: Implemented > [integrating an open-source SDN controller] Using OF Controller like a VM > - > > Key: CLOUDSTACK-3517 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3517 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: tuna >Assignee: tuna > Fix For: 4.2.0 > > -- 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] [Created] (CLOUDSTACK-3515) [integrating an open-source SDN controller] Prototype coding
tuna created CLOUDSTACK-3515: Summary: [integrating an open-source SDN controller] Prototype coding Key: CLOUDSTACK-3515 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3515 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: tuna Assignee: tuna making a prototype design (api, command, management class, resource, DAO, VO) -- 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
