Ask Your Question

ICBeter's profile - activity

2018-11-25 10:21:55 -0600 received badge  Notable Question (source)
2018-11-25 10:21:55 -0600 received badge  Popular Question (source)
2018-10-11 07:32:36 -0600 received badge  Famous Question (source)
2018-07-26 11:13:21 -0600 commented answer Dashboard Problem with URL of VNC Console

I resolved that with only setting novncproxy_base_url. As arbcat mentioned: on the computes nodes, NOT the controller!

2018-07-12 04:27:37 -0600 asked a question Enable Monasca in Horizon

I have an Openstack installation with running Horizon dashboard. On a different machine I installed Monasca. Now I wanted to integrate it in my Horizon.

When I copy _50_admin_add_monitoring_panel.py to /usr/share/openstack-dashboard/openstack_dashboard/enabled/ the dashboard gets completely messed up and the Firefox console gives the following error:

Error: [$injector:modulerr] Failed to instantiate module horizon.app due to:
[$injector:nomod] Module 'horizon.app' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.5.8/$injector/nomod?p0=horizon.app
minErr/<@http://controller/horizon/static/dashboard/js/732ce617825a.js:699:8
module/<@http://controller/horizon/static/dashboard/js/732ce617825a.js:818:59
ensure@http://controller/horizon/static/dashboard/js/732ce617825a.js:816:320
module@http://controller/horizon/static/dashboard/js/732ce617825a.js:818:8
loadModules/<@http://controller/horizon/static/dashboard/js/732ce617825a.js:925:35
forEach@http://controller/horizon/static/dashboard/js/732ce617825a.js:703:391
loadModules@http://controller/horizon/static/dashboard/js/732ce617825a.js:924:156
createInjector@http://controller/horizon/static/dashboard/js/732ce617825a.js:913:464
doBootstrap@http://controller/horizon/static/dashboard/js/732ce617825a.js:792:36
bootstrap@http://controller/horizon/static/dashboard/js/732ce617825a.js:793:58
angularInit@http://controller/horizon/static/dashboard/js/732ce617825a.js:789:556
@http://controller/horizon/static/dashboard/js/732ce617825a.js:1846:1383
fire@http://controller/horizon/static/dashboard/js/732ce617825a.js:208:281
fireWith@http://controller/horizon/static/dashboard/js/732ce617825a.js:213:198
ready@http://controller/horizon/static/dashboard/js/732ce617825a.js:32:1
completed@http://controller/horizon/static/dashboard/js/732ce617825a.js:14:1184

What's going wrong here? It is Openstack Queens running on Ubuntu 16.04.

2018-07-11 16:31:54 -0600 commented question Monasca: Forbidden or unreachable?

Thanks! Indeed the problem was that the monasca user did not have the necessary roles.

2018-07-09 12:37:49 -0600 asked a question Monasca: Forbidden or unreachable?

Hi, I installed Monasca with Docker. I use Keystone from my Openstack installation. I added these lines to docker-compose.yml in agent-forwarder, agent-collector etc...

  OS_AUTH_URL: http://controller:5000/identity/v3
  OS_USERNAME: monasca-agent
  OS_PASSWORD: mypassword
  OS_PROJECT_NAME: monasca
  OS_PROJECT_DOMAIN_NAME: Default
  OS_USER_DOMAIN_NAME: Default

The user is existent in Keystone and I can log into Openstack with this user. Now I get hundreds of this errors:

