[jira] [Commented] (CLOUDSTACK-10245) ResetPassword for guestVm in nuage isolated networks is not working, unable to login with new password

2018-01-22 Thread Kris Sterckx (JIRA)

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

Kris Sterckx commented on CLOUDSTACK-10245:
---

Fix in https://github.com/apache/cloudstack/pull/2419

> ResetPassword for guestVm in nuage isolated networks is not working, unable 
> to login with new password
> --
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in Nuage isolated networks is not 
> working as password_server is not running on VirtualRouter. Unable to login 
> with new password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409]
>  



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


[jira] [Created] (CLOUDSTACK-10247) L2 network not shared on projects

2018-01-22 Thread Nicolas Vazquez (JIRA)
Nicolas Vazquez created CLOUDSTACK-10247:


 Summary: L2 network not shared on projects
 Key: CLOUDSTACK-10247
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10247
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Nicolas Vazquez
Assignee: Nicolas Vazquez


L2 networks are not shared between projects. When trying to deploy a vm 
assigning a project id, error is logged:

2018-01-18 09:04:31,749 INFO  [c.c.a.ApiServer] (qtp1310540333-17:ctx-7ff91c56 
ctx-8c37c46b ctx-d58064ad) (logid:74e86028) PermissionDenied: Unable to use 
network with id= 5bee486a-ff20-4db2-b62e-4b4f3485cfff, permission denied on 
objs: []



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


[jira] [Created] (CLOUDSTACK-10246) VM HA issues

2018-01-22 Thread Nux (JIRA)
Nux created CLOUDSTACK-10246:


 Summary: VM HA issues
 Key: CLOUDSTACK-10246
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10246
 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: My setup is CentOS 7 Management server with 3 CentOS 7 
KVM HVs, NFS as primary and secondary storages.
Reporter: Nux


VM HA fails to kick in when one of the hypervisors goes down.

It even fails to restart the system VMs which remain down along with the 
instances until the affected HV comes back online.

When I crash or power off the HV the system marks it in the hosts list as 
"Alert" or "Disconnected" respectively. It should get changed to "Down" after 
that, but this never happens.

 

I have tried various combinations of setups (Adv, Basic), none succeeded.

 

My instances use HA enabled offerings.

Management server DEBUG logs here:

[http://tmp.nux.ro/CW4-vmhafail-411rc1.txt]

 

 

 

 

 



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


[jira] [Updated] (CLOUDSTACK-10245) ResetPassword for guestVm in nuage isolated networks is not working, unable to login with new password

2018-01-22 Thread Raf Smeets (JIRA)

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

Raf Smeets updated CLOUDSTACK-10245:

Description: 
ResetPassword functionality for guestVm's in Nuage isolated networks is not 
working as password_server is not running on VirtualRouter. Unable to login 
with new password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409]

 

  was:
ResetPassword functionality for guestVm's in Nuage isolated networks is not 
working as password_server is not running on VirtualRouter. Unable to login 
with new password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409]

There is a difference in between native and nuage VR in isolated 
networks:systemvm boot cmdline for native: type=router while it is 
type=dhcpsrvr in Nuage.

It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
 Moving the code block to the if self.config.has_metadata(): block fixes the 
bug.

 


> ResetPassword for guestVm in nuage isolated networks is not working, unable 
> to login with new password
> --
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in Nuage isolated networks is not 
> working as password_server is not running on VirtualRouter. Unable to login 
> with new password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409]
>  



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


[jira] [Updated] (CLOUDSTACK-10245) ResetPassword for guestVm in nuage isolated networks is not working, unable to login with new password

2018-01-22 Thread Raf Smeets (JIRA)

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

Raf Smeets updated CLOUDSTACK-10245:

Description: 
ResetPassword functionality for guestVm's in Nuage isolated networks is not 
working as password_server is not running on VirtualRouter. Unable to login 
with new password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409]

There is a difference in between native and nuage VR in isolated 
networks:systemvm boot cmdline for native: type=router while it is 
type=dhcpsrvr in Nuage.

It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
 Moving the code block to the if self.config.has_metadata(): block fixes the 
bug.

 

  was:
ResetPassword functionality for guestVm's in isolated networks is not working 
as password_server is not running on VirtualRouter. Unable to login with new 
password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
 It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
 Moving the code block to the if self.config.has_metadata(): block fixes the 
bug.

 


> ResetPassword for guestVm in nuage isolated networks is not working, unable 
> to login with new password
> --
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in Nuage isolated networks is not 
> working as password_server is not running on VirtualRouter. Unable to login 
> with new password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409]
> There is a difference in between native and nuage VR in isolated 
> networks:systemvm boot cmdline for native: type=router while it is 
> type=dhcpsrvr in Nuage.
> It seems neither self.config.is_vpc() nor self.config.is_router() are true 
> while the VPC VR is of type DHCP server.
>  Moving the code block to the if self.config.has_metadata(): block fixes the 
> bug.
>  



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


