[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[JIRA]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624489#comment-15624489
 ] 

Özhan Rüzgar Karaman commented on CLOUDSTACK-9503:
--

First for all this is an important bug so thanks for fixing for this bugfix 
[~aprateek] [~jburwell] , i am also following a smilar bug CLOUDSTACK-9319 
which was accepted and will be available for upcoming 4.10 release. Your 
solution has wide coverage area for different host so yours are better, i write 
this comment just for the information and thanks for the great work & effort

> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624300#comment-15624300
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9503:


Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1745
  
@karuturi I guess jenkins' failure is due to env ? 
"ERROR: Step ‘Archive the artifacts’ failed: no workspace for 
cloudstack-pr-analysis #2184"


> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624294#comment-15624294
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9503:


Github user abhinandanprateek closed the pull request at:

https://github.com/apache/cloudstack/pull/1678


> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624293#comment-15624293
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9503:


Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1678
  
@jburwell Created a new PR for 4.8 
https://github.com/apache/cloudstack/pull/1745, closing this one.


> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624292#comment-15624292
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9503:


Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1745
  
Moved PR from 4.9 (https://github.com/apache/cloudstack/pull/1678) to 4.8 
here.


> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624287#comment-15624287
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9503:


GitHub user abhinandanprateek opened a pull request:

https://github.com/apache/cloudstack/pull/1745

CLOUDSTACK-9503: Increased the VR script timeout. Most of the changes…

… are about converting int/long time values to joda Duration.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shapeblue/cloudstack CLOUDSTACK-9503

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1745.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 #1745


commit 32cdcba600260578ec36e7fc875f4bd57442db17
Author: Abhinandan Prateek 
Date:   2016-09-20T07:30:46Z

CLOUDSTACK-9503: Increased the VR script timeout. Most of the changes are 
about converting int/long time values to joda Duration.




> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8830) [VMware] VM snapshot fails for 12 min after instance creation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624140#comment-15624140
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8830:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1677
  
@rhtyd could you check into the status of the test run for this PR?


