[jira] [Assigned] (CLOUDSTACK-10244) Online storage migration for KVM fails and corrupts disk

2018-01-19 Thread Mike Tutkowski (JIRA)

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

Mike Tutkowski reassigned CLOUDSTACK-10244:
---

Assignee: Mike Tutkowski

> Online storage migration for KVM fails and corrupts disk
> 
>
> Key: CLOUDSTACK-10244
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10244
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.11.0.0
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
>Priority: Blocker
> Fix For: 4.11.0.0
>
>
> This is an issue that was introduced in the code-review process of 
> https://github.com/apache/cloudstack/pull/2298.
> I plan to open a PR for 4.11 RC2 soon.



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


[jira] [Commented] (CLOUDSTACK-10244) Online storage migration for KVM fails and corrupts disk

2018-01-19 Thread Mike Tutkowski (JIRA)

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

Mike Tutkowski commented on CLOUDSTACK-10244:
-

This use case only applies to online storage migration from NFS or Ceph to 
managed storage, which is a new feature for 4.11.

> Online storage migration for KVM fails and corrupts disk
> 
>
> Key: CLOUDSTACK-10244
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10244
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.11.0.0
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
>Priority: Blocker
> Fix For: 4.11.0.0
>
>
> This is an issue that was introduced in the code-review process of 
> https://github.com/apache/cloudstack/pull/2298.
> I plan to open a PR for 4.11 RC2 soon.



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


[jira] [Updated] (CLOUDSTACK-10244) Online storage migration for KVM fails and corrupts disk

2018-01-19 Thread Mike Tutkowski (JIRA)

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

Mike Tutkowski updated CLOUDSTACK-10244:

Description: 
This is an issue that was introduced in the code-review process of 
https://github.com/apache/cloudstack/pull/2298.

I plan to open a PR for 4.11 RC2 soon.

  was:
