[jira] [Resolved] (CLOUDSTACK-6278) Baremetal Advanced Networking support

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-6278.
-
Resolution: Fixed

> Baremetal Advanced Networking support
> -
>
> Key: CLOUDSTACK-6278
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.5.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.5.0
>
>
> functional spec link: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support



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

[jira] [Updated] (CLOUDSTACK-7619) Baremetal - Have an out of the box Isolated network offering with PXE & DHCP services provided by VR along with all other services from default isolated network offe

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-7619:

Fix Version/s: (was: 4.5.0)
   4.6.0

> Baremetal - Have an out of the box Isolated network offering with PXE & DHCP 
> services provided by VR along with all other services from default isolated 
> network offering for baremetal instances.
> --
>
> Key: CLOUDSTACK-7619
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7619
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.6.0
>
>
> Baremetal - Have an out of the box Isolated network offering with PXE & DHCP 
> services provided by VR slong with all other services from default isolated 
> network offering for baremetal instances.



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

[jira] [Commented] (CLOUDSTACK-7619) Baremetal - Have an out of the box Isolated network offering with PXE & DHCP services provided by VR along with all other services from default isolated network of

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-7619:
-

This need schema change which is too late to 4.5.
It's an enhancement feature; put it off to 4.6

> Baremetal - Have an out of the box Isolated network offering with PXE & DHCP 
> services provided by VR along with all other services from default isolated 
> network offering for baremetal instances.
> --
>
> Key: CLOUDSTACK-7619
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7619
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.6.0
>
>
> Baremetal - Have an out of the box Isolated network offering with PXE & DHCP 
> services provided by VR slong with all other services from default isolated 
> network offering for baremetal instances.



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

[jira] [Updated] (CLOUDSTACK-7619) Baremetal - Have an out of the box Isolated network offering with PXE & DHCP services provided by VR along with all other services from default isolated network offe

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-7619:

Affects Version/s: (was: 4.5.0)
   4.6.0

> Baremetal - Have an out of the box Isolated network offering with PXE & DHCP 
> services provided by VR along with all other services from default isolated 
> network offering for baremetal instances.
> --
>
> Key: CLOUDSTACK-7619
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7619
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.6.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.6.0
>
>
> Baremetal - Have an out of the box Isolated network offering with PXE & DHCP 
> services provided by VR slong with all other services from default isolated 
> network offering for baremetal instances.



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

[jira] [Resolved] (CLOUDSTACK-7629) addBaremetalRct() API call is not available in cloudstackAPI library in marvin.

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-7629.
-
Resolution: Fixed

> addBaremetalRct() API call is not available in cloudstackAPI library in 
> marvin.
> ---
>
> Key: CLOUDSTACK-7629
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7629
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.5.0
>
>
> addBaremetalRct() API call is not available in cloudstackAPI library in 
> marvin.
> When a new API call is added , we expect the python libraries for this API to 
> be available as part of cloudstackAPI in marvin.
>  



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

[jira] [Updated] (CLOUDSTACK-7618) Baremetal - AddHost() API docs should include parameters - cpunumber,cpuspeed,memory,hostmac

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-7618:

Fix Version/s: (was: 4.5.0)
   4.6.0

> Baremetal - AddHost() API docs should include parameters - 
> cpunumber,cpuspeed,memory,hostmac
> 
>
> Key: CLOUDSTACK-7618
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7618
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.6.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.6.0
>
>
> Baremetal - AddHost() API docs should include parameters - 
> cpunumber,cpuspeed,memory,hostmac.
> When adding a baremetal host , following 4 parameters are supported  for 
> addHost() API call - cpunumber,cpuspeed,memory,hostmac.
> API docs should include information about these parameters. 



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

[jira] [Updated] (CLOUDSTACK-7618) Baremetal - AddHost() API docs should include parameters - cpunumber,cpuspeed,memory,hostmac

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-7618:

Affects Version/s: (was: 4.5.0)
   4.6.0

> Baremetal - AddHost() API docs should include parameters - 
> cpunumber,cpuspeed,memory,hostmac
> 
>
> Key: CLOUDSTACK-7618
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7618
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.6.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.6.0
>
>
> Baremetal - AddHost() API docs should include parameters - 
> cpunumber,cpuspeed,memory,hostmac.
> When adding a baremetal host , following 4 parameters are supported  for 
> addHost() API call - cpunumber,cpuspeed,memory,hostmac.
> API docs should include information about these parameters. 



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

[jira] [Commented] (CLOUDSTACK-7618) Baremetal - AddHost() API docs should include parameters - cpunumber,cpuspeed,memory,hostmac

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-7618:
-

This is some architecture flaw that cannot be fixed in 4.5
CloudStack API doesn't provide a way that accepts extra parameters. Back to 3 
years ago when baremetal was initially designed, the extra parameters  
cpunumber,cpuspeed,memory,hostmac were passed in as query parameters in URL, 
and baremetal discoverer will parse these parameters by itself; this make API 
doc generation code will not be aware of these parameters' existence. To fix it,
we need to either build a new API doc generator or introduce new API that has 
these parameters as class field.
Given the design change, I suggest putting off this bug to next release, as it 
won't effect any CloudStack functionality.

> Baremetal - AddHost() API docs should include parameters - 
> cpunumber,cpuspeed,memory,hostmac
> 
>
> Key: CLOUDSTACK-7618
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7618
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
> Fix For: 4.5.0
>
>
> Baremetal - AddHost() API docs should include parameters - 
> cpunumber,cpuspeed,memory,hostmac.
> When adding a baremetal host , following 4 parameters are supported  for 
> addHost() API call - cpunumber,cpuspeed,memory,hostmac.
> API docs should include information about these parameters. 



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

[jira] [Commented] (CLOUDSTACK-7746) Baremetal related script erros seen on router console

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-7746:
-

reassign to Hari. please close it after fixing the template

> Baremetal related script erros seen on router console
> -
>
> Key: CLOUDSTACK-7746
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7746
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
> Environment: Build from master
>Reporter: Sangeetha Hariharan
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.5.0
>
> Attachments: router.png
>
>
> Baremetal related script erros seen on router console.
> Advanced zone set up with 3 xenserver hosts in a cluster.
> When logging into the console view of router , following script errors are 
> seen:
> /opt/cloud/bin/baremetal-vr.py:159: SyntaxWarning : name 'server' is assigned 
> to before glocal declaration. ..
> Attached is the screen shot



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

[jira] [Updated] (CLOUDSTACK-7746) Baremetal related script erros seen on router console

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-7746:

Assignee: Harikrishna Patnala  (was: frank zhang)

> Baremetal related script erros seen on router console
> -
>
> Key: CLOUDSTACK-7746
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7746
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
> Environment: Build from master
>Reporter: Sangeetha Hariharan
>Assignee: Harikrishna Patnala
>Priority: Critical
> Fix For: 4.5.0
>
> Attachments: router.png
>
>
> Baremetal related script erros seen on router console.
> Advanced zone set up with 3 xenserver hosts in a cluster.
> When logging into the console view of router , following script errors are 
> seen:
> /opt/cloud/bin/baremetal-vr.py:159: SyntaxWarning : name 'server' is assigned 
> to before glocal declaration. ..
> Attached is the screen shot



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

[jira] [Resolved] (CLOUDSTACK-7834) Web UI shows all DHCP/PXE providers in cloud when admin click DHCP/PXE IP for A zone.

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-7834.
-
Resolution: Fixed

> Web UI shows all DHCP/PXE providers in cloud when admin click DHCP/PXE IP for 
> A zone.
> -
>
> Key: CLOUDSTACK-7834
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7834
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.5.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.5.0
>
>




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

[jira] [Created] (CLOUDSTACK-7834) Web UI shows all DHCP/PXE providers in cloud when admin click DHCP/PXE IP for A zone.

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-7834:
---

 Summary: Web UI shows all DHCP/PXE providers in cloud when admin 
click DHCP/PXE IP for A zone.
 Key: CLOUDSTACK-7834
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7834
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Baremetal
Affects Versions: 4.5.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.5.0






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

[jira] [Resolved] (CLOUDSTACK-7795) Fix multiple baremetal rct configuraitons

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-7795.
-
Resolution: Fixed

> Fix multiple baremetal rct configuraitons
> -
>
> Key: CLOUDSTACK-7795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7795
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.5.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.5.0
>
>




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

[jira] [Created] (CLOUDSTACK-7795) Fix multiple baremetal rct configuraitons

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-7795:
---

 Summary: Fix multiple baremetal rct configuraitons
 Key: CLOUDSTACK-7795
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7795
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Baremetal
Affects Versions: 4.5.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.5.0






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

[jira] [Resolved] (CLOUDSTACK-7523) java.lang.NullPointerException when listing accounts.

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-7523.
-
Resolution: Fixed

>  java.lang.NullPointerException when listing accounts.
> --
>
> Key: CLOUDSTACK-7523
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7523
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0
> Environment: Build from master
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.5.0
>
>
> Deploy a fresh Management server.
> After this try to list Accounts , by going to Accounts tab in UI.
> There is no entries returned and the UI keeps spinning.
> listAccounts() fail with return code - 530 .
>  
> 2014-09-09 12:38:59,932 INFO  [a.c.c.a.ApiServer] 
> (catalina-exec-18:ctx-0c561c21 ctx-dcbc1d59) (userId=2 accountId=2 
> sessionId=600DA8E1BD8DC8B8DF75DD5B5FC9E7E9) 10.215.3.17 -- GET 
> command=listAccounts&response=json&sessionkey=2%2Bf%2BWC0FhPn6j%2BiLp3mj2POhdsY%3D&listAll=true&page=1&pagesize=20&_=1410305103203
>  530 null
> Following exception seen in management server logs:
> 2014-09-09 08:39:22,417 DEBUG [c.c.a.ApiServlet] 
> (catalina-exec-7:ctx-d2a3ffdc) ===START===  10.216.50.29 -- GET  
> command=listAccounts&response=json&sessionkey=XkWSjL0e3Xe3ckgR5jW2CsSYOeA%3D&listAll=true&page=1&pagesize=20&_=1410290672605
> 2014-09-09 08:39:22,832 ERROR [c.c.a.ApiServer] (catalina-exec-7:ctx-d2a3ffdc 
> ctx-9db713ee) unhandled exception executing api command: 
> [Ljava.lang.String;@1a1bdce4
> java.lang.NullPointerException
> at 
> com.cloud.api.query.dao.AccountJoinDaoImpl.setResourceLimits(AccountJoinDaoImpl.java:144)
> at 
> com.cloud.api.query.dao.AccountJoinDaoImpl.newAccountResponse(AccountJoinDaoImpl.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at com.sun.proxy.$Proxy111.newAccountResponse(Unknown Source)
> at com.cloud.api.ApiDBUtils.newAccountResponse(ApiDBUtils.java:1788)
> at 
> com.cloud.api.query.ViewResponseHelper.createAccountResponse(ViewResponseHelper.java:353)
> at 
> com.cloud.api.query.QueryManagerImpl.searchForAccounts(QueryManagerImpl.java:1835)
> at 
> org.apache.cloudstack.api.command.user.account.ListAccountsCmd.execute(ListAccountsCmd.java:93)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:694)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:517)
> at 
> com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:273)
> at com.cloud.api.ApiServlet$1.run(ApiServlet.java:117)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:114)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:76)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCha

[jira] [Created] (CLOUDSTACK-7660) Enhance system vm template to support baremetal

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-7660:
---

 Summary: Enhance system vm template to support baremetal
 Key: CLOUDSTACK-7660
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7660
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: SystemVM
Affects Versions: 4.5.0
Reporter: frank zhang
Assignee: Harikrishna Patnala
 Fix For: 4.5.0


Two things need doing:
1. pip install flask when building template
2. merge 7 disk partitions to single one



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

[jira] [Resolved] (CLOUDSTACK-7366) Baremetal agent is not including in RPM spec file

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-7366.
-

Resolution: Fixed

> Baremetal agent is not including in RPM spec file
> -
>
> Key: CLOUDSTACK-7366
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7366
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.5.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CLOUDSTACK-7366) Baremetal agent is not including in RPM spec file

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-7366:
---

 Summary: Baremetal agent is not including in RPM spec file
 Key: CLOUDSTACK-7366
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7366
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Packaging
Affects Versions: 4.5.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.5.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CLOUDSTACK-6933) [Automation] Registering an iso fails in KVM deployment.

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-6933.
-

Resolution: Won't Fix

> [Automation] Registering an iso fails in KVM deployment.
> 
>
> Key: CLOUDSTACK-6933
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6933
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.4.0
> Environment: KVM advanced network
>Reporter: Bharat Kumar
>Assignee: frank zhang
> Fix For: 4.4.0
>
>
> registing an iso fails with the connection refused error in KVM deployment.
> below are the iptable rules on the relevant SSVM in the env.
> Chain INPUT (policy DROP 28 packets, 1340 bytes)
>  pkts bytes target prot opt in out source   
> destination 
> 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:443
> 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:80
> 0 0 ACCEPT tcp  --  eth1   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:3922
>   172 13277 ACCEPT all  --  eth0   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
>  4122  469K ACCEPT all  --  eth1   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
>   196 10976 ACCEPT all  --  eth2   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
> 0 0 ACCEPT all  --  eth3   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
> 0 0 ACCEPT all  --  lo *   0.0.0.0/00.0.0.0/0 
>   
> 0 0 DROP   icmp --  *  *   0.0.0.0/00.0.0.0/0 
>icmptype 13
> 0 0 ACCEPT icmp --  *  *   0.0.0.0/00.0.0.0/0 
>   
> 3   180 ACCEPT tcp  --  eth0   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:3922
> Chain FORWARD (policy DROP 0 packets, 0 bytes)
>  pkts bytes target prot opt in out source   
> destination 
> Chain OUTPUT (policy ACCEPT 511 packets, 81586 bytes)
>  pkts bytes target prot opt in out source   
> destination 
> 0 0 ACCEPT tcp  --  *  eth10.0.0.0/0
> 172.16.88.0/24   state NEW tcp
>  2576  155K ACCEPT tcp  --  *  eth10.0.0.0/0
> 172.16.88.0/24   state NEW tcp
> 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:80 reject-with icmp-port-unreachable
> 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:443 reject-with icmp-port-unreachable
> Chain HTTP (0 references)
>  pkts bytes target prot opt in out source   
> destination 
> root@s-54-QA:~# route -n 
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse Iface
> 0.0.0.0 172.16.171.10.0.0.0 UG0  00 eth2
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 eth0
> 172.16.88.0 0.0.0.0 255.255.255.0   U 0  00 eth1
> 172.16.88.0 0.0.0.0 255.255.255.0   U 0  00 eth3
> 172.16.171.00.0.0.0 255.255.255.0   U 0  00 eth2
> As per the above config when a packet is sent to 172.16.88.x/24 subnet  we 
> are routing it via interface eth1. but we also have a reject rule in the 
> OUTPUT chain for the packets leaving from eth1. as a result the packets get 
> dropped. 
> if we interchange the routes i.e. if the route related to eth3 is hit before 
> hitting the eth1 route the register iso is successful. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CLOUDSTACK-6933) [Automation] Registering an iso fails in KVM deployment.

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-6933:
-

This is a corner case in storage network. The storage network is designed to 
have a separate subnet from management subnet, however, we also allow mgmt 
network and storage network to be the same subnet in case customer only has one 
network for both purpose.
In this case, you must set global setting "secstorage.allowed.internal.sites" 
to a smaller CIDR than mgmt network CIDR. The best practice is to set it to ip 
to secondary storage.
By doing so, the routing issue is solved because Linux routing use most 
specific match.
 