> [VMware] VM snapshot fails for 12 min after instance creation
> -
>
> Key: CLOUDSTACK-8830
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8830
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Maneesha
>Assignee: Maneesha
>
> ISSUE
> 
> [VMware] VM snapshot fails for 12 min after instance creation
> Environment
> ==
> Product Name: Cloudstack
> Hypervisor: VMWare VSphere 6
> VM DETAILS
> ==
> i-84987-16119-VM
> TROUBLESHOOTING
> ==
> I see that the following failure and immediate success result for the 
> CreateVMSnapshot call
> {noformat}
> 2015-07-24 08:20:55,363 DEBUG [c.c.a.t.Request] 
> (Work-Job-Executor-61:ctx-03fad7f2 job-64835/job-64836 ctx-746f3965) 
> (logid:8b87ab8a) Seq 80-6161487240196259878: Sending  { Cmd , MgmtId: 
> 345051581208, via: 80(ussfoldcsesx112.adslab.local), Ver: v1, Flags: 100011, 
> [{"com.cloud.agent.api.CreateVMSnapshotCommand":{"volumeTOs":[{"uuid":"a89b4ad5-f23f-4df6-84a8-89c4f40b2edb","volumeType":"ROOT","volumeState":"Ready","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"346b381a-8543-3f7b-9eff-fa909ad243c7","id":205,"poolType":"NetworkFilesystem","host":"10.144.35.110","path":"/tintri/ECS-SR-CLD200","port":2049,"url":"NetworkFilesystem://10.144.35.110/tintri/ECS-SR-CLD200/?ROLE=Primary&STOREUUID=346b381a-8543-3f7b-9eff-fa909ad243c7"}},"name":"ROOT-16119","size":1073741824,"path":"ROOT-16119","volumeId":19311,"vmName":"i-84987-16119-VM","vmState":"Running","accountId":84987,"chainInfo":"{\"diskDeviceBusName\":\"ide0:1\",\"diskChain\":[\"[346b381a85433f7b9efffa909ad243c7]
>  i-84987-16119-VM/ROOT-16119.vmdk\",\"[346b381a85433f7b9efffa909ad243c7] 
> 49f59e1a4ce23fec8890c8b9e5891d56/49f59e1a4ce23fec8890c8b9e5891d56.vmdk\"]}","format":"OVA","provisioningType":"THIN","id":19311,"deviceId":0,"cacheMode":"NONE","hypervisorType":"VMware"}],"target":{"id":962,"snapshotName":"i-84987-16119-VM_VS_20150724152053","type":"Disk","current":false,"description":"unit-test-instance-snapshot","quiescevm":false},"vmName":"i-84987-16119-VM","guestOSType":"None","wait":1800}}]
>  }
> 2015-07-24 08:20:55,373 DEBUG [c.c.a.t.Request] 
> (Work-Job-Executor-61:ctx-03fad7f2 job-64835/job-64836 ctx-746f3965) 
> (logid:8b87ab8a) Seq 80-6161487240196259878: Executing:  { Cmd , MgmtId: 
> 345051581208, via: 80(ussfoldcsesx112.adslab.local), Ver: v1, Flags: 100011, 
> [{"com.cloud.agent.api.CreateVMSnapshotCommand":{"volumeTOs":[{"uuid":"a89b4ad5-f23f-4df6-84a8-89c4f40b2edb","volumeType":"ROOT","volumeState":"Ready","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"346b381a-8543-3f7b-9eff-fa909ad243c7","id":205,"poolType":"NetworkFilesystem","host":"10.144.35.110","path":"/tintri/ECS-SR-CLD200","port":2049,"url":"NetworkFilesystem://10.144.35.110/tintri/ECS-SR-CLD200/?ROLE=Primary&STOREUUID=346b381a-8543-3f7b-9eff-fa909ad243c7"}},"name":"ROOT-16119","size":1073741824,"path":"ROOT-16119","volumeId":19311,"vmName":"i-84987-16119-VM","vmState":"Running","accountId":84987,"chainInfo":"{\"diskDeviceBusName\":\"ide0:1\",\"diskChain\":[\"[346b381a85433f7b9efffa909ad243c7]
>  i-84987-16119-VM/ROOT-16119.vmdk\",\"[346b381a85433f7b9efffa909ad243c7] 
> 49f59e1a4ce23fec8890c8b9e5891d56/49f59e1a4ce23fec8890c8b9e5891d56.vmdk\"]}","format":"OVA","provisioningType":"THIN","id":19311,"deviceId":0,"cacheMode":"NONE","hypervisorType":"VMware"}],"target":{"id":962,"snapshotName":"i-84987-16119-VM_VS_20150724152053","type":"Disk","current":false,"description":"unit-test-instance-snapshot","quiescevm":false},"vmName":"i-84987-16119-VM","guestOSType":"None","wait":1800}}]
>  }
> 2015-07-24 08:20:55,374 DEBUG [c.c.a.m.DirectAgentAttache] 
> (DirectAgent-66:ctx-5fbdccd8) (logid:710814a5) Seq 80-6161487240196259878: 
> Executing request
> 2015-07-24 08:20:55,523 ERROR [c.c.h.v.m.VmwareStorageManagerImpl] 
> (DirectAgent-66:ctx-5fbdccd8 ussfoldcsesx112.adslab.local, 
> job-64835/job-64836, cmd: CreateVMSnapshotCommand) (logid:8b87ab8a) failed to 
> create snapshot for vm:i-84987-16119-VM due to null
> 2015-07-24 08:20:55,524 DEBUG [c.c.a.m.DirectAgentAttache] 
> (DirectAgent-66:ctx-5fbdccd8) (logid:8b87ab8a) Seq 80-6161487240196259878: 
> Response Received: 
> 2015-07-24 08:20:55,525 DEBUG [c.c.a.t.Request] (DirectAgent-66:ctx-5fbdccd8) 
> (logid:8b87

[jira] [Commented] (CLOUDSTACK-9071) stats.output.uri stops the server from starting if the uri is malformed

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624136#comment-15624136
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9071:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1673
  
@jburwell a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


> stats.output.uri stops the server from starting if the uri is malformed
> ---
>
> Key: CLOUDSTACK-9071
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9071
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Carles Figuerola
>
> After inputting a malformed uri (was missing the graphite://) and restarting 
> the management service, the application stops at:
> 2015-11-17 11:06:42,861 INFO  [c.c.s.StatsCollector] 
> (localhost-startStop-1:null) metrics.dev.company.net is not a valid protocol 
> for external statistics. No statistics will be send.
> No more logs are output and tomcat is up but serving a completely blank page.
> When the uri has this form: (graphite://metrics.dev.company.net:2013), the 
> end result is very similar to the previous one
> (also, the last word should be "sent")



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9071) stats.output.uri stops the server from starting if the uri is malformed

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624135#comment-15624135
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9071:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1673
  
@blueorangutan test


> stats.output.uri stops the server from starting if the uri is malformed
> ---
>
> Key: CLOUDSTACK-9071
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9071
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Carles Figuerola
>
> After inputting a malformed uri (was missing the graphite://) and restarting 
> the management service, the application stops at:
> 2015-11-17 11:06:42,861 INFO  [c.c.s.StatsCollector] 
> (localhost-startStop-1:null) metrics.dev.company.net is not a valid protocol 
> for external statistics. No statistics will be send.
> No more logs are output and tomcat is up but serving a completely blank page.
> When the uri has this form: (graphite://metrics.dev.company.net:2013), the 
> end result is very similar to the previous one
> (also, the last word should be "sent")



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9379) Support nested virtualization at VM level on VMware Hypervisor

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624078#comment-15624078
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9379:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1542
  
@nvazquez I would like to get this PR merged for 4.10.0.0.  Could you 
please rebase this PR to pull the latest Marvin enhancements/fixes?  Once that 
is done, I will kick off a regression test in preparation to merge it.


> Support nested virtualization at VM level on VMware Hypervisor
> --
>
> Key: CLOUDSTACK-9379
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9379
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.9.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Fix For: 4.10.0.0
>
>
> h2. Introduction
> It is desired to support nested virtualization at VM level for VMware 
> hypervisor. Current behaviour supports enabling/desabling global nested 
> virtualization by modifying global config {{'vmware.nested.virtualization'}}. 
> It is wished to improve this feature, having control at VM level instead of a 
> global control only.
> h2. Proposal
> A new global configuration is added, to enable/disable VM nested 
> virtualization control: {{'vmware.nested.virtualization.perVM'}}. Default 
> value=false
> h2. Behaviour
> After a vm deployment or start command, vm params include 
> {{nestedVirtualizationFlag}} key and its value is:
> * true -> nested virtualization enabled
> * false -> nested virtualization disabled
> We will determinate nested virtualization enabled/disabled by examining:
> * (1) global configuration {{'vmware.nested.virtualization'}} value
> * (2) global configuration {{'vmware.nested.virtualization.perVM'}} value
> * (3) {{'nestedVirtualizationFlag'}} value in {{user_vm_details}} if present, 
> null if not.
> Using this 3 values, there are different use cases:
> # (1) = TRUE, (2) = TRUE, (3) is null -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = TRUE, (2) = FALSE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) is null -> DISABLED
> # (1) = FALSE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = FALSE, (2) = FALSE -> DISABLED



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9498) VR CsFile search utility methods fail when search string has char *, + etc

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624131#comment-15624131
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9498:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1680
  
@jburwell a Trillian-Jenkins test job (centos6 mgmt + vmware55u3) has been 
kicked to run smoke tests


> VR CsFile search utility methods fail when search string has char *, + etc
> --
>
> Key: CLOUDSTACK-9498
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9498
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.8.1, 4.9.0
>Reporter: Murali Reddy
>Assignee: Murali Reddy
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> VR CsFile search utility methods fail when search string has char *, + etc.
> These utility methods in CsFile [1] uses python regular expression module to 
> search a string in a file. However, if caller passes a search string, that 
> has chars *, +, . etc that are also happen to be express wild card / match 
> expression in regular expression results in exceptions from python 're' 
> module.
> For instance searching for VPN user [2] passes "username * password *" as 
> search string, if password has chars the interfer with regular expression 
> metacharecters then search will result in exception.
> 2016-09-12 13:55:48,976 configure.py add_l2tp_ipsec_user:569 Adding vpn user 
> murali * abcd++efgh## *
> 2016-09-12 13:55:48,976 CsFile.py load:39 Reading file /etc/ppp/chap-secrets
> 2016-09-12 13:55:48,976 CsFile.py searchString:140 Searching for murali * 
> abcd++efgh## * string
> 2016-09-12 13:55:48,976 configure.py main:1020 Exception while configuring 
> router
> Traceback (most recent call last):
> File "/opt/cloud/bin/configure.py", line 965, in main
> vpnuser.process()
> File "/opt/cloud/bin/configure.py", line 559, in process
> self.add_l2tp_ipsec_user(user, userconfig)
> File "/opt/cloud/bin/configure.py", line 572, in add_l2tp_ipsec_user
> userfound = file.searchString(userSearchEntry, '#')
> File "/opt/cloud/bin/cs/CsFile.py", line 146, in searchString
> if re.search(search, line):
> File "/usr/lib/python2.7/re.py", line 142, in search
> return _compile(pattern, flags).search(string)
> File "/usr/lib/python2.7/re.py", line 242, in _compile
> raise error, v # invalid expression
> 1 
> https://github.com/apache/cloudstack/blob/master/systemvm/patches/debian/config/opt/cloud/bin/cs/CsFile.py
> 2 
> https://github.com/apache/cloudstack/blob/master/systemvm/patches/debian/config/opt/cloud/bin/configure.py#L572



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9491) Vmware resource: incorrect parsing of device list to find ethener index of plugged nic

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624129#comment-15624129
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9491:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1681
  
@rhtyd could you check into the status of the test run for this PR?


> Vmware resource: incorrect parsing of device list to find ethener index of 
> plugged nic
> --
>
> Key: CLOUDSTACK-9491
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9491
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Murali Reddy
>Assignee: Murali Reddy
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> In VmwareResource.java, there is logic ( in findRouterEthDeviceIndex) to find 
> ethernet interface a mac address is associated with.
> After NIC in plugged in to a Vm through vSphere, it takes some time for the 
> device to show up in the guest VM.
> Logic loops through the device list obtained from /proc/sys/net/ipv4/conf 
> from the VM, and matched againest mac.
> However '/proc/sys/net/ipv4/conf'  is not refreshed, heve logic loops through 
> old device list always.
> In addition there is no exception thrown and error is maked by sending -1. 
> Eventually, VR scripts are getting -1 as device number causing failure in 
> processing the scripts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9498) VR CsFile search utility methods fail when search string has char *, + etc

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624127#comment-15624127
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9498:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1680
  
