[jira] [Commented] (CLOUDSTACK-9120) As a Developer I want the new component tests to be moved into the smoke directory
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048212#comment-15048212 ] ASF GitHub Bot commented on CLOUDSTACK-9120: Github user DaanHoogland commented on the pull request: https://github.com/apache/cloudstack/pull/1195#issuecomment-163140684 fine by me. I will get soem time to add a PR with read.me files per directory indicating what type of test should go where. LGTM pending the outcome of the tests. > As a Developer I want the new component tests to be moved into the smoke > directory > -- > > Key: CLOUDSTACK-9120 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9120 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues >Priority: Minor > > The following tests... > component/test_routers_network_ops.py > component/test_vpc_redundant.py > component/test_router_dhcphosts.py > component/test_routers_iptables_default_policy > component/test_vpc_router_nics > ... should be moved into the smoke directory due to their nature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9094) Multiple threads are being used to collect the stats from the same VR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048207#comment-15048207
]
ASF GitHub Bot commented on CLOUDSTACK-9094:
Github user ustcweizhou commented on the pull request:
https://github.com/apache/cloudstack/pull/1140#issuecomment-163140236
sorry guys, just notice it is already merged.
> Multiple threads are being used to collect the stats from the same VR
> -
>
> Key: CLOUDSTACK-9094
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9094
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Virtual Router
>Affects Versions: 4.6.0
>Reporter: Harikrishna Patnala
>Assignee: Harikrishna Patnala
> Fix For: 4.7.0
>
>
> From the logs we can see that the management server is sending the
> networkusagecommand to a VR twice within a very short interval. This doesn't
> have any impact on the network usage being reported, however it seems to
> consume direct agent threads unnecessarily.
> See the below snippet from the logs where networkusage command was sent to
> the same VR at the same time
> 2014-03-04 00:02:07,178 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-113:null) Seq 10-1242718973: Executing request
> 2014-03-04 00:02:07,482 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-113:null) Seq 10-1242718973: Response Received:
> 2014-03-04 00:02:07,482 DEBUG [agent.transport.Request]
> (DirectAgent-113:null) Seq 10-1242718973: Processing: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.NetworkUsageAnswer":{"routerName":"r-59-VM","bytesSent":2937782,"bytesReceived":114175352,"result":true,"details":"","wait":0}}]
> }
> 2014-03-04 00:02:07,482 DEBUG [agent.transport.Request]
> (RouterMonitor-1:null) Seq 10-1242718973: Received: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10, { NetworkUsageAnswer } }
> 2014-03-04 00:02:07,482 DEBUG [agent.manager.AgentManagerImpl]
> (RouterMonitor-1:null) Details from executing class
> com.cloud.agent.api.NetworkUsageCommand:
> 2014-03-04 00:02:07,198 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-244:null) Seq 10-1242718974: Executing request
> 2014-03-04 00:02:07,510 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-244:null) Seq 10-1242718974: Response Received:
> 2014-03-04 00:02:07,510 DEBUG [agent.transport.Request]
> (DirectAgent-244:null) Seq 10-1242718974: Processing: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.NetworkUsageAnswer":{"routerName":"r-59-VM","bytesSent":2937782,"bytesReceived":114175352,"result":true,"details":"","wait":0}}]
> }
> 2014-03-04 00:02:07,510 DEBUG [agent.transport.Request]
> (RouterMonitor-1:null) Seq 10-1242718974: Received: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10, { NetworkUsageAnswer } }
> 2014-03-04 00:02:07,510 DEBUG [agent.manager.AgentManagerImpl]
> (RouterMonitor-1:null) Details from executing class
> com.cloud.agent.api.NetworkUsageCommand:
> 2014-03-04 00:02:07,513 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null)
> Router stats changed from the time NetworkUsageCommand was sent. Ignoring
> current answer. Router: r-59-VM Rcvd: 114175352Sent: 2937782
> 2014-03-04 00:02:07,514 DEBUG [db.Transaction.Transaction]
> (RouterMonitor-1:null) Rolling back the transaction: Time = 2 Name =
> -VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:900-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701;
> called by
> -Transaction.rollback:897-Transaction.removeUpTo:840-Transaction.close:664-VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:955-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9094) Multiple threads are being used to collect the stats from the same VR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048205#comment-15048205
]
ASF GitHub Bot commented on CLOUDSTACK-9094:
Github user ustcweizhou commented on the pull request:
https://github.com/apache/cloudstack/pull/1140#issuecomment-163140058
@DaanHoogland the fix is simple. We do not need special /extra process for
VPC routers.
@bhaisaab this issue does not exist in 4.5, as @koushik-das mentioned, it
is a regression bug in 4.6.
LGTM
this is almost same to commit e444a03, so we can merge it or cherry pick
the old commit
> Multiple threads are being used to collect the stats from the same VR
> -
>
> Key: CLOUDSTACK-9094
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9094
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Virtual Router
>Affects Versions: 4.6.0
>Reporter: Harikrishna Patnala
>Assignee: Harikrishna Patnala
> Fix For: 4.7.0
>
>
> From the logs we can see that the management server is sending the
> networkusagecommand to a VR twice within a very short interval. This doesn't
> have any impact on the network usage being reported, however it seems to
> consume direct agent threads unnecessarily.
> See the below snippet from the logs where networkusage command was sent to
> the same VR at the same time
> 2014-03-04 00:02:07,178 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-113:null) Seq 10-1242718973: Executing request
> 2014-03-04 00:02:07,482 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-113:null) Seq 10-1242718973: Response Received:
> 2014-03-04 00:02:07,482 DEBUG [agent.transport.Request]
> (DirectAgent-113:null) Seq 10-1242718973: Processing: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.NetworkUsageAnswer":{"routerName":"r-59-VM","bytesSent":2937782,"bytesReceived":114175352,"result":true,"details":"","wait":0}}]
> }
> 2014-03-04 00:02:07,482 DEBUG [agent.transport.Request]
> (RouterMonitor-1:null) Seq 10-1242718973: Received: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10, { NetworkUsageAnswer } }
> 2014-03-04 00:02:07,482 DEBUG [agent.manager.AgentManagerImpl]
> (RouterMonitor-1:null) Details from executing class
> com.cloud.agent.api.NetworkUsageCommand:
> 2014-03-04 00:02:07,198 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-244:null) Seq 10-1242718974: Executing request
> 2014-03-04 00:02:07,510 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-244:null) Seq 10-1242718974: Response Received:
> 2014-03-04 00:02:07,510 DEBUG [agent.transport.Request]
> (DirectAgent-244:null) Seq 10-1242718974: Processing: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.NetworkUsageAnswer":{"routerName":"r-59-VM","bytesSent":2937782,"bytesReceived":114175352,"result":true,"details":"","wait":0}}]
> }
> 2014-03-04 00:02:07,510 DEBUG [agent.transport.Request]
> (RouterMonitor-1:null) Seq 10-1242718974: Received: { Ans: , MgmtId:
> 144027776315500, via: 10, Ver: v1, Flags: 10, { NetworkUsageAnswer } }
> 2014-03-04 00:02:07,510 DEBUG [agent.manager.AgentManagerImpl]
> (RouterMonitor-1:null) Details from executing class
> com.cloud.agent.api.NetworkUsageCommand:
> 2014-03-04 00:02:07,513 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl] (RouterMonitor-1:null)
> Router stats changed from the time NetworkUsageCommand was sent. Ignoring
> current answer. Router: r-59-VM Rcvd: 114175352Sent: 2937782
> 2014-03-04 00:02:07,514 DEBUG [db.Transaction.Transaction]
> (RouterMonitor-1:null) Rolling back the transaction: Time = 2 Name =
> -VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:900-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701;
> called by
> -Transaction.rollback:897-Transaction.removeUpTo:840-Transaction.close:664-VirtualNetworkApplianceManagerImpl$NetworkUsageTask.run:955-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9127) Missing PV-bootloader-args for "SUSE Linux Enterprise Server 10 SP2 and SP3"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048188#comment-15048188
]
ASF GitHub Bot commented on CLOUDSTACK-9127:
GitHub user SudharmaJain opened a pull request:
https://github.com/apache/cloudstack/pull/1196
CLOUDSTACK-9127 Missing PV-bootloader-args for "SUSE Linux Enterprise…
… Server 10 SP2 and SP3"
ISSUE
STOP-START of SUSE Linux VMs fail, as PV-bootloader-args are missing during
the start command.
DESCRIPTION
--
Repro steps
1. Upload Suse ISO
2. Create a VM with this ISO, and install it.
3. Detach ISO from the VM.
4. Reboot the VM, : This will work fine, as the pv-bootloader-args are
not missing during reboot.
5.Stop the VM from CCP(VM will get destroyed in Xencenter)
6. Start the same VM from CCP , it will try to start but will fail.
Before Applying the fix
Before applying the starting the VM failed with following exception
com.cloud.utils.exception.CloudRuntimeException: Unable to start
VM(i-2-6-VM) on host(7cfd6388-b763-4c09-b3a3-9679db2904a3) due to Task failed!
Task record: uuid: 21a6799f-9523-7c0e-bb86-1de750a38d74
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Wed Dec 09 07:00:29 UTC 2015
finished: Wed Dec 09 07:00:31 UTC 2015
status: failure
residentOn: com.xensource.xenapi.Host@513d238c
progress: 1.0
type:
result:
errorInfo: [BOOTLOADER_FAILED,
OpaqueRef:0b10b6ac-837d-29af-da9d-6ef1e11a064a, Unable to find partition
containing kernel
]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
After Applying the fix
--
After applying the fix I am able to start the vm.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SudharmaJain/cloudstack cs-9127
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1196.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1196
commit fa81844812a26832e42b31e415de66277c59e3c5
Author: SudharmaJain
Date: 2015-12-09T06:23:51Z
CLOUDSTACK-9127 Missing PV-bootloader-args for "SUSE Linux Enterprise
Server 10 SP2 and SP3"
> Missing PV-bootloader-args for "SUSE Linux Enterprise Server 10 SP2 and SP3"
>
>
> Key: CLOUDSTACK-9127
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9127
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: sudharma jain
>
> STOP-START of SUSE Linux VMs fail, as PV-bootloader-args are missing during
> the start command.
> DESCRIPTION
> ===
> Repro steps
> 1. Upload Suse ISO
> 2. Create a VM with this ISO, and install it.
> 3. Detach ISO from the VM.
> 4. Reboot the VM, : This will work fine, as the pv-bootloader-args are
> not missing during reboot.
> 5.Stop the VM from CCP(VM will get destroyed in Xencenter)
> 6. Start the same VM from CCP , it will try to start but will fail with below
> error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9120) As a Developer I want the new component tests to be moved into the smoke directory
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048133#comment-15048133 ] ASF GitHub Bot commented on CLOUDSTACK-9120: GitHub user wilderrodrigues opened a pull request: https://github.com/apache/cloudstack/pull/1195 CLOUDSTACK-9120 - As a Developer I want the new component tests to be moved into the smoke directory This PR only moves the tests I wrote form the ```component``` to the ```smoke``` directory. Given the nature of the tests, the should be moved. - Those tests are doing a lot more than component tests would do. They require hardware and a lot of resources from real hypervisors. I'm now running the five test files that were moved and will post results once they are done. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ekholabs/cloudstack refactor/smoke_tests-CLOUDSTACK-9120 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1195.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1195 commit fb92de52623f5a5a354cf78f5e91dafa3ee6f337 Author: Wilder Rodrigues Date: 2015-12-08T19:28:07Z CLOUDSTACK-9120 - Moves tests to the smoke directory - Those tests are doing a lot more than component tests would do. They require hardware and a lot of resources from real hypervisors. > As a Developer I want the new component tests to be moved into the smoke > directory > -- > > Key: CLOUDSTACK-9120 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9120 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues >Priority: Minor > > The following tests... > component/test_routers_network_ops.py > component/test_vpc_redundant.py > component/test_router_dhcphosts.py > component/test_routers_iptables_default_policy > component/test_vpc_router_nics > ... should be moved into the smoke directory due to their nature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9128) Testcase to verify if snapshot_store_ref table stores actual size of back snapshot in secondary storage
Priti Sarap created CLOUDSTACK-9128: --- Summary: Testcase to verify if snapshot_store_ref table stores actual size of back snapshot in secondary storage Key: CLOUDSTACK-9128 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9128 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.1 Reporter: Priti Sarap Fix For: 4.5.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9125) Add Brazilian translation for quota labels
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048121#comment-15048121 ] ASF GitHub Bot commented on CLOUDSTACK-9125: GitHub user agneya2001 opened a pull request: https://github.com/apache/cloudstack/pull/1194 CLOUDSTACK-9125: Brazilian translations The pull request contains brazilian translations for quota labels. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack master-9125 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1194.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1194 commit 7859c6813c00af5de8c7f6e1e7416334ca0a049b Author: Abhinandan Prateek Date: 2015-12-08T06:10:00Z CLOUDSTACK-9125: Brazilian translations > Add Brazilian translation for quota labels > -- > > Key: CLOUDSTACK-9125 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9125 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9127) Missing PV-bootloader-args for "SUSE Linux Enterprise Server 10 SP2 and SP3"
sudharma jain created CLOUDSTACK-9127: - Summary: Missing PV-bootloader-args for "SUSE Linux Enterprise Server 10 SP2 and SP3" Key: CLOUDSTACK-9127 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9127 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sudharma jain STOP-START of SUSE Linux VMs fail, as PV-bootloader-args are missing during the start command. DESCRIPTION === Repro steps 1. Upload Suse ISO 2. Create a VM with this ISO, and install it. 3. Detach ISO from the VM. 4. Reboot the VM, : This will work fine, as the pv-bootloader-args are not missing during reboot. 5.Stop the VM from CCP(VM will get destroyed in Xencenter) 6. Start the same VM from CCP , it will try to start but will fail with below error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9125) Add Brazilian translation for quota labels
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-9125: --- Priority: Critical (was: Minor) > Add Brazilian translation for quota labels > -- > > Key: CLOUDSTACK-9125 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9125 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9126) Quota: display dates as per users expectations
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048077#comment-15048077 ] Abhinandan Prateek commented on CLOUDSTACK-9126: https://github.com/apache/cloudstack/pull/1193 > Quota: display dates as per users expectations > -- > > Key: CLOUDSTACK-9126 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9126 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9125) Add Brazilian translation for quota labels
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-9125: --- Assignee: Abhinandan Prateek > Add Brazilian translation for quota labels > -- > > Key: CLOUDSTACK-9125 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9125 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9126) Quota: display dates as per users expectations
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-9126: --- Assignee: Abhinandan Prateek > Quota: display dates as per users expectations > -- > > Key: CLOUDSTACK-9126 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9126 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9122) Quota Service: The credits made in future are not getting reflected in balance
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048072#comment-15048072 ] ASF GitHub Bot commented on CLOUDSTACK-9122: GitHub user agneya2001 opened a pull request: https://github.com/apache/cloudstack/pull/1192 CLOUDSTACK-9122: future credit etries should be incorporated when the… future credit etries should be incorporated when the balance is calculated 1. Some code is refactored so that unit tests (TODO in future) are more comprehensive 2. The fix is to incorporate the credit entries on line 228. https://issues.apache.org/jira/browse/CLOUDSTACK-9122 You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack master-9122 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1192.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1192 commit f6828268ccb6c2218650e9870d09843714dfd791 Author: Abhinandan Prateek Date: 2015-12-08T11:51:00Z CLOUDSTACK-9122: future credit etries should be incorporated when the balance is calculated > Quota Service: The credits made in future are not getting reflected in balance > -- > > Key: CLOUDSTACK-9122 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9122 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.7.0 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Blocker > Fix For: 4.7.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9126) Quota: display dates as per users expectations
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-9126: --- Priority: Critical (was: Major) > Quota: display dates as per users expectations > -- > > Key: CLOUDSTACK-9126 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9126 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Abhinandan Prateek >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9126) Quota: display dates as per users expectations
Abhinandan Prateek created CLOUDSTACK-9126: -- Summary: Quota: display dates as per users expectations Key: CLOUDSTACK-9126 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9126 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Abhinandan Prateek -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9112) deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048058#comment-15048058 ] ASF GitHub Bot commented on CLOUDSTACK-9112: Github user harikrishna-patnala commented on the pull request: https://github.com/apache/cloudstack/pull/1180#issuecomment-163112385 Thank you for the feedback, I'll add the unit tests for the new methods and integration tests for the changes that I have made. > deployVM thread is holding the global lock on network longer and cause delays > and some improvements in the planner > -- > > Key: CLOUDSTACK-9112 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9112 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.7.0 > > > There are some VM deployment failures happening when multiple VMs are > deployed at a time, failures mainly due to NetworkModel code that iterates > over all the vlans in the pod. This causes each deployVM thread to hold the > global lock on Network longer and cause delays. This delay in turn causes > more threads to choose same host and fail since capacity is not available on > that host. > Following are some changes required to be done to reduce delays during VM > deployments which in turn causes some vm deployment failures when multiple > VMs are launched at a time. > - In Planner, remove the clusters that do not contain a host with matching > service offering tag. This will save some iterations over clusters that dont > have matching tagged host > - In NetworkModel, do not query the vlans for the pod within the loop. Also > optimized the logic to query the ip/ipv6 > - In DeploymentPlanningManagerImpl, do not process the affinity group if the > plan has hostId provided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9125) Add Brazilian translation for quota labels
Abhinandan Prateek created CLOUDSTACK-9125: -- Summary: Add Brazilian translation for quota labels Key: CLOUDSTACK-9125 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9125 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Abhinandan Prateek Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7889) Static NAT Public IPV4 from metadata server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047657#comment-15047657 ] Venkat Srinivasan commented on CLOUDSTACK-7889: --- Any update on this ? Is there any ETA for a fix for this ? > Static NAT Public IPV4 from metadata server > --- > > Key: CLOUDSTACK-7889 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7889 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.4.0 >Reporter: Venkat Srinivasan > > Hello All, > I have setup cloudstack 4.4 with advanced networking and created a VPC and a > network tier. I launched a virtual machine inside this network which to the > isolated network assigned as > 10.0.0.117 > I acquired a new IP from the guest network , 172.16.10.110 and associated it > with this virtual machine and applied the ACLS and Iam able to connect to > this VM. > However, when I try to get the public ip of the virtual machine from within > the VM using the metadata server > http://metadata/latest/meta-data/public-ipv4 > I get the IP address of the Source NAT associated with the VPC. I expected > the static nat IP I acquired and associated to the VM to be returned .Is this > correct ? If so , is this a know bug ? > -- > Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8937) Xenserver - VM migration with storage fails in a clustered management server setup
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047363#comment-15047363
]
ASF GitHub Bot commented on CLOUDSTACK-8937:
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/1037#issuecomment-162995054
Hi @atrbgithub
Yes, the info clarifies feel things, but unfortunately I'm also busy and do
not have time to write a test to cover it. I also have some
refactoring/development to do and cannot be 100% allocated to write tests to
run against other PRs.
Since you mentioned in your comment that ```Everything appears to compile
ok and tests pass``` I thought you were talking about existing integration
tests.
Unfortunately, unless someone tests this PR with the setup provided by
@atrbgithub, I will have to hold a :-1: against it.
Cheers,
Wilder
> Xenserver - VM migration with storage fails in a clustered management server
> setup
> --
>
> Key: CLOUDSTACK-8937
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8937
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.5.2
>Reporter: CS User
>
> When using the migrateVirtualMachineWithVolume, in a clustered management
> server environment, migrations intermittently fail. This appears to be a
> similar issue to this jira ticket:
> https://issues.apache.org/jira/browse/CLOUDSTACK-8412
> For reference, the error is:
> {noformat}
> ERROR [c.c.a.t.Request] (AgentManager-Handler-11:null) Caught problem with
> [{"com.cloud.agent.api.MigrateWithStorageCommand":{"vm":{"id":26631,"name":"i-2-26631-VM","bootloader":"PyGrub","type":"Us
> er","cpus":1,"minSpeed":1200,"maxSpeed":1200,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
> 5.6 (64-bit)","platformEmulator":"CentOS 5
> (64-bit)","bootArgs":"","enableHA":false,"
> limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"","params":{"memoryOvercommitRatio":"1","platform":"viridian:true;acpi:1;apic:true;pae:true;nx:t
> rue","hypervisortoolsversion":"xenserver56","cpuOvercommitRatio":"4"},"uuid":"b37e76e8-e19a-4100-bf1c-1ee8eba674f2","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"8f51
> e73f-9bfc-4a37-bf86-664067a2cf40","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"b114d58e-a37a-6433-c0ff-07f3613a3c68","id":219,"poolType":"LVM","ho
> st":"192.168.97.2","path":"lvm","port":0,"url":"LVM://192.168.97.2/lvm/?ROLE\u003dPrimary\u0026STOREUUID\u003db114d58e-a37a-6433-c0ff-07f3613a3c68"}},"name":"ROOT-26631","size":21474836480,"path":"48
> fe494b-ee02-4f08-b7aa-975baecd7b3e","volumeId":119075,"vmName":"i-2-26631-VM","accountId":2,"format":"VHD","provisioningType":"THIN","id":119075,"deviceId":0,"cacheMode":"NONE","hypervisorType":"Xe
> nServer"}},"diskSeq":0,"path":"48fe494b-ee02-4f08-b7aa-975baecd7b3e","type":"ROOT","_details":{"managed":"false","storagePort":"0","storageHost":"192.168.97.2","volumeSize":"21474836480"}},{"data":{
> "org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":2000,"defaultNic":true,"pxe
> Disable":false,"nicUuid":"aaef8c14-784c-403f-91fc-b6a3167f2595","uuid":"508d0384-5bf0-4434-8155-0b5bb1b33b43","ip":"192.168.8.112","netmask":"255.255.254.0","gateway":"192.168.9.254","mac":"06:68:80:
> 00:00:7f","dns1":"192.168.0.224","dns2":"192.168.0.224","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isSecurityGroupEnabled":true,"name":"CS-Guest-Public"}],"vcpuMaxLimit":
> 16},"volumeToFiler":{"Vol[119075|ROOT|48fe494b-ee02-4f08-b7aa-975baecd7b3e|21474836480]":{"id":223,"uuid":"bc01ca2b-e6d8-a856-27b5-6f6b55a06b1d","host":"192.168.97.1","path":"lvm","port":0,"type":"L
> VM"}},"contextMap":{"job":"job-347068/job-347069"},"wait":0}}]
> com.google.gson.JsonParseException: Expecting object found:
> "Vol[119075|ROOT|48fe494b-ee02-4f08-b7aa-975baecd7b3e|21474836480]"
> at
> com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:100)
> at
> com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonPrimitive(JsonDeserializationContextDefault.java:85)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:56)
> at com.google.gson.MapTypeAdapter.
[jira] [Commented] (CLOUDSTACK-9112) deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047358#comment-15047358 ] ASF GitHub Bot commented on CLOUDSTACK-9112: Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1180#issuecomment-162994057 @remibergsma It doesn't break things covered by the tests that were execute, which is fine. However, @harikrishna-patnala hasn't provided any support in terms of how to test it; if there is any integration test to help; or about the unit tests for the new methods he introduced. I'm not very keen to LGTM a PR without support from the author himself. Unless he comes back with some more details, I will hold a :-1: for this PR. Cheers, Wilder > deployVM thread is holding the global lock on network longer and cause delays > and some improvements in the planner > -- > > Key: CLOUDSTACK-9112 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9112 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.7.0 > > > There are some VM deployment failures happening when multiple VMs are > deployed at a time, failures mainly due to NetworkModel code that iterates > over all the vlans in the pod. This causes each deployVM thread to hold the > global lock on Network longer and cause delays. This delay in turn causes > more threads to choose same host and fail since capacity is not available on > that host. > Following are some changes required to be done to reduce delays during VM > deployments which in turn causes some vm deployment failures when multiple > VMs are launched at a time. > - In Planner, remove the clusters that do not contain a host with matching > service offering tag. This will save some iterations over clusters that dont > have matching tagged host > - In NetworkModel, do not query the vlans for the pod within the loop. Also > optimized the logic to query the ip/ipv6 > - In DeploymentPlanningManagerImpl, do not process the affinity group if the > plan has hostId provided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9074) Support shared networking in NiciraNVP Plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047337#comment-15047337 ] ASF GitHub Bot commented on CLOUDSTACK-9074: Github user nvazquez commented on the pull request: https://github.com/apache/cloudstack/pull/1094#issuecomment-162990802 @remibergsma my mistake, I meant to modify schema-460to470.sql and schema-461to470.sql but not setup/db/db/schema-410to420-cleanup.sql as I did. I'll push some other changes and also fix this. > Support shared networking in NiciraNVP Plugin > - > > Key: CLOUDSTACK-9074 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9074 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.7.0 >Reporter: Nicolas Vazquez > Fix For: 4.7.0 > > > h3. Introduction > Currently NiciraNVP plugin supports only Isolated networking. In this mode of > operations networks are assigned to individual Cloudstack accounts and on NSX > side are completely isolated on the L3 level. Many use cases especially in > corporate environment call for shared networking mode support. In some > circumstances there also may be a need to translate shared NSX network over > to a physical VLAN via L2 NSX gateway. > Features that will be introduced to support Cloudstack shared networks in two > modes of NiciraNVP plugin: > * Shared networks mapped to a physical VLAN with L2 NSX gateway > * Shared networks within the same L3 NSX domain. Multiple L3 NSX domains will > be supported. > h3. Features > h4. 1) Shared networking model support > # Support native Cloudstack shared network in NiciraNVP plugin. > # Current code that implements isolated networking mode support will stay > intact. > # Designate network service offering by configuring VirtualNetworking > provider with NiciraNVP. > # Static/Source NAT is not used and ignored if defined in the network > offering. > # Nicira_vvp_router_map table will support non-unique logical routers to > implement L3 NSX routing domains where multiple Cloudstack networks are > attached to the same logical router. > # Shared network with NSX based Virtual networking will go through the > following states: > ## Allocated > ## Implementing > ## Implemented > ## Destroy > h4. 2) Support NSX L2 gateways for L2 based VLANs mapped to a physical network > # Optional L2gatewayserviceuuid parameter for NiciraNVP controller > # VLAN ID of a Shared network represents VLAN to pass through L2 gateway > similar to native Cloudstack shared networking > # NSX workflow for network allocation > ## Check if l2gatewayservice defined > ## Create record in networks table > ### NiciraNvpGuestNetworkGuru as Guru_name > ### Lswitch as broadcast_doamin > ### Vlan://vlan_id as broadcast_uri > ## Create record in VLAN table > # NSX workflow for network implementation > ## Check if l2gatewayservice defined and valid > ## Create logical switch > ## Map logical switch to L2gateway service assigning shared network VLAN ID > # NSX workflow for NIC management and/or hypervisor support > ## No changes from current implementation > h4. 3) Support NSX L3 multiple routing domains > # VLAN ID of a Shared network represents an UUID of a NSX virtual router of a > particular routing domain. We will support UUID style notation for VLAN ID. > l3gatewayservice option is not used in shared networking > # It is assumed that if connectivity to the physical networking is required > then logical router is configured and connected to the physical network in > advance. NiciraNVP plugin will not perform any task beyond basic connectivity > to the logical router > # Support NSX L3 multiple routing domains > # NSX workflow for network allocation > ## Create record in networks table > ### NiciraNvpGuestNetworkGuru as Guru_name > ### Lswitch as broadcast_domain > ### NULL as broadcast_uri > ## Create record in VLAN table > ## Create record in nicira_nvp_router_map table > # NSX workflow for network implementation > ## Check if logical router exists on NSX side which UUID matches the one > defined during shared network creation. This mode is activated if VLAN ID > supplied in UUID style notation > ## Create logical switch > ## Attach logical switch to the logical router > ## Assign shared network default gateway to the inside port of the logical > router > # NSX workflow for NIC management and/or hypervisor support > ## No changes from current implementation > h4. 4) API Changes > # Existing API addNiciraNvpDevices will be updated > ## Adding 1 new optional parameter – l2gatewayserviceuuid > ## Adding 1 new response tag – l2gatewayserviceuuid > # Existing API listNiciraNvpDevices will be updated > ## Adding 1 new response ta
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047303#comment-15047303 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047305#comment-15047305 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 738b78886e2d8e2ffb8fe46918991eb06e463acc in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=738b788 ] Merge release branch 4.6 to master * 4.6: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047302#comment-15047302 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047298#comment-15047298 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit f81a29351d2c20714db1220c32fee4cdff61ed3b in cloudstack's branch refs/heads/master from [~wilder.rodrigues] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f81a293 ] CLOUDSTACK-9118 - Improves the existing checkrouter.sh script > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047304#comment-15047304 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 738b78886e2d8e2ffb8fe46918991eb06e463acc in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=738b788 ] Merge release branch 4.6 to master * 4.6: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047301#comment-15047301 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047300#comment-15047300 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047289#comment-15047289 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 848ef78158b29749ac20f8d4fdf919b07e722af6 in cloudstack's branch refs/heads/4.6 from [~wilder.rodrigues] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=848ef78 ] CLOUDSTACK-9118 - Adds integration test to cover routers state. - Refactoring the existing tests > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047295#comment-15047295 ] ASF GitHub Bot commented on CLOUDSTACK-9118: Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/1189 > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047288#comment-15047288 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit f81a29351d2c20714db1220c32fee4cdff61ed3b in cloudstack's branch refs/heads/4.6 from [~wilder.rodrigues] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f81a293 ] CLOUDSTACK-9118 - Improves the existing checkrouter.sh script > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047290#comment-15047290 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/4.6 from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047292#comment-15047292 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/4.6 from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047299#comment-15047299 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 848ef78158b29749ac20f8d4fdf919b07e722af6 in cloudstack's branch refs/heads/master from [~wilder.rodrigues] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=848ef78 ] CLOUDSTACK-9118 - Adds integration test to cover routers state. - Refactoring the existing tests > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047291#comment-15047291 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/4.6 from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047294#comment-15047294 ] ASF subversion and git services commented on CLOUDSTACK-9118: - Commit 3515f574c39dd8249012cefbce3db7169ffcb59f in cloudstack's branch refs/heads/4.6 from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3515f57 ] Merge pull request #1189 from ekholabs/fix/4.6-rvr_routers_state-CLOUDSTACK-9118 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers stateThis PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state * pr/1189: CLOUDSTACK-9118 - Adds integration test to cover routers state. CLOUDSTACK-9118 - Improves the existing checkrouter.sh script Signed-off-by: Remi Bergsma > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047284#comment-15047284
]
ASF GitHub Bot commented on CLOUDSTACK-9118:
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1189#issuecomment-162984674
LGTM based on these tests:
```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py
```
Result:
```
Test iptables default INPUT/FORWARD policies on VPC router ... ===
TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics
after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status :
SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default
routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName:
test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... ===
TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName:
test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName:
test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName:
test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... ===
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80
| Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status :
SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status :
SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS
===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS
===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS
===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS
===
ok
Test Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS
===
ok
Test for port forwarding on source NAT ... === TestName:
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName:
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status :
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status :
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS
===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status :
SUCCESS ===
ok
--
Ran 33 tests in 17793.167s
OK
```
And:
```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,requir
[jira] [Commented] (CLOUDSTACK-8847) ListServiceOfferings is returning incompatible tagged offerings when called with VM id
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047079#comment-15047079 ] ASF GitHub Bot commented on CLOUDSTACK-8847: Github user nitin-maharana commented on the pull request: https://github.com/apache/cloudstack/pull/823#issuecomment-162947373 The functionality purely depends on the meaning of compatibility. Here is what I understood about the compatibility. For example, if our current compute offering is associated with tags (x,y) then the new compute offering should have tags atleast (x,y), then only it can have the same functionality as the current one. Suppose the new offering has the only tag(x), then it is missing the functionality associated with tag(y). One more example, Suppose we have three hosts H1,H2,H3. The tags associated with H1 is (x,y), H2 is only (y) and H3 is (x,y,z). Suppose our current compute offering has (x,y) as host tags. So the VM can be placed in H1 or H3 as both the tags are associated with these hosts but cannot be placed in H2 as tag (x) is missing. But according to the prior situation, it can list a compute offering which has host tag only (y), so the VM can be placed in H2 also. I think this is an issue. > ListServiceOfferings is returning incompatible tagged offerings when called > with VM id > -- > > Key: CLOUDSTACK-8847 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8847 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nitin Kumar Maharana > > When calling listServiceOfferings with VM id as parameter. It is returning > incompatible tagged offerings. It should only list all compatible tagged > offerings. The new service offering should contain all the tags of the > existing service offering. If that is the case It should list in the result. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047050#comment-15047050 ] ASF GitHub Bot commented on CLOUDSTACK-9118: Github user borisroman commented on the pull request: https://github.com/apache/cloudstack/pull/1189#issuecomment-162941648 Hi @wilderrodrigues, I tested it just now! Looking good! Ran against Ubuntu 14.04 KVM management/hypervisor. ``` Test redundant router internals ... === TestName: test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_03_RVR_Network_check_router_state | Status : SUCCESS === ok -- Ran 5 tests in 2569.926s ``` LGTM :+1: > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9124) GPG Key published on cloudstack.apt-get.eu is outdated
lmwangi created CLOUDSTACK-9124: --- Summary: GPG Key published on cloudstack.apt-get.eu is outdated Key: CLOUDSTACK-9124 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9124 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc, Management Server Reporter: lmwangi The key published on http://cloudstack.apt-get.eu/release.asc is outdated. Consequently, trying to install cloudstack on ubuntu fails with a signature mismatch error. The incorrect key is: ``` pub 2048R/86C278E3 2012-09-07 uid Apache CloudStack sub 2048R/B7C7765A 2012-09-07 ``` Correct key: ``` pub 4096R/CC56CEA8 2012-08-06 [expires: 2016-08-06] uid Chip Childers uid Chip Childers (Personal email address) uid Chip Childers (SunGard work address) sub 4096R/A99A5D58 2012-08-06 [expires: 2016-08-06] ``` Cheers, Laban -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9022) We should keep Destroyed volumes for some time
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-9022. -- Resolution: Fixed Fix Version/s: 4.6.2 > We should keep Destroyed volumes for some time > -- > > Key: CLOUDSTACK-9022 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9022 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.6.2 > > > for now, the Destroyed volumes will be expunged in Storage cleanup thread, no > matter when they are destroyed. > In Expunging vm, we only clean the Destroyed vms which have been destroyed at > least 'expunge.delay' seconds. > We need to add the similar configuration for volumes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9051) Update Ip address of NIC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-9051. -- Resolution: Fixed Fix Version/s: 4.6.2 > Update Ip address of NIC > > > Key: CLOUDSTACK-9051 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9051 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.6.2 > > > Sometimes we want to change the ipaddress of a NIC to a specified ip. > we need to add an API to replace the manual database change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9101) some issues in resize volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhou resolved CLOUDSTACK-9101. -- Resolution: Fixed Fix Version/s: 4.6.2 > some issues in resize volume > > > Key: CLOUDSTACK-9101 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9101 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.6.2 > > > I found some issues in the testing of resizeVolume > (1) it is not implemented on UI > (2) volume size is not updated even if the operation succeed > mysql> select volumes.id,volumes.size,disk_offering.disk_size from volumes > left join disk_offering on volumes.disk_offering_id=disk_offering.id where > volumes.uuid='999b8ad2-3664-44b9-8cf6-985e60a98cc8'; > +--+-+-+ > | id | size| disk_size | > +--+-+-+ > | 45 | 85899345920 | 85899345920 | > +--+-+-+ > | id | size| disk_size | > +--+-+-+ > | 7530 | 5368709120 | 21474836480 | > +--+-+-+ > 1 row in set (0.00 sec) > (3) on KVM, the resize on running vm is good > root@KVM015:~# qemu-img info > /mnt/f773b66d-fd8c-3576-aa37-e3f0e685b183/e9ddd9b1-57c4-4ad7-b950-7b7f5c5cf2dc > image: > /mnt/f773b66d-fd8c-3576-aa37-e3f0e685b183/e9ddd9b1-57c4-4ad7-b950-7b7f5c5cf2dc > file format: qcow2 > virtual size: 41G (44023414784 bytes) > but root volume on stopped vm is not correct > root@KVM015:~# qemu-img info > /mnt/1dcbc42c-99bc-3276-9d86-4ad81ef1ad8e/2412a4c0-8271-4e21-a3d1-61b041d209d6 > image: > /mnt/1dcbc42c-99bc-3276-9d86-4ad81ef1ad8e/2412a4c0-8271-4e21-a3d1-61b041d209d6 > file format: qcow2 > virtual size: 40G (42949672960 bytes) > (4) resource count of primary_storage is not updated after restorevm, if the > root volume has been resized before. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9123) As a Developer I want the test_internal_lb.py to work with multiple hypervisors and rVPCs
Wilder Rodrigues created CLOUDSTACK-9123: Summary: As a Developer I want the test_internal_lb.py to work with multiple hypervisors and rVPCs Key: CLOUDSTACK-9123 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9123 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Reporter: Wilder Rodrigues Assignee: Wilder Rodrigues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9099) SecretKey is returned from the APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046817#comment-15046817 ] ASF GitHub Bot commented on CLOUDSTACK-9099: Github user DaanHoogland commented on the pull request: https://github.com/apache/cloudstack/pull/1152#issuecomment-162869020 @kansal looks good, but for a change like this I would like a marvin test to prove it and guarantee it's continued functioning/functionality Do you see chance to add that? > SecretKey is returned from the APIs > --- > > Key: CLOUDSTACK-9099 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9099 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kshitij Kansal >Assignee: Kshitij Kansal > > The sercreKey parameter is returned from the following APIs: > createAccount > createUser > disableAccount > disableUser > enableAccount > enableUser > listAccounts > listUsers > lockAccount > lockUser > registerUserKeys > updateAccount > updateUser -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9099) SecretKey is returned from the APIs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046814#comment-15046814
]
ASF GitHub Bot commented on CLOUDSTACK-9099:
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1152#discussion_r46947711
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/user/ListKeysCmd.java ---
@@ -0,0 +1,74 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+
+package org.apache.cloudstack.api.command.admin.user;
+
+
+import com.cloud.user.Account;
+import com.cloud.user.User;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.BaseCmd;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.response.RegisterResponse;
+import org.apache.cloudstack.api.response.UserResponse;
+
+import java.util.List;
+import java.util.logging.Logger;
+
+@APICommand(name = "listUserKeys",
+description = "This command allows the user to query the
seceret and API keys for the account",
+responseObject = RegisterResponse.class,
+requestHasSensitiveInfo = false,
+responseHasSensitiveInfo = true)
+
+public class ListKeysCmd extends BaseCmd{
+
+@Parameter(name= ApiConstants.ID, type = CommandType.UUID, entityType
= UserResponse.class, required = true, description = "ID of the user whose keys
are required")
+private Long id;
+
+public static final Logger s_logger =
Logger.getLogger(RegisterCmd.class.getName());
--- End diff --
how about using LOGGER as a name for this static final? would be more in
line with standards
> SecretKey is returned from the APIs
> ---
>
> Key: CLOUDSTACK-9099
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9099
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Kshitij Kansal
>Assignee: Kshitij Kansal
>
> The sercreKey parameter is returned from the following APIs:
> createAccount
> createUser
> disableAccount
> disableUser
> enableAccount
> enableUser
> listAccounts
> listUsers
> lockAccount
> lockUser
> registerUserKeys
> updateAccount
> updateUser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9099) SecretKey is returned from the APIs
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046815#comment-15046815
]
ASF GitHub Bot commented on CLOUDSTACK-9099:
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1152#discussion_r46947731
--- Diff:
api/src/org/apache/cloudstack/api/command/admin/user/ListKeysCmd.java ---
@@ -0,0 +1,74 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements. See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership. The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied. See the License for the
+// specific language governing permissions and limitations
+// under the License.
+
+package org.apache.cloudstack.api.command.admin.user;
+
+
+import com.cloud.user.Account;
+import com.cloud.user.User;
+import org.apache.cloudstack.api.APICommand;
+import org.apache.cloudstack.api.ApiConstants;
+import org.apache.cloudstack.api.BaseCmd;
+import org.apache.cloudstack.api.Parameter;
+import org.apache.cloudstack.api.response.RegisterResponse;
+import org.apache.cloudstack.api.response.UserResponse;
+
+import java.util.List;
+import java.util.logging.Logger;
+
+@APICommand(name = "listUserKeys",
+description = "This command allows the user to query the
seceret and API keys for the account",
+responseObject = RegisterResponse.class,
+requestHasSensitiveInfo = false,
+responseHasSensitiveInfo = true)
+
+public class ListKeysCmd extends BaseCmd{
+
+@Parameter(name= ApiConstants.ID, type = CommandType.UUID, entityType
= UserResponse.class, required = true, description = "ID of the user whose keys
are required")
+private Long id;
+
+public static final Logger s_logger =
Logger.getLogger(RegisterCmd.class.getName());
+public static final String s_name = "listuserkeysresponse";
--- End diff --
same here
> SecretKey is returned from the APIs
> ---
>
> Key: CLOUDSTACK-9099
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9099
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Kshitij Kansal
>Assignee: Kshitij Kansal
>
> The sercreKey parameter is returned from the following APIs:
> createAccount
> createUser
> disableAccount
> disableUser
> enableAccount
> enableUser
> listAccounts
> listUsers
> lockAccount
> lockUser
> registerUserKeys
> updateAccount
> updateUser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9099) SecretKey is returned from the APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046810#comment-15046810 ] ASF GitHub Bot commented on CLOUDSTACK-9099: Github user kansal commented on the pull request: https://github.com/apache/cloudstack/pull/1152#issuecomment-162867278 @jburwell @DaanHoogland @kishankavala Have included some changes related to the UI. Now after generating the keys from UI, after ListUserCmd() api, listKeysCmd() will be called to fill the secret key as I have removed it from the response value of other API's. Also added a test in which a normal user tries to call the listKeysCmd() for the admin account and hence giving a permission denied exception. > SecretKey is returned from the APIs > --- > > Key: CLOUDSTACK-9099 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9099 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kshitij Kansal >Assignee: Kshitij Kansal > > The sercreKey parameter is returned from the following APIs: > createAccount > createUser > disableAccount > disableUser > enableAccount > enableUser > listAccounts > listUsers > lockAccount > lockUser > registerUserKeys > updateAccount > updateUser -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9122) Quota Service: The credit made is not getting reflected in balance
Abhinandan Prateek created CLOUDSTACK-9122: -- Summary: Quota Service: The credit made is not getting reflected in balance Key: CLOUDSTACK-9122 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9122 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.7.0 Reporter: Abhinandan Prateek Assignee: Abhinandan Prateek Priority: Blocker Fix For: 4.7.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9122) Quota Service: The credits made in future are not getting reflected in balance
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-9122: --- Summary: Quota Service: The credits made in future are not getting reflected in balance (was: Quota Service: The credit made is not getting reflected in balance) > Quota Service: The credits made in future are not getting reflected in balance > -- > > Key: CLOUDSTACK-9122 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9122 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.7.0 >Reporter: Abhinandan Prateek >Assignee: Abhinandan Prateek >Priority: Blocker > Fix For: 4.7.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046788#comment-15046788 ] ASF GitHub Bot commented on CLOUDSTACK-9118: Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1189#issuecomment-162860695 Ping @DaanHoogland @remibergsma @miguelaferreira @borisroman @bhaisaab @karuturi Since I changed the checkrouter.sh, also used by rVPCs, I will run some more tests. * Environment * Hardware required: TRUE * Management Server + MySQL on CentOS 7.1 * One KVM Host on CentOS 7.1 * Agent + Common RPMs built from 4.6.1 source * Tests executed ``` nosetests --with-marvin --marvin-config=/data/shared/marvin/mct-zone2-kvm2-ISOLATED.cfg -s -a tags=advanced,required_hardware=true component/test_routers_network_ops.py ``` * Results `` Test redundant router internals ... === TestName: test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_03_RVR_Network_check_router_state | Status : SUCCESS === ok -- Ran 5 tests in 3068.947s OK /tmp//MarvinLogs/test_routers_network_ops_2ZGX9V/results.txt (END) `` > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-9095) Hypervisor changes to support UserData for Nuage VSP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Livens closed CLOUDSTACK-9095. --- Resolution: Fixed > Hypervisor changes to support UserData for Nuage VSP > > > Key: CLOUDSTACK-9095 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9095 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Nick Livens >Assignee: Nick Livens > > Hypervisor changes to support UserData for Nuage VSP -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9112) deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046755#comment-15046755
]
ASF GitHub Bot commented on CLOUDSTACK-9112:
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1180#issuecomment-162851856
LGTM based on these tests:
```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py
```
Result:
```
Test iptables default INPUT/FORWARD policies on VPC router ... ===
TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics
after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status :
SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default
routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName:
test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... ===
TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName:
test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName:
test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName:
test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... ===
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80
| Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status :
SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status :
SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS
===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS
===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS
===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS
===
ok
Test Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS
===
ok
Test for port forwarding on source NAT ... === TestName:
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName:
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status :
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status :
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS
===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status :
SUCCESS ===
ok
--
Ran 33 tests in 17222.324s
OK
```
And:
```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,requir
[jira] [Commented] (CLOUDSTACK-9121) Adding VmSnapshot validation in testpath_revert_snap.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046745#comment-15046745 ] ASF GitHub Bot commented on CLOUDSTACK-9121: Github user pritisarap12 commented on the pull request: https://github.com/apache/cloudstack/pull/1190#issuecomment-162851170 Testpath Result: Test revert snapshot on XenServer ... === TestName: test_01_check_revert_snapshot | Status : SUCCESS === ok -- Ran 1 test in 119.808s OK > Adding VmSnapshot validation in testpath_revert_snap.py > --- > > Key: CLOUDSTACK-9121 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9121 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.1 >Reporter: Priti Sarap > Fix For: 4.5.1 > > > In testpath_revert_snap.py, there was no code to check if VM snapshot is > created or not hence adding code for snapshot validation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9121) Adding VmSnapshot validation in testpath_revert_snap.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046744#comment-15046744 ] ASF GitHub Bot commented on CLOUDSTACK-9121: GitHub user pritisarap12 opened a pull request: https://github.com/apache/cloudstack/pull/1190 CLOUDSTACK-9121: Adding VmSnapshot validation in testpath_revert_snap.py In testpath_revert_snap.py, there was no code to check if VM snapshot is created or not hence adding code for snapshot validation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pritisarap12/cloudstack CLOUDSTACK-9121-Adding-VmSnapshot-validation-in-testpath_revert_snap.py Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1190.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1190 commit 1cf44dee3a94dcac765aff9b2827e20cd05f971f Author: Priti Sarap Date: 2015-12-08T10:59:13Z CLOUDSTACK-9121: Adding VmSnapshot validation in testpath_revert_snap.py > Adding VmSnapshot validation in testpath_revert_snap.py > --- > > Key: CLOUDSTACK-9121 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9121 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.5.1 >Reporter: Priti Sarap > Fix For: 4.5.1 > > > In testpath_revert_snap.py, there was no code to check if VM snapshot is > created or not hence adding code for snapshot validation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9113) Vm stats can not be updated if one vm has inconsistent state between KVM and db
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046741#comment-15046741
]
ASF GitHub Bot commented on CLOUDSTACK-9113:
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1182#issuecomment-162850730
LGTM based on these tests:
```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py
```
Result:
```
Test iptables default INPUT/FORWARD policies on VPC router ... ===
TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics
after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status :
SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default
routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName:
test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... ===
TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName:
test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName:
test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName:
test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... ===
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80
| Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status :
SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status :
SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS
===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS
===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS
===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS
===
ok
Test Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS
===
ok
Test for port forwarding on source NAT ... === TestName:
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName:
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status :
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status :
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS
===
ok
Test for Router rules for network rules on acquired public IP ... ===
TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status :
SUCCESS ===
ok
--
Ran 33 tests in 17748.128s
OK
```
And:
```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a
tags=advanced,requir
[jira] [Created] (CLOUDSTACK-9121) Adding VmSnapshot validation in testpath_revert_snap.py
Priti Sarap created CLOUDSTACK-9121: --- Summary: Adding VmSnapshot validation in testpath_revert_snap.py Key: CLOUDSTACK-9121 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9121 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.1 Reporter: Priti Sarap Fix For: 4.5.1 In testpath_revert_snap.py, there was no code to check if VM snapshot is created or not hence adding code for snapshot validation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9120) As a Developer I want the new component tests to be moved into the smoke directory
Wilder Rodrigues created CLOUDSTACK-9120: Summary: As a Developer I want the new component tests to be moved into the smoke directory Key: CLOUDSTACK-9120 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9120 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Reporter: Wilder Rodrigues Assignee: Wilder Rodrigues Priority: Minor The following tests... component/test_routers_network_ops.py component/test_vpc_redundant.py component/test_router_dhcphosts.py component/test_routers_iptables_default_policy component/test_vpc_router_nics ... should be moved into the smoke directory due to their nature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilder Rodrigues updated CLOUDSTACK-9118: - Fix Version/s: 4.6.2 > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0, 4.6.2 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9086) ACS allows to create isolated networks with invalid gateway IP address
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046687#comment-15046687 ] ASF GitHub Bot commented on CLOUDSTACK-9086: Github user kansal commented on the pull request: https://github.com/apache/cloudstack/pull/1188#issuecomment-162839268 cc @bhaisaab @DaanHoogland I closed the previous PR. Created this one and rebased with the master. Not sure why the tests were failing in the previous one. Maybe some mistakes in the merge conflicts resolving while rebasing. > ACS allows to create isolated networks with invalid gateway IP address > -- > > Key: CLOUDSTACK-9086 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9086 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kshitij Kansal >Assignee: Kshitij Kansal > > When entering invalid combination no check is performed anymore and VR is > created with invalid interface. Of course, nothing works in the isolated > network. For example, you are allowed to create network with 172.16.21.0 IP > address for GW and 255.255.255.0 for SM - this address is not valid, however > it is accepted and even used in VR. One more example - 192.168.255.255 for GW > address and 255.255.255.0 for SM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046688#comment-15046688 ] ASF GitHub Bot commented on CLOUDSTACK-9118: Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1189#issuecomment-162839426 Ping @remibergsma @bhaisaab @DaanHoogland @miguelaferreira @borisroman I'm currently running the other tests, but feel free to start testing now. * Result of the newly added test ``` Test redundant router internals ... === TestName: test_03_RVR_Network_check_router_state | Status : SUCCESS === ok -- Ran 5 tests in 736.443s OK (SKIP=4) /tmp//MarvinLogs/test_routers_network_ops_AXSXD3/results.txt (END) ``` > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9118) As a Developer I want the checkrouter.sh script to report the right information about RVR routers state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046680#comment-15046680 ] ASF GitHub Bot commented on CLOUDSTACK-9118: GitHub user wilderrodrigues opened a pull request: https://github.com/apache/cloudstack/pull/1189 CLOUDSTACK-9118 - As a Developer I want the checkrouter.sh script to report the right information about RVR routers state This PR fixes the RVR routers state information retrieved by the Management Server via the ```checkrouter.sh``` script. In order to cover the changes, a new test has been added to the component/test_routers_network_ops.py test suite: test_03_RVR_Network_check_router_state You can merge this pull request into a Git repository by running: $ git pull https://github.com/ekholabs/cloudstack fix/4.6-rvr_routers_state-CLOUDSTACK-9118 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1189.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1189 commit f81a29351d2c20714db1220c32fee4cdff61ed3b Author: Wilder Rodrigues Date: 2015-12-07T18:18:20Z CLOUDSTACK-9118 - Improves the existing checkrouter.sh script commit 848ef78158b29749ac20f8d4fdf919b07e722af6 Author: Wilder Rodrigues Date: 2015-12-07T18:26:43Z CLOUDSTACK-9118 - Adds integration test to cover routers state. - Refactoring the existing tests > As a Developer I want the checkrouter.sh script to report the right > information about RVR routers state > --- > > Key: CLOUDSTACK-9118 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9118 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0, 4.6.1 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0 > > > The routers are working properly, as BACK and MASTER, but the checkrouter.sh > script is not working properly and show both router as MASTER. > The script is working fine for rVPC routers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9086) ACS allows to create isolated networks with invalid gateway IP address
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046662#comment-15046662 ] ASF GitHub Bot commented on CLOUDSTACK-9086: GitHub user kansal opened a pull request: https://github.com/apache/cloudstack/pull/1188 CLOUDSTACK-9086: ACS allows to create isolated networks with invalide… … gateway IP address - Fixed and Test cases added Problem: There was no check for the network and broadcast IP addresses in the case where we provide the gateway and netmask while creating the isolated network. As a result the provided IP gets assigned to the eth0 interface of the VR. Note: This is in continuation of PR #1125 which I closed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kansal/cloudstack CLOUDSTACK-9086 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1188.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1188 commit 1b607b9c75bca7ac42086f56d79a6b83fa9d4bc0 Author: Kshitij Kansal Date: 2015-12-08T07:31:39Z CLOUDSTACK-9086: ACS allows to create isolated networks with invalide gateway IP address - Fixed and Test cases added > ACS allows to create isolated networks with invalid gateway IP address > -- > > Key: CLOUDSTACK-9086 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9086 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kshitij Kansal >Assignee: Kshitij Kansal > > When entering invalid combination no check is performed anymore and VR is > created with invalid interface. Of course, nothing works in the isolated > network. For example, you are allowed to create network with 172.16.21.0 IP > address for GW and 255.255.255.0 for SM - this address is not valid, however > it is accepted and even used in VR. One more example - 192.168.255.255 for GW > address and 255.255.255.0 for SM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8937) Xenserver - VM migration with storage fails in a clustered management server setup
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046640#comment-15046640
]
ASF GitHub Bot commented on CLOUDSTACK-8937:
Github user atrbgithub commented on the pull request:
https://github.com/apache/cloudstack/pull/1037#issuecomment-162829832
Hi @wilderrodrigues
To test this you would need to have 2 or more cloudstack management servers
operating in a cluster with Xen hosts. Before applying this fix, when you try
to live migrate vm's between hosts (root disks on local storage or primary
storage), occasionally this will fail. It is random depending on which
management servers are allocated the job.
After applying the change in the pull request, migrations should no longer
fail.
Hope that is ok.
Thanks!
> Xenserver - VM migration with storage fails in a clustered management server
> setup
> --
>
> Key: CLOUDSTACK-8937
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8937
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.5.2
>Reporter: CS User
>
> When using the migrateVirtualMachineWithVolume, in a clustered management
> server environment, migrations intermittently fail. This appears to be a
> similar issue to this jira ticket:
> https://issues.apache.org/jira/browse/CLOUDSTACK-8412
> For reference, the error is:
> {noformat}
> ERROR [c.c.a.t.Request] (AgentManager-Handler-11:null) Caught problem with
> [{"com.cloud.agent.api.MigrateWithStorageCommand":{"vm":{"id":26631,"name":"i-2-26631-VM","bootloader":"PyGrub","type":"Us
> er","cpus":1,"minSpeed":1200,"maxSpeed":1200,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
> 5.6 (64-bit)","platformEmulator":"CentOS 5
> (64-bit)","bootArgs":"","enableHA":false,"
> limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"","params":{"memoryOvercommitRatio":"1","platform":"viridian:true;acpi:1;apic:true;pae:true;nx:t
> rue","hypervisortoolsversion":"xenserver56","cpuOvercommitRatio":"4"},"uuid":"b37e76e8-e19a-4100-bf1c-1ee8eba674f2","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"8f51
> e73f-9bfc-4a37-bf86-664067a2cf40","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"b114d58e-a37a-6433-c0ff-07f3613a3c68","id":219,"poolType":"LVM","ho
> st":"192.168.97.2","path":"lvm","port":0,"url":"LVM://192.168.97.2/lvm/?ROLE\u003dPrimary\u0026STOREUUID\u003db114d58e-a37a-6433-c0ff-07f3613a3c68"}},"name":"ROOT-26631","size":21474836480,"path":"48
> fe494b-ee02-4f08-b7aa-975baecd7b3e","volumeId":119075,"vmName":"i-2-26631-VM","accountId":2,"format":"VHD","provisioningType":"THIN","id":119075,"deviceId":0,"cacheMode":"NONE","hypervisorType":"Xe
> nServer"}},"diskSeq":0,"path":"48fe494b-ee02-4f08-b7aa-975baecd7b3e","type":"ROOT","_details":{"managed":"false","storagePort":"0","storageHost":"192.168.97.2","volumeSize":"21474836480"}},{"data":{
> "org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":2000,"defaultNic":true,"pxe
> Disable":false,"nicUuid":"aaef8c14-784c-403f-91fc-b6a3167f2595","uuid":"508d0384-5bf0-4434-8155-0b5bb1b33b43","ip":"192.168.8.112","netmask":"255.255.254.0","gateway":"192.168.9.254","mac":"06:68:80:
> 00:00:7f","dns1":"192.168.0.224","dns2":"192.168.0.224","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isSecurityGroupEnabled":true,"name":"CS-Guest-Public"}],"vcpuMaxLimit":
> 16},"volumeToFiler":{"Vol[119075|ROOT|48fe494b-ee02-4f08-b7aa-975baecd7b3e|21474836480]":{"id":223,"uuid":"bc01ca2b-e6d8-a856-27b5-6f6b55a06b1d","host":"192.168.97.1","path":"lvm","port":0,"type":"L
> VM"}},"contextMap":{"job":"job-347068/job-347069"},"wait":0}}]
> com.google.gson.JsonParseException: Expecting object found:
> "Vol[119075|ROOT|48fe494b-ee02-4f08-b7aa-975baecd7b3e|21474836480]"
> at
> com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:100)
> at
> com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonPrimitive(JsonDeserializationContextDefault.java:85)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:56)
> at com.google.gson.MapTypeAdapter.deserialize(MapTypeAdapter.java:67)
> at com.google.gson.MapTypeAd
[jira] [Created] (CLOUDSTACK-9119) issues with volumes in Expunged state but not removed
Wei Zhou created CLOUDSTACK-9119: Summary: issues with volumes in Expunged state but not removed Key: CLOUDSTACK-9119 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9119 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Wei Zhou Assignee: Wei Zhou sometimes the volume is Expunged but not removed from db. step to reproduce it: (1) create a vm or create/attach a volume (2) download volume (3) expunge the vm, or detach and removed the volume in this case, the volume will be expunged from primary storage, but not removed from database, because a snapshot of volume still exist in secondary storage (when we download the volume). we need to fix the issuse related to this case: (1) resource count of volume and primary storage should not count the Expunged volume (2) delete a Expunge volume (disabled it, or remove it from secondary storage ?) (3) auto-delete the volume from database if the download url are cleaned and files on secondary storage are removed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8937) Xenserver - VM migration with storage fails in a clustered management server setup
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046628#comment-15046628
]
ASF GitHub Bot commented on CLOUDSTACK-8937:
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/1037#issuecomment-162824106
Ping @bhaisaab @atrbgithub
If I get some details on how to test - steps - I can give it a try.
Cheers,
Wilder
> Xenserver - VM migration with storage fails in a clustered management server
> setup
> --
>
> Key: CLOUDSTACK-8937
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8937
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.5.2
>Reporter: CS User
>
> When using the migrateVirtualMachineWithVolume, in a clustered management
> server environment, migrations intermittently fail. This appears to be a
> similar issue to this jira ticket:
> https://issues.apache.org/jira/browse/CLOUDSTACK-8412
> For reference, the error is:
> {noformat}
> ERROR [c.c.a.t.Request] (AgentManager-Handler-11:null) Caught problem with
> [{"com.cloud.agent.api.MigrateWithStorageCommand":{"vm":{"id":26631,"name":"i-2-26631-VM","bootloader":"PyGrub","type":"Us
> er","cpus":1,"minSpeed":1200,"maxSpeed":1200,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
> 5.6 (64-bit)","platformEmulator":"CentOS 5
> (64-bit)","bootArgs":"","enableHA":false,"
> limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"","params":{"memoryOvercommitRatio":"1","platform":"viridian:true;acpi:1;apic:true;pae:true;nx:t
> rue","hypervisortoolsversion":"xenserver56","cpuOvercommitRatio":"4"},"uuid":"b37e76e8-e19a-4100-bf1c-1ee8eba674f2","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"8f51
> e73f-9bfc-4a37-bf86-664067a2cf40","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"b114d58e-a37a-6433-c0ff-07f3613a3c68","id":219,"poolType":"LVM","ho
> st":"192.168.97.2","path":"lvm","port":0,"url":"LVM://192.168.97.2/lvm/?ROLE\u003dPrimary\u0026STOREUUID\u003db114d58e-a37a-6433-c0ff-07f3613a3c68"}},"name":"ROOT-26631","size":21474836480,"path":"48
> fe494b-ee02-4f08-b7aa-975baecd7b3e","volumeId":119075,"vmName":"i-2-26631-VM","accountId":2,"format":"VHD","provisioningType":"THIN","id":119075,"deviceId":0,"cacheMode":"NONE","hypervisorType":"Xe
> nServer"}},"diskSeq":0,"path":"48fe494b-ee02-4f08-b7aa-975baecd7b3e","type":"ROOT","_details":{"managed":"false","storagePort":"0","storageHost":"192.168.97.2","volumeSize":"21474836480"}},{"data":{
> "org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":2000,"defaultNic":true,"pxe
> Disable":false,"nicUuid":"aaef8c14-784c-403f-91fc-b6a3167f2595","uuid":"508d0384-5bf0-4434-8155-0b5bb1b33b43","ip":"192.168.8.112","netmask":"255.255.254.0","gateway":"192.168.9.254","mac":"06:68:80:
> 00:00:7f","dns1":"192.168.0.224","dns2":"192.168.0.224","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://untagged","isSecurityGroupEnabled":true,"name":"CS-Guest-Public"}],"vcpuMaxLimit":
> 16},"volumeToFiler":{"Vol[119075|ROOT|48fe494b-ee02-4f08-b7aa-975baecd7b3e|21474836480]":{"id":223,"uuid":"bc01ca2b-e6d8-a856-27b5-6f6b55a06b1d","host":"192.168.97.1","path":"lvm","port":0,"type":"L
> VM"}},"contextMap":{"job":"job-347068/job-347069"},"wait":0}}]
> com.google.gson.JsonParseException: Expecting object found:
> "Vol[119075|ROOT|48fe494b-ee02-4f08-b7aa-975baecd7b3e|21474836480]"
> at
> com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectDeserializationVisitor.java:100)
> at
> com.google.gson.ReflectingFieldNavigator.visitFieldsReflectively(ReflectingFieldNavigator.java:63)
> at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:120)
> at
> com.google.gson.JsonDeserializationContextDefault.fromJsonPrimitive(JsonDeserializationContextDefault.java:85)
> at
> com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:56)
> at com.google.gson.MapTypeAdapter.deserialize(MapTypeAdapter.java:67)
> at com.google.gson.MapTypeAdapter.deserialize(MapTypeAdapter.java:33)
> at
> com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:51)
> at
> com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:92)
> at
> com.google.gson.JsonObjectDeserializationVisitor.visitFieldUsingCustomHandler(JsonObjectD
[jira] [Commented] (CLOUDSTACK-9112) deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046605#comment-15046605 ] ASF GitHub Bot commented on CLOUDSTACK-9112: Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1180#issuecomment-162821748 Hi @harikrishna-patnala Anyway we can test this? Is there any integration test that we can use to cover your changes? Concerning the new methods you introduced, any chance to get some unit tests to cover the logic? Could you describe which steps you followed to test those changes? Would be nice to come up with some strategy that will help reviewers to test your changes. Cheers, Wilder > deployVM thread is holding the global lock on network longer and cause delays > and some improvements in the planner > -- > > Key: CLOUDSTACK-9112 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9112 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.7.0 > > > There are some VM deployment failures happening when multiple VMs are > deployed at a time, failures mainly due to NetworkModel code that iterates > over all the vlans in the pod. This causes each deployVM thread to hold the > global lock on Network longer and cause delays. This delay in turn causes > more threads to choose same host and fail since capacity is not available on > that host. > Following are some changes required to be done to reduce delays during VM > deployments which in turn causes some vm deployment failures when multiple > VMs are launched at a time. > - In Planner, remove the clusters that do not contain a host with matching > service offering tag. This will save some iterations over clusters that dont > have matching tagged host > - In NetworkModel, do not query the vlans for the pod within the loop. Also > optimized the logic to query the ip/ipv6 > - In DeploymentPlanningManagerImpl, do not process the affinity group if the > plan has hostId provided. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9106) As a Developer I want the Redundant VPC private gateway feature fixed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilder Rodrigues resolved CLOUDSTACK-9106. -- Resolution: Fixed PR merged. > As a Developer I want the Redundant VPC private gateway feature fixed > - > > Key: CLOUDSTACK-9106 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9106 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.6.0 >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues > Fix For: 4.7.0 > > > Bug in BasicNetworkTopology.applyRules() method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
