Error Unable To Retrieve Quota Information
Contents |
1885 26 ●4 ●8 ●11
Error Unauthorized Unable To Retrieve Quota Information
updated 2014-12-31 19:35:08 -0500 9lives 1223 ●20 ●37 ●40 openstack unable to get quota information http://ilives.tk/ Test server: Hardware - Lenovo y50 - 16GB RAM - /boot
Openstack Error Unable To Get Quota Info
swap (32GB) / (root about 50 GB) /home 120GB duel boot with window 8.1 Error from admin user: Error: Unable to unable to retrieve usage information retrieve network quota information. Errors from demo user: Error: Unable to retrieve list of security groups Error: Unable to retrieve networks. When I try to start a test instance I get these errors: Danger: There was an error submitting the form. Please try devstack unable to retrieve usage information again. Error: Unable to retrieve networks. Error: Unable to retrieve list of security groups My network is: 192.168.1.0/24 Here is the nova-compute.log 2014-12-31 11:30:47.818 6277 INFO nova.compute.resource_tracker [-] Compute_service record updated for vita.io:vita.io 2014-12-31 11:31:47.792 6277 ERROR nova.compute.manager [-] [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] An error occurred while refreshing the network cache. 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] Traceback (most recent call last): 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5345, in _heal_instance_info_cache 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] self._get_instance_nw_info(context, instance, use_slave=True) 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1231, in _get_instance_nw_info 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] instance) 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a471af2a8] File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 598, in get_instance_nw_info 2014-12-31 11:31:47.792 6277 TRACE nova.compute.manager [instance: f90392b0-2b8b-490a-b0b5-e66a47
2015-01-30 23:40:48 -0500 Waid 61 ●4 ●6 ●8 updated 2015-01-31 00:06:39 -0500 Hi there, I'd installed the OpenStack by devStack successfully(installed in VirtualBox Ubuntu 12.04). After that , I
Error Unable To Retrieve Instances Openstack
can connect to the dashboard by the Chrome browser. But the first openstack error unable to retrieve hypervisor information warning jumped out 'Error: Unable to retrieve usage information' after I logged in. Then I press 'Project' and it showed
Error: Unable To Retrieve Network Quota Information.
'Error: Unable to retrieve usage information.' I found that no matter what I pressed, it always get the messages to inform me that it can't retrieve anything. And when I press 'image', https://ask.openstack.org/en/question/57377/error-unable-to-retrieve-network-quota-information/ a page show up with title: CommunicationError at /project/images/ Error finding address for htt p://10.0.1.15: 9292/v1/images/detail?sort_key=created_at&sort_dir=desc&limit=1000: ('Connection aborted.', error(111, 'Connection refused')) I am a newbie don't know where to check. Not sure what's wrong with it. Any help? I am glad to provide further info. if you like. edit retag flag offensive close merge delete add a comment 2 answers Sort by ยป oldest newest https://ask.openstack.org/en/question/59904/dashboard-cant-retrieve-anything-or-do-anything/ most voted 1 answered 2015-01-31 10:34:34 -0500 Waid 61 ●4 ●6 ●8 updated 2015-01-31 10:54:44 -0500 Now the problem is solved, I give my solution as a reference: The problem occurred when I set my localrc as the following: HOST_IP=10.0.1.15 FLAT_INTERFACE=eth0 FLOATING_RANGE={-...not important for this case} (module passwords....) Here, my network setting is actually: eth0:dhcp(Virtualbox NAT give it IP), eth1: static IP: 10.0.1.15(Virtualbox host-only network) The problem is solved by setting localrc as the following: HOST_IP=10.0.1.15 FLAT_INTERFACE=br100 PUBLIC_INTERFACE=eth1 FLOATING_RANGE={-...not important for this case} (module passwords....) In this setting, I changed my /etc/network/interfaces as: eth0:dhcp, br100+eth1:static IP:10.0.1.15 I guess the problem is solved because I changed FLAT_INTERFACE from eth0 to eth1. eth1 is the entry to the openstack host. edit flag offensive delete link more add a comment 0 answered 2015-01-31 01:57:30 -0500 Yashpal Beppurana 314 ●2 ●10 http://www.Pthinks.com/ Hi Waid, 1. Ensure whether your database is working properly. 2. Enable the logs, and try to figure out the cause. To enable log, add the following lines to the localrc file. LOGFILE=/opt/stack/logs/stack.sh.log SCREEN_LOGDIR=/opt/stack/logs/screen edit flag offensive delete link more CommentsI, like Waid, am new to openstack.Experiencing the same error. Pretty sure that its
web user interface openstack; horizon; adminUI; httpd; disabled Technote (troubleshooting) Problem(Abstract) http://www.ibm.com/support/docview.wss?uid=swg21700503 You attempt to display hypervisor, instances, and images information using https://answers.launchpad.net/horizon/+question/181166 the IBM Cloud Orchestrator Administration user interface. However, it results in various errors including "unable to retrieve usage information. Symptom The user interface displays error messages like the following text: Error: Unable to retrieve usage information Error: Unable to retrieve unable to limit information Error: Unable to retrieve floating IP addresses Error: Unable to retrieve security groups Error: Unable to retrieve network quota information Error: Unable to retrieve volume limit information The following screen shot illustrates the error messages that are displayed in the user interface: Cause Local operating system user accounts might unable to retrieve have become disabled or passwords might have expired. Diagnosing the problem The openstack-dashboard-error.log file contains HTTP 500 and other errors. For example: [Tue Mar 24 18:56:47 2015] [error] Recoverable error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-4e36fa7a-91da-4285-b94b-fbcf46120568) Resolving the problem Check the following database user accounts on Central Server 1 to determine if their password have expired: db2das1 db2inst1 db2fenc1 In addition, check all openstack-related accounts on Central Server 1 and the region servers to ensure they are not disabled. For example: nova dash keystone glance ceil neutron cinder heat Document information More support for: IBM Cloud Orchestrator User Interface Software version: 2.4, 2.4.0.1 Operating system(s): Linux Reference #: 1700503 Modified date: 2015-03-25 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
from https://github.com/openstack/horizon everything is fine until I've logged in to openstack-dashboard it's say Error: Unable to get service info: This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required. Error: Unable to get usage info: This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required. There are 2 errors that says Unable to get service&usage info I've tried in everyway but can't solved my problem. Question information Language: English Edit question Status: Answered For: OpenStack Dashboard (Horizon) Edit question Assignee: No assignee Edit question Last query: 2011-12-08 Last reply: 2015-08-24 Related bugs Link existing bug Related FAQ: None Link to a FAQ Gabriel Hurley (gabriel-hurley) said on 2011-12-07: #1 This error is related to the rest of your openstack deployment. It is most often caused by mismatched service tokens between nova, keystone, etc. but similar errors can also be raised by failure to have the openstackx extensions properly installed with nova or bad service endpoint data in keystone causing connection errors. My first suggestion, though, would be to check all your conf/proxy server files (nova, keystone, glance, etc.) and make sure they match the correct admin service token defined by keystone. piyadol (piyadol-h) said on 2011-12-08: #2 Thanks for your answered Gabriel but I've already checked all config files but still got the same error.Here is my config file keystone.conf,nova.conf,api-pase.ini ##Keystone.conf## [DEFAULT] # Show more verbose log output (sets INFO log level output) verbose = False # Show debugging output in logs (sets DEBUG log level output) debug = False # Which backend store should Keystone use by default. # Default: 'sqlite' # Available choices are 'sqlite' [future will include LDAP, PAM, etc] default_store = sqlite # Log to this file. Make sure you do not set the same log # file for both the API and registry servers! log_file = keystone.log log_dir = . # List of backends to be configured backends = keystone.backends.sqlalchemy #For LDAP support, add: ,keystone.backends.ldap # Dictionary Maps every service to a header.Missing services would get header # X_(SER