[jira] [Commented] (CLOUDSTACK-10296) Fix timestamp difference in heartbeat script for rVRs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10296:
-

ustcweizhou commented on issue #2458: CLOUDSTACK-10296: Find time different 
from last timestamp
URL: https://github.com/apache/cloudstack/pull/2458#issuecomment-368760532
 
 
   We met the issue several times on our production.
   the final change is
   ```
   diff --git 
a/systemvm/patches/debian/config/opt/cloud/templates/check_heartbeat.sh.templ 
b/systemvm/patches/debian/config/opt/cloud/templates/check_heartbeat.sh.templ
   index 6a0d8a9..a8ddc7d 100755
   --- 
a/systemvm/patches/debian/config/opt/cloud/templates/check_heartbeat.sh.templ
   +++ 
b/systemvm/patches/debian/config/opt/cloud/templates/check_heartbeat.sh.templ
   @@ -19,14 +19,29 @@
ROUTER_BIN_PATH=/ramdisk/rrouter
ROUTER_LOG=${ROUTER_BIN_PATH}/keepalived.log
STRIKE_FILE="$ROUTER_BIN_PATH/keepalived.strikes"
   +CHECKTIME_FILE="$ROUTER_BIN_PATH/keepalived.checktime"
   
if [ -e $ROUTER_BIN_PATH/keepalived.ts2 ]
then
thistime=$(cat $ROUTER_BIN_PATH/keepalived.ts)
lasttime=$(cat $ROUTER_BIN_PATH/keepalived.ts2)
   -diff=$(($lasttime - $thistime))
   +diff=$(($thistime - $lasttime))
   +lastcheck=0
   +if [ -e $CHECKTIME_FILE ]
   +then
   +lastcheck=`cat $CHECKTIME_FILE 2>/dev/null`
   +fi
   +thischeck=$(date +%s)
   +checkdiff=$(($thischeck - $lastcheck))
   +echo "thischeck: $thischeck, lastcheck: $lastcheck. this heartbeat: 
$thistime, last heartbeat: $lasttime, time diff: $diff" >> $ROUTER_LOG
   +if [ $checkdiff -ge 0 ] && [ $checkdiff -lt 30 ]
   +then
   +echo time duration after last check is less than 30 seconds, 
ignored >> $ROUTER_LOG
   +exit
   +fi
   +echo $thischeck > $CHECKTIME_FILE
s=0
   -if [ $diff -ge 10 ]
   +if [ $diff -lt 30 ]
then
if [ -e $STRIKE_FILE ]
then
   ```


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix timestamp difference in heartbeat script for rVRs
> -
>
> Key: CLOUDSTACK-10296
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.9.3.0
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Raised recently on dev@ ML by Jayakartheek, the difference code in heartbeat 
> checker script for rVRs wrongly take difference, that will always be less 
> than or equal to 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10296) Fix timestamp difference in heartbeat script for rVRs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10296:
-

rhtyd commented on issue #2458: CLOUDSTACK-10296: Find time different from last 
timestamp
URL: https://github.com/apache/cloudstack/pull/2458#issuecomment-368649529
 
 
   @blueorangutan test
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix timestamp difference in heartbeat script for rVRs
> -
>
> Key: CLOUDSTACK-10296
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.9.3.0
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Raised recently on dev@ ML by Jayakartheek, the difference code in heartbeat 
> checker script for rVRs wrongly take difference, that will always be less 
> than or equal to 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10296) Fix timestamp difference in heartbeat script for rVRs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10296:
-

blueorangutan commented on issue #2458: CLOUDSTACK-10296: Find time different 
from last timestamp
URL: https://github.com/apache/cloudstack/pull/2458#issuecomment-368649652
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix timestamp difference in heartbeat script for rVRs
> -
>
> Key: CLOUDSTACK-10296
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.9.3.0
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Raised recently on dev@ ML by Jayakartheek, the difference code in heartbeat 
> checker script for rVRs wrongly take difference, that will always be less 
> than or equal to 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10296) Fix timestamp difference in heartbeat script for rVRs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10296:
-

blueorangutan commented on issue #2458: CLOUDSTACK-10296: Find time different 
from last timestamp
URL: https://github.com/apache/cloudstack/pull/2458#issuecomment-368643189
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1735


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix timestamp difference in heartbeat script for rVRs
> -
>
> Key: CLOUDSTACK-10296
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.9.3.0
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Raised recently on dev@ ML by Jayakartheek, the difference code in heartbeat 
> checker script for rVRs wrongly take difference, that will always be less 
> than or equal to 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10296) Fix timestamp difference in heartbeat script for rVRs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10296:
-

