[jira] [Updated] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-7671: - Priority: Blocker (was: Major) > [RHEL7] management server failed to start once machine is rebooted > -- > > Key: CLOUDSTACK-7671 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Damodar Reddy T >Assignee: Rohit Yadav >Priority: Blocker > > Repro stesp: > Create a rhel 7 host > Install MS > Start MS > Once MS is up and running . Reboot MS . Notice Cloudstack-management service > status > Bug: > Notice MS fails to start even after calling service cloudstack-management > restart it failed to start > systemctl status cloudstack-management.service > cloudstack-management.service - Citrix Cloud Plaltform >Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled) >Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min > 28s ago > Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, > status=1/FAILURE) > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... > Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: > /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission > denied > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: > control process exited, code=exited status=1 > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud > Plaltform. > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit > cloudstack-management.service entered failed state. > [root@Rack1Pod1Host27 run]# > service cloudstack-management status > Redirecting to /bin/systemctl status cloudstack-management.service > cloudstack-management.service - Citrix Cloud Plaltform >Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled) >Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s > ago > Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, > status=1/FAILURE) > Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: > /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission > denied > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: > control process exited, code=exited status=1 > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud > Plaltform. > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit > cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7671) [RHEL7] management server failed to start once machine is rebooted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-7671: - Assignee: (was: Damodar Reddy T) > [RHEL7] management server failed to start once machine is rebooted > -- > > Key: CLOUDSTACK-7671 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7671 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Damodar Reddy T > > Repro stesp: > Create a rhel 7 host > Install MS > Start MS > Once MS is up and running . Reboot MS . Notice Cloudstack-management service > status > Bug: > Notice MS fails to start even after calling service cloudstack-management > restart it failed to start > systemctl status cloudstack-management.service > cloudstack-management.service - Citrix Cloud Plaltform >Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled) >Active: failed (Result: exit-code) since Tue 2014-09-23 12:10:09 IST; 1min > 28s ago > Process: 4618 ExecStart=/usr/sbin/cloudstack-management start (code=exited, > status=1/FAILURE) > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Starting Citrix Cloud Plaltform... > Sep 23 12:10:09 Rack1Pod1Host27 cloudstack-management[4618]: > /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission > denied > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: > control process exited, code=exited status=1 > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud > Plaltform. > Sep 23 12:10:09 Rack1Pod1Host27 systemd[1]: Unit > cloudstack-management.service entered failed state. > [root@Rack1Pod1Host27 run]# > service cloudstack-management status > Redirecting to /bin/systemctl status cloudstack-management.service > cloudstack-management.service - Citrix Cloud Plaltform >Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service; > enabled) >Active: failed (Result: exit-code) since Tue 2014-09-23 12:14:05 IST; 8s > ago > Process: 4691 ExecStart=/usr/sbin/cloudstack-management start (code=exited, > status=1/FAILURE) > Sep 23 12:14:05 Rack1Pod1Host27 cloudstack-management[4691]: > /usr/sbin/tomcat: line 50: /var/run/cloudstack-management.pid: Permission > denied > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: cloudstack-management.service: > control process exited, code=exited status=1 > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Failed to start Citrix Cloud > Plaltform. > Sep 23 12:14:05 Rack1Pod1Host27 systemd[1]: Unit > cloudstack-management.service entered failed state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14246918#comment-14246918 ] David Nalley commented on CLOUDSTACK-8042: -- Is this still an issue? > 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 > 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-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 ] David Nalley updated CLOUDSTACK-8042: - Priority: Blocker (was: Major) > 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 > 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] [Commented] (CLOUDSTACK-7151) vmware: Type of vSwitch was not detected correctly while preparing public/guest virtual networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229935#comment-14229935 ] David Nalley commented on CLOUDSTACK-7151: -- I am going to drop this as a blocker. We released 4.3.x and 4.4.x without this being an issue. It seems no one cares enough to fix it. > vmware: Type of vSwitch was not detected correctly while preparing > public/guest virtual networks > > > Key: CLOUDSTACK-7151 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7151 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.3.0, 4.3.1 > Environment: VMware ESXi 5.0 > ACS 4.3.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.5.0 > > > After upgrade to 4.3.0 from 4.2.0 system vms are not able to start. > 2014-07-18 07:14:16,732 INFO [c.c.h.v.r.VmwareResource] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Prepare > network on vmwaresvs Public_Guest_Net with name prefix: cloud.public > 2014-07-18 07:14:16,778 ERROR [c.c.h.v.m.HypervisorHostHelper] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Unable to > find vSwitchPublic_Guest_Net > 2014-07-18 07:14:16,778 WARN [c.c.h.v.r.VmwareResource] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) StartCommand > failed due to Exception: java.lang.Exception > Message: Unable to find vSwitchPublic_Guest_Net -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7151) vmware: Type of vSwitch was not detected correctly while preparing public/guest virtual networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-7151: - Priority: Major (was: Blocker) > vmware: Type of vSwitch was not detected correctly while preparing > public/guest virtual networks > > > Key: CLOUDSTACK-7151 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7151 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.3.0, 4.3.1 > Environment: VMware ESXi 5.0 > ACS 4.3.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Fix For: 4.5.0 > > > After upgrade to 4.3.0 from 4.2.0 system vms are not able to start. > 2014-07-18 07:14:16,732 INFO [c.c.h.v.r.VmwareResource] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Prepare > network on vmwaresvs Public_Guest_Net with name prefix: cloud.public > 2014-07-18 07:14:16,778 ERROR [c.c.h.v.m.HypervisorHostHelper] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Unable to > find vSwitchPublic_Guest_Net > 2014-07-18 07:14:16,778 WARN [c.c.h.v.r.VmwareResource] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) StartCommand > failed due to Exception: java.lang.Exception > Message: Unable to find vSwitchPublic_Guest_Net -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7626) SAMLUtilsTest failing inconsistently during build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed CLOUDSTACK-7626. Resolution: Fixed This (at least on jenkins.bacd) is not failing. > SAMLUtilsTest failing inconsistently during build > --- > > Key: CLOUDSTACK-7626 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7626 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.5.0 > Environment: 4.5 >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.5.0 > > > 4.5 build failing inconsistently while running unit test, unning > org.apache.cloudstack.utils.auth.SAMLUtilsTest > I have seen this issue multiple times, after the some merge happened 2 week > ago, > > Build fails with below error > [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-utils --- > [INFO] Surefire report directory: > /root/jenkins/build/workspace/CloudPlatform-4.x-rhel63_Simulator/internal-cloudstack/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/utils/target/surefire-reports > --- > T E S T S > --- > Running org.apache.cloudstack.utils.auth.SAMLUtilsTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.245 sec > Running com.cloud.utils.TestProfiler > Configure log4j with default properties > 2014-09-24 03:38:16,415 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() started > 2014-09-24 03:38:17,417 INFO [cloud.utils.TestProfiler] (main:) Duration : > 1000 > 2014-09-24 03:38:17,419 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() stopped > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.012 sec > Running com.cloud.utils.ScriptTest > 2014-09-24 03:38:17,526 DEBUG [utils.script.Script] (main:) Executing: > /bin/echo bar > 2014-09-24 03:38:17,537 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) Looking for pwd > in the classpath > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) System resource: > null > 2014-09-24 03:38:17,546 DEBUG [utils.script.Script] (main:) Classpath > resource: null > 2014-09-24 03:38:17,549 DEBUG [utils.script.Script] (main:) Executing: > /bin/bash -c echo 'hello world!' > 2014-09-24 03:38:17,551 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,551 WARN [utils.script.Script] (main:) Exception: > /bin/bash -c echo 'hello world!' > java.lang.IllegalArgumentException > at com.cloud.utils.ScriptTest$1.interpret(ScriptTest.java:107) > at com.cloud.utils.script.Script.execute(Script.java:220) > at > com.cloud.utils.ScriptTest.executeWithOutputInterpreter(ScriptTest.java:103) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl
[jira] [Commented] (CLOUDSTACK-7642) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208506#comment-14208506 ] David Nalley commented on CLOUDSTACK-7642: -- [~devdeep] Is this still an issue? Any idea on timeline for a fix? > [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 > with Xenserver HV. > -- > > Key: CLOUDSTACK-7642 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7642 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Upgrade >Affects Versions: 4.5.0 > Environment: upgrade from 4.3.0 to 4.5 using Xen server 6.2 >Reporter: manasaveloori >Assignee: Devdeep Singh >Priority: Blocker > Fix For: 4.5.0 > > Attachments: management-server.rar, mysqldump4.5.rar, > mysqldumpBeforeUp.rar > > > 1. Deployed 4.3.0 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0 > build. > 2. Registered the 4.5 template as "systemvm-xenserver-4.5" > 3. Upgraded to 4.5 and started the MS. > Observation: > Observed the following exception in MS logs .Hosts went into disconnected > stated. > 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] > (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host > 1(Rack1Pod1Host29) > 2014-09-29 13:45:26,851 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager > Timer:ctx-7b268e53) Unable to find class > com.cloud.hypervisor.xen.resource.XenServer620Resource > java.lang.ClassNotFoundException: > com.cloud.hypervisor.xen.resource.XenServer620Resource > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:186) > at > com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89) > at > com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150) > at > com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:235) > at > org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) > 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.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > 2014-09-29 13:45:26,852 WARN [c.c.a.m.AgentManagerImpl] > (ClusteredAgentManager Timer:ctx-7b268e53) Unable to load the resource: 1 > 2014-09-29 13:45:26,853 DEBUG [c.c.h.Status] (ClusteredAgentManager > Timer:ctx-7b268e53) Transition:[Resource state = Enabled, Agent event = > AgentDisconnected, Host id = 1, name = Rack1Pod1Host29] > Attaching the dumps and logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7151) vmware: Type of vSwitch was not detected correctly while preparing public/guest virtual networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206783#comment-14206783 ] David Nalley commented on CLOUDSTACK-7151: -- [~sateeshc] is this still an issue? There hasn't been movement on this bug in months. > vmware: Type of vSwitch was not detected correctly while preparing > public/guest virtual networks > > > Key: CLOUDSTACK-7151 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7151 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.3.0, 4.3.1 > Environment: VMware ESXi 5.0 > ACS 4.3.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.5.0 > > > After upgrade to 4.3.0 from 4.2.0 system vms are not able to start. > 2014-07-18 07:14:16,732 INFO [c.c.h.v.r.VmwareResource] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Prepare > network on vmwaresvs Public_Guest_Net with name prefix: cloud.public > 2014-07-18 07:14:16,778 ERROR [c.c.h.v.m.HypervisorHostHelper] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Unable to > find vSwitchPublic_Guest_Net > 2014-07-18 07:14:16,778 WARN [c.c.h.v.r.VmwareResource] > (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) StartCommand > failed due to Exception: java.lang.Exception > Message: Unable to find vSwitchPublic_Guest_Net -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7626) SAMLUtilsTest failing inconsistently during build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169284#comment-14169284 ] David Nalley commented on CLOUDSTACK-7626: -- [~bhaisaab] Can you take a look at this? > SAMLUtilsTest failing inconsistently during build > --- > > Key: CLOUDSTACK-7626 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7626 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.5.0 > Environment: 4.5 >Reporter: Rayees Namathponnan >Priority: Blocker > Fix For: 4.5.0 > > > 4.5 build failing inconsistently while running unit test, unning > org.apache.cloudstack.utils.auth.SAMLUtilsTest > I have seen this issue multiple times, after the some merge happened 2 week > ago, > > Build fails with below error > [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-utils --- > [INFO] Surefire report directory: > /root/jenkins/build/workspace/CloudPlatform-4.x-rhel63_Simulator/internal-cloudstack/dist/rpmbuild/BUILD/cloudstack-4.5.0-SNAPSHOT/utils/target/surefire-reports > --- > T E S T S > --- > Running org.apache.cloudstack.utils.auth.SAMLUtilsTest > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.245 sec > Running com.cloud.utils.TestProfiler > Configure log4j with default properties > 2014-09-24 03:38:16,415 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() started > 2014-09-24 03:38:17,417 INFO [cloud.utils.TestProfiler] (main:) Duration : > 1000 > 2014-09-24 03:38:17,419 INFO [cloud.utils.TestProfiler] (main:) > testProfiler() stopped > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.012 sec > Running com.cloud.utils.ScriptTest > 2014-09-24 03:38:17,526 DEBUG [utils.script.Script] (main:) Executing: > /bin/echo bar > 2014-09-24 03:38:17,537 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) Looking for pwd > in the classpath > 2014-09-24 03:38:17,545 DEBUG [utils.script.Script] (main:) System resource: > null > 2014-09-24 03:38:17,546 DEBUG [utils.script.Script] (main:) Classpath > resource: null > 2014-09-24 03:38:17,549 DEBUG [utils.script.Script] (main:) Executing: > /bin/bash -c echo 'hello world!' > 2014-09-24 03:38:17,551 DEBUG [utils.script.Script] (main:) Execution is > successful. > 2014-09-24 03:38:17,551 WARN [utils.script.Script] (main:) Exception: > /bin/bash -c echo 'hello world!' > java.lang.IllegalArgumentException > at com.cloud.utils.ScriptTest$1.interpret(ScriptTest.java:107) > at com.cloud.utils.script.Script.execute(Script.java:220) > at > com.cloud.utils.ScriptTest.executeWithOutputInterpreter(ScriptTest.java:103) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl
[jira] [Updated] (CLOUDSTACK-6156) Retired maven repo breaking awsapi build and RPM packaging
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-6156: - Priority: Blocker (was: Critical) > Retired maven repo breaking awsapi build and RPM packaging > -- > > Key: CLOUDSTACK-6156 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6156 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Affects Versions: 4.2.0, 4.3.0 >Reporter: John Kinsella >Assignee: John Kinsella >Priority: Blocker > > The awsapi sub-project depends on several jars from Apache Axis-Rampart. > The Rampart poms have a broken maven repo hard-coded into them: > http://shibboleth.internet2.edu/downloads/maven2/ > Which does not return a 404 when maven attempts to fetch a jar, but HTTP 200. > *golf clap* > Rampart is aware of this (see RAMPART-393) but the fix won't be released > until version 1.7, whenever that is. > CLOUDSTACK-744 shows we hit this before for opensaml, although I'm not sure > when the rampart jars started erroring out. > From my research so far, looks like rampart isn't being used and the rampart > dependencies can be removed from the pom... > Steps to reproduce (On a clean system with no cached maven repo, and not > using a maven repo mirror): > mvn -P awsapi > Expected results: > Happily built awsapi package > Actual results: > ... > Downloaded: > http://repo.maven.apache.org/maven2/org/apache/rampart/rampart-policy/1.5.1/rampart-policy-1.5.1.pom > (3 KB at 116.1 KB/sec) > Downloading: > http://shibboleth.internet2.edu/downloads/maven2/org/apache/rampart/rampart-policy/1.5.1/rampart-policy-1.5.1.pom > Feb 21, 2014 12:18:31 PM > org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies > processCookies > WARNING: Invalid cookie header: "Set-Cookie: django_language=en-us; > expires=time.struct_time(tm_year=2015, tm_mon=2, tm_mday=21, tm_hour=15, > tm_min=18, tm_sec=33, tm_wday=5, tm_yday=52, tm_isdst=0); Max-Age=31536000; > Path=/". Unable to parse expires attribute: time.struct_time(tm_year=2015, > tm_mon=2, tm_mday=21, tm_hour=15, tm_min=18, tm_sec=33, tm_wday=5, > tm_yday=52, tm_isdst=0) > Feb 21, 2014 12:18:32 PM > org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies > processCookies > WARNING: Invalid cookie header: "Set-Cookie: django_language=en-us; > expires=time.struct_time(tm_year=2015, tm_mon=2, tm_mday=21, tm_hour=15, > tm_min=18, tm_sec=33, tm_wday=5, tm_yday=52, tm_isdst=0); Max-Age=31536000; > Path=/". Unable to parse expires attribute: time.struct_time(tm_year=2015, > tm_mon=2, tm_mday=21, tm_hour=15, tm_min=18, tm_sec=33, tm_wday=5, > tm_yday=52, tm_isdst=0) > Feb 21, 2014 12:18:32 PM > org.apache.maven.wagon.providers.http.httpclient.client.protocol.ResponseProcessCookies > processCookies > ... > [WARNING] Invalid POM for org.apache.rampart:rampart-policy:jar:1.5.1, > transitive dependencies (if any) will not be available, enable debug logging > for more details > etc, etc -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6149) Don't specify a repository in pom
David Nalley created CLOUDSTACK-6149: Summary: Don't specify a repository in pom Key: CLOUDSTACK-6149 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6149 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Contrail Affects Versions: 4.3.0 Reporter: David Nalley Contrail's pom has this: cloud-plugin-network-contrail Apache CloudStack Plugin - Network Juniper Contrail org.apache.cloudstack cloudstack-plugins 4.3.0 ../../pom.xml juniper-contrail http://juniper.github.io/contrail-maven/snapshots Hardcoding a repository is a bad idea for many reasons; please don't do it. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5438) Missing RPM dependency
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-5438. -- Resolution: Fixed Fix Version/s: Future Thanks for the patch Alex. applied to 4.3 forward (78f62c63479a81383ff8957a12c88ee4c181cfda) and master (a9c25dcfa363005beddf830267f54e85835c4af6) Please use the full ID of the bug in the future as that allows the automation to update both the bug and ReviewBoard (e.g. use CloudStack-5438 instead of CS-5438) > Missing RPM dependency > -- > > Key: CLOUDSTACK-5438 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5438 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Virtual Router >Affects Versions: 4.2.0 > Environment: CentOS 6 x86_64 >Reporter: Nux >Assignee: Alexander Hitchins > Labels: kvm,, rpm,, vr > Fix For: Future > > > Hello, > On CS 4.2 with KVM on CentOS the cloudstack-agent RPM should have > openssh-clients as a dependency, otherwise the host cannot contact the > Virtual Router, making it's deployment impossible. > A minimal CentOS deployment comes without this package and I would guess many > start from a minimal deployment. > This is probably also valid for Debian/Ubuntu. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5902) Database upgrade fails, 4.2.1 to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-5902: - Component/s: Upgrade > Database upgrade fails, 4.2.1 to 4.3 > > > Key: CLOUDSTACK-5902 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5902 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Upgrade >Affects Versions: 4.3.0 > Environment: CentOS 6.5 64bit >Reporter: Nux >Priority: Blocker > Labels: database, management, server > > Yum update completes nicely, but upon restart the management server fails to > upgrade the DB: > "Duplicate column name 'related'" > http://paste.fedoraproject.org/69630/59802139/raw/ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5902) Database upgrade fails, 4.2.1 to 4.3
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-5902: - Priority: Blocker (was: Major) > Database upgrade fails, 4.2.1 to 4.3 > > > Key: CLOUDSTACK-5902 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5902 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Upgrade >Affects Versions: 4.3.0 > Environment: CentOS 6.5 64bit >Reporter: Nux >Priority: Blocker > Labels: database, management, server > > Yum update completes nicely, but upon restart the management server fails to > upgrade the DB: > "Duplicate column name 'related'" > http://paste.fedoraproject.org/69630/59802139/raw/ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-4912) API docs are missing some APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875374#comment-13875374 ] David Nalley commented on CLOUDSTACK-4912: -- Yes, this shouldn't block the release. I'll get the issue updated in documentation and maybe the script as well. --David > API docs are missing some APIs > -- > > Key: CLOUDSTACK-4912 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4912 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Doc >Affects Versions: 4.2.0, 4.3.0 >Reporter: Demetrius Tsitrelis >Assignee: David Nalley >Priority: Critical > Fix For: 4.3.0 > > > I grep’ed the source code and came up with a list of the APIs which the UI > uses. Many of them (addNetscalerLoadBalancer, addVmwareDc, etc.) are not in > the generated API documentation which appears at > http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html > Here’s the list of APIs used by the UI: > activateProject > addAccountToProject > addBaremetalDhcp > addBaremetalPxeKickStartServer > addCluster > addHost > addImageStore > addIpToNic > addLdapConfiguration > addNetscalerLoadBalancer > addNetworkServiceProvider > addNicToVirtualMachine > addRegion > addTrafficType > addUcsManager > addVmwareDc > addVpnUser > archiveAlerts > archiveEvents > assignToGlobalLoadBalancerRule > assignToLoadBalancerRule > assignVirtualMachine > associateIpAddress > associateUcsProfileToBlade > attachIso > attachVolume > authorizeSecurityGroupEgress > authorizeSecurityGroupIngress > cancelHostMaintenance > cancelStorageMaintenance > configureInternalLoadBalancerElement > configureVirtualRouterElement > copyIso > copyTemplate > createAccount > createAffinityGroup > createAutoScalePolicy > createAutoScaleVmGroup > createAutoScaleVmProfile > createCondition > createDiskOffering > createDomain > createEgressFirewallRule > createFirewallRule > createGlobalLoadBalancerRule > createIpForwardingRule > createLBHealthCheckPolicy > createLBStickinessPolicy > createLoadBalancer > createLoadBalancerRule > createNetwork > createNetworkACL > createNetworkACLList > createNetworkOffering > createPhysicalNetwork > createPod > createPortableIpRange > createPortForwardingRule > createPrivateGateway > createProject > createRemoteAccessVpn > createSecondaryStagingStore > createSecurityGroup > createServiceOffering > createSnapshot > createSnapshotPolicy > createStaticRoute > createStorageNetworkIpRange > createStoragePool > createTags > createTemplate > createUser > createVlanIpRange > createVMSnapshot > createVolume > createVPC > createVpnConnection > createVpnCustomerGateway > createVpnGateway > createZone > dedicateCluster > dedicateGuestVlanRange > dedicateHost > dedicatePod > dedicatePublicIpRange > dedicateZone > deleteAccount > deleteAccountFromProject > deleteAffinityGroup > deleteAlerts > deleteBigSwitchVnsDevice > deleteCiscoNexusVSM > deleteCluster > deleteCondition > deleteDiskOffering > deleteDomain > deleteEgressFirewallRule > deleteEvents > deleteF5LoadBalancer > deleteFirewallRule > deleteGlobalLoadBalancerRule > deleteHost > deleteImageStore > deleteIpForwardingRule > deleteIso > deleteLBHealthCheckPolicy > deleteLBStickinessPolicy > deleteLdapConfiguration > deleteLoadBalancer > deleteLoadBalancerRule > deleteNetscalerLoadBalancer > deleteNetwork > deleteNetworkACL > deleteNetworkACLList > deleteNetworkOffering > deleteNetworkServiceProvider > deleteNiciraNvpDevice > deletePhysicalNetwork > deletePod > deletePortableIpRange > deletePortForwardingRule > deletePrivateGateway > deleteProject > deleteProjectInvitation > deleteRemoteAccessVpn > deleteSecondaryStagingStore > deleteSecurityGroup > deleteServiceOffering > deleteSnapshot > deleteSnapshotPolicies > deleteSrxFirewall > deleteStaticRoute > deleteStorageNetworkIpRange > deleteStoragePool > deleteTags > deleteTemplate > deleteUcsManager > deleteUser > deleteVlanIpRange > deleteVMSnapshot > deleteVolume > deleteVPC > deleteVpnConnection > deleteVpnCustomerGateway > deleteVpnGateway > deleteZone > deployVirtualMachine > destroyRouter > destroySystemVm > destroyVirtualMachine > detachIso > detachVolume > disableAccount > disableAutoScaleVmGroup > disableCiscoNexusVSM > disableStaticNat > disableUser > disassociateIpAddress > disassociateUcsProfileFromBlade > enableAccount > enableAutoScaleVmGroup > enableCiscoNexusVSM > enableStaticNat > enableStorageMaintenance > enableUser > extractVolume > findHostsForMigration > findStoragePoolsForMigration > ldapCreateAccount > listAccounts > listAffinityGroups > listAffinityGroupTypes > listAlerts > listAutoScaleVmGroups > listAutoScaleVmProfiles > listBaremetalDhcp > listBaremetalPxeServers > listBi
[jira] [Updated] (CLOUDSTACK-4912) API docs are missing some APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-4912: - Priority: Critical (was: Blocker) > API docs are missing some APIs > -- > > Key: CLOUDSTACK-4912 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4912 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Doc >Affects Versions: 4.2.0, 4.3.0 >Reporter: Demetrius Tsitrelis >Assignee: David Nalley >Priority: Critical > Fix For: 4.3.0 > > > I grep’ed the source code and came up with a list of the APIs which the UI > uses. Many of them (addNetscalerLoadBalancer, addVmwareDc, etc.) are not in > the generated API documentation which appears at > http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html > Here’s the list of APIs used by the UI: > activateProject > addAccountToProject > addBaremetalDhcp > addBaremetalPxeKickStartServer > addCluster > addHost > addImageStore > addIpToNic > addLdapConfiguration > addNetscalerLoadBalancer > addNetworkServiceProvider > addNicToVirtualMachine > addRegion > addTrafficType > addUcsManager > addVmwareDc > addVpnUser > archiveAlerts > archiveEvents > assignToGlobalLoadBalancerRule > assignToLoadBalancerRule > assignVirtualMachine > associateIpAddress > associateUcsProfileToBlade > attachIso > attachVolume > authorizeSecurityGroupEgress > authorizeSecurityGroupIngress > cancelHostMaintenance > cancelStorageMaintenance > configureInternalLoadBalancerElement > configureVirtualRouterElement > copyIso > copyTemplate > createAccount > createAffinityGroup > createAutoScalePolicy > createAutoScaleVmGroup > createAutoScaleVmProfile > createCondition > createDiskOffering > createDomain > createEgressFirewallRule > createFirewallRule > createGlobalLoadBalancerRule > createIpForwardingRule > createLBHealthCheckPolicy > createLBStickinessPolicy > createLoadBalancer > createLoadBalancerRule > createNetwork > createNetworkACL > createNetworkACLList > createNetworkOffering > createPhysicalNetwork > createPod > createPortableIpRange > createPortForwardingRule > createPrivateGateway > createProject > createRemoteAccessVpn > createSecondaryStagingStore > createSecurityGroup > createServiceOffering > createSnapshot > createSnapshotPolicy > createStaticRoute > createStorageNetworkIpRange > createStoragePool > createTags > createTemplate > createUser > createVlanIpRange > createVMSnapshot > createVolume > createVPC > createVpnConnection > createVpnCustomerGateway > createVpnGateway > createZone > dedicateCluster > dedicateGuestVlanRange > dedicateHost > dedicatePod > dedicatePublicIpRange > dedicateZone > deleteAccount > deleteAccountFromProject > deleteAffinityGroup > deleteAlerts > deleteBigSwitchVnsDevice > deleteCiscoNexusVSM > deleteCluster > deleteCondition > deleteDiskOffering > deleteDomain > deleteEgressFirewallRule > deleteEvents > deleteF5LoadBalancer > deleteFirewallRule > deleteGlobalLoadBalancerRule > deleteHost > deleteImageStore > deleteIpForwardingRule > deleteIso > deleteLBHealthCheckPolicy > deleteLBStickinessPolicy > deleteLdapConfiguration > deleteLoadBalancer > deleteLoadBalancerRule > deleteNetscalerLoadBalancer > deleteNetwork > deleteNetworkACL > deleteNetworkACLList > deleteNetworkOffering > deleteNetworkServiceProvider > deleteNiciraNvpDevice > deletePhysicalNetwork > deletePod > deletePortableIpRange > deletePortForwardingRule > deletePrivateGateway > deleteProject > deleteProjectInvitation > deleteRemoteAccessVpn > deleteSecondaryStagingStore > deleteSecurityGroup > deleteServiceOffering > deleteSnapshot > deleteSnapshotPolicies > deleteSrxFirewall > deleteStaticRoute > deleteStorageNetworkIpRange > deleteStoragePool > deleteTags > deleteTemplate > deleteUcsManager > deleteUser > deleteVlanIpRange > deleteVMSnapshot > deleteVolume > deleteVPC > deleteVpnConnection > deleteVpnCustomerGateway > deleteVpnGateway > deleteZone > deployVirtualMachine > destroyRouter > destroySystemVm > destroyVirtualMachine > detachIso > detachVolume > disableAccount > disableAutoScaleVmGroup > disableCiscoNexusVSM > disableStaticNat > disableUser > disassociateIpAddress > disassociateUcsProfileFromBlade > enableAccount > enableAutoScaleVmGroup > enableCiscoNexusVSM > enableStaticNat > enableStorageMaintenance > enableUser > extractVolume > findHostsForMigration > findStoragePoolsForMigration > ldapCreateAccount > listAccounts > listAffinityGroups > listAffinityGroupTypes > listAlerts > listAutoScaleVmGroups > listAutoScaleVmProfiles > listBaremetalDhcp > listBaremetalPxeServers > listBigSwitchVnsDevices > listCapabilities > listCapacity > listCiscoNexusVSMs > listClusters > listConfigurations > listCounters > listDedicatedClu
[jira] [Updated] (CLOUDSTACK-4912) API docs are missing some APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-4912: - Priority: Blocker (was: Major) > API docs are missing some APIs > -- > > Key: CLOUDSTACK-4912 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4912 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Doc >Affects Versions: 4.2.0, 4.3.0 >Reporter: Demetrius Tsitrelis >Priority: Blocker > > I grep’ed the source code and came up with a list of the APIs which the UI > uses. Many of them (addNetscalerLoadBalancer, addVmwareDc, etc.) are not in > the generated API documentation which appears at > http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html > Here’s the list of APIs used by the UI: > activateProject > addAccountToProject > addBaremetalDhcp > addBaremetalPxeKickStartServer > addCluster > addHost > addImageStore > addIpToNic > addLdapConfiguration > addNetscalerLoadBalancer > addNetworkServiceProvider > addNicToVirtualMachine > addRegion > addTrafficType > addUcsManager > addVmwareDc > addVpnUser > archiveAlerts > archiveEvents > assignToGlobalLoadBalancerRule > assignToLoadBalancerRule > assignVirtualMachine > associateIpAddress > associateUcsProfileToBlade > attachIso > attachVolume > authorizeSecurityGroupEgress > authorizeSecurityGroupIngress > cancelHostMaintenance > cancelStorageMaintenance > configureInternalLoadBalancerElement > configureVirtualRouterElement > copyIso > copyTemplate > createAccount > createAffinityGroup > createAutoScalePolicy > createAutoScaleVmGroup > createAutoScaleVmProfile > createCondition > createDiskOffering > createDomain > createEgressFirewallRule > createFirewallRule > createGlobalLoadBalancerRule > createIpForwardingRule > createLBHealthCheckPolicy > createLBStickinessPolicy > createLoadBalancer > createLoadBalancerRule > createNetwork > createNetworkACL > createNetworkACLList > createNetworkOffering > createPhysicalNetwork > createPod > createPortableIpRange > createPortForwardingRule > createPrivateGateway > createProject > createRemoteAccessVpn > createSecondaryStagingStore > createSecurityGroup > createServiceOffering > createSnapshot > createSnapshotPolicy > createStaticRoute > createStorageNetworkIpRange > createStoragePool > createTags > createTemplate > createUser > createVlanIpRange > createVMSnapshot > createVolume > createVPC > createVpnConnection > createVpnCustomerGateway > createVpnGateway > createZone > dedicateCluster > dedicateGuestVlanRange > dedicateHost > dedicatePod > dedicatePublicIpRange > dedicateZone > deleteAccount > deleteAccountFromProject > deleteAffinityGroup > deleteAlerts > deleteBigSwitchVnsDevice > deleteCiscoNexusVSM > deleteCluster > deleteCondition > deleteDiskOffering > deleteDomain > deleteEgressFirewallRule > deleteEvents > deleteF5LoadBalancer > deleteFirewallRule > deleteGlobalLoadBalancerRule > deleteHost > deleteImageStore > deleteIpForwardingRule > deleteIso > deleteLBHealthCheckPolicy > deleteLBStickinessPolicy > deleteLdapConfiguration > deleteLoadBalancer > deleteLoadBalancerRule > deleteNetscalerLoadBalancer > deleteNetwork > deleteNetworkACL > deleteNetworkACLList > deleteNetworkOffering > deleteNetworkServiceProvider > deleteNiciraNvpDevice > deletePhysicalNetwork > deletePod > deletePortableIpRange > deletePortForwardingRule > deletePrivateGateway > deleteProject > deleteProjectInvitation > deleteRemoteAccessVpn > deleteSecondaryStagingStore > deleteSecurityGroup > deleteServiceOffering > deleteSnapshot > deleteSnapshotPolicies > deleteSrxFirewall > deleteStaticRoute > deleteStorageNetworkIpRange > deleteStoragePool > deleteTags > deleteTemplate > deleteUcsManager > deleteUser > deleteVlanIpRange > deleteVMSnapshot > deleteVolume > deleteVPC > deleteVpnConnection > deleteVpnCustomerGateway > deleteVpnGateway > deleteZone > deployVirtualMachine > destroyRouter > destroySystemVm > destroyVirtualMachine > detachIso > detachVolume > disableAccount > disableAutoScaleVmGroup > disableCiscoNexusVSM > disableStaticNat > disableUser > disassociateIpAddress > disassociateUcsProfileFromBlade > enableAccount > enableAutoScaleVmGroup > enableCiscoNexusVSM > enableStaticNat > enableStorageMaintenance > enableUser > extractVolume > findHostsForMigration > findStoragePoolsForMigration > ldapCreateAccount > listAccounts > listAffinityGroups > listAffinityGroupTypes > listAlerts > listAutoScaleVmGroups > listAutoScaleVmProfiles > listBaremetalDhcp > listBaremetalPxeServers > listBigSwitchVnsDevices > listCapabilities > listCapacity > listCiscoNexusVSMs > listClusters > listConfigurations > listCounters > listDedicatedClusters > listDedicatedGuestVlanRanges > listDedicatedHosts > listDedicat
[jira] [Updated] (CLOUDSTACK-4912) API docs are missing some APIs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-4912: - Affects Version/s: 4.3.0 > API docs are missing some APIs > -- > > Key: CLOUDSTACK-4912 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4912 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Doc >Affects Versions: 4.2.0, 4.3.0 >Reporter: Demetrius Tsitrelis > > I grep’ed the source code and came up with a list of the APIs which the UI > uses. Many of them (addNetscalerLoadBalancer, addVmwareDc, etc.) are not in > the generated API documentation which appears at > http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html > Here’s the list of APIs used by the UI: > activateProject > addAccountToProject > addBaremetalDhcp > addBaremetalPxeKickStartServer > addCluster > addHost > addImageStore > addIpToNic > addLdapConfiguration > addNetscalerLoadBalancer > addNetworkServiceProvider > addNicToVirtualMachine > addRegion > addTrafficType > addUcsManager > addVmwareDc > addVpnUser > archiveAlerts > archiveEvents > assignToGlobalLoadBalancerRule > assignToLoadBalancerRule > assignVirtualMachine > associateIpAddress > associateUcsProfileToBlade > attachIso > attachVolume > authorizeSecurityGroupEgress > authorizeSecurityGroupIngress > cancelHostMaintenance > cancelStorageMaintenance > configureInternalLoadBalancerElement > configureVirtualRouterElement > copyIso > copyTemplate > createAccount > createAffinityGroup > createAutoScalePolicy > createAutoScaleVmGroup > createAutoScaleVmProfile > createCondition > createDiskOffering > createDomain > createEgressFirewallRule > createFirewallRule > createGlobalLoadBalancerRule > createIpForwardingRule > createLBHealthCheckPolicy > createLBStickinessPolicy > createLoadBalancer > createLoadBalancerRule > createNetwork > createNetworkACL > createNetworkACLList > createNetworkOffering > createPhysicalNetwork > createPod > createPortableIpRange > createPortForwardingRule > createPrivateGateway > createProject > createRemoteAccessVpn > createSecondaryStagingStore > createSecurityGroup > createServiceOffering > createSnapshot > createSnapshotPolicy > createStaticRoute > createStorageNetworkIpRange > createStoragePool > createTags > createTemplate > createUser > createVlanIpRange > createVMSnapshot > createVolume > createVPC > createVpnConnection > createVpnCustomerGateway > createVpnGateway > createZone > dedicateCluster > dedicateGuestVlanRange > dedicateHost > dedicatePod > dedicatePublicIpRange > dedicateZone > deleteAccount > deleteAccountFromProject > deleteAffinityGroup > deleteAlerts > deleteBigSwitchVnsDevice > deleteCiscoNexusVSM > deleteCluster > deleteCondition > deleteDiskOffering > deleteDomain > deleteEgressFirewallRule > deleteEvents > deleteF5LoadBalancer > deleteFirewallRule > deleteGlobalLoadBalancerRule > deleteHost > deleteImageStore > deleteIpForwardingRule > deleteIso > deleteLBHealthCheckPolicy > deleteLBStickinessPolicy > deleteLdapConfiguration > deleteLoadBalancer > deleteLoadBalancerRule > deleteNetscalerLoadBalancer > deleteNetwork > deleteNetworkACL > deleteNetworkACLList > deleteNetworkOffering > deleteNetworkServiceProvider > deleteNiciraNvpDevice > deletePhysicalNetwork > deletePod > deletePortableIpRange > deletePortForwardingRule > deletePrivateGateway > deleteProject > deleteProjectInvitation > deleteRemoteAccessVpn > deleteSecondaryStagingStore > deleteSecurityGroup > deleteServiceOffering > deleteSnapshot > deleteSnapshotPolicies > deleteSrxFirewall > deleteStaticRoute > deleteStorageNetworkIpRange > deleteStoragePool > deleteTags > deleteTemplate > deleteUcsManager > deleteUser > deleteVlanIpRange > deleteVMSnapshot > deleteVolume > deleteVPC > deleteVpnConnection > deleteVpnCustomerGateway > deleteVpnGateway > deleteZone > deployVirtualMachine > destroyRouter > destroySystemVm > destroyVirtualMachine > detachIso > detachVolume > disableAccount > disableAutoScaleVmGroup > disableCiscoNexusVSM > disableStaticNat > disableUser > disassociateIpAddress > disassociateUcsProfileFromBlade > enableAccount > enableAutoScaleVmGroup > enableCiscoNexusVSM > enableStaticNat > enableStorageMaintenance > enableUser > extractVolume > findHostsForMigration > findStoragePoolsForMigration > ldapCreateAccount > listAccounts > listAffinityGroups > listAffinityGroupTypes > listAlerts > listAutoScaleVmGroups > listAutoScaleVmProfiles > listBaremetalDhcp > listBaremetalPxeServers > listBigSwitchVnsDevices > listCapabilities > listCapacity > listCiscoNexusVSMs > listClusters > listConfigurations > listCounters > listDedicatedClusters > listDedicatedGuestVlanRanges > listDedicatedHosts > listDedicatedPods > listDedicatedZones > listDepl
[jira] [Updated] (CLOUDSTACK-5263) Virtual router stop/start modifies firewall rules allowing additional access
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-5263: - Security: Public (was: Non-Public) > Virtual router stop/start modifies firewall rules allowing additional access > > > Key: CLOUDSTACK-5263 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5263 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.1.1 >Reporter: John Kinsella >Assignee: Jayapal Reddy >Priority: Critical > Labels: security > Fix For: 4.2.1, 4.3.0 > > Attachments: > 0001-Fix-issue-with-sourceCidr-not-being-passed-to-the-VR.patch > > > Say a user created a firewall rule to allow all access to port 22 from > 172.16.40.0/24 it would be correctly processed by the VRouter and stored in > the database. If the Vrouter instance would be stopped and started, the > source cidr (172.16.40.0/24) would become null and consequently set to > 0.0.0.0/0. Allowing free access to this port from the internet when the > router finished restarting. Changing a rule on the firewall would send the > correct information again including the sourceCids until the next stop start. > This behavior was observed in version 4.1.1 and confirmed to still exist in > the current master build. > Considering that a stop/start of the router vms is part of our standard > upgrade procedure, this is a serious issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5263) Virtual router stop/start modifies firewall rules allowing additional access
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-5263: - Fix Version/s: 4.2.1 > Virtual router stop/start modifies firewall rules allowing additional access > > > Key: CLOUDSTACK-5263 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5263 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.1.1 >Reporter: John Kinsella >Assignee: Jayapal Reddy >Priority: Critical > Labels: security > Fix For: 4.2.1, 4.3.0 > > Attachments: > 0001-Fix-issue-with-sourceCidr-not-being-passed-to-the-VR.patch > > > Say a user created a firewall rule to allow all access to port 22 from > 172.16.40.0/24 it would be correctly processed by the VRouter and stored in > the database. If the Vrouter instance would be stopped and started, the > source cidr (172.16.40.0/24) would become null and consequently set to > 0.0.0.0/0. Allowing free access to this port from the internet when the > router finished restarting. Changing a rule on the firewall would send the > correct information again including the sourceCids until the next stop start. > This behavior was observed in version 4.1.1 and confirmed to still exist in > the current master build. > Considering that a stop/start of the router vms is part of our standard > upgrade procedure, this is a serious issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5183) Docs around ports for vswitch in VMware causes VMware failure
David Nalley created CLOUDSTACK-5183: Summary: Docs around ports for vswitch in VMware causes VMware failure Key: CLOUDSTACK-5183 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5183 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc, VMware Affects Versions: 4.2.0 Reporter: David Nalley admin guide says set # of ports on vswitch to max (4088). If you have 2 vswtiches set to 4088 & reboot hypervisor 2nd switch disappears -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CLOUDSTACK-5117) Update VPN docs
David Nalley created CLOUDSTACK-5117: Summary: 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 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.1#6144)
[jira] [Commented] (CLOUDSTACK-4799) Update Deployment Architecture Overview section
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786194#comment-13786194 ] David Nalley commented on CLOUDSTACK-4799: -- Travis: Why are we using linkend on some, and urls on others? I am reticent to put version specific urls in documents as that becomes a maintenance nightmare. --David > Update Deployment Architecture Overview section > --- > > Key: CLOUDSTACK-4799 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4799 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Travis Graham > Labels: documentaion > Fix For: 4.2.1 > > Attachments: deployment-architecture-overview.patch > > > Adds in links to other docs it only loosely references by name and adds the > Primary Storage info about being zone wide for 4.2. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4800) Updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-4800. -- Resolution: Fixed Assignee: David Nalley Looks good - thanks for the patch commit 941c197b51e66ffea70658532c65304d7a80a1d4 Author: Travis Graham Date: Thu Oct 3 17:07:19 2013 -0400 updating sections of the Cloud Infrastructure Concepts chapter of the Admin Guide > Updating sections of the Cloud Infrastructure Concepts chapter of the Admin > Guide > - > > Key: CLOUDSTACK-4800 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4800 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.2.0 >Reporter: Travis Graham >Assignee: David Nalley > Labels: documentation > Fix For: 4.2.1 > > Attachments: cloud-infrastructure-concepts.patch > > > Adding missing links to referenced sections of the Admin Guide and fixes a > few typos. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4409) [packing]KVM agent is not getting installed on RHEL6.1 due to dependency errors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed CLOUDSTACK-4409. Resolution: Not A Problem I am going to close this - if you can provide error from installation of CloudStack, we can reopen. > [packing]KVM agent is not getting installed on RHEL6.1 due to dependency > errors > --- > > Key: CLOUDSTACK-4409 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4409 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Packaging >Affects Versions: 4.2.0 > Environment: KVM agent installation on RHEL6.2 >Reporter: manasaveloori >Priority: Blocker > Fix For: 4.2.0 > > > Facing the following dependency errors while installing KVM agent on RHEL6.1 > [root@RHEL61 ~]# rpm -ivh jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > warning: jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm: Header V3 > RSA/SHA256 Signature, key ID c105b9de: NOKEY > error: Failed dependencies: > java-gcj-compat is needed by > jakarta-commons-daemon-jsvc-1:1.0.1-8.9.el6.x86_64 > [root@RHEL61 ~]# rpm -ivh java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64.rpm > warning: java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64.rpm: Header V3 RSA/SHA256 > Signature, key ID fd431d51: NOKEY > error: Failed dependencies: > /usr/bin/gcj-dbtool is needed by > java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > /usr/bin/gij is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > /usr/lib64/security/classpath.security is needed by > java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > libgcj >= 4.1.2-5 is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > sinjdoc is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4409) [packing]KVM agent is not getting installed on RHEL6.1 due to dependency errors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745108#comment-13745108 ] David Nalley commented on CLOUDSTACK-4409: -- This look like NOTABUG to me. Why are you trying to use rpm to install java deps? Is there something failing with ACS install? If so, please let us know, but this looks like dependency resolution problems. > [packing]KVM agent is not getting installed on RHEL6.1 due to dependency > errors > --- > > Key: CLOUDSTACK-4409 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4409 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Packaging >Affects Versions: 4.2.0 > Environment: KVM agent installation on RHEL6.2 >Reporter: manasaveloori >Priority: Blocker > Fix For: 4.2.0 > > > Facing the following dependency errors while installing KVM agent on RHEL6.1 > [root@RHEL61 ~]# rpm -ivh jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > warning: jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm: Header V3 > RSA/SHA256 Signature, key ID c105b9de: NOKEY > error: Failed dependencies: > java-gcj-compat is needed by > jakarta-commons-daemon-jsvc-1:1.0.1-8.9.el6.x86_64 > [root@RHEL61 ~]# rpm -ivh java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64.rpm > warning: java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64.rpm: Header V3 RSA/SHA256 > Signature, key ID fd431d51: NOKEY > error: Failed dependencies: > /usr/bin/gcj-dbtool is needed by > java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > /usr/bin/gij is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > /usr/lib64/security/classpath.security is needed by > java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > libgcj >= 4.1.2-5 is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > sinjdoc is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-4409) [packing]KVM agent is not getting installed on RHEL6.1 due to dependency errors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745108#comment-13745108 ] David Nalley commented on CLOUDSTACK-4409: -- This look like NOTABUG to me. Why are you trying to use rpm to install java deps? Is there something failing with ACS install? If so, please let us know, but this looks like dependency resolution problems. > [packing]KVM agent is not getting installed on RHEL6.1 due to dependency > errors > --- > > Key: CLOUDSTACK-4409 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4409 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Packaging >Affects Versions: 4.2.0 > Environment: KVM agent installation on RHEL6.2 >Reporter: manasaveloori >Priority: Blocker > Fix For: 4.2.0 > > > Facing the following dependency errors while installing KVM agent on RHEL6.1 > [root@RHEL61 ~]# rpm -ivh jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm > warning: jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm: Header V3 > RSA/SHA256 Signature, key ID c105b9de: NOKEY > error: Failed dependencies: > java-gcj-compat is needed by > jakarta-commons-daemon-jsvc-1:1.0.1-8.9.el6.x86_64 > [root@RHEL61 ~]# rpm -ivh java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64.rpm > warning: java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64.rpm: Header V3 RSA/SHA256 > Signature, key ID fd431d51: NOKEY > error: Failed dependencies: > /usr/bin/gcj-dbtool is needed by > java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > /usr/bin/gij is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > /usr/lib64/security/classpath.security is needed by > java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > libgcj >= 4.1.2-5 is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 > sinjdoc is needed by java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-732) Add back KVM snapshot support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739134#comment-13739134 ] David Nalley commented on CLOUDSTACK-732: - So I thought we got this included in EL6.4 (at least - snapshots work for me with 4.1.1 and EL6.4. - not saying that it doesn't take a long time, just that it does - I specifically thought they backported one of Edison's upstream qemu patches - but not the second one into EL6.4) Why inject another configuration item instead of just telling people to use 6.4 or later? Finally - this looks to be a global setting rather than a cluster setting. > Add back KVM snapshot support > - > > Key: CLOUDSTACK-732 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-732 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.0.0 > Environment: RHEL 6.3 >Reporter: edison su >Assignee: Fang Wang >Priority: Critical > Fix For: 4.2.0 > > > In the latest KVM(on both RHEL 6.3 and Ubuntu 12.04), it supports external > snapshot. We need to investigate the status of external snapshot, as far as I > know, it still doesn't support disk-only snapshot(taking snapshot will pause > VM for a long time, e.g. few minutes). > 1. testing external snapshot: take an external snapshot instead of default > qcow2 internal snapshot, then back it up into backup storage. Only need to > test with libvirt snapshot API, if it works, then works, no need to hack on > the qemu-kvm. > 2. test how long it will pause a VM during taking snapshot. from link [2] and > [3], only qemu-kvm-rhev supports disk-only snapshot, not sure ubuntu 12.04 > supports it or not. We need to investigate on the issue. > If item 1 and item 2(disk-only snapshot) works, then we can support default > kvm qcow2 snapshot again. > The link: > [1] > http://kashyapc.wordpress.com/2011/10/04/snapshotting-with-libvirt-for-qcow2-images/ > [2] > http://www.linux-kvm.com/content/first-look-virtual-machine-online-disk-snapshots-coming-fedora-18 > [3] http://www.redhat.com/archives/libvir-list/2012-July/msg00782.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3457) Language: Japanese. Nothing is displayed on a screen after login.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-3457: - Component/s: UI > Language: Japanese. Nothing is displayed on a screen after login. > -- > > Key: CLOUDSTACK-3457 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3457 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Management Server : CentOS 6.3 >Reporter: satoru nakaya > > 1. Language : Choose Japanese. > 2. Log in. > 3. Nothing is displayed on a screen after login. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3457) Language: Japanese. Nothing is displayed on a screen after login.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-3457: - Priority: Critical (was: Major) > Language: Japanese. Nothing is displayed on a screen after login. > -- > > Key: CLOUDSTACK-3457 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3457 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.2.0 > Environment: Management Server : CentOS 6.3 >Reporter: satoru nakaya >Priority: Critical > > 1. Language : Choose Japanese. > 2. Log in. > 3. Nothing is displayed on a screen after login. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-3328) cloudstack-agent RPM package doesn't require qemu-kvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-3328. -- Resolution: Fixed > cloudstack-agent RPM package doesn't require qemu-kvm > -- > > Key: CLOUDSTACK-3328 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3328 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.1.0 >Reporter: David Nalley >Assignee: David Nalley > Fix For: 4.1.1 > > > cloudstack-agent doesn't require qemu-kvm, which is necessary for KVM and by > extension the agent to be functioning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3328) cloudstack-agent RPM package doesn't require qemu-kvm
David Nalley created CLOUDSTACK-3328: Summary: cloudstack-agent RPM package doesn't require qemu-kvm Key: CLOUDSTACK-3328 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3328 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Packaging Affects Versions: 4.1.0 Reporter: David Nalley Assignee: David Nalley Fix For: 4.1.1 cloudstack-agent doesn't require qemu-kvm, which is necessary for KVM and by extension the agent to be functioning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3310) UCS-functionality appears to store UCS creds in cleartext
David Nalley created CLOUDSTACK-3310: Summary: UCS-functionality appears to store UCS creds in cleartext Key: CLOUDSTACK-3310 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3310 Project: CloudStack Issue Type: Bug Components: UCS Affects Versions: 4.2.0 Reporter: David Nalley Priority: Blocker Fix For: 4.2.0 CLOUDSTACK-3307 seems to show the ucs_manager table being populated with cleartext passwords. These should be encrypted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-308) ec2-describe-instances - Instance type is always retuned as "m1.small"
[
https://issues.apache.org/jira/browse/CLOUDSTACK-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691720#comment-13691720
]
David Nalley commented on CLOUDSTACK-308:
-
Can this be fixed in 4.1.1 as well?
> ec2-describe-instances - Instance type is always retuned as "m1.small"
> --
>
> Key: CLOUDSTACK-308
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-308
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AWSAPI
>Affects Versions: pre-4.0.0
> Environment: [root@vmwasfmgmt management]# cloud-sccs
> Git Revision: 66daa1a2bc6e86adea265a8a0b8b512756c8f77c
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
>Reporter: Sangeetha Hariharan
>Assignee: Likitha Shetty
> Fix For: 4.2.0
>
>
> ec2-describe-instances - Instance type is always retuned as "m1.small"
> Using ec2 API call , Deploy a VM using instance-type as "m1.large"
> Once instance is deployed , describe this instance using
> ec2-describe-instances.
> Instance type is always retuned as "m1.small"
> [root@Host41-4 bin]# ./ec2-run-instances 6c7d0b07-9f04-4abd-8069-a4208870218e
> --instance-type m1.large --connection-timeout 300 --request-timeout 00
> RESERVATION 84b79c96-93b1-474d-bf24-1a3f3b8e171d:hello
> default
> INSTANCEac7703ca-68bc-437f-a687-45f7e0af7158
> 6c7d0b07-9f04-4abd-8069-a4208870218erunning
> m1.large 2012-10-09T22:39:39-0700ZONE-RHEL-ASF
>monitoring- 10.223.59.59
>XenServer
> TAG instanceac7703ca-68bc-437f-a687-45f7e0af7158
> [root@Host41-4 bin]# ./ec2-describe-instances
> ac7703ca-68bc-437f-a687-45f7e0af7158
> RESERVATION ac7703ca-68bc-437f-a687-45f7e0af7158
> 84b79c96-93b1-474d-bf24-1a3f3b8e171d:hello default
> INSTANCEac7703ca-68bc-437f-a687-45f7e0af7158
> 6c7d0b07-9f04-4abd-8069-a4208870218erunning
> m1.small 2012-10-09T22:39:39-0700ZONE-RHEL-ASF
>monitoring- 10.223.59.59
>XenServer
> TAG instanceac7703ca-68bc-437f-a687-45f7e0af7158
> aws-api.logs:
> 2012-10-09 22:47:08,829 DEBUG [auth.ec2.AuthenticationHandler]
> (catalina-exec-int-3:null) X509 cert's uniqueId: EMAILADDRESS=ca, CN=ca,
> OU=ca, O=ca, L=ca, ST=ca, C=CA, serial=11892681842750832289
> 2012-10-09 22:47:08,832 DEBUG [bridge.service.UserContext]
> (catalina-exec-int-3:null) initializing a new [anonymous] UserContext!
> 2012-10-09 22:47:08,833 DEBUG [cloud.stack.CloudStackClient]
> (catalina-exec-int-3:null) Cloud API call +
> [http://127.0.0.1:8080/client/api?command=listVirtualMachines&id=ac7703ca-68bc-437f-a687-45f7e0af7158&response=json&listall=true&apikey=9TAhE9nErO3FyFkA4sQIBcz6BwdjZL-J6whVeoQcNNDtzl2qbsHPaA_ebwEOU3X-sIE6ef2PGvuTPrEtdxLjew&signature=ELmVPZF1cvFSjkKCED%2F1mtjXTiw%3D]
> 2012-10-09 22:47:08,853 DEBUG [cloud.stack.CloudStackClient]
> (catalina-exec-int-3:null) Cloud API call +
> [http://127.0.0.1:8080/client/api?command=listVirtualMachines&id=ac7703ca-68bc-437f-a687-45f7e0af7158&response=json&listall=true&apikey=9TAhE9nErO3FyFkA4sQIBcz6BwdjZL-J6whVeoQcNNDtzl2qbsHPaA_ebwEOU3X-sIE6ef2PGvuTPrEtdxLjew&signature=ELmVPZF1cvFSjkKCED%2F1mtjXTiw%3D]
> returned:
> {"listvirtualmachinesresponse":{"count":1,"virtualmachine":[{"id":"ac7703ca-68bc-437f-a687-45f7e0af7158","name":"ac7703ca-68bc-437f-a687-45f7e0af7158","displayname":"ac7703ca-68bc-437f-a687-45f7e0af7158","account":"hello","domainid":"84b79c96-93b1-474d-bf24-1a3f3b8e171d","domain":"ROOT","created":"2012-10-09T22:39:39-0700","state":"Running","haenable":false,"zoneid":"c2f29592-038e-4b7a-871c-34ae1c559439","zonename":"ZONE-RHEL-ASF","templateid":"6c7d0b07-9f04-4abd-8069-a4208870218e","templatename":"CentOS
> 5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no
> GUI
> (XenServer)","passwordenabled":false,"serviceofferingid":"0c7970fc-b70c-460a-92e0-b4c4280f9d55","serviceofferingname":"m1.large","cpunumber":1,"cpuspeed":100,"memory":124,"cpuused":"0.19%","networkkbsread":2,"networkkbswrite":2,"guestosid":"b366c5fe-bfdf-47b5-b79f-103c6ce59e99","rootdeviceid":0,"rootdevicetype":"NetworkFilesystem","securitygroup":[{"id":"10b78f4f-91a6-47de-a4be-bf024b2a9948","name":"default","description":"Default
> Security
> Group"}],"nic":[{"id":"98ab6001-f32f-4017-9376-72bdfcdb51fa","networkid":"308de7fe-fe95-45cc-b1d7-3c440d501401","netmask":"255.255.255.192","gateway":"10.223.59.1","ipaddress":"10.223.59.59","traffictype":"Guest","type":"Shared","isdef
[jira] [Closed] (CLOUDSTACK-3140) Debs still have a number of utilities as cloud-*
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed CLOUDSTACK-3140. Resolution: Invalid I blame chip > Debs still have a number of utilities as cloud-* > - > > Key: CLOUDSTACK-3140 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3140 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.1.0 >Reporter: David Nalley > > Debian generated packages contain a number of cloud-* utilities (i.e. > cloud-setup-databases) these have been migrated to cloudstack-* in RPM, and > debs should follow this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3140) Debs still have a number of utilities as cloud-*
David Nalley created CLOUDSTACK-3140: Summary: Debs still have a number of utilities as cloud-* Key: CLOUDSTACK-3140 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3140 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Packaging Affects Versions: 4.1.0 Reporter: David Nalley Debian generated packages contain a number of cloud-* utilities (i.e. cloud-setup-databases) these have been migrated to cloudstack-* in RPM, and debs should follow this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-3097) Installation docs have the wrong package names
David Nalley created CLOUDSTACK-3097: Summary: Installation docs have the wrong package names Key: CLOUDSTACK-3097 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3097 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: David Nalley Priority: Blocker Fix For: 4.1.1 Both RPM and Deb install instructions refer to cloud- package names. Package names changed in 4.1.0 to be cloudstack-* While the RPM packages are done such that cloud-* should still work, it's an ugly hack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-2912) Installation instruction wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley reassigned CLOUDSTACK-2912: Assignee: David Nalley > Installation instruction wrong > -- > > Key: CLOUDSTACK-2912 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2912 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.0 > Environment: Centos >Reporter: Ron Wheeler >Assignee: David Nalley >Priority: Minor > Labels: documentation > > 3.6.1. Generating RPMS > First command cd ./packaging/centos63/ missing from commands to be given > I found a file called /docs/en-US/build-rpm.xml that lloks like the page in > question > At line 48 it has the following > > Generating RPMS > Now that we have the prerequisites and source, you will cd to > the packaging/centos63/ directory. > Generating RPMs is done using the > package.sh script: > $./package.sh > > which I guess should be something like > > Generating RPMS > Now that we have the prerequisites and source, you will cd to > the packaging/centos63/ directory. > $ cd packaging/centos63 > > Generating RPMs is done using the > package.sh script: > $./package.sh > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2912) Installation instruction wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-2912. -- Resolution: Fixed Thanks for the bug report and fix suggestion. I've committed a fix to 4.1 and master branches. > Installation instruction wrong > -- > > Key: CLOUDSTACK-2912 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2912 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.0 > Environment: Centos >Reporter: Ron Wheeler >Assignee: David Nalley >Priority: Minor > Labels: documentation > > 3.6.1. Generating RPMS > First command cd ./packaging/centos63/ missing from commands to be given > I found a file called /docs/en-US/build-rpm.xml that lloks like the page in > question > At line 48 it has the following > > Generating RPMS > Now that we have the prerequisites and source, you will cd to > the packaging/centos63/ directory. > Generating RPMs is done using the > package.sh script: > $./package.sh > > which I guess should be something like > > Generating RPMS > Now that we have the prerequisites and source, you will cd to > the packaging/centos63/ directory. > $ cd packaging/centos63 > > Generating RPMs is done using the > package.sh script: > $./package.sh > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2872) ubuntu 12.4 kvm issue CS 4.1 libvirt complaint and not able to start systemvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-2872: - Priority: Blocker (was: Major) > ubuntu 12.4 kvm issue CS 4.1 libvirt complaint and not able to start systemvm > -- > > Key: CLOUDSTACK-2872 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2872 > 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 12.04 host libvirt 0.98 >Reporter: Philippe Van Hecke >Priority: Blocker > Fix For: 4.1.1 > > > I upgraded our test environemen(4.0.2) to 4.1 > and we have the following issue with libvirtd > virDomainTimerDefParseXML:4630 : internal error unknown timer name > 'kvmclock' > After an upgrade of libvirt to > version 1.0.2 from following ppa ppa:pfak/backports > https://launchpad.net/~pfak/+archive/backports > The problem was solved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2872) ubuntu 12.4 kvm issue CS 4.1 libvirt complaint and not able to start systemvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-2872: - Fix Version/s: 4.1.1 > ubuntu 12.4 kvm issue CS 4.1 libvirt complaint and not able to start systemvm > -- > > Key: CLOUDSTACK-2872 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2872 > 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 12.04 host libvirt 0.98 >Reporter: Philippe Van Hecke > Fix For: 4.1.1 > > > I upgraded our test environemen(4.0.2) to 4.1 > and we have the following issue with libvirtd > virDomainTimerDefParseXML:4630 : internal error unknown timer name > 'kvmclock' > After an upgrade of libvirt to > version 1.0.2 from following ppa ppa:pfak/backports > https://launchpad.net/~pfak/+archive/backports > The problem was solved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2406) language display error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667435#comment-13667435 ] David Nalley commented on CLOUDSTACK-2406: -- Is the problem one with Transifex, or is it on our side? --David > language display error > --- > > Key: CLOUDSTACK-2406 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2406 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 > Environment: Ubuntu 12.0.4 kvm >Reporter: terryye > Original Estimate: 72h > Remaining Estimate: 72h > > All of chinese lable is "???" . > Japanese is display the word code .like \u65e5\u672c\.. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2330) [Automation] Failed to deploy VR in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649135#comment-13649135
]
David Nalley commented on CLOUDSTACK-2330:
--
Rayees: When did this last work? What are the commit hashes when this was last
working and when it started failing?
> [Automation] Failed to deploy VR in KVM
>
>
> Key: CLOUDSTACK-2330
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2330
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
> Environment: KVM,
> Master build
>Reporter: Rayees Namathponnan
> Fix For: 4.2.0
>
> Attachments: CLOUDSTACK-2330.rar
>
>
> Automation running on KVM with advanced zone,VR deployment failing during
> automation run
> Observed below error in MS log, attaching MS and agent log
> 2013-05-04 13:43:13,032 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-99:job-369)
> Reapplying vm data (userData and metaData) entries as a part of domR
> VM[DomainRouter|r-155-VM] start...
> 2013-05-04 13:43:13,040 DEBUG [agent.transport.Request]
> (Job-Executor-99:job-369) Seq 4-98894092: Sending { Cmd , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 100111, [{"Sta
> rtCommand":{"vm":{"id":155,"name":"r-155-VM","type":"DomainRouter","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":134217728,"maxRam":134217728,"arch":"x86_64","os":"Debian
> GNU/
> Linux 5.0 (32-bit)","bootArgs":" template=domP name=r-155-VM
> eth2ip=10.223.122.89 eth2mask=255.255.255.192 gateway=10.223.122.65
> eth0ip=10.1.1.1 eth0mask=255.255.255.0 domain=cs
> 2auto.advanced dhcprange=10.1.1.1 eth1ip=169.254.3.220 eth1mask=255.255.0.0
> type=router disable_rp_filter=true
> dns1=72.52.126.11","rebootOnCrash":false,"enableHA":true,"limitCpu
> Use":false,"vncPassword":"a3b0c243e954e90e","params":{},"uuid":"f114bcc5-1f3f-4fcb-85f7-3ed9d40467dc","disks":[{"id":155,"name":"ROOT-155","size":741212160,"type":"ROOT","storag
> ePoolType":"NetworkFilesystem","storagePoolUuid":"fff90cb5-06dd-33b3-8815-d78c08ca01d9","deviceId":0}],"nics":[{"deviceId":2,"networkRateMbps":200,"defaultNic":true,"uuid":"1dee
> a081-1ca4-4af5-ba98-bdac0dac722f","ip":"10.223.122.89","netmask":"255.255.255.192","gateway":"10.223.122.65","mac":"06:31:6c:00:00:52","dns1":"72.52.126.11","broadcastType":"Vla
> n","type":"Public","broadcastUri":"vlan://1221","isolationUri":"vlan://1221","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":200,"defaultNic":false,"uuid":"abb44
> 284-bbc9-41e6-a1d5-53b2a9256ee6","ip":"10.1.1.1","netmask":"255.255.255.0","mac":"02:00:71:47:00:02","dns1":"72.52.126.11","broadcastType":"Vlan","type":"Guest","broadcastUri":"
> vlan://2354","isolationUri":"vlan://2354","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"8b060664-4c4f-4f0f-bffc-87871cbab662","ip
> ":"169.254.3.220","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:03:dc","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false}]},"hostI
> p":"10.223.50.66","wait":0}},{"check.CheckSshCommand":{"ip":"169.254.3.220","port":3922,"interval":6,"retries":100,"name":"r-155-VM","wait":0}},{"GetDomRVersionCmd":{"accessDeta
> ils":{"router.ip":"169.254.3.220","router.name":"r-155-VM"},"wait":0}},{},{"routing.IpAssocCommand":{"ipAddresses":[{"accountId":2,"publicIp":"10.223.122.89","sourceNat":true,"a
> dd":true,"oneToOneNat":false,"firstIP":true,"vlanId":"1221","vlanGateway":"10.223.122.65","vlanNetmask":"255.255.255.192","vifMacAddress":"06:bb:60:00:00:52","networkRate":200,"
> trafficType":"Public"}],"accessDetails":{"router.guest.ip":"10.1.1.1","zone.network.type":"Advanced","router.ip":"169.254.3.220","router.name":"r-155-VM"},"wait":0}}]
> }
> 2013-05-04 13:43:13,306 DEBUG [agent.transport.Request]
> (AgentManager-Handler-10:null) Seq 4-98894092: Processing: { Ans: , MgmtId:
> 29066118877352, via: 4, Ver: v1, Flags: 110,
>
> [{"Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException:
> org.libvirt.LibvirtException: invalid argument:
> virStorageVolLookupByName\n\tat com.cloud
> .hypervisor.kvm.storage.LibvirtStorageAdaptor.getVolume(LibvirtStorageAdaptor.java:95)\n\tat
>
> com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.getPhysicalDisk(LibvirtStorag
> eAdaptor.java:390)\n\tat
> com.cloud.hypervisor.kvm.storage.LibvirtStoragePool.getPhysicalDisk(LibvirtStoragePool.java:123)\n\tat
> com.cloud.hypervisor.kvm.resource.LibvirtComputin
> gResource.createVbd(LibvirtComputingResource.java:3323)\n\tat
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3214)\n\
[jira] [Commented] (CLOUDSTACK-2171) Unable to Create a VM In the VMware Setup with the latest Master.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642774#comment-13642774
]
David Nalley commented on CLOUDSTACK-2171:
--
Kiran,
Please update the ticket with the information in your email, or alternatively
push the discussion to the mailing list. Please don't take discussions private.
> Unable to Create a VM In the VMware Setup with the latest Master.
> -
>
> Key: CLOUDSTACK-2171
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2171
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
>Affects Versions: 4.2.0
>Reporter: Kiran Koneti
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> I have created a VMware Advanced Zone Setup.
> Once the system Vm's came up I added a template and tried to create a VM for
> the first time.
> The Router VM is created and the VM also came up.
> Then I tried to create another VM this the the VM fails with an error message
> saying insufficient capacity.
> When started debugging the issue I found that the VM creation initially
> failed with an error message as below.
> "c":true,"uuid":"9c0b7d10-be63-4bd3-8e07-9e3e86955fd6","ip":"10.1.1.2","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:49:1b:00:05","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://923","isolationUri":"vlan://923","isSecurityGroupEnabled":false,"name":"undefined"}
> 2013-04-24 22:14:22,636 INFO [vmware.resource.VmwareResource]
> (DirectAgent-66:10.147.40.9) Prepare network on vmwaresvs
> P[undefined:untagged] with name prefix: cloud.guest
> 2013-04-24 22:14:22,660 ERROR [vmware.mo.HypervisorHostHelper]
> (DirectAgent-66:10.147.40.9) Unable to find vSwitchundefined
> 2013-04-24 22:14:22,660 WARN [vmware.resource.VmwareResource]
> (DirectAgent-66:10.147.40.9) StartCommand failed due to Exception:
> java.lang.Exception
> Message: Unable to find vSwitchundefined
> java.lang.Exception: Unable to find vSwitchundefined
> at
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:697)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2532)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2308)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:433)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)"
> When started debugging the issue there is a new field added to the VM start
> command with as "name":"undefined" after the "isSecurityGroupEnabled":false
> which I didn't observe for the VM created for the first time.
> The Start command for the VM which was created Successfully is as below:
> "2013-04-24 21:51:55,245 INFO [vmware.resource.VmwareResource]
> (DirectAgent-17:10.147.40.9) Executing resource StartCommand:
> {"vm":{"id":3,"name":"i-2-3-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":1000,"maxSpeed":1000,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"CentOS
> 5.3
> (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"67afc54d34162749","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"876c4e5b-0549-40a5-9ac6-07ee6b94bab7","disks":[{"id":3,"name":"ROOT-3","mountPoint":"/export/home/kiran/p1","path":"ROOT-3-3","size":2147483648,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec982716","deviceId":0},{"id":4,"name":"DATA-3","mountPoint":"/export/home/kiran/p1","path":"604556bb425a4368853736a5731c262a","size":5368709120,"type":"DATADISK","storagePoolType":"NetworkFilesystem","storagePoolUuid":"b4825bd6-2b6d-33ef-b324-bfbbec
[jira] [Commented] (CLOUDSTACK-1301) VM Disk I/O Throttling
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641743#comment-13641743 ] David Nalley commented on CLOUDSTACK-1301: -- Wei: Does this still work without a patched QEMU? Can we get the throttling code up for review on reviewboard? > VM Disk I/O Throttling > -- > > Key: CLOUDSTACK-1301 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1301 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.1.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.2.0 > > > VM Disk I/O Throttling, to set the maximum disk I/O rate of VMs. > Virtual machines are running on the same storage device (local storage or > share strage). Because of the rate limitation of device (such as iops), if > one VM has large disk operation, it may affect the disk performance of other > VMs running on the same storage device. > It is neccesary to set the maximum rate and limit the disk I/O of VMs. > More details: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+IO+Throttling -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1629) Need to move location or conflict with antlr
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-1629. -- Resolution: Fixed See above commit. > Need to move location or conflict with antlr > > > Key: CLOUDSTACK-1629 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1629 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.0.1 >Reporter: David Nalley >Assignee: David Nalley > Fix For: 4.0.2 > > > Transaction Check Error: > file /usr/share/java/antlr-2.7.7.jar from install of > cloud-deps-4.0.1-1.el6.x86_64 conflicts with file from package > antlr-0:2.7.7-6.5.el6.x86_64 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1781) GSoC: Create a cloud in a box using DevCloud
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628351#comment-13628351 ] David Nalley commented on CLOUDSTACK-1781: -- d...@cloudstack.apache.org <-- that's the best email to talk about details on. > GSoC: Create a cloud in a box using DevCloud > > > Key: CLOUDSTACK-1781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1781 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: sebastien goasguen > Labels: gsoc2013 > Fix For: 4.2.0 > > > DevCloud is an Apache CloudStack sandbox, it contains all the software > necessary to run CloudStack. It is used primarily as a development > environment to test new code or as a demo sandbox. > In this project , the student would extend devcloud to create a complete > cloud configuration with a management server and multiple hosts. The number > of hosts would be configurable to accomodate the resources available. > Language: python,bash > Knowledge: virtualization, networking, vagrant, veewee, puppet -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1929) ASF 4.1 cloudstack agent fail to install in KVM host CENTOS 6.3 OS: qemu-kvm-0.12.1.2-3.295.el6.10.x86_64 requires libusbredirparser.so.0
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed CLOUDSTACK-1929. Resolution: Invalid I believe this to be invalid, and marking it as such - feel free to reopen if I misunderstand. We do not ship qemu-kvm with CloudStack, yet you appear to be pulling qemu-kvm from cloud-temp repo. That also isn't the current qemu-kvm that CentOS is shipping with in EL6 (Current is qemu-kvm-0.12.1.2-2.355.el6.x86_64.rpm - crossing the streams and supplying identically named packages in another repo is bound to result in problems like this) > ASF 4.1 cloudstack agent fail to install in KVM host CENTOS 6.3 OS: > qemu-kvm-0.12.1.2-3.295.el6.10.x86_64 requires libusbredirparser.so.0 > --- > > Key: CLOUDSTACK-1929 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1929 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Packaging >Affects Versions: 4.1.0 > Environment: KVM host CentOS 6.3 - try to install ASF 4.1 cloudstack > latest build 4/4/13 >Reporter: angeline shen >Assignee: Fang Wang >Priority: Critical > Fix For: 4.1.0 > > > install cloudstack agent encountered errors: > Error: Package: 2:qemu-kvm-0.12.1.2-3.295.el6.10.x86_64 (cloud-temp) >Requires: libusbredirparser.so.0()(64bit) > Error: Package: 2:qemu-img-0.12.1.2-3.295.el6.10.x86_64 (cloud-temp) >Requires: libusbredirparser.so.0()(64bit) > [root@kvm194 CloudStack-non-OSS-4.1-172-rhel6.3]# ./install.sh > Setting up the temporary repository... > Cleaning Yum cache... > Loaded plugins: fastestmirror, security > Cleaning repos: base cloud-temp extras updates > 6 metadata files removed > Welcome to the Apache CloudStack (Incubating) Installer. What would you like > to do? > M) Install the Management Server > A) Install the Agent > S) Install the Usage Monitor > D) Install the database server > Q) Quit > > A > Installing the Agent... > Loaded plugins: fastestmirror, security > Loading mirror speeds from cached hostfile > * base: mirrors.cat.pdx.edu > * extras: mirrors.sonic.net > * updates: mirrors.sonic.net > base > | 3.7 kB 00:00 > cloud-temp > | 1.3 kB 00:00 ... > cloud-temp/primary > | 3.6 kB 00:00 ... > cloud-temp >9/9 > extras > | 3.5 kB 00:00 > updates > | 3.5 kB 00:00 > Setting up Install Process > Resolving Dependencies > --> Running transaction check > ---> Package cloudstack-agent.x86_64 0:4.1.0-SNAPSHOT.el6 will be installed > --> Processing Dependency: cloudstack-common = 4.1.0 for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: jna >= 3.2.4 for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: qemu-kvm for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: qemu-img for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: libvirt for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: jakarta-commons-daemon for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: ipset for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Processing Dependency: ebtables for package: > cloudstack-agent-4.1.0-SNAPSHOT.el6.x86_64 > --> Running transaction check > ---> Package cloudstack-common.x86_64 0:4.1.0-SNAPSHOT.el6 will be installed > ---> Package ebtables.x86_64 0:2.0.9-6.el6 will be installed > ---> Package ipset.x86_64 0:6.11-1.el6 will be installed > --> Processing Dependency: libmnl.so.0(LIBMNL_1.0)(64bit) for package: > ipset-6.11-1.el6.x86_64 > --> Processing Dependency: libmnl.so.0()(64bit) for package: > ipset-6.11-1.el6.x86_64 > ---> Package jakarta-commons-daemon.x86_64 1:1.0.1-8.9.el6 will be installed > ---> Package jna.x86_64 0:3.2.4-2.el6 will be installed > ---> Package libvirt.x86_64 0:0.10.2-18.el6_4.2 will be installed > --> Processing Dependency: libvirt-client = 0.10.2-18.el6_4.2 for package: > libvirt-0.10.2-18.el6_4.
[jira] [Assigned] (CLOUDSTACK-1936) On CentOS, after a upgrade from 4.0.1 to 4.1 on a cloud node (cloud-agent), the new cloustack-agent isn't add as a service (chkconfig)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley reassigned CLOUDSTACK-1936: Assignee: David Nalley > On CentOS, after a upgrade from 4.0.1 to 4.1 on a cloud node (cloud-agent), > the new cloustack-agent isn't add as a service (chkconfig) > -- > > Key: CLOUDSTACK-1936 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1936 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.0 >Reporter: Milamber >Assignee: David Nalley >Priority: Critical > Labels: upgrade > > On CentOS 6.4, after a upgrade from 4.0.1 to 4.1 on a cloud node (server with > cloud-agent), the new cloudstack-agent isn't add as a service > chkconfig --list without cloustack-agent, but it's present into /etc/init.d/ > 4.1-SNAPSHOT (2013/04/04) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1936) On CentOS, after a upgrade from 4.0.1 to 4.1 on a cloud node (cloud-agent), the new cloustack-agent isn't add as a service (chkconfig)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-1936: - Priority: Critical (was: Major) > On CentOS, after a upgrade from 4.0.1 to 4.1 on a cloud node (cloud-agent), > the new cloustack-agent isn't add as a service (chkconfig) > -- > > Key: CLOUDSTACK-1936 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1936 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.1.0 >Reporter: Milamber >Priority: Critical > Labels: upgrade > > On CentOS 6.4, after a upgrade from 4.0.1 to 4.1 on a cloud node (server with > cloud-agent), the new cloudstack-agent isn't add as a service > chkconfig --list without cloustack-agent, but it's present into /etc/init.d/ > 4.1-SNAPSHOT (2013/04/04) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1650) Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed CLOUDSTACK-1650. Resolution: Won't Fix > Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed > --- > > Key: CLOUDSTACK-1650 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1650 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.0.1 > Environment: CentOS 6.3 >Reporter: Sean Truman >Assignee: David Nalley > > The yum repository is reporting that cloud-deps-4.0.1-1.el6.x86_64.rpm is not > signed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-1650) Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley reopened CLOUDSTACK-1650: -- Assignee: David Nalley > Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed > --- > > Key: CLOUDSTACK-1650 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1650 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.0.1 > Environment: CentOS 6.3 >Reporter: Sean Truman >Assignee: David Nalley > > The yum repository is reporting that cloud-deps-4.0.1-1.el6.x86_64.rpm is not > signed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1650) Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620431#comment-13620431 ] David Nalley commented on CLOUDSTACK-1650: -- Sean - the project doesn't maintain official yum repos or provide binaries. The packages in the repo are unsigned, just set gpg verification to false for that repo definition. > Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed > --- > > Key: CLOUDSTACK-1650 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1650 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.0.1 > Environment: CentOS 6.3 >Reporter: Sean Truman > > The yum repository is reporting that cloud-deps-4.0.1-1.el6.x86_64.rpm is not > signed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1650) Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley closed CLOUDSTACK-1650. Resolution: Fixed > Package cloud-deps-4.0.1-1.el6.x86_64.rpm is not signed > --- > > Key: CLOUDSTACK-1650 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1650 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Packaging >Affects Versions: 4.0.1 > Environment: CentOS 6.3 >Reporter: Sean Truman > > The yum repository is reporting that cloud-deps-4.0.1-1.el6.x86_64.rpm is not > signed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1532) Ability to plug a VPC private gateway interface onto a specified Nicira NVP logical switch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-1532: - Component/s: (was: Cloudmonkey) Network Devices Network Controller > Ability to plug a VPC private gateway interface onto a specified Nicira NVP > logical switch > -- > > Key: CLOUDSTACK-1532 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1532 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Network Devices >Reporter: Roeland Kuipers >Assignee: Hugo Trippaers > > Currently a VPC private gateway interface can be plugged on a specific VLAN. > We like to see the possibility to specify a Nicira NVP logical switch instead > of a VLAN. > One of the use cases we have for this is VPC <-> VPC connectivity (routing) > within the logical space of NVP -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1533) Ability to specify a NVP logical switch GUID for a shared network and implement this network as a NVP logical switch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-1533: - Component/s: (was: Cloudmonkey) Network Devices Network Controller > Ability to specify a NVP logical switch GUID for a shared network and > implement this network as a NVP logical switch > > > Key: CLOUDSTACK-1533 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1533 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Network Devices >Affects Versions: 4.0.0 >Reporter: Roeland Kuipers >Assignee: Hugo Trippaers > > Currently shared networks can only be implemented using VLAN isolation. We > would like to have possibility to use NVP SDN isolation by means of a logical > switch. So we can handle shared networking within the logical space of NVP. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1746) Cloudstack Usage Server won't start
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley updated CLOUDSTACK-1746: - Priority: Blocker (was: Major) > Cloudstack Usage Server won't start > --- > > Key: CLOUDSTACK-1746 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1746 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Francois Gaudreault >Priority: Blocker > > Using the latest 4.1 (commit cfff6708f35cfbe3a8f8a61b854b8043942d5b4c), the > cloudstack-usage server will not start. Error is : > log4j:WARN No appenders could be found for logger > (org.springframework.core.env.StandardEnvironment). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more > info. > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177) > Caused by: java.lang.ExceptionInInitializerError > at > com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:34) > at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) > at > org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) > at > org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) > at > com.cloud.configuration.dao.ConfigurationDaoImpl$$EnhancerByCGLIB$$27aaa385.configure() > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:97) > at com.cloud.usage.UsageServer.start(UsageServer.java:53) > ... 5 more > Caused by: java.lang.NullPointerException > at java.io.FileInputStream.(FileInputStream.java:133) > at > com.cloud.utils.crypt.EncryptionSecretKeyChecker.check(EncryptionSecretKeyChecker.java:65) > at com.cloud.utils.db.Transaction.(Transaction.java:101) > ... 19 more > 20/03/2013 13:53:33 20255 jsvc.exec error: Cannot start daemon > 20/03/2013 13:53:33 20254 jsvc.exec error: Service exit with a return value > of 5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1810) listTemplate API with templatefilter=featured|community is not returning any list
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615526#comment-13615526
]
David Nalley commented on CLOUDSTACK-1810:
--
Min: Is this a change in behavior from 4.0.x?
--David
> listTemplate API with templatefilter=featured|community is not returning any
> list
> -
>
> Key: CLOUDSTACK-1810
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1810
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
>Affects Versions: 4.1.0
>Reporter: Srikanteswararao Talluri
>Assignee: Min Chen
>Priority: Blocker
> Fix For: 4.1.0
>
>
> listTemplates API is not returning any output when templatefilter is set to
> 'featured'
> http://10.147.38.207:8080/client/api?command=listTemplates&response=json&sessionkey=vC9DIqP6xiOkmmk2oMvt4slxu%2Fs%3D&listAll=true&page=1&pagesize=20&templatefilter=featured&_=1364314333779
> Resonse:
> { "listtemplatesresponse" : { } }
> Where as if templatefilter=all returns all the templates
> http://10.147.38.207:8080/client/api?command=listTemplates&response=json&sessionkey=vC9DIqP6xiOkmmk2oMvt4slxu%2Fs%3D&listAll=true&page=1&pagesize=20&templatefilter=all&_=1364314283591
> Response :
> { "listtemplatesresponse" : { "count":5 ,"template" : [
> {"id":"80bff0be-9604-11e2-90e0-06b27059","name":"SystemVM Template
> (XenServer)","displaytext":"SystemVM Template
> (XenServer)","ispublic":false,"created":"2013-03-26T17:01:40+0530","isready":true,"passwordenabled":false,"format":"VHD","isfeatured":false,"crossZones":true,"ostypeid":"8116119c-9604-11e2-90e0-06b27059","ostypename":"Debian
> GNU/Linux
> 6(64-bit)","account":"system","zoneid":"faf4777c-2a8d-45ee-959c-bc1b0f07f3cf","zonename":"Sandbox-XenServer","status":"Download
>
> Complete","size":565240320,"templatetype":"SYSTEM","hypervisor":"XenServer","domain":"ROOT","domainid":"80b38fa4-9604-11e2-90e0-06b27059","isextractable":false,"checksum":"f613f38c96bf039f2e5cbf92fa8ad4f8","tags":[],"sshkeyenabled":false},
> {"id":"80bff0be-9604-11e2-90e0-06b27059","name":"SystemVM Template
> (XenServer)","displaytext":"SystemVM Template
> (XenServer)","ispublic":false,"created":"2013-03-26T17:02:31+0530","isready":true,"passwordenabled":false,"format":"VHD","isfeatured":false,"crossZones":true,"ostypeid":"8116119c-9604-11e2-90e0-06b27059","ostypename":"Debian
> GNU/Linux
> 6(64-bit)","account":"system","zoneid":"48b9906b-5cf7-4ed7-b623-12cbdcdc71b0","zonename":"Sandbox-XenServer1","status":"Download
>
> Complete","size":565240320,"templatetype":"SYSTEM","hypervisor":"XenServer","domain":"ROOT","domainid":"80b38fa4-9604-11e2-90e0-06b27059","isextractable":false,"checksum":"f613f38c96bf039f2e5cbf92fa8ad4f8","tags":[],"sshkeyenabled":false},
> {"id":"80c297ec-9604-11e2-90e0-06b27059","name":"CentOS 5.6(64-bit) no
> GUI (XenServer)","displaytext":"CentOS 5.6(64-bit) no GUI
> (XenServer)","ispublic":true,"created":"2013-03-26T17:07:15+0530","isready":false,"passwordenabled":false,"format":"VHD","isfeatured":true,"crossZones":true,"ostypeid":"80d1d4b4-9604-11e2-90e0-06b27059","ostypename":"CentOS
> 5.3
> (64-bit)","account":"system","zoneid":"faf4777c-2a8d-45ee-959c-bc1b0f07f3cf","zonename":"Sandbox-XenServer","status":"Connection
>
> refused","templatetype":"BUILTIN","hypervisor":"XenServer","domain":"ROOT","domainid":"80b38fa4-9604-11e2-90e0-06b27059","isextractable":true,"checksum":"905cec879afd9c9d22ecc8036131a180","tags":[],"sshkeyenabled":false},
> {"id":"80c297ec-9604-11e2-90e0-06b27059","name":"CentOS 5.6(64-bit) no
> GUI (XenServer)","displaytext":"CentOS 5.6(64-bit) no GUI
> (XenServer)","ispublic":true,"created":"2013-03-26T17:08:53+0530","isready":false,"passwordenabled":false,"format":"VHD","isfeatured":true,"crossZones":true,"ostypeid":"80d1d4b4-9604-11e2-90e0-06b27059","ostypename":"CentOS
> 5.3
> (64-bit)","account":"system","zoneid":"48b9906b-5cf7-4ed7-b623-12cbdcdc71b0","zonename":"Sandbox-XenServer1","status":"Connection
>
> refused","templatetype":"BUILTIN","hypervisor":"XenServer","domain":"ROOT","domainid":"80b38fa4-9604-11e2-90e0-06b27059","isextractable":true,"checksum":"905cec879afd9c9d22ecc8036131a180","tags":[],"sshkeyenabled":false},
> {"id":"38184ddf-bea4-4bf0-afb1-ad6fc85bd363","name":"Cent OS
> Template-FG1P2G","displaytext":"Cent OS
> Template","ispublic":true,"created":"2013-03-27T02:51:35+0530","isready":false,"passwordenabled":true,"format":"VHD","isfeatured":false,"crossZones":false,"ostypeid":"80d1d4b4-9604-11e2-90e0-06b27059","ostypename":"CentOS
> 5.3
> (64-bit)","account":"test-YAEZQZ","zoneid"
[jira] [Resolved] (CLOUDSTACK-1806) Change category and url on CloudStack's JIRA page
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Nalley resolved CLOUDSTACK-1806. -- Resolution: Fixed URL changed. I don't have karma to change category. Please file a ticket with INFRA for that. > Change category and url on CloudStack's JIRA page > - > > Key: CLOUDSTACK-1806 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1806 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: David Nalley > > Change the category and url on CloudStack's JIRA page: > https://issues.apache.org/jira/browse/CLOUDSTACK > Assigned to David as he's mentioned as Lead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1733) [ACS41][UI] Add guest network is missing ip range fields and missing network offerings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611471#comment-13611471 ] David Nalley commented on CLOUDSTACK-1733: -- Jessica: Screenshots were in the link he provided for the ticket: https://www.diigo.com/item/image/3qjce/3m5o > [ACS41][UI] Add guest network is missing ip range fields and missing network > offerings > -- > > Key: CLOUDSTACK-1733 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1733 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: ACS 4.1 as of 03/18/2013 >Reporter: ilya musayev >Assignee: Jessica Wang >Priority: Blocker > Labels: UI > Fix For: 4.1.0 > > Attachments: jessica_01.PNG, jessica_02.PNG, jessica_03.PNG > > > Noticed 2 issues in latest ACS41 when I attempt to add a network using > Advanced Zones shared network - "without natting". > Issue 1: > Network Offering has DefaultIsolatedWithSourceNat - I don't see the network > offering I've created. > Issue 2: > IPv4 IP Range is no longer visible. Previous (2 weeks back) behavior was, we > had IPv6 enabled and required, now we are missing both IPv4 and IPv6. > https://www.diigo.com/item/image/3qjce/3m5o -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