monasca_1               | 2018-07-09 17:20:16 [66] gunicorn.access [INFO] 172.18.0.8 - - [09/Jul/2018:17:20:16 +0000] POST /v2.0/metrics HTTP/1.1 401 97 "-" "monasca-agent keystoneauth1/3.3.0 python-requests/2.18.4 CPython/2.7.13" 0.004476
monasca_1               | 2018-07-09 17:20:17 [66] gunicorn.access [INFO] 172.18.0.8 - - [09/Jul/2018:17:20:17 +0000] POST /v2.0/metrics HTTP/1.1 401 97 "-" "monasca-agent keystoneauth1/3.3.0 python-requests/2.18.4 CPython/2.7.13" 0.139112
agent-forwarder_1       | 2018-07-09 17:20:17,190 | ERROR | forwarder | monasca_agent.forwarder.api.monasca_api(monasca_api.py:149) | Error sending message to Monasca API.
agent-forwarder_1       | Traceback (most recent call last):
agent-forwarder_1       |   File "/usr/local/lib/python2.7/site-packages/monasca_agent/forwarder/api/monasca_api.py", line 141, in _send_message
agent-forwarder_1       |     self._mon_client.metrics.create(**kwargs)
agent-forwarder_1       |   File "/usr/local/lib/python2.7/site-packages/monascaclient/v2_0/metrics.py", line 31, in create
agent-forwarder_1       |     body = self.client.create(url=url_str, json=data)
agent-forwarder_1       |   File "/usr/local/lib/python2.7/site-packages/osc_lib/api/api.py", line 164, in create
agent-forwarder_1       |     ret = self._request(method, url, session=session, **params)
agent-forwarder_1       |   File "/usr/local/lib/python2.7/site-packages/osc_lib/api/api.py", line 141, in _request
agent-forwarder_1       |     return session.request(url, method, **kwargs)
agent-forwarder_1       |   File "/usr/local/lib/python2.7/site-packages/keystoneauth1/session.py", line 737, in request
agent-forwarder_1       |     raise exceptions.from_response(resp, method, url)
agent-forwarder_1       | Unauthorized: Forbidden (HTTP 401) (Request-ID: req-de995882-dd2d-4892-b58e-a3d47c46e101)
agent-forwarder_1       | 2018-07-09 17:20:17,190 | WARNING | forwarder | monasca_agent.forwarder.api.monasca_api(monasca_api.py:168) | The Monasca API is DOWN or unreachable. Queuing the messages to send later...

So... the second last line says I get a 401 Error, the last line says the API is unreachable. What is true now? If it is unreachable, it cannot give a 401 Error (Forbidden). How to start debugging here? What can be the problem?

2018-06-13 13:10:02 -0600 received badge  Notable Question (source)
2018-05-30 08:46:07 -0600 commented question Network problems after compute node reboot

Yes, I tried detaching and reattaching the interface. When I created a new instance, everything worked, so linuxbridge on the compute node must be ok. If that happens again I will check with tcpdump. Anyone any other idea?

2018-05-30 07:36:47 -0600 received badge  Notable Question (source)
2018-05-30 01:51:14 -0600 received badge  Popular Question (source)
2018-05-30 00:25:53 -0600 asked a question Network problems after compute node reboot

We rebooted a compute node while running an instance on it. After the reboot the network of this instance did not work. I could not ping the internal address nor the floating IP. Rebooting, Hard resetting... nothing helped. I had to recreate the instance based on the volume. Then it worked again.

What could been the problem?

It is Queens running on Ubuntu 16.04 with networking done by Neutron.

2018-05-15 04:50:38 -0600 answered a question Unable to establish connection to http://cic-mgmt:35357/v2.0/users

Are you using Openstack Queens? The Keystone port has changed from 35357 to 5000 in Queens.

You should look into your Ceilometer configuration if you find any 35357 there and change it to 5000.

2018-05-09 21:22:48 -0600 received badge  Popular Question (source)
2018-05-07 11:00:17 -0600 commented question Trove: Unable to locate package ubuntu-cloud-keyring

Inside the instance calling add-apt-repository cloud-archive:queens shows an error Error: retrieving gpg key timed out., but the repository seems to be added anyway, including the package ubuntu-cloud-keyring

2018-05-07 11:00:17 -0600 received badge  Commentator
2018-05-07 02:41:58 -0600 commented question I get Unauthorized message when i create a default domain in keystone

Is Keystone listening on Port 35357? Check that with netstat -pan|grep 35357.

2018-05-06 15:08:28 -0600 commented question Trove: Unable to locate package ubuntu-cloud-keyring

Could be, but I cannot find another docu. I need to use 16.04 and not 14.04.

2018-05-03 03:09:05 -0600 asked a question Trove: Unable to locate package ubuntu-cloud-keyring

I set up Trove an now try to create a guest image via cloud-init according to this documentation. When I start a new database instance I get the following errors in the startup log of the instance:

[  437.346139] cloud-init[1095]: 2018-04-30 21:41:03,609 - cc_apt_configure.py[ERROR]: add-apt-repository failed.
[  437.371922] cloud-init[1095]: Traceback (most recent call last):
[  437.402786] cloud-init[1095]:   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_apt_configure.py", line 615, in add_apt_sources
[  437.427157] cloud-init[1095]:     util.subp(["add-apt-repository", source], target=target)
[  437.446281] cloud-init[1095]:   File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1957, in subp
[  437.486109] cloud-init[1095]:     cmd=args)
[  437.517475] cloud-init[1095]: cloudinit.util.ProcessExecutionError: Unexpected error while running command.
[  437.546221] cloud-init[1095]: Command: ['add-apt-repository', 'cloud-archive:queens']
[  437.578697] cloud-init[1095]: Exit code: 1
[  437.602570] cloud-init[1095]: Reason: -
[  437.638407] cloud-init[1095]: Stdout:  Ubuntu Cloud Archive for OpenStack Queens
[  437.674750] cloud-init[1095]:          More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive
[  437.693931] cloud-init[1095]:         Reading package lists...
[  437.721120] cloud-init[1095]:         Building dependency tree...
[  437.742770] cloud-init[1095]:         Reading state information...
[  437.754358] cloud-init[1095]:         Failed to add key.
[  437.790756] cloud-init[1095]: Stderr: E: Unable to locate package ubuntu-cloud-keyring

and later:

[  771.137018] cloud-init[1372]: E: There were unauthenticated packages and -y was used without --allow-unauthenticated
[  771.166616] cloud-init[1372]: Cloud-init v. 18.2 running 'modules:final' at Mon, 30 Apr 2018 21:41:20 +0000. Up 454.31 seconds.
[  771.185561] cloud-init[1372]: 2018-04-30 21:47:06,204 - util.py[WARNING]: Failed to install packages: ['trove-guestagent', 'mysql-server-5.7']
[  771.225740] cloud-init[1372]: 2018-04-30 21:47:06,457 - cc_package_update_upgrade_install.py[WARNING]: 1 failed with exceptions, re-raising the last one
[  771.264518] cloud-init[1372]: 2018-04-30 21:47:06,537 - util.py[WARNING]: Running module package-update-upgrade-install (<module 'cloudinit.config.cc_package_update_upgrade_install' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_package_update_upgrade_install.py'>) failed

It seems that cloud-init cannot find the package ubuntu-cloud-keyring and therefore it is unable to install some packages. Is this a bug or am I doing something wrong? The only difference in my /etc/trove/cloudinit/mysql.cloudinit to the docu ist that I replaced pike with queens.

2018-05-03 02:48:55 -0600 commented answer ERROR trove Failed to create volume for instance The resource could not be found HTTP 404

Yes, I have reported this bug. And several others. But none of the bugs has been fixed yet :-( I have marked my bug report as duplicate of yours now.

2018-05-03 02:46:08 -0600 received badge  Enthusiast
2018-04-30 12:06:33 -0600 answered a question ERROR trove Failed to create volume for instance The resource could not be found HTTP 404

Finally after dozens of test runs I figured out that the error disappears if you change

cinder_url = http://controller:8776/v1 to cinder_url = http://controller:8776/v3 in trove-taskmanager.conf.

Unfortunately the trove documentation ist one of the worst in the Openstack universe and it seems to be hopeless outdated!

2018-04-30 09:19:32 -0600 commented answer ERROR trove Failed to create volume for instance The resource could not be found HTTP 404

Mee too. Has anyone got around that issue?

2018-04-30 03:20:16 -0600 received badge  Editor (source)
2018-04-30 03:15:50 -0600 asked a question Trove: 'Client' object has no attribute 'security_groups'

I installed Openstack Queens according to the documentation. I also installed Trove with this guide.

When I try to create an new instance I get the following error:

Error creating security group for instance: eb18e0a4-bb22-42cd-bd81-302c908e3105 'Client' object has no attribute 'security_groups'

What Client object is missing an attribute here? What can I have done wrong?

Here are the lines of the logfile:

2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server [-] Exception during message handling: TroveError: Error creating security group for instance: eb18e0a4-bb22-42cd-bd81-302c908e3105
'Client' object has no attribute 'security_groups'
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 220, in dispatch
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 190, in _do_dispatch
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     result = func(ctxt, **new_args)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 158, in wrapper
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     result = f(*args, **kwargs)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/trove/taskmanager/manager.py", line 395, in create_instance
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     locality)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/trove/taskmanager/manager.py", line 375, in _create_instance
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     scheduler_hints)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/trove/taskmanager/models.py", line 479, in create_instance
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     self._log_and_raise(e, log_fmt, exc_fmt, self.id, err)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/trove/taskmanager/models.py", line 862, in _log_and_raise
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server     raise TroveError(message=full_message)
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server TroveError: Error creating security group for instance: eb18e0a4-bb22-42cd-bd81-302c908e3105
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server 'Client' object has no attribute 'security_groups'
2018-04-30 09:57:02.935 2733 ERROR oslo_messaging.rpc.server
2018-01-22 02:30:24 -0600 received badge  Famous Question (source)
2018-01-22 02:30:24 -0600 received badge  Notable Question (source)
2018-01-22 02:30:24 -0600 received badge  Popular Question (source)
2017-08-03 08:38:05 -0600 received badge  Notable Question (source)
2017-08-03 08:38:05 -0600 received badge  Famous Question (source)
2017-03-03 09:02:30 -0600 commented answer Router management not available in dashboard

yes, there is a namespace. And with cmdline tools I also see the router!

controller:~$ ip netns
qrouter-234fb5fd-518a-4271-99bb-ddfdd776fb35 (id: 2)
qdhcp-d53cae93-9b52-4363-bb18-395b6b9a8ac3 (id: 1)
qdhcp-b856defb-9cbb-4852-b654-80897c76f125 (id: 0)

controller:~$ neutron router-list
+--------------------------------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| id                                   | name   | external_gateway_info                                                                                                                                             |
+--------------------------------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 234fb5fd-518a-4271-99bb-ddfdd776fb35 | router | {"network_id": "b856defb-9cbb-4852-b654-80897c76f125", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "bedb6b3f-a88a-4434-ba2e-564fa6fd4ab0",          |
|                                      |        | "ip_address": "172.16.255.2"}]}                                                                                                                                   |
+--------------------------------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2017-03-02 10:10:58 -0600 asked a question Router management not available in dashboard

Hello,

I set up a test installation of Openstack following the Online-Guide.

I created a router as described in the Guide. But in the dashboard it is not visible. Even the whole "Router" section is missing in the menu on the left. So there is also no "create router" available.

As I set up this installation for students learning the basics of Openstack without having shell access (that will come later), I need all this functionality in the dashboard.

I did not find any hints in the log files. Any ideas what could be wrong?

Thanks, Peter

openstack-no-router.png

2016-05-30 16:35:12 -0600 received badge  Notable Question (source)
2016-05-30 16:35:12 -0600 received badge  Famous Question (source)
2016-03-01 06:36:13 -0600 received badge  Good Answer (source)
2016-03-01 01:11:13 -0600 received badge  Nice Answer (source)
2016-03-01 01:10:50 -0600 received badge  Popular Question (source)
2016-02-29 16:58:21 -0600 received badge  Self-Learner (source)
2016-02-29 16:58:21 -0600 received badge  Teacher (source)
2016-02-29 16:21:21 -0600 received badge  Scholar (source)
2016-02-29 16:19:06 -0600 answered a question devstack: Keystone not listening on 5000 after rejoin-stack.sh

Looks like I found the problem:

./unstack.sh seems to remove the symlink /etc/apache2/sites-enabled/keystone.conf and ./rejoin_stack.sh does not recreate it. The solution is:

cd /etc/apache2/sites-enabled 
ln -s ../sites-available/keystone.conf

before calling ./rejoin-stack.sh

2016-02-29 16:13:34 -0600 commented answer How to properly reboot a machine running devstack.sh?

It is important to point out that the first is not to be typed in after ./unstack.sh Even it eventually does not do any harm...

2016-02-29 15:53:36 -0600 commented question Devstack displays only text on port 5000

Horizon should run on port 80, not port 5000.

2016-02-29 13:51:50 -0600 edited question devstack: Keystone not listening on 5000 after rejoin-stack.sh

I installed devstack in a Virtualbox machine with no problems. I could log into the dashboard and start a cirros instance.

Then I shut everything down with ./unstack.sh and rebooted the machine. After reboot I executed ./rejoin-stack.sh. When I try to log in on the dashboard it shows: Unable to establish connection to keystone endpoint.

The log shows: Unable to establish connection to http://10.0.0.149:5000/v3/auth/tokens and a netstat -pan also shows nothing listening on port 5000.

I can start keystone manually with:

/usr/bin/python /usr/local/bin/keystone-all
--config-file /etc/keystone/keystone.conf

But that is just a workaround... Keystone should of course start automatically. What is going wrong here and where could I start looking for the problem?