[jira] [Closed] (CLOUDSTACK-7584) Cannot convert snapshot to template using Swift Secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-7584. --- Resolution: Invalid not code related. > Cannot convert snapshot to template using Swift Secondary Storage > - > > Key: CLOUDSTACK-7584 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7584 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.1 >Reporter: Francois Gaudreault >Priority: Minor > > Using swift as secondary storage, converting volume snapshots to template is > not working. We get a null pointer exception. > 2014-09-18 13:10:13,807 DEBUG [o.a.c.s.m.AncientDataMotionStrategy] > (API-Job-Executor-25:ctx-a5afd470 job-2139 ctx-bc889788) copy failed > java.lang.NullPointerException > at > org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.createTemplateFromSnapshot(AncientDataMotionStrategy.java:469) > at > org.apache.cloudstack.storage.motion.AncientDataMotionStrategy.copyAsync(AncientDataMotionStrategy.java:420) > at > org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:68) > at > org.apache.cloudstack.storage.motion.DataMotionServiceImpl.copyAsync(DataMotionServiceImpl.java:73) > at > org.apache.cloudstack.storage.image.TemplateServiceImpl.copyAsync(TemplateServiceImpl.java:635) > at > org.apache.cloudstack.storage.image.TemplateServiceImpl.createTemplateFromSnapshotAsync(TemplateServiceImpl.java:641) > at > com.cloud.template.TemplateManagerImpl.createPrivateTemplate(TemplateManagerImpl.java:1388) > 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 > org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) > 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.$Proxy173.createPrivateTemplate(Unknown Source) > at > org.apache.cloudstack.api.command.admin.template.CreateTemplateCmdByAdmin.execute(CreateTemplateCmdByAdmin.java:42) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at > com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) > 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.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 2014-09-18 13:10:13,816 DEBUG [c.c.t.Temp
[jira] [Created] (CLOUDSTACK-7887) fail to push snapshot to secondary storage if using multipart using swift
Pierre-Luc Dion created CLOUDSTACK-7887: --- Summary: fail to push snapshot to secondary storage if using multipart using swift Key: CLOUDSTACK-7887 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7887 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller, XenServer Affects Versions: 4.4.0, 4.4.1 Reporter: Pierre-Luc Dion Using Swift as secondary storage with XenServer, creating a snapshot from a big disk will display as succeed in CloudStack but the snapshot file will fail to upload in Swift. So snapshot are not working for Swift with XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7887) fail to push snapshot to secondary storage if using multipart using swift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208098#comment-14208098 ] Pierre-Luc Dion commented on CLOUDSTACK-7887: - fix to be committed shortly, the issue is in /etc/xapi.d/plugins/swiftxen file. > fail to push snapshot to secondary storage if using multipart using swift > - > > Key: CLOUDSTACK-7887 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7887 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, XenServer >Affects Versions: 4.4.0, 4.4.1 >Reporter: Pierre-Luc Dion > > Using Swift as secondary storage with XenServer, creating a snapshot from a > big disk will display as succeed in CloudStack but the snapshot file will > fail to upload in Swift. So snapshot are not working for Swift with > XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7887) fail to push snapshot to secondary storage if using multipart using swift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-7887: --- Assignee: Pierre-Luc Dion > fail to push snapshot to secondary storage if using multipart using swift > - > > Key: CLOUDSTACK-7887 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7887 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, XenServer >Affects Versions: 4.4.0, 4.4.1 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion > > Using Swift as secondary storage with XenServer, creating a snapshot from a > big disk will display as succeed in CloudStack but the snapshot file will > fail to upload in Swift. So snapshot are not working for Swift with > XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7887) fail to push snapshot to secondary storage if using multipart using swift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7887: Status: Reviewable (was: In Progress) > fail to push snapshot to secondary storage if using multipart using swift > - > > Key: CLOUDSTACK-7887 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7887 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, XenServer >Affects Versions: 4.4.0, 4.4.1 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion > > Using Swift as secondary storage with XenServer, creating a snapshot from a > big disk will display as succeed in CloudStack but the snapshot file will > fail to upload in Swift. So snapshot are not working for Swift with > XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7887) fail to push snapshot to secondary storage if using multipart using swift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-7887. - Resolution: Fixed Fix Version/s: 4.5.0 > fail to push snapshot to secondary storage if using multipart using swift > - > > Key: CLOUDSTACK-7887 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7887 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, XenServer >Affects Versions: 4.4.0, 4.4.1 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion > Fix For: 4.5.0 > > > Using Swift as secondary storage with XenServer, creating a snapshot from a > big disk will display as succeed in CloudStack but the snapshot file will > fail to upload in Swift. So snapshot are not working for Swift with > XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7887) fail to push snapshot to secondary storage if using multipart using swift
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7887: Fix Version/s: 4.4.2 > fail to push snapshot to secondary storage if using multipart using swift > - > > Key: CLOUDSTACK-7887 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7887 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, XenServer >Affects Versions: 4.4.0, 4.4.1 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion > Fix For: 4.5.0, 4.4.2 > > > Using Swift as secondary storage with XenServer, creating a snapshot from a > big disk will display as succeed in CloudStack but the snapshot file will > fail to upload in Swift. So snapshot are not working for Swift with > XenServer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7822) test SSL cert expired
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion updated CLOUDSTACK-7822:
Fix Version/s: 4.4.2
> test SSL cert expired
> -
>
> Key: CLOUDSTACK-7822
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7822
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Test
>Affects Versions: 4.4.0, 4.5.0, 4.4.1
>Reporter: Pierre-Luc Dion
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future, 4.5.0, 4.4.2
>
>
> Building from source (apache-cloudstack-4.4.1-src.tar.bz2) fail to build
> using {{mvn install}} or package.sh due to test ssl cert that are expired.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7722) add.label: Add button for tags show the label not "Add" text
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7722: Fix Version/s: 4.4.2 > add.label: Add button for tags show the label not "Add" text > > > Key: CLOUDSTACK-7722 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7722 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0, 4.4.1 >Reporter: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0, 4.4.2 > > > on every language, all sections the "Add" button display "add.label" instead > of "Add" on the button of the UI. > example: at the bottom of the page for a selected template in tags section. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7822) test SSL cert expired
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion resolved CLOUDSTACK-7822.
-
Resolution: Fixed
> test SSL cert expired
> -
>
> Key: CLOUDSTACK-7822
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7822
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Test
>Affects Versions: 4.4.0, 4.5.0, 4.4.1
>Reporter: Pierre-Luc Dion
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future, 4.5.0, 4.4.2
>
>
> Building from source (apache-cloudstack-4.4.1-src.tar.bz2) fail to build
> using {{mvn install}} or package.sh due to test ssl cert that are expired.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7752) Management Server goes in infinite loop while creating a vm with tagged local data disk when the pool is not tagged
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7752: Fix Version/s: 4.4.2 > Management Server goes in infinite loop while creating a vm with tagged local > data disk when the pool is not tagged > --- > > Key: CLOUDSTACK-7752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7752 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Fix For: 4.4.2 > > > Steps to reproduce: > Setup must have a single cluster with both local and shared storage. > 1) Create a local disk offering and tag it T1 > 2) Deploy vm with shared root disk and local data disk > Management server goes in an infinite loop. The vm is never started/expunged. > Also this causes vmops.log size to go very high. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-3383) GetHostStatsCommand fails when agent is running Ubuntu 13.04 (raring)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219586#comment-14219586
]
Pierre-Luc Dion commented on CLOUDSTACK-3383:
-
Hi Wido, does this get fixed in 4.4.2 since their is commit in 4.4 branch?
thanks
> GetHostStatsCommand fails when agent is running Ubuntu 13.04 (raring)
> -
>
> Key: CLOUDSTACK-3383
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3383
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
>Affects Versions: 4.1.0
> Environment: Ubuntu 13.04
>Reporter: Harm van Tilborg
>Assignee: Wido den Hollander
> Labels: agent, kvm, libvirt
> Attachments: ubuntu14-usage-stats.patch
>
>
> 2013-07-05 13:02:37,782 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-3:null) Processing command:
> com.cloud.agent.api.GetHostStatsCommand
> 2013-07-05 13:02:37,782 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Executing: /bin/bash -c idle=$(top -b -n 1|grep
> Cpu\(s\):|cut -d% -f4|cut -d, -f2);echo $idle
> 2013-07-05 13:02:37,940 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Execution is successful.
> 2013-07-05 13:02:37,941 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-3:null) Seq 1-2144469000: { Ans: , MgmtId:
> 159497075554, via: 1, Ver: v1, Flags: 10,
> [{"Answer":{"result":false,"details":"empty String","wait":0}}] }
> When I check the output of Ubuntu's 13.04 top (top -v = procps-ng version
> 3.3.3), it's formatted like this:
> raring# top -b -n 1|grep Cpu\(s\):
> %Cpu(s): 0.2 us, 0.2 sy, 0.0 ni, 99.5 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0
> st
> While on Ubuntu 12.04 (top -v = procps version 3.2.8) it looks like this:
> precise# top -b -n 1|grep Cpu\(s\):
> Cpu(s): 0.3%us, 0.1%sy, 0.0%ni, 99.6%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
> So I believe it is better to split the string on a comma (,) than using the
> percentage (%).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7883) Allow infrastructure to handle delete of volume from DB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7883: Fix Version/s: (was: 4.4.1) 4.4.2 > Allow infrastructure to handle delete of volume from DB > --- > > Key: CLOUDSTACK-7883 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7883 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.4.1 > Environment: N/A >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.4.2 > > > To do this, remove this line (from SolidfirePrimaryDataStoreDriver): > _volumeDao.deleteVolumesByInstance(volumeInfo.getId()); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7246) VM deployment failed due to wrong in script name createipalias.sh
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7246: Fix Version/s: 4.4.2 > VM deployment failed due to wrong in script name createipalias.sh > -- > > Key: CLOUDSTACK-7246 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7246 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.5.0 >Reporter: Jayapal Reddy >Assignee: Jayapal Reddy > Labels: DEVREV > Fix For: 4.5.0, 4.4.2 > > > 1. added multiple ip range. > 2. deployed vm in shared network failed. > 3. createipalias failed because cloudstack referring 'createipalias.sh' but > the file in VR is 'createIpAlias.sh' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7826) UI - dialog widget - dependent dropdown field (dependsOn property specified) - fix a bug that default opton in dependent dropdown field didn't trigger change event h
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7826: Fix Version/s: 4.4.2 > UI - dialog widget - dependent dropdown field (dependsOn property specified) > - fix a bug that default opton in dependent dropdown field didn't trigger > change event handler until another option in dependent dropdown field was > selected. > -- > > Key: CLOUDSTACK-7826 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7826 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Jessica Wang >Assignee: Jessica Wang >Priority: Critical > Fix For: 4.5.0, 4.4.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7871) Fix update VirtualMachine/Template API to allow nic/disk controller details for VMWare VMs/Templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7871: Fix Version/s: 4.4.2 4.5.0 > Fix update VirtualMachine/Template API to allow nic/disk controller details > for VMWare VMs/Templates > > > Key: CLOUDSTACK-7871 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7871 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0, 4.5.0, 4.3.1, 4.4.1 >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: 4.5.0, 4.4.2 > > > In case of VMWare, when we register a new template we can pass in nic type > and disk controller but there is no API (or parameter passable to current > APIs) to change nic type and disk controller for both VM and template. The > fix is that we add a details map type to the updateTemplate and > updateVirtualMachine API which updates the nic/disk controller values in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7855) Sec storage/network MTU should be on nic3 and not nic1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7855: Fix Version/s: 4.4.2 > Sec storage/network MTU should be on nic3 and not nic1 > -- > > Key: CLOUDSTACK-7855 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7855 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0, 4.3.1, 4.4.1 >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: 4.5.0, 4.4.2 > > > In cloud-early-config, the nic3 on ssvm should have MTU set and not nic1, the > MTU is defined by a global settings variable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7988) Template status is empty while the template is creating.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7988: Description: Once the Template is created and is downloading, the status attribute of the template is empty until the template is ready. usually the status indicate the "% downloaded" or "Installing template". the status was working in 4.4.0. was: Once the Template is created and is downloading, the status attribute of the template is empty until the template is ready. usually the status indicate the % downloaded or "Installing template". the status was working in 4.4.0. > Template status is empty while the template is creating. > > > Key: CLOUDSTACK-7988 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7988 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.1, 4.4.2 >Reporter: Pierre-Luc Dion >Priority: Minor > > Once the Template is created and is downloading, the status attribute of the > template is empty until the template is ready. usually the status indicate > the "% downloaded" or "Installing template". > the status was working in 4.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7988) Template status is empty while the template is creating.
Pierre-Luc Dion created CLOUDSTACK-7988: --- Summary: Template status is empty while the template is creating. Key: CLOUDSTACK-7988 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7988 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.1, 4.4.2 Reporter: Pierre-Luc Dion Priority: Minor Once the Template is created and is downloading, the status attribute of the template is empty until the template is ready. usually the status indicate the % downloaded or "Installing template". the status was working in 4.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7988) Template status is empty while the template is creating.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228044#comment-14228044 ] Pierre-Luc Dion commented on CLOUDSTACK-7988: - This is observed in the UI and API. > Template status is empty while the template is creating. > > > Key: CLOUDSTACK-7988 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7988 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.1, 4.4.2 >Reporter: Pierre-Luc Dion >Priority: Minor > > Once the Template is created and is downloading, the status attribute of the > template is empty until the template is ready. usually the status indicate > the % downloaded or "Installing template". > the status was working in 4.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7988) Template status is empty while the template is creating.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228045#comment-14228045 ] Pierre-Luc Dion commented on CLOUDSTACK-7988: - also observed on 4.4.2 while running SSVM at 4.4.0 and 4.4.1 version. > Template status is empty while the template is creating. > > > Key: CLOUDSTACK-7988 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7988 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.1, 4.4.2 >Reporter: Pierre-Luc Dion >Priority: Minor > > Once the Template is created and is downloading, the status attribute of the > template is empty until the template is ready. usually the status indicate > the "% downloaded" or "Installing template". > the status was working in 4.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7988) Template status is empty while the template is creating.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228050#comment-14228050 ] Pierre-Luc Dion commented on CLOUDSTACK-7988: - Work fine when template is from URL, look like it append when creating template from snapshot or root disk. > Template status is empty while the template is creating. > > > Key: CLOUDSTACK-7988 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7988 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.1, 4.4.2 >Reporter: Pierre-Luc Dion >Priority: Minor > > Once the Template is created and is downloading, the status attribute of the > template is empty until the template is ready. usually the status indicate > the "% downloaded" or "Installing template". > the status was working in 4.4.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7906) certificate tests fail in CertServiceTest.java
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7906: Assignee: Will Stevens > certificate tests fail in CertServiceTest.java > -- > > Key: CLOUDSTACK-7906 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7906 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0, 4.4.1, 4.4.2 >Reporter: Daan Hoogland >Assignee: Will Stevens > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7906) certificate tests fail in CertServiceTest.java
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-7906. - Resolution: Fixed Fix Version/s: 4.4.2 fixed by: commit 9c0c4f713f95e5fa228a8b22c51a0f59e5f8a9d1 > certificate tests fail in CertServiceTest.java > -- > > Key: CLOUDSTACK-7906 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7906 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0, 4.4.1, 4.4.2 >Reporter: Daan Hoogland >Assignee: Will Stevens > Fix For: 4.4.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229291#comment-14229291
]
Pierre-Luc Dion commented on CLOUDSTACK-7482:
-
here is what I'm seeing into 4.5.0-snapshot:
{code}
Received unknown parameters for command listZones. Unknown parameters : listall
Received unknown parameters for command listPods. Unknown parameters : listall
Received unknown parameters for command listClusters. Unknown parameters :
listall
Received unknown parameters for command listHosts. Unknown parameters : listall
Received unknown parameters for command listStoragePools. Unknown parameters :
listall
Received unknown parameters for command listImageStores. Unknown parameters :
listall type
Received unknown parameters for command listSystemVms. Unknown parameters :
listall
Received unknown parameters for command listAccounts. Unknown parameters :
details
Received unknown parameters for command listProjects. Unknown parameters :
details
Received unknown parameters for command listServiceOfferings. Unknown
parameters : listall
Received unknown parameters for command listNetworkOfferings. Unknown
parameters : listall
Received unknown parameters for command listVPCOfferings. Unknown parameters :
listall
Received unknown parameters for command listDiskOfferings. Unknown parameters
: listall
Received unknown parameters for command listServiceOfferings. Unknown
parameters : listall
Received unknown parameters for command listLdapConfigurations. Unknown
parameters : listall
Received unknown parameters for command listBaremetalRct. Unknown parameters :
listall
Received unknown parameters for command listHypervisorCapabilities. Unknown
parameters : listall
Received unknown parameters for command listRegions. Unknown parameters :
listall
Received unknown parameters for command listNetworks. Unknown parameters :
details
{code}
> Ajax calls in mgmt UI causing log pollution
> ---
>
> Key: CLOUDSTACK-7482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: Kedron Touvell
>Priority: Minor
> Fix For: Future
>
>
> Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
> despite the fact that the underlying API call does not support listAll. This
> is causing a decent amount of log pollution:
> {quote}
> 2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
> command listImageStores. Unknown parameters : listall type
> {quote}
> These parameters are set in {{ui/scripts/system.js}}, for example:
> {noformat}
> systemVmCount: function (data) {
> $.ajax({
> url: createURL('listSystemVms'),
> data: {
> listAll: true,
> {noformat}
> Here's the list of API calls that I see generating warnings:
> * listClusters
> * listHosts
> * listImageStores
> * listNetworkOfferings
> * listPods
> * listRegions
> * listServiceOfferings
> * listStoragePools
> * listSystemVms
> * listZones
> One more to add...listDomains is being called with a parentdomainid
> parameter, leading to the following warning:
> {quote}
> 2014-09-04 11:59:01,217 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-5:ctx-c85dc843 ctx-647a43c1 ctx-bcd4e41b) Received unknown
> parameters for command listDomains. Unknown parameters : parentdomainid
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion reassigned CLOUDSTACK-7482:
---
Assignee: Pierre-Luc Dion
> Ajax calls in mgmt UI causing log pollution
> ---
>
> Key: CLOUDSTACK-7482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: Kedron Touvell
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future
>
>
> Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
> despite the fact that the underlying API call does not support listAll. This
> is causing a decent amount of log pollution:
> {quote}
> 2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
> command listImageStores. Unknown parameters : listall type
> {quote}
> These parameters are set in {{ui/scripts/system.js}}, for example:
> {noformat}
> systemVmCount: function (data) {
> $.ajax({
> url: createURL('listSystemVms'),
> data: {
> listAll: true,
> {noformat}
> Here's the list of API calls that I see generating warnings:
> * listClusters
> * listHosts
> * listImageStores
> * listNetworkOfferings
> * listPods
> * listRegions
> * listServiceOfferings
> * listStoragePools
> * listSystemVms
> * listZones
> One more to add...listDomains is being called with a parentdomainid
> parameter, leading to the following warning:
> {quote}
> 2014-09-04 11:59:01,217 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-5:ctx-c85dc843 ctx-647a43c1 ctx-bcd4e41b) Received unknown
> parameters for command listDomains. Unknown parameters : parentdomainid
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion updated CLOUDSTACK-7482:
Fix Version/s: 4.5.0
> Ajax calls in mgmt UI causing log pollution
> ---
>
> Key: CLOUDSTACK-7482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: Kedron Touvell
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future, 4.5.0
>
>
> Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
> despite the fact that the underlying API call does not support listAll. This
> is causing a decent amount of log pollution:
> {quote}
> 2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
> command listImageStores. Unknown parameters : listall type
> {quote}
> These parameters are set in {{ui/scripts/system.js}}, for example:
> {noformat}
> systemVmCount: function (data) {
> $.ajax({
> url: createURL('listSystemVms'),
> data: {
> listAll: true,
> {noformat}
> Here's the list of API calls that I see generating warnings:
> * listClusters
> * listHosts
> * listImageStores
> * listNetworkOfferings
> * listPods
> * listRegions
> * listServiceOfferings
> * listStoragePools
> * listSystemVms
> * listZones
> One more to add...listDomains is being called with a parentdomainid
> parameter, leading to the following warning:
> {quote}
> 2014-09-04 11:59:01,217 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-5:ctx-c85dc843 ctx-647a43c1 ctx-bcd4e41b) Received unknown
> parameters for command listDomains. Unknown parameters : parentdomainid
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion updated CLOUDSTACK-7482:
Status: Reviewable (was: In Progress)
> Ajax calls in mgmt UI causing log pollution
> ---
>
> Key: CLOUDSTACK-7482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: Kedron Touvell
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future, 4.5.0
>
>
> Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
> despite the fact that the underlying API call does not support listAll. This
> is causing a decent amount of log pollution:
> {quote}
> 2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
> command listImageStores. Unknown parameters : listall type
> {quote}
> These parameters are set in {{ui/scripts/system.js}}, for example:
> {noformat}
> systemVmCount: function (data) {
> $.ajax({
> url: createURL('listSystemVms'),
> data: {
> listAll: true,
> {noformat}
> Here's the list of API calls that I see generating warnings:
> * listClusters
> * listHosts
> * listImageStores
> * listNetworkOfferings
> * listPods
> * listRegions
> * listServiceOfferings
> * listStoragePools
> * listSystemVms
> * listZones
> One more to add...listDomains is being called with a parentdomainid
> parameter, leading to the following warning:
> {quote}
> 2014-09-04 11:59:01,217 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-5:ctx-c85dc843 ctx-647a43c1 ctx-bcd4e41b) Received unknown
> parameters for command listDomains. Unknown parameters : parentdomainid
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229345#comment-14229345
]
Pierre-Luc Dion commented on CLOUDSTACK-7482:
-
merge conflict in 4.4 :-(
> Ajax calls in mgmt UI causing log pollution
> ---
>
> Key: CLOUDSTACK-7482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: Kedron Touvell
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future, 4.5.0
>
>
> Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
> despite the fact that the underlying API call does not support listAll. This
> is causing a decent amount of log pollution:
> {quote}
> 2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
> command listImageStores. Unknown parameters : listall type
> {quote}
> These parameters are set in {{ui/scripts/system.js}}, for example:
> {noformat}
> systemVmCount: function (data) {
> $.ajax({
> url: createURL('listSystemVms'),
> data: {
> listAll: true,
> {noformat}
> Here's the list of API calls that I see generating warnings:
> * listClusters
> * listHosts
> * listImageStores
> * listNetworkOfferings
> * listPods
> * listRegions
> * listServiceOfferings
> * listStoragePools
> * listSystemVms
> * listZones
> One more to add...listDomains is being called with a parentdomainid
> parameter, leading to the following warning:
> {quote}
> 2014-09-04 11:59:01,217 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-5:ctx-c85dc843 ctx-647a43c1 ctx-bcd4e41b) Received unknown
> parameters for command listDomains. Unknown parameters : parentdomainid
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5120) Adding userdata support for new instance wizard
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229403#comment-14229403 ] Pierre-Luc Dion commented on CLOUDSTACK-5120: - Look like this review: https://reviews.apache.org/r/19995/ does address this Feature request. > Adding userdata support for new instance wizard > --- > > Key: CLOUDSTACK-5120 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5120 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.2.0 >Reporter: Bjoern Teipel > > Currently the instance userdata can only be set when the instance is created > over an API call. > There is definitely GUI support missing, especially the support in the > Instance Wizard of the management server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-4991) Remove limitation of only one network in 'Account' source nat type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-4991. - Resolution: Fixed Fix Version/s: 4.4.0 Patch submitted by Sheng Yang > Remove limitation of only one network in 'Account' source nat type > -- > > Key: CLOUDSTACK-4991 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4991 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Will Stevens >Priority: Blocker > Fix For: 4.4.0 > > > Please check the PDF attached to the patch review: > https://reviews.apache.org/r/15047/ > Summary... > If you specify 'per account' for Supported Source NAT Type in the Create > network service offering interface, then you are subject to a limitation of > only being able to create one network per account. > There is nothing that makes this limitation required. > In writing the Palo Alto Networks firewall integration, I needed to remove > this limitation in order for an account to have more than one network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-4991) Remove limitation of only one network in 'Account' source nat type
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-4991: Assignee: Sheng Yang > Remove limitation of only one network in 'Account' source nat type > -- > > Key: CLOUDSTACK-4991 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4991 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Will Stevens >Assignee: Sheng Yang >Priority: Blocker > Fix For: 4.4.0 > > > Please check the PDF attached to the patch review: > https://reviews.apache.org/r/15047/ > Summary... > If you specify 'per account' for Supported Source NAT Type in the Create > network service offering interface, then you are subject to a limitation of > only being able to create one network per account. > There is nothing that makes this limitation required. > In writing the Palo Alto Networks firewall integration, I needed to remove > this limitation in order for an account to have more than one network. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-4151) 4.5.5. About Password and Key Encryption unclear
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-4151: --- Assignee: Pierre-Luc Dion > 4.5.5. About Password and Key Encryption unclear > > > Key: CLOUDSTACK-4151 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4151 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.1 > Environment: all >Reporter: Ron Wheeler >Assignee: Pierre-Luc Dion >Priority: Blocker > > 4.5.5. About Password and Key Encryption > The purpose of this section is a bit obcure. What is the reader supposed to > do with this information? > There seems to be a lot of magical activities here wherein keys and secrets > get stored in databases without any mention of how they get there. > There seems to be a list of items that are incrypted but no explaination > about what is the reader\'s role in this or who creates them or why you are > telling the reader this at this point in the process. > It might be clearer if " The data values are encrypted and decrypted using a > database secret key, which is stored in one of CloudStack’s internal > properties files along with the database password. The other encrypted values > listed above, such as SSH keys, are in the CloudStack internal database." > included some mention about how this happens and when and whether the reader > has to do something to make any of this happen correctly. > If it is really only informational and has nothing to do with the > installation process, it could be moved out of the flow and referenced as > something that terminally curious might wish to know. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7195) security_group.py should log exceptions instead of discarding them
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-7195: --- Assignee: Pierre-Luc Dion > security_group.py should log exceptions instead of discarding them > -- > > Key: CLOUDSTACK-7195 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7195 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.3.0 >Reporter: Vincent Bernat >Assignee: Pierre-Luc Dion > > security_group.py discards exceptions with a vague message. This is > troublesome and hide some other bugs. See for example CLOUDSTACK-7193. Any > try/except should at least log the exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7195) security_group.py should log exceptions instead of discarding them
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7195: Fix Version/s: 4.6.0 Future > security_group.py should log exceptions instead of discarding them > -- > > Key: CLOUDSTACK-7195 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7195 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.3.0 >Reporter: Vincent Bernat >Assignee: Pierre-Luc Dion > Fix For: Future, 4.6.0 > > > security_group.py discards exceptions with a vague message. This is > troublesome and hide some other bugs. See for example CLOUDSTACK-7193. Any > try/except should at least log the exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7195) security_group.py should log exceptions instead of discarding them
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-7195. - Resolution: Fixed Vincent patches pushed into master branch. Thanks Vincent. > security_group.py should log exceptions instead of discarding them > -- > > Key: CLOUDSTACK-7195 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7195 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.3.0 >Reporter: Vincent Bernat >Assignee: Pierre-Luc Dion > Fix For: Future, 4.6.0 > > > security_group.py discards exceptions with a vague message. This is > troublesome and hide some other bugs. See for example CLOUDSTACK-7193. Any > try/except should at least log the exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-1973) Delete Secondary Storage API Doc
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-1973. - Resolution: Fixed > Delete Secondary Storage API Doc > > > Key: CLOUDSTACK-1973 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1973 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Doc > Environment: API >Reporter: Tim Schultheiss >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > The API documentation needs a note on how to delete Secondary Storage. > The process is accomplished via the DeleteHost command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent
Pierre-Luc Dion created CLOUDSTACK-8041:
---
Summary: 4.5.0 db upgrade fail if new systemvm templates are
abscent
Key: CLOUDSTACK-8041
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8041
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.5.0
Reporter: Pierre-Luc Dion
Priority: Critical
When upgrading ACS to 4.5.0 without systemvm-{hypervisor}-4.5 already in place,
the db upgrade fail.
Upgrading ACS without systemvm should not affect db upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236566#comment-14236566
]
Pierre-Luc Dion commented on CLOUDSTACK-8041:
-
{code}
INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability
enabled? Ans : false
INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 7566289535078
INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 7566289535078
INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system
integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@74173125
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for
database upgrade.
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.4.2 Code
Version = 4.5.0
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be
performed from 4.4.2 to 4.5.0
WARN [c.c.u.d.Upgrade442to450] (main:null) 4.5.0 Hyperv SystemVm template not
found. Hyperv hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade442to450] (main:null) 4.5.0 KVM SystemVm template not
found. KVM hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade442to450] (main:null) 4.5.0 VMware SystemVm template not
found. VMware hypervisor is not used, so not failing upgrade
WARN [c.c.u.d.Upgrade442to450] (main:null) 4.5.0 LXC SystemVm template not
found. LXC hypervisor is not used, so not failing upgrade
ERROR [c.c.u.DatabaseUpgradeChecker] (main:null) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: 4.5.0 XenServer SystemVm
template not found. Cannot upgrade system Vms
at
com.cloud.upgrade.dao.Upgrade442to450.updateSystemVmTemplates(Upgrade442to450.java:262)
at
com.cloud.upgrade.dao.Upgrade442to450.performDataMigration(Upgrade442to450.java:68)
at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:329)
at
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:452)
at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65)
at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55)
at
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167)
at
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
at
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)
at
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143)
at
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79)
at
org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
at
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70)
at
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:57)
at
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.(CloudStackSpringContext.java:61)
at
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4709)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.
[jira] [Updated] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion updated CLOUDSTACK-8041:
Component/s: Management Server
> 4.5.0 db upgrade fail if new systemvm templates are abscent
>
>
> Key: CLOUDSTACK-8041
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8041
> 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: Pierre-Luc Dion
>Priority: Critical
>
> When upgrading ACS to 4.5.0 without systemvm-{hypervisor}-4.5 already in
> place, the db upgrade fail.
> Upgrading ACS without systemvm should not affect db upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236814#comment-14236814
]
Pierre-Luc Dion commented on CLOUDSTACK-8041:
-
I'd like to avoid the need to have a systemvm-template for each upgrade, as
this RN:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.2/upgrade/upgrade-4.2.html
Now with 4.5, a user upgrading from 4.2.1 to 4.5 need to register 3
systemvm-templates prior to upgrade, and they cannot be deleted from the ui
afterward.
> 4.5.0 db upgrade fail if new systemvm templates are abscent
>
>
> Key: CLOUDSTACK-8041
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8041
> 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: Pierre-Luc Dion
>Priority: Blocker
> Fix For: 4.5.0, 4.6.0
>
>
> When upgrading ACS to 4.5.0 without systemvm-{hypervisor}-4.5 already in
> place, the db upgrade fail.
> Upgrading ACS without systemvm should not affect db upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236874#comment-14236874
]
Pierre-Luc Dion commented on CLOUDSTACK-8041:
-
This might be already resolved and not exist from 4.3. I will perform more
upgrade tests...
> 4.5.0 db upgrade fail if new systemvm templates are abscent
>
>
> Key: CLOUDSTACK-8041
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8041
> 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: Pierre-Luc Dion
>Priority: Blocker
> Fix For: 4.5.0, 4.6.0
>
>
> When upgrading ACS to 4.5.0 without systemvm-{hypervisor}-4.5 already in
> place, the db upgrade fail.
> Upgrading ACS without systemvm should not affect db upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8041) 4.5.0 db upgrade fail if new systemvm templates are abscent
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion closed CLOUDSTACK-8041.
---
Resolution: Invalid
Look like upgrading from 4.3.0 require only one SystemVM-template in place.
> 4.5.0 db upgrade fail if new systemvm templates are abscent
>
>
> Key: CLOUDSTACK-8041
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8041
> 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: Pierre-Luc Dion
>Priority: Blocker
> Fix For: 4.5.0, 4.6.0
>
>
> When upgrading ACS to 4.5.0 without systemvm-{hypervisor}-4.5 already in
> place, the db upgrade fail.
> Upgrading ACS without systemvm should not affect db upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-8042: Labels: upgrade (was: ) > Fail to upgrade to 4.5.0 from 4.3.1 > --- > > Key: CLOUDSTACK-8042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8042 > 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: Pierre-Luc Dion > Labels: upgrade > > Fail to upgrade the management-server from 4.3.1 to 4.5.0. > The management-server is not working anymore after a direct upgrade from > 4.3.1 -> 4.5.0-rc1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1
Pierre-Luc Dion created CLOUDSTACK-8042: --- Summary: Fail to upgrade to 4.5.0 from 4.3.1 Key: CLOUDSTACK-8042 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8042 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: Pierre-Luc Dion Fail to upgrade the management-server from 4.3.1 to 4.5.0. The management-server is not working anymore after a direct upgrade from 4.3.1 -> 4.5.0-rc1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-8042: Attachment: management-server.log localhost.2014-12-06.log catalina.out logs > Fail to upgrade to 4.5.0 from 4.3.1 > --- > > Key: CLOUDSTACK-8042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8042 > 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: Pierre-Luc Dion > Labels: upgrade > Attachments: catalina.out, localhost.2014-12-06.log, > management-server.log > > > Fail to upgrade the management-server from 4.3.1 to 4.5.0. > The management-server is not working anymore after a direct upgrade from > 4.3.1 -> 4.5.0-rc1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7098) Improved CloudByte Storage Plugin for 4.5 and above.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7098: Summary: Improved CloudByte Storage Plugin for 4.5 and above. (was: Improvised CloudByte Storage Plugin for 4.5 and above.) > Improved CloudByte Storage Plugin for 4.5 and above. > > > Key: CLOUDSTACK-7098 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7098 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: punith > Fix For: 4.5.0 > > > The new improvised cloudbyte plugin for cloudstack supports the following > features > * support for managed storage, where each vm disk has the guaranteed > QoS. > * account integration in cloudbyte with respect to domains in cloudstack. > * supports resize of the volume. > * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for > KVM and vmware ESX. > * supports storage level snapshot capabilites as well as hypervisor level > snapshot feature. > * also exposing the custom api's for ui integration. > * support for unlimited storage nodes across the sites. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7098) Improved CloudByte Storage Plugin for 4.5 and above.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-7098: Description: The new improved cloudbyte plugin for cloudstack supports the following features * support for managed storage, where each vm disk has the guaranteed QoS. * account integration in cloudbyte with respect to domains in CloudStack. * supports resize of the volume. * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for KVM and vmware ESX. * supports storage level snapshot capabilities as well as hypervisor level snapshot feature. * also exposing the custom api's for ui integration. * support for unlimited storage nodes across the sites. was: The new improvised cloudbyte plugin for cloudstack supports the following features * support for managed storage, where each vm disk has the guaranteed QoS. * account integration in cloudbyte with respect to domains in cloudstack. * supports resize of the volume. * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for KVM and vmware ESX. * supports storage level snapshot capabilites as well as hypervisor level snapshot feature. * also exposing the custom api's for ui integration. * support for unlimited storage nodes across the sites. > Improved CloudByte Storage Plugin for 4.5 and above. > > > Key: CLOUDSTACK-7098 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7098 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.5.0 >Reporter: punith > Fix For: 4.5.0 > > > The new improved cloudbyte plugin for cloudstack supports the following > features > * support for managed storage, where each vm disk has the guaranteed > QoS. > * account integration in cloudbyte with respect to domains in CloudStack. > * supports resize of the volume. > * supports both iscsi and nfs protocols in XEN server, and iscsi protocol for > KVM and vmware ESX. > * supports storage level snapshot capabilities as well as hypervisor level > snapshot feature. > * also exposing the custom api's for ui integration. > * support for unlimited storage nodes across the sites. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-6059) Restarting a VPC that has a Private Gateway fails due to a NPE, but message is not clear
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-6059: Affects Version/s: 4.4.1 > Restarting a VPC that has a Private Gateway fails due to a NPE, but message > is not clear > > > Key: CLOUDSTACK-6059 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6059 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.2.1, 4.4.1 > Environment: Cloudstack 4.2.1-SNAPSHOT, Linux >Reporter: Wilder Rodrigues >Priority: Minor > > When trying to restart a VPC that has a Private Gateway configured, it fails > with a message "Failed to restart VPC". However, in the logs, we have > observed that there is a NullPointerException when calling > createPrivateNicProfileForGateway(VpcVirtualNetworkApplianceManagerImpl.java:1295). > We know that's not possible to restart a VPC that has a Private Gateway, but > we are opening this issue just to have in mind that the method is currently > returning "null" and the message on the UI is not clear at all. > 2014-02-07 10:53:22,639 DEBUG [db.Transaction.Transaction] > (Job-Executor-75:job-224729 = [ bb0b666a-ef03-4712-bc62-f3e27c82282c ]) > Rolling back the transaction: Time = 3 Name = -AsyncJobManagerImp > l$1.run:494-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; > called by -Transac > tion.rollback:897-PrivateIpDaoImpl.allocateIpAddress:85-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VpcVirtualNetworkApplianceManagerImpl.createPrivateNicProfileForGatew > ay:1294-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VpcVirtualNetworkApplianceManagerImpl.createVpcRouterNetworks:1250-VpcVirtualNetworkApplianceManagerImpl.deployVpcRou > ter:329-VpcVirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInVpc:227-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VpcVirtualNetworkApplianceManagerImpl.deploy > VirtualRouterInVpc:176-VpcVirtualRouterElement.implementVpc:126-VpcManagerImpl.startVpc:992 > 2014-02-07 10:53:22,642 WARN [network.vpc.VpcManagerImpl] > (Job-Executor-75:job-224729 = [ bb0b666a-ef03-4712-bc62-f3e27c82282c ]) > Failed to start vpc [VPC [237-SBP_VPC_AJENKINS1] due to > java.lang.NullPointerException > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createPrivateNicProfileForGateway(VpcVirtualNetworkApplianceManagerImpl.java:1295) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createVpcRouterNetworks(VpcVirtualNetworkApplianceManagerImpl.java:1250) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVpcRouter(VpcVirtualNetworkApplianceManagerImpl.java:329) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:227) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:176) > at > com.cloud.network.element.VpcVirtualRouterElement.implementVpc(VpcVirtualRouterElement.java:126) > at > com.cloud.network.vpc.VpcManagerImpl.startVpc(VpcManagerImpl.java:992) > at > com.cloud.network.vpc.VpcManagerImpl.startVpc(VpcManagerImpl.java:964) > at > com.cloud.network.vpc.VpcManagerImpl.restartVpc(VpcManagerImpl.java:1304) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vpc.RestartVPCCmd.execute(RestartVPCCmd.java:80) > 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.c
[jira] [Updated] (CLOUDSTACK-6059) Restarting a VPC that has a Private Gateway fails due to a NPE, but message is not clear
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-6059: Affects Version/s: (was: 4.4.1) 4.4.2 > Restarting a VPC that has a Private Gateway fails due to a NPE, but message > is not clear > > > Key: CLOUDSTACK-6059 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6059 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.2.1, 4.4.2 > Environment: Cloudstack 4.2.1-SNAPSHOT, Linux >Reporter: Wilder Rodrigues >Priority: Minor > > When trying to restart a VPC that has a Private Gateway configured, it fails > with a message "Failed to restart VPC". However, in the logs, we have > observed that there is a NullPointerException when calling > createPrivateNicProfileForGateway(VpcVirtualNetworkApplianceManagerImpl.java:1295). > We know that's not possible to restart a VPC that has a Private Gateway, but > we are opening this issue just to have in mind that the method is currently > returning "null" and the message on the UI is not clear at all. > 2014-02-07 10:53:22,639 DEBUG [db.Transaction.Transaction] > (Job-Executor-75:job-224729 = [ bb0b666a-ef03-4712-bc62-f3e27c82282c ]) > Rolling back the transaction: Time = 3 Name = -AsyncJobManagerImp > l$1.run:494-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679; > called by -Transac > tion.rollback:897-PrivateIpDaoImpl.allocateIpAddress:85-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VpcVirtualNetworkApplianceManagerImpl.createPrivateNicProfileForGatew > ay:1294-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VpcVirtualNetworkApplianceManagerImpl.createVpcRouterNetworks:1250-VpcVirtualNetworkApplianceManagerImpl.deployVpcRou > ter:329-VpcVirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInVpc:227-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-VpcVirtualNetworkApplianceManagerImpl.deploy > VirtualRouterInVpc:176-VpcVirtualRouterElement.implementVpc:126-VpcManagerImpl.startVpc:992 > 2014-02-07 10:53:22,642 WARN [network.vpc.VpcManagerImpl] > (Job-Executor-75:job-224729 = [ bb0b666a-ef03-4712-bc62-f3e27c82282c ]) > Failed to start vpc [VPC [237-SBP_VPC_AJENKINS1] due to > java.lang.NullPointerException > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createPrivateNicProfileForGateway(VpcVirtualNetworkApplianceManagerImpl.java:1295) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.createVpcRouterNetworks(VpcVirtualNetworkApplianceManagerImpl.java:1250) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVpcRouter(VpcVirtualNetworkApplianceManagerImpl.java:329) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.findOrDeployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:227) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.deployVirtualRouterInVpc(VpcVirtualNetworkApplianceManagerImpl.java:176) > at > com.cloud.network.element.VpcVirtualRouterElement.implementVpc(VpcVirtualRouterElement.java:126) > at > com.cloud.network.vpc.VpcManagerImpl.startVpc(VpcManagerImpl.java:992) > at > com.cloud.network.vpc.VpcManagerImpl.startVpc(VpcManagerImpl.java:964) > at > com.cloud.network.vpc.VpcManagerImpl.restartVpc(VpcManagerImpl.java:1304) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > org.apache.cloudstack.api.command.user.vpc.RestartVPCCmd.execute(RestartVPCCmd.java:80) > 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(ThreadPoolExecuto
[jira] [Created] (CLOUDSTACK-8187) webui: label.add.isolated.guest.network not found
Pierre-Luc Dion created CLOUDSTACK-8187: --- Summary: webui: label.add.isolated.guest.network not found Key: CLOUDSTACK-8187 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8187 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Pierre-Luc Dion Priority: Trivial When Creating Isolated Guest Network using UI, the notification display ``label.add.isolated.guest.network`` instead text like "Creating isolated guest network" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8188) using ReinstallVM display label.password.reset.confirm in the popup for the new password
Pierre-Luc Dion created CLOUDSTACK-8188: --- Summary: using ReinstallVM display label.password.reset.confirm in the popup for the new password Key: CLOUDSTACK-8188 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8188 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Pierre-Luc Dion Priority: Trivial Using "ReinstallVM" button display ``label.password.reset.confirm`` in the popup containing the new root password when password is enable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8042) Fail to upgrade to 4.5.0 from 4.3.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-8042. --- Resolution: Fixed Fix Version/s: 4.5.0 This issue is fixed since 4.5.0-RC2 > Fail to upgrade to 4.5.0 from 4.3.1 > --- > > Key: CLOUDSTACK-8042 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8042 > 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: Pierre-Luc Dion >Priority: Blocker > Labels: upgrade > Fix For: 4.5.0 > > Attachments: catalina.out, localhost.2014-12-06.log, > management-server.log > > > Fail to upgrade the management-server from 4.3.1 to 4.5.0. > The management-server is not working anymore after a direct upgrade from > 4.3.1 -> 4.5.0-rc1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8231) Fail to create load-balancing service on VPC
Pierre-Luc Dion created CLOUDSTACK-8231: --- Summary: Fail to create load-balancing service on VPC Key: CLOUDSTACK-8231 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Pierre-Luc Dion Priority: Critical Using the uI, cannot create Load-Balancing rules on a VPC tier because the load-balancing algorithm is empty and the drop down display nothing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8231) Fail to create load-balancing service on VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311346#comment-14311346 ] Pierre-Luc Dion commented on CLOUDSTACK-8231: - CLOUDSTACK-7915 might be the cause of this issue. > Fail to create load-balancing service on VPC > > > Key: CLOUDSTACK-8231 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Priority: Critical > Attachments: lb-algo.png > > > Using the uI, cannot create Load-Balancing rules on a VPC tier because the > load-balancing algorithm is empty and the drop down display nothing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8231) Fail to create load-balancing service on VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-8231: Attachment: lb-algo.png > Fail to create load-balancing service on VPC > > > Key: CLOUDSTACK-8231 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Priority: Critical > Attachments: lb-algo.png > > > Using the uI, cannot create Load-Balancing rules on a VPC tier because the > load-balancing algorithm is empty and the drop down display nothing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8231) Fail to create load-balancing service on VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-8231: Priority: Major (was: Critical) > Fail to create load-balancing service on VPC > > > Key: CLOUDSTACK-8231 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion > Attachments: lb-algo.png > > > Using the uI, cannot create Load-Balancing rules on a VPC tier because the > load-balancing algorithm is empty and the drop down display nothing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8231) Fail to create load-balancing service on VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311349#comment-14311349 ] Pierre-Luc Dion commented on CLOUDSTACK-8231: - this bug does not affect the API. creating LB rule does work with cloudmonkey. > Fail to create load-balancing service on VPC > > > Key: CLOUDSTACK-8231 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Priority: Critical > Attachments: lb-algo.png > > > Using the uI, cannot create Load-Balancing rules on a VPC tier because the > load-balancing algorithm is empty and the drop down display nothing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8232) UI: missing label: label.na
Pierre-Luc Dion created CLOUDSTACK-8232: --- Summary: UI: missing label: label.na Key: CLOUDSTACK-8232 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8232 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: Pierre-Luc Dion Priority: Trivial in the Details page of a Guest Network, the VPC ID display: 'label.na' instead of 'N/A'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8231) Fail to create load-balancing service on VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311498#comment-14311498 ] Pierre-Luc Dion commented on CLOUDSTACK-8231: - This issue does not affect Load-Balancing for an Isolated Guest Network. > Fail to create load-balancing service on VPC > > > Key: CLOUDSTACK-8231 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8231 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion > Attachments: lb-algo.png > > > Using the uI, cannot create Load-Balancing rules on a VPC tier because the > load-balancing algorithm is empty and the drop down display nothing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CLOUDSTACK-8234) SS VM agent fails to start due to Java error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311702#comment-14311702 ] Pierre-Luc Dion edited comment on CLOUDSTACK-8234 at 2/9/15 1:46 AM: - Did you add new SystemVM template when the upgrade to 4.5.0 was performed? also, can you get the version of the running systemvm ? "cat /etc/cloudstack-release" inside the SSVM. Thanks, was (Author: pdion): Did you add new SystemVM template when the upgrade to 4.5.0 was performed? also, can you get the version of the running systemvm ? "cat /etc/cloudstack" inside the SSVM. Thanks, > SS VM agent fails to start due to Java error > > > Key: CLOUDSTACK-8234 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8234 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Nux >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8234) SS VM agent fails to start due to Java error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311702#comment-14311702 ] Pierre-Luc Dion commented on CLOUDSTACK-8234: - Did you add new SystemVM template when the upgrade to 4.5.0 was performed? also, can you get the version of the running systemvm ? "cat /etc/cloudstack" inside the SSVM. Thanks, > SS VM agent fails to start due to Java error > > > Key: CLOUDSTACK-8234 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8234 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.5.0 > Environment: CentOS 6, KVM >Reporter: Nux >Priority: Critical > Labels: secondary_storage, ssvm > > After an upgrade from 4.4.2 everything appears to go smoothly except the SSVM > agent which fails to start: > From the VM's /var/log/cloud.log: > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource > class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource > due to: java.lang.ClassNotFoundException: > com.cloud.storage.resource.PremiumSecondaryStorageResource > More here http://fpaste.org/183058/34269811/raw/ > Java is installed: > root@s-386-VM:~# dpkg -l| grep jre > ii openjdk-7-jre-headless:amd64 7u75-2.5.4-1~deb7u1 amd64 >OpenJDK Java runtime, using Hotspot JIT (headless) > The HV and management servers are also on openjdk 7 (1.7.0) from CentOS 6 > stock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6823) Brocade Network plugin to orchestrate Brocade VDX switches
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313423#comment-14313423 ] Pierre-Luc Dion commented on CLOUDSTACK-6823: - Is this part of 4.5.0 currently in RC? > Brocade Network plugin to orchestrate Brocade VDX switches > -- > > Key: CLOUDSTACK-6823 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6823 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.4.0 > Environment: •CloudStack supported KVM Hypervisor, VMWare, > XenServer > • Brocade VDX switches running Network Operating System 5.0 or above. The > following models are supported: > o VDX 8770, VDX 8770-8, VDX 8770-4, VDX 6740 and VDX 6740T >Reporter: Ritu Sabharwal >Assignee: Ritu Sabharwal > Labels: Brocade > Fix For: 4.5.0 > > > This plugin is focused on providing L2 services initially with other services > coming in later. This feature is about a CloudStack network-guru plugin to > automatically orchestrate Brocade’s switches to provide tenant isolation via > VLAN. When isolated networks are created from CloudStack and allocated VLAN, > a port profile is created on the switch for the network with the VLAN profile > for the allocated VLAN which defines the VLAN membership for the overall port > profile. When a VM is created and attached to the network, the VMs MAC > address is associated with the port profile of the network. The port profile > is applied to the switch when the MAC address is learned. When the VM is > deleted, the VMs MAC address is disassociated from the port profile of the > network. When an isolated Network is deleted, the port-profile for the > network is deleted from the switches. The plugin also implements the > capability to monitor the availability of the switch when it is configured > first time. If there are no isolated Networks using the physical switch, the > monitoring capability is disabled for the switch. > The Brocade Network Plugin orchestrates Brocade’s switches using REST APIs. > The plugin uses pre-configured properties file to provide the details of > Brocade switches (IP Address, UserName, Password). In order to find out which > switches are connected to the hypervisor hosts, the plugin uses the > properties file to specify the pod to switch mapping. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-8232) UI: missing label: label.na
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-8232: --- Assignee: Pierre-Luc Dion > UI: missing label: label.na > --- > > Key: CLOUDSTACK-8232 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8232 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > > in the Details page of a Guest Network, the VPC ID display: 'label.na' > instead of 'N/A'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-4351) [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading or premature note
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327355#comment-14327355 ] Pierre-Luc Dion commented on CLOUDSTACK-4351: - I've never removed that line, and never got any feed back, so I will remove it while updating install guide to 4.5.0... Thanks for the reminder :-) > [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading or premature > note > -- > > Key: CLOUDSTACK-4351 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4351 > 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: All >Reporter: Ron Wheeler >Assignee: Pierre-Luc Dion > Fix For: 4.5.0 > > > Note > If DHCP is used for hosts, ensure that no conflict occurs between DHCP server > used for these hosts and the DHCP router created by CloudStack. > How can you do this at this point? > Cloudstack does not have a DHCP server at this point. > There is nothing for the user to do at this point. > It should be moved to closer to the point where the DHCP server addresses are > specified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-8187) webui: label.add.isolated.guest.network not found
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-8187: --- Assignee: Pierre-Luc Dion > webui: label.add.isolated.guest.network not found > -- > > Key: CLOUDSTACK-8187 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8187 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > > When Creating Isolated Guest Network using UI, the notification display > ``label.add.isolated.guest.network`` instead text like "Creating isolated > guest network" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-8188) using ReinstallVM display label.password.reset.confirm in the popup for the new password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-8188: --- Assignee: Pierre-Luc Dion > using ReinstallVM display label.password.reset.confirm in the popup for the > new password > > > Key: CLOUDSTACK-8188 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8188 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > > Using "ReinstallVM" button display ``label.password.reset.confirm`` in the > popup containing the new root password when password is enable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8188) using ReinstallVM display label.password.reset.confirm in the popup for the new password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-8188. - Resolution: Fixed Fix Version/s: 4.5.0 > using ReinstallVM display label.password.reset.confirm in the popup for the > new password > > > Key: CLOUDSTACK-8188 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8188 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > Using "ReinstallVM" button display ``label.password.reset.confirm`` in the > popup containing the new root password when password is enable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8187) webui: label.add.isolated.guest.network not found
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-8187. --- > webui: label.add.isolated.guest.network not found > -- > > Key: CLOUDSTACK-8187 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8187 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > When Creating Isolated Guest Network using UI, the notification display > ``label.add.isolated.guest.network`` instead text like "Creating isolated > guest network" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8188) using ReinstallVM display label.password.reset.confirm in the popup for the new password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-8188. --- > using ReinstallVM display label.password.reset.confirm in the popup for the > new password > > > Key: CLOUDSTACK-8188 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8188 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > Using "ReinstallVM" button display ``label.password.reset.confirm`` in the > popup containing the new root password when password is enable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8232) UI: missing label: label.na
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-8232. --- > UI: missing label: label.na > --- > > Key: CLOUDSTACK-8232 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8232 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > in the Details page of a Guest Network, the VPC ID display: 'label.na' > instead of 'N/A'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8187) webui: label.add.isolated.guest.network not found
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-8187. - Resolution: Fixed Fix Version/s: 4.5.0 > webui: label.add.isolated.guest.network not found > -- > > Key: CLOUDSTACK-8187 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8187 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > When Creating Isolated Guest Network using UI, the notification display > ``label.add.isolated.guest.network`` instead text like "Creating isolated > guest network" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8232) UI: missing label: label.na
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion resolved CLOUDSTACK-8232. - Resolution: Fixed Fix Version/s: 4.5.0 > UI: missing label: label.na > --- > > Key: CLOUDSTACK-8232 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8232 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.5.0 >Reporter: Pierre-Luc Dion >Assignee: Pierre-Luc Dion >Priority: Trivial > Fix For: 4.5.0 > > > in the Details page of a Guest Network, the VPC ID display: 'label.na' > instead of 'N/A'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7482) Ajax calls in mgmt UI causing log pollution
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion resolved CLOUDSTACK-7482.
-
Resolution: Fixed
> Ajax calls in mgmt UI causing log pollution
> ---
>
> Key: CLOUDSTACK-7482
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7482
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.4.0
>Reporter: Kedron Touvell
>Assignee: Pierre-Luc Dion
>Priority: Minor
> Fix For: Future, 4.5.0
>
>
> Many of the ajax calls in the mgmt UI are specifying a listAll parameter,
> despite the fact that the underlying API call does not support listAll. This
> is causing a decent amount of log pollution:
> {quote}
> 2014-09-03 10:54:21,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-8:ctx-aefb6d5e ctx-08b63c18) Received unknown parameters for
> command listImageStores. Unknown parameters : listall type
> {quote}
> These parameters are set in {{ui/scripts/system.js}}, for example:
> {noformat}
> systemVmCount: function (data) {
> $.ajax({
> url: createURL('listSystemVms'),
> data: {
> listAll: true,
> {noformat}
> Here's the list of API calls that I see generating warnings:
> * listClusters
> * listHosts
> * listImageStores
> * listNetworkOfferings
> * listPods
> * listRegions
> * listServiceOfferings
> * listStoragePools
> * listSystemVms
> * listZones
> One more to add...listDomains is being called with a parentdomainid
> parameter, leading to the following warning:
> {quote}
> 2014-09-04 11:59:01,217 WARN [c.c.a.d.ParamGenericValidationWorker]
> (catalina-exec-5:ctx-c85dc843 ctx-647a43c1 ctx-bcd4e41b) Received unknown
> parameters for command listDomains. Unknown parameters : parentdomainid
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-2373) Docs page not found http://cloudstack.apache.org/docs/zh-CN/index.html
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-2373. --- Resolution: Fixed it's working. > Docs page not found http://cloudstack.apache.org/docs/zh-CN/index.html > -- > > Key: CLOUDSTACK-2373 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2373 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: zhifeng hu > > Docs page not found http://cloudstack.apache.org/docs/zh-CN/index.html > Not Found > The requested URL /docs/zh-CN/index.html was not found on this server. > Apache/2.4.4 (Unix) mod_wsgi/3.4 Python/2.7.3 OpenSSL/1.0.0g Server at > cloudstack.apache.org Port 80 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-4151) 4.5.5. About Password and Key Encryption unclear
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-4151. --- Resolution: Fixed Fix Version/s: 4.5.0 The section About Password and Key Encryption of the installation doc as been moved out of the installation precedure. > 4.5.5. About Password and Key Encryption unclear > > > Key: CLOUDSTACK-4151 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4151 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.1 > Environment: all >Reporter: Ron Wheeler >Assignee: Pierre-Luc Dion >Priority: Blocker > Fix For: 4.5.0 > > > 4.5.5. About Password and Key Encryption > The purpose of this section is a bit obcure. What is the reader supposed to > do with this information? > There seems to be a lot of magical activities here wherein keys and secrets > get stored in databases without any mention of how they get there. > There seems to be a list of items that are incrypted but no explaination > about what is the reader\'s role in this or who creates them or why you are > telling the reader this at this point in the process. > It might be clearer if " The data values are encrypted and decrypted using a > database secret key, which is stored in one of CloudStack’s internal > properties files along with the database password. The other encrypted values > listed above, such as SSH keys, are in the CloudStack internal database." > included some mention about how this happens and when and whether the reader > has to do something to make any of this happen correctly. > If it is really only informational and has nothing to do with the > installation process, it could be moved out of the flow and referenced as > something that terminally curious might wish to know. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-4351) [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading or premature note
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-4351. --- Resolution: Fixed the note as been removed. > [DOC] 4.3.2. Host/Hypervisor System Requirements has misleading or premature > note > -- > > Key: CLOUDSTACK-4351 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4351 > 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: All >Reporter: Ron Wheeler >Assignee: Pierre-Luc Dion > Fix For: 4.5.0 > > > Note > If DHCP is used for hosts, ensure that no conflict occurs between DHCP server > used for these hosts and the DHCP router created by CloudStack. > How can you do this at this point? > Cloudstack does not have a DHCP server at this point. > There is nothing for the user to do at this point. > It should be moved to closer to the point where the DHCP server addresses are > specified. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-2179) The url for downloading the maven 3.0.4 in INSTALL.md is not valid.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-2179. --- Resolution: Fixed this as been corrected. the link work. > The url for downloading the maven 3.0.4 in INSTALL.md is not valid. > --- > > Key: CLOUDSTACK-2179 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2179 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc > Environment: master >Reporter: Isaac Chiang >Priority: Minor > Labels: doc > > The resource link (line 26 in INSTALL.md) for maven 3.0.4 is no longer > available, need to relocate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-6952) Building from Source Doc needs updating
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-6952: --- Assignee: Pierre-Luc Dion > Building from Source Doc needs updating > --- > > Key: CLOUDSTACK-6952 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6952 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.4.0 > Environment: Ubuntu 12.04.4 >Reporter: Carlos Reategui >Assignee: Pierre-Luc Dion > > http://cloudstack-installation.readthedocs.org/en/latest/building_from_source.html > needs the following updates: > Building DEB packages section: > - maven 3 is now part of the standard precise repo. No need to add ppa. See > http://packages.ubuntu.com/precise/maven > - The pre-reqs say not to use tomcat 6.0.35 however tomcat6 default in 12.04 > is currently 6.0.35. I would have edited the doc in github but wasn't sure > what the preferred way to fix this one was. > - change mvn3 command to mvn. assumes above change to install default rather > than from ppa. > - 'mvn -P deps' gave me a warning that deps profile does not exist. > - 'dpkg-buildpackage -uc -us' fails tomcat6 dependency if one manually sets > up tomcat 6.0.33 since dpkg doesn't know about it. Need to add -d option, > however not sure how safe that is since other dependencies will not be > checked. > - packages are available in the parent path (i.e. ../*.deb) but the doc > doesn't mention that and therefore the commands to create the apt repo won't > work. Not sure if this is a difference since I built from git rather than > from the tar file linked in the doc. > Also should review https://github.com/apache/cloudstack/blob/4.4/INSTALL.md > and make sure it is consistent with this doc and some of the above apply to > it as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-6952) Building from Source Doc needs updating
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-6952. --- Resolution: Fixed fixed in 4.5.0 install doc > Building from Source Doc needs updating > --- > > Key: CLOUDSTACK-6952 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6952 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.4.0 > Environment: Ubuntu 12.04.4 >Reporter: Carlos Reategui >Assignee: Pierre-Luc Dion > > http://cloudstack-installation.readthedocs.org/en/latest/building_from_source.html > needs the following updates: > Building DEB packages section: > - maven 3 is now part of the standard precise repo. No need to add ppa. See > http://packages.ubuntu.com/precise/maven > - The pre-reqs say not to use tomcat 6.0.35 however tomcat6 default in 12.04 > is currently 6.0.35. I would have edited the doc in github but wasn't sure > what the preferred way to fix this one was. > - change mvn3 command to mvn. assumes above change to install default rather > than from ppa. > - 'mvn -P deps' gave me a warning that deps profile does not exist. > - 'dpkg-buildpackage -uc -us' fails tomcat6 dependency if one manually sets > up tomcat 6.0.33 since dpkg doesn't know about it. Need to add -d option, > however not sure how safe that is since other dependencies will not be > checked. > - packages are available in the parent path (i.e. ../*.deb) but the doc > doesn't mention that and therefore the commands to create the apt repo won't > work. Not sure if this is a difference since I built from git rather than > from the tar file linked in the doc. > Also should review https://github.com/apache/cloudstack/blob/4.4/INSTALL.md > and make sure it is consistent with this doc and some of the above apply to > it as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-1990) Docs: Update "Choosing a Hypervisor" feature matrix with new info
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-1990. --- Resolution: Fixed Fix Version/s: (was: 4.4.3) 4.5.0 does contain missing information. > Docs: Update "Choosing a Hypervisor" feature matrix with new info > - > > Key: CLOUDSTACK-1990 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1990 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Pierre-Luc Dion > Fix For: 4.5.0 > > > This section was added to the Installation Guide as a straight port from > older docs. It still needs someone to review it, remove outdated hypervisor > versions, and put in the additional hypervisors and versions that will be > supported in the next CloudStack release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-1359) Clarify what we mean by GB in CloudStack documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351766#comment-14351766 ] Pierre-Luc Dion commented on CLOUDSTACK-1359: - added this : in Create disk offering: Disk Size: Appears only if Custom Disk Size is not selected. Define the volume size in GB (2^30 1GB = 1,073,741,824 Bytes). http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/service_offerings.html#creating-a-new-disk-offering > Clarify what we mean by GB in CloudStack documentation > -- > > Key: CLOUDSTACK-1359 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1359 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0, 4.0.0 > Environment: Here is an example page with this issue: > http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/root_admin/createDiskOffering.html >Reporter: Mike Tutkowski >Assignee: Pierre-Luc Dion > Labels: documentation > Fix For: pre-4.0.0, 4.0.0 > > > On the example page above, the disksize field lists that that it is in GB. > For some people GB means 10 raised to the 9th power (1,000,000,000) bytes > while for others it means 2 raised to the 30th power (1,073,741,824) bytes. > Check out Wiki here: http://en.wikipedia.org/wiki/Gigabyte. > I recommend we clarify documents to indicate we are talking about a GB being > equal to 1,073,741,824 bytes (which is often known as a GiB). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-1359) Clarify what we mean by GB in CloudStack documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351778#comment-14351778 ] Pierre-Luc Dion commented on CLOUDSTACK-1359: - added to APIDOC: size of the disk offering in GB (1GB = 1,073,741,824 bytes) for createDiskOffering. > Clarify what we mean by GB in CloudStack documentation > -- > > Key: CLOUDSTACK-1359 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1359 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0, 4.0.0 > Environment: Here is an example page with this issue: > http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/root_admin/createDiskOffering.html >Reporter: Mike Tutkowski >Assignee: Pierre-Luc Dion > Labels: documentation > Fix For: pre-4.0.0, 4.0.0 > > > On the example page above, the disksize field lists that that it is in GB. > For some people GB means 10 raised to the 9th power (1,000,000,000) bytes > while for others it means 2 raised to the 30th power (1,073,741,824) bytes. > Check out Wiki here: http://en.wikipedia.org/wiki/Gigabyte. > I recommend we clarify documents to indicate we are talking about a GB being > equal to 1,073,741,824 bytes (which is often known as a GiB). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-1359) Clarify what we mean by GB in CloudStack documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-1359. --- Resolution: Fixed Fix Version/s: (was: pre-4.0.0) (was: 4.0.0) 4.6.0 Documentation updated on ACS 4.5.0 > Clarify what we mean by GB in CloudStack documentation > -- > > Key: CLOUDSTACK-1359 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1359 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: pre-4.0.0, 4.0.0 > Environment: Here is an example page with this issue: > http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/root_admin/createDiskOffering.html >Reporter: Mike Tutkowski >Assignee: Pierre-Luc Dion > Labels: documentation > Fix For: 4.6.0 > > > On the example page above, the disksize field lists that that it is in GB. > For some people GB means 10 raised to the 9th power (1,000,000,000) bytes > while for others it means 2 raised to the 30th power (1,073,741,824) bytes. > Check out Wiki here: http://en.wikipedia.org/wiki/Gigabyte. > I recommend we clarify documents to indicate we are talking about a GB being > equal to 1,073,741,824 bytes (which is often known as a GiB). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-2574) Release note pdf link
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-2574. --- Resolution: Fixed outdated issue > Release note pdf link > - > > Key: CLOUDSTACK-2574 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2574 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.2 >Reporter: Alireza Eskandari >Priority: Trivial > Original Estimate: 5m > Remaining Estimate: 5m > > PDF link for release note of 4.0.2 is not correct. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6166) Should we be recommending ASYNC NFS in documentation?
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351834#comment-14351834 ] Pierre-Luc Dion commented on CLOUDSTACK-6166: - There is a not about the async flag, at the end of this page: http://cloudstack-installation.readthedocs.org/en/latest/storage_setup.html sync is usually not performant which probably explain the reason for this configuration. > Should we be recommending ASYNC NFS in documentation? > - > > Key: CLOUDSTACK-6166 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6166 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: John Kinsella >Priority: Minor > > Looking at current and past installation, we recommend users export secondary > storage with async NFS: > /export *(rw,async,no_root_squash,no_subtree_check) > Generally async mode is considered risky from a data reliability point of > view (eg > http://serverfault.com/questions/328931/how-dangerous-is-nfs-async-when-raid-bbu-and-ups-are-present > ). > While advanced users will see this and ignore it, we probably shouldn't be > guiding new ACS users towards async NFS... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-5117) Update VPN docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-5117: --- Assignee: Pierre-Luc Dion > Update VPN docs > --- > > Key: CLOUDSTACK-5117 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5117 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley >Assignee: Pierre-Luc Dion > > There are differences in the VPN setup on Win8 - JLK has documented those > here: > http://theresnomon.co/2013/connecting-to-cloudstack-vpn-from-windows-8/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-5117) Update VPN docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-5117. --- Resolution: Fixed Fix Version/s: 4.5.0 http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/networking/using_remote_access.html > Update VPN docs > --- > > Key: CLOUDSTACK-5117 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5117 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: David Nalley >Assignee: Pierre-Luc Dion > Fix For: 4.5.0 > > > There are differences in the VPN setup on Win8 - JLK has documented those > here: > http://theresnomon.co/2013/connecting-to-cloudstack-vpn-from-windows-8/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-6166) Should we be recommending ASYNC NFS in documentation?
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-6166: --- Assignee: Pierre-Luc Dion > Should we be recommending ASYNC NFS in documentation? > - > > Key: CLOUDSTACK-6166 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6166 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: John Kinsella >Assignee: Pierre-Luc Dion >Priority: Minor > > Looking at current and past installation, we recommend users export secondary > storage with async NFS: > /export *(rw,async,no_root_squash,no_subtree_check) > Generally async mode is considered risky from a data reliability point of > view (eg > http://serverfault.com/questions/328931/how-dangerous-is-nfs-async-when-raid-bbu-and-ups-are-present > ). > While advanced users will see this and ignore it, we probably shouldn't be > guiding new ACS users towards async NFS... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-4844) Docs show incorrect URL for Windows password reset service download
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-4844. --- Resolution: Fixed documentation migrated to ReadTheDoc.org, the link is working. > Docs show incorrect URL for Windows password reset service download > --- > > Key: CLOUDSTACK-4844 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4844 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Demetrius Tsitrelis >Assignee: Travis Graham > Attachments: password-management-script-links.patch > > > In Section 12.13.2. Windows OS Installation of the admin guide, there is a > link to the CloudInstanceManager.msi. A slash is missing from the URL. Even > when the slash is added the referenced file does not seem to be in the > indicated location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-489) Document how to use userdata feature for user vms
[
https://issues.apache.org/jira/browse/CLOUDSTACK-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion reassigned CLOUDSTACK-489:
--
Assignee: Pierre-Luc Dion
> Document how to use userdata feature for user vms
> -
>
> Key: CLOUDSTACK-489
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-489
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
>Affects Versions: pre-4.0.0
> Environment: KVM, Xen, VMWare etc.
>Reporter: Rohit Yadav
>Assignee: Pierre-Luc Dion
> Fix For: Future
>
>
> The userdata should be a base64 encoded string upto 2KB which is put on
> domr's html directory and using HTTP GET the userdata information can be
> obtained from the domr. The operation does not require the VM to be in
> stopped state, though it is advised to stop and call this api in case the
> user vm has a script which gets the userdata information from domr while
> starting.
> It is fixed with 4c86b1545dda53b74c534d479133692331e12a28. We need to
> document it, how to use userdata, for example, this script can be used to
> fetch the data:
> server_ip=$(grep dhcp-server-identifier /var/lib/dhclient-eth0.leases |
> tail -1 | awk '{print $NF}' | tr '\;' ' ')
> wget http://${server_ip}/latest/user-data
>
> This feature can be useful, for example to use into puppet facts [1], or to
> do automation and horizontal scaling etc. based on userdata.
>
> [0]
> http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/domain_admin/updateVirtualMachine.html
> [1]
> http://geek.jasonhancock.com/2011/11/09/cloudstack-userdata-into-puppet-facts/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-489) Document how to use userdata feature for user vms
[
https://issues.apache.org/jira/browse/CLOUDSTACK-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Luc Dion closed CLOUDSTACK-489.
--
Resolution: Fixed
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/virtual_machines.html#user-data-and-meta-data
> Document how to use userdata feature for user vms
> -
>
> Key: CLOUDSTACK-489
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-489
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
>Affects Versions: pre-4.0.0
> Environment: KVM, Xen, VMWare etc.
>Reporter: Rohit Yadav
>Assignee: Pierre-Luc Dion
> Fix For: Future
>
>
> The userdata should be a base64 encoded string upto 2KB which is put on
> domr's html directory and using HTTP GET the userdata information can be
> obtained from the domr. The operation does not require the VM to be in
> stopped state, though it is advised to stop and call this api in case the
> user vm has a script which gets the userdata information from domr while
> starting.
> It is fixed with 4c86b1545dda53b74c534d479133692331e12a28. We need to
> document it, how to use userdata, for example, this script can be used to
> fetch the data:
> server_ip=$(grep dhcp-server-identifier /var/lib/dhclient-eth0.leases |
> tail -1 | awk '{print $NF}' | tr '\;' ' ')
> wget http://${server_ip}/latest/user-data
>
> This feature can be useful, for example to use into puppet facts [1], or to
> do automation and horizontal scaling etc. based on userdata.
>
> [0]
> http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/domain_admin/updateVirtualMachine.html
> [1]
> http://geek.jasonhancock.com/2011/11/09/cloudstack-userdata-into-puppet-facts/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-1605) No Documentation on Network Throttling
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-1605. --- Resolution: Fixed doc does exist: http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/service_offerings.html#network-throttling > No Documentation on Network Throttling > -- > > Key: CLOUDSTACK-1605 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1605 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.0.1 > Environment: KVM >Reporter: Brian Furry > > There is no documentation in the 4.0.0 or 4.0.1 Admin Guide on network > throttling (network.throttling.rate and vm.network.throttling.rate global > settings). > Is this throttling done at the hypervisor? What hypervisors does this feature > work with? Does it work with KVM? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-2100) Need tooltips for new VM Snapshot dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-2100: Fix Version/s: 4.6.0 > Need tooltips for new VM Snapshot dialog > > > Key: CLOUDSTACK-2100 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2100 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, UI >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Priority: Minor > Fix For: 4.6.0 > > > In the new Take VM Snapshot dialog (Instances - instance name - Take VM > Snapshot button) there are no popup tooltips to describe the fields and the > checkbox. > Also, it would be useful to note in the dialog text somewhere that "The VM > file system will not be quiesced" since this is an important limitation when > you're using this dialog. > Some suggested text for the tooltips: > Name: (Optional) Give the snapshot a name. A unique name will be > automatically generated if you leave this blank. > Description: (Optional) Notes or comments about the snapshot. > Snapshot memory: Check this to include CPU/memory state. If not checked, the > snapshot includes only data volumes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-2100) Need tooltips for new VM Snapshot dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-2100: --- Assignee: Pierre-Luc Dion > Need tooltips for new VM Snapshot dialog > > > Key: CLOUDSTACK-2100 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2100 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, UI >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Pierre-Luc Dion >Priority: Minor > Fix For: 4.6.0 > > > In the new Take VM Snapshot dialog (Instances - instance name - Take VM > Snapshot button) there are no popup tooltips to describe the fields and the > checkbox. > Also, it would be useful to note in the dialog text somewhere that "The VM > file system will not be quiesced" since this is an important limitation when > you're using this dialog. > Some suggested text for the tooltips: > Name: (Optional) Give the snapshot a name. A unique name will be > automatically generated if you leave this blank. > Description: (Optional) Notes or comments about the snapshot. > Snapshot memory: Check this to include CPU/memory state. If not checked, the > snapshot includes only data volumes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-2100) Need tooltips for new VM Snapshot dialog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-2100. --- Resolution: Fixed commit 002236e489047508e8483034f42981c9fbad1f04 > Need tooltips for new VM Snapshot dialog > > > Key: CLOUDSTACK-2100 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2100 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, UI >Affects Versions: 4.2.0 >Reporter: Jessica Tomechak >Assignee: Pierre-Luc Dion >Priority: Minor > Fix For: 4.6.0 > > > In the new Take VM Snapshot dialog (Instances - instance name - Take VM > Snapshot button) there are no popup tooltips to describe the fields and the > checkbox. > Also, it would be useful to note in the dialog text somewhere that "The VM > file system will not be quiesced" since this is an important limitation when > you're using this dialog. > Some suggested text for the tooltips: > Name: (Optional) Give the snapshot a name. A unique name will be > automatically generated if you leave this blank. > Description: (Optional) Notes or comments about the snapshot. > Snapshot memory: Check this to include CPU/memory state. If not checked, the > snapshot includes only data volumes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-3008) Section 4.5.3.2 of the 4.1.0 documentation is incorrect cloud-client does not seem to exist
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-3008. --- Resolution: Won't Fix documentation too old. > Section 4.5.3.2 of the 4.1.0 documentation is incorrect cloud-client does not > seem to exist > --- > > Key: CLOUDSTACK-3008 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3008 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 > Environment: Ubuntu Precise >Reporter: Gary Richards >Priority: Minor > Labels: documentation > > Section 4.5.3.2 of the 4.1.0 documentation is incorrect, the package > cloud-client does not seem to exist. > Further along in the documentation I located the suggestion that I use the > cloudstack-setup-databases tool. > I tracked this down to the cloudstack-management package. Which I would guess > is probably what the documentation should now say. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-2896) pt-BR docs without index.html
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion closed CLOUDSTACK-2896. --- Resolution: Won't Fix documentation move on readthedocs.org > pt-BR docs without index.html > - > > Key: CLOUDSTACK-2896 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2896 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 > Environment: Environment: Windows Vista, Google Chrome Browser, > Locale pt-BR >Reporter: Ricardo Katz >Priority: Trivial > Fix For: 4.1.0 > > > On pt-BR the index.html from the 'docs' doesn't exists yet. As it grabs the > locale from my browser it redirects me to > http://cloudstack.apache.org/docs/pt-BR/index.html which doesn't exists, but > the rest > (http://cloudstack.apache.org/docs/pt-BR/Apache_CloudStack/4.1.0/html/Admin_Guide/index.html) > is there -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-3990) Change host password documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion reassigned CLOUDSTACK-3990: --- Assignee: Pierre-Luc Dion > Change host password documentation > -- > > Key: CLOUDSTACK-3990 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3990 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Kirk Jantzer >Assignee: Pierre-Luc Dion >Priority: Minor > Labels: documentation > > http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Admin_Guide/change-host-password.html > This document says to update the password column, which doesn't exist in the > host table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3990) Change host password documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Luc Dion updated CLOUDSTACK-3990: Fix Version/s: 4.5.0 > Change host password documentation > -- > > Key: CLOUDSTACK-3990 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3990 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Kirk Jantzer >Assignee: Pierre-Luc Dion >Priority: Minor > Labels: documentation > Fix For: 4.5.0 > > > http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Admin_Guide/change-host-password.html > This document says to update the password column, which doesn't exist in the > host table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