This is an issue that was introduced in the code-review process of 
[https://github.com/apache/cloudstack/pull/2298|https://github.com/apache/cloudstack/pull/2298.].

I plan to open a PR for 4.11 RC2 soon.


> Online storage migration for KVM fails and corrupts disk
> 
>
> Key: CLOUDSTACK-10244
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10244
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.11.0.0
>Reporter: Mike Tutkowski
>Priority: Blocker
> Fix For: 4.11.0.0
>
>
> This is an issue that was introduced in the code-review process of 
> https://github.com/apache/cloudstack/pull/2298.
> I plan to open a PR for 4.11 RC2 soon.



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


[jira] [Updated] (CLOUDSTACK-10244) Online storage migration for KVM fails and corrupts disk

2018-01-19 Thread Mike Tutkowski (JIRA)

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

Mike Tutkowski updated CLOUDSTACK-10244:

Description: 
This is an issue that was introduced in the code-review process of 
[https://github.com/apache/cloudstack/pull/2298|https://github.com/apache/cloudstack/pull/2298.].

I plan to open a PR for 4.11 RC2 soon.

  was:
This is an issue that was introduced in the code-review process of 
[https://github.com/apache/cloudstack/pull/2298.]

I plan to open a PR for 4.11 RC2 soon.


> Online storage migration for KVM fails and corrupts disk
> 
>
> Key: CLOUDSTACK-10244
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10244
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM
>Affects Versions: 4.11.0.0
>Reporter: Mike Tutkowski
>Priority: Blocker
> Fix For: 4.11.0.0
>
>
> This is an issue that was introduced in the code-review process of 
> [https://github.com/apache/cloudstack/pull/2298|https://github.com/apache/cloudstack/pull/2298.].
> I plan to open a PR for 4.11 RC2 soon.



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


[jira] [Created] (CLOUDSTACK-10244) Online storage migration for KVM fails and corrupts disk

2018-01-19 Thread Mike Tutkowski (JIRA)
Mike Tutkowski created CLOUDSTACK-10244:
---

 Summary: Online storage migration for KVM fails and corrupts disk
 Key: CLOUDSTACK-10244
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10244
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: KVM
Affects Versions: 4.11.0.0
Reporter: Mike Tutkowski
 Fix For: 4.11.0.0


This is an issue that was introduced in the code-review process of 
[https://github.com/apache/cloudstack/pull/2298.]

I plan to open a PR for 4.11 RC2 soon.



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF subversion and git services (JIRA)

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

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

Commit 5eb09565b390e82072423e9d8b06b7af23884927 in cloudstack's branch 
refs/heads/master from [~dahn]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=5eb0956 ]

CLOUDSTACK-10117: Allow scoped setting to have nullable values (#2413)

Allows scope setting for domain_details to have nullable values.

> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF subversion and git services (JIRA)

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

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

Commit 5eb09565b390e82072423e9d8b06b7af23884927 in cloudstack's branch 
refs/heads/4.11 from [~dahn]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=5eb0956 ]

CLOUDSTACK-10117: Allow scoped setting to have nullable values (#2413)

Allows scope setting for domain_details to have nullable values.

> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10238:
-

blueorangutan commented on issue #2411: CLOUDSTACK-10238: Fix for metalink 
support on SSVM agents
URL: https://github.com/apache/cloudstack/pull/2411#issuecomment-359049950
 
 
   Trillian test result (tid-2173)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 31320 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2411-t2173-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py
   Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 64 look OK, 3 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_04_extract_template | `Failure` | 128.35 | test_templates.py
   ContextSuite context=TestISOUsage>:setup | `Error` | 0.00 | test_usage.py
   test_06_download_detached_volume | `Failure` | 136.58 | test_volumes.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


> Fix for metalink support on SSVM agents
> ---
>
> Key: CLOUDSTACK-10238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Fix for metalink support



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


[jira] [Commented] (CLOUDSTACK-10241) Duplicated file SRs being created in XenServer pools

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10241:
-

rafaelweingartner opened a new pull request #2414: [CLOUDSTACK-10241] 
Duplicated file SRs being created in XenServer pools
URL: https://github.com/apache/cloudstack/pull/2414
 
 
   Due to a race condition between multiple management servers, in some rare 
cases, CloudStack is creating multiple file SRs to the same secondary folder. 
This causes a problem when introducing the SR to the XenServer pools, as “there 
will be VDIs with duplicated UUIDs“. The VDIs are the same, but they are seen 
in different SRs, and therefore cause an error.
   
   The solution to avoid race conditions between management servers is to use a 
deterministic srUuid for the file SR to be created (we are leaving XenServer 
with the burden of managing race conditions). The UUID is based on the SR file 
path and is generated using  `UUID.nameUUIDFromBytes`. Therefore, if there is 
an SR with the generated UUID, this means that some other management server has 
just created it. An exception will occur and it will contain a message saying 
'Db_exn.Uniqueness_constraint_violation'. In these unlikely events, we catch 
the exception and use the method `retrieveAlreadyConfiguredSrWithoutException` 
to get the SR that has already been created for the given mount point.


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


> Duplicated file SRs being created in XenServer pools
> 
>
> Key: CLOUDSTACK-10241
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10241
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rafael Weingärtner
>Assignee: Rafael Weingärtner
>Priority: Major
>
> Due to a race condition between multiple management servers, in some rare 
> cases, CloudStack is creating multiple file SRs to the same secondary folder. 
> This causes a problem when introducing the SR to the XenServer pools, as 
> “there will be VDIs with duplicated UUIDs“. The VDIs are the same, but they 
> are seen in different SRs, and therefore cause an error.



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


[jira] [Commented] (CLOUDSTACK-10239) User LDAP authentication not working in UI (but works via API)

2018-01-19 Thread Jean-Francois Nadeau (JIRA)

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

Jean-Francois Nadeau commented on CLOUDSTACK-10239:
---

Confirmed this is a regression from 4.9.   I reinstalled controller and can use 
LDAP credentials from the UI

> User LDAP authentication not working in UI (but works via API)
> --
>
> Key: CLOUDSTACK-10239
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10239
> 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
> Environment: CentOS 7, KVM, MSAD
>Reporter: Jean-Francois Nadeau
>Priority: Major
>
> hi,
> I setup LDAP authentication with the microsoft AD ldap provider and get 
> different behaviors in the UI vs using the API (cs python cli)
> Through the UI,  I can see the list of our AD users using the "Add ldap 
> account" action but selecting a user and adding it returns there are no 
> username by that name:
> INFO  [c.c.a.ApiServer] (qtp510113906-20:ctx-e32d5ff4 ctx-c3c50b46) 
> (logid:89c8c538) No LDAP user exists with the username of 
>  
> Doing the same thing from though CLI works fine:
> $ cs ldapCreateAccount username=markp accounttype=1 account=admin
>  ...
> {
>  "account": "admin", 
>  "accountid": "0683fdb0-fbae-11e7-9574-96a9f76bb706", 
>  "accounttype": 1, 
>  "created": "2018-01-18T19:21:31+", 
>  "domain": "ROOT", 
>  "domainid": "d9bbe213-fbad-11e7-9574-96a9f76bb706", 
> "firstname": "Mark", 
>  "id": "5ed90ce8-5c54-4f72-8579-639947f5c368", 
>  "iscallerchilddomain": false, 
>  "isdefault": false, 
>  "lastname": "p", 
>  "roleid": "f8a368af-fbad-11e7-9574-96a9f76bb706", 
>  "rolename": "Root Admin", 
>  "roletype": "Admin", 
>  "state": "enabled", 
>  "username": "markp", 
>  "usersource": "ldap"
>  }
>  
> Also,  once this user is added,  he can not login in the UI using his LDAP 
> credentials with the same error in the ms logs.  Then,  if i generate keys 
> for that same admin user,  he can use the API without problems.
>  



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

blueorangutan commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for 
direct downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-359033399
 
 
   Trillian test result (tid-2172)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 30851 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2408-t2172-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 62 look OK, 5 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_04_extract_template | `Failure` | 128.28 | test_templates.py
   ContextSuite context=TestISOUsage>:setup | `Error` | 0.00 | test_usage.py
   test_06_download_detached_volume | `Failure` | 137.58 | test_volumes.py
   test_05_rvpc_multi_tiers | `Failure` | 310.07 | test_vpc_redundant.py
   test_05_rvpc_multi_tiers | `Error` | 332.97 | test_vpc_redundant.py
   test_hostha_enable_ha_when_host_in_maintenance | `Error` | 1.44 | 
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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

blueorangutan commented on issue #2413: CLOUDSTACK-10117 scoped setting have 
nullable values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-359029430
 
 
   Trillian test result (tid-2174)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 20493 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2413-t2174-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10242) Problem Using Ingress/Egress SG Rules over 4.11 rc Tests

2018-01-19 Thread Wido den Hollander (JIRA)

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

Wido den Hollander commented on CLOUDSTACK-10242:
-

I will look into this. We need to use ; as a delimiter, because : will not work 
with IPv6.

 

I'll try to draft a patch and PR as soon as possible.

> Problem Using Ingress/Egress SG Rules over 4.11 rc Tests
> 
>
> Key: CLOUDSTACK-10242
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10242
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server
>Affects Versions: 4.11.0.0
> Environment: KVM Host Ubuntu 16.04.3, Management Server Ubuntu 14.04.5
>Reporter: Özhan Rüzgar Karaman
>Assignee: Wido den Hollander
>Priority: Blocker
>
> We noticed that Cloudstack-9853 fix generates some problems on applying SG 
> rules on security_group.py script. We compare the commands which send to 
> script between 4.9.3 and 4.11 versions and we noticed that SG rule delimiter 
> and nicsecips values changed on 4.11 release its examples are below:
> 4.9.3
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> default_network_rules --vmname i-2-573-VM --vmid 573 --vmip 192.168.2.56 
> --vmmac 06:31:56:00:04:09 --vif vnet15 --brname brenp4s0f0-23 --nicsecips 0:
>  
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> add_network_rules --vmname i-2-573-VM --vmid 573 --vmip 192.168.2.56 --sig 
> d60255deb618b7be9f477eed10d65234 --seq 2 --vmmac 06:31:56:00:04:09 --vif 
> vnet15 --brname brenp4s0f0-23 --nicsecips 0: --rules 
> "I:icmp:-1:-1:0.0.0.0/0,NEXT;I:tcp:1:65535:0.0.0.0/0,NEXT;I:udp:1:65535:0.0.0.0/0,NEXT;E:icmp:-1:-1:0.0.0.0/0,NEXT;E:tcp:1:65535:0.0.0.0/0,NEXT;E:udp:1:65535:0.0.0.0/0,NEXT;"
>  
> 4.11.0
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> default_network_rules --vmname i-2-3-VM --vmid 3 --vmip 192.168.18.189 
> --vmmac 1e:00:50:00:00:bc --vif vnet10 --brname breth0-23 --nicsecips 0;
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> add_network_rules --vmname "i-2-3-VM" --vmid "3" --vmip "192.168.18.189" 
> --sig "9b1c4aa31c811204e1dae5310d7711b5" --seq "12" --vmmac 
> "1e:00:50:00:00:bc" --vif "vnet10" --brname "breth0-23" --nicsecips "0:" 
> --rules 
> "I:icmp;-1;-1;0.0.0.0/0,NEXT;I:tcp;1;65535;0.0.0.0/0,NEXT;I:udp;1;65535;0.0.0.0/0,NEXT;E:icmp;-1;-1;0.0.0.0/0,NEXT;E:tcp;1;65535;0.0.0.0/0,NEXT;E:udp;1;65535;0.0.0.0/0,NEXT;"
>  
> This change creates problem on parse_network_rules function in 
> security_group.py. We made this test only on ipv4 enabled environment. So 
> this need to be fixed to make SG operational for 4.11 release.
>  
>  



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


[jira] [Assigned] (CLOUDSTACK-10242) Problem Using Ingress/Egress SG Rules over 4.11 rc Tests

2018-01-19 Thread Wido den Hollander (JIRA)

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

Wido den Hollander reassigned CLOUDSTACK-10242:
---

Assignee: Wido den Hollander

> Problem Using Ingress/Egress SG Rules over 4.11 rc Tests
> 
>
> Key: CLOUDSTACK-10242
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10242
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Management Server
>Affects Versions: 4.11.0.0
> Environment: KVM Host Ubuntu 16.04.3, Management Server Ubuntu 14.04.5
>Reporter: Özhan Rüzgar Karaman
>Assignee: Wido den Hollander
>Priority: Blocker
>
> We noticed that Cloudstack-9853 fix generates some problems on applying SG 
> rules on security_group.py script. We compare the commands which send to 
> script between 4.9.3 and 4.11 versions and we noticed that SG rule delimiter 
> and nicsecips values changed on 4.11 release its examples are below:
> 4.9.3
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> default_network_rules --vmname i-2-573-VM --vmid 573 --vmip 192.168.2.56 
> --vmmac 06:31:56:00:04:09 --vif vnet15 --brname brenp4s0f0-23 --nicsecips 0:
>  
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> add_network_rules --vmname i-2-573-VM --vmid 573 --vmip 192.168.2.56 --sig 
> d60255deb618b7be9f477eed10d65234 --seq 2 --vmmac 06:31:56:00:04:09 --vif 
> vnet15 --brname brenp4s0f0-23 --nicsecips 0: --rules 
> "I:icmp:-1:-1:0.0.0.0/0,NEXT;I:tcp:1:65535:0.0.0.0/0,NEXT;I:udp:1:65535:0.0.0.0/0,NEXT;E:icmp:-1:-1:0.0.0.0/0,NEXT;E:tcp:1:65535:0.0.0.0/0,NEXT;E:udp:1:65535:0.0.0.0/0,NEXT;"
>  
> 4.11.0
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> default_network_rules --vmname i-2-3-VM --vmid 3 --vmip 192.168.18.189 
> --vmmac 1e:00:50:00:00:bc --vif vnet10 --brname breth0-23 --nicsecips 0;
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py 
> add_network_rules --vmname "i-2-3-VM" --vmid "3" --vmip "192.168.18.189" 
> --sig "9b1c4aa31c811204e1dae5310d7711b5" --seq "12" --vmmac 
> "1e:00:50:00:00:bc" --vif "vnet10" --brname "breth0-23" --nicsecips "0:" 
> --rules 
> "I:icmp;-1;-1;0.0.0.0/0,NEXT;I:tcp;1;65535;0.0.0.0/0,NEXT;I:udp;1;65535;0.0.0.0/0,NEXT;E:icmp;-1;-1;0.0.0.0/0,NEXT;E:tcp;1;65535;0.0.0.0/0,NEXT;E:udp;1;65535;0.0.0.0/0,NEXT;"
>  
> This change creates problem on parse_network_rules function in 
> security_group.py. We made this test only on ipv4 enabled environment. So 
> this need to be fixed to make SG operational for 4.11 release.
>  
>  



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


[jira] [Created] (CLOUDSTACK-10243) Updating metadata might hang on VR on "ip rule show"

2018-01-19 Thread Wido den Hollander (JIRA)
Wido den Hollander created CLOUDSTACK-10243:
---

 Summary: Updating metadata might hang on VR on "ip rule show"
 Key: CLOUDSTACK-10243
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10243
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Virtual Router
Affects Versions: 4.10.0.0, 4.11.0.0
 Environment: CloudStack 4.10 - Basic Networking
Reporter: Wido den Hollander
Assignee: Wido den Hollander
 Fix For: Future


On a CloudStack 4.10 setup running with Basic Networking we noticed VMs being 
in the "Starting" state.

After investigating in the VR we show the "ip rule show" command run for ever 
and never end. This causes Python scripts to wait and thus never start the 
Instance.

This seems to be a issue in CsHelper.py where it uses p.wait() which might 
block in certain situations.



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


[jira] [Commented] (CLOUDSTACK-9677) Swift Storage Policy support for Secondary Storage

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-9677:


rafaelweingartner commented on a change in pull request #2412: CLOUDSTACK-9677: 
Adding storage policy support for swift as secondary…
URL: https://github.com/apache/cloudstack/pull/2412#discussion_r162616231
 
 

 ##
 File path: 
plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/XenServerStorageProcessor.java
 ##
 @@ -914,20 +917,45 @@ public Answer copyVolumeFromPrimaryToSecondary(final 
CopyCommand cmd) {
 
 private boolean swiftUpload(final Connection conn, final SwiftTO swift, 
final String container, final String ldir, final String lfilename, final 
Boolean isISCSI,
 final int wait) {
-String result = null;
+
+List params = getSwiftParams(swift, container, ldir, 
lfilename, isISCSI);
+
 try {
-result =
-hypervisorResource.callHostPluginAsync(conn, 
"swiftxenserver", "swift", wait, "op", "upload", "url", swift.getUrl(), 
"account", swift.getAccount(), "username",
-swift.getUserName(), "key", swift.getKey(), 
"container", container, "ldir", ldir, "lfilename", lfilename, "isISCSI", 
isISCSI.toString());
-if (result != null && result.equals("true")) {
-return true;
-}
+String result = hypervisorResource.callHostPluginAsync(conn, 
"swiftxenserver", "swift", wait, params.toArray(new String[params.size()]));
+return "true".equals(result);
 } catch (final Exception e) {
 s_logger.warn("swift upload failed due to " + e.toString(), e);
 }
 return false;
 }
 
+private List getSwiftParams(SwiftTO swift, String container, 
String ldir, String lfilename, Boolean isISCSI) {
 
 Review comment:
   This method could really benefit from unit 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


> Swift Storage Policy support for Secondary Storage
> --
>
> Key: CLOUDSTACK-9677
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9677
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Patrick D.
>Assignee: Patrick D.
>Priority: Major
>




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


[jira] [Commented] (CLOUDSTACK-9677) Swift Storage Policy support for Secondary Storage

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-9677:


rafaelweingartner commented on a change in pull request #2412: CLOUDSTACK-9677: 
Adding storage policy support for swift as secondary…
URL: https://github.com/apache/cloudstack/pull/2412#discussion_r162615113
 
 

 ##
 File path: 
plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/XenServerStorageProcessor.java
 ##
 @@ -914,20 +917,45 @@ public Answer copyVolumeFromPrimaryToSecondary(final 
CopyCommand cmd) {
 
 private boolean swiftUpload(final Connection conn, final SwiftTO swift, 
final String container, final String ldir, final String lfilename, final 
Boolean isISCSI,
 final int wait) {
-String result = null;
+
+List params = getSwiftParams(swift, container, ldir, 
lfilename, isISCSI);
+
 try {
-result =
-hypervisorResource.callHostPluginAsync(conn, 
"swiftxenserver", "swift", wait, "op", "upload", "url", swift.getUrl(), 
"account", swift.getAccount(), "username",
-swift.getUserName(), "key", swift.getKey(), 
"container", container, "ldir", ldir, "lfilename", lfilename, "isISCSI", 
isISCSI.toString());
-if (result != null && result.equals("true")) {
-return true;
-}
+String result = hypervisorResource.callHostPluginAsync(conn, 
"swiftxenserver", "swift", wait, params.toArray(new String[params.size()]));
+return "true".equals(result);
 
 Review comment:
   what about using `org.apache.commons.lang3.BooleanUtils.toBoolean(String)` 
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


> Swift Storage Policy support for Secondary Storage
> --
>
> Key: CLOUDSTACK-9677
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9677
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Patrick D.
>Assignee: Patrick D.
>Priority: Major
>




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


[jira] [Created] (CLOUDSTACK-10242) Problem Using Ingress/Egress SG Rules over 4.11 rc Tests

2018-01-19 Thread JIRA
Özhan Rüzgar Karaman created CLOUDSTACK-10242:
-

 Summary: Problem Using Ingress/Egress SG Rules over 4.11 rc Tests
 Key: CLOUDSTACK-10242
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10242
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: KVM, Management Server
Affects Versions: 4.11.0.0
 Environment: KVM Host Ubuntu 16.04.3, Management Server Ubuntu 14.04.5
Reporter: Özhan Rüzgar Karaman


We noticed that Cloudstack-9853 fix generates some problems on applying SG 
rules on security_group.py script. We compare the commands which send to script 
between 4.9.3 and 4.11 versions and we noticed that SG rule delimiter and 
nicsecips values changed on 4.11 release its examples are below:

4.9.3

/usr/share/cloudstack-common/scripts/vm/network/security_group.py 
default_network_rules --vmname i-2-573-VM --vmid 573 --vmip 192.168.2.56 
--vmmac 06:31:56:00:04:09 --vif vnet15 --brname brenp4s0f0-23 --nicsecips 0:

 

/usr/share/cloudstack-common/scripts/vm/network/security_group.py 
add_network_rules --vmname i-2-573-VM --vmid 573 --vmip 192.168.2.56 --sig 
d60255deb618b7be9f477eed10d65234 --seq 2 --vmmac 06:31:56:00:04:09 --vif vnet15 
--brname brenp4s0f0-23 --nicsecips 0: --rules 
"I:icmp:-1:-1:0.0.0.0/0,NEXT;I:tcp:1:65535:0.0.0.0/0,NEXT;I:udp:1:65535:0.0.0.0/0,NEXT;E:icmp:-1:-1:0.0.0.0/0,NEXT;E:tcp:1:65535:0.0.0.0/0,NEXT;E:udp:1:65535:0.0.0.0/0,NEXT;"

 

4.11.0

/usr/share/cloudstack-common/scripts/vm/network/security_group.py 
default_network_rules --vmname i-2-3-VM --vmid 3 --vmip 192.168.18.189 --vmmac 
1e:00:50:00:00:bc --vif vnet10 --brname breth0-23 --nicsecips 0;

/usr/share/cloudstack-common/scripts/vm/network/security_group.py 
add_network_rules --vmname "i-2-3-VM" --vmid "3" --vmip "192.168.18.189" --sig 
"9b1c4aa31c811204e1dae5310d7711b5" --seq "12" --vmmac "1e:00:50:00:00:bc" --vif 
"vnet10" --brname "breth0-23" --nicsecips "0:" --rules 
"I:icmp;-1;-1;0.0.0.0/0,NEXT;I:tcp;1;65535;0.0.0.0/0,NEXT;I:udp;1;65535;0.0.0.0/0,NEXT;E:icmp;-1;-1;0.0.0.0/0,NEXT;E:tcp;1;65535;0.0.0.0/0,NEXT;E:udp;1;65535;0.0.0.0/0,NEXT;"

 

This change creates problem on parse_network_rules function in 
security_group.py. We made this test only on ipv4 enabled environment. So this 
need to be fixed to make SG operational for 4.11 release.

 

 



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


[jira] [Created] (CLOUDSTACK-10241) Duplicated file SRs being created in XenServer pools

2018-01-19 Thread JIRA
Rafael Weingärtner created CLOUDSTACK-10241:
---

 Summary: Duplicated file SRs being created in XenServer pools
 Key: CLOUDSTACK-10241
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10241
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Rafael Weingärtner
Assignee: Rafael Weingärtner


Due to a race condition between multiple management servers, in some rare 
cases, CloudStack is creating multiple file SRs to the same secondary folder. 
This causes a problem when introducing the SR to the XenServer pools, as “there 
will be VDIs with duplicated UUIDs“. The VDIs are the same, but they are seen 
in different SRs, and therefore cause an error.



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

marcaurele commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358954824
 
 
   @rhtyd rebase done, conflict gone


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Created] (CLOUDSTACK-10240) ACS cannot migrate a volume from local to shared storage (for XenServer)

2018-01-19 Thread JIRA
Rafael Weingärtner created CLOUDSTACK-10240:
---

 Summary: ACS cannot migrate a volume from local to shared storage 
(for XenServer)
 Key: CLOUDSTACK-10240
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10240
 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


CloudStack is logically restricting the migration of local storages to shared 
storage and vice versa. This restriction is a logical one and can be removed 
for XenServer deployments. Therefore, we will enable migration of volumes 
between local-shared storages in XenServers independently of their service 
offering. This will work as an override mechanism to the disk offering used by 
volumes. If administrators want to migrate local volumes to a shared storage, 
they should be able to do so (the hypervisor already allows that). The same the 
other way around.



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

DaanHoogland commented on issue #2413: CLOUDSTACK-10117 scoped setting have 
nullable values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-358950494
 
 
   @rafaelweingartner it is a generic quality of settings that they are null 
able. I booboo'd here by making them non null. The code is really just part of 
the general functionality.
   
   @rhtyd I will remove 4.11.1 milestone as it would have to be a alter table 
statement if it needs to go in there.


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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358949582
 
 
   @rafaelweingartner I pretty sure it's different than what was actually asked 
:)
   I'll leave the squash merging to @marcaurele after xenserver test (kvm tests 
LGTM) are back later today (hopefully few hours) and he can fix a merge 
conflict in 
`plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java`


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358949582
 
 
   @rafaelweingartner I pretty sure it's different than what was actually asked 
:)
   I'll leave the squash merging to @marcaurele after xenserver test (kvm tests 
LGTM) are back later today (hopefully few hours) and he can fix a merge 
conflict in 
`plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
   Squash and merge `


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

blueorangutan commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358949299
 
 
   Trillian test result (tid-2171)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 17383 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2283-t2171-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py
   Smoke tests completed. 54 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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

rafaelweingartner commented on issue #2413: CLOUDSTACK-10117 scoped setting 
have nullable values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-358949234
 
 
   It seems to be something simple. However, I have no clues why you are 
changing a field in the database from not null to null able. I checked the Jira 
ticket, and it is a generic one regarding a feature that you were/are 
developing.
   
   It is always good to provide these details either in the Jira ticket you 
create for the PR, or in the PR description itself. I also checked the commit, 
but it does not provide information regarding the necessity for this change and 
the impacts it may cause.
   


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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

rafaelweingartner commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358948196
 
 
   I saw it. My question was actually "considering that the tests finished 
successfully", will this be merged today? Or maybe we have something else to do 
or check before proceeding to merge.


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

rhtyd commented on issue #2413: CLOUDSTACK-10117 scoped setting have nullable 
values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-358948134
 
 
   Yes @rafaelweingartner that's it.


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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358947759
 
 
   @rafaelweingartner I think you missed my comment, for changes like this we 
shouldn't be merging them without test results. We only have test result for 
vmware, awaiting results for xenserver and kvm. Due to testing of RC1, our 
Trillian+Jenkins pipelines are full. I checked, smoketests are running for kvm 
and xenserver now, the results should be available in next 4-6 hours.
   
   @marcaurele can you fix the conflict?


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

rhtyd commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358947759
 
 
   @rafaelweingartner I think you missed my comment, for changes like this we 
shouldn't be merging them without test results. We only have test result for 
vmware, awaiting results for xenserver and kvm.
   @marcaurele can you fix the conflict?


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

rafaelweingartner commented on issue #2413: CLOUDSTACK-10117 scoped setting 
have nullable values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-358947722
 
 
   Ah, now I got it.
   You say, add this now, so we do not need to create upgrade paths for the 
minor version 4.11.1.0
   Is that it?


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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10105) Follow maven standard for all modules

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10105:
-

rafaelweingartner commented on issue #2283: CLOUDSTACK-10105: Maven standard
URL: https://github.com/apache/cloudstack/pull/2283#issuecomment-358947492
 
 
   @marcaurele any plan to execute this merge?


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


> Follow maven standard for all modules
> -
>
> Key: CLOUDSTACK-10105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10105
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Marc-Aurèle Brothier
>Assignee: Marc-Aurèle Brothier
>Priority: Minor
>
> The goal is to remove the custom module layout used and follow maven standard 
> structures for all. This will remove one module. It's only a matter of moving 
> files around to their correct location.



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

rhtyd commented on issue #2413: CLOUDSTACK-10117 scoped setting have nullable 
values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-358947322
 
 
   @rafaelweingartner this will add complexity that's all, ideally, we should 
n't (or at least try not to) have db changes in minor/dot releases.


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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10117) LDAP mapping on domain level

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10117:
-

rafaelweingartner commented on issue #2413: CLOUDSTACK-10117 scoped setting 
have nullable values
URL: https://github.com/apache/cloudstack/pull/2413#issuecomment-358946949
 
 
   I did not understand why this change will avoid us having an upgrade path 
between 4.11 - 4.12.
   @DaanHoogland can you provide some extra details 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


> LDAP mapping on domain level
> 
>
> Key: CLOUDSTACK-10117
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>Priority: Major
>
> see FS: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Domain+level+LDAP+bindinings



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


[jira] [Commented] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10233:
-

rhtyd commented on issue #2410: CLOUDSTACK-10233: use namespace in Libvirt 
domain metadata.
URL: https://github.com/apache/cloudstack/pull/2410#issuecomment-358895845
 
 
   Test LGTM, merging based on test results and code reviews.
   
   This PR has been accepted towards 4.11.0.0, and should make into RC2 as it 
fixes a libvirt domain/vm xml spec issue and may cause issue when users are 
using nuage integration.


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


> When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in 
> metadata is missing
> ---
>
> Key: CLOUDSTACK-10233
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> 
> 
> 
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Commented] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-9749:


rhtyd commented on issue #2409: CLOUDSTACK-9749: Fix Password server running on 
internal LB VM
URL: https://github.com/apache/cloudstack/pull/2409#issuecomment-358895327
 
 
   No regressions seen, merging this based on that and code reviews. This PR 
has been accepted towards 4.11.0.0, and should make into RC2 as it fixes a 
borderline blocker issue causing password server to run on ilbm vm.


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


> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0, 4.11.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

nvazquez commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for 
direct downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358940350
 
 
   @rhtyd agree with @DaanHoogland, it is a fix only for new Direct Download 
functionality


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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

DaanHoogland commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for 
direct downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358922832
 
 
   @rhtyd I don't think it is a blocker. It is new functionality failing, but 
it is nice to include if it is fixed and we need another RC.


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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10238:
-

blueorangutan commented on issue #2411: CLOUDSTACK-10238: Fix for metalink 
support on SSVM agents
URL: https://github.com/apache/cloudstack/pull/2411#issuecomment-358916260
 
 
   @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


> Fix for metalink support on SSVM agents
> ---
>
> Key: CLOUDSTACK-10238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Fix for metalink support



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


[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10238:
-

borisstoyanov commented on issue #2411: CLOUDSTACK-10238: Fix for metalink 
support on SSVM agents
URL: https://github.com/apache/cloudstack/pull/2411#issuecomment-358916216
 
 
   @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 for metalink support on SSVM agents
> ---
>
> Key: CLOUDSTACK-10238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Fix for metalink support



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


[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10238:
-

blueorangutan commented on issue #2411: CLOUDSTACK-10238: Fix for metalink 
support on SSVM agents
URL: https://github.com/apache/cloudstack/pull/2411#issuecomment-358915385
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1662


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 for metalink support on SSVM agents
> ---
>
> Key: CLOUDSTACK-10238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Fix for metalink support



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


[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10238:
-

blueorangutan commented on issue #2411: CLOUDSTACK-10238: Fix for metalink 
support on SSVM agents
URL: https://github.com/apache/cloudstack/pull/2411#issuecomment-358908835
 
 
   @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


> Fix for metalink support on SSVM agents
> ---
>
> Key: CLOUDSTACK-10238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Fix for metalink support



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


[jira] [Commented] (CLOUDSTACK-10238) Fix for metalink support on SSVM agents

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10238:
-

borisstoyanov commented on issue #2411: CLOUDSTACK-10238: Fix for metalink 
support on SSVM agents
URL: https://github.com/apache/cloudstack/pull/2411#issuecomment-358908675
 
 
   @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 for metalink support on SSVM agents
> ---
>
> Key: CLOUDSTACK-10238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Fix for metalink support



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


[jira] [Commented] (CLOUDSTACK-10146) Bypass Secondary Storage for KVM templates

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10146:
-

borisstoyanov commented on issue #2405: CLOUDSTACK-10146 checksum in java 
instead of script
URL: https://github.com/apache/cloudstack/pull/2405#issuecomment-358908779
 
 
   @blueoranbutan 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


> Bypass Secondary Storage for KVM templates
> --
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>




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


[jira] [Commented] (CLOUDSTACK-10141) no password with instance creation

2018-01-19 Thread Rohit Yadav (JIRA)

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

Rohit Yadav commented on CLOUDSTACK-10141:
--

Kristian - I think, there is no credential leak. Yes, agree stale password/ssh 
public key may be available to new VMs that have the IP of a old/destroy VM. 
However, if the new VM (from a ssh/password enabled template) is indeed 
password or SSH enabled, during provisioning the user/account specific ssh key 
and new password will be stored in the VR. So I don't think it's a security 
issue but a GC issue perhaps. I think the solution could be to rid of ssh 
public key and passwords when VM is destroyed/removed?

> no password with instance creation 
> ---
>
> Key: CLOUDSTACK-10141
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10141
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Virtual Router
>Affects Versions: 4.9.0, 4.10.0.0
> Environment: 2 x Xenserver 7.0 pool.   ACSv 4.10,  system vms 4.10
>Reporter: Kristian Liivak
>Priority: Major
>  Labels: patch
>
> With instance creation password is not created
> I performed several tests with macchinina template. 
> Before that i restarted network with clean up option eg new VR was created.
> But result are: VR password file is not modified after instance creation. 
> File is not created when i first time created instance.
> Shutdown instance and reset password only created VR password file and it 
> contains correct entry
> I have only one network present. its one big /24 shared network for all vms. 
> Also ipv6 is present.  Cloudmonkey list network output is also added below.
> My log is here:; ips are changed with aaa.bbb.ccc
> Restarted netowrk with option cleanup. logged in to VR
> root@r-377-VM  :/ var/cache/cloud# ls -lah
> total 36K
> drwxr-xr-x  3 root root 4.0K Nov 13 14:35 .
> drwxr-xr-x 10 root root 4.0K Nov 13 14:29 ..
> -rw-r--r--  1 root root   29 Nov 13 14:29 boot_up_done
> -rw-r--r--  1 root root   33 Nov 13 14:28 cloud-scripts-signature
> -rw-r--r--  1 root root  754 Nov 13 14:29 cmdline
> -rw-r--r--  1 root root   33 Nov 13 14:29 disabled_svcs
> -rw-r--r--  1 root root2 Nov 13 14:29 dnsmasq_managed_lease
> -rw-r--r--  1 root root   38 Nov 13 14:29 enabled_svcs
> drwxr-xr-x  2 root root 4.0K Nov 13 14:35 processed
> Created new instance and get gui password "Password of new VM Macchinina1 is 
> EJ4cQ2"
> Nothing changed in files /var/cache/cloud
> Shutdown instance and reset succesfully  password in gui"Password has been 
> reset to dt8sNZ"
> Now i have correct file created in VR and it contains correct password
> root@r-377-VM  :/ var/cache/cloud# ls -lah
> total 40K
> drwxr-xr-x  3 root root 4.0K Nov 13 14:37 .
> drwxr-xr-x 10 root root 4.0K Nov 13 14:29 ..
> -rw-r--r--  1 root root   29 Nov 13 14:29 boot_up_done
> -rw-r--r--  1 root root   33 Nov 13 14:28 cloud-scripts-signature
> -rw-r--r--  1 root root  754 Nov 13 14:29 cmdline
> -rw-r--r--  1 root root   33 Nov 13 14:29 disabled_svcs
> -rw-r--r--  1 root root2 Nov 13 14:29 dnsmasq_managed_lease
> -rw-r--r--  1 root root   38 Nov 13 14:29 enabled_svcs
> -rw-r--r--  1 root root   21 Nov 13 14:37 passwords-aaa.bbb.ccc.2
> drwxr-xr-x  2 root root 4.0K Nov 13 14:37 processed
> root@r-377-VM  :/ var/cache/cloud# more passwords-aaa.bbb.ccc.2
> aaa.bbb.ccc.196=dt8sNZ
> Powered up instance and tailed VR  password file
> root@r-377-VM  :/ var/cache/cloud# tail -f passwords-aaa.bbb.ccc.2
> aaa.bbb.ccc.196=dt8sNZ
> tail: passwords-aaa.bbb.ccc.2: file truncated
> Vm have correct password. And VR password file is empty
> Next try with new instance. created. Password of new VM Macchinina2 is 
> U8jBqC,,  tailed VR password file. No changes at all..
> Stopped new instance. resetted password "Password has been reset to Y9mwzN"
> root@r-377-VM  :/ var/cache/cloud# tail -f passwords-aaa.bbb.ccc.2
> aaa.bbb.ccc.196=dt8sNZ
> aaa.bbb.ccc.169=Y9mwzN
> New password is there.
> tail: passwords-aaa.bbb.ccc.2: file truncated
> aaa.bbb.ccc.196=dt8sNZ
> Vm started. password is changed . VR password file entry is removed 
> Conclusion : with instance creation no password is provided. With password 
> reset everything is ok.  I noticed issue allready ACSv 4.9,  system vms 4.6 . 
> After upgade nothing changed.



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


[jira] [Closed] (CLOUDSTACK-10236) Unable to login to ACS after upgrading 4.5 -> 4.11

2018-01-19 Thread Rohit Yadav (JIRA)

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

Rohit Yadav closed CLOUDSTACK-10236.

Resolution: Not A Problem
  Assignee: Rohit Yadav

Post upgrading, if admin is still using static role base checker, i.e. 
commands.properties file - they need to add new APIs to it and restart mgmt 
server.

By adding quotaIsEnabled=15 (enable API for all), fixes the issue of UI login 
failure. I checked without the fix, cloudmonkey/APIs work.

> Unable to login to ACS after upgrading 4.5 -> 4.11 
> ---
>
> Key: CLOUDSTACK-10236
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10236
> 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: Boris Stoyanov
>Assignee: Rohit Yadav
>Priority: Blocker
> Fix For: 4.11.0.0
>
>
> I've upgraded my CentOS6 env from 4.5 to 4.11 and ended up not being able to 
> login. I'm getting 'Session expired' message right after I enter my admin 
> username and password. Here's the management log output: 
>  
> {code:java}
> 2018-01-17 13:07:47,383 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Attempting to log in user: 
> admin in domain 1
> 2018-01-17 13:07:47,389 DEBUG [o.a.c.s.a.PBKDF2UserAuthenticator] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Retrieving user: admin
> 2018-01-17 13:07:48,248 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) CIDRs from which account 
> 'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed to perform API 
> calls: 0.0.0.0/0,::/0
> 2018-01-17 13:07:48,249 DEBUG [c.c.u.AccountManagerImpl] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) User: admin in domain 1 has 
> successfully logged in
> 2018-01-17 13:07:48,260 INFO [c.c.a.ApiServer] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Current user logged in under 
> UTC timezone
> 2018-01-17 13:07:48,260 INFO [c.c.a.ApiServer] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) Timezone offset from UTC is: 
> 0.0
> 2018-01-17 13:07:48,267 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-19:ctx-404c4037) (logid:2d1dd5ba) ===END=== 10.1.0.1 – POST
> 2018-01-17 13:07:48,340 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-16:ctx-390d3282) (logid:b98a9144) ===START=== 10.1.0.1 – GET 
> command=listCapabilities=json&_=1516194514030
> 2018-01-17 13:07:48,349 DEBUG [c.c.a.ApiServer] 
> (qtp1310540333-16:ctx-390d3282 ctx-0509900f) (logid:b98a9144) CIDRs from 
> which account 'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed 
> to perform API calls: 0.0.0.0/0,::/0
> 2018-01-17 13:07:48,372 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-16:ctx-390d3282 ctx-0509900f) (logid:b98a9144) ===END=== 
> 10.1.0.1 – GET command=listCapabilities=json&_=1516194514030
> 2018-01-17 13:07:48,439 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-19:ctx-495f6fd0) (logid:67992211) ===START=== 10.1.0.1 – GET 
> command=listZones=json&_=1516194514137
> 2018-01-17 13:07:48,449 DEBUG [c.c.a.ApiServer] 
> (qtp1310540333-19:ctx-495f6fd0 ctx-606dcc84) (logid:67992211) CIDRs from 
> which account 'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed 
> to perform API calls: 0.0.0.0/0,::/0
> 2018-01-17 13:07:48,474 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-19:ctx-495f6fd0 ctx-606dcc84) (logid:67992211) ===END=== 
> 10.1.0.1 – GET command=listZones=json&_=1516194514137
> 2018-01-17 13:07:48,549 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-16:ctx-f2bcf13f) (logid:f73a6f0c) ===START=== 10.1.0.1 – GET 
> command=cloudianIsEnabled=json&_=1516194514249
> 2018-01-17 13:07:48,556 DEBUG [c.c.a.ApiServer] 
> (qtp1310540333-16:ctx-f2bcf13f ctx-3e6a3a41) (logid:f73a6f0c) CIDRs from 
> which account 'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed 
> to perform API calls: 0.0.0.0/0,::/0
> 2018-01-17 13:07:48,579 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-16:ctx-f2bcf13f ctx-3e6a3a41) (logid:f73a6f0c) ===END=== 
> 10.1.0.1 – GET command=cloudianIsEnabled=json&_=1516194514249
> 2018-01-17 13:07:48,645 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-19:ctx-560f926e) (logid:62a5cb2f) ===START=== 10.1.0.1 – GET 
> command=quotaIsEnabled=json&_=1516194514343
> 2018-01-17 13:07:48,653 DEBUG [c.c.a.ApiServer] 
> (qtp1310540333-19:ctx-560f926e ctx-c9a2914a) (logid:62a5cb2f) CIDRs from 
> which account 'Acct[3daa963c-fb6a-11e7-ae7e-06efa8010701-admin]' is allowed 
> to perform API calls: 0.0.0.0/0,::/0
> 2018-01-17 13:07:48,658 DEBUG [c.c.a.ApiServer] 
> (qtp1310540333-19:ctx-560f926e ctx-c9a2914a) (logid:62a5cb2f) The given 
> command 'quotaIsEnabled' either does not exist, is not available for user, or 
> not available from ip address 