> [Automation] Registering an iso fails in KVM deployment.
> 
>
> Key: CLOUDSTACK-6933
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6933
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation
>Affects Versions: 4.4.0
> Environment: KVM advanced network
>Reporter: Bharat Kumar
>Assignee: frank zhang
> Fix For: 4.4.0
>
>
> registing an iso fails with the connection refused error in KVM deployment.
> below are the iptable rules on the relevant SSVM in the env.
> Chain INPUT (policy DROP 28 packets, 1340 bytes)
>  pkts bytes target prot opt in out source   
> destination 
> 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:443
> 0 0 ACCEPT tcp  --  eth2   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:80
> 0 0 ACCEPT tcp  --  eth1   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:3922
>   172 13277 ACCEPT all  --  eth0   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
>  4122  469K ACCEPT all  --  eth1   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
>   196 10976 ACCEPT all  --  eth2   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
> 0 0 ACCEPT all  --  eth3   *   0.0.0.0/00.0.0.0/0 
>state RELATED,ESTABLISHED
> 0 0 ACCEPT all  --  lo *   0.0.0.0/00.0.0.0/0 
>   
> 0 0 DROP   icmp --  *  *   0.0.0.0/00.0.0.0/0 
>icmptype 13
> 0 0 ACCEPT icmp --  *  *   0.0.0.0/00.0.0.0/0 
>   
> 3   180 ACCEPT tcp  --  eth0   *   0.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:3922
> Chain FORWARD (policy DROP 0 packets, 0 bytes)
>  pkts bytes target prot opt in out source   
> destination 
> Chain OUTPUT (policy ACCEPT 511 packets, 81586 bytes)
>  pkts bytes target prot opt in out source   
> destination 
> 0 0 ACCEPT tcp  --  *  eth10.0.0.0/0
> 172.16.88.0/24   state NEW tcp
>  2576  155K ACCEPT tcp  --  *  eth10.0.0.0/0
> 172.16.88.0/24   state NEW tcp
> 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:80 reject-with icmp-port-unreachable
> 0 0 REJECT tcp  --  *  eth10.0.0.0/00.0.0.0/0 
>state NEW tcp dpt:443 reject-with icmp-port-unreachable
> Chain HTTP (0 references)
>  pkts bytes target prot opt in out source   
> destination 
> root@s-54-QA:~# route -n 
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse Iface
> 0.0.0.0 172.16.171.10.0.0.0 UG0  00 eth2
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 eth0
> 172.16.88.0 0.0.0.0 255.255.255.0   U 0  00 eth1
> 172.16.88.0 0.0.0.0 255.255.255.0   U 0  00 eth3
> 172.16.171.00.0.0.0 255.255.255.0   U 0  00 eth2
> As per the above config when a packet is sent to 172.16.88.x/24 subnet  we 
> are routing it via interface eth1. but we also have a reject rule in the 
> OUTPUT chain for the packets leaving from eth1. as a result the packets get 
> dropped. 
> if we interchange the routes i.e. if the route related to eth3 is hit before 
> hitting the eth1 route the register iso is successful. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CLOUDSTACK-6278) Baremetal Advanced Networking support

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-6278:


Description: functional spec link: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support

> Baremetal Advanced Networking support
> -
>
> Key: CLOUDSTACK-6278
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.4.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.4.0
>
>
> functional spec link: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Baremetal+Advanced+Networking+Support



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CLOUDSTACK-6278) Baremetal Advanced Networking support

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-6278:
---

 Summary: Baremetal Advanced Networking support
 Key: CLOUDSTACK-6278
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6278
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Baremetal
Affects Versions: 4.4.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.4.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CLOUDSTACK-6219) 3.0.7 Patch E to Felton: fk_external_dhcp_devices_pod_id` foreign key constraint is remanant on `baremetal_dhcp_devices` table on the Upgraded Setup. It is not prese

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-6219:
---

 Summary: 3.0.7 Patch E to Felton: fk_external_dhcp_devices_pod_id` 
foreign key constraint is remanant on `baremetal_dhcp_devices` table on the 
Upgraded Setup. It is not present on the Fresh Setup
 Key: CLOUDSTACK-6219
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6219
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Baremetal
Affects Versions: 4.3.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.3.0






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (CLOUDSTACK-6219) 3.0.7 Patch E to Felton: fk_external_dhcp_devices_pod_id` foreign key constraint is remanant on `baremetal_dhcp_devices` table on the Upgraded Setup. It is not presen

[frank zhang (JIRA)]

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

frank zhang closed CLOUDSTACK-6219.
---

Resolution: Fixed

wrong bug report

> 3.0.7 Patch E to Felton: fk_external_dhcp_devices_pod_id` foreign key 
> constraint is remanant on `baremetal_dhcp_devices` table on the Upgraded 
> Setup. It is not present on the Fresh Setup
> --
>
> Key: CLOUDSTACK-6219
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6219
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.3.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CLOUDSTACK-6155) Baremetal agent RPM missing in spec file

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-6155.
-

Resolution: Fixed

> Baremetal agent RPM missing in spec file
> 
>
> Key: CLOUDSTACK-6155
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6155
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.3.0
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (CLOUDSTACK-6155) Baremetal agent RPM missing in spec file

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-6155:
---

 Summary: Baremetal agent RPM missing in spec file
 Key: CLOUDSTACK-6155
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6155
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Baremetal
Affects Versions: 4.3.0
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.3.0






--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CLOUDSTACK-5350) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-5350.
-

Resolution: Duplicate

> [Automation] Failed to attach volume to VM, if the vm is created with option 
> startvm=false
> --
>
> Key: CLOUDSTACK-5350
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5350
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes
>Affects Versions: 4.3.0
> Environment: KVM (RHEL 6.3)
> Branch : 4.3
>Reporter: Rayees Namathponnan
>Assignee: frank zhang
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Regression automation failure 
> test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume
> Steps to reproduce 
>  # Validate the following:
> 1. deploy Vm  with the startvm=false. Attach volume to the instance
> 2. listVM command should return the deployed VM.State of this VM should be 
> "Stopped".
> 3. Attach volume should be successful
> Actual Result
>  
> Attach volume failed with below error 
> 2013-12-03 08:45:50,190 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] 
> (Job-Executor-8:ctx-780454c7 ctx-c09f3d6f) List of pools in ascending order
> of number of volumes for account id: 516 is: []
> 2013-12-03 08:45:50,190 WARN  [o.a.c.e.o.VolumeOrchestrator] 
> (Job-Executor-8:ctx-780454c7 ctx-c09f3d6f) Unable to find suitable primary 
> storage whe
> n creating volume DataDisk
> 2013-12-03 08:45:50,208 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (Job-Executor-8:ctx-780454c7) Unexpected exception while executing 
> org.apache.cloudstac
> k.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable 
> primary storage when creating volume DataDisk
> at 
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:399)
> at 
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:697)
> at 
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1086)
> at sun.reflect.GeneratedMethodAccessor681.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy232.attachVolumeToVM(Unknown Source)
> at 
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at 
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at 
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
> at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache

[jira] [Commented] (CLOUDSTACK-5350) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-5350:
-

Rayees, How to rerun this to get a db dump?

> [Automation] Failed to attach volume to VM, if the vm is created with option 
> startvm=false
> --
>
> Key: CLOUDSTACK-5350
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5350
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes
>Affects Versions: 4.3.0
> Environment: KVM (RHEL 6.3)
> Branch : 4.3
>Reporter: Rayees Namathponnan
>Assignee: frank zhang
>Priority: Blocker
> Fix For: 4.3.0
>
>
> Regression automation failure 
> test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume
> Steps to reproduce 
>  # Validate the following:
> 1. deploy Vm  with the startvm=false. Attach volume to the instance
> 2. listVM command should return the deployed VM.State of this VM should be 
> "Stopped".
> 3. Attach volume should be successful
> Actual Result
>  
> Attach volume failed with below error 
> 2013-12-03 08:45:50,190 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] 
> (Job-Executor-8:ctx-780454c7 ctx-c09f3d6f) List of pools in ascending order
> of number of volumes for account id: 516 is: []
> 2013-12-03 08:45:50,190 WARN  [o.a.c.e.o.VolumeOrchestrator] 
> (Job-Executor-8:ctx-780454c7 ctx-c09f3d6f) Unable to find suitable primary 
> storage whe
> n creating volume DataDisk
> 2013-12-03 08:45:50,208 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (Job-Executor-8:ctx-780454c7) Unexpected exception while executing 
> org.apache.cloudstac
> k.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable 
> primary storage when creating volume DataDisk
> at 
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:399)
> at 
> org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:697)
> at 
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1086)
> at sun.reflect.GeneratedMethodAccessor681.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
> at $Proxy232.attachVolumeToVM(Unknown Source)
> at 
> org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> at 
> com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
> at 
> com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
> at 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520)
> at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.c

[jira] [Resolved] (CLOUDSTACK-5115) [baremetal] upgrade 4.2.0 ->4.2.1. Unable to start baremetal instance due to Cannot prepare pxe server

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-5115.
-

Resolution: Fixed

fixed in 88047a458b94ab2db3af360b6615f5812f22819a

> [baremetal] upgrade 4.2.0 ->4.2.1. Unable to start baremetal instance due to 
> Cannot prepare pxe server
> --
>
> Key: CLOUDSTACK-5115
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5115
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.2.1
> Environment: MS10.223.50.3   rhel 6.4   
>  upgrade  CloudPlatform-4.2.0-2-rhel6.4.tar.gz  ->  
> CloudPlatform-4.2.1-41-rhel6.4.tar.gz
> baremetal host1
>  host2
>Reporter: angeline shen
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> 1. MS   installed  with   CloudPlatform-4.2.0-2-rhel6.4.tar.gz
> BM DHCP VM installed with  CloudPlatform-4.2.0-2-rhel6.4.tar.gz
>  Deploy  BM zone. create BM  cluster, add host1, register template
>  Deploy  BM  instance.  Verify  BM instance installed correctly.
> 2. MS:   upgrade to  CloudPlatform-4.2.1-41-rhel6.4.tar.gz
>  ./install.sh> U
> BM DHCP VM:  upgrade to  CloudPlatform-4.2.1-41-rhel6.4.tar.gz
>  ./install.sh> U
>  cloudstack-setup-baremetal
> 3. MS:   service cloudstack-management start
>  In  BM  cluster, add host2, register template2
>  Deploy  BM  instance  FAIL:
> Error: Unable to start baremetal instance due to Cannot prepare pxe server
> 2013-11-08 16:50:45,975 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-1:job-17 = [ 36497193-c912-4a4c-b171-7f5c181a73e3 ]) release 
> cpu from host: 4, old used: 100,reserved: 0, actual total: 2600, total with 
>  overprovisioning: 2600; new used: 0,reserved:0; movedfromreserved: 
> false,moveToReserveredfalse 
> 2013-11-08 16:50:45,975 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-1:job-17 = [ 36497193-c912-4a4c-b171-7f5c181a73e3 ]) release 
> mem from host: 4, old used: 536870912,reserved: 0, total: 17179869184; new  
> used: 0,reserved:0; movedfromreserved: false,moveToReserveredfalse 
> 2013-11-08 16:50:46,077 DEBUG [cloud.vm.UserVmManagerImpl] 
> (Job-Executor-1:job-17 = [ 36497193-c912-4a4c-b171-7f5c181a73e3 ]) Destroying 
> vm VM[User|z1bm63V5] as it failed to create on Host with Id:null 
> 2013-11-08 16:50:46,185 DEBUG [baremetal.manager.BaremetalManagerImpl] 
> (Job-Executor-1:job-17 = [ 36497193-c912-4a4c-b171-7f5c181a73e3 ]) Skip 
> oldState Stopped to newState Error transimtion 
> 2013-11-08 16:50:46,186 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-1:job-17 = [ 36497193-c912-4a4c-b171-7f5c181a73e3 ]) VM state 
> transitted from :Stopped to Error with event: OperationFailedToErrorvm's 
> original host id: null new host id: null host id before state transition: 
> null 
> 2013-11-08 16:50:46,342 WARN  [apache.cloudstack.alerts] 
> (Job-Executor-1:job-17 = [ 36497193-c912-4a4c-b171-7f5c181a73e3 ])  
> alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // 
> message:: Failed to deploy Vm with Id: 2, on Host with Id: null 
> 2013-11-08 16:50:46,619 WARN  [user.vm.DeployVMCmd] (Job-Executor-1:job-17 = 
> [ 36497193-c912-4a4c-b171-7f5c181a73e3 ]) Exception:  
> com.cloud.exception.AgentUnavailableException: Resource [Host:4] is 
> unreachable: Host 4: Unable to start instance due to Cannot prepare pxe server
> at 
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:999)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577)
> at 
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
> at 
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3440)
>  at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3000)
>  at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2986)
>  at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531

[jira] [Resolved] (CLOUDSTACK-5112) [Baremetal]Make IPMI retry times configurable

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-5112.
-

Resolution: Fixed

> [Baremetal]Make IPMI retry times configurable
> -
>
> Key: CLOUDSTACK-5112
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5112
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.2.1
>Reporter: frank zhang
>Assignee: frank zhang
> Fix For: 4.2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (CLOUDSTACK-5112) [Baremetal]Make IPMI retry times configurable

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-5112:
---

 Summary: [Baremetal]Make IPMI retry times configurable
 Key: CLOUDSTACK-5112
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5112
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Baremetal
Affects Versions: 4.2.1
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.2.1






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4711) UCS:API: Premature API response prevent CS from syncing association status

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4711:
-

This is fixed by introducing sync blades status API in 4.2.1

> UCS:API: Premature API response prevent CS from syncing association status
> --
>
> Key: CLOUDSTACK-4711
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4711
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> We rely on association tag from UCS manager to determine the association 
> success.
> association="none" 
> However UCS sometimes send this response prematurely in which case CS fails 
> the API and association is unsuccessful.
> Eventually UCS finishes association and CS and UCS are now out of sync.
> Now if admin attempts to re-associate this blade then it will error out 
> saying the "Object already exists" 
> We need to device another strategy for this to work flawlessly.
> 2013-09-19 14:35:08,554 WARN  
> [commons.httpclient.SimpleHttpConnectionManager] (Job-Executor-19:job-19 = [ 
> 561e963d-be42-418b-be73-dcb7abf98e08 ]) SimpleHttpConnectionManager being 
> used incorrectly.  Be sure that HttpMethod.releaseConnection() is always 
> called and that only one thread and/or method is using this connection 
> manager at a time.
> 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) 
> association response is   cookie="1379626356/ce72a30f-c52f-4772-a546-b2620243" response="yes"> 
>   assignedToDn="" association="none" availability="available" 
> availableMemory="65536" chassisId="1" checkPoint="discovered"  connPath="A" 
> connStatus="A" descr="" discovery="complete" dn="sys/chassis-1/blade-1" 
> fltAggr="0" fsmDescr="" fsmFlags="" fsmPrev="DisassociateSuccess" 
> fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" 
> fsmStageDescr="" fsmStamp="2013-09-19T14:35:06.906" fsmStatus="nop" 
> fsmTry="0" intId="36071" lc="discovered" lcTs="1969-12-31T16:00:00.000" 
> lowVoltageMemory="low-voltage" managingInst="A" memorySpeed="1333" 
> mfgTime="2012-10-14T01:00:00.000" model="UCSB-B200-M3" name="" 
> numOfAdaptors="1" numOfCores="12" numOfCoresEnabled="12" numOfCpus="2" 
> numOfEthHostIfs="0" numOfFcHostIfs="0" numOfThreads="24" operPower="off" 
> operQualifier="" operState="unassociated" operability="operable" 
> originalUuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" partNumber="73-13217-08" 
> presence="equipped" revision="0"  serial="FCH16407N8A" serverId="1/1" 
> slotId="1"  totalMemory="65536" usrLbl="" 
> uuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" vendor="Cisco Systems Inc" 
> vid="V03"/>  
> 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeCmd] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Exception:
> com.cloud.utils.exception.CloudRuntimeException: cannot associated a profile 
> to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for 
> detailed error information
> at 
> com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsManagerImpl.java:351)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(UcsManagerImpl.java:380)
> at 
> org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execute(AssociateUcsProfileToBladeCmd.java:58)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete 
> async job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: cannot associated a 
> profile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger 
> for detailed error information
> 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
>