blueorangutan commented on issue #2458: CLOUDSTACK-10296: Find time different 
from last timestamp
URL: https://github.com/apache/cloudstack/pull/2458#issuecomment-368632704
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix timestamp difference in heartbeat script for rVRs
> -
>
> Key: CLOUDSTACK-10296
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.9.3.0
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Raised recently on dev@ ML by Jayakartheek, the difference code in heartbeat 
> checker script for rVRs wrongly take difference, that will always be less 
> than or equal to 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10296) Fix timestamp difference in heartbeat script for rVRs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10296:
-

rhtyd commented on issue #2458: CLOUDSTACK-10296: Find time different from last 
timestamp
URL: https://github.com/apache/cloudstack/pull/2458#issuecomment-368632376
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Fix timestamp difference in heartbeat script for rVRs
> -
>
> Key: CLOUDSTACK-10296
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.9.3.0
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Raised recently on dev@ ML by Jayakartheek, the difference code in heartbeat 
> checker script for rVRs wrongly take difference, that will always be less 
> than or equal to 0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10307:
-

rafaelweingartner commented on issue #2438: [CLOUDSTACK-10307] Remove unused 
things from HostDaoImpl
URL: https://github.com/apache/cloudstack/pull/2438#issuecomment-368620530
 
 
   @borisstoyanov is this "test_hostha_enable_ha_when_host_in_maintenance" 
failure a false positive?
I have seen this around in some other PRs.
   In the log file I see the following:
   `2018-02-26 19:01:11,248 DEBUG [c.c.a.m.AgentManagerImpl] 
(API-Job-Executor-63:ctx-62ff4a7f job-2987 ctx-3ead5878) (logid:c3cec415) Can 
not send command com.cloud.agent.api.MaintainCommand due to Host 2 is not up`
   
   It looks like an environment problem.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove unused things from HostDaoImpl
> -
>
> Key: CLOUDSTACK-10307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> Remove unnecessary annotation of HostDaoImpl. While removing this annotation 
> I noticed that one of the methods were not necessary. While removing it, I 
> found some code in CloudZonesStartupProcessor that was also not used, and 
> removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10306:
-

blueorangutan commented on issue #2467: CLOUDSTACK-10306: Upgrade to VMware 6.5 
vim jar dependency
URL: https://github.com/apache/cloudstack/pull/2467#issuecomment-368618240
 
 
   Trillian test result (tid-2281)
   Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 28185 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2467-t2281-vmware-65.zip
   Smoke tests completed. 67 look OK, 0 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10307:
-

blueorangutan commented on issue #2438: [CLOUDSTACK-10307] Remove unused things 
from HostDaoImpl
URL: https://github.com/apache/cloudstack/pull/2438#issuecomment-368614844
 
 
   Trillian test result (tid-2283)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 24033 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2438-t2283-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_internal_lb.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_hostha_enable_ha_when_host_in_maintenance | `Error` | 5.01 | 
test_hostha_kvm.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove unused things from HostDaoImpl
> -
>
> Key: CLOUDSTACK-10307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> Remove unnecessary annotation of HostDaoImpl. While removing this annotation 
> I noticed that one of the methods were not necessary. While removing it, I 
> found some code in CloudZonesStartupProcessor that was also not used, and 
> removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

smeetsr commented on issue #2460: CLOUDSTACK-10298: fix for recreation of an 
earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368583882
 
 
   Thank you @borisstoyanov 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

blueorangutan commented on issue #2460: CLOUDSTACK-10298: fix for recreation of 
an earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368578743
 
 
   Trillian test result (tid-2282)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 20924 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2460-t2282-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_01_redundant_vpc_site2site_vpn | `Failure` | 197.90 | test_vpc_vpn.py
   test_01_vpc_site2site_vpn_multiple_options | `Failure` | 264.16 | 
test_vpc_vpn.py
   test_01_vpc_site2site_vpn | `Failure` | 114.71 | test_vpc_vpn.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) 

[jira] [Commented] (CLOUDSTACK-10274) L2 network refused to be designed on VXLAN physical network

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10274:
-

NuxRo commented on issue #2448: CLOUDSTACK-10274: L2 network refused to be 
designed on VXLAN physical network
URL: https://github.com/apache/cloudstack/pull/2448#issuecomment-368576767
 
 
   Sorry to be a pain, but is there a patch that addresses this yet? I want to 