[jira] [Closed] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread Rohit Yadav (JIRA)

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

Rohit Yadav closed CLOUDSTACK-10233.


> When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in 
> metadata is missing
> ---
>
> Key: CLOUDSTACK-10233
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> 
> 
> 
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Closed] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread Rohit Yadav (JIRA)

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

Rohit Yadav closed CLOUDSTACK-9749.
---

> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0, 4.11.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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


[jira] [Updated] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread Rohit Yadav (JIRA)

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

Rohit Yadav updated CLOUDSTACK-9749:

Fix Version/s: 4.11.0.0

> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0, 4.11.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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


[jira] [Resolved] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread Raf Smeets (JIRA)

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

Raf Smeets resolved CLOUDSTACK-10233.
-
   Resolution: Fixed
Fix Version/s: 4.11.0.0

Fixed in 4.11

> When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in 
> metadata is missing
> ---
>
> Key: CLOUDSTACK-10233
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.11.0.0
>
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> 
> 
> 
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

blueorangutan commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for 
direct downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358902982
 
 
   @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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

rhtyd commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for direct 
downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358902885
 
 
   @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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

blueorangutan commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for 
direct downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358901735
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1661


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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread ASF subversion and git services (JIRA)

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

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

Commit a9fdb31585a1e3250fd3a4d1627c697d6f624018 in cloudstack's branch 
refs/heads/master from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=a9fdb31 ]