[jira] [Resolved] (CLOUDSTACK-4674) [baremetal] /usr/share/cloudstack-common/scripts/util/ipmi.py script need to recognize various ipmi version and BMC type of server

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4674.
-

Resolution: Fixed

> [baremetal] /usr/share/cloudstack-common/scripts/util/ipmi.py script need to 
> recognize various ipmi version and BMC type of server
> --
>
> Key: CLOUDSTACK-4674
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4674
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS   4.2  campo
> baremetal 
>Reporter: angeline shen
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> On MS:  ./usr/share/cloudstack-common/scripts/util/ipmi.py :
>  o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "chassis", 
> "bootdev", dev)
> need to include  -l   lanplus option :
> o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "-l", 
> "lanplus",  "chassis", "bootdev", dev)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4674) [baremetal] /usr/share/cloudstack-common/scripts/util/ipmi.py script need to recognize various ipmi version and BMC type of server

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4674:
-

In process, should be done by end of this week or early next week

> [baremetal] /usr/share/cloudstack-common/scripts/util/ipmi.py script need to 
> recognize various ipmi version and BMC type of server
> --
>
> Key: CLOUDSTACK-4674
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4674
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS   4.2  campo
> baremetal 
>Reporter: angeline shen
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> On MS:  ./usr/share/cloudstack-common/scripts/util/ipmi.py :
>  o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "chassis", 
> "bootdev", dev)
> need to include  -l   lanplus option :
> o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "-l", 
> "lanplus",  "chassis", "bootdev", dev)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-4676) [Baremetal] baremetal hostename should not be fixed in kickstart file

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4676.
-

Resolution: Won't Fix

This feature needs lots of effort. Unless it's from PM team, I won't commit to 
it

> [Baremetal]  baremetal hostename should not be fixed in  kickstart file 
> 
>
> Key: CLOUDSTACK-4676
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4676
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
>Reporter: angeline shen
>Assignee: frank zhang
> Fix For: 4.3.0
>
>
> since baremetal hostname is fixed in kickstart file, if baremetal server 
> choose same template, hostnames are all the same.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-3765) [packaging][document] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-3765.
-

Resolution: Fixed

> [packaging][document] unable to upgrade cp 4.2 build on centos5.5
> -
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (CLOUDSTACK-4676) [Baremetal] baremetal hostename should not be fixed in kickstart file

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4676:
-

this is a big feature enhancement that cannot be fixed in 4.3.

Kickstart templates are provided by user which is out of controller of 
CloudStack. this bug requires CloudStack has ability to modify template content

> [Baremetal]  baremetal hostename should not be fixed in  kickstart file 
> 
>
> Key: CLOUDSTACK-4676
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4676
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
>Reporter: angeline shen
>Assignee: frank zhang
> Fix For: 4.3.0
>
>
> since baremetal hostname is fixed in kickstart file, if baremetal server 
> choose same template, hostnames are all the same.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (CLOUDSTACK-4888) API:UCS:NPE Refresh blades on a decommissioned chassis results in NPE

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4888.
-

Resolution: Fixed

> API:UCS:NPE Refresh blades on a decommissioned chassis results in NPE
> -
>
> Key: CLOUDSTACK-4888
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4888
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> Expecting an appropriate error.
> When refresh blades is issues on a decommissioned chassis.
> 2013-10-17 13:52:26,432 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) 
> ===START===  10.215.2.19 -- GET  
> command=refreshUcsBlades&response=json&sessionkey=e0Kgb2hcBQPMXSe5O%2FDeRH8v2%2B8%3D&ucsmanagerid=f185ae78-08cb-4a06-a3c8-47c3d2afa896&_=1382043146927
> 2013-10-17 13:52:26,451 DEBUG [ucs.manager.UcsHttpClient] 
> (catalina-exec-6:null) UCS call:  cookie="1382042998/2e94d89b-026b-4fbd-be82-489759483570" 
> inHierarchical="false" classId="computeBlade" />
> 2013-10-17 13:52:26,458 WARN  [ucs.manager.UcsManagerImpl] 
> (catalina-exec-6:null) null
> java.lang.NullPointerException
> at 
> com.cloud.ucs.structure.ComputeBlade.fromXmlObject(ComputeBlade.java:62)
> at 
> com.cloud.ucs.structure.ComputeBlade.fromXmString(ComputeBlade.java:55)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:285)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.access$100(UcsManagerImpl.java:65)
> at 
> com.cloud.ucs.manager.UcsManagerImpl$SyncBladesThread.syncBlades(UcsManagerImpl.java:141)
> at 
> com.cloud.ucs.manager.UcsManagerImpl$SyncBladesThread.run(UcsManagerImpl.java:156)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.refreshBlades(UcsManagerImpl.java:624)
> at 
> org.apache.cloudstack.api.RefreshUcsBladesCmd.execute(RefreshUcsBladesCmd.java:42)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:514)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:372)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:305)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at 
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at 
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> 2013-10-17 13:52:26,468 DEBUG [ucs.manager.UcsHttpClient] 
> (catalina-exec-6:null) UCS call:  cookie="1382042998/2e94d89b-026b-4fbd-be82-489759483570" 
> inHierarchical="false" classId="computeBlade" />
> 2013-10-17 13:52:26,471 WARN  [cloudstack.api.RefreshUcsBladesCmd] 
> (catalina-exec-6:null) unhandled exception:
> java.lang.NullPointerException
> at 
> com.cloud.ucs.structure.ComputeBlade.fromXmlObject(ComputeBlade.java:62)
> at 
> com.cloud.ucs.structure.ComputeBlade.fromXmString(ComputeBlade.java:55)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.listBlades(UcsManagerImpl.java:285)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.refreshBlades(UcsManagerImpl.java:627)
> at 
> org.apache.cl

[jira] [Resolved] (CLOUDSTACK-4688) UCS:UI: queryAsyncJobResult keeps getting fired upon an unsuccessfull profile association

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4688.
-

Resolution: Fixed
  Assignee: frank zhang

> UCS:UI: queryAsyncJobResult keeps getting fired upon an unsuccessfull profile 
> association
> -
>
> Key: CLOUDSTACK-4688
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4688
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UCS, UI
>Affects Versions: 4.2.1
>Reporter: Parth Jagirdar
>Assignee: frank zhang
> Attachments: UCS-UI_Query.png
>
>
> 2013-09-16 14:33:04,801 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) 
> ===START===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%
> 3D&_=1379368164145
> 2013-09-16 14:33:04,811 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-15:null) Async job-13 = [ cb17e5c3-64a4-4c37-bdf7-e03cdadeb618 
> ] completed
> 2013-09-16 14:33:04,815 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) 
> ===END===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%3D
> &_=1379368164145
> 2013-09-16 14:33:07,174 DEBUG [agent.manager.AgentManagerImpl] 
> (AgentManager-Handler-15:null) SeqA 3-1252: Processing Seq 3-1252:  { Cmd , 
> MgmtId: -1, via: 3, Ver: v1, Flags: 11, 
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{
> "_proxyVmId":2,"_loadInfo":"{\n  \"connections\": []\n}","wait":0}}] }
> 2013-09-16 14:33:07,179 DEBUG [agent.manager.AgentManagerImpl] 
> (AgentManager-Handler-15:null) SeqA 3-1252: Sending Seq 3-1252:  { Ans: , 
> MgmtId: 6788531356733, via: 3, Ver: v1, Flags: 100010, 
> [{"com.cloud.agent.api.AgentControlAnswer"
> :{"result":true,"wait":0}}] }
> 2013-09-16 14:33:07,876 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) 
> ===START===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%
> 3D&_=1379368167154
> 2013-09-16 14:33:07,885 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-24:null) Async job-13 = [ cb17e5c3-64a4-4c37-bdf7-e03cdadeb618 
> ] completed
> 2013-09-16 14:33:07,888 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) 
> ===END===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%3D
> &_=1379368167154
> 2013-09-16 14:33:10,834 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
> ===START===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%
> 3D&_=1379368170178
> 2013-09-16 14:33:10,844 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-17:null) Async job-13 = [ cb17e5c3-64a4-4c37-bdf7-e03cdadeb618 
> ] completed
> 2013-09-16 14:33:10,848 DEBUG [cloud.api.ApiServlet] (catalina-exec-17:null) 
> ===END===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%3D
> &_=1379368170178
> 2013-09-16 14:33:13,952 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) 
> ===START===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%3
> D&_=1379368173208
> 2013-09-16 14:33:13,961 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-5:null) Async job-13 = [ cb17e5c3-64a4-4c37-bdf7-e03cdadeb618 
> ] completed
> 2013-09-16 14:33:13,964 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null) 
> ===END===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%3D&
> _=1379368173208
> 2013-09-16 14:33:15,862 DEBUG [agent.manager.AgentManagerImpl] 
> (AgentManager-Handler-2:null) Ping from 4
> 2013-09-16 14:33:16,921 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===START===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHhm0sdUeSo%3
> D&_=1379368176233
> 2013-09-16 14:33:16,930 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-1:null) Async job-13 = [ cb17e5c3-64a4-4c37-bdf7-e03cdadeb618 
> ] completed
> 2013-09-16 14:33:16,933 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===END===  10.215.2.19 -- GET  
> command=queryAsyncJobResult&jobId=cb17e5c3-64a4-4c37-bdf7-e03cdadeb618&response=json&sessionkey=K1TUaBBWENJHygmfpHh

[jira] [Resolved] (CLOUDSTACK-4711) UCS:API: Premature API response prevent CS from syncing association status

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4711.
-

Resolution: Fixed

> UCS:API: Premature API response prevent CS from syncing association status
> --
>
> Key: CLOUDSTACK-4711
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4711
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> We rely on association tag from UCS manager to determine the association 
> success.
> association="none" 
> However UCS sometimes send this response prematurely in which case CS fails 
> the API and association is unsuccessful.
> Eventually UCS finishes association and CS and UCS are now out of sync.
> Now if admin attempts to re-associate this blade then it will error out 
> saying the "Object already exists" 
> We need to device another strategy for this to work flawlessly.
> 2013-09-19 14:35:08,554 WARN  
> [commons.httpclient.SimpleHttpConnectionManager] (Job-Executor-19:job-19 = [ 
> 561e963d-be42-418b-be73-dcb7abf98e08 ]) SimpleHttpConnectionManager being 
> used incorrectly.  Be sure that HttpMethod.releaseConnection() is always 
> called and that only one thread and/or method is using this connection 
> manager at a time.
> 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) 
> association response is   cookie="1379626356/ce72a30f-c52f-4772-a546-b2620243" response="yes"> 
>   assignedToDn="" association="none" availability="available" 
> availableMemory="65536" chassisId="1" checkPoint="discovered"  connPath="A" 
> connStatus="A" descr="" discovery="complete" dn="sys/chassis-1/blade-1" 
> fltAggr="0" fsmDescr="" fsmFlags="" fsmPrev="DisassociateSuccess" 
> fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" 
> fsmStageDescr="" fsmStamp="2013-09-19T14:35:06.906" fsmStatus="nop" 
> fsmTry="0" intId="36071" lc="discovered" lcTs="1969-12-31T16:00:00.000" 
> lowVoltageMemory="low-voltage" managingInst="A" memorySpeed="1333" 
> mfgTime="2012-10-14T01:00:00.000" model="UCSB-B200-M3" name="" 
> numOfAdaptors="1" numOfCores="12" numOfCoresEnabled="12" numOfCpus="2" 
> numOfEthHostIfs="0" numOfFcHostIfs="0" numOfThreads="24" operPower="off" 
> operQualifier="" operState="unassociated" operability="operable" 
> originalUuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" partNumber="73-13217-08" 
> presence="equipped" revision="0"  serial="FCH16407N8A" serverId="1/1" 
> slotId="1"  totalMemory="65536" usrLbl="" 
> uuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" vendor="Cisco Systems Inc" 
> vid="V03"/>  
> 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeCmd] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Exception:
> com.cloud.utils.exception.CloudRuntimeException: cannot associated a profile 
> to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for 
> detailed error information
> at 
> com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsManagerImpl.java:351)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(UcsManagerImpl.java:380)
> at 
> org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execute(AssociateUcsProfileToBladeCmd.java:58)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete 
> async job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: cannot associated a 
> profile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger 
> for detailed error information
> 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===START===  10.252.113.141 -- GET  
> command=queryAsyncJobResult&jobId=561e963d-be42-418b-b

[jira] [Assigned] (CLOUDSTACK-4850) [UCS] using template instead of cloning profile

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4850:
---

Assignee: Jessica Wang  (was: frank zhang)

> [UCS] using template instead of cloning profile
> ---
>
> Key: CLOUDSTACK-4850
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4850
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UCS
>Affects Versions: 4.2.1
>Reporter: frank zhang
>Assignee: Jessica Wang
> Fix For: 4.2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (CLOUDSTACK-4850) [UCS] using template instead of cloning profile

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-4850:
---

 Summary: [UCS] using template instead of cloning profile
 Key: CLOUDSTACK-4850
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4850
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UCS
Affects Versions: 4.2.1
Reporter: frank zhang
Assignee: frank zhang
 Fix For: 4.2.1






--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (CLOUDSTACK-4729) Document workaround for IPMI protocal type for specific hardware on baremetal

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-4729:
---

 Summary: Document workaround for IPMI protocal type for specific 
hardware on baremetal
 Key: CLOUDSTACK-4729
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4729
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Affects Versions: 4.2.1
Reporter: frank zhang
Assignee: Jessica Tomechak
 Fix For: 4.2.1


We should mention to users that Baremetal uses ipmitool to control lifecycle of 
baremetal host. ipmitool default uses interface 'lan' to issue ipmi commands. 
Depending on your motherboard, the interface may need to be 'lanplus', in this 
case, user has to modify script

/usr/lib64/cloud/agent/scripts/util/ipmi.py

replace all lines calling ipmi tool for example:
o = ipmitool("-H", hostname, "-U", usrname, "-P", password, "chassis", "power", 
"status")

to

o = ipmitool("-H", hostname, ,"-I", "lanplus", "-U", usrname, "-P", password, 
"chassis", "power", "status")

this issue will be addressed in next release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4694) UCS:API:UI: Need ability to dis-associate a UCS blade from profile

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4694.
-

Resolution: Fixed

commit fe5468881a37a63f2218ea301acc684c53d0d722
Author: frank 
Date:   Fri Sep 13 22:27:46 2013 -0700

Add disassocating profile to UCS

> UCS:API:UI: Need ability to dis-associate a UCS blade from profile
> --
>
> Key: CLOUDSTACK-4694
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4694
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.1
> Environment: UCS/Master
>Reporter: Parth Jagirdar
>Priority: Critical
>
> We need an API to disassociate a blade from CS, should reflect disassociation 
> on UCS Manager.
> Need UI/icon to do the same.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4689) UI:API: associate Profile to Blade may take longer in some cases, which will result in timeout

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4689.
-

Resolution: Fixed

> UI:API: associate Profile to Blade may take longer in some cases, which will 
> result in timeout
> --
>
> Key: CLOUDSTACK-4689
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4689
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.1
>Reporter: Parth Jagirdar
>Priority: Critical
> Attachments: log
>
>
> In mnay cases association of a profile to blade may take longer in such cases 
> timeout is reached and an error is thrown. However on backend on UCS the 
> association eventually succeeds but on UI/DB this association will not be 
> reflected.
> Please see the log.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4224) UCS:UI: Delete UCS returns unknown API

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4224.
-

Resolution: Fixed

> UCS:UI: Delete UCS returns unknown API
> --
>
> Key: CLOUDSTACK-4224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS, UI
>Affects Versions: 4.2.0
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Attachments: delete UCS.jpeg
>
>
> Please refer to screen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3765) [packaging][document] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

it does


> [packaging][document] unable to upgrade cp 4.2 build on centos5.5
> -
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3765) [packaging][document] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

at latest release note, I don't see instructions to install repos mentioned in 
this bug.
That is when upgrade usage server on rhel5/centos5, user must do 

rpm -Uvh 
http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm

before uggrade

