[jira] [Resolved] (CLOUDSTACK-6863) [Automation] test_09_delete_detached_volume failing inconsistently with during simulator run
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye resolved CLOUDSTACK-6863.
Resolution: Fixed
> [Automation] test_09_delete_detached_volume failing inconsistently with
> during simulator run
> -
>
> Key: CLOUDSTACK-6863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6863
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-06-08T08:22:13-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'83431fd6-b825-4135-9ad8-2569d640c49c', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Unexpected
> exception'}, accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> >> begin captured stdout << -
> === TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: STARTED : TC: test_09_delete_detached_volume :::
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Delete Volume ID: 272cac5d-ae41-4050-9de4-8423f868cafd
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'account': u'test-account-TestCreateVolume-4E4YII',
> 'domainid': u'4c297c20-ef1e-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
> 'zoneid': u'b7c31495-c072-48b0-8a58-6f306766e5fb', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'createVolume', 'signature': 'EkCWUkVoE7Z70x8DFQq3YFEzuqQ=',
> 'diskofferingid': u'0445f51d-b324-49bf-9bec-f144d937a5da', 'response': 'json'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : createVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?account=test-account-TestCreateVolume-4E4YII&domainid=4c297c20-ef1e-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=b7c31495-c072-48b0-8a58-6f306766e5fb&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=createVolume&signature=EkCWUkVoE7Z70x8DFQq3YFEzuqQ%3D&diskofferingid=0445f51d-b324-49bf-9bec-f144d937a5da&response=json
> HTTP/1.1" 200 121
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === Jobid: 0cf9d61c-011a-421d-aff1-888bff6dd1ae Started ===
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'signature': 'N835/7k+Amcr5xbSUAn2G+mxTco=', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=0cf9d61c-011a-421d-aff1-888bff6dd1ae&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=queryAsyncJobResult&response=json&signature=N835%2F7k%2BAmcr5xbSUAn2G%2BmxTco%3D
> HTTP/1.1" 200 430
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T08:22:08-0700',
> cmd :
> u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae', jobresultcode : 0, jobinstanceid :
> u'2094423c-96fc-45af-a898-f058ef742c05', jobinstancetype : u'Volume',
> accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === JobId:0cf9d61c-011a-421d-aff1-888bff6dd1ae is Still Processing,
> Will TimeOut in:3595
> test_09_delete_detached_volume (integrat
[jira] [Closed] (CLOUDSTACK-6863) [Automation] test_09_delete_detached_volume failing inconsistently with during simulator run
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye closed CLOUDSTACK-6863.
--
Duplicate
> [Automation] test_09_delete_detached_volume failing inconsistently with
> during simulator run
> -
>
> Key: CLOUDSTACK-6863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6863
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-06-08T08:22:13-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'83431fd6-b825-4135-9ad8-2569d640c49c', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Unexpected
> exception'}, accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> >> begin captured stdout << -
> === TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: STARTED : TC: test_09_delete_detached_volume :::
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Delete Volume ID: 272cac5d-ae41-4050-9de4-8423f868cafd
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'account': u'test-account-TestCreateVolume-4E4YII',
> 'domainid': u'4c297c20-ef1e-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
> 'zoneid': u'b7c31495-c072-48b0-8a58-6f306766e5fb', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'createVolume', 'signature': 'EkCWUkVoE7Z70x8DFQq3YFEzuqQ=',
> 'diskofferingid': u'0445f51d-b324-49bf-9bec-f144d937a5da', 'response': 'json'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : createVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?account=test-account-TestCreateVolume-4E4YII&domainid=4c297c20-ef1e-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=b7c31495-c072-48b0-8a58-6f306766e5fb&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=createVolume&signature=EkCWUkVoE7Z70x8DFQq3YFEzuqQ%3D&diskofferingid=0445f51d-b324-49bf-9bec-f144d937a5da&response=json
> HTTP/1.1" 200 121
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === Jobid: 0cf9d61c-011a-421d-aff1-888bff6dd1ae Started ===
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'signature': 'N835/7k+Amcr5xbSUAn2G+mxTco=', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=0cf9d61c-011a-421d-aff1-888bff6dd1ae&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=queryAsyncJobResult&response=json&signature=N835%2F7k%2BAmcr5xbSUAn2G%2BmxTco%3D
> HTTP/1.1" 200 430
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T08:22:08-0700',
> cmd :
> u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae', jobresultcode : 0, jobinstanceid :
> u'2094423c-96fc-45af-a898-f058ef742c05', jobinstancetype : u'Volume',
> accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === JobId:0cf9d61c-011a-421d-aff1-888bff6dd1ae is Still Processing,
> Will TimeOut in:3595
> test_09_delete_detached_volume (integration.smoke.test_
[jira] [Reopened] (CLOUDSTACK-6863) [Automation] test_09_delete_detached_volume failing inconsistently with during simulator run
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye reopened CLOUDSTACK-6863:
Keeping open till product bug gets fixed
> [Automation] test_09_delete_detached_volume failing inconsistently with
> during simulator run
> -
>
> Key: CLOUDSTACK-6863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6863
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-06-08T08:22:13-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'83431fd6-b825-4135-9ad8-2569d640c49c', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Unexpected
> exception'}, accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> >> begin captured stdout << -
> === TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: STARTED : TC: test_09_delete_detached_volume :::
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Delete Volume ID: 272cac5d-ae41-4050-9de4-8423f868cafd
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'account': u'test-account-TestCreateVolume-4E4YII',
> 'domainid': u'4c297c20-ef1e-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
> 'zoneid': u'b7c31495-c072-48b0-8a58-6f306766e5fb', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'createVolume', 'signature': 'EkCWUkVoE7Z70x8DFQq3YFEzuqQ=',
> 'diskofferingid': u'0445f51d-b324-49bf-9bec-f144d937a5da', 'response': 'json'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : createVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?account=test-account-TestCreateVolume-4E4YII&domainid=4c297c20-ef1e-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=b7c31495-c072-48b0-8a58-6f306766e5fb&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=createVolume&signature=EkCWUkVoE7Z70x8DFQq3YFEzuqQ%3D&diskofferingid=0445f51d-b324-49bf-9bec-f144d937a5da&response=json
> HTTP/1.1" 200 121
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === Jobid: 0cf9d61c-011a-421d-aff1-888bff6dd1ae Started ===
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'signature': 'N835/7k+Amcr5xbSUAn2G+mxTco=', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=0cf9d61c-011a-421d-aff1-888bff6dd1ae&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=queryAsyncJobResult&response=json&signature=N835%2F7k%2BAmcr5xbSUAn2G%2BmxTco%3D
> HTTP/1.1" 200 430
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T08:22:08-0700',
> cmd :
> u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae', jobresultcode : 0, jobinstanceid :
> u'2094423c-96fc-45af-a898-f058ef742c05', jobinstancetype : u'Volume',
> accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === JobId:0cf9d61c-011a-421d-aff1-888bff6dd1ae is Still Processing,
> Will TimeOut in:3595
> test_09_delete_detac
[jira] [Created] (CLOUDSTACK-6990) VM console displays blank page.AgentControlChannelException in cloud.log
manasaveloori created CLOUDSTACK-6990:
-
Summary: VM console displays blank
page.AgentControlChannelException in cloud.log
Key: CLOUDSTACK-6990
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6990
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: SystemVM
Affects Versions: 4.4.0
Reporter: manasaveloori
Priority: Critical
Fix For: 4.4.0
Deployed Cloudstack using the build :
[root@RHEL63test ~]# cloudstack-sccs
9024ad14681858ac7caafaf86f267a213ce6b61c
Deployed a user VM.
Now try to open the console of any VM.
It is displaying blank page.
In CPVM cloud.log observed the following exception continuously:
2014-06-25 06:31:14,620 INFO [utils.exception.CSExceptionErrorCode] (Console
Proxy GC Thread:null) Could not find exception:
com.cloud.exception.AgentControlChannelException in error code list for
exceptions
2014-06-25 06:31:14,621 ERROR [resource.consoleproxy.ConsoleProxyResource]
(Console Proxy GC Thread:null) Unable to send out load info due to Unable to
post agent control request as link is not available
com.cloud.exception.AgentControlChannelException: Unable to post agent control
request as link is not available
at com.cloud.agent.Agent.postRequest(Agent.java:689)
at com.cloud.agent.Agent.postRequest(Agent.java:677)
at
com.cloud.agent.resource.consoleproxy.ConsoleProxyResource.reportLoadInfo(ConsoleProxyResource.java:418)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.consoleproxy.ConsoleProxy.reportLoadInfo(ConsoleProxy.java:227)
at
com.cloud.consoleproxy.ConsoleProxyGCThread.run(ConsoleProxyGCThread.java:102)
2014-06-25 06:31:14,621 DEBUG [cloud.consoleproxy.ConsoleProxyGCThread]
(Console Proxy GC Thread:null) Report load change : {
"connections": []
}
2014-06-25 06:31:14,897 INFO [cloud.agent.Agent] (Agent-Handler-4:null)
Reconnecting...
2014-06-25 06:31:14,897 INFO [utils.nio.NioClient] (Agent-Selector:null)
Connecting to 10.147.59.222:8250
Attaching the Ms logs and CPVM log.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6990) VM console displays blank page.AgentControlChannelException in cloud.log
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
manasaveloori updated CLOUDSTACK-6990:
--
Attachment: cloud.log
management-server.rar
> VM console displays blank page.AgentControlChannelException in cloud.log
>
>
> Key: CLOUDSTACK-6990
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6990
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM
>Affects Versions: 4.4.0
>Reporter: manasaveloori
>Priority: Critical
> Fix For: 4.4.0
>
> Attachments: cloud.log, management-server.rar
>
>
> Deployed Cloudstack using the build :
> [root@RHEL63test ~]# cloudstack-sccs
> 9024ad14681858ac7caafaf86f267a213ce6b61c
> Deployed a user VM.
> Now try to open the console of any VM.
> It is displaying blank page.
> In CPVM cloud.log observed the following exception continuously:
> 2014-06-25 06:31:14,620 INFO [utils.exception.CSExceptionErrorCode] (Console
> Proxy GC Thread:null) Could not find exception:
> com.cloud.exception.AgentControlChannelException in error code list for
> exceptions
> 2014-06-25 06:31:14,621 ERROR [resource.consoleproxy.ConsoleProxyResource]
> (Console Proxy GC Thread:null) Unable to send out load info due to Unable to
> post agent control request as link is not available
> com.cloud.exception.AgentControlChannelException: Unable to post agent
> control request as link is not available
> at com.cloud.agent.Agent.postRequest(Agent.java:689)
> at com.cloud.agent.Agent.postRequest(Agent.java:677)
> at
> com.cloud.agent.resource.consoleproxy.ConsoleProxyResource.reportLoadInfo(ConsoleProxyResource.java:418)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.cloud.consoleproxy.ConsoleProxy.reportLoadInfo(ConsoleProxy.java:227)
> at
> com.cloud.consoleproxy.ConsoleProxyGCThread.run(ConsoleProxyGCThread.java:102)
> 2014-06-25 06:31:14,621 DEBUG [cloud.consoleproxy.ConsoleProxyGCThread]
> (Console Proxy GC Thread:null) Report load change : {
> "connections": []
> }
> 2014-06-25 06:31:14,897 INFO [cloud.agent.Agent] (Agent-Handler-4:null)
> Reconnecting...
> 2014-06-25 06:31:14,897 INFO [utils.nio.NioClient] (Agent-Selector:null)
> Connecting to 10.147.59.222:8250
> Attaching the Ms logs and CPVM log.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6692) Service offering upgrade from non GPU to GPU is causing for windows 8 instance into repair state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043203#comment-14043203 ] Sanjay Tripathi commented on CLOUDSTACK-6692: - This issue is because of the conflict between PV drivers and VGPU drivers trying to access the same device_id in XS. Will get fixed as a part of fix for CLOUDSTACK-6453. > Service offering upgrade from non GPU to GPU is causing for windows 8 > instance into repair state > > > Key: CLOUDSTACK-6692 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6692 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, XenServer >Affects Versions: 4.4.0 >Reporter: Sailaja Mada >Assignee: Sanjay Tripathi >Priority: Critical > Fix For: 4.4.0 > > Attachments: vgpulogs.zip > > > Steps: > 1. Configure Adv zone with Xen 6.2.5 > 2. Deploy windows 8 VM . > 3. Install PV drivers . Stop the VM and create template from ROOT volume > 4. Deploy windows 8 instance using this template with non GPU offering > 5. Stop the VM > 6. Upgrade the service offering to GPU offering (K2 260) > 7. Tried to start the VM. Start VM is completed . > 8. View Console of this VM - Noticed that its moved to Automatic Repair state > and VM moved to stopped state later from XS and then from Cloudstack > Observation: > Service offering upgrade from non GPU to GPU is causing for windows 8 > instance into repair state -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5005) issue with stopping vms parallelly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043280#comment-14043280
]
Daan Hoogland commented on CLOUDSTACK-5005:
---
marked as future because of lack of activity
> issue with stopping vms parallelly
> ---
>
> Key: CLOUDSTACK-5005
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5005
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.1
>Reporter: prashant kumar mishra
>Assignee: Kelven Yang
>Priority: Critical
> Fix For: Future
>
> Attachments: MS_XEN_DB.rar
>
>
> steps to reproduce
> ---
> 1-prepare CS setup with xen 6.1
> 2-set execute.in.sequence.hypervisor.commands and
> execute.in.sequence.network.element.commands to false
> 3-Restart MS
> 4-deploy 35 vms parallelly with default centOS template
> 5-try to stop all uservms using script
> Expected
> -
> All vms should get stopped ,
> Actual
>
> before vms went in stopped state , Log show error messages
> Logs
>
> [root@localhost ~]# grep "job-436"
> /var/log/cloudstack/management/management-server.log
> 2013-10-30 12:21:57,817 DEBUG [cloud.async.AsyncJobManagerImpl]
> (ApiServer-1:null) submit async job-436 = [
> 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ], details: AsyncJobVO {id:436, userId:
> 1, accountId: 1, sessionKey: null, instanceType: VirtualMachine, instanceId:
> 78, cmd: org.apache.cloudstack.api.command.user.vm.StopVMCmd, cmdOriginator:
> null, cmdInfo:
> {"id":"78","cmdEventType":"VM.STOP","ctxUserId":"1","httpmethod":"GET","ctxAccountId":"1","ctxStartEventId":"1384"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7484181839895,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-10-30 12:21:57,818 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> Executing org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-436 = [
> 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]
> 2013-10-30 12:21:57,941 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> ControlledEntity name is:com.cloud.vm.VirtualMachine
> 2013-10-30 12:21:58,056 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> ControlledEntity name is:com.cloud.uservm.UserVm
> 2013-10-30 12:21:58,111 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> ControlledEntity name is:com.cloud.network.router.VirtualRouter
> 2013-10-30 12:21:58,528 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) VM
> state transitted from :Running to Stopping with event: StopRequestedvm's
> original host id: 3 new host id: 3 host id before state transition: 3
> 2013-10-30 12:21:58,696 DEBUG [agent.transport.Request]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Seq
> 3-125568146: Sending { Cmd , MgmtId: 7484181839895, via: 3, Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-78-VM","wait":0}}]
> }
> 2013-10-30 12:21:58,696 DEBUG [agent.transport.Request]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Seq
> 3-125568146: Executing: { Cmd , MgmtId: 7484181839895, via: 3, Ver: v1,
> Flags: 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-78-VM","wait":0}}]
> }
> 2013-10-30 12:22:58,051 DEBUG [agent.transport.Request]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Seq
> 3-125568146: Received: { Ans: , MgmtId: 7484181839895, via: 3, Ver: v1,
> Flags: 10, { StopAnswer } }
> 2013-10-30 12:22:58,078 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> VM[User|f1ad8bfe-b9a4-4669-a37c-f0edb2f0098f] is stopped on the host.
> Proceeding to release resource held.
> 2013-10-30 12:22:58,088 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Service
> SecurityGroup is not supported in the network id=204
> 2013-10-30 12:22:58,095 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> Changing active number of nics for network id=204 on -1
> 2013-10-30 12:22:58,123 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc
[jira] [Updated] (CLOUDSTACK-5005) issue with stopping vms parallelly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland updated CLOUDSTACK-5005:
--
Fix Version/s: (was: 4.4.0)
Future
> issue with stopping vms parallelly
> ---
>
> Key: CLOUDSTACK-5005
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5005
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.1
>Reporter: prashant kumar mishra
>Assignee: Kelven Yang
>Priority: Critical
> Fix For: Future
>
> Attachments: MS_XEN_DB.rar
>
>
> steps to reproduce
> ---
> 1-prepare CS setup with xen 6.1
> 2-set execute.in.sequence.hypervisor.commands and
> execute.in.sequence.network.element.commands to false
> 3-Restart MS
> 4-deploy 35 vms parallelly with default centOS template
> 5-try to stop all uservms using script
> Expected
> -
> All vms should get stopped ,
> Actual
>
> before vms went in stopped state , Log show error messages
> Logs
>
> [root@localhost ~]# grep "job-436"
> /var/log/cloudstack/management/management-server.log
> 2013-10-30 12:21:57,817 DEBUG [cloud.async.AsyncJobManagerImpl]
> (ApiServer-1:null) submit async job-436 = [
> 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ], details: AsyncJobVO {id:436, userId:
> 1, accountId: 1, sessionKey: null, instanceType: VirtualMachine, instanceId:
> 78, cmd: org.apache.cloudstack.api.command.user.vm.StopVMCmd, cmdOriginator:
> null, cmdInfo:
> {"id":"78","cmdEventType":"VM.STOP","ctxUserId":"1","httpmethod":"GET","ctxAccountId":"1","ctxStartEventId":"1384"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 7484181839895,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-10-30 12:21:57,818 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> Executing org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-436 = [
> 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]
> 2013-10-30 12:21:57,941 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> ControlledEntity name is:com.cloud.vm.VirtualMachine
> 2013-10-30 12:21:58,056 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> ControlledEntity name is:com.cloud.uservm.UserVm
> 2013-10-30 12:21:58,111 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> ControlledEntity name is:com.cloud.network.router.VirtualRouter
> 2013-10-30 12:21:58,528 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) VM
> state transitted from :Running to Stopping with event: StopRequestedvm's
> original host id: 3 new host id: 3 host id before state transition: 3
> 2013-10-30 12:21:58,696 DEBUG [agent.transport.Request]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Seq
> 3-125568146: Sending { Cmd , MgmtId: 7484181839895, via: 3, Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-78-VM","wait":0}}]
> }
> 2013-10-30 12:21:58,696 DEBUG [agent.transport.Request]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Seq
> 3-125568146: Executing: { Cmd , MgmtId: 7484181839895, via: 3, Ver: v1,
> Flags: 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-78-VM","wait":0}}]
> }
> 2013-10-30 12:22:58,051 DEBUG [agent.transport.Request]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Seq
> 3-125568146: Received: { Ans: , MgmtId: 7484181839895, via: 3, Ver: v1,
> Flags: 10, { StopAnswer } }
> 2013-10-30 12:22:58,078 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> VM[User|f1ad8bfe-b9a4-4669-a37c-f0edb2f0098f] is stopped on the host.
> Proceeding to release resource held.
> 2013-10-30 12:22:58,088 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Service
> SecurityGroup is not supported in the network id=204
> 2013-10-30 12:22:58,095 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ])
> Changing active number of nics for network id=204 on -1
> 2013-10-30 12:22:58,123 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-122:job-436 = [ 432f8bd7-8f4b-4e72-b69b-b148fc1733dc ]) Asking
> VirtualRouter to release
>
[jira] [Updated] (CLOUDSTACK-5736) KVM - Recurring Snapshots - Snapshots reported as being in "BackedUp" state even though a Nullpointer exception is seen during post processing of snapshot.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-5736: -- Fix Version/s: (was: 4.4.0) Future > KVM - Recurring Snapshots - Snapshots reported as being in "BackedUp" state > even though a Nullpointer exception is seen during post processing of > snapshot. > > > Key: CLOUDSTACK-5736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: Kelven Yang >Priority: Critical > Fix For: Future > > Attachments: kvm.rar > > > Set up: > Advanced zone set up with 2 KVM (rhel 63) hosts. > Steps to reproduce the problem: > Deploy about 17 Vms in both hosts. > Start "Hourly" snapshot for all the ROOT volumes of these Vms. > Snapshots were reported as being in "BackedUp" state even though Nullpointer > exception is seen during post processing of snapshot. > Following exception seen in management server logs: > 014-01-02 19:57:53,560 DEBUG [c.c.s.s.SnapshotManagerImpl] > (Job-Executor-166:ctx-c0f157b4 ctx-2654c4f7) post process snapshot failed > java.lang.NullPointerException > at > com.cloud.storage.snapshot.SnapshotManagerImpl.postCreateSnapshot(SnapshotManagerImpl.java:374) > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:954) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy160.takeSnapshot(Unknown Source) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1371) > at > com.cloud.storage.VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VolumeApiServiceImpl.java:1723) > at > com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2478) > at sun.reflect.GeneratedMethodAccessor524.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy195.handleVmWorkJob(Unknown Source) > at > com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManaged
[jira] [Commented] (CLOUDSTACK-5736) KVM - Recurring Snapshots - Snapshots reported as being in "BackedUp" state even though a Nullpointer exception is seen during post processing of snapshot.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043282#comment-14043282 ] Daan Hoogland commented on CLOUDSTACK-5736: --- moving out of 4.4 to future because of lack of activity > KVM - Recurring Snapshots - Snapshots reported as being in "BackedUp" state > even though a Nullpointer exception is seen during post processing of > snapshot. > > > Key: CLOUDSTACK-5736 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5736 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: Kelven Yang >Priority: Critical > Fix For: Future > > Attachments: kvm.rar > > > Set up: > Advanced zone set up with 2 KVM (rhel 63) hosts. > Steps to reproduce the problem: > Deploy about 17 Vms in both hosts. > Start "Hourly" snapshot for all the ROOT volumes of these Vms. > Snapshots were reported as being in "BackedUp" state even though Nullpointer > exception is seen during post processing of snapshot. > Following exception seen in management server logs: > 014-01-02 19:57:53,560 DEBUG [c.c.s.s.SnapshotManagerImpl] > (Job-Executor-166:ctx-c0f157b4 ctx-2654c4f7) post process snapshot failed > java.lang.NullPointerException > at > com.cloud.storage.snapshot.SnapshotManagerImpl.postCreateSnapshot(SnapshotManagerImpl.java:374) > at > com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:954) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy160.takeSnapshot(Unknown Source) > at > org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1371) > at > com.cloud.storage.VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VolumeApiServiceImpl.java:1723) > at > com.cloud.storage.VolumeApiServiceImpl.handleVmWorkJob(VolumeApiServiceImpl.java:2478) > at sun.reflect.GeneratedMethodAccessor524.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy195.handleVmWorkJob(Unknown Source) > at > com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:99) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:522) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.ap
[jira] [Updated] (CLOUDSTACK-5738) Recurring Snapshots - Few Snapshots are stuck in "Creating" state for more than 30 minutes.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-5738: -- Fix Version/s: (was: 4.4.0) Future > Recurring Snapshots - Few Snapshots are stuck in "Creating" state for more > than 30 minutes. > --- > > Key: CLOUDSTACK-5738 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5738 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: Kelven Yang >Priority: Critical > Fix For: Future > > Attachments: kvm.rar > > > KVM - Parallel Snapshots - Few Snapshots are stuck in "Creating" state for > more than 30 minutes. > Set up: > Advanced zone set up with 2 KVM (rhel 63) hosts. > Steps to reproduce the problem: > Deploy about 17 Vms in both hosts. > Start "Hourly" snapshot for all the ROOT volumes of these Vms. > Few Snapshots are stuck in "Creating" state for more than 30 minutes now. > mysql> select id,volume_id,name,status,created from snapshots ; > ++---+-+---+-+ > | id | volume_id | name| status > | created | > ++---+-+---+-+ > | 1 | 3 | TestVM-1_ROOT-3_20131231011723 | > Destroyed | 2013-12-31 01:17:23 | > | 2 | 5 | TestVM-tiny-host-0ps-0-0_ROOT-5_20131231222951 | > Destroyed | 2013-12-31 22:29:51 | > | 3 |10 | test-new_ROOT-10_20140102201054 | BackedUp > | 2014-01-02 20:10:54 | > | 4 |22 | TestVM-tiny-host-0ps-0-6_ROOT-22_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 5 |21 | TestVM-tiny-host-0ps-0-5_ROOT-21_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 6 |20 | TestVM-tiny-host-0ps-0-4_ROOT-20_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 7 |19 | TestVM-tiny-host-0ps-0-3_ROOT-19_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 8 |18 | TestVM-tiny-host-0ps-0-2_ROOT-18_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 9 |17 | TestVM-tiny-host-0ps-0-1_ROOT-17_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 10 |16 | TestVM-tiny-host-0ps-0-0_ROOT-16_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 11 |14 | TestVM-1_ROOT-14_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 12 |31 | TestVM-tiny-host-1ps-0-5_ROOT-31_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 13 |30 | TestVM-tiny-host-1ps-0-4_ROOT-30_20140102234419 | Error > | 2014-01-02 23:44:19 | > | 14 |29 | TestVM-tiny-host-1ps-0-3_ROOT-29_20140102234419 | Error > | 2014-01-02 23:44:19 | > | 15 |28 | TestVM-tiny-host-1ps-0-2_ROOT-28_20140102234419 | Error > | 2014-01-02 23:44:19 | > | 16 |27 | TestVM-tiny-host-1ps-0-1_ROOT-27_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 17 |26 | TestVM-tiny-host-1ps-0-0_ROOT-26_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 18 |25 | TestVM-tiny-host-0ps-0-9_ROOT-25_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 19 |24 | TestVM-tiny-host-0ps-0-8_ROOT-24_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 20 |23 | TestVM-tiny-host-0ps-0-7_ROOT-23_20140102234419 | > BackingUp | 2014-01-02 23:44:19 | > | 21 |22 | TestVM-tiny-host-0ps-0-6_ROOT-22_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 22 |21 | TestVM-tiny-host-0ps-0-5_ROOT-21_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 23 |20 | TestVM-tiny-host-0ps-0-4_ROOT-20_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 24 |18 | TestVM-tiny-host-0ps-0-2_ROOT-18_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 25 |17 | TestVM-tiny-host-0ps-0-1_ROOT-17_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 26 |31 | TestVM-tiny-host-1ps-0-5_ROOT-31_20140103014418 | BackedUp > | 2014-01-03 01:44:18 | > | 27 |30 | TestVM-tiny-host-1ps-0-4_ROOT-30_20140103014419 | BackedUp > | 2014-01-03 01:44:19 | > | 28 |29 | TestVM-tiny-host-1ps-0-3_ROOT-29_20140103014419 | BackedUp > | 2014-01-03 01:44:19 | > | 29 |28 | TestVM-tiny-host-1ps-0-2_ROOT-28_20140103014419 | Error > | 2014-01-03 01:44:19 | > | 30 |27 | TestVM-tiny-host-1ps-0-1_ROOT-27_20140103014419 | BackedUp > | 2014-01
[jira] [Commented] (CLOUDSTACK-5738) Recurring Snapshots - Few Snapshots are stuck in "Creating" state for more than 30 minutes.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043284#comment-14043284 ] Daan Hoogland commented on CLOUDSTACK-5738: --- moving out of 4.4 to future due to lack of activity > Recurring Snapshots - Few Snapshots are stuck in "Creating" state for more > than 30 minutes. > --- > > Key: CLOUDSTACK-5738 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5738 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 > Environment: Build from 4.3 >Reporter: Sangeetha Hariharan >Assignee: Kelven Yang >Priority: Critical > Fix For: Future > > Attachments: kvm.rar > > > KVM - Parallel Snapshots - Few Snapshots are stuck in "Creating" state for > more than 30 minutes. > Set up: > Advanced zone set up with 2 KVM (rhel 63) hosts. > Steps to reproduce the problem: > Deploy about 17 Vms in both hosts. > Start "Hourly" snapshot for all the ROOT volumes of these Vms. > Few Snapshots are stuck in "Creating" state for more than 30 minutes now. > mysql> select id,volume_id,name,status,created from snapshots ; > ++---+-+---+-+ > | id | volume_id | name| status > | created | > ++---+-+---+-+ > | 1 | 3 | TestVM-1_ROOT-3_20131231011723 | > Destroyed | 2013-12-31 01:17:23 | > | 2 | 5 | TestVM-tiny-host-0ps-0-0_ROOT-5_20131231222951 | > Destroyed | 2013-12-31 22:29:51 | > | 3 |10 | test-new_ROOT-10_20140102201054 | BackedUp > | 2014-01-02 20:10:54 | > | 4 |22 | TestVM-tiny-host-0ps-0-6_ROOT-22_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 5 |21 | TestVM-tiny-host-0ps-0-5_ROOT-21_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 6 |20 | TestVM-tiny-host-0ps-0-4_ROOT-20_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 7 |19 | TestVM-tiny-host-0ps-0-3_ROOT-19_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 8 |18 | TestVM-tiny-host-0ps-0-2_ROOT-18_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 9 |17 | TestVM-tiny-host-0ps-0-1_ROOT-17_20140102234418 | BackedUp > | 2014-01-02 23:44:18 | > | 10 |16 | TestVM-tiny-host-0ps-0-0_ROOT-16_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 11 |14 | TestVM-1_ROOT-14_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 12 |31 | TestVM-tiny-host-1ps-0-5_ROOT-31_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 13 |30 | TestVM-tiny-host-1ps-0-4_ROOT-30_20140102234419 | Error > | 2014-01-02 23:44:19 | > | 14 |29 | TestVM-tiny-host-1ps-0-3_ROOT-29_20140102234419 | Error > | 2014-01-02 23:44:19 | > | 15 |28 | TestVM-tiny-host-1ps-0-2_ROOT-28_20140102234419 | Error > | 2014-01-02 23:44:19 | > | 16 |27 | TestVM-tiny-host-1ps-0-1_ROOT-27_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 17 |26 | TestVM-tiny-host-1ps-0-0_ROOT-26_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 18 |25 | TestVM-tiny-host-0ps-0-9_ROOT-25_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 19 |24 | TestVM-tiny-host-0ps-0-8_ROOT-24_20140102234419 | BackedUp > | 2014-01-02 23:44:19 | > | 20 |23 | TestVM-tiny-host-0ps-0-7_ROOT-23_20140102234419 | > BackingUp | 2014-01-02 23:44:19 | > | 21 |22 | TestVM-tiny-host-0ps-0-6_ROOT-22_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 22 |21 | TestVM-tiny-host-0ps-0-5_ROOT-21_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 23 |20 | TestVM-tiny-host-0ps-0-4_ROOT-20_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 24 |18 | TestVM-tiny-host-0ps-0-2_ROOT-18_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 25 |17 | TestVM-tiny-host-0ps-0-1_ROOT-17_20140103014418 | > BackingUp | 2014-01-03 01:44:18 | > | 26 |31 | TestVM-tiny-host-1ps-0-5_ROOT-31_20140103014418 | BackedUp > | 2014-01-03 01:44:18 | > | 27 |30 | TestVM-tiny-host-1ps-0-4_ROOT-30_20140103014419 | BackedUp > | 2014-01-03 01:44:19 | > | 28 |29 | TestVM-tiny-host-1ps-0-3_ROOT-29_20140103014419 | BackedUp > | 2014-01-03 01:44:19 | > | 29 |28 | TestVM-tiny-host-1ps-0-2_ROOT-28_20140103014419 | Error > | 2014-01-03 01:44:19 | > | 30 |27 | TestVM-tiny-host-1ps-0-1_
[jira] [Closed] (CLOUDSTACK-6863) [Automation] test_09_delete_detached_volume failing inconsistently with during simulator run
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Aradhye closed CLOUDSTACK-6863.
--
Resolution: Fixed
> [Automation] test_09_delete_detached_volume failing inconsistently with
> during simulator run
> -
>
> Key: CLOUDSTACK-6863
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6863
> Project: CloudStack
> Issue Type: Test
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Affects Versions: 4.4.0
>Reporter: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.4.0
>
>
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-06-08T08:22:13-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'83431fd6-b825-4135-9ad8-2569d640c49c', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Unexpected
> exception'}, accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> >> begin captured stdout << -
> === TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: STARTED : TC: test_09_delete_detached_volume :::
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Delete Volume ID: 272cac5d-ae41-4050-9de4-8423f868cafd
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'account': u'test-account-TestCreateVolume-4E4YII',
> 'domainid': u'4c297c20-ef1e-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
> 'zoneid': u'b7c31495-c072-48b0-8a58-6f306766e5fb', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'createVolume', 'signature': 'EkCWUkVoE7Z70x8DFQq3YFEzuqQ=',
> 'diskofferingid': u'0445f51d-b324-49bf-9bec-f144d937a5da', 'response': 'json'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : createVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?account=test-account-TestCreateVolume-4E4YII&domainid=4c297c20-ef1e-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=b7c31495-c072-48b0-8a58-6f306766e5fb&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=createVolume&signature=EkCWUkVoE7Z70x8DFQq3YFEzuqQ%3D&diskofferingid=0445f51d-b324-49bf-9bec-f144d937a5da&response=json
> HTTP/1.1" 200 121
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === Jobid: 0cf9d61c-011a-421d-aff1-888bff6dd1ae Started ===
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'signature': 'N835/7k+Amcr5xbSUAn2G+mxTco=', 'apiKey':
> u'itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=0cf9d61c-011a-421d-aff1-888bff6dd1ae&apiKey=itSv94rGboiox-l2LC0VMd7G23t_AbSJWTe_itqpq662L3ZycKb8e-YR6nGLeOXj139gHU4E4OQM30re12HD4A&command=queryAsyncJobResult&response=json&signature=N835%2F7k%2BAmcr5xbSUAn2G%2BmxTco%3D
> HTTP/1.1" 200 430
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T08:22:08-0700',
> cmd :
> u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
> userid : u'4c29db3e-ef1e-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
> u'0cf9d61c-011a-421d-aff1-888bff6dd1ae', jobresultcode : 0, jobinstanceid :
> u'2094423c-96fc-45af-a898-f058ef742c05', jobinstancetype : u'Volume',
> accountid : u'4c29b190-ef1e-11e3-a86b-00163e0af42c'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === JobId:0cf9d61c-011a-421d-aff1-888bff6dd1ae is Still Processing,
> Will TimeOut in:3595
> test_09_delete_detached_volume (integration.
[jira] [Reopened] (CLOUDSTACK-6875) test_volumes.TestVolumes.test_09_delete_detached_volume is failing on simulator runs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Girish Shilamkar reopened CLOUDSTACK-6875:
--
Keeping open till linked product bug gets fixed
> test_volumes.TestVolumes.test_09_delete_detached_volume is failing on
> simulator runs
>
>
> Key: CLOUDSTACK-6875
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6875
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Bharat Kumar
>Assignee: Girish Shilamkar
>
> Error Message
> Job failed: {jobprocstatus : 0, created : u'2014-06-08T20:26:20-0700', cmd :
> u'org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin',
> userid : u'36a2cda6-ef83-11e3-a86b-00163e0af42c', jobstatus : 2, jobid :
> u'b263a941-29b1-4ab8-9c00-7a0d2678b591', jobresultcode : 530, jobresulttype :
> u'object', jobresult : {errorcode : 530, errortext : u'Unexpected
> exception'}, accountid : u'36a29ade-ef83-11e3-a86b-00163e0af42c'}
> >> begin captured stdout << -
> === TestName: test_09_delete_detached_volume | Status : EXCEPTION ===
> - >> end captured stdout << --
> >> begin captured logging <<
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: STARTED : TC: test_09_delete_detached_volume :::
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Delete Volume ID: 24051890-92ad-4cee-8ca3-119d278b072a
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'account': u'test-account-TestCreateVolume-N2SRV2',
> 'domainid': u'36a27fb8-ef83-11e3-a86b-00163e0af42c', 'name': 'Test Volume',
> 'zoneid': u'ef5040e4-6e78-433b-a21a-656a7ab31e80', 'apiKey':
> u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
> 'command': 'createVolume', 'signature': 'O0mZxBTYte8bIWPhtBYKUycq8Yo=',
> 'diskofferingid': u'92b2888e-c624-4042-82b4-632bed2bb38d', 'response': 'json'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : createVolume===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?account=test-account-TestCreateVolume-N2SRV2&domainid=36a27fb8-ef83-11e3-a86b-00163e0af42c&name=Test+Volume&zoneid=ef5040e4-6e78-433b-a21a-656a7ab31e80&apiKey=Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ&command=createVolume&signature=O0mZxBTYte8bIWPhtBYKUycq8Yo%3D&diskofferingid=92b2888e-c624-4042-82b4-632bed2bb38d&response=json
> HTTP/1.1" 200 121
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === Jobid: 2249fb73-7560-4d22-a7f9-dba0507b096e Started ===
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Payload: {'signature': '8di/lZIPnn9qCgFh0fHVVrH7/8U=', 'apiKey':
> u'Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ',
> 'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
> u'2249fb73-7560-4d22-a7f9-dba0507b096e'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Sending GET Cmd : queryAsyncJobResult===
> requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
> (1): 172.16.88.23
> requests.packages.urllib3.connectionpool: DEBUG: "GET
> /client/api?jobid=2249fb73-7560-4d22-a7f9-dba0507b096e&apiKey=Qj0GwLB-3JHedsfK1fMgeybPzQuxKvXOOkIh-WNqEuJzupMkPVV7gCa7ZIV6jMwu1bIBqZhJAKd-TWfLH7XBXQ&command=queryAsyncJobResult&response=json&signature=8di%2FlZIPnn9qCgFh0fHVVrH7%2F8U%3D
> HTTP/1.1" 200 430
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: Response : {jobprocstatus : 0, created : u'2014-06-08T20:26:14-0700',
> cmd :
> u'org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin',
> userid : u'36a2cda6-ef83-11e3-a86b-00163e0af42c', jobstatus : 0, jobid :
> u'2249fb73-7560-4d22-a7f9-dba0507b096e', jobresultcode : 0, jobinstanceid :
> u'c936802c-42f3-4ff3-9eb2-dd003517a8ef', jobinstancetype : u'Volume',
> accountid : u'36a29ade-ef83-11e3-a86b-00163e0af42c'}
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEBUG: === JobId:2249fb73-7560-4d22-a7f9-dba0507b096e is Still Processing,
> Will TimeOut in:3595
> test_09_delete_detached_volume (integration.smoke.test_volumes.TestVolumes):
> DEB
[jira] [Created] (CLOUDSTACK-6991) VM does not get expunged even after waiting for 10 times the expunge interval time
Gaurav Aradhye created CLOUDSTACK-6991: -- Summary: VM does not get expunged even after waiting for 10 times the expunge interval time Key: CLOUDSTACK-6991 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6991 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, KVM Affects Versions: 4.4.0 Environment: Observed on KVM Reporter: Gaurav Aradhye Fix For: 4.4.0 Create a VM and destroy it. VM should get expunged after expunge interval, but it stays in "Destroyed" state. test_09_expunge_vm failing due to this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6992) [Portable_IP] All tests failed from advanced regression suite test_portable_ip.py
Sanjeev N created CLOUDSTACK-6992: - Summary: [Portable_IP] All tests failed from advanced regression suite test_portable_ip.py Key: CLOUDSTACK-6992 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6992 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Environment: Latest build from 4.4 Reporter: Sanjeev N Priority: Critical Fix For: 4.4.0 [Portable_IP] All tests failed from advanced regression suite test_portable_ip.py In this test_portable_ip.py file every test method has the following line: portable_ip_range_services = getPortableIpRangeServices(self.config) However self.config is not defined. So we are seeing following error from the test run: 'NoneType' object has no attribute 'startip' >> begin captured stdout << - === TestName: test_associate_ip_address | Status : EXCEPTION === test_associate_ip_address (integration.component.test_portable_ip.TestAssociatePublicIp): DEBUG: STARTED : TC: test_associate_ip_address ::: test_associate_ip_address (integration.component.test_portable_ip.TestAssociatePublicIp): CRITICAL: EXCEPTION: test_associate_ip_address: ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7/unittest/case.py", line 323, in run\n self.setUp()\n', ' File "/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_portable_ip.py", line 639, in setUp\nportable_ip_range_services = getPortableIpRangeServices(self.config)\n', ' File "/local/jenkins/workspace/xenrt-reg-adv-xs/work.57/env/local/lib/python2.7/site-packages/marvin/lib/common.py", line 1198, in getPortableIpRangeServices\nif config.portableIpRange.startip:\n', "AttributeError: 'NoneType' object has no attribute 'startip'\n"] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6926) Usage service fails to start when java 1.6 is not installed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043358#comment-14043358 ] ASF subversion and git services commented on CLOUDSTACK-6926: - Commit c468228fe807c621decc5919dadae9bcbb38c753 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c468228 ] CLOUDSTACK-6926: removed hard coded jdk dirs and setting java home using readlink and dirname > Usage service fails to start when java 1.6 is not installed > --- > > Key: CLOUDSTACK-6926 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6926 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Usage >Affects Versions: 4.2.1 >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > > was able to start only after editing JDK_DIRS in /etc/init.d/cloudstack-usage > it is searching only 1.6 java install directories by default -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6747: -- Fix Version/s: Future > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland >Priority: Minor > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland reassigned CLOUDSTACK-6747: - Assignee: Daan Hoogland > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland >Priority: Minor > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland updated CLOUDSTACK-6747: -- Priority: Major (was: Minor) > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043397#comment-14043397 ] Daan Hoogland commented on CLOUDSTACK-6747: --- fix seems simple: create a more forgiving check and use that instead of the validGuestCidrList check will fix for master but as we ran into this as well we might put effort into backporting increased level to major as this is counter intuitive and restrictive on the functionality of ACS > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043408#comment-14043408 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 018b471ad300ea0987e52d6b42dde71387de8c5b in cloudstack's branch refs/heads/master from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=018b471 ] CLOUDSTACK-6747 test to allow all cidrs on other end of vpc, public or private > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043457#comment-14043457 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 17850c7aff432a504d65a34d2f22ca7e1952a770 in cloudstack's branch refs/heads/master from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=17850c7 ] CLOUDSTACK-6747: call a more forgiving test on the supplied peer cidr-list > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6993) Missing usage stats for network traffic
Nux created CLOUDSTACK-6993: --- Summary: Missing usage stats for network traffic Key: CLOUDSTACK-6993 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6993 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.3.0 Environment: CentOS 6.5 HV and Mgmt, KVM/libvirt, ADV zone + SG Reporter: Nux As per this thread there seems to be a bug affecting at least Adv zone + SG and Basic zones; the usage stats for network are missing completely. http://www.mail-archive.com/dev@cloudstack.apache.org/msg31263.html There are no obvious errors anywhere, no exception in the logs and so on. The API will simply not show any data when "listusagerecords" is called with type "4" or "5"; the cloud_usage DB is also completely missing any data of these types. It looks like no data is actually inserted in the DB, so the problem may lie at a lower level. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6993) Missing usage stats for network traffic
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043521#comment-14043521 ] Nux commented on CLOUDSTACK-6993: - The bug doesn't seem to be affecting Adv zones without SG rules. > Missing usage stats for network traffic > --- > > Key: CLOUDSTACK-6993 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6993 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.3.0 > Environment: CentOS 6.5 HV and Mgmt, KVM/libvirt, ADV zone + SG >Reporter: Nux > Labels: kvm, stats, usage > > As per this thread there seems to be a bug affecting at least Adv zone + SG > and Basic zones; the usage stats for network are missing completely. > http://www.mail-archive.com/dev@cloudstack.apache.org/msg31263.html > There are no obvious errors anywhere, no exception in the logs and so on. > The API will simply not show any data when "listusagerecords" is called with > type "4" or "5"; the cloud_usage DB is also completely missing any data of > these types. > It looks like no data is actually inserted in the DB, so the problem may lie > at a lower level. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043578#comment-14043578 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 218c4713ae796bcb0002f12421d24dfee9a5320f in cloudstack's branch refs/heads/master from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=218c471 ] CLOUDSTACK-6747 test for test to allow all cidrs on other end of a vpc > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043590#comment-14043590 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit d90b8d88ed16aae91759a287c1c3f527d4d2cb18 in cloudstack's branch refs/heads/master from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d90b8d8 ] Revert "CLOUDSTACK-6747 test for test to allow all cidrs on other end of a vpc" This reverts commit 218c4713ae796bcb0002f12421d24dfee9a5320f. > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043595#comment-14043595 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 3268f5bd1f2175ccd919ee7195d69b05d5b3f3e2 in cloudstack's branch refs/heads/master from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3268f5b ] CLOUDSTACK-6747 test for test to allow all cidrs on other end of a vpc > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6994) [Automation] Secondary storage counts for a project does not include the resorce counts of accounts other than the admin account
Ashutosk Kelkar created CLOUDSTACK-6994: --- Summary: [Automation] Secondary storage counts for a project does not include the resorce counts of accounts other than the admin account Key: CLOUDSTACK-6994 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6994 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Environment: KVM Reporter: Ashutosk Kelkar Fix For: 4.4.0 Observed on KVM. Create an account A. Create project in the account. Create an account B and add account to project. Register a template with the account B. Check secondary storage count for project. It should be of template size. But it is still 0. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043602#comment-14043602 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit c05a007536af3e8ad628f77beda88b2d99129c4e in cloudstack's branch refs/heads/4.3 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c05a007 ] CLOUDSTACK-6747 test to allow all cidrs on other end of vpc, public or private (cherry picked from commit 018b471ad300ea0987e52d6b42dde71387de8c5b) > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043603#comment-14043603 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 5673c036c0307b873ebaabd39cbc319ecd0ee977 in cloudstack's branch refs/heads/4.3 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5673c03 ] CLOUDSTACK-6747 test for test to allow all cidrs on other end of a vpc (cherry picked from commit 3268f5bd1f2175ccd919ee7195d69b05d5b3f3e2) Conflicts: utils/test/com/cloud/utils/net/NetUtilsTest.java > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043604#comment-14043604 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 8d0f49adddc973de39aa48010e0ba64b8d46b9f2 in cloudstack's branch refs/heads/4.3 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8d0f49a ] CLOUDSTACK-6747: call a more forgiving test on the supplied peer cidr-list (cherry picked from commit 17850c7aff432a504d65a34d2f22ca7e1952a770) Conflicts: api/src/org/apache/cloudstack/api/command/user/vpn/CreateVpnCustomerGatewayCmd.java server/src/com/cloud/network/vpn/Site2SiteVpnManagerImpl.java > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043608#comment-14043608 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 8cb2a878156b5a78991869a565e84ff62b61da93 in cloudstack's branch refs/heads/4.4 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8cb2a87 ] CLOUDSTACK-6747 test for test to allow all cidrs on other end of a vpc (cherry picked from commit 3268f5bd1f2175ccd919ee7195d69b05d5b3f3e2) > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043607#comment-14043607 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit ce69bd707d73d6a6baea0e9e19bb7f97135e297a in cloudstack's branch refs/heads/4.4 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ce69bd7 ] CLOUDSTACK-6747 test to allow all cidrs on other end of vpc, public or private (cherry picked from commit 018b471ad300ea0987e52d6b42dde71387de8c5b) > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6747) Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043609#comment-14043609 ] ASF subversion and git services commented on CLOUDSTACK-6747: - Commit 86aff86b7872485d7068c4b8ee2c759d54b2112f in cloudstack's branch refs/heads/4.4 from [~dahn] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=86aff86 ] CLOUDSTACK-6747: call a more forgiving test on the supplied peer cidr-list (cherry picked from commit 17850c7aff432a504d65a34d2f22ca7e1952a770) > Allowing non rfc1918 networks on the other end of VPC Site 2 Site VPN > - > > Key: CLOUDSTACK-6747 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6747 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller, Virtual Router >Affects Versions: 4.2.0, 4.3.0 >Reporter: Erik Weber >Assignee: Daan Hoogland > Fix For: Future > > > When you configure a Site 2 Site VPN Customer gateway the other end from > CloudStack point of view is not allowed to be outside rfc1918 address scope. > There are use cases where the client / remote networks use official/public > addresses and you want to encrypt / secure the traffic with VPN. > Log excerpt: > 2014-05-21 12:30:42,326 WARN [c.c.u.n.NetUtils] (API-Job-Executor-7:job-3072 > ctx-bf3922b1) cidr 50.0.1.0/24 is not RFC 1918 compliant > 2014-05-21 12:30:42,335 ERROR [c.c.a.ApiAsyncJobDispatcher] > (API-Job-Executor-7:job-3072) Unexpected exception while executing > org.apache.cloudstack.api.command.user.vpn.CreateVpnCustomerGatewayCmd > com.cloud.exception.InvalidParameterValueException: The customer gateway > guest cidr list 50.0.1.0/24 is invalid guest cidr! > at > com.cloud.network.vpn.Site2SiteVpnManagerImpl.createCustomerGateway(Site2SiteVpnManagerImpl.java:176) > Expected behavior is that guest cidr should be allowed as long as it's a > valid cidr, including if it's outside of RFC1918 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6909) Marvin fails to handle SMB credentials in deployDataCenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043805#comment-14043805 ] ASF subversion and git services commented on CLOUDSTACK-6909: - Commit 477a812a6f7aaab74122c11488713f417dfe4d89 in cloudstack's branch refs/heads/master from [~johnmdilley] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=477a812 ] CLOUDSTACK-6909 - fix marvin's handling of SMB credentials for storage Signed-off-by: Daan Hoogland > Marvin fails to handle SMB credentials in deployDataCenter > -- > > Key: CLOUDSTACK-6909 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6909 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test Tools >Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0, 4.3.1 >Reporter: John Dilley > > Marvin fails to correctly handle SMB credentials in primary and secondary > storage. > This is because > - For primary storage, the details field is passed to the API as a JSONLoader > object > - For secondary storage, the details field is only used for S3 and Swift > storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6909) Marvin fails to handle SMB credentials in deployDataCenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043819#comment-14043819 ] ASF subversion and git services commented on CLOUDSTACK-6909: - Commit 2498f65683bd529b2b03bac9a6cfd2fdbf65aca2 in cloudstack's branch refs/heads/4.4-forward from [~johnmdilley] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2498f65 ] CLOUDSTACK-6909 - fix marvin's handling of SMB credentials for storage Signed-off-by: Daan Hoogland (cherry picked from commit 477a812a6f7aaab74122c11488713f417dfe4d89) > Marvin fails to handle SMB credentials in deployDataCenter > -- > > Key: CLOUDSTACK-6909 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6909 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test Tools >Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0, 4.3.1 >Reporter: John Dilley > > Marvin fails to correctly handle SMB credentials in primary and secondary > storage. > This is because > - For primary storage, the details field is passed to the API as a JSONLoader > object > - For secondary storage, the details field is only used for S3 and Swift > storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6917) dashboard view for regular user should have more information
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6917: Summary: dashboard view for regular user should have more information (was: dashboard view for account should have more information) > dashboard view for regular user should have more information > > > Key: CLOUDSTACK-6917 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6917 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0, 4.5.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.4.0, 4.5.0 > > > This dashboard doesn't give much useful info for a regular user. > e.g. CPU, network, memory, storage usage/available and performance. > I think listAccounts API gives a lot of useful information on this and that > should be utilized to have a more informative dashboard for a regular user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6894) Secondary storage problem
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044032#comment-14044032 ] Dean Kamali commented on CLOUDSTACK-6894: - I'm having the same issue with cloudstack 4.3 and xenserver 6.2, I'm able to mount nfs manually on the vm, however when running check script I'm getting "ERROR: Java process not running. Try restarting the SSVM." I have redeployed the vm several times but no luck! > Secondary storage problem > - > > Key: CLOUDSTACK-6894 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6894 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.3.0 >Reporter: Raafat Mhamed >Priority: Blocker > Labels: SSVM > > I have a problem in secondary storage that the NFS is not mounted and the > cloud service is not running. > root@s-3-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh > > First DNS server is 172.20.20.20 > PING 172.20.20.20 (172.20.20.20): 48 data bytes > --- 172.20.20.20 ping statistics --- > 2 packets transmitted, 0 packets received, 100% packet loss > WARNING: cannot ping DNS server > route follows > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > 0.0.0.0 192.168.140.254 0.0.0.0 UG0 00 eth2 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 > 192.168.129.0 0.0.0.0 255.255.255.0 U 0 00 eth1 > 192.168.129.0 0.0.0.0 255.255.255.0 U 0 00 eth3 > 192.168.140.0 0.0.0.0 255.255.252.0 U 0 00 eth2 > > Good: DNS resolves download.cloud.com > > ERROR: NFS is not currently mounted > Try manually mounting from inside the VM > NFS server is eth2 > ping: unknown host > WARNING: cannot ping nfs server > routing table follows > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > 0.0.0.0 192.168.140.254 0.0.0.0 UG0 00 eth2 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 > 192.168.129.0 0.0.0.0 255.255.255.0 U 0 00 eth1 > 192.168.129.0 0.0.0.0 255.255.255.0 U 0 00 eth3 > 192.168.140.0 0.0.0.0 255.255.252.0 U 0 00 eth2 > > Management server is 192.168.129.9. Checking connectivity. > Good: Can connect to management server port 8250 > > ERROR: Java process not running. Try restarting the SSVM. > root@s-3-VM:~# tail /var/log/cloud.log > 2014-06-11 12:57:44,666 ERROR [cloud.agent.AgentShell] (main:null) Unable to > start agent: Resource class not found: > com.cloud.storage.resource.PremiumSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > 2014-06-11 12:57:52,169 INFO [cloud.agent.AgentShell] (main:null) Agent > started > 2014-06-11 12:57:52,171 INFO [cloud.agent.AgentShell] (main:null) > Implementation Version is 4.3.0 > 2014-06-11 12:57:52,171 INFO [cloud.agent.AgentShell] (main:null) > agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties > 2014-06-11 12:57:52,181 DEBUG [cloud.agent.AgentShell] (main:null) Found > property: instance > 2014-06-11 12:57:52,181 DEBUG [cloud.agent.AgentShell] (main:null) Found > property: resource > 2014-06-11 12:57:52,181 INFO [cloud.agent.AgentShell] (main:null) Defaulting > to using properties file for storage > 2014-06-11 12:57:52,183 INFO [cloud.agent.AgentShell] (main:null) Defaulting > to the constant time backoff algorithm > 2014-06-11 12:57:52,197 INFO [cloud.utils.LogUtils] (main:null) log4j > configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml > 2014-06-11 12:57:52,212 DEBUG [cloud.agent.AgentShell] (main:null) Checking > to see if agent.SecStorage.pid exists. > 2014-06-11 12:57:52,214 DEBUG [cloud.utils.ProcessUtil] (main:null) > environment.properties could not be opened > 2014-06-11 12:57:52,220 DEBUG [cloud.utils.ProcessUtil] (main:null) > Executing: bash -c echo $PPID > 2014-06-11 12:57:52,224 DEBUG [cloud.utils.ProcessUtil] (main:null) Execution > is successful. > 2014-06-11 12:57:52,228 ERROR [cloud.agent.AgentShell] (main:null) Unable to > start agent: Resource class not found: > com.cloud.storage.resource.PremiumSecondaryStorageResource due to: > java.lang.ClassNotFoundException: > com.cloud.storage.
[jira] [Created] (CLOUDSTACK-6995) Stress Test to test multiple Remote Access VPN Connections to VPC
Srikanteswararao Talluri created CLOUDSTACK-6995: Summary: Stress Test to test multiple Remote Access VPN Connections to VPC Key: CLOUDSTACK-6995 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6995 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.4.0 Reporter: Srikanteswararao Talluri Assignee: Chandan Purushothama Fix For: 4.4.0 Stress Test to test multiple Remote Access VPN Connections to VPC -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6995) Stress Test to test multiple Remote Access VPN Connections to VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044324#comment-14044324 ] ASF subversion and git services commented on CLOUDSTACK-6995: - Commit defed59b97324ff51360a24edc470b5e6efda7ac in cloudstack's branch refs/heads/4.4-forward from [~chandanp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=defed59 ] CLOUDSTACK-6995:Stress Test to test multiple Remote Access VPN Connections to VPC > Stress Test to test multiple Remote Access VPN Connections to VPC > - > > Key: CLOUDSTACK-6995 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6995 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.4.0 >Reporter: Srikanteswararao Talluri >Assignee: Chandan Purushothama > Fix For: 4.4.0 > > > Stress Test to test multiple Remote Access VPN Connections to VPC -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6996) Adding cluster to legacy zone failed
Sateesh Chodapuneedi created CLOUDSTACK-6996: Summary: Adding cluster to legacy zone failed Key: CLOUDSTACK-6996 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6996 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.2.0, 4.3.0 Environment: VMware ESXi 5.1. CloudStack 4.2 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.1, 4.3.1 1.Deployed CloudStack 4.1 2.Created 1 advanced zone "Z1" with VMware hypervisor. 3.Added 2 clusters to the zone, where each cluster belongs to a different VMware datacenter. 4.Upgraded to CloudStack 4.2 5.Tried to add a cluster to zone "Z1" which failed with error, "Zone 1 is not associated with any VMware DC yet. Please add VMware DC to this zone first and then try to add clusters." -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6772) [UI]need to change popup message fo Attach volume failure "Unexpected exception"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prashant kumar mishra updated CLOUDSTACK-6772:
--
Summary: [UI]need to change popup message fo Attach volume failure
"Unexpected exception" (was: [UI]need to chane popup message fo Attach volume
failure "Unexpected exception")
> [UI]need to change popup message fo Attach volume failure "Unexpected
> exception"
> --
>
> Key: CLOUDSTACK-6772
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6772
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: prashant kumar mishra
>Priority: Minor
> Fix For: 4.4.0
>
> Attachments: management-server.log
>
>
> step to reproduce
> ==
> 1-tried to attach a volume( size> available size on PS)
> 2-Attach volume failed
> 3-UI pop up a message " Unexpected exception"
> Expected
> ===
> we should clearly pop up message like " no suitable primary storage found"
> Logs
>
> 2014-05-27 10:01:51,360 DEBUG [c.c.s.StorageManagerImpl]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Insufficient
> un-allocated capacity on: 1 for volume allocation: [Vol[8|vm=null|DATADISK]]
> since its allocated percentage: 1.6727310608597301 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2014-05-27 10:01:51,361 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457)
> ClusterScopeStoragePoolAllocator returning 0 suitable storage pools
> 2014-05-27 10:01:51,364 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457)
> ZoneWideStoragePoolAllocator to find storage pool
> 2014-05-27 10:01:51,372 WARN [o.a.c.e.o.VolumeOrchestrator]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Unable to find
> suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,381 ERROR [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Invocation
> exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Unable
> to find suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,382 INFO [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39 ctx-e6180457) Rethrow
> exception com.cloud.utils.exception.CloudRuntimeException: Unable to find
> suitable primary storage when creating volume fifty
> 2014-05-27 10:01:51,382 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Done with run of VM work
> job: com.cloud.storage.VmWorkAttachVolume for VM 6, job origin: 38
> 2014-05-27 10:01:51,384 ERROR [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-1:ctx-bf2f08f1 job-38/job-39) Unable to complete
> AsyncJobVO {id:39, userId: 2, accountId: 2, instanceType: null, instanceId:
> null, cmd: com.cloud.storage.VmWorkAttachVolume, cmdInfo:
> rO0ABXNyACRjb20uY2xvdWQuc3RvcmFnZS5WbVdvcmtBdHRhY2hWb2x1bWUHra_5YYfiHAIAAkwACGRldmljZUlkdAAQTGphdmEvbGFuZy9Mb25nO0wACHZvbHVtZUlkcQB-AAF4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1ldAASTGphdmEvbGFuZy9TdHJpbmc7eHAAAgACAAZ0ABRWb2x1bWVBcGlTZXJ2aWNlSW1wbHBzcgAOamF2YS5sYW5nLkxvbmc7i-SQzI8j3wIAAUoABXZhbHVleHIAEGphdmEubGFuZy5OdW1iZXKGrJUdC5TgiwIAAHhwAAg,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 7204337877055, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: Tue May 27 10:01:50 EDT 2014}, job origin:38
> com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable
> primary storage when creating volume fifty
> at
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:447)
> at
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:734)
> at
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1186)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:1054)
> at
> com.cloud.storage.VolumeApiServiceImpl.orchestrateAttachVolumeToVM(VolumeApiServiceImpl.java:2475)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