showcase the L2+VXLAN feature, but the 4096 limit will make it look bad.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> L2 network refused to be designed on VXLAN physical network 
> 
>
> Key: CLOUDSTACK-10274
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10274
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.1
>
>
> Issue reported by [~nuxro] while trying to add an L2 network on a VXLAN 
> physical network:
> 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical 
> network id=201 based on requested tags mellanoxvxlan
> 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical 
> network id=201 based on requested tags mellanoxvxlan
> 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network, the physical isolation type is not BCF_SEGMENT
> 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not 
> configured to be active
> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design this network
> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to 
> design network using network offering 19 on physical network 201
> 2018-02-06 11:20:27,770 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Releasing lock 
> for Acct[6af2875b-04fc-11e8-923e-002590474525-admin]
> 2018-02-06 11:20:27,789 DEBUG [c.c.u.d.T.Transaction] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Rolling back 
> the transaction: Time = 38 Name =  qtp788117692-390; called by 
> -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-NetworkOrchestrator.createGuestNetwork:2315-NetworkServiceImpl$4.doInTransaction:1383-NetworkServiceImpl$4.doInTransaction:1331-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1331-NetworkServiceImpl.createGuestNetwork:1294-NativeMethodAccessorImpl.invoke0:-2
> 2018-02-06 11:20:27,798 ERROR [c.c.a.ApiServer] 
> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) unhandled 
> exception executing api command: [Ljava.lang.String;@43b9df02
> com.cloud.utils.exception.CloudRuntimeException: Unable to convert network 
> offering with specified id to network profile
>     at 
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:726)
>     at 
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2364)
>     at 
> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2315)
>     at 
> com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50)
>     at 

[jira] [Commented] (CLOUDSTACK-10305) Rare race condition in KVM migration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-10305:
--

Commit 703054964a9bae27a563412c35166bae515d10e3 in cloudstack's branch 
refs/heads/master from [~nicolas.vazquez]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=7030549 ]

CLOUDSTACK-10305: Rare race condition in KVM migration (#2466)

There is a race condition in the monitoring of the migration process on KVM. If 
the monitor wakes up in the tight window after the migration succeeds, but 
before the migration thread terminates, the monitor will get a LibvirtException 
“Domain not found: no domain with matching uuid” when checking on the migration 
status. This in turn causes CloudStack to sync the VM state to stop, in which 
it issues a defensive StopCommand to ensure it is correctly synced.

Fix: Prevent LibvirtException: "Domain not found" caused by the call to 
dm.getInfo()

> Rare race condition in KVM migration
> 
>
> Key: CLOUDSTACK-10305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10305
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.0
>
>
> There is a race condition in the monitoring of the migration process on KVM. 
> If the monitor wakes up in the tight window after the migration succeeds, but 
> before the migration thread terminates, the monitor will get a 
> LibvirtException “Domain not found: no domain with matching uuid” when 
> checking on the migration status. This in turn causes CloudStack to sync the 
> VM state to stop, in which it issues a defensive StopCommand to ensure it is 
> correctly synced.
> This is issue is reported under these conditions:
>  * VM migration has physically finished
>  * Migration thread executor is still not marked as terminated
> From the migration monitoring process, as VM has been migrated, that domain 
> cannot be found (we should get the destination domain from the migration 
> thread later) and the LibvirtException is thrown: {{LibvirtException “Domain 
> not found: no domain with matching uuid”}}.
> So basically the idea is just logging the issue but not suspending the VM as 
> the migration has already been performed, but the migration thread is not 
> marked as finished. Once the migrarion thread is marked as finished, the 
> migration monitoring process (while loop) ends and the migration command 
> wrapper would continue its execution.
> Regarding your last question, we won't need to suspend the VM in this case as 
> the migration has already been performed. VM suspension will take place 
> whenever the migration is in progress and those conditions are met



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10305) Rare race condition in KVM migration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CLOUDSTACK-10305:
--

Commit 703054964a9bae27a563412c35166bae515d10e3 in cloudstack's branch 
refs/heads/4.11 from [~nicolas.vazquez]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=7030549 ]

CLOUDSTACK-10305: Rare race condition in KVM migration (#2466)

There is a race condition in the monitoring of the migration process on KVM. If 
the monitor wakes up in the tight window after the migration succeeds, but 
before the migration thread terminates, the monitor will get a LibvirtException 
“Domain not found: no domain with matching uuid” when checking on the migration 
status. This in turn causes CloudStack to sync the VM state to stop, in which 
it issues a defensive StopCommand to ensure it is correctly synced.

Fix: Prevent LibvirtException: "Domain not found" caused by the call to 
dm.getInfo()

> Rare race condition in KVM migration
> 
>
> Key: CLOUDSTACK-10305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10305
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.0
>
>
> There is a race condition in the monitoring of the migration process on KVM. 
> If the monitor wakes up in the tight window after the migration succeeds, but 
> before the migration thread terminates, the monitor will get a 
> LibvirtException “Domain not found: no domain with matching uuid” when 
> checking on the migration status. This in turn causes CloudStack to sync the 
> VM state to stop, in which it issues a defensive StopCommand to ensure it is 
> correctly synced.
> This is issue is reported under these conditions:
>  * VM migration has physically finished
>  * Migration thread executor is still not marked as terminated
> From the migration monitoring process, as VM has been migrated, that domain 
> cannot be found (we should get the destination domain from the migration 
> thread later) and the LibvirtException is thrown: {{LibvirtException “Domain 
> not found: no domain with matching uuid”}}.
> So basically the idea is just logging the issue but not suspending the VM as 
> the migration has already been performed, but the migration thread is not 
> marked as finished. Once the migrarion thread is marked as finished, the 
> migration monitoring process (while loop) ends and the migration command 
> wrapper would continue its execution.
> Regarding your last question, we won't need to suspend the VM in this case as 
> the migration has already been performed. VM suspension will take place 
> whenever the migration is in progress and those conditions are met



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10305) Rare race condition in KVM migration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10305:
-