> [packaging][document] unable to upgrade cp 4.2 build on centos5.5
> -
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2224) "filterwin2k" should not be set in dnsmasq.conf

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-2224.
-

Resolution: Fixed

> "filterwin2k" should not be set in dnsmasq.conf
> ---
>
> Key: CLOUDSTACK-2224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.0.2, 4.1.0, 4.2.0
>Reporter: Dennis Lawler
>Assignee: frank zhang
>
> The dnsmasq "filterwin2k" option disables SRV record requests, affecting 
> Kerberos, SIP, Windows KMS, XMPP, and Google Talk. 
> The default configuration in dnsmasq had disabled this option, but it was 
> brought back with commit 3b75abb for unclear reasons. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3765) [packaging][document] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

yes. the upgrade instructions are the same among former releases 

> [packaging][document] unable to upgrade cp 4.2 build on centos5.5
> -
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4554) [upgrade from 3.0.6 to 4.2][vmware] System VM agent doesn't come up after adding a zone on an upgraded setup

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4554.
-

Resolution: Duplicate

> [upgrade from 3.0.6 to 4.2][vmware] System VM agent doesn't come up after 
> adding a zone on an upgraded setup
> 
>
> Key: CLOUDSTACK-4554
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4554
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: SystemVM, Upgrade, VMware
>Affects Versions: 4.2.0
> Environment: upgrade from 3.0.6 to 4.2
> host : esx 4.1 and esx 5.0
>Reporter: Abhinav Roy
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: CS-4554.zip
>
>
> Steps :
> ===
> 1. Deploy a CS 3.0.6 advanced zone network with esx 4.1 host.
> 2. create VMs, snapshots, templates etc.
> 3. upgrade to CS 4.2
> 4. Add a zone with Esx 5.0
> Expected behaviour :
> ===
> System vms for the newly added zone should come up and their agent status 
> should be running.
> Observed behaviour :
> ==
> System vms of the newly added zone do come up but their agent status is not 
> up.
> Their entry is not there in cloud.host tables.
> Attaching all relevant logs and db dumps

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4555) [Upgrade from 3.0.6 to 4.2][vmware] After upgrade the system vms fail to come up because "Secondary storage mount point" is pointing to a wrong location

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4555.
-

Resolution: Fixed

> [Upgrade from 3.0.6 to 4.2][vmware] After upgrade the system vms fail to come 
> up because "Secondary storage mount point" is pointing to a wrong location
> 
>
> Key: CLOUDSTACK-4555
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4555
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Upgrade, VMware
>Affects Versions: 4.2.0
> Environment: upgrade from 3.0.6 to 4.2 
> host : esx 4.1 and esx 5.0
>Reporter: Abhinav Roy
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: CS-4555.zip
>
>
> Steps : 
> === 
> 1. Deploy a CS 3.0.6 advanced zone network with esx 4.1 host. 
> 2. create VMs, snapshots, templates etc. 
> 3. upgrade to CS 4.2 
> 4. Stop and start the system vms once management server has come up
> Observations :
> ===
> When the system vms are restarted so that they can be started with the new 
> templates, following error is seen in the logs :
> 192.100/cpg_vol/abhinav/esx-sec4239, templatePathAtSecondaryStorage: 
> template/tmpl//2/202/, templateName: 319654a4-b3e6-3be0-b501-5cf015efbf09
> 2013-08-29 15:41:25,775 DEBUG [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) Executing: sudo mount -t nfs 
> 10.102.192.100:/cpg_vol/abhinav/esx-sec4239 
> /var/cloudstack/mnt/VM/90310994128556.4b062819
> 2013-08-29 15:41:26,167 DEBUG [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) Execution is successful.
> 2013-08-29 15:41:26,168 DEBUG [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) Executing: sudo chmod -R 777 
> /var/cloudstack/mnt/VM/90310994128556.4b062819
> 2013-08-29 15:41:26,261 DEBUG [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) Exit value is 1
> 2013-08-29 15:41:26,261 DEBUG [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) chmod: changing permissions of 
> `/var/cloudstack/mnt/VM/90310994128556.4b062819/.snapshot': Read-only file 
> system
> 2013-08-29 15:41:26,262 WARN  [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) Unable to set permissions for 
> /var/cloudstack/mnt/VM/90310994128556.4b062819 due to chmod: changing 
> permissions of `/var/cloudstack/mnt/VM/90310994128556.4b062819/.snapshot': 
> Read-only file system
> 2013-08-29 15:41:26,262 ERROR [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-7:10.102.192.23) Unable to create mount point for 
> nfs://10.102.192.100/cpg_vol/abhinav/esx-sec4239
> 2013-08-29 15:41:26,263 INFO  [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-7:10.102.192.23) Secondary storage mount point: /mnt/sec
> 2013-08-29 15:41:26,271 INFO  [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-7:10.102.192.23) Executing command: tar --no-same-owner -xf 
> /mnt/sec/template/tmpl//2/202//319654a4-b3e6-3be0-b501-5cf015efbf09.ova
> 2013-08-29 15:41:26,271 DEBUG [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-7:10.102.192.23) Executing: tar --no-same-owner -xf 
> /mnt/sec/template/tmpl//2/202//319654a4-b3e6-3be0-b501-5cf015efbf09.ova
> 2013-08-29 15:41:26,316 WARN  [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-7:10.102.192.23) Exception: tar --no-same-owner -xf 
> /mnt/sec/template/tmpl//2/202//319654a4-b3e6-3be0-b501-5cf015efbf09.ova
> java.io.IOException: Cannot run program "tar" (in directory 
> "/mnt/sec/template/tmpl/2/202"): java.io.IOException: error=2, No such file 
> or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
> at com.cloud.utils.script.Script.execute(Script.java:183)
> at com.cloud.utils.script.Script.execute(Script.java:161)
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:148)
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:223)
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
> at 
> com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147)
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:561)
> a

[jira] [Commented] (CLOUDSTACK-4426) [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4426:
-

no needs. I am putting a fix to 4555, it's revealed by my fix but it's an old 
bug which has been there for a while.
4554 has nothing to do with my fix.

> [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2
> --
>
> Key: CLOUDSTACK-4426
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4426
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.1
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: cloud_after_upgrade.dmp, cloud-backup.dmp, 
> management-server.log.tar.gz
>
>
> did and upgrade on 3.0.4 patch1 to 4.2 . 
> Having two advance zone 
> 1 with EXI 4.1 
> second with xen 
> After upgrade I destroyed system VM of Vmware zone . New system Vm failed to 
> start . Hitting exception .. 
> MS log snippet shows : 
> 2013-08-20 03:34:58,662 DEBUG [cloud.storage.VolumeManagerImpl] 
> (consoleproxy-1:null) Checking if we need to prepare 1 volumes for 
> VM[ConsoleProxy|v-41-VM] 
> 2013-08-20 03:34:58,677 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:6, type:Image 
> 2013-08-20 03:34:58,688 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:201, type:Primary 
> 2013-08-20 03:34:58,691 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Found template 
> 202-2-d0b7f194-a096-3dd3-b9fa-7fb26ed627a7 in storage pool 201 with 
> VMTemplateStoragePool id: 11 
> 2013-08-20 03:34:58,706 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Acquire lock on VMTemplateStoragePool 11 with timeout 
> 3600 seconds 
> 2013-08-20 03:34:58,724 WARN [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Exception: tar --no-same-owner -xf 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> java.io.IOException: Cannot run program "tar" (in directory 
> "/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl/2/202"): 
> java.io.IOException: error=13, Permission denied 
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:488) 
> at com.cloud.utils.script.Script.execute(Script.java:183) 
> at com.cloud.utils.script.Script.execute(Script.java:161) 
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:147)
>  
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222)
>  
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
>  
> at 
> com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147)
>  
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
>  
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:560)
>  
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>  
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>  
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:679) 
> Caused by: java.io.IOException: java.io.IOException: error=13, Permission 
> denied 
> at java.lang.UNIXProcess.(UNIXProcess.java:164) 
> at java.lang.ProcessImpl.start(ProcessImpl.java:81) 
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) 
> ... 17 more 
> 2013-08-20 03:34:58,726 ERROR [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Unable to unpack snapshot OVA file at: 
> /v

[jira] [Resolved] (CLOUDSTACK-4533) permission issue in usage server and it failed to start after upgrade from 3.0.4 to 4.2

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4533.
-

Resolution: Cannot Reproduce

please reopen if you can reproduce and leave that environment to me

> permission issue in usage server and it failed to start after upgrade from 
> 3.0.4 to 4.2
> ---
>
> Key: CLOUDSTACK-4533
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4533
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging, Upgrade, Usage
>Affects Versions: 4.2.1
> Environment: 
>Reporter: shweta agarwal
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: cloudstack-usage.err, cloudstack-usage.out
>
>
> did an upgrade from 3.0.4 to 4.2  and then start usage server. 
> Usage server failed to start
> giving following exception :
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
> (Permission denied)
> at java.io.FileOutputStream.openAppend(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:207)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at 
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at 
> org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
> at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
> at 
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773)
> at 
> org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:901)
> at 
> org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69)
> at com.cloud.usage.UsageServer.initLog4j(UsageServer.java:89)
> at com.cloud.usage.UsageServer.init(UsageServer.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207)
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
> (Permission denied)
> at java.io.FileOutputStream.openAppend(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:207)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at 
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at 
> org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
> at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
> at 
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:755)
> Attaching full logs.
>   
>   

--
This message is automatically generated by

[jira] [Commented] (CLOUDSTACK-4533) permission issue in usage server and it failed to start after upgrade from 3.0.4 to 4.2

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4533:
-

did you change anything on the environment?
I can not reproduce after logging in. The usage server is running well even if 
I delete the usage.log

> permission issue in usage server and it failed to start after upgrade from 
> 3.0.4 to 4.2
> ---
>
> Key: CLOUDSTACK-4533
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4533
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging, Upgrade, Usage
>Affects Versions: 4.2.1
> Environment: 
>Reporter: shweta agarwal
>Priority: Blocker
> Fix For: 4.2.1
>
> Attachments: cloudstack-usage.err, cloudstack-usage.out
>
>
> did an upgrade from 3.0.4 to 4.2  and then start usage server. 
> Usage server failed to start
> giving following exception :
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
> (Permission denied)
> at java.io.FileOutputStream.openAppend(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:207)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at 
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at 
> org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
> at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
> at 
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:773)
> at 
> org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:901)
> at 
> org.springframework.util.Log4jConfigurer.initLogging(Log4jConfigurer.java:69)
> at com.cloud.usage.UsageServer.initLog4j(UsageServer.java:89)
> at com.cloud.usage.UsageServer.init(UsageServer.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:207)
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /var/log/cloudstack/usage/usage.log 
> (Permission denied)
> at java.io.FileOutputStream.openAppend(Native Method)
> at java.io.FileOutputStream.(FileOutputStream.java:207)
> at java.io.FileOutputStream.(FileOutputStream.java:131)
> at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
> at 
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
> at 
> org.apache.log4j.rolling.RollingFileAppender.activateOptions(RollingFileAppender.java:179)
> at 
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
> at 
> org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
> at 
> org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:492)
> at 
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1001)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:867)
> at 
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:755)
> Attaching full logs.
>   

[jira] [Resolved] (CLOUDSTACK-4426) [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4426.
-

Resolution: Fixed

fixed by change permission every time mounting secondary storage

> [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2
> --
>
> Key: CLOUDSTACK-4426
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4426
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.1
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: cloud_after_upgrade.dmp, cloud-backup.dmp, 
> management-server.log.tar.gz
>
>
> did and upgrade on 3.0.4 patch1 to 4.2 . 
> Having two advance zone 
> 1 with EXI 4.1 
> second with xen 
> After upgrade I destroyed system VM of Vmware zone . New system Vm failed to 
> start . Hitting exception .. 
> MS log snippet shows : 
> 2013-08-20 03:34:58,662 DEBUG [cloud.storage.VolumeManagerImpl] 
> (consoleproxy-1:null) Checking if we need to prepare 1 volumes for 
> VM[ConsoleProxy|v-41-VM] 
> 2013-08-20 03:34:58,677 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:6, type:Image 
> 2013-08-20 03:34:58,688 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:201, type:Primary 
> 2013-08-20 03:34:58,691 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Found template 
> 202-2-d0b7f194-a096-3dd3-b9fa-7fb26ed627a7 in storage pool 201 with 
> VMTemplateStoragePool id: 11 
> 2013-08-20 03:34:58,706 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Acquire lock on VMTemplateStoragePool 11 with timeout 
> 3600 seconds 
> 2013-08-20 03:34:58,724 WARN [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Exception: tar --no-same-owner -xf 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> java.io.IOException: Cannot run program "tar" (in directory 
> "/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl/2/202"): 
> java.io.IOException: error=13, Permission denied 
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:488) 
> at com.cloud.utils.script.Script.execute(Script.java:183) 
> at com.cloud.utils.script.Script.execute(Script.java:161) 
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:147)
>  
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222)
>  
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
>  
> at 
> com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147)
>  
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
>  
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:560)
>  
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>  
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>  
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:679) 
> Caused by: java.io.IOException: java.io.IOException: error=13, Permission 
> denied 
> at java.lang.UNIXProcess.(UNIXProcess.java:164) 
> at java.lang.ProcessImpl.start(ProcessImpl.java:81) 
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) 
> ... 17 more 
> 2013-08-20 03:34:58,726 ERROR [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Unable to unpack snapshot OVA file at: 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> 2013-08-

[jira] [Commented] (CLOUDSTACK-4426) [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4426:
-

I checked the DB, the upgrade is success.
It seems some other issue. What's your mgmt server ip?

> [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2
> --
>
> Key: CLOUDSTACK-4426
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4426
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.1
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: cloud_after_upgrade.dmp, cloud-backup.dmp, 
> management-server.log.tar.gz
>
>
> did and upgrade on 3.0.4 patch1 to 4.2 . 
> Having two advance zone 
> 1 with EXI 4.1 
> second with xen 
> After upgrade I destroyed system VM of Vmware zone . New system Vm failed to 
> start . Hitting exception .. 
> MS log snippet shows : 
> 2013-08-20 03:34:58,662 DEBUG [cloud.storage.VolumeManagerImpl] 
> (consoleproxy-1:null) Checking if we need to prepare 1 volumes for 
> VM[ConsoleProxy|v-41-VM] 
> 2013-08-20 03:34:58,677 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:6, type:Image 
> 2013-08-20 03:34:58,688 DEBUG [storage.image.TemplateDataFactoryImpl] 
> (consoleproxy-1:null) template 202 is already in store:201, type:Primary 
> 2013-08-20 03:34:58,691 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Found template 
> 202-2-d0b7f194-a096-3dd3-b9fa-7fb26ed627a7 in storage pool 201 with 
> VMTemplateStoragePool id: 11 
> 2013-08-20 03:34:58,706 DEBUG [storage.volume.VolumeServiceImpl] 
> (consoleproxy-1:null) Acquire lock on VMTemplateStoragePool 11 with timeout 
> 3600 seconds 
> 2013-08-20 03:34:58,724 WARN [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Exception: tar --no-same-owner -xf 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
>  
> java.io.IOException: Cannot run program "tar" (in directory 
> "/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl/2/202"): 
> java.io.IOException: error=13, Permission denied 
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:488) 
> at com.cloud.utils.script.Script.execute(Script.java:183) 
> at com.cloud.utils.script.Script.execute(Script.java:161) 
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:147)
>  
> at 
> com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222)
>  
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
>  
> at 
> com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147)
>  
> at 
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
>  
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:560)
>  
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>  
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>  
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  
> at java.lang.Thread.run(Thread.java:679) 
> Caused by: java.io.IOException: java.io.IOException: error=13, Permission 
> denied 
> at java.lang.UNIXProcess.(UNIXProcess.java:164) 
> at java.lang.ProcessImpl.start(ProcessImpl.java:81) 
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) 
> ... 17 more 
> 2013-08-20 03:34:58,726 ERROR [storage.resource.VmwareStorageProcessor] 
> (DirectAgent-21:10.147.40.27) Unable to unpack snapshot OVA file at: 
> /var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl

[jira] [Resolved] (CLOUDSTACK-4484) Vmware - Not able to fetch userdata from guest Vms using http:///latest/user-data

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4484.
-

Resolution: Fixed

> Vmware - Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> -
>
> Key: CLOUDSTACK-4484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4484
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0, 4.2.1
> Environment: Build from 4.2-forward
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> Set up:
> Advanced zone set up with vmware host.
> Steps to reproduce the problem:
> Deploy Vm using user data.
> Vm deployment succeeds.
> From with in the guest Vm , try to access the user data using  
> http:///latest/user-data.
> [root@dd-1 ~]# wget http://10.1.1.1/latest/user-data
> --19:58:29--  http://10.1.1.1/latest/user-data
> Connecting to 10.1.1.1:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 19:58:29 ERROR 404: Not Found.
> [root@dd-1 ~]#
> On the router , we do not see /var/www/html/userdata/ file. 
> In my case guest ip address is 10.1.1.45.
> Note- For all instances which  were deployed with no userdata , i see 
> /var/www/html/userdata//user-data which are empty. In case 
> of Vms deployed with userdata , this file is not being created.
> deployVirtualMachine() api call used:
> 2013-08-23 15:26:07,078 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) 
> ===START===  10.215.3.28 -- GET  
> command=deployVirtualMachine&zoneId=93368e7c-db1b-4344-8777-2a6e0507c2ba&templateId=dd5c6bb5-602a-4cc4-9328-a26096294cf7&hypervisor=XenServer&serviceOfferingId=e83c2f9a-cbdc-46dc-8743-c76f3c270e99&networkIds=95528f66-22f8-4932-86b6-96b1183d5693&response=json&name=dd-1&displayName=dd-1&userdata=aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8=&apiKey=2aLe3o6TVY7286zbAJSCqbmhHlhaKU4at9HqUGbLoImE9SzR6Ys6tyWEbkCcDJDH-_Z5RlutsOYhMql2kixZpw&signature=s6Dvwr%2F8vEvqONyJKGmQKETcDVo%3D
> Management server log indicating that the user-data progarmming succeeds:
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Use router's private IP for SSH control.
> IP : 10.223.58.70
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Run vm_data command on domain router 10.2
> 23.58.70, data: routerIP
> 10.223.58.70
> vmIP
> 10.1.1.45
> userdata,user-data
> aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8
> metadata,service-offering
> tiny1
> metadata,availability-zone
> zone1
> metadata,local-ipv4
> 10.1.1.45
> metadata,local-hostname
> dd-1
> metadata,public-ipv4
> 10.223.138.68
> metadata,public-hostname
> 10.223.138.68
> metadata,instance-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,vm-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,public-keys
> none
> metadata,cloud-identifier
> CloudStack-{c9bcecaa-a61a-4192-9df2-4b7c8a9d1294}
> 2013-08-23 15:26:09,983 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) vm_data command on domain router 10.223.58.70 
> completed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (CLOUDSTACK-4484) Vmware - Not able to fetch userdata from guest Vms using http:///latest/user-data

[frank zhang (JIRA)]

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

frank zhang reopened CLOUDSTACK-4484:
-


> Vmware - Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> -
>
> Key: CLOUDSTACK-4484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4484
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0, 4.2.1
> Environment: Build from 4.2-forward
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> Set up:
> Advanced zone set up with vmware host.
> Steps to reproduce the problem:
> Deploy Vm using user data.
> Vm deployment succeeds.
> From with in the guest Vm , try to access the user data using  
> http:///latest/user-data.
> [root@dd-1 ~]# wget http://10.1.1.1/latest/user-data
> --19:58:29--  http://10.1.1.1/latest/user-data
> Connecting to 10.1.1.1:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 19:58:29 ERROR 404: Not Found.
> [root@dd-1 ~]#
> On the router , we do not see /var/www/html/userdata/ file. 
> In my case guest ip address is 10.1.1.45.
> Note- For all instances which  were deployed with no userdata , i see 
> /var/www/html/userdata//user-data which are empty. In case 
> of Vms deployed with userdata , this file is not being created.
> deployVirtualMachine() api call used:
> 2013-08-23 15:26:07,078 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) 
> ===START===  10.215.3.28 -- GET  
> command=deployVirtualMachine&zoneId=93368e7c-db1b-4344-8777-2a6e0507c2ba&templateId=dd5c6bb5-602a-4cc4-9328-a26096294cf7&hypervisor=XenServer&serviceOfferingId=e83c2f9a-cbdc-46dc-8743-c76f3c270e99&networkIds=95528f66-22f8-4932-86b6-96b1183d5693&response=json&name=dd-1&displayName=dd-1&userdata=aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8=&apiKey=2aLe3o6TVY7286zbAJSCqbmhHlhaKU4at9HqUGbLoImE9SzR6Ys6tyWEbkCcDJDH-_Z5RlutsOYhMql2kixZpw&signature=s6Dvwr%2F8vEvqONyJKGmQKETcDVo%3D
> Management server log indicating that the user-data progarmming succeeds:
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Use router's private IP for SSH control.
> IP : 10.223.58.70
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Run vm_data command on domain router 10.2
> 23.58.70, data: routerIP
> 10.223.58.70
> vmIP
> 10.1.1.45
> userdata,user-data
> aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8
> metadata,service-offering
> tiny1
> metadata,availability-zone
> zone1
> metadata,local-ipv4
> 10.1.1.45
> metadata,local-hostname
> dd-1
> metadata,public-ipv4
> 10.223.138.68
> metadata,public-hostname
> 10.223.138.68
> metadata,instance-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,vm-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,public-keys
> none
> metadata,cloud-identifier
> CloudStack-{c9bcecaa-a61a-4192-9df2-4b7c8a9d1294}
> 2013-08-23 15:26:09,983 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) vm_data command on domain router 10.223.58.70 
> completed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4484) Vmware - Not able to fetch userdata from guest Vms using http:///latest/user-data

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4484.
-

Resolution: Invalid

the userdata you use is invalid encoded.
try:

userdata='aGFkZmFhZGZhZHNm' which is encoded from 'hadfaadfadsf'

> Vmware - Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> -
>
> Key: CLOUDSTACK-4484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4484
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0, 4.2.1
> Environment: Build from 4.2-forward
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> Set up:
> Advanced zone set up with vmware host.
> Steps to reproduce the problem:
> Deploy Vm using user data.
> Vm deployment succeeds.
> From with in the guest Vm , try to access the user data using  
> http:///latest/user-data.
> [root@dd-1 ~]# wget http://10.1.1.1/latest/user-data
> --19:58:29--  http://10.1.1.1/latest/user-data
> Connecting to 10.1.1.1:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 19:58:29 ERROR 404: Not Found.
> [root@dd-1 ~]#
> On the router , we do not see /var/www/html/userdata/ file. 
> In my case guest ip address is 10.1.1.45.
> Note- For all instances which  were deployed with no userdata , i see 
> /var/www/html/userdata//user-data which are empty. In case 
> of Vms deployed with userdata , this file is not being created.
> deployVirtualMachine() api call used:
> 2013-08-23 15:26:07,078 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) 
> ===START===  10.215.3.28 -- GET  
> command=deployVirtualMachine&zoneId=93368e7c-db1b-4344-8777-2a6e0507c2ba&templateId=dd5c6bb5-602a-4cc4-9328-a26096294cf7&hypervisor=XenServer&serviceOfferingId=e83c2f9a-cbdc-46dc-8743-c76f3c270e99&networkIds=95528f66-22f8-4932-86b6-96b1183d5693&response=json&name=dd-1&displayName=dd-1&userdata=aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8=&apiKey=2aLe3o6TVY7286zbAJSCqbmhHlhaKU4at9HqUGbLoImE9SzR6Ys6tyWEbkCcDJDH-_Z5RlutsOYhMql2kixZpw&signature=s6Dvwr%2F8vEvqONyJKGmQKETcDVo%3D
> Management server log indicating that the user-data progarmming succeeds:
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Use router's private IP for SSH control.
> IP : 10.223.58.70
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Run vm_data command on domain router 10.2
> 23.58.70, data: routerIP
> 10.223.58.70
> vmIP
> 10.1.1.45
> userdata,user-data
> aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8
> metadata,service-offering
> tiny1
> metadata,availability-zone
> zone1
> metadata,local-ipv4
> 10.1.1.45
> metadata,local-hostname
> dd-1
> metadata,public-ipv4
> 10.223.138.68
> metadata,public-hostname
> 10.223.138.68
> metadata,instance-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,vm-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,public-keys
> none
> metadata,cloud-identifier
> CloudStack-{c9bcecaa-a61a-4192-9df2-4b7c8a9d1294}
> 2013-08-23 15:26:09,983 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) vm_data command on domain router 10.223.58.70 
> completed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-4484) Vmware - Not able to fetch userdata from guest Vms using http:///latest/user-data

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4484:
---

Assignee: frank zhang

> Vmware - Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> -
>
> Key: CLOUDSTACK-4484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4484
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0, 4.2.1
> Environment: Build from 4.2-forward
>Reporter: Sangeetha Hariharan
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.rar
>
>
> Not able to fetch userdata from guest Vms using 
> http:///latest/user-data
> Set up:
> Advanced zone set up with vmware host.
> Steps to reproduce the problem:
> Deploy Vm using user data.
> Vm deployment succeeds.
> From with in the guest Vm , try to access the user data using  
> http:///latest/user-data.
> [root@dd-1 ~]# wget http://10.1.1.1/latest/user-data
> --19:58:29--  http://10.1.1.1/latest/user-data
> Connecting to 10.1.1.1:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 19:58:29 ERROR 404: Not Found.
> [root@dd-1 ~]#
> On the router , we do not see /var/www/html/userdata/ file. 
> In my case guest ip address is 10.1.1.45.
> Note- For all instances which  were deployed with no userdata , i see 
> /var/www/html/userdata//user-data which are empty. In case 
> of Vms deployed with userdata , this file is not being created.
> deployVirtualMachine() api call used:
> 2013-08-23 15:26:07,078 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) 
> ===START===  10.215.3.28 -- GET  
> command=deployVirtualMachine&zoneId=93368e7c-db1b-4344-8777-2a6e0507c2ba&templateId=dd5c6bb5-602a-4cc4-9328-a26096294cf7&hypervisor=XenServer&serviceOfferingId=e83c2f9a-cbdc-46dc-8743-c76f3c270e99&networkIds=95528f66-22f8-4932-86b6-96b1183d5693&response=json&name=dd-1&displayName=dd-1&userdata=aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8=&apiKey=2aLe3o6TVY7286zbAJSCqbmhHlhaKU4at9HqUGbLoImE9SzR6Ys6tyWEbkCcDJDH-_Z5RlutsOYhMql2kixZpw&signature=s6Dvwr%2F8vEvqONyJKGmQKETcDVo%3D
> Management server log indicating that the user-data progarmming succeeds:
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Use router's private IP for SSH control.
> IP : 10.223.58.70
> 2013-08-23 15:26:08,123 DEBUG [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) Run vm_data command on domain router 10.2
> 23.58.70, data: routerIP
> 10.223.58.70
> vmIP
> 10.1.1.45
> userdata,user-data
> aGVsbG8gaG93IHIgdSA/IEkgYW0gZmluZSAuLi51IG9rID8
> metadata,service-offering
> tiny1
> metadata,availability-zone
> zone1
> metadata,local-ipv4
> 10.1.1.45
> metadata,local-hostname
> dd-1
> metadata,public-ipv4
> 10.223.138.68
> metadata,public-hostname
> 10.223.138.68
> metadata,instance-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,vm-id
> eb6adb2c-576c-4722-bb89-a52f2ad49fb3
> metadata,public-keys
> none
> metadata,cloud-identifier
> CloudStack-{c9bcecaa-a61a-4192-9df2-4b7c8a9d1294}
> 2013-08-23 15:26:09,983 INFO  [vmware.resource.VmwareResource] 
> (DirectAgent-162:10.223.58.66) vm_data command on domain router 10.223.58.70 
> completed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1366) UI support for adding baremetal host

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-1366:
-

wont't fix, postpone to future 

> UI support for adding baremetal host
> 
>
> Key: CLOUDSTACK-1366
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1366
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: Future
>Reporter: frank zhang
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: Future
>
> Attachments: management-server.log.gz
>
>
> Current UI call AddHostCmd to add baremetal host, it should switch to 
> AddBaremetalHostCmd

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1366) UI support for adding baremetal host

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-1366:


Fix Version/s: (was: 4.2.0)
   Future

> UI support for adding baremetal host
> 
>
> Key: CLOUDSTACK-1366
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1366
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: Future
>Reporter: frank zhang
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: Future
>
> Attachments: management-server.log.gz
>
>
> Current UI call AddHostCmd to add baremetal host, it should switch to 
> AddBaremetalHostCmd

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1366) UI support for adding baremetal host

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-1366:


Affects Version/s: (was: 4.2.0)
   Future

> UI support for adding baremetal host
> 
>
> Key: CLOUDSTACK-1366
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1366
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: Future
>Reporter: frank zhang
>Assignee: Jessica Wang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz
>
>
> Current UI call AddHostCmd to add baremetal host, it should switch to 
> AddBaremetalHostCmd

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-4081) [DOC]Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4081:
-

I think it's only CloudPlatform. ACS has no install.sh, it's CloudPlatform 
installer

> [DOC]Fresh install of cloud platform failed with dependency errors on 
> centos5.5 OS
> --
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: shweta agarwal
>Priority: Critical
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1365) UI support for baremetal PXE server

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-1365.
-

Resolution: Fixed

> UI support for baremetal PXE server
> ---
>
> Key: CLOUDSTACK-1365
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1365
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: frank zhang
>Assignee: angeline shen
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - 
> Mozilla Firefox-1.png
>
>
> Baremetal PXE needs a page to add device
> the API is AddBaremetalKickStartPxeCmd
> please contact frank for details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-1364) UI support for baremetal DHCP server

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-1364.
-

Resolution: Fixed

> UI support for baremetal DHCP server
> 
>
> Key: CLOUDSTACK-1364
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1364
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: frank zhang
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - 
> Mozilla Firefox.png
>
>
> Baremetal DHCP needs a page to add device
> the API is AddBaremetalDhcpCmd
> please contact frank for details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1365) UI support for baremetal PXE server

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-1365:
-

no worry Jessica, I checked it looks like a server side bug

> UI support for baremetal PXE server
> ---
>
> Key: CLOUDSTACK-1365
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1365
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: frank zhang
>Assignee: angeline shen
>Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.log.gz, Screenshot-CloudPlatform™ - 
> Mozilla Firefox-1.png
>
>
> Baremetal PXE needs a page to add device
> the API is AddBaremetalKickStartPxeCmd
> please contact frank for details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-4426) [VMware] [upgrade] system VM not coming up after upgrade from 3.0.4 to 4.2

[frank zhang (JIRA)]

frank zhang created CLOUDSTACK-4426:
---

 Summary: [VMware] [upgrade] system VM not coming up after upgrade 
from 3.0.4 to 4.2
 Key: CLOUDSTACK-4426
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4426
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: VMware
Affects Versions: 4.2.1
Reporter: frank zhang
Priority: Critical
 Fix For: 4.2.1


did and upgrade on 3.0.4 patch1 to 4.2 . 
Having two advance zone 
1 with EXI 4.1 
second with xen 

After upgrade I destroyed system VM of Vmware zone . New system Vm failed to 
start . Hitting exception .. 


