How to list ipaddressid
Hi Guys, I am trying to use cloudmonkey to create a firewall rule: create firewallrule protocol=udp cidrlist=0.0.0.0/12 ipaddressid=... My question is this: How do I know which ipaddressid to use. I can create the rule successfully if I first do: "list firewallrules listall=true" and then use the ipaddressid I see in the output. But how do I know which ipaddressid to supply if I don't first list them OR if its the first rule I'm creating? Thanks, Fred PS: The command completion on cloudmonkey is terrific!!! Good job!
Re: How to list ipaddressid
Thanks for your help Jayapal. I should have stated earlier that I added the first three firewalls thru the web GUI. When I list the public IPs like soI don't see any IDs that match what I see when I list the firewall rules that I added thru the GUI > list publicipaddresses listall=true count = 1 publicipaddress: id = a2ed3fda-c343-4282-bbb4-603064f2893a account = admin allocated = 2013-05-08T09:41:39-0400 associatednetworkid = dcea58f0-16d0-4968-a04c-3d9749909434 domain = ROOT domainid = b2f28f25-c26f-415c-9b28-edfea50e65f2 forvirtualnetwork = True ipaddress = 192.168.220.31 issourcenat = True isstaticnat = False issystem = False networkid = ce820e86-a07b-454f-ad11-c4e8fcb46fb0 physicalnetworkid = d625e56c-ec75-44bc-87c6-17760f801d7c state = Allocated vlanid = 712aaca4-6a14-42da-84f1-f5337b83c8fb vlanname = untagged zoneid = a5b1138d-d15c-4480-aca6-f0ae1f363955 zonename = Zone-0 now the rirewall rules.I added these with the GUI. Note the ipaddressid = 32s.When I create a rule thru cloudmonkey and specify ipaddressID=32, the rule gets added and I can then see it thru the GUI when I refresh. > list firewallrules listall=true count = 3 firewallrule: id = 0dbfc6c6-f1f7-491e-a3de-71f3b06a7bd6 cidrlist = 0.0.0.0/12 ipaddress = 192.168.220.31 ipaddressid = 32 protocol = udp state = Active id = 6010b6b6-7e82-48e7-9682-8272a35bd7f1 cidrlist = 0.0.0.0/11 endport = 64000 ipaddress = 192.168.220.31 ipaddressid = 32 protocol = udp startport = 11 state = Active id = 07c18ef0-9ae4-471b-ad5d-8f8675fdc20f cidrlist = 0.0.0.0/0 icmpcode = -1 icmptype = -1 ipaddress = 192.168.220.31 ipaddressid = 32 protocol = icmp state = Active On Mon, May 20, 2013 at 9:59 AM, Jayapal Reddy Uradi < jayapalreddy.ur...@citrix.com> wrote: > Try the list public ip addresses using listPublicIpAddresses API. > > Thanks, > Jayapal > > On 20-May-2013, at 5:04 PM, Fred Messinger > wrote: > > > Hi Guys, > > > > I am trying to use cloudmonkey to create a firewall rule: > > create firewallrule protocol=udp cidrlist=0.0.0.0/12 ipaddressid=... > > > > My question is this: How do I know which ipaddressid to use. I can > create > > the rule successfully if I first do: > > > > "list firewallrules listall=true" > > > > and then use the ipaddressid I see in the output. But how do I know > which > > ipaddressid to supply if I don't first list them OR if its the first rule > > I'm creating? > > > > Thanks, > > Fred > > > > PS: The command completion on cloudmonkey is terrific!!! Good job! > >
Re: Doc Updates
Agreed Carlos. I've spent all day reading said emails and trying to wrangle through this problem myself. How to update the templates is here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack# but even getting that to work was an adventure. On Thu, Oct 10, 2013 at 2:44 PM, Carlos Reategui wrote: > On Thu, Oct 10, 2013 at 10:48 AM, David Nalley wrote: > > > That is how it has been done previously - but we recently moved docs > > to their own repo to separate the software lifecycle from the docs > > lifecycle, and we have already had at least one update pushed to the > > docs post-release. > > Over the past couple weeks a good percentage of the emails to the list have > been caused due to the wrong template URL in the installation docs. I just > had a look and they are still pointing to the old templates. > Along the same lines the other problem most people have had is not knowing > to upgrade the templates when upgrading from 4.1 to 4.2. Just had a look > at the docs and that is still not been updated. > > I would have thought this would have been a high priority to fix and would > have been in that first update given the number of people running into > these. > > > > > The goal is to try and keep this up, and I hope to > > publish another set of updates tomorrow or over the weekend. > > > > Bad docs make even the best software unusable IMO. That said, we could > > use more eyeballs - at least identify the problems for us. Bonus > > points for fixes. > > > Can you point us to a guide on how to make doc fixes? Is this in git? I > though I just saw a reference to SVN in another email in this thread. > > > > > > --David > > > > On Wed, Oct 9, 2013 at 4:24 PM, Carlos Reategui > > wrote: > > > It seems like the only way that docs ( > > > http://cloudstack.apache.org/docs/en-US/index.html) are updated is > when > > a > > > release is done. Is it not possible to have these updated otherwise? > > > Waiting for the next patch release of the software so that the docs > get > > > updated is causing problems with folks not being able to get CloudStack > > > installed properly and therefore gives them a bad impression of the > > > maturity of CloudStack. > > > > > > It makes no sense to me why there are multiple versions of documents > for > > > each of the point releases (currently there is 4.0.0, 4.0.1, 4.0.2, > > 4.1.0, > > > 4.1.1 and 4.0.2 docs) when the feature set has not changed within each > of > > > these. I understand that the docs are built as part of the build and > > > release process but why does that have to impact the rate at which the > > > primary doc site is updated. Can't the patch releases simply update > the > > > release notes? Personally I think there should be a single 4.x version > > of > > > the docs (I would be ok with a 4.0, 4.1 and 4.2 versions too if major > > > features are going to be added to them). Maybe the doc site should > have > > > wiki like capabilities so that it can be more easily maintained. > > > > > > ok, I am done ranting... > > >
Is this how we should be building debian packages for a vmware centric cloudstack?
Hi All, Since I'm trying to build the non-oss version from the most recent 4.2 Installation Guide on http://jenkins.buildacloud.org I followed these steps: $ sudo apt-get update $ sudo apt-get install python-software-properties $ sudo add-apt-repository ppa:natecarlson/maven3 $ sudo apt-get update $ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6 libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven3 $ mvn3 -P deps $ dpkg-buildpackage -uc -us The docs state these packages will be generated: cloud-agent_4.0.0-incubating_amd64.deb cloud-agent-deps_4.0.0-incubating_amd64.deb cloud-agent-libs_4.0.0-incubating_amd64.deb cloud-awsapi_4.0.0-incubating_amd64.deb cloud-cli_4.0.0-incubating_amd64.deb cloud-client_4.0.0-incubating_amd64.deb cloud-client-ui_4.0.0-incubating_amd64.deb cloud-core_4.0.0-incubating_amd64.deb cloud-deps_4.0.0-incubating_amd64.deb cloud-python_4.0.0-incubating_amd64.deb cloud-scripts_4.0.0-incubating_amd64.deb cloud-server_4.0.0-incubating_amd64.deb cloud-setup_4.0.0-incubating_amd64.deb cloud-system-iso_4.0.0-incubating_amd64.deb cloud-usage_4.0.0-incubating_amd64.deb cloud-utils_4.0.0-incubating_amd64.deb But, in fact the only packages that are generated are ../cloudstack-agent_4.2.0_all.deb ../cloudstack-awsapi_4.2.0_all.deb ../cloudstack-cli_4.2.0_all.deb ../cloudstack-common_4.2.0_all.deb ../cloudstack-docs_4.2.0_all.deb ../cloudstack-management_4.2.0_all.deb ../cloudstack-usage_4.2.0_all.deb And by the way, this is after I followed the instructions on https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack# for updating the deps directory with respect to vhdutil and others like vim25_51 etc. Is this expected? Second point...After it's all daid and done and I follow the rest of the installation enstructions, I still end up getting a recurring exception: 2013-10-15 14:32:55,586 WARN [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:null) Unable to find class com.cloud.hypervisor.vmware.resource.VmwareResource java.lang.ClassNotFoundException: com.cloud.hypervisor.vmware.resource.VmwareResource at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:188) at com.cloud.agent.manager.AgentManagerImpl.loadResourcesWithoutHypervisor(AgentManagerImpl.java:667) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:741) Management-server.log file attached. Thanks in advance to anyone who can provide insights; I'be been battling this dragon for a week. I tried including my log file, but I think it's too big; the apache mailer barfed.
Re: Is this how we should be building debian packages for a vmware centric cloudstack?
Thanks, Travis, Doc bug 4873 submitted. On Tue, Oct 15, 2013 at 3:01 PM, Travis Graham wrote: > I can only speak to the first part. There should only be 7 packages > generated, not the 16 referenced on the cwiki page. > > Travis > > On Oct 15, 2013, at 2:55 PM, Fred Messinger > wrote: > > > Hi All, > > > > Since I'm trying to build the non-oss version from the most recent 4.2 > > Installation Guide on http://jenkins.buildacloud.org I followed these > > steps: > > > > $ sudo apt-get update > > $ sudo apt-get install python-software-properties > > $ sudo add-apt-repository ppa:natecarlson/maven3 > > $ sudo apt-get update > > $ sudo apt-get install ant debhelper openjdk-6-jdk tomcat6 > > libws-commons-util-java genisoimage python-mysqldb libcommons-codec-java > > libcommons-httpclient-java liblog4j1.2-java maven3 > > $ mvn3 -P deps > > $ dpkg-buildpackage -uc -us > > > > > > The docs state these packages will be generated: > > > > cloud-agent_4.0.0-incubating_amd64.deb > > cloud-agent-deps_4.0.0-incubating_amd64.deb > > cloud-agent-libs_4.0.0-incubating_amd64.deb > > cloud-awsapi_4.0.0-incubating_amd64.deb > > cloud-cli_4.0.0-incubating_amd64.deb > > cloud-client_4.0.0-incubating_amd64.deb > > cloud-client-ui_4.0.0-incubating_amd64.deb > > cloud-core_4.0.0-incubating_amd64.deb > > cloud-deps_4.0.0-incubating_amd64.deb > > cloud-python_4.0.0-incubating_amd64.deb > > cloud-scripts_4.0.0-incubating_amd64.deb > > cloud-server_4.0.0-incubating_amd64.deb > > cloud-setup_4.0.0-incubating_amd64.deb > > cloud-system-iso_4.0.0-incubating_amd64.deb > > cloud-usage_4.0.0-incubating_amd64.deb > > cloud-utils_4.0.0-incubating_amd64.deb > > > > > > But, in fact the only packages that are generated are > > > > ../cloudstack-agent_4.2.0_all.deb > > ../cloudstack-awsapi_4.2.0_all.deb > > ../cloudstack-cli_4.2.0_all.deb > > ../cloudstack-common_4.2.0_all.deb > > ../cloudstack-docs_4.2.0_all.deb > > ../cloudstack-management_4.2.0_all.deb > > ../cloudstack-usage_4.2.0_all.deb > > > > > > > > And by the way, this is after I followed the instructions on > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack# > > for updating the deps directory with respect to vhdutil and others like > > vim25_51 etc. > > > > Is this expected? > > > > Second point...After it's all daid and done and I follow the rest of the > > installation enstructions, I still end up getting a recurring exception: > > > > 2013-10-15 14:32:55,586 WARN [agent.manager.AgentManagerImpl] > > (ClusteredAgentManager Timer:null) Unable to find class > > com.cloud.hypervisor.vmware.resource.VmwareResource > > java.lang.ClassNotFoundException: > > com.cloud.hypervisor.vmware.resource.VmwareResource > >at > > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680) > >at > > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526) > >at java.lang.Class.forName0(Native Method) > >at java.lang.Class.forName(Class.java:188) > >at > > > com.cloud.agent.manager.AgentManagerImpl.loadResourcesWithoutHypervisor(AgentManagerImpl.java:667) > >at > > > com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:741) > > > > Management-server.log file attached. > > > > Thanks in advance to anyone who can provide insights; I'be been battling > > this dragon for a week. > > I tried including my log file, but I think it's too big; the apache > mailer > > barfed. > >
Re: Doc Updates
David, Would you mind posting the url for the update you reference? I'm looking at the 4.2 view on buildacloud.com and the last update there was a month ago. So I assume I'm looking in the wrong place. Thanks, Fred On Mon, Oct 14, 2013 at 2:07 PM, David Nalley wrote: > And just as a heads up, thanks for help from Prasanna and Travis, I've > published an updated version of the IG for 4.2, hopefully that at > least gets us 'installable'. > > --David > > On Thu, Oct 10, 2013 at 2:10 PM, David Nalley wrote: > > On Thu, Oct 10, 2013 at 1:53 PM, Travis Graham > wrote: > >> What's an acceptable/expected timeframe for rolling out the published > fixes once a patch has made it's way in? Is that something that can be > automated after a successful Jenkins run? > >> > >> Travis > >> > > > > It depends on the scope of changes. For a document like the release > > notes, assuming someone already has an updated SVN tree, it shouldn't > > take more than 30 minutes to update, and it could happen pretty > > regularly. If it's every document in a single release, that's > > historically taken the better part of a day. I don't think we'll get > > away with getting it to happen in an automated fashion, simply because > > it requires commit access to SVN, which is tied to an individual, > > which means someone would need to expose their creds, which would be a > > bad thing. > > > > --David >
Missing jar vmware-lib-jaxrpc.jar?
Hi All, I'm trying to upgrade from 4.1.1 to 4.2 using vmware. And I think I am SO close! My management server log file is attached. It describes some deserialization problems and it also shows that a VMware resource class file cannot be loaded. From googling the exception, I found this jira ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-211 Is the reason I can't start my ssvm because of this? Thanks, Fred
How to clean systmVM from the database?
I've download a new system VM and used cloudstack-sysvmadm to try to stop the old ones... root@cloudstack:~# cloudstack-sysvmadm -d -u cloud -p dbpassword -a Stopping and starting 1 secondary storage vm(s)... ERROR: Failed to stop secondary storage vm with id 1 Done stopping and starting secondary storage vm(s) Stopping and starting 1 console proxy vm(s)... ERROR: Failed to stop console proxy vm with id 2 Done stopping and starting console proxy vm(s) . Stopping and starting 0 running routing vm(s)... I also can't seem to stop the systemvms by using the GUI. Can I just shut them down in vSphere and delete them from the DB using mysql commands? Help!!!
Building 4.2 -nonoss
Hi,
I've followed the instructione for building 4.2 -nonoss from source here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#
Couple things...the install-non-oss.sh is a little different for 4.2 than
it was for 4.1.1 and 4.1 in that it does not process the
cloud-netscaler.jar any more? Is this intentional?
Second thing is this from the management-server.log - I seem to be missing
a load balancer bean?
2013-10-18 07:33:13,382 ERROR [web.context.ContextLoader] (main:null)
Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'apiDBUtils': Injection of autowire
d dependencies failed; nested exception is
org.springframework.beans.factory.BeanCreationException: Could not autowire
field: private
com.cloud.region.ha.GlobalLoadBalancingRulesService
com.cloud.api.ApiDBUtils.gslbService; nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No
matching bean of type [com.cloud.region.ha.GlobalLoadB
alancingRulesService] found for
dependency: expected at least 1 bean which qualifies as autowire candidate
for this depend
ency. Dependency annotations: {@javax.inject.Inject()}
at
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(Aut
owiredAnnotationBeanPostProcessor.java:287)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapab
leBeanFactory.java:1106)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapab
leBeanFactory.java:517)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapable
BeanFactory.java:456)
Suggestions?
Thanks for your help,
Fred
Re: Missing jar vmware-lib-jaxrpc.jar?
Hi Daan, I was reluctant to do that because of this: git commit: CLOUDSTACK-346: Replace vmware-lib-jaxrpc with axis-jaxrpc The fact that I was seeing something trying to load this class meant that something was very wrong. Which makes me suspect the dependencies section on this page: https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack# Is this documentation still good? Thanks, Fred On Thu, Oct 17, 2013 at 1:38 PM, Daan Hoogland wrote: > Fred, > > Attachements are stripped from maila to the list. It sounds like this > is your problem yes. Why don't you try adding the jar and restarting > the ms? > > regards, > Daan > > On Wed, Oct 16, 2013 at 3:04 PM, Fred Messinger > wrote: > > Hi All, > > > > I'm trying to upgrade from 4.1.1 to 4.2 using vmware. And I think I am > > SO close! > > > > My management server log file is attached. It describes some > > deserialization problems and it also shows that a VMware resource class > file > > cannot be loaded. From googling the exception, I found this jira ticket: > > > > https://issues.apache.org/jira/browse/CLOUDSTACK-211 > > > > Is the reason I can't start my ssvm because of this? > > > > Thanks, > > Fred >
Re: Running devcloud on dom0
Thanks for the info Travis. Perhaps we need to update Section 3.1, step 7 of this document to reflect such: http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.1 Thanks, Fred On Mon, Oct 21, 2013 at 8:41 AM, Travis Graham wrote: > You can run both. The agent is only needed for KVM so if you aren't using > KVM you won't need it. > > Travis > > On Monday, October 21, 2013, Mario Giammarco wrote: > > > Hello, > > I have a server with ubuntu server 12.04 fresh installed. > > I would like to run on it cloudstack manager AND agent. > > I read in forum to use devcloud with nested virtualization. > > > > I wonder why I cannot install cloudstack server and agent directly on my > > dom0. > > > > Is it possible? > > Thanks, > > Mario > > > > >
Can not delete port forwarding rule with UI in 4.1.1 Is there a global parameter timeout for this?
This is what I did using the UI:
added a guest network in my advance zone,
added a guest to the network,
opened up a firewall on the network
added a port forwarding rule, specifying my guest
And this seemed to work. Database updated as expected. Log messages
seemed ok too.
THEN! using the UI, I trieddeleting the port forwarding rule I just
created.
Internal Server error.
Pertinent log messages:
2013-10-22 08:14:14,087 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
===START=== 192.168.220.1 -- GET
command=deletePortForwardingRule&response=json&sessionkey=YwEeHOyxyQa9chYMY4VtUbIQPe8%3D&id=2cbaa440-c4b1-4472-a27b-28c71f7c1dcf&_=1382444054170
2013-10-22 08:14:14,147 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-9:null) submit async job-39, details: AsyncJobVO {id:39,
userId: 2, accountId: 2, sessionKey: null, instanceType: FirewallRule,
instanceId: null, cmd:
org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd,
cmdOriginator: null, cmdInfo:
{"response":"json","id":"2cbaa440-c4b1-4472-a27b-28c71f7c1dcf","sessionkey":"YwEeHOyxyQa9chYMY4VtUbIQPe8\u003d","ctxUserId":"2","_":"1382444054170","ctxAccountId":"2","ctxStartEventId":"178"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 345052229336,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-10-22 08:14:14,153 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-44:job-39) Executing
org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd
for job-39
2013-10-22 08:14:14,155 DEBUG [cloud.api.ApiServlet] (catalina-exec-9:null)
===END=== 192.168.220.1 -- GET
command=deletePortForwardingRule&response=json&sessionkey=YwEeHOyxyQa9chYMY4VtUbIQPe8%3D&id=2cbaa440-c4b1-4472-a27b-28c71f7c1dcf&_=1382444054170
2013-10-22 08:14:14,172 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-44:job-39) Sync job-39 execution on object network.212
2013-10-22 08:14:14,185 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-44:job-39) job
org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd
for job-39 was queued, processing the queue.
2013-10-22 08:14:14,200 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-44:job-39) Executing sync queue item: SyncQueueItemVO {id:18,
queueId: 19, contentType: AsyncJob, contentId: 39, lastProcessMsid:
345052229336, lastprocessNumber: 5, lastProcessTime: Tue Oct 22 08:14:14
EDT 2013, created: Tue Oct 22 08:14:14 EDT 2013}
2013-10-22 08:14:14,202 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-44:job-39) Schedule queued job-39
2013-10-22 08:14:14,241 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-45:job-39) Executing
org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd
for job-39
2013-10-22 08:14:14,242 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-44:job-39) There is a pending process in sync queue(id: 19)
2013-10-22 08:14:14,285 DEBUG [db.Transaction.Transaction]
(Job-Executor-45:job-39) Rolling back the transaction: Time = 5 Name =
-AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
called by
-Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-RulesManagerImpl.revokePortForwardingRuleInternal:571-RulesManagerImpl.revokePortForwardingRule:562-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-DeletePortForwardingRuleCmd.execute:98-ApiDispatcher.dispatch:162-AsyncJobManagerImpl$1.run:437-Executors$RunnableAdapter.call:471
2013-10-22 08:14:14,336 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-45:job-39) Unexpected exception while executing
org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd
java.lang.NullPointerException
at
com.cloud.event.UsageEventUtils.publishUsageEvent(UsageEventUtils.java:132)
at
com.cloud.event.UsageEventUtils.publishUsageEvent(UsageEventUtils.java:73)
at
com.cloud.network.firewall.FirewallManagerImpl.revokeRule(FirewallManagerImpl.java:710)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.network.rules.RulesManagerImpl.revokePortForwardingRuleInternal(RulesManagerImpl.java:571)
at
com.cloud.network.rules.RulesManagerImpl.revokePortForwardingRule(RulesManagerImpl.java:562)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.firewall.DeletePortForwardingRuleCmd.execute(DeletePortForwardingRuleCmd.java:98)
at com.cloud.api.ApiDispatcher.disp
Re: 4.2.0 Upgrade and System Templates (KVM - Ubuntu 12.04)
Marty, I think the place to go for the most up to date docs is here: http://jenkins.buildacloud.org/view/4.2/ Fred On Sat, Oct 26, 2013 at 4:51 PM, Marcus Sorensen wrote: > Yes, you do need to upgrade your system VMS, and you should also have a new > systemvm.iso that was bundled in the cloudstack-common deb file that would > have been installed as an upgrade on your KVM hosts. I also feel that the > documentation of system vm upgrade is lacking. The only place I know if is > in the release notes: > > http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html-single/Release_Notes/index.html > , > see 3.1 "Upgrade Instructions", item 12. It references a script > "cloudstack-sysvmadm", but the upgrade of the system vm template should be > done beforehand. Now look at the section just below, 3.2. This > documentation is obviously messed up because it first says "this applies > only to VMware", and then it promptly gives system vm upgrade instructions > for XenServer, KVM, and VMWare hosts. It's unclear why this system vm > upgrade would only apply to zones which had VMware hosts, and why these > instructions aren't also on the 4.1.x to 4.2.x instructions. At any rate, > the system vm instuctions there for KVM should apply. Register the template > (optionally, check the data base to ensure the template is set as system > type), then restart the system vms per the item 12 script. If your KVM > hosts relaunch the system vms per the new template and they have the new > systemvm.iso, they should work. > > > On Oct 26, 2013 2:19 PM, "Marty Sweet" wrote: > > > Hi Guys, > > > > I have just upgraded to 4.2.0 from 4.1.1 and am having some issues with > the > > SystemVMs. > > I understand that we are meant to upgrade to the new system image? Using > > the script in the 'Prepare systemvm' documentation I did this with no > > avail, editing the database to suit what I think would work has also not > > worked. > > > > Restoring a backup, I now have my original 4.1.1 acton systemvm > templates. > > What steps should I take to launch a systemVM successfully? > > > > The upgrade documentation is pretty lacking in this respect, and just > says > > restart the systemvms, with no reference to upgrading the image. > > > > I also note that the new systemvms don't seem to be mounting the NFS and > > are instead using /usr/share/cloudstack-common/vms/systemvm.iso. > > > > Opening a VNC session to the VM, shows the following messages: > > Cannot assign requested address: make_sock: could not bind address > > dnsmasq: unknown interface eth0 > > dnsmasq apache2 ... failed! > > > > My MD5 sum for the CD boot file is below and is consistant across all 4 > > nodes: > > 092a299932bda93cc522b1c3e56af4a8 > > /usr/share/cloudstack-common/vms/systemvm.iso > > > > > > Many thanks, > > Marty > > >