rhtyd closed pull request #2466: CLOUDSTACK-10305: Rare race condition in KVM 
migration
URL: https://github.com/apache/cloudstack/pull/2466
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/wrapper/LibvirtMigrateCommandWrapper.java
 
b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/wrapper/LibvirtMigrateCommandWrapper.java
index 30f0e20ddd9..ad32759a517 100644
--- 
a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/wrapper/LibvirtMigrateCommandWrapper.java
+++ 
b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/wrapper/LibvirtMigrateCommandWrapper.java
@@ -172,13 +172,21 @@ Use VIR_DOMAIN_XML_SECURE (value = 1) prior to v1.0.0.
 
 // pause vm if we meet the vm.migrate.pauseafter threshold and 
not already paused
 final int migratePauseAfter = 
libvirtComputingResource.getMigratePauseAfter();
-if (migratePauseAfter > 0 && sleeptime > migratePauseAfter && 
dm.getInfo().state == DomainState.VIR_DOMAIN_RUNNING ) {
-s_logger.info("Pausing VM " + vmName + " due to property 
vm.migrate.pauseafter setting to " + migratePauseAfter+ "ms to complete 
migration");
+if (migratePauseAfter > 0 && sleeptime > migratePauseAfter) {
+DomainState state = null;
 try {
-dm.suspend();
+state = dm.getInfo().state;
 } catch (final LibvirtException e) {
-// pause could be racy if it attempts to pause right 
when vm is finished, simply warn
-s_logger.info("Failed to pause vm " + vmName + " : " + 
e.getMessage());
+s_logger.info("Couldn't get VM domain state after " + 
sleeptime + "ms: " + e.getMessage());
+}
+if (state != null && state == 
DomainState.VIR_DOMAIN_RUNNING) {
+try {
+s_logger.info("Pausing VM " + vmName + " due to 
property vm.migrate.pauseafter setting to " + migratePauseAfter + "ms to 
complete migration");
+dm.suspend();
+} catch (final LibvirtException e) {
+// pause could be racy if it attempts to pause 
right when vm is finished, simply warn
+s_logger.info("Failed to pause vm " + vmName + " : 
" + e.getMessage());
+}
 }
 }
 }


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rare race condition in KVM migration
> 
>
> Key: CLOUDSTACK-10305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10305
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.0
>
>
> There is a race condition in the monitoring of the migration process on KVM. 
> If the monitor wakes up in the tight window after the migration succeeds, but 
> before the migration thread terminates, the monitor will get a 
> LibvirtException “Domain not found: no domain with matching uuid” when 
> checking on the migration status. This in turn causes CloudStack to sync the 
> VM state to stop, in which it issues a defensive StopCommand to ensure it is 
> correctly synced.
> This is issue is reported under these conditions:
>  * VM migration has physically finished
>  * Migration thread executor is still not marked as terminated
> From the migration monitoring process, as VM has been migrated, that domain 
> cannot be found (we should get the destination domain from the migration 
> thread later) and the LibvirtException is thrown: {{LibvirtException “Domain 
> not found: no domain with matching uuid”}}.
> So basically the idea is just logging the issue but not suspending the VM as 
> the migration has already been performed, but the migration thread is not 
> marked as finished. Once the migrarion thread is marked 

[jira] [Commented] (CLOUDSTACK-10305) Rare race condition in KVM migration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10305:
-

nvazquez commented on issue #2466: CLOUDSTACK-10305: Rare race condition in KVM 
migration
URL: https://github.com/apache/cloudstack/pull/2466#issuecomment-368509179
 
 
   Thanks @borisstoyanov! @rhtyd can we merge this one?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rare race condition in KVM migration
> 
>
> Key: CLOUDSTACK-10305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10305
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.0
>
>
> There is a race condition in the monitoring of the migration process on KVM. 
> If the monitor wakes up in the tight window after the migration succeeds, but 
> before the migration thread terminates, the monitor will get a 
> LibvirtException “Domain not found: no domain with matching uuid” when 
> checking on the migration status. This in turn causes CloudStack to sync the 
> VM state to stop, in which it issues a defensive StopCommand to ensure it is 
> correctly synced.
> This is issue is reported under these conditions:
>  * VM migration has physically finished
>  * Migration thread executor is still not marked as terminated
> From the migration monitoring process, as VM has been migrated, that domain 
> cannot be found (we should get the destination domain from the migration 
> thread later) and the LibvirtException is thrown: {{LibvirtException “Domain 
> not found: no domain with matching uuid”}}.
> So basically the idea is just logging the issue but not suspending the VM as 
> the migration has already been performed, but the migration thread is not 
> marked as finished. Once the migrarion thread is marked as finished, the 
> migration monitoring process (while loop) ends and the migration command 
> wrapper would continue its execution.
> Regarding your last question, we won't need to suspend the VM in this case as 
> the migration has already been performed. VM suspension will take place 
> whenever the migration is in progress and those conditions are met



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10307:
-

blueorangutan commented on issue #2438: [CLOUDSTACK-10307] Remove unused things 
from HostDaoImpl
URL: https://github.com/apache/cloudstack/pull/2438#issuecomment-368478260
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove unused things from HostDaoImpl
> -
>
> Key: CLOUDSTACK-10307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> Remove unnecessary annotation of HostDaoImpl. While removing this annotation 
> I noticed that one of the methods were not necessary. While removing it, I 
> found some code in CloudZonesStartupProcessor that was also not used, and 
> removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10307:
-

borisstoyanov commented on issue #2438: [CLOUDSTACK-10307] Remove unused things 
from HostDaoImpl
URL: https://github.com/apache/cloudstack/pull/2438#issuecomment-368478209
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove unused things from HostDaoImpl
> -
>
> Key: CLOUDSTACK-10307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> Remove unnecessary annotation of HostDaoImpl. While removing this annotation 
> I noticed that one of the methods were not necessary. While removing it, I 
> found some code in CloudZonesStartupProcessor that was also not used, and 
> removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

borisstoyanov commented on issue #2460: CLOUDSTACK-10298: fix for recreation of 
an earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368465191
 
 
   @blueorangutan test


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

blueorangutan commented on issue #2460: CLOUDSTACK-10298: fix for recreation of 
an earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368465314
 
 
   @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG 

[jira] [Commented] (CLOUDSTACK-10299) Network listing return error in project mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10299:
-

resmo commented on issue #2464: [4.11] CLOUDSTACK-10299: UI: fix error in 
network listing in project mode
URL: https://github.com/apache/cloudstack/pull/2464#issuecomment-368464113
 
 
   ready for review


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Network listing return error in project mode
> 
>
> Key: CLOUDSTACK-10299
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10299
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.11.0.0
>Reporter: René Moser
>Priority: Minor
> Attachments: Selection_142.png
>
>
> {{Clicking the network button in a project returns the following error:}}
>  
> {{{"listremoteaccessvpnsresponse":{"uuidList":[],"errorcode":431,"cserrorcode":4350,"errortext":"Account}}{{
>  and projectId can't be specified together"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10306:
-

blueorangutan commented on issue #2467: CLOUDSTACK-10306: Upgrade to VMware 6.5 
vim jar dependency
URL: https://github.com/apache/cloudstack/pull/2467#issuecomment-368463662
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-65) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10306:
-

rhtyd commented on issue #2467: CLOUDSTACK-10306: Upgrade to VMware 6.5 vim jar 
dependency
URL: https://github.com/apache/cloudstack/pull/2467#issuecomment-368463401
 
 
   @blueorangutan test centos7 vmware-65


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10283) Use sudo to execute keystore setup/import for kvm agents, and fail on keystore setup failures

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10283:
-

rhtyd commented on issue #2454: CLOUDSTACK-10283: Sudo to setup agent keystore, 
fail on host add failure
URL: https://github.com/apache/cloudstack/pull/2454#issuecomment-368460512
 
 
   @rafaelweingartner feel free to rekick the discussion and start a vote. I've 
shared my preference with you which is based on two things - (a) allows 
git-users like myself who prefers to keep track of changes using command-line, 
(b) for maintainers who would want to backport a feature/fix which is easier if 
every fix/pr is a single commit than bunch of them. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Use sudo to execute keystore setup/import for kvm agents, and fail on 
> keystore setup failures
> -
>
> Key: CLOUDSTACK-10283
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10283
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> Addition of a KVM host creates keystore on the KVM host's 
> /etc/cloudstack/agent path. The current scripts and codebase assumes that it 
> will be the root user which is why the script don't call keytool with 'sudo'. 
> To allow addition of host using a sudo-enabled/admin user, make suitable 
> changes to the script, and also fail the addHost execution if keystore 
> scripts fail (say due to permission issues etc).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10299) Network listing return error in project mode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10299:
-

resmo commented on issue #2464: [4.11] CLOUDSTACK-10299: UI: fix error in 
network listing in project mode
URL: https://github.com/apache/cloudstack/pull/2464#issuecomment-368459084
 
 
   Before
   
   
![selection_149](https://user-images.githubusercontent.com/23809/3001-7a44ebee-1ae9-11e8-868f-c3b697ad54f7.png)
   
   After
   
   
![selection_151](https://user-images.githubusercontent.com/23809/3027-8c1a956c-1ae9-11e8-9619-b4fd31d202d9.png)
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Network listing return error in project mode
> 
>
> Key: CLOUDSTACK-10299
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10299
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.11.0.0
>Reporter: René Moser
>Priority: Minor
> Attachments: Selection_142.png
>
>
> {{Clicking the network button in a project returns the following error:}}
>  
> {{{"listremoteaccessvpnsresponse":{"uuidList":[],"errorcode":431,"cserrorcode":4350,"errortext":"Account}}{{
>  and projectId can't be specified together"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[JIRA]

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

Rafael Weingärtner updated CLOUDSTACK-10307:

Status: Reviewable  (was: In Progress)

> Remove unused things from HostDaoImpl
> -
>
> Key: CLOUDSTACK-10307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> Remove unnecessary annotation of HostDaoImpl. While removing this annotation 
> I noticed that one of the methods were not necessary. While removing it, I 
> found some code in CloudZonesStartupProcessor that was also not used, and 
> removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10307:
-

rafaelweingartner commented on issue #2438: [CLOUDSTACK-10307] Remove unused 
things from HostDaoImpl
URL: https://github.com/apache/cloudstack/pull/2438#issuecomment-368455995
 
 
   @borisstoyanov done.
   Thanks for the review here.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove unused things from HostDaoImpl
> -
>
> Key: CLOUDSTACK-10307
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Minor
>
> Remove unnecessary annotation of HostDaoImpl. While removing this annotation 
> I noticed that one of the methods were not necessary. While removing it, I 
> found some code in CloudZonesStartupProcessor that was also not used, and 
> removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CLOUDSTACK-10307) Remove unused things from HostDaoImpl

[JIRA]

Rafael Weingärtner created CLOUDSTACK-10307:
---

 Summary: Remove unused things from HostDaoImpl
 Key: CLOUDSTACK-10307
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rafael Weingärtner
Assignee: Rafael Weingärtner


Remove unnecessary annotation of HostDaoImpl. While removing this annotation I 
noticed that one of the methods were not necessary. While removing it, I found 
some code in CloudZonesStartupProcessor that was also not used, and removed it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10283) Use sudo to execute keystore setup/import for kvm agents, and fail on keystore setup failures

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10283:
-

rafaelweingartner commented on issue #2454: CLOUDSTACK-10283: Sudo to setup 
agent keystore, fail on host add failure
URL: https://github.com/apache/cloudstack/pull/2454#issuecomment-368455248
 
 
   I am sorry @rhtyd, but I find using merge commits when merging PRs a good 
idea. We do not have a protocol for merges yet (use or not use the merge 
commit). There was a thread a while ago discussing this topic in [1]. Some 
people preferred maintaining the merge commits when merging a PR (myself 
included). However, the thread died after a while, I believe the author (Daan) 
was busy with something else to finalize the discussion and create something 
formal.
   
   [1] 
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201801.mbox/%3CCAGQtxva9xnipUXvc56wA4NT5fuwLXzR3cpD%3DFf1mO%3DxZYoKQ7w%40mail.gmail.com%3E
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Use sudo to execute keystore setup/import for kvm agents, and fail on 
> keystore setup failures
> -
>
> Key: CLOUDSTACK-10283
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10283
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> Addition of a KVM host creates keystore on the KVM host's 
> /etc/cloudstack/agent path. The current scripts and codebase assumes that it 
> will be the root user which is why the script don't call keytool with 'sudo'. 
> To allow addition of host using a sudo-enabled/admin user, make suitable 
> changes to the script, and also fail the addHost execution if keystore 
> scripts fail (say due to permission issues etc).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (CLOUDSTACK-10283) Use sudo to execute keystore setup/import for kvm agents, and fail on keystore setup failures

[Rohit Yadav (JIRA)]

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

Rohit Yadav closed CLOUDSTACK-10283.


> Use sudo to execute keystore setup/import for kvm agents, and fail on 
> keystore setup failures
> -
>
> Key: CLOUDSTACK-10283
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10283
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> Addition of a KVM host creates keystore on the KVM host's 
> /etc/cloudstack/agent path. The current scripts and codebase assumes that it 
> will be the root user which is why the script don't call keytool with 'sudo'. 
> To allow addition of host using a sudo-enabled/admin user, make suitable 
> changes to the script, and also fail the addHost execution if keystore 
> scripts fail (say due to permission issues etc).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (CLOUDSTACK-10283) Use sudo to execute keystore setup/import for kvm agents, and fail on keystore setup failures

[Rohit Yadav (JIRA)]

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

Rohit Yadav resolved CLOUDSTACK-10283.
--
Resolution: Fixed

> Use sudo to execute keystore setup/import for kvm agents, and fail on 
> keystore setup failures
> -
>
> Key: CLOUDSTACK-10283
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10283
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> Addition of a KVM host creates keystore on the KVM host's 
> /etc/cloudstack/agent path. The current scripts and codebase assumes that it 
> will be the root user which is why the script don't call keytool with 'sudo'. 
> To allow addition of host using a sudo-enabled/admin user, make suitable 
> changes to the script, and also fail the addHost execution if keystore 
> scripts fail (say due to permission issues etc).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

blueorangutan commented on issue #2460: CLOUDSTACK-10298: fix for recreation of 
an earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368452590
 
 
   Packaging result: ✔centos6 ✔centos7 ✖debian. JID-1734


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 

[jira] [Commented] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10306:
-

blueorangutan commented on issue #2467: CLOUDSTACK-10306: Upgrade to VMware 6.5 
vim jar dependency
URL: https://github.com/apache/cloudstack/pull/2467#issuecomment-368447071
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1733


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

blueorangutan commented on issue #2460: CLOUDSTACK-10298: fix for recreation of 
an earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368442830
 
 
   @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG 

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

borisstoyanov commented on issue #2460: CLOUDSTACK-10298: fix for recreation of 
an earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368442539
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) 

[jira] [Commented] (CLOUDSTACK-10298) Recreation of an earlier deleted Nuage managed isolated or vpc tier network fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10298:
-

smeetsr commented on issue #2460: CLOUDSTACK-10298: fix for recreation of an 
earlier deleted Nuage managed network
URL: https://github.com/apache/cloudstack/pull/2460#issuecomment-368440358
 
 
   @borisstoyanov Can you please trigger trillian test for this PR? I guess 
there was a typo in earlier comment? Thanks.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Recreation of an earlier deleted Nuage managed isolated or vpc tier network 
> fails
> -
>
> Key: CLOUDSTACK-10298
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Sigert Goeminne
>Priority: Major
>
> Scenario to reproduce for isolated network: (same applies for vpc tier 
> network)
> Create L3Domain/Zone/Subnet/DefaultACLs in VSD and create a non-persistent 
> NetworkOffering in ACS, then createNetwork by specifying externalID attribute 
> in the request, which refers to the Subnet ID in VSD.
> Then verify VSD objects and verify networking by deploying 2 VM's in this 
> network, enable static nat to one VM and ping to the other VM.
> After that delete tall the VM's in this network and delete the network itself.
> Don't delete data in VSD.
> Recreate same network by specifying same externalID attribute in the request, 
> which refers to the Subnet ID in VSD.
> management-server.log shows following error
> 2018-02-07 00:15:27,464 DEBUG [c.c.a.ApiServlet] 
> (qtp66233253-20:ctx-a9727f69) (logid:13bd8add) ===START=== 10.30.39.11 - GET 
> acltype=Account=StjgrAiYEguhhZwogkx4SggkPhImhdxgSrDbfUZhLjL4As6bm4Xec8GC7WKFWuZXJmTAIl9zx_Qeh767T_yfpQ=f17d2601-984f-4cc6-ba78-4b89bdc87115=11ce9c88-0a46-11e8-bff2-faac09080700=Test+Network=10.0.0.1=b0fbe47b-173e-415b-b0e6-80fd17f75f1d=255.255.255.0=43897d72-6781-4e29-9a13-5ad9addbec01=json=test-a-TestNuageManagedSubnets-VL53W7=TestNet-10.0.0.1-NET_OFF-True-0KWFQ8=createNetwork=688UxfzAZdtoj%2BEFxHpwf6rrAoQ%3D
> 2018-02-07 00:15:27,468 DEBUG [c.c.a.ApiServer] (qtp66233253-20:ctx-a9727f69 
> ctx-3d2464e6) (logid:13bd8add) CIDRs from which account 
> 'Acct[555cb263-0a46-11e8-bff2-faac09080700-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-02-07 00:15:27,479 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Access granted to Acct[5ff94a35-075a-4023-bb2a-2186a6a00853-admin] to 
> Domain:1/ by AffinityGroupAccessChecker
> 2018-02-07 00:15:27,488 DEBUG [c.c.r.ResourceLimitManagerImpl] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Checking if amount of resources of Type = 'network' for Account Name = 
> test-a-TestNuageManagedSubnets-VL53W7 in Domain Id = 1 is exceeded: Account 
> Resource Limit = 20, Current Account Resource Amount = 0, Requested Resource 
> Amount = 1.
> 2018-02-07 00:15:27,506 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network, the physical isolation type is not 
> BCF_SEGMENT
> 2018-02-07 00:15:27,506 DEBUG [o.a.c.n.c.m.ContrailGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,507 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,508 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,509 DEBUG [c.c.n.g.OvsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,512 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) SSP 
> not configured to be active
> 2018-02-07 00:15:27,513 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] 
> (qtp66233253-20:ctx-a9727f69 ctx-3d2464e6 ctx-4b65e7ca) (logid:13bd8add) 
> Refusing to design this network
> 2018-02-07 00:15:27,515 DEBUG 

[jira] [Commented] (CLOUDSTACK-10283) Use sudo to execute keystore setup/import for kvm agents, and fail on keystore setup failures

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10283:
-

rhtyd commented on issue #2454: CLOUDSTACK-10283: Sudo to setup agent keystore, 
fail on host add failure
URL: https://github.com/apache/cloudstack/pull/2454#issuecomment-368437038
 
 
   @rafaelweingartner can you kindly squash merge in future, otherwise, we'll 
have commit+merge commits on the branches that make the git graph look weird 
and difficult to track changes.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Use sudo to execute keystore setup/import for kvm agents, and fail on 
> keystore setup failures
> -
>
> Key: CLOUDSTACK-10283
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10283
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Major
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> Addition of a KVM host creates keystore on the KVM host's 
> /etc/cloudstack/agent path. The current scripts and codebase assumes that it 
> will be the root user which is why the script don't call keytool with 'sudo'. 
> To allow addition of host using a sudo-enabled/admin user, make suitable 
> changes to the script, and also fail the addHost execution if keystore 
> scripts fail (say due to permission issues etc).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[Rohit Yadav (JIRA)]

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

Rohit Yadav updated CLOUDSTACK-10306:
-
Status: Reviewable  (was: In Progress)

> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10306:
-

blueorangutan commented on issue #2467: CLOUDSTACK-10306: Upgrade to VMware 6.5 
vim jar dependency
URL: https://github.com/apache/cloudstack/pull/2467#issuecomment-368436065
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10306:
-

rhtyd opened a new pull request #2467: CLOUDSTACK-10306: Upgrade to VMware 6.5 
vim jar dependency
URL: https://github.com/apache/cloudstack/pull/2467
 
 
   Upgrade to VMware 6.5 vim jar dependency.
   
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[Rohit Yadav (JIRA)]

Rohit Yadav created CLOUDSTACK-10306:


 Summary: Update vmware dependency vim jar to 6.5 version
 Key: CLOUDSTACK-10306
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rohit Yadav
Assignee: Rohit Yadav
 Fix For: 4.11.1.1, 4.12.0.0


Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (CLOUDSTACK-10306) Update vmware dependency vim jar to 6.5 version

[Rohit Yadav (JIRA)]

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

Rohit Yadav updated CLOUDSTACK-10306:
-
Priority: Minor  (was: Major)

> Update vmware dependency vim jar to 6.5 version
> ---
>
> Key: CLOUDSTACK-10306
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Minor
> Fix For: 4.11.1.1, 4.12.0.0
>
>
> Upgrade to vmware sdk 6.5's vim.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10305) Rare race condition in KVM migration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CLOUDSTACK-10305:
-

borisstoyanov commented on issue #2466: CLOUDSTACK-10305: Rare race condition 
in KVM migration
URL: https://github.com/apache/cloudstack/pull/2466#issuecomment-368423155
 
 
   Thanks for this fix @nvazquez, I've managed to test it out. On master 
(without the fix) I've set the vm.migrate.pauseafter to 1 and did a migration, 
the issue is reproduce every time you try to migrate and the VM is put to 
stopped state, when applying the fix and using the same settings I was able to 
migrate successfully the VM around and got nothing in the management. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rare race condition in KVM migration
> 
>
> Key: CLOUDSTACK-10305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10305
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Priority: Major
> Fix For: 4.11.1.0
>
>
> There is a race condition in the monitoring of the migration process on KVM. 
> If the monitor wakes up in the tight window after the migration succeeds, but 
> before the migration thread terminates, the monitor will get a 
> LibvirtException “Domain not found: no domain with matching uuid” when 
> checking on the migration status. This in turn causes CloudStack to sync the 
> VM state to stop, in which it issues a defensive StopCommand to ensure it is 
> correctly synced.
> This is issue is reported under these conditions:
>  * VM migration has physically finished
>  * Migration thread executor is still not marked as terminated
> From the migration monitoring process, as VM has been migrated, that domain 
> cannot be found (we should get the destination domain from the migration 
> thread later) and the LibvirtException is thrown: {{LibvirtException “Domain 
> not found: no domain with matching uuid”}}.
> So basically the idea is just logging the issue but not suspending the VM as 
> the migration has already been performed, but the migration thread is not 
> marked as finished. Once the migrarion thread is marked as finished, the 
> migration monitoring process (while loop) ends and the migration command 
> wrapper would continue its execution.
> Regarding your last question, we won't need to suspend the VM in this case as 
> the migration has already been performed. VM suspension will take place 
> whenever the migration is in progress and those conditions are met



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)