@blueorangutan test centos6 vmware55u3


> VR CsFile search utility methods fail when search string has char *, + etc
> --
>
> Key: CLOUDSTACK-9498
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9498
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.2, 4.7.1, 4.8.0, 4.8.1, 4.9.0
>Reporter: Murali Reddy
>Assignee: Murali Reddy
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> VR CsFile search utility methods fail when search string has char *, + etc.
> These utility methods in CsFile [1] uses python regular expression module to 
> search a string in a file. However, if caller passes a search string, that 
> has chars *, +, . etc that are also happen to be express wild card / match 
> expression in regular expression results in exceptions from python 're' 
> module.
> For instance searching for VPN user [2] passes "username * password *" as 
> search string, if password has chars the interfer with regular expression 
> metacharecters then search will result in exception.
> 2016-09-12 13:55:48,976 configure.py add_l2tp_ipsec_user:569 Adding vpn user 
> murali * abcd++efgh## *
> 2016-09-12 13:55:48,976 CsFile.py load:39 Reading file /etc/ppp/chap-secrets
> 2016-09-12 13:55:48,976 CsFile.py searchString:140 Searching for murali * 
> abcd++efgh## * string
> 2016-09-12 13:55:48,976 configure.py main:1020 Exception while configuring 
> router
> Traceback (most recent call last):
> File "/opt/cloud/bin/configure.py", line 965, in main
> vpnuser.process()
> File "/opt/cloud/bin/configure.py", line 559, in process
> self.add_l2tp_ipsec_user(user, userconfig)
> File "/opt/cloud/bin/configure.py", line 572, in add_l2tp_ipsec_user
> userfound = file.searchString(userSearchEntry, '#')
> File "/opt/cloud/bin/cs/CsFile.py", line 146, in searchString
> if re.search(search, line):
> File "/usr/lib/python2.7/re.py", line 142, in search
> return _compile(pattern, flags).search(string)
> File "/usr/lib/python2.7/re.py", line 242, in _compile
> raise error, v # invalid expression
> 1 
> https://github.com/apache/cloudstack/blob/master/systemvm/patches/debian/config/opt/cloud/bin/cs/CsFile.py
> 2 
> https://github.com/apache/cloudstack/blob/master/systemvm/patches/debian/config/opt/cloud/bin/configure.py#L572



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9502) Target CLOUDSTACK-9386 into 4.9 release branch

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624119#comment-15624119
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9502:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1676
  
@rhtyd can you check into the status of the test run?


> Target CLOUDSTACK-9386 into 4.9 release branch
> --
>
> Key: CLOUDSTACK-9502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9502
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624113#comment-15624113
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9503:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1678
  
@abhinandanprateek this fix seems like a good fix for 4.8 users as well 
which I would like to get included in 4.8.2.0, as well as, 4.9.1.0 and 
4.10.0.0.  Could rebase this PR and change the base branch to 4.8?


> The router script times out resulting in failure of deployment
> --
>
> Key: CLOUDSTACK-9503
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9503
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0
> Environment: KVM, Xen
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>
> When starting the virtual router in a shared network in advance zone the 
> scripts on router time out. This happen as there are several sub-commands 
> that are consolidated in a single command. The default timeout of 2 minutes 
> is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) Command: com.cloud.agent.api.Command failed while starting 
> virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] 
> (Work-Job-Executor-110:ctx-e8089ec7 job-5135/job-5137 ctx-c3a8da18) 
> (logid:8aedea66) The guru did not like the answers so stopping 
> VM[DomainRouter|r-3445-VM]
> —



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8715) Add support for qemu-guest-agent to libvirt provider

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624094#comment-15624094
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8715:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1545
  
@wido I would like to get this PR merged for 4.10.0.0.  Could you please 
rebase to resolve conflicts and pick up the latest Marvin enhancements/fixes?  
Once this rebase is done, I will kick off KVM regression tests in order to 
merge this PR.


> Add support for qemu-guest-agent to libvirt provider
> 
>
> Key: CLOUDSTACK-8715
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8715
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Reporter: Sten Spans
>Assignee: Wido den Hollander
>  Labels: kvm, libvirt, qemu, systemvm
> Fix For: Future
>
>
> The qemu guest agent is a newer part of qemu/kvm/libvirt which exposes quite 
> a lot of useful functionality, which can only be provided by having an agent 
> on the VM. This includes things like freezing/thawing filesystems (for 
> backups), reading files on the guest, listing interfaces / ip addresses, etc.
> This feature has been requested by users, but is currently not implemented.
> http://users.cloudstack.apache.narkive.com/3TTmy3zj/enabling-qemu-guest-agent
> The first change needed is to add the following to the XML generated for KVM 
> virtual machines,:
> 
>   
>   
> 
> This provides the communication channel between libvirt and the agent on the 
> host. All in all a pretty simple change to LibvirtComputingResource.java / 
> LibvirtVMDef.java
> Secondly the qemu-guest-agent package needs to be added to the systemvm 
> template.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9460) Graceful handling of Mysql server connection timeout

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624068#comment-15624068
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9460:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1674
  