[jira] [Updated] (CLOUDSTACK-10245) ResetPassword for guestVm in nuage isolated networks is not working, unable to login with new password

2018-01-22 Thread Raf Smeets (JIRA)

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

Raf Smeets updated CLOUDSTACK-10245:

Summary: ResetPassword for guestVm in nuage isolated networks is not 
working, unable to login with new password  (was: ResetPassword for guestVm in 
isolated networks is not working, unable to login with new password)

> ResetPassword for guestVm in nuage isolated networks is not working, unable 
> to login with new password
> --
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in isolated networks is not working 
> as password_server is not running on VirtualRouter. Unable to login with new 
> password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
>  It seems neither self.config.is_vpc() nor self.config.is_router() are true 
> while the VPC VR is of type DHCP server.
>  Moving the code block to the if self.config.has_metadata(): block fixes the 
> bug.
>  



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


[jira] [Updated] (CLOUDSTACK-10245) ResetPassword for guestVm in isolated networks is not working, unable to login with new password

2018-01-22 Thread Raf Smeets (JIRA)

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

Raf Smeets updated CLOUDSTACK-10245:

Description: 
ResetPassword functionality for guestVm's in isolated networks is not working 
as password_server is not running on VirtualRouter. Unable to login with new 
password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
 It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
 Moving the code block to the if self.config.has_metadata(): block fixes the 
bug.

 

  was:
ResetPassword functionality for guestVm's in isolated networks is not working 
as password_server is not running on VirtualRouter. Unable to login with new 
password.

Scenario to reproduce: native run 
test/integration/component/test_vm_passwdenabled.py
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
 It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
 Moving the code block to the if self.config.has_metadata(): block fixes the 
bug.

 


> ResetPassword for guestVm in isolated networks is not working, unable to 
> login with new password
> 
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in isolated networks is not working 
> as password_server is not running on VirtualRouter. Unable to login with new 
> password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
>  It seems neither self.config.is_vpc() nor self.config.is_router() are true 
> while the VPC VR is of type DHCP server.
>  Moving the code block to the if self.config.has_metadata(): block fixes the 
> bug.
>  



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


[jira] [Updated] (CLOUDSTACK-10245) ResetPassword for guestVm in isolated networks is not working, unable to login with new password

2018-01-22 Thread Raf Smeets (JIRA)

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

Raf Smeets updated CLOUDSTACK-10245:

Description: 
ResetPassword functionality for guestVm's in isolated networks is not working 
as password_server is not running on VirtualRouter. Unable to login with new 
password.

Scenario to reproduce: native run 
test/integration/component/test_vm_passwdenabled.py
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
 It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
 Moving the code block to the if self.config.has_metadata(): block fixes the 
bug.

 

  was:
ResetPassword functionality for guestVm's in isolated networks is not working 
as password_server is not running on VirtualRouter. Unable to login with new 
password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
Moving the code block to the if self.config.has_metadata(): block fixes the bug.


> ResetPassword for guestVm in isolated networks is not working, unable to 
> login with new password
> 
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in isolated networks is not working 
> as password_server is not running on VirtualRouter. Unable to login with new 
> password.
> Scenario to reproduce: native run 
> test/integration/component/test_vm_passwdenabled.py
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
>  It seems neither self.config.is_vpc() nor self.config.is_router() are true 
> while the VPC VR is of type DHCP server.
>  Moving the code block to the if self.config.has_metadata(): block fixes the 
> bug.
>  



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


[jira] [Updated] (CLOUDSTACK-10245) ResetPassword for guestVm in isolated networks is not working, unable to login with new password

2018-01-22 Thread Kris Sterckx (JIRA)

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

Kris Sterckx updated CLOUDSTACK-10245:
--
Priority: Blocker  (was: Critical)

> ResetPassword for guestVm in isolated networks is not working, unable to 
> login with new password
> 
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Blocker
>
> ResetPassword functionality for guestVm's in isolated networks is not working 
> as password_server is not running on VirtualRouter. Unable to login with new 
> password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
> It seems neither self.config.is_vpc() nor self.config.is_router() are true 
> while the VPC VR is of type DHCP server.
> Moving the code block to the if self.config.has_metadata(): block fixes the 
> bug.



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


[jira] [Assigned] (CLOUDSTACK-10245) ResetPassword for guestVm in isolated networks is not working, unable to login with new password

2018-01-22 Thread Kris Sterckx (JIRA)

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