CLOUDSTACK-9749: Fix Password server running on internal LB VM (#2409)

Fixes code to start password server only on routers.

> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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


[jira] [Commented] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread ASF subversion and git services (JIRA)

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

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

Commit cfff78d9a114dca8f0552503a68bade83a7faeaa in cloudstack's branch 
refs/heads/master from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=cfff78d ]

CLOUDSTACK-10233: Use namespace in Libvirt domain metadata. (#2410)

The documentation of Libvirt specifies the requirement of using an XML 
namespace,
when having metadata in the Domain XML. The Nuage extenstion metadata was not
adhering to this specification, and the lastest Libvirt version ignores it in 
that case.

> When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in 
> metadata is missing
> ---
>
> Key: CLOUDSTACK-10233
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> 
> 
> 
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

blueorangutan commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for 
direct downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358896223
 
 
   @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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

rhtyd commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for direct 
downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358896030
 
 
   @nvazquez should this be seen as a blocker? /cc @DaanHoogland and others
   @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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10231) Detach ISO fails for direct downloaded ISO on KVM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10231:
-

rhtyd commented on issue #2408: CLOUDSTACK-10231: Detach ISO fails for direct 
downloaded ISO on KVM
URL: https://github.com/apache/cloudstack/pull/2408#issuecomment-358896030
 
 
   @nvazquez should this been seen as a blocker? /cc @DaanHoogland and others
   @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


> Detach ISO fails for direct downloaded ISO on KVM
> -
>
> Key: CLOUDSTACK-10231
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
> 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
>Assignee: Nicolas Vazquez
>Priority: Major
>
> Dettach ISO fails when trying to detach a direct download ISO (KVM only)



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


[jira] [Commented] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10233:
-

rhtyd commented on issue #2410: CLOUDSTACK-10233: use namespace in Libvirt 
domain metadata.
URL: https://github.com/apache/cloudstack/pull/2410#issuecomment-358895845
 
 
   Test LGTM, merging based on test results and code reviews.


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


> When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in 
> metadata is missing
> ---
>
> Key: CLOUDSTACK-10233
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> 
> 
> 
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Commented] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-10233:
-

rhtyd closed pull request #2410: CLOUDSTACK-10233: use namespace in Libvirt 
domain metadata.
URL: https://github.com/apache/cloudstack/pull/2410
 
 
   

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/LibvirtVMDef.java
 
b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
index 81077fa7254..385fe79ef2a 100644
--- 
a/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
+++ 
b/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java
@@ -1544,7 +1544,7 @@ public void addNuageExtension(String macAddress, String 
vrIp) {
 public String toString() {
 StringBuilder fsBuilder = new StringBuilder();
 for (Map.Entry address : addresses.entrySet()) {
-fsBuilder.append("\n")
+fsBuilder.append("\n")
 .append("  
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Commented] (CLOUDSTACK-10233) When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in metadata is missing

2018-01-19 Thread ASF subversion and git services (JIRA)

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

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

Commit cfff78d9a114dca8f0552503a68bade83a7faeaa in cloudstack's branch 
refs/heads/4.11 from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=cfff78d ]

CLOUDSTACK-10233: Use namespace in Libvirt domain metadata. (#2410)

The documentation of Libvirt specifies the requirement of using an XML 
namespace,
when having metadata in the Domain XML. The Nuage extenstion metadata was not
adhering to this specification, and the lastest Libvirt version ignores it in 
that case.

> When installed ACS on Rhel7.4 with libvirt-3.2.0 the nuage-extension in 
> metadata is missing
> ---
>
> Key: CLOUDSTACK-10233
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10233
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.11.0.0
> Environment: Nuage VSP plugin on RHEL 7.4
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
>
> When installed ACS 4.11 on top of Rhel7.4 baseimage with libvirt-3.2.0 ,there 
> is an issue with the metadata of the created VM in cloudstack. 
> It leads to password reset failure as the nuage vrs is not allowing passage 
> to DomainRouter.
> After debugging , it was found that the nuage-extension in metadata was 
> missing.
> When cloudstack-agent is preparing xml to be sent to openvswitch it contains 
> metadata with nuage-extension block as follows
> 
> 
> 
> 
> 
> In /var/log/openvswitch/vm-monitor.log , the received XML of VM is without 
> nuage-extension block in metadata as follows:
> Jan 15 18:17:17 ovs-1 vm-monitor.log: 
> So the metadata block is now empty. It seems libvirt 3.2.0 requires an url in 
> its metada, so the libvirt namespace needs to be adapted.



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


[jira] [Commented] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread ASF subversion and git services (JIRA)

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

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

Commit a9fdb31585a1e3250fd3a4d1627c697d6f624018 in cloudstack's branch 
refs/heads/4.11 from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=a9fdb31 ]

CLOUDSTACK-9749: Fix Password server running on internal LB VM (#2409)

Fixes code to start password server only on routers.

> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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


[jira] [Commented] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-9749:


rhtyd commented on issue #2409: CLOUDSTACK-9749: Fix Password server running on 
internal LB VM
URL: https://github.com/apache/cloudstack/pull/2409#issuecomment-358895327
 
 
   No regressions seen, merging this based on that and code reviews.


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


> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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


[jira] [Commented] (CLOUDSTACK-9749) cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by password server on lb VM

2018-01-19 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on CLOUDSTACK-9749:


rhtyd closed pull request #2409: CLOUDSTACK-9749: Fix Password server running 
on internal LB VM
URL: https://github.com/apache/cloudstack/pull/2409
 
 
   

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/systemvm/debian/opt/cloud/bin/cs/CsAddress.py 
b/systemvm/debian/opt/cloud/bin/cs/CsAddress.py
index 6ad50459b57..8b68f538fa4 100755
--- a/systemvm/debian/opt/cloud/bin/cs/CsAddress.py
+++ b/systemvm/debian/opt/cloud/bin/cs/CsAddress.py
@@ -549,10 +549,21 @@ def post_config_change(self, method):
 self.fw_router()
 self.fw_vpcrouter()
 
+cmdline = self.config.cmdline()
+
 # On deletion nw_type will no longer be known
 if self.get_type() in ('guest'):
 if self.config.is_vpc() or self.config.is_router():
 CsDevice(self.dev, self.config).configure_rp()
+
+# If redundant then this is dealt with
+# by the master backup functions
+if not cmdline.is_redundant():
+if method == "add":
+CsPasswdSvc(self.address['public_ip']).start()
+elif method == "delete":
+CsPasswdSvc(self.address['public_ip']).stop()
+
 logging.error(
 "Not able to setup source-nat for a regular router yet")
 
@@ -564,11 +575,6 @@ def post_config_change(self, method):
 app = CsApache(self)
 app.setup()
 
-cmdline = self.config.cmdline()
-# If redundant then this is dealt with by the master backup functions
-if self.get_type() in ["guest"] and not cmdline.is_redundant():
-pwdsvc = CsPasswdSvc(self.address['public_ip']).start()
-
 if self.get_type() == "public" and self.config.is_vpc() and method == 
"add":
 if self.address["source_nat"]:
 vpccidr = cmdline.get_vpccidr()


 


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


> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> --
>
> Key: CLOUDSTACK-9749
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.10.0.0, 4.9.2.0, 4.8.2.0, 4.11.0.0
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
> Fix For: 4.10.0.0
>
> Attachments: runinfo.txt
>
>
> cloudstack master vpc_internal_lb feature is broken as port 8080 is in use by 
> password server on lb VM
> Executed test/integration/plugins/nuagevsp/test_nuage_vpc_internal_lb.py 
> which failed in test_05_nuage_internallb_traffic at the point where it is 
> checking the lb via wget of file using port 8080.
> As port 8080 already is occupied by the password_server, it fails.
> I have added the runinfo.txt of the failing test to this bugticket.
> Similar issue was reported internally via CLOUD-972.



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