@rhtyd this issue impacts any user with long-running secondary storage 
jobs.  I think it is a valuable fix for all users as the only recourse to fix 
these errors is to manually cleanup the database.

@abhinandanprateek I would like to get this PR merged in time for 4.8.2.0.  
Could you please change the base branch of this PR to 4.8 and rebase it to pull 
in the most recent Marvin enhancements/fixes?


> Graceful handling of Mysql server connection timeout
> 
>
> Key: CLOUDSTACK-9460
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9460
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.9.0
>Reporter: Abhinandan Prateek
>Assignee: Abhinandan Prateek
> Fix For: 4.9.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9402) Nuage VSP Plugin : Support for underlay features (Source & Static NAT to underlay) including Marvin test coverage on master

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624057#comment-15624057
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9402:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1580
  
@nlivens I would like to get this PR merged for 4.10.0.0.  I will code 
review in the next few days.  In the meantime, please rebase this PR to pick up 
the latest Marvin enhancements/fixes, as well as, resolve conflicts, and squash 
the commits.


> Nuage VSP Plugin : Support for underlay features (Source & Static NAT to 
> underlay) including Marvin test coverage on master
> ---
>
> Key: CLOUDSTACK-9402
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9402
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, Network Controller
>Affects Versions: 4.10.0.0
>Reporter: Mani Prashanth Varma Manthena
>Assignee: Nick Livens
>
> Support for underlay features (Source & Static NAT to underlay) with Nuage 
> VSP SDN Plugin including Marvin test coverage for corresponding Source & 
> Static NAT features on master. Moreover, our Marvin tests are written in such 
> a way that they can validate our supported feature set with both Nuage VSP 
> SDN platform's overlay and underlay infra.
> PR contents:
> 1) Support for Source NAT to underlay feature on master with Nuage VSP SDN 
> Plugin.
> 2) Support for Static NAT to underlay feature on master with Nuage VSP SDN 
> Plugin.
> 3) Marvin test coverage for Source & Static NAT to underlay on master with 
> Nuage VSP SDN Plugin.
> 4) Enhancements on our exiting Marvin test code (nuagevsp plugins directory).
> 5) PEP8 & PyFlakes compliance with our Marvin test code.
> Our Marvin test code PEP8 & PyFlakes compliance:
> CloudStack$
> CloudStack$ pep8 --max-line-length=150 test/integration/plugins/nuagevsp/.py
> CloudStack$
> CloudStack$ pyflakes test/integration/plugins/nuagevsp/.py
> CloudStack$
> Validations:
> 1) Underlay infra (Source & Static NAT to underlay)
> Marvin test run:
> nosetests --with-marvin --marvin-config=nuage.cfg 
> plugins/nuagevsp/test_nuage_source_nat.py
> Test results:
> Test Nuage VSP Isolated networks with different combinations of Source NAT 
> service providers ... === TestName: test_01_nuage_SourceNAT_isolated_networks 
> | Status : SUCCESS ===
> ok
> Test Nuage VSP VPC networks with different combinations of Source NAT service 
> providers ... === TestName: test_02_nuage_SourceNAT_vpc_networks | Status : 
> SUCCESS ===
> ok
> Test Nuage VSP Source NAT functionality for Isolated network by performing 
> (wget) traffic tests to the ... === TestName: 
> test_03_nuage_SourceNAT_isolated_network_traffic | Status : SUCCESS ===
> ok
> Test Nuage VSP Source NAT functionality for VPC network by performing (wget) 
> traffic tests to the Internet ... === TestName: 
> test_04_nuage_SourceNAT_vpc_network_traffic | Status : SUCCESS ===
> ok
> Test Nuage VSP Source NAT functionality with different Egress 
> Firewall/Network ACL rules by performing (wget) ... === TestName: 
> test_05_nuage_SourceNAT_acl_rules_traffic | Status : SUCCESS ===
> ok
> Test Nuage VSP Source NAT functionality with VM NIC operations by performing 
> (wget) traffic tests to the ... === TestName: 
> test_06_nuage_SourceNAT_vm_nic_operations_traffic | Status : SUCCESS ===
> ok
> Test Nuage VSP Source NAT functionality with VM migration by performing 
> (wget) traffic tests to the Internet ... === TestName: 
> test_07_nuage_SourceNAT_vm_migration_traffic | Status : SUCCESS ===
> ok
> Test Nuage VSP Source NAT functionality with network restarts by performing 
> (wget) traffic tests to the ... === TestName: 
> test_08_nuage_SourceNAT_network_restarts_traffic | Status : SUCCESS ===
> ok
> --
> Ran 8 tests in 13360.858s
> OK
> Marvin test run:
> nosetests --with-marvin --marvin-config=nuage.cfg 
> plugins/nuagevsp/test_nuage_static_nat.py
> Test results:
> Test Nuage VSP Public IP Range creation and deletion ... === TestName: 
> test_01_nuage_StaticNAT_public_ip_range | Status : SUCCESS ===
> ok
> Test Nuage VSP Nuage Underlay (underlay networking) enabled Public IP Range 
> creation and deletion ... === TestName: 
> test_02_nuage_StaticNAT_underlay_public_ip_range | Status : SUCCESS ===
> ok
> Test Nuage VSP Isolated networks with different combinations of Static NAT 
> service providers ... === TestName: test_03_nuage_StaticNAT_isolated_networks 
> | Status : SUCCESS ===
> ok
> Test Nuage VSP VPC networks with different combinations of Static NAT se

[jira] [Commented] (CLOUDSTACK-9403) Nuage VSP Plugin : Support for SharedNetwork fuctionality including Marvin test coverage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624055#comment-15624055
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9403:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1579
  
@nlivens I would like to get this PR merged for 4.10.0.0.  I will code 
review in the next few days.  In the meantime, please rebase this PR to pick up 
the latest Marvin enhancements/fixes, as well as, resolve conflicts, and squash 
the commits.


> Nuage VSP Plugin : Support for SharedNetwork fuctionality including Marvin 
> test coverage
> 
>
> Key: CLOUDSTACK-9403
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9403
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, Network Controller
>Reporter: Rahul Singal
>Assignee: Nick Livens
>
> This is first phase of support of Shared Network in cloudstack through 
> NuageVsp Network Plugin. A shared network is a type of virtual network that 
> is shared between multiple accounts i.e. a shared network can be accessed by 
> virtual machines that belong to many different accounts. This basic 
> functionality will be supported with the below common use case:
> - shared network can be used for monitoring purposes. A shared network can be 
> assigned to a domain and can be used for monitoring VMs  belonging to all 
> accounts in that domain.
> - Public accessible of shared Network.
> With the current implementation with NuageVsp plugin, It support over-lapping 
> of Ip address, Public Access and also adding Ip ranges in shared Network.
> In VSD, it is implemented in below manner:
> - In order to have tenant isolation for shared networks, we will have to 
> create a Shared L3 Subnet for each shared network, and instantiate it across 
> the relevant enterprises. A shared network will only exist under an 
> enterprise when it is needed, so when the first VM is spinned under that ACS 
> domain inside that shared network.
> - For public shared Network it will also create a floating ip subnet pool in 
> VSD along with all the things mentioned in above point.
> PR contents:
> 1) Support for shared networks with tenant isolation on master with Nuage VSP 
> SDN Plugin.
> 2) Support of shared network with publicly accessible ip ranges.  
> 2) Marvin test coverage for shared networks on master with Nuage VSP SDN 
> Plugin.
> 3) Enhancements on our exiting Marvin test code (nuagevsp plugins directory).
> 4) PEP8 & PyFlakes compliance with our Marvin test code.
> Test Results are:-
> Valiate that ROOT admin is NOT able to deploy a VM for a user in ROOT domain 
> in a shared network with ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_account_ROOTuser | Status : 
> SUCCESS ===
> ok
> Valiate that ROOT admin is NOT able to deploy a VM for a admin user in a 
> shared network with ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_account_differentdomain | 
> Status : SUCCESS ===
> ok
> Valiate that ROOT admin is NOT able to deploy a VM for admin user in the same 
> domain but in a ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_account_domainadminuser | 
> Status : SUCCESS ===
> ok
> Valiate that ROOT admin is NOT able to deploy a VM for user in the same 
> domain but in a different ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_account_domainuser | Status : 
> SUCCESS ===
> ok
> Valiate that ROOT admin is able to deploy a VM for regular user in a shared 
> network with scope=account ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_account_user | Status : SUCCESS 
> ===
> ok
> Valiate that ROOT admin is able to deploy a VM for user in ROOT domain in a 
> shared network with scope=all ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_all_ROOTuser | Status : SUCCESS 
> ===
> ok
> Valiate that ROOT admin is able to deploy a VM for a domain admin users in a 
> shared network with scope=all ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_all_domainadminuser | Status : 
> SUCCESS ===
> ok
> Valiate that ROOT admin is able to deploy a VM for other users in a shared 
> network with scope=all ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_all_domainuser | Status : 
> SUCCESS ===
> ok
> Valiate that ROOT admin is able to deploy a VM for admin user in a domain in 
> a shared network with scope=all ... === TestName: 
> test_deployVM_in_sharedNetwork_as_admin_scope_all_subdomainadminuser | Status 
> : SUCCESS ===
> ok
> Valiate that ROOT admin is able to deploy a VM for any user in a subdomain in 
> a sha

[jira] [Commented] (CLOUDSTACK-9321) Multiple Internal LB rules (more than one Internal LB rule with same source IP address) are not getting resolved in the corresponding InternalLbVm instance's hapro

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624053#comment-15624053
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9321:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1577
  
@nlivens I would like to get this PR merged for 4.10.0.0.  I will code 
review in the next few days.  In the meantime, please rebase this PR to pick up 
the latest Marvin enhancements/fixes and squash the commits.


> Multiple Internal LB rules (more than one Internal LB rule with same source 
> IP address) are not getting resolved in the corresponding InternalLbVm 
> instance's haproxy.cfg file
> --
>
> Key: CLOUDSTACK-9321
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9321
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Network Controller
>Reporter: Mani Prashanth Varma Manthena
>Assignee: Nick Livens
>Priority: Critical
> Fix For: 4.9.1.0
>
>
> Multiple Internal LB rules (more than one Internal LB rule with same source 
> IP address) are not getting resolved in the corresponding InternalLbVm 
> instance's haproxy.cfg file. Moreover, each time a new Internal LB rule is 
> added to the corresponding InternalLbVm instance, it replaces the existing 
> one. Thus, traffic corresponding to these un-resolved (old) Internal LB rules 
> are getting dropped by the InternalLbVm instance.
> PR contents:
> 1) Fix for this bug.
> 2) Marvin test coverage for Internal LB feature on master with native ACS 
> setup (component directory) including validations for this bug fix.
> 3) Enhancements on our exiting Internal LB Marvin test code (nuagevsp plugins 
> directory) to validate this bug fix.
> 4) PEP8 & PyFlakes compliance with the added Marvin test code.
> Added Marvin test code PEP8 & PyFlakes compliance:
> CloudStack$
> CloudStack$ pep8 --max-line-length=150 
> test/integration/component/test_vpc_network_internal_lbrules.py
> CloudStack$
> CloudStack$ pyflakes 
> test/integration/component/test_vpc_network_internal_lbrules.py
> CloudStack$
> CloudStack$ pep8 --max-line-length=150 test/integration/plugins/nuagevsp/.py
> CloudStack$
> CloudStack$ pyflakes test/integration/plugins/nuagevsp/.py
> CloudStack$
> Validations:
> 1) Made sure that we didn't break any Public LB (VpcVirtualRouter) 
> functionality.
> Marvin test run:
> nosetests --with-marvin --marvin-config=nuage.cfg 
> test/integration/component/test_vpc_network_lbrules.py
> Test results:
> Test case no 210 and 227: List Load Balancing Rules belonging to a VPC ... 
> === TestName: test_01_VPC_LBRulesListing | Status : SUCCESS ===
> ok
> Test Create LB rules for 1 network which is part of a two/multiple virtual 
> networks of a ... === TestName: test_02_VPC_CreateLBRuleInMultipleNetworks | 
> Status : SUCCESS ===
> ok
> Test case no 222 : Create LB rules for a two/multiple virtual networks of a 
> ... === TestName: test_03_VPC_CreateLBRuleInMultipleNetworksVRStoppedState | 
> Status : SUCCESS ===
> ok
> Test case no 222 : Create LB rules for a two/multiple virtual networks of a 
> ... === TestName: test_04_VPC_CreateLBRuleInMultipleNetworksVRStoppedState | 
> Status : SUCCESS ===
> ok
> Test case no 214 : Delete few(not all) LB rules for a single virtual network 
> of a ... === TestName: test_05_VPC_CreateAndDeleteLBRule | Status : SUCCESS 
> ===
> ok
> Test Delete few(not all) LB rules for a single virtual network of ... === 
> TestName: test_06_VPC_CreateAndDeleteLBRuleVRStopppedState | Status : SUCCESS 
> ===
> ok
> Test Delete all LB rules for a single virtual network of a ... === TestName: 
> test_07_VPC_CreateAndDeleteAllLBRule | Status : SUCCESS ===
> ok
> Test Delete all LB rules for a single virtual network of a ... === TestName: 
> test_08_VPC_CreateAndDeleteAllLBRuleVRStoppedState | Status : SUCCESS ===
> ok
> Test User should not be allowed to create a LB rule for a VM that belongs to 
> a different VPC. ... === TestName: test_09_VPC_LBRuleCreateFailMultipleVPC | 
> Status : SUCCESS ===
> ok
> Test User should not be allowed to create a LB rule for a VM that does not 
> belong to any VPC. ... === TestName: 
> test_10_VPC_FailedToCreateLBRuleNonVPCNetwork | Status : SUCCESS ===
> ok
> Test case no 217 and 236: User should not be allowed to create a LB rule for 
> a ... === TestName: test_11_VPC_LBRuleCreateNotAllowed | Status : SUCCESS ===
> ok
> Test User should not be allowed to create a LB rule on an Ipaddress that 
> Source Nat enabled. ... === TestName: test_12_VPC_LBRuleCreateFailF