Kris Sterckx reassigned CLOUDSTACK-10245:
-

Assignee: Frank Maximus

> ResetPassword for guestVm in isolated networks is not working, unable to 
> login with new password
> 
>
> Key: CLOUDSTACK-10245
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.11.0.0, 4.12
>Reporter: Raf Smeets
>Assignee: Frank Maximus
>Priority: Critical
>
> ResetPassword functionality for guestVm's in isolated networks is not working 
> as password_server is not running on VirtualRouter. Unable to login with new 
> password.
> Scenario to reproduce:
>  # Execute ResetPassword on GuestVM
>  # Try to login with new password fails as passwordserver is not running on 
> port 8080 in VR.
> After some further debugging, found that this bug is introduced while fixing 
> CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
> It seems neither self.config.is_vpc() nor self.config.is_router() are true 
> while the VPC VR is of type DHCP server.
> Moving the code block to the if self.config.has_metadata(): block fixes the 
> bug.



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


[jira] [Created] (CLOUDSTACK-10245) ResetPassword for guestVm in isolated networks is not working, unable to login with new password

2018-01-22 Thread Raf Smeets (JIRA)
Raf Smeets created CLOUDSTACK-10245:
---

 Summary: ResetPassword for guestVm in isolated networks is not 
working, unable to login with new password
 Key: CLOUDSTACK-10245
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10245
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.11.0.0, 4.12
Reporter: Raf Smeets


ResetPassword functionality for guestVm's in isolated networks is not working 
as password_server is not running on VirtualRouter. Unable to login with new 
password.

Scenario to reproduce:
 # Execute ResetPassword on GuestVM
 # Try to login with new password fails as passwordserver is not running on 
port 8080 in VR.

After some further debugging, found that this bug is introduced while fixing 
CLOUDSTACK-9749 by [https://github.com/apache/cloudstack/pull/2409] 
It seems neither self.config.is_vpc() nor self.config.is_router() are true 
while the VPC VR is of type DHCP server.
Moving the code block to the if self.config.has_metadata(): block fixes the bug.



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


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

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

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

Wido den Hollander commented on CLOUDSTACK-10243:
-

I haven't tried 4.11 RC1, but the Python code hasn't changed in between.

 

The Python code say that p.wait() should not be used and can block with large 
output

> 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
>Priority: Major
>  Labels: basic-networking, python, virtual-router
> 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] [Reopened] (CLOUDSTACK-10236) Unable to login to ACS after upgrading 4.5 -> 4.11

2018-01-22 Thread Boris Stoyanov (JIRA)

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

Boris Stoyanov reopened CLOUDSTACK-10236:
-

Reopening, this shouldn't be admin duty. This upgrade problem should be handled 
by the upgrade process since it's part of a feature and it shouldn't be 
blocking any user from logging in. 

> 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 '/10.1.0.1'.
> 2018-01-17 13:07:48,660 DEBUG [c.c.a.ApiServlet] 
> (qtp1310540333-19:ctx-560f926e ctx-c9a2914a) (logid:62a5cb2f) ===END=== 
> 10.1.0.1 – 

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

2018-01-22 Thread Rohit Yadav (JIRA)

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

Rohit Yadav commented on CLOUDSTACK-10141:
--

[~k...@wavecom.ee] my answer was in-line and for reference with the on-going 
discussion on dev@ ML that links to this issue.

Sure, continue testing and keep us posted.

> 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] [Commented] (CLOUDSTACK-10243) Updating metadata might hang on VR on "ip rule show"

2018-01-22 Thread Rohit Yadav (JIRA)

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

Rohit Yadav commented on CLOUDSTACK-10243:
--

[~widodh] are you able to reproduce this with 4.11.0.0-rc1?

> 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
>Priority: Major
>  Labels: basic-networking, python, virtual-router
> 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-10244) Online storage migration for KVM fails and corrupts disk

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

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

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

Commit 7e39961f22ab3157994fc075325287ecaf365d11 in cloudstack's branch 
refs/heads/master from [~rohit.ya...@shapeblue.com]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=7e39961 ]

Merge branch '4.11'

- CLOUDSTACK-10244: Cache whether to migrate storage

Signed-off-by: Rohit Yadav 


> 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-22 Thread ASF subversion and git services (JIRA)

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

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

Commit 2ca264ca4d78d89f7f190d6e4c6af81f5f3d7569 in cloudstack's branch 
refs/heads/master from [~mike.tutkow...@netapp.com]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=2ca264c ]

CLOUDSTACK-10244: Cache whether to migrate storage (#2416)

KVM online storage migration fails, this fixes use of whether to migrate 
storage using a cached variable.


> 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)