cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nuno Tavares (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-8140) secstorage.service.offering in GS set to service offering ID Webui fails to start
Date Fri, 02 Jan 2015 16:24:13 GMT
Nuno Tavares created CLOUDSTACK-8140:
----------------------------------------

             Summary: secstorage.service.offering in GS set to service offering ID Webui fails
to start
                 Key: CLOUDSTACK-8140
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8140
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.1
            Reporter: Nuno Tavares


Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected in next versions:

It seems secstorage.service.offering setting in GS is expecting an integer ID instead of the
typical GUID. According to Nitin Mehta it's a bug, and here is the bug report. 

I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results

Not sure why/if it is directly related, if I set any value with
update configuration set value = XXXXX where name = 'secstorage.service.offering';

the management server will not launch properly. After restarting, this is what I get:

🐵 > list capabilities
Error: The given command:listCapabilities does not exist or it is not available for user with
id:null
🐵 > list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available for user with
id:null

(mgt server logs complain about listCapabilites as well).

After setting the value to NULL everything comes back well.




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

Mime
View raw message