[jira] [Commented] (CLOUDSTACK-9401) Nuage VSP Plugin : Support for InternalDns including Marvin test coverage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624040#comment-15624040
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9401:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1578
  
@nlivens I would like to get this PR into 4.10.0.0.  Could you please 
squash the commits?  Once this is done, I will trigger a regression test across 
VMware, KVM, and XenServer.


> Nuage VSP Plugin : Support for InternalDns including Marvin test coverage
> -
>
> Key: CLOUDSTACK-9401
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9401
> Project: CloudStack
>  Issue Type: Task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, Network Controller
>Reporter: Rahul Singal
>Assignee: Nick Livens
>
> Supporting Internal Dns by using Dns service provider as Virtual Router but 
> Dhcp provider will be NuageVsp. The idea is here is to keep using Internal 
> Dns service of cloudstack when network provider is some other vendor.
> A sample network offering will be like below one:-
> Service   Provider
> DHCP NuageVsp
> DNSVirtualRouter/VpcVirtualRouter
> UserDataVirtualRouter/VpcVirtualRouter
> Virtual Networking   NuageVsp
> SourceNat   NuageVsp
> StaticNat NuageVsp
> NetworkAcl/FirewallNuageVsp
> Testrun:-
> Verify InternalDns on Isolated Network ... === TestName: 
> test_01_Isolated_Network_with_zone | Status : SUCCESS ===
> ok
> Verify InternalDns on Isolated Network with ping by hostname ... === 
> TestName: test_02_Isolated_Network | Status : SUCCESS ===
> ok
> Verify update NetworkDomain for InternalDns on Isolated Network ... === 
> TestName: test_03_Update_Network_with_Domain | Status : SUCCESS ===
> ok
> Verify update NetworkDomain for InternalDns on Isolated Network with ping VM 
> ... === TestName: test_04_Update_Network_with_Domain | Status : SUCCESS ===
> ok
> Verify InternalDns on VPC Network ... === TestName: 
> test_05_VPC_Network_With_InternalDns | Status : SUCCESS ===
> ok
> Verify InternalDns on VPC Network by ping with hostname ... === TestName: 
> test_06_VPC_Network_With_InternalDns | Status : SUCCESS ===
> ok
> --
> Ran 6 tests in 5736.562s
> OK
> cloudstack$ pep8 --max-line-length=150 test_internal_dns.py
> cloudstack$  pyflakes test_internal_dns.py
> cloudstack$



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623744#comment-15623744
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9183:


GitHub user olafurgreen reopened a pull request:

https://github.com/apache/cloudstack/pull/1744

CLOUDSTACK-9183: bash: /opt/cloud/bin/getRouterAlerts.sh: No such fil…

…e or directory

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/greenqloud/cloudstack 4.7

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1744.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 #1744


commit 420d06f4d371e31761440c3d3957bab737531af3
Author: Ólafur Stefán Arnarsson 
Date:   2016-10-31T21:44:15Z

CLOUDSTACK-9183: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
directory




> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623740#comment-15623740
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9183:


Github user olafurgreen commented on the issue:

https://github.com/apache/cloudstack/pull/1744
  
Seams like Wilder Rodrigues accidentally deleted this file so I just want 
to bring back.


> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623741#comment-15623741
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9183:


Github user olafurgreen closed the pull request at:

https://github.com/apache/cloudstack/pull/1744


> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9183) CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623606#comment-15623606
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9183:


GitHub user olafurgreen opened a pull request:

https://github.com/apache/cloudstack/pull/1744

CLOUDSTACK-9183: bash: /opt/cloud/bin/getRouterAlerts.sh: No such fil…

…e or directory

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/greenqloud/cloudstack 4.7

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1744.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 #1744


commit 420d06f4d371e31761440c3d3957bab737531af3
Author: Ólafur Stefán Arnarsson 
Date:   2016-10-31T21:44:15Z

CLOUDSTACK-9183: bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
directory




> CS 4.7.0 bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or directory
> ---
>
> Key: CLOUDSTACK-9183
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9183
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM
>Affects Versions: 4.7.0
> Environment: CloudStack 4.7.0 RC1, Ubuntu 14.04.3, KVM, NFS
>Reporter: Milamber
>  Labels: kvm, systemvm
>
> On my 4.7.0 RC1 test environment, I've this warning message:
> 2015-12-15 23:57:35,165 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:ctx-f1556e81) (logid:db80c3d4) Unable to get alerts 
> from router r-11-VM bash: /opt/cloud/bin/getRouterAlerts.sh: No such file or 
> directory
> I don't find this bash script anywhere (on management node, host node and 
> inside the VR)
> I find theses references to this script inside:
> public static final String ROUTER_ALERTS = "getRouterAlerts.sh";
> ./core/src/com/cloud/agent/resource/virtualnetwork/VRScripts.java
> ExecutionResult result = _vrDeployer.executeInVR(routerIp, 
> VRScripts.ROUTER_ALERTS, args);
> ./core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8326) Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP Debian Wheezy specific

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623156#comment-15623156
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8326:


GitHub user wido opened a pull request:

https://github.com/apache/cloudstack/pull/1743

CLOUDSTACK-8326: Always fill UDP checksums in DHCP replies in VR

In some cases the UDP checksums in packets from DHCP servers are
incorrect. This is a problem for some DHCP clients that ignore
packets with bad checksums. This patch inserts an iptables rule
to ensure DHCP servers always send packets with correct checksums.

Due to this bug DHCP offers are sometimes not accepted by Instances.

The end-result without this fix is no connectivity for the Instance
due to the lack of a IPv4 address.

Signed-off-by: Wido den Hollander 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/wido/cloudstack CLOUDSTACK-8326

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1743.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 #1743