MS log snippet shows : 
2013-08-20 03:34:58,662 DEBUG [cloud.storage.VolumeManagerImpl] 
(consoleproxy-1:null) Checking if we need to prepare 1 volumes for 
VM[ConsoleProxy|v-41-VM] 
2013-08-20 03:34:58,677 DEBUG [storage.image.TemplateDataFactoryImpl] 
(consoleproxy-1:null) template 202 is already in store:6, type:Image 
2013-08-20 03:34:58,688 DEBUG [storage.image.TemplateDataFactoryImpl] 
(consoleproxy-1:null) template 202 is already in store:201, type:Primary 
2013-08-20 03:34:58,691 DEBUG [storage.volume.VolumeServiceImpl] 
(consoleproxy-1:null) Found template 202-2-d0b7f194-a096-3dd3-b9fa-7fb26ed627a7 
in storage pool 201 with VMTemplateStoragePool id: 11 
2013-08-20 03:34:58,706 DEBUG [storage.volume.VolumeServiceImpl] 
(consoleproxy-1:null) Acquire lock on VMTemplateStoragePool 11 with timeout 
3600 seconds 
2013-08-20 03:34:58,724 WARN [storage.resource.VmwareStorageProcessor] 
(DirectAgent-21:10.147.40.27) Exception: tar --no-same-owner -xf 
/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
 
java.io.IOException: Cannot run program "tar" (in directory 
"/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl/2/202"): 
java.io.IOException: error=13, Permission denied 
at java.lang.ProcessBuilder.start(ProcessBuilder.java:488) 
at com.cloud.utils.script.Script.execute(Script.java:183) 
at com.cloud.utils.script.Script.execute(Script.java:161) 
at 
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryToPrimary(VmwareStorageProcessor.java:147)
 
at 
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateToPrimaryStorage(VmwareStorageProcessor.java:222)
 
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
 
at 
com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:147)
 
at 
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
 
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:560)
 
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:679) 
Caused by: java.io.IOException: java.io.IOException: error=13, Permission 
denied 
at java.lang.UNIXProcess.(UNIXProcess.java:164) 
at java.lang.ProcessImpl.start(ProcessImpl.java:81) 
at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) 
... 17 more 
2013-08-20 03:34:58,726 ERROR [storage.resource.VmwareStorageProcessor] 
(DirectAgent-21:10.147.40.27) Unable to unpack snapshot OVA file at: 
/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
 
2013-08-20 03:34:58,727 ERROR [storage.resource.VmwareStorageProcessor] 
(DirectAgent-21:10.147.40.27) Unable to copy template to primary storage due to 
exception:Exception: java.lang.Exception 
Message: Unable to unpack snapshot OVA file at: 
/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
 

java.lang.Exception: Unable to unpack snapshot OVA file at: 
/var/lib/cloud/mnt/VM/6755849339011.2ddcc473/template/tmpl//2/202//5a1201b7-e458-32c9-aede-dbf9cf3e14d0.ova
 
at 
com.cloud.storage.resource.VmwareStorageProcessor.copyTemplateFromSecondaryTo

[jira] [Commented] (CLOUDSTACK-3765) [packaging][document] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

3.1. Upgrade from 4.0.x to 4.2.0
the upgrade instructions should be divided in two parts. mgmt server upgrade 
and kvm agent upgrade. upgrading cloud-agent is actually upgrading KVM agent 
running on host. Putting them together will confuse customers who don't use KVM

the same applies to upgrading xenserver and usage server. we should put them in 
dedicated chapter, now all stuff are in a single chapter which is quite 
confusing.

can we arrange them like this:

- Upgrade management server
  - 4.0 to 4.2
  - 2.2.x to 4.2

- Upgrade cloud agent
  - 4.0 to 4.2
  - 2.2.x to 4.2

- Upgrade usage server
  - 4.0 to 4.2
  - 2.2.x to 4.2

- Upgrade Xenserver host
  


> [packaging][document] unable to upgrade cp 4.2 build on centos5.5
> -
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Sudha Ponnaganti
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Apache_CloudStack-4.2.0-Release_Notes-en-US.pdf
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4370) [packaging]unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4370.
-

Resolution: Fixed

> [packaging]unable to upgrade cp 4.2 build on centos5.5
> --
>
> Key: CLOUDSTACK-4370
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4370
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Two advanced zone one xen and one vmware
> upgrade from 3.0.4 patch1 to 4.2 on centos 5.5
> build :
>   CloudPlatform-4.2-4.2-78-rhel5
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Blocker
> Fix For: 4.2.0
>
>
> upgrade from 3.0.4 patch1 to 4.2 on centos 5.5 failed with dependency missing 
> errors
> Steps :
> 1. Installed Management server and usage server of 3.0.4 patch 1 on centos5.5 
> machine
> 2. installed epel repo : rpm -Uvh 
> http://mirror.pnl.gov/epel/5/i386/epel-release-5-4.noarch.rpm
> 3 installed jsvc :rpm -Uvh 
> http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> 4. untar 4.2 build and used U option 
> Getting dependency error :
> Q) Quit
>  > U
> Updating the CloudPlatform and its dependencies...
> Loaded plugins: fastestmirror
> Determining fastest mirrors
>  * addons: centos.excellmedia.net
>  * base: centos.excellmedia.net
>  * epel: epel.mirror.net.in
>  * extras: centos.excellmedia.net
>  * jpackage-generic: ftp.heanet.ie
>  * jpackage-generic-updates: ftp.heanet.ie
>  * updates: centos.excellmedia.net
> addons
>| 1.9 kB   
>   00:00
> addons/primary_db 
>| 1.1 kB   
>   00:00
> base  
>| 1.1 kB   
>   00:00
> base/primary  
>| 1.2 MB   
>   00:05
> base  
>   
>   3641/3641
> cloud-temp
>|  951 B   
>   00:00
> epel  
>| 3.6 kB   
>   00:00
> epel/primary_db   
>| 3.8 MB   
>   00:06
> extras
>| 2.1 kB   
>   00:00
> extras/primary_db 
>| 188 kB   
>   00:01
> jpackage-generic  
>| 2.3 kB   
>   00:00
> jpackage-generic/primary_db   
>| 1.0 MB   
>   00:10
> jpackage-generic-updates  
>| 2.3 kB   
>   00:00
> jpackage-generic-updates/primary_db   
>|  12 kB   
>   00:00
> updates   
>| 1.9 kB   
>   00:00
> updates/primary_db
>| 602 kB   
>   00:02
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloudstack-agent.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated
> --> Processing Dependency: jna >= 3.2.4 for package: cloudstack-agent
> --> Processing Dependency: qemu-kvm for package: cloudstack-agent
> --> Processing Dependency: qemu-img for package: cloudstack-agent
> --> Processing Dep

[jira] [Assigned] (CLOUDSTACK-4370) [packaging]unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4370:
---

Assignee: Rayees Namathponnan  (was: frank zhang)

> [packaging]unable to upgrade cp 4.2 build on centos5.5
> --
>
> Key: CLOUDSTACK-4370
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4370
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Two advanced zone one xen and one vmware
> upgrade from 3.0.4 patch1 to 4.2 on centos 5.5
> build :
>   CloudPlatform-4.2-4.2-78-rhel5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> upgrade from 3.0.4 patch1 to 4.2 on centos 5.5 failed with dependency missing 
> errors
> Steps :
> 1. Installed Management server and usage server of 3.0.4 patch 1 on centos5.5 
> machine
> 2. installed epel repo : rpm -Uvh 
> http://mirror.pnl.gov/epel/5/i386/epel-release-5-4.noarch.rpm
> 3 installed jsvc :rpm -Uvh 
> http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> 4. untar 4.2 build and used U option 
> Getting dependency error :
> Q) Quit
>  > U
> Updating the CloudPlatform and its dependencies...
> Loaded plugins: fastestmirror
> Determining fastest mirrors
>  * addons: centos.excellmedia.net
>  * base: centos.excellmedia.net
>  * epel: epel.mirror.net.in
>  * extras: centos.excellmedia.net
>  * jpackage-generic: ftp.heanet.ie
>  * jpackage-generic-updates: ftp.heanet.ie
>  * updates: centos.excellmedia.net
> addons
>| 1.9 kB   
>   00:00
> addons/primary_db 
>| 1.1 kB   
>   00:00
> base  
>| 1.1 kB   
>   00:00
> base/primary  
>| 1.2 MB   
>   00:05
> base  
>   
>   3641/3641
> cloud-temp
>|  951 B   
>   00:00
> epel  
>| 3.6 kB   
>   00:00
> epel/primary_db   
>| 3.8 MB   
>   00:06
> extras
>| 2.1 kB   
>   00:00
> extras/primary_db 
>| 188 kB   
>   00:01
> jpackage-generic  
>| 2.3 kB   
>   00:00
> jpackage-generic/primary_db   
>| 1.0 MB   
>   00:10
> jpackage-generic-updates  
>| 2.3 kB   
>   00:00
> jpackage-generic-updates/primary_db   
>|  12 kB   
>   00:00
> updates   
>| 1.9 kB   
>   00:00
> updates/primary_db
>| 602 kB   
>   00:02
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloudstack-agent.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated
> --> Processing Dependency: jna >= 3.2.4 for package: cloudstack-agent
> --> Processing Dependency: qemu-kvm for package: cloudstack-agent
> --> Processing Dependency: qemu-img for pa

[jira] [Assigned] (CLOUDSTACK-4370) [packaging]unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4370:
---

Assignee: frank zhang  (was: Rayees Namathponnan)

> [packaging]unable to upgrade cp 4.2 build on centos5.5
> --
>
> Key: CLOUDSTACK-4370
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4370
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Two advanced zone one xen and one vmware
> upgrade from 3.0.4 patch1 to 4.2 on centos 5.5
> build :
>   CloudPlatform-4.2-4.2-78-rhel5
>Reporter: shweta agarwal
>Assignee: frank zhang
>Priority: Blocker
> Fix For: 4.2.0
>
>
> upgrade from 3.0.4 patch1 to 4.2 on centos 5.5 failed with dependency missing 
> errors
> Steps :
> 1. Installed Management server and usage server of 3.0.4 patch 1 on centos5.5 
> machine
> 2. installed epel repo : rpm -Uvh 
> http://mirror.pnl.gov/epel/5/i386/epel-release-5-4.noarch.rpm
> 3 installed jsvc :rpm -Uvh 
> http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> 4. untar 4.2 build and used U option 
> Getting dependency error :
> Q) Quit
>  > U
> Updating the CloudPlatform and its dependencies...
> Loaded plugins: fastestmirror
> Determining fastest mirrors
>  * addons: centos.excellmedia.net
>  * base: centos.excellmedia.net
>  * epel: epel.mirror.net.in
>  * extras: centos.excellmedia.net
>  * jpackage-generic: ftp.heanet.ie
>  * jpackage-generic-updates: ftp.heanet.ie
>  * updates: centos.excellmedia.net
> addons
>| 1.9 kB   
>   00:00
> addons/primary_db 
>| 1.1 kB   
>   00:00
> base  
>| 1.1 kB   
>   00:00
> base/primary  
>| 1.2 MB   
>   00:05
> base  
>   
>   3641/3641
> cloud-temp
>|  951 B   
>   00:00
> epel  
>| 3.6 kB   
>   00:00
> epel/primary_db   
>| 3.8 MB   
>   00:06
> extras
>| 2.1 kB   
>   00:00
> extras/primary_db 
>| 188 kB   
>   00:01
> jpackage-generic  
>| 2.3 kB   
>   00:00
> jpackage-generic/primary_db   
>| 1.0 MB   
>   00:10
> jpackage-generic-updates  
>| 2.3 kB   
>   00:00
> jpackage-generic-updates/primary_db   
>|  12 kB   
>   00:00
> updates   
>| 1.9 kB   
>   00:00
> updates/primary_db
>| 602 kB   
>   00:02
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloudstack-agent.x86_64 0:4.2.0-SNAPSHOT.el5 set to be updated
> --> Processing Dependency: jna >= 3.2.4 for package: cloudstack-agent
> --> Processing Dependency: qemu-kvm for package: cloudstack-agent
> --> Processing Dependency: qemu-img for package: c

[jira] [Resolved] (CLOUDSTACK-4081) Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4081.
-

Resolution: Fixed

we fixed this by bringing all old CloudStack 2.x dependencies back.
now the installation step simplifies to:
1. setup EPEL repo:
rpm -Uvh http://mirror.pnl.gov/epel/5/i386/epel-release-5-4.noarch.rpm 

2. use 'M' option

note if you want to install usage server as well you have to install jsvc by

 rpm -Uvh 
http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
 

> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-40) New Image based provisioning method for Baremetal

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-40.
---

Resolution: Won't Fix

> New Image based provisioning method for Baremetal
> -
>
> Key: CLOUDSTACK-40
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-40
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: pre-4.0.0
>Reporter: Rohit Yadav
>Assignee: frank zhang
>
> Get rid of PING, implement a solution that:
> - takes/restores image on host: Use Partimage or DD to restore a disk image 
> to baremetal host and take an image from host and saving as CloudStack 
> template
> - a way to notify state of provisioning. Especially when provisioning is done.
> - have a well organized API and doc
> - easy to setup. 
> Release Planning:
> Dev List Discussion:  http://markmail.org/thread/lpfptu7wv22pexlk
> Functional Spec:  
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Baremetal
> Feature Branch: Unknown

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-40) New Image based provisioning method for Baremetal

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-40:
---

no plan to support his feature, mark is as won't fix

> New Image based provisioning method for Baremetal
> -
>
> Key: CLOUDSTACK-40
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-40
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: pre-4.0.0
>Reporter: Rohit Yadav
>Assignee: frank zhang
>
> Get rid of PING, implement a solution that:
> - takes/restores image on host: Use Partimage or DD to restore a disk image 
> to baremetal host and take an image from host and saving as CloudStack 
> template
> - a way to notify state of provisioning. Especially when provisioning is done.
> - have a well organized API and doc
> - easy to setup. 
> Release Planning:
> Dev List Discussion:  http://markmail.org/thread/lpfptu7wv22pexlk
> Functional Spec:  
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Baremetal
> Feature Branch: Unknown

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-4081) Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4081:
-

I got the cause, it's headache. The problem is jppackage repo has some package 
having the same name with package in centos default repo but provides different 
functionality. 
the package in centos default repo is required by gcj, however during 
installation yum installer wrongly resolves dependency to package in jppackage 
repo which leads a failure because it cannot provide dependency gcj requires.
this issue happens in a random manner which depends on the order yum installer 
searches dependency in repos, if centos default repo is queried before 
jppackage repo, it won't happen.

I am seeking a solution

> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2064) The Vmware template dosent have permissions to be copied from secondary storage.

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-2064:
-

emm. this issue may happen in following criteria:
1. user uses 'root' to run cloud-install-sys-tmplt that seeds secondary storage 
with 'root' privilege
2. CloudStack is running as user 'cloud'
3. NFS4 somehow perform a strictly check on file privilege that stops use 
'cloud' from accessing secondary storage template

I will seek a fix in cloud-install-sys-tmplt

> The Vmware template dosent have permissions to be copied from secondary 
> storage.
> 
>
> Key: CLOUDSTACK-2064
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2064
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Kiran Koneti
>Assignee: Hugo Trippaers
>Priority: Critical
> Fix For: 4.1.0, 4.2.0
>
>
> 0When the VMware template is seeded to the secondary storage and while trying 
> to create the system Vm's there is a error message saying no permission to 
> tar the routing-8.ova 
> The error message is as below.
> "2013-04-17 11:33:18,074 ERROR [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-4:10.102.192.18) Unable to execute PrimaryStorageDownloadCommand 
> due to exception
> java.io.FileNotFoundException: 
> /var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/tmpl/1/8/systemvmtemplate-2013-04-15-master-vmware.ovf
>  (Permission denied)
>  
> [root@rhel63 management]# ll /var/cloudstack/mnt/VM/
> total 20
> drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:34 73143235720.154199bd
> drwxrwxrwx. 5 root  bin   4096 Apr 17 11:35 73143235720.4a5f0cef
> drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:29 73143235720.4c8848c4
> drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:54 73143235720.525f3d5f
> drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:44 73143235720.526d73ac
> [root@rhel63 management]# ll /var/cloudstack/mnt/VM/73143235720.4a5f0cef/
> drwxrwxr-x. 2 cloud cloud 4096 Apr 17 11:35 systemvm
> drwxr-xr-x. 3 root  root  4096 Apr 17 09:41 template
> [root@rhel63 management]# ll 
> /var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/
> drwxr-xr-x. 3 root root 4096 Apr 17 09:41 tmpl
> -rw-r--r--. 1 root root 260070912 Apr 17 09:56 
> 56058ae3-12ea-4bbc-838c-f2e25ceba314.ova
> -rw---. 1 root root 260057600 Apr 16 09:49 
> systemvmtemplate-2013-04-15-master-vmware-disk1.vmdk
> -rw---. 1 root root 12178 Apr 16 09:49 
> systemvmtemplate-2013-04-15-master-vmware.ovf
> -rw-r--r--. 1 root root   283 Apr 17 10:00 template.properties"
> There is a workaround for the same.
> After seeding the template if we change the permissions of the template in 
> the secondary storage (i.e give read/write permission) then the template is 
> seeded properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4081) Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4081.
-

Resolution: Fixed

> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-4081) Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4081:
-

have you setup epel repo as well? here is full instructions to install ACS 
build on centos5.x

1. setup EPEL repo:
rpm -Uvh http://mirror.pnl.gov/epel/5/i386/epel-release-5-4.noarch.rpm

2. install jppackage repo:
# cd /etc/yum.repos.d/
# wget http://jpackage.org/jpackage50.repo

3. do install

this works in SC lab, I have tested in different machines.
if you still encounter any issues. please send me ip/credentials by mail so I 
can log in to debug 

> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Critical
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2064) The Vmware template dosent have permissions to be copied from secondary storage.

[frank zhang (JIRA)]

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

frank zhang updated CLOUDSTACK-2064:


Description: 
0When the VMware template is seeded to the secondary storage and while trying 
to create the system Vm's there is a error message saying no permission to tar 
the routing-8.ova 
The error message is as below.

"2013-04-17 11:33:18,074 ERROR [vmware.manager.VmwareStorageManagerImpl] 
(DirectAgent-4:10.102.192.18) Unable to execute PrimaryStorageDownloadCommand 
due to exception
java.io.FileNotFoundException: 
/var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/tmpl/1/8/systemvmtemplate-2013-04-15-master-vmware.ovf
 (Permission denied)
 
[root@rhel63 management]# ll /var/cloudstack/mnt/VM/
total 20
drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:34 73143235720.154199bd
drwxrwxrwx. 5 root  bin   4096 Apr 17 11:35 73143235720.4a5f0cef
drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:29 73143235720.4c8848c4
drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:54 73143235720.525f3d5f
drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:44 73143235720.526d73ac
[root@rhel63 management]# ll /var/cloudstack/mnt/VM/73143235720.4a5f0cef/
drwxrwxr-x. 2 cloud cloud 4096 Apr 17 11:35 systemvm
drwxr-xr-x. 3 root  root  4096 Apr 17 09:41 template
[root@rhel63 management]# ll 
/var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/
drwxr-xr-x. 3 root root 4096 Apr 17 09:41 tmpl
-rw-r--r--. 1 root root 260070912 Apr 17 09:56 
56058ae3-12ea-4bbc-838c-f2e25ceba314.ova
-rw---. 1 root root 260057600 Apr 16 09:49 
systemvmtemplate-2013-04-15-master-vmware-disk1.vmdk
-rw---. 1 root root 12178 Apr 16 09:49 
systemvmtemplate-2013-04-15-master-vmware.ovf
-rw-r--r--. 1 root root   283 Apr 17 10:00 template.properties"

There is a workaround for the same.

After seeding the template if we change the permissions of the template in the 
secondary storage (i.e give read/write permission) then the template is seeded 
properly.

  was:
When the VMware template is seeded to the secondary storage and while trying to 
create the system Vm's there is a error message saying no permission to tar the 
routing-8.ova 
The error message is as below.

"2013-04-17 11:33:18,074 ERROR [vmware.manager.VmwareStorageManagerImpl] 
(DirectAgent-4:10.102.192.18) Unable to execute PrimaryStorageDownloadCommand 
due to exception
java.io.FileNotFoundException: 
/var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/tmpl/1/8/systemvmtemplate-2013-04-15-master-vmware.ovf
 (Permission denied)
 
[root@rhel63 management]# ll /var/cloudstack/mnt/VM/
total 20
drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:34 73143235720.154199bd
drwxrwxrwx. 5 root  bin   4096 Apr 17 11:35 73143235720.4a5f0cef
drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:29 73143235720.4c8848c4
drwxrwxrwx. 2 cloud cloud 4096 Apr 16 11:54 73143235720.525f3d5f
drwxrwxrwx. 2 cloud cloud 4096 Apr 17 10:44 73143235720.526d73ac
[root@rhel63 management]# ll /var/cloudstack/mnt/VM/73143235720.4a5f0cef/
drwxrwxr-x. 2 cloud cloud 4096 Apr 17 11:35 systemvm
drwxr-xr-x. 3 root  root  4096 Apr 17 09:41 template
[root@rhel63 management]# ll 
/var/cloudstack/mnt/VM/73143235720.4a5f0cef/template/
drwxr-xr-x. 3 root root 4096 Apr 17 09:41 tmpl
-rw-r--r--. 1 root root 260070912 Apr 17 09:56 
56058ae3-12ea-4bbc-838c-f2e25ceba314.ova
-rw---. 1 root root 260057600 Apr 16 09:49 
systemvmtemplate-2013-04-15-master-vmware-disk1.vmdk
-rw---. 1 root root 12178 Apr 16 09:49 
systemvmtemplate-2013-04-15-master-vmware.ovf
-rw-r--r--. 1 root root   283 Apr 17 10:00 template.properties"

There is a workaround for the same.

After seeding the template if we change the permissions of the template in the 
secondary storage (i.e give read/write permission) then the template is seeded 
properly.


> The Vmware template dosent have permissions to be copied from secondary 
> storage.
> 
>
> Key: CLOUDSTACK-2064
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2064
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Kiran Koneti
>Assignee: Hugo Trippaers
>Priority: Critical
> Fix For: 4.1.0, 4.2.0
>
>
> 0When the VMware template is seeded to the secondary storage and while trying 
> to create the system Vm's there is a error message saying no permission to 
> tar the routing-8.ova 
> The error message is as below.
> "2013-04-17 11:33:18,074 ERROR [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-4:10.102.192.18) Unable to execute PrimaryStorageDownloadCommand 
> due to exception
> java.io.FileNotFoundException: 
> /var/clou

[jira] [Resolved] (CLOUDSTACK-3765) [packaging] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-3765.
-

Resolution: Fixed

unfortunately yum installer has a bug in centos5.x, that's the reason you saw 
rpmlib is required to install jsvc. I have rebuilt a new package at 
http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm

do:
1. rpm -Uvh 
http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
2. upgrade usage server

> [packaging] unable to upgrade cp 4.2 build on centos5.5
> ---
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3765) [packaging] unable to upgrade cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

OK. now it makes much sense to me. as you were upgrading usage server, it does 
require jvsc. 

> [packaging] unable to upgrade cp 4.2 build on centos5.5
> ---
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4149) [upgrade][2.2.13 -> 2.2.14 -> 4.2][KVM] When we try to upgrade the KVM agent from 2.2.14 to 4.2 using the "U" option in install.sh script, management server also ge

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4149.
-

Resolution: Fixed

> [upgrade][2.2.13 -> 2.2.14 -> 4.2][KVM] When we try to upgrade the KVM agent 
> from 2.2.14 to 4.2 using the "U" option in install.sh script, management 
> server also gets installed!
> -
>
> Key: CLOUDSTACK-4149
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4149
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging, Upgrade
>Affects Versions: 4.2.0
> Environment: upgrade from 2.2.13 (rhel 6.1 build) -> 2.2.14 (rhel 6.1 
> build) -> 4.2 (rhel 6.2 build) 
> MS : CentOS 6.1 
> KVM : CentOS 6.1
>Reporter: Abhinav Roy
>Assignee: frank zhang
>Priority: Blocker
> Fix For: 4.2.0
>
>
> 1. Deploy a CS 2.2.13 advanced zone setup.
> 2. Do some operations and upgrade to 2.2.14
> 3. Now when we try to upgrade it from 2.2.14 to 4.2 using the "U" option in 
> install.sh script, it installs the management server also.
> [root@centos61-band28 CloudPlatform-4.2-4.2-104-rhel6.2]# ./install.sh
> Setting up the temporary repository...
> Cleaning Yum cache...
> Loaded plugins: fastestmirror
> Cleaning repos: cloud-temp rhel
> 2 metadata files removed
> Welcome to the CloudPlatform Installer.  What would you like to do?
> NOTE:   For installing KVM agent, please setup 
> EPEL yum repo first;
> For installing CloudPlatform on RHEL6.x, please setup 
> distribution yum repo either from ISO or from your registeration account.
> M) Install the Management Server
> A) Install the Agent
> B) Install BareMetal Agent
> S) Install the Usage Monitor
> D) Install the database server (from distribution's repo)
> U) Upgrade the CloudPlatform packages installed on this computer
> R) Stop any running CloudPlatform services and remove the CloudPlatform 
> packages from this computer
> L) Install the MySQL 5.1.58 (only for CentOS5.x, Rhel6.x naturally has 
> higher version MySql)
> Q) Quit
>  > u
> Updating the CloudPlatform and its dependencies...
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
> cloud-temp
>   
> | 1.3 kB 00:00 ...
> rhel  
>   
> | 4.0 kB 00:00 ...
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloud-agent.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-agent-libs.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-core.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-daemonize.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-deps.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-python.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-utils.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloudstack-agent.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
> --> Processing Dependency: jakarta-commons-daemon for package: 
> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: ipset for package: 
> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64
> ---> Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
> ---> Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el6 will be 
> obsoleting
> --> Processing Dependency: cloudstack-awsapi = 4.2.0 for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: ws-commons-util for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: tomcat6 for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: mysql-connector-java for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: mkisofs for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: ipmitool for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: MySQL-python for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Running transaction check
> ---> Package MySQL-python.x86_64 0:1.2.3-0.3.c1.1.el6 will be installed
> ---> Package cloudstack-awsapi.x86_64 0:4.2.0-SNAPSHOT.el6 will be installed
> ---> Package geniso

[jira] [Commented] (CLOUDSTACK-3765) [packaging] unable to install cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

shwta, can you clarify the steps you were doing? were you using 'M' option to 
install mgmt server or using 'A' to install cloud-agent?
first of all, for rhel5.5 you can only install mgmt server which means using 
option 'M'. jakarta-commons-daemon-jsvc is a dependency only for 
cloudstack-agent and cloudstack-usage, if you just install 
cloudstack-management using option 'M', you should not encounter any issue. I 
have successfully installed cloudstack-management on centos5.3 with 
insturctions I provided before. (I tried it again just now it still succeeds)

if you do use 'M' option, please provide me information following below steps:
1. having a fresh centos5.5 vm
1. untar latest package
2. run install.sh then click 'M'
3. yum installer will then calculate dependencies and show them in a text table 
on console. paste that table to this ticket. it's event better if you can get 
me all log after you click 'M' option

> [packaging] unable to install cp 4.2 build on centos5.5
> ---
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3765) [packaging] unable to install cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-3765.
-

Resolution: Cannot Reproduce

> [packaging] unable to install cp 4.2 build on centos5.5
> ---
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4090) [Upgrade] System VM's are failed to start on a new zone(VMWARE Nexus Zone) which is created after upgrade

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4090.
-

Resolution: Fixed

it's a DB upgrade issue.
in commit 8652e5f8 we changed mount point of VMWare secondary storage to 
/var/cloudstack/mnt that is in new home directory of user 'cloudstack'. 
however, DB upgrade schema doesn't update corresponding entry in Configuration 
table which is still pointing to old place /var/lib/cloud/mnt that has been 
returned to user root.



> [Upgrade] System VM's are failed to start on a new zone(VMWARE Nexus Zone) 
> which is created after upgrade 
> --
>
> Key: CLOUDSTACK-4090
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4090
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log, Bforeupgraedecloud-backup.dmp, 
> postupgradecloud-backup.dmp
>
>
> Steps:
> 1. Upgraded from 305 Patch A to 4.2 with Xenserver Zone
> 2. Enabled Nexus global config value 
> 3. Configure one more Adv zone with VMWARE cluster with Nexus 1000v Switch 
> enabled 
> 4. Seeded secondary storage with new 4.2 vMWARE template (vh7)
> Physical network 1 : 
> Mgmt Traffic label name  - vSwitch0,,vmwaresvs 
> Physical network 1 : 
> Public & Guest Traffic label name  - nexuspp91,,nexusdvs
> Observation:System VM's are failed to start on a new zone(VMWARE Nexus Zone) 
> which is created after upgrade 
> After upgrade I have enabled Nexus vSwtich and configured zone with Nexus 
> cluster.  Now system VM’s are coming up now : I I am using vh7 template) - 
> 2013-08-05 21:01:52,084 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-08-05 21:01:52,091 DEBUG [storage.motion.AncientDataMotionStrategy] 
> (consoleproxy-1:null) copyAsync inspecting src type TEMPLATE copyAsync 
> inspecting dest type TEMPLATE
> 2013-08-05 21:01:52,174 DEBUG [agent.transport.Request] (consoleproxy-1:null) 
> Seq 8-268894239: Sending  { Cmd , MgmtId: 7674049379768, via: 8, Ver: v1, 
> Flags: 100011, 
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/8/","origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/sailaja/vmwaress1/","_role":"Image"}},"name":"routing-8","hypervisorType":"VMware"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"55e6d095-7e22-3f4a-b533-874a9fede8df","id":202,"poolType":"NetworkFilesystem","host":"10.102.192.100","path":"/cpg_vol/sailaja/vmwareps1","port":2049}},"name":"routing-8","hypervisorType":"VMware"}},"executeInSequence":false,"wait":10800}}]
>  }
> 2013-08-05 21:01:52,175 DEBUG [agent.transport.Request] (consoleproxy-1:null) 
> Seq 8-268894239: Executing:  { Cmd , MgmtId: 7674049379768, via: 8, Ver: v1, 
> Flags: 100011, 
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/8/","origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/sailaja/vmwaress1/","_role":"Image"}},"name":"routing-8","hypervisorType":"VMware"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"55e6d095-7e22-3f4a-b533-874a9fede8df","id":202,"poolType":"NetworkFilesystem","host":"10.102.192.1

[jira] [Assigned] (CLOUDSTACK-4090) [Upgrade] System VM's are failed to start on a new zone(VMWARE Nexus Zone) which is created after upgrade

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4090:
---

Assignee: frank zhang  (was: Sateesh Chodapuneedi)

> [Upgrade] System VM's are failed to start on a new zone(VMWARE Nexus Zone) 
> which is created after upgrade 
> --
>
> Key: CLOUDSTACK-4090
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4090
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sailaja Mada
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: apilog.log, Bforeupgraedecloud-backup.dmp, 
> postupgradecloud-backup.dmp
>
>
> Steps:
> 1. Upgraded from 305 Patch A to 4.2 with Xenserver Zone
> 2. Enabled Nexus global config value 
> 3. Configure one more Adv zone with VMWARE cluster with Nexus 1000v Switch 
> enabled 
> 4. Seeded secondary storage with new 4.2 vMWARE template (vh7)
> Physical network 1 : 
> Mgmt Traffic label name  - vSwitch0,,vmwaresvs 
> Physical network 1 : 
> Public & Guest Traffic label name  - nexuspp91,,nexusdvs
> Observation:System VM's are failed to start on a new zone(VMWARE Nexus Zone) 
> which is created after upgrade 
> After upgrade I have enabled Nexus vSwtich and configured zone with Nexus 
> cluster.  Now system VM’s are coming up now : I I am using vh7 template) - 
> 2013-08-05 21:01:52,084 DEBUG 
> [network.router.VirtualNetworkApplianceManagerImpl] 
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-08-05 21:01:52,091 DEBUG [storage.motion.AncientDataMotionStrategy] 
> (consoleproxy-1:null) copyAsync inspecting src type TEMPLATE copyAsync 
> inspecting dest type TEMPLATE
> 2013-08-05 21:01:52,174 DEBUG [agent.transport.Request] (consoleproxy-1:null) 
> Seq 8-268894239: Sending  { Cmd , MgmtId: 7674049379768, via: 8, Ver: v1, 
> Flags: 100011, 
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/8/","origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/sailaja/vmwaress1/","_role":"Image"}},"name":"routing-8","hypervisorType":"VMware"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"55e6d095-7e22-3f4a-b533-874a9fede8df","id":202,"poolType":"NetworkFilesystem","host":"10.102.192.100","path":"/cpg_vol/sailaja/vmwareps1","port":2049}},"name":"routing-8","hypervisorType":"VMware"}},"executeInSequence":false,"wait":10800}}]
>  }
> 2013-08-05 21:01:52,175 DEBUG [agent.transport.Request] (consoleproxy-1:null) 
> Seq 8-268894239: Executing:  { Cmd , MgmtId: 7674049379768, via: 8, Ver: v1, 
> Flags: 100011, 
> [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/1/8/","origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.102.192.100/cpg_vol/sailaja/vmwaress1/","_role":"Image"}},"name":"routing-8","hypervisorType":"VMware"}},"destTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"origUrl":"http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova","uuid":"8","id":8,"format":"OVA","accountId":1,"checksum":"7137e453f950079ea2ba6feaafd939e8","hvm":false,"displayText":"SystemVM
>  Template 
> (vSphere)","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"55e6d095-7e22-3f4a-b533-874a9fede8df","id":202,"poolType":"NetworkFilesystem","host":"10.102.192.100","path":"/cpg_vol/sailaja/vmwareps1","port":2049}},"name":"routing-8","hypervisorType":"VMware"}},"executeInSequence":false,"wait":10800}}]
>  }
> 2013-08-05 21:01:52,186 DEBUG [agent.manager.DirectAgentAttache] 
> (DirectAgent-204:null) Seq 8-268894239: Executing request
> 2013-08-05 21:01:52,318 DEBUG 
> [network.router.Vir

[jira] [Commented] (CLOUDSTACK-4149) [upgrade][2.2.13 -> 2.2.14 -> 4.2][KVM] When we try to upgrade the KVM agent from 2.2.14 to 4.2 using the "U" option in install.sh script, management server also g

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4149:
-

The issue is caused by rpm reorganization in ACS. ACS uses 
cloudstack-management package to make cloud-agent as obsolete, this causes 
cloudstack-management to be unnecessarily installed during agent upgrade


> [upgrade][2.2.13 -> 2.2.14 -> 4.2][KVM] When we try to upgrade the KVM agent 
> from 2.2.14 to 4.2 using the "U" option in install.sh script, management 
> server also gets installed!
> -
>
> Key: CLOUDSTACK-4149
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4149
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging, Upgrade
>Affects Versions: 4.2.0
> Environment: upgrade from 2.2.13 (rhel 6.1 build) -> 2.2.14 (rhel 6.1 
> build) -> 4.2 (rhel 6.2 build) 
> MS : CentOS 6.1 
> KVM : CentOS 6.1
>Reporter: Abhinav Roy
>Assignee: frank zhang
>Priority: Blocker
> Fix For: 4.2.0
>
>
> 1. Deploy a CS 2.2.13 advanced zone setup.
> 2. Do some operations and upgrade to 2.2.14
> 3. Now when we try to upgrade it from 2.2.14 to 4.2 using the "U" option in 
> install.sh script, it installs the management server also.
> [root@centos61-band28 CloudPlatform-4.2-4.2-104-rhel6.2]# ./install.sh
> Setting up the temporary repository...
> Cleaning Yum cache...
> Loaded plugins: fastestmirror
> Cleaning repos: cloud-temp rhel
> 2 metadata files removed
> Welcome to the CloudPlatform Installer.  What would you like to do?
> NOTE:   For installing KVM agent, please setup 
> EPEL yum repo first;
> For installing CloudPlatform on RHEL6.x, please setup 
> distribution yum repo either from ISO or from your registeration account.
> M) Install the Management Server
> A) Install the Agent
> B) Install BareMetal Agent
> S) Install the Usage Monitor
> D) Install the database server (from distribution's repo)
> U) Upgrade the CloudPlatform packages installed on this computer
> R) Stop any running CloudPlatform services and remove the CloudPlatform 
> packages from this computer
> L) Install the MySQL 5.1.58 (only for CentOS5.x, Rhel6.x naturally has 
> higher version MySql)
> Q) Quit
>  > u
> Updating the CloudPlatform and its dependencies...
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
> cloud-temp
>   
> | 1.3 kB 00:00 ...
> rhel  
>   
> | 4.0 kB 00:00 ...
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> ---> Package cloud-agent.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-agent-libs.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-core.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-daemonize.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-deps.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-python.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloud-utils.x86_64 0:2.2.14-1.el6 will be obsoleted
> ---> Package cloudstack-agent.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
> --> Processing Dependency: jakarta-commons-daemon for package: 
> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: ipset for package: 
> cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64
> ---> Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
> ---> Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el6 will be 
> obsoleting
> --> Processing Dependency: cloudstack-awsapi = 4.2.0 for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: ws-commons-util for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: tomcat6 for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: mysql-connector-java for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: mkisofs for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: ipmitool for package: 
> cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
> --> Processing Dependency: MySQL-python for package: 
>

[jira] [Resolved] (CLOUDSTACK-4224) UCS:UI: Delete UCS returns unknown API

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4224.
-

Resolution: Fixed

> UCS:UI: Delete UCS returns unknown API
> --
>
> Key: CLOUDSTACK-4224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS, UI
>Affects Versions: 4.2.0
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Attachments: delete UCS.jpeg
>
>
> Please refer to screen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-4224) UCS:UI: Delete UCS returns unknown API

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4224:
---

Assignee: frank zhang

> UCS:UI: Delete UCS returns unknown API
> --
>
> Key: CLOUDSTACK-4224
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4224
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS, UI
>Affects Versions: 4.2.0
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Attachments: delete UCS.jpeg
>
>
> Please refer to screen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3833) 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the Upgraded Setup - Tables "baremetal_dhcp_devices" and "baremetal_pxe_devices"

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-3833.
-

Resolution: Fixed

> 3.0.6 to ASF 4.2 Upgrade: "cloud" Database Schema Inconsistencies on the 
> Upgraded Setup - Tables "baremetal_dhcp_devices" and "baremetal_pxe_devices"
> -
>
> Key: CLOUDSTACK-3833
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3833
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Upgrade
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
>
> Table 1: baremetal_dhcp_devices
> On ASF 4.2 Setup:
>  `nsp_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `pod_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `device_type` varchar(255) DEFAULT NULL,
>  `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `host_id` bigint(20) UNSIGNED DEFAULT NULL,
> On the 4.2 Upgraded Setup:
>  `nsp_id` bigint(20) UNSIGNED NOT NULL,
>  `pod_id` bigint(20) UNSIGNED NOT NULL,
>  `device_type` varchar(255) NOT NULL,
>  `physical_network_id` bigint(20) UNSIGNED NOT NULL,
>  `host_id` bigint(20) UNSIGNED NOT NULL,
> Table 2: baremetal_pxe_devices
> On ASF 4.2 Setup:
>  `nsp_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `device_type` varchar(255) DEFAULT NULL,
>  `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `host_id` bigint(20) UNSIGNED DEFAULT NULL,
> On the 4.2 Upgraded Setup:
>  `nsp_id` bigint(20) UNSIGNED NOT NULL,
>  `device_type` varchar(255) NOT NULL,
>  `physical_network_id` bigint(20) UNSIGNED NOT NULL,
>  `host_id` bigint(20) UNSIGNED NOT NULL,

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3612) 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded Setup

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-3612.
-

Resolution: Fixed

> 3.0.6 to ASF 4.2 Upgrade: Database Schema Inconsistencies on the Upgraded 
> Setup
> ---
>
> Key: CLOUDSTACK-3612
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3612
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Upgrade
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.0
>
>
> Table 1: baremetal_dhcp_devices
> On ASF 4.2 Setup:
>  `nsp_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `pod_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `device_type` varchar(255) DEFAULT NULL,
>  `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `host_id` bigint(20) UNSIGNED DEFAULT NULL,
> On the 4.2 Upgraded Setup: 
>  `nsp_id` bigint(20) UNSIGNED NOT NULL,
>  `pod_id` bigint(20) UNSIGNED NOT NULL,
>  `device_type` varchar(255) NOT NULL,
>  `physical_network_id` bigint(20) UNSIGNED NOT NULL,
>  `host_id` bigint(20) UNSIGNED NOT NULL,
> Table 2: baremetal_pxe_devices
> On ASF 4.2 Setup:
>  `nsp_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `device_type` varchar(255) DEFAULT NULL,
>  `physical_network_id` bigint(20) UNSIGNED DEFAULT NULL,
>  `host_id` bigint(20) UNSIGNED DEFAULT NULL,
> On the 4.2 Upgraded Setup:
>  `nsp_id` bigint(20) UNSIGNED NOT NULL,
>  `device_type` varchar(255) NOT NULL,
>  `physical_network_id` bigint(20) UNSIGNED NOT NULL,
>  `host_id` bigint(20) UNSIGNED NOT NULL,
> Table 3: netscaler_pod_ref
> On ASF 4.2 Setup:
> Present on the Setup
> Missing on the Upgraded Setup.
> Table 4: nicira_nvp_nic_map
> On ASF 4.2 Setup:
> Constraint:
> ALTER TABLE `cloud`.`nicira_nvp_nic_map` ADD CONSTRAINT 
> `fk_nicira_nvp_nic_map__nic`
>  FOREIGN KEY ( `nic` ) REFERENCES `nics` ( `uuid` ) ON DELETE CASCADE;
> On the 4.2 Upgraded Setup:
> No such constraint
> Table 5: router_network_ref
> On ASF 4.2 Setup:
> Constraint:
> ALTER TABLE `cloud`.`router_network_ref` ADD CONSTRAINT 
> `fk_router_network_ref__router_id`
>  FOREIGN KEY ( `router_id` ) REFERENCES `domain_router` ( `id` ) ON DELETE 
> CASCADE;
> On the 4.2 Upgraded Setup:
> No such constraint
> Table 6: sync_queue
> On ASF 4.2 Setup:
>   `queue_size` smallint(6) NOT NULL DEFAULT '0',
>  `queue_size_limit` smallint(6) NOT NULL DEFAULT '1',
> On the 4.2 Upgraded Setup: 
>  `queue_size` smallint(6) DEFAULT '0',
>  `queue_size_limit` smallint(6) DEFAULT '1',
> Table 7: usage_event
> On ASF 4.2 Setup:
> no virtual_size column
> On the 4.2 Upgraded Setup: 
>  `virtual_size` bigint(20) UNSIGNED DEFAULT NULL,
> Table 8: volumes
> On ASF 4.2 Setup:
> no iso_id column
> On the 4.2 Upgraded Setup: 
>  `iso_id` bigint(20) UNSIGNED DEFAULT NULL,

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2534) Packaging puts SSH private keys as public readable on management server

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-2534:
-

This is invalid bug. 
/usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud is here for 
historically reason but we never use it to login to SSVM/VR.
the correct key is at /var/cloudstack/management/.ssh/id_rsa  which is home 
directory of user cloud.
let's remove the /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud 
at next release as it's quite confusing.

> Packaging puts SSH private keys as public readable on management server
> ---
>
> Key: CLOUDSTACK-2534
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2534
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Girish Shilamkar
>Assignee: Rayees Namathponnan
>Priority: Critical
>  Labels: security
> Fix For: 4.2.0
>
>
> SSH public key is group readable which is security threat.
>  ls -la /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud
> -rw-r--r--. 1 root root 1670 May 15 22:54 
> /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2534) Packaging puts SSH private keys as public readable on management server

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-2534.
-

Resolution: Invalid

> Packaging puts SSH private keys as public readable on management server
> ---
>
> Key: CLOUDSTACK-2534
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2534
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Girish Shilamkar
>Assignee: Rayees Namathponnan
>Priority: Critical
>  Labels: security
> Fix For: 4.2.0
>
>
> SSH public key is group readable which is security threat.
>  ls -la /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud
> -rw-r--r--. 1 root root 1670 May 15 22:54 
> /usr/share/cloudstack-common/scripts/vm/systemvm/id_rsa.cloud

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-4218) UCS:API: list UCS Manager API failes due to invalid param

[frank zhang (JIRA)]

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

frank zhang reassigned CLOUDSTACK-4218:
---

Assignee: Jessica Wang  (was: frank zhang)

> UCS:API: list UCS Manager API failes due to invalid param
> -
>
> Key: CLOUDSTACK-4218
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4218
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Assignee: Jessica Wang
>Priority: Blocker
> Attachments: UCS API ERROR.jpg
>
>
> Unable to execute API command listucsmanage due to invalid value. Invalid 
> parameter id value=479f0df8-3207-47cb-83c0-ed72ceb48596 due to incorrect long 
> value format, or entity does not exist or due to incorrect parameter 
> annotation for the field in api cmd class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-4081) Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-4081.
-

Resolution: Fixed

> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-3765) [packaging] unable to install cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang resolved CLOUDSTACK-3765.
-

Resolution: Fixed

> [packaging] unable to install cp 4.2 build on centos5.5
> ---
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-4081) Fresh install of cloud platform failed with dependency errors on centos5.5 OS

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-4081:
-

Yes. we should document this in upgrade procedure

> Fresh install of cloud platform failed with dependency errors on centos5.5 OS
> -
>
> Key: CLOUDSTACK-4081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4081
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.2.0
> Environment: centos 5.5 MS host
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Trying to install CloudPlatform-4.2-dbupgrade-56-rhel5.tar.gz build on centos 
> 5.5  OS 
> Installation failing with following dependency error
> --> Finished Dependency Resolution
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 from cloud-temp has 
> depsolving problems
>   --> Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: python-paramiko is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: ws-commons-util is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: mysql-connector-java is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
> Error: Missing Dependency: tomcat6 is needed by package 
> cloudstack-management-4.2.0-SNAPSHOT.el5.x86_64 (cloud-temp)
>  You could try using --skip-broken to work around the problem
>  You could try running: package-cleanup --problems
> package-cleanup --dupes
> rpm -Va --nofiles --nodigest
> The program package-cleanup is found in the yum-utils package.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-3765) [packaging] unable to install cp 4.2 build on centos5.5

[frank zhang (JIRA)]

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

frank zhang commented on CLOUDSTACK-3765:
-

install below repo before installing mgmt server

# cd /etc/yum.repos.d/




> [packaging] unable to install cp 4.2 build on centos5.5
> ---
>
> Key: CLOUDSTACK-3765
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3765
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
> Environment: Centos5.5
>Reporter: shweta agarwal
>Assignee: Rayees Namathponnan
>Priority: Blocker
> Fix For: 4.2.0
>
>
> When I am trying to install 
> http://repo-ccp.citrix.com/releases/ASF/rhel/5/4.2/CP4.2-dbupgrade-44-rhel5.tar.gz
>  
>  I am hitting JSVC dependency error
> When I tried to install  jsvc via rpm its also failing giving error
> rpm -Uvh 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> Retrieving 
> http://mirror.centos.org/centos/6/os/x86_64/Packages/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm
> warning: /var/tmp/rpm-xfer.qxSLPS: Header V3 RSA/SHA256 signature: NOKEY, key 
> ID c105b9de
> error: Failed dependencies:
> rpmlib(FileDigests) <= 4.6.0-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> rpmlib(PayloadIsXz) <= 5.2-1 is needed by 
> jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64
> Centos 5.5 repo does not contain any jsvc package
> Infact at rpmfind  location also JSVC package only exists for centos6.4
> http://rpmfind.net/linux/rpm2html/search.php?query=jsvc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira