ec2-* and euca-* not working for non-admin credentials

Bug #453177 reported by John O'loughlin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
Invalid
Undecided
chris grzegorczyk
eucalyptus (Ubuntu)
Fix Released
Critical
Dustin Kirkland 
Karmic
Fix Released
Critical
Dustin Kirkland 

Bug Description

I'm using Ubuntu 9.10 and have installed UEC, I have one cloud/cluster controller and two nodes.

As a user with admin credentials I can upload an run images and my instances are reported correctly with ec2-describe-instances (and also euca-describe-instances). However, as a user with non-admin credentials I can start an instance (and verify its running by tailing the nc logs on the nodes and then sshing to them after) but ec2-describe-instances does not report these properly.

I get the message:

jo0006@orion:~/euca1.6$ ec2-describe-instances
VmControl: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'

On the cloud controller, from cloud-output.log:

15:00:37 WARN NetworkStateHandler | Response from cluster [nebula]: NOTSUPPORTED
15:00:41 INFO ServiceSinkHandler | :1255701632.0000:eucalyptus/ServiceSinkHandler.handleUpstream.189:eucalyptus:eucalyptus:MSG_RECEIVED:DescribeInstancesType:
15:00:41 ERROR VmControl | org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
15:00:41 ERROR tServiceExceptionStrategy |
                                         | ********************************************************************************
                                         | Message : Component that caused exception is: VmControl. Message payload is of type: DescribeInstancesType
                                         | Type : org.mule.api.service.ServiceException
                                         | Code : MULE_ERROR--2
                                         | Payload : <?xml version="1.0" encoding="UTF-8"?>
                                         | <euca:DescribeInstances xmlns:euca="http://msgs.eucalyptus.ucsb.edu">
                                         | <euca:VmControlMessage>
                                         | <euca:correlationId>2608a852-b7f0-47fe-81f1-a3d79864b0c9</euca:correlationId>
                                         | <euca:userId>peter</euca:userId>
                                         | <euca:effectiveUserId>peter</euca:effectiveUserId>
                                         | </euca:VmControlMessage>
                                         | <euca:instancesSet/>
                                         | </euca:DescribeInstances>
                                         | JavaDoc : http://mule.mulesource.org/docs/apidocs/org/mule/api/service/ServiceException.html
                                         | ********************************************************************************
                                         | Exception stack is:
                                         | 1. Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java' (com.eucalyptus.util.EucalyptusCloudException)
                                         | edu.ucsb.eucalyptus.cloud.ws.VmControl:91 (null)
                                         | 2. Component that caused exception is: VmControl. Message payload is of type: DescribeInstancesType (org.mule.api.service.ServiceException)
                                         | org.mule.component.DefaultLifecycleAdapter:214 (http://mule.mulesource.org/docs/apidocs/org/mule/api/service/ServiceException.html)
                                         | ********************************************************************************
                                         | Root Exception stack trace:
                                         | com.eucalyptus.util.EucalyptusCloudException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
                                         | at edu.ucsb.eucalyptus.cloud.ws.VmControl.DescribeInstances(VmControl.java:91)
                                         | 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.mule.model.resolvers.AbstractEntryPointResolver.invokeMethod(AbstractEntryPointResolver.java:147)
                                         | at org.mule.model.resolvers.ReflectionEntryPointResolver.invoke(ReflectionEntryPointResolver.java:127)
                                         | at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:50)
                                         | at org.mule.component.DefaultLifecycleAdapter.intercept(DefaultLifecycleAdapter.java:202)
                                         | at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:82)
                                         | at org.mule.component.AbstractJavaComponent.doOnCall(AbstractJavaComponent.java:73)
                                         | at org.mule.component.AbstractComponent.onCall(AbstractComponent.java:87)
                                         | at org.mule.model.seda.SedaService$ComponentStageWorker.run(SedaService.java:533)
                                         | at org.mule.work.WorkerContext.run(WorkerContext.java:310)
                                         | at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
                                         | at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
                                         | at java.lang.Thread.run(Thread.java:636)

John

Revision history for this message
Neil Soman (neilsoman) wrote :

I have linked this against the package. I can't reproduce it against a source install.

Changed in eucalyptus (Ubuntu):
status: New → In Progress
importance: Undecided → Critical
Changed in eucalyptus:
status: New → In Progress
Changed in eucalyptus (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
milestone: none → ubuntu-9.10
summary: - ec2-describe-instances not working for non-admin credentials
+ ec2-* and euca-* not working for non-admin credentials
Changed in eucalyptus (Ubuntu):
status: In Progress → Fix Committed
Changed in eucalyptus:
assignee: nobody → chris grzegorczyk (chris-grze)
status: In Progress → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6~bzr931-0ubuntu4

---------------
eucalyptus (1.6~bzr931-0ubuntu4) karmic; urgency=low

  [ Kees Cook ]
  * Fix unsafe /tmp file uses (LP: #445105):
    - tools/detach.pl: remove debugging XML dump call.
    - node/handlers_xen.c: use mkstemp().

  [ Mathias Gug ]
  * debian/eucalyptus-common.eucalyptus.upstart: Start eucalyptus-cloud
    with all the relevant options (LP: #452665).

  [ Dustin Kirkland ]
  * cluster/handlers.c, net/vnetwork.c: label the 169.254.169.254 link
    local address with :metadata, the public vm ip addresses with :pub,
    and the private vm ip addresses with :priv, to separate it appropriately
    (LP: #452754)
  * debian/eucalyptus-ipaddr.conf: and now that we're separating the weird
    addresses to their own labels, we can show just the device label, much
    cleaner output, (LP: #451607)
  * debian/copyright: Eucalyptus licensed 1.6 under the GPLv3, update
    our copyright file accordingly, (LP: #453129)
  * debian/control, debian/eucalyptus-java-common.links: the CLC absolutely
    needs the ecj.jar installed and linked for euca-* and ec2-* API calls
    to work (LP: #453177)

 -- Dustin Kirkland <email address hidden> Fri, 16 Oct 2009 13:28:32 -0500

Changed in eucalyptus (Ubuntu Karmic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.