commit 32689b26d0f2f6763604b2b67649cca9e470fcf7
Author: Wido den Hollander 
Date:   2016-10-31T19:43:39Z

CLOUDSTACK-8326: Always fill UDP checksums in DHCP replies in VR

In some cases the UDP checksums in packets from DHCP servers are
incorrect. This is a problem for some DHCP clients that ignore
packets with bad checksums. This patch inserts an iptables rule
to ensure DHCP servers always send packets with correct checksums.

Due to this bug DHCP offers are sometimes not accepted by Instances.

The end-result without this fix is no connectivity for the Instance
due to the lack of a IPv4 address.

Signed-off-by: Wido den Hollander 




> Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP 
> Debian Wheezy specific
> ---
>
> Key: CLOUDSTACK-8326
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8326
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Virtual Router
>Affects Versions: 4.3.2
> Environment: Ubuntu 12.04.5 for Host
> Debian Squeeze for VR
>Reporter: Ivan A Kudryavtsev
>Assignee: Wido den Hollander
> Fix For: Future, 4.10.0.0, 4.9.2.0
>
>
> I've found bug in DHCP component of VR 4.3.2. The bug is completely described 
> at:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217
> DHCP responses with bad checksum. As a result, dhcp client unable to get 
> lease: "dhcpd: 5 bad udp checksums in 5 packets"
> Hotfix is:
> iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM 
> --checksum-fill
> on VR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-8326) Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP Debian Wheezy specific

[Wido den Hollander (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wido den Hollander updated CLOUDSTACK-8326:
---
Fix Version/s: 4.9.2.0
   4.10.0.0
   Future

> Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP 
> Debian Wheezy specific
> ---
>
> Key: CLOUDSTACK-8326
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8326
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Virtual Router
>Affects Versions: 4.3.2
> Environment: Ubuntu 12.04.5 for Host
> Debian Squeeze for VR
>Reporter: Ivan A Kudryavtsev
>Assignee: Wido den Hollander
> Fix For: Future, 4.10.0.0, 4.9.2.0
>
>
> I've found bug in DHCP component of VR 4.3.2. The bug is completely described 
> at:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217
> DHCP responses with bad checksum. As a result, dhcp client unable to get 
> lease: "dhcpd: 5 bad udp checksums in 5 packets"
> Hotfix is:
> iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM 
> --checksum-fill
> on VR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8326) Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP Debian Wheezy specific

[Wido den Hollander (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623129#comment-15623129
 ] 

Wido den Hollander commented on CLOUDSTACK-8326:


This is also affecting me and a more detailed report can be found on Github 
about this: https://github.com/projectcalico/felix/issues/40

A short quote:

"My CirrOS based virtual machines Linux cirros 3.2.0-68-virtual #102-Ubuntu SMP 
Tue Aug 12 22:14:39 UTC 2014 x86_64 GNU/Linux ignore the DHCP reply sent by 
dnsmasq. When tcpdumping on the VM's tap interface, I can see the DHCP request 
AND the DHCP reply, but the reply is not accepted.

It appears to be down to a problem with checksum generation, which usually only 
happens on the physical interface (offloading), but with Calico all DHCP 
happens inside the same compute node and only goes from the dnsmasq ns to the 
relevant tap ports...

A workaround that helped me make my instances accept the DHCP reply is adding 
the following iptables/mangle entry on my compute node:

iptables -A POSTROUTING -t mangle -p udp --dport bootpc -d 100.64.0.0/10 -j 
CHECKSUM --checksum-fill"

> Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP 
> Debian Wheezy specific
> ---
>
> Key: CLOUDSTACK-8326
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8326
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Virtual Router
>Affects Versions: 4.3.2
> Environment: Ubuntu 12.04.5 for Host
> Debian Squeeze for VR
>Reporter: Ivan A Kudryavtsev
>Assignee: Wido den Hollander
> Fix For: Future, 4.10.0.0, 4.9.2.0
>
>
> I've found bug in DHCP component of VR 4.3.2. The bug is completely described 
> at:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217
> DHCP responses with bad checksum. As a result, dhcp client unable to get 
> lease: "dhcpd: 5 bad udp checksums in 5 packets"
> Hotfix is:
> iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM 
> --checksum-fill
> on VR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CLOUDSTACK-8326) Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP Debian Wheezy specific

[Wido den Hollander (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wido den Hollander reassigned CLOUDSTACK-8326:
--

Assignee: Wido den Hollander

> Bug in cloudstack virtual router (KVM) in Simple zone with public ips / DHCP 
> Debian Wheezy specific
> ---
>
> Key: CLOUDSTACK-8326
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8326
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Virtual Router
>Affects Versions: 4.3.2
> Environment: Ubuntu 12.04.5 for Host
> Debian Squeeze for VR
>Reporter: Ivan A Kudryavtsev
>Assignee: Wido den Hollander
>
> I've found bug in DHCP component of VR 4.3.2. The bug is completely described 
> at:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217
> DHCP responses with bad checksum. As a result, dhcp client unable to get 
> lease: "dhcpd: 5 bad udp checksums in 5 packets"
> Hotfix is:
> iptables -A POSTROUTING -t mangle -p udp --dport bootpc -j CHECKSUM 
> --checksum-fill
> on VR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Description: 
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!http://www.host.com/image.gif!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.

  was:
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!PS.PNG|thumbnail!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.


> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> !http://www.host.com/image.gif!
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Description: 
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG|align=left!
!https://issues.apache.org/jira/secure/attachment/12836196/PS-DETAILS.PNG|align=right!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.

  was:
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.


> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> !https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG|align=left!
> !https://issues.apache.org/jira/secure/attachment/12836196/PS-DETAILS.PNG|align=right!
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Description: 
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!https://issues.apache.org/jira/secure/attachment/12836196/PS-DETAILS.PNG!
!https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.

  was:
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG|align=left!
!https://issues.apache.org/jira/secure/attachment/12836196/PS-DETAILS.PNG|align=right!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.


> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> !https://issues.apache.org/jira/secure/attachment/12836196/PS-DETAILS.PNG!
> !https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG!
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Description: 
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.

  was:
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!http://www.host.com/image.gif!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.


> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> !https://issues.apache.org/jira/secure/attachment/12836195/PS.PNG!
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Description: 
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

!PS.PNG|thumbnail!

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.

  was:
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.


h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.


> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> !PS.PNG|thumbnail!
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Description: 
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.


h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.

  was:
h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.


> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Vazquez updated CLOUDSTACK-9574:

Attachment: PS-DETAILS.PNG
PS.PNG

Screenshots

> Redesign storage tags for primary storage
> -
>
> Key: CLOUDSTACK-9574
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UI
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Attachments: PS-DETAILS.PNG, PS.PNG
>
>
> h3. Actual behavior
> Primary storage tags are being saved as an entry on {{storage_pool_details}} 
> with:
> * name = TAG_NAME
> * value = "true"
> When a boolean property is defined in {{storage_pool_details}} and has value 
> = "true", it is displayed as a tag.
> h3. Goal
> Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host 
> Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9574) Redesign storage tags for primary storage

[Nicolas Vazquez (JIRA)]

Nicolas Vazquez created CLOUDSTACK-9574:
---

 Summary: Redesign storage tags for primary storage
 Key: CLOUDSTACK-9574
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9574
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API, UI
Reporter: Nicolas Vazquez
Assignee: Nicolas Vazquez


h3. Actual behavior

Primary storage tags are being saved as an entry on {{storage_pool_details}} 
with:
* name = TAG_NAME
* value = "true"

When a boolean property is defined in {{storage_pool_details}} and has value = 
"true", it is displayed as a tag.

h3. Goal

Redesign {{Storage Tags}} for Primary Storage view, as it is done in Host Tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9502) Target CLOUDSTACK-9386 into 4.9 release branch

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622772#comment-15622772
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9502:


Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1676
  
Thanks! @jburwell 


> Target CLOUDSTACK-9386 into 4.9 release branch
> --
>
> Key: CLOUDSTACK-9502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9502
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9502) Target CLOUDSTACK-9386 into 4.9 release branch

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622573#comment-15622573
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9502:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1676
  
@nvazquez kicking regression tests now.  If they pass, then I will add my 
LGTM and merge.


> Target CLOUDSTACK-9386 into 4.9 release branch
> --
>
> Key: CLOUDSTACK-9502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9502
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9502) Target CLOUDSTACK-9386 into 4.9 release branch

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622572#comment-15622572
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9502:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1676
  
@jburwell a Trillian-Jenkins test job (centos6 mgmt + vmware55u3) has been 
kicked to run smoke tests


> Target CLOUDSTACK-9386 into 4.9 release branch
> --
>
> Key: CLOUDSTACK-9502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9502
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9502) Target CLOUDSTACK-9386 into 4.9 release branch

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622570#comment-15622570
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9502:


Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1676
  
@blueorangutan test centos6 vmware55u3


> Target CLOUDSTACK-9386 into 4.9 release branch
> --
>
> Key: CLOUDSTACK-9502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9502
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9502) Target CLOUDSTACK-9386 into 4.9 release branch

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622382#comment-15622382
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9502:


Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1676
  
Hi @rhtyd @jburwell could this be merged?


> Target CLOUDSTACK-9386 into 4.9 release branch
> --
>
> Key: CLOUDSTACK-9502
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9502
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9498) VR CsFile search utility methods fail when search string has char *, + etc

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621763#comment-15621763
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9498:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1680
  
Trillian test result (tid-228)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 27152 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1680-t228-kvm-centos7.zip
Test completed. 46 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_02_redundant_VPC_default_routes | `Failure` | 869.98 | 
test_vpc_redundant.py
ContextSuite context=TestRVPCSite2SiteVpn>:setup | `Error` | 0.00 | 
test_vpc_vpn.py
test_01_vpc_site2site_vpn | Success | 160.40 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.16 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 275.84 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 558.87 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 516.84 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1420.15 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 554.03 | test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1297.41 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 15.44 | test_volumes.py
test_08_resize_volume | Success | 15.43 | test_volumes.py
test_07_resize_fail | Success | 20.44 | test_volumes.py
test_06_download_detached_volume | Success | 15.32 | test_volumes.py
test_05_detach_volume | Success | 100.24 | test_volumes.py
test_04_delete_attached_volume | Success | 10.20 | test_volumes.py
test_03_download_attached_volume | Success | 15.28 | test_volumes.py
test_02_attach_volume | Success | 73.78 | test_volumes.py
test_01_create_volume | Success | 712.50 | test_volumes.py
test_deploy_vm_multiple | Success | 273.65 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.62 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.20 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 40.92 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.13 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.86 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.84 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.18 | test_vm_life_cycle.py
test_01_stop_vm | Success | 40.34 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 60.66 | test_templates.py
test_08_list_system_templates | Success | 0.04 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.07 | test_templates.py
test_04_extract_template | Success | 5.17 | test_templates.py
test_03_delete_template | Success | 5.12 | test_templates.py
test_02_edit_template | Success | 90.15 | test_templates.py
test_01_create_template | Success | 50.61 | test_templates.py
test_10_destroy_cpvm | Success | 161.64 | test_ssvm.py
test_09_destroy_ssvm | Success | 168.57 | test_ssvm.py
test_08_reboot_cpvm | Success | 161.86 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.64 | test_ssvm.py
test_06_stop_cpvm | Success | 131.68 | test_ssvm.py
test_05_stop_ssvm | Success | 133.74 | test_ssvm.py
test_04_cpvm_internals | Success | 1.21 | test_ssvm.py
test_03_ssvm_internals | Success | 3.31 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.09 | test_snapshots.py
test_04_change_offering_small | Success | 239.50 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.05 | test_service_offerings.py
test_01_create_service_offering | Success | 0.11 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.18 | test_secondary_storage.py
test_09_reboot_router | Success | 35.31 | test_routers.py
test_08_start_router | Success | 30.30 | test_routers.py
test_07_stop_router | Success | 10.18 | test_routers.py
test_06_router_advanced | Success | 0.06 | test_routers.py
test_05_router_basic | Success | 0.04 | test_routers.py
test_04_restart_network_wo_cleanup | Success | 5.70 | test_routers.py
tes

[jira] [Commented] (CLOUDSTACK-9552) KVM Security Groups do not allow DNS over TCP egress

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621660#comment-15621660
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9552:


Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1713
  
@jburwell I rebased it against 4.9, checks are running now.

Regarding Marvin, I have to be honest, I wouldn't know where to start for 
adding such a test. Do we also have Basic Networking tests at all to test stuff 
like this?


> KVM Security Groups do not allow DNS over TCP egress
> 
>
> Key: CLOUDSTACK-9552
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9552
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.8.0, 4.9.0
> Environment: KVM Basic Networking
>Reporter: Wido den Hollander
>Assignee: Wido den Hollander
>  Labels: dns, dnssec, security-groups
> Fix For: Future
>
>
> When egress filtering is configured all outbound traffic is blocked unless 
> configured otherwise.
> With the exception that UDP/53 DNS is allowed implicitly by the Security 
> Groups.
> Many DNS responses are larger then 4k, with DNSSEC for example and require 
> TCP to be allowed.
> The Security Groups should also allow TCP/53 when egress filtering is 
> configured.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)