Ask Your Question

arbermejo's profile - activity

2019-05-10 15:55:56 -0500 asked a question openstack dashboard frozen at login screen

Hi I'm having problems with Horizon (OpenStack Queens running in Ubuntu 18.04.1 LTS), I've installed it following the recomendations at the oficial guides and i can't login into the dasboard, i'm stuck at the login screen. I checked the content of /var/log/apache2/error.log and this is the output:

[Fri May 10 20:47:33.347995 2019] [wsgi:error] [pid 24256:tid 140032273983232] [remote 10.8.2.116:36002] INFO openstack_auth.plugin.base Attempted scope to domain Default failed, will attemptto scope to another domain.
[Fri May 10 20:47:36.008849 2019] [wsgi:error] [pid 24256:tid 140032273983232] [remote 10.8.2.116:36002] INFO openstack_auth.forms Login successful for user "admin" using domain "Default", remote address 10.8.2.116.
[Fri May 10 20:47:54.033509 2019] [wsgi:error] [pid 24255:tid 140032232019712] [remote 10.8.2.116:36008] INFO openstack_auth.plugin.base Attempted scope to domain Default failed, will attemptto scope to another domain.
[Fri May 10 20:47:54.383471 2019] [wsgi:error] [pid 24255:tid 140032232019712] [remote 10.8.2.116:36008] INFO openstack_auth.forms Login successful for user "admin" using domain "Default", remote address 10.8.2.116.

According to this i should be already logged into the admin dashboard but i'm still in the login screen

Does anyone ever experienced this error, or knows what solution can be done???

2019-05-09 11:27:33 -0500 received badge  Famous Question (source)
2019-04-30 07:53:39 -0500 answered a question docker network create with kuryr

Thanks to hongobin034 for giving me the solution. I'll add it here in case someone have the same porblem. I had indeed a problem with the kuryr authentication in keystone. I changed the param auth_url in /etc/kuryr/kuryr.conf

[neutron]

auth_url = http://controller:5000

After i changed the port kuryr was able to start correctly

root@compute /h/team# systemctl status kuryr-libnetwork
● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for Neutron
   Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-04-29 22:14:05 UTC; 5s ago
 Main PID: 9341 (kuryr-server)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/kuryr-libnetwork.service
           └─9341 /usr/bin/python /usr/local/bin/kuryr-server --config-file /etc/kuryr/kuryr.conf

Apr 29 22:14:05 compute systemd[1]: Started Kuryr-libnetwork - Docker network plugin for Neutron.
Apr 29 22:14:08 compute kuryr-server[9341]: 2019-04-29 22:14:08.690 9341 INFO werkzeug [-]  * Running on http://127.0.0.1:23750/ (Press CTRL+C to quit)

As a result of this i could create the new docker network

root@compute /h/team# docker network create --driver kuryr --ipam-driver kuryr \
                            --subnet 10.10.0.0/16 --gateway=10.10.0.1 test_net
14c05b18623eb3cac3d6fe20ae90b4603e3eb89cc2230eaf487be116e9b66288
2019-04-29 12:44:10 -0500 received badge  Notable Question (source)
2019-04-29 11:21:15 -0500 commented answer docker network create with kuryr

ok i runned the command and this is the output: Failed to discover available identity versions when contacting http://controller:35357. Attempting to parse version from URL. Could not determine a suitable URL for the plugin

I checked at the controller node and that port isn't open either

2019-04-28 12:23:31 -0500 received badge  Popular Question (source)
2019-04-27 09:54:58 -0500 received badge  Associate Editor (source)
2019-04-27 09:48:40 -0500 asked a question docker network create with kuryr

Hi i've installed Openstack Queens on Ubuntu 18.04 and i'm following the Zun Installation Guide to deploy a container infrastructure. I'm following the steps to install kuryr-libnetwork (I've already installed docker on the compute node and it's working fine). The kuryr installation process had no errors but when i try to verify the operation as it's said in the guide

docker network create --driver kuryr --ipam-driver kuryr \ --subnet 10.10.0.0/16 --gateway=10.10.0.1 test_net

I'm Getting this error Errorresponse from daemon: legacy plugin: Post http://10.8.9.54:23750/Plugin.Activate: dial tcp 10.8.9.54:23750: connect: connection refused

I tryed to find the error wit journalctl -u kuryr-libnetwork

Apr 27 13:11:12 compute systemd[1]: Started Kuryr-libnetwork - Docker network plugin for Neutron.

Apr 27 13:11:13 compute kuryr-server[10736]: 2019-04-27 13:11:13.273 10736 WARNINGkeystoneauth.identity.generic.base [-] Failed to discover available identity versions when contacting http://controller:35357. Attempting to parse version from URL.: ConnectFailure: Unable to establish connection to http://controller:35357: HTTPConnectionPool(host='controller', port=35357): MTTPConnectionPool(host='controller', port=35357): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.httpconnection 0x7fecef1a8090="" at="" object="">: Failed to establish a new connection: [Errno 111] Connection refused',))</urllib3.connection.httpconnection>

Apr 27 13:11:13 compute kuryr-server[10736]: 2019-04-27 13:11:13.274 10736 CRITICAL kuryr [-] Unhandled error: DiscoveryFailure: Could not determine a suitable URL for the plugin

Apr 27 13:11:13 compute kuryr-server[10736]: 2019-04-27 13:11:13.274 10736 ERROR kuryr Traceback (most recent call last):

This is the relevant content of my /etc/kuryr/kuryr.conf

[DEFAULT]

bindir = /usr/local/libexec/kuryr

[neutron]

www_authenticate_uri = http://controller:5000

auth_url = http://controller:35357

username = kuryr

user_domain_name = default

password = 123

project_name = service

project_domain_name = default

auth_type = password

And this is the one at /usr/lib/docker/plugins/kuryr/kuryr.spec:

http://conrtoller:23750

Btw compute node have connectivity with controller. I already have worked with the environment and launched kvm VMs on it

Can someone help troubleshoot this error??

UPDATE2

I tried the recommendations given by hongbin034 and confirm that i had a problem with Keystone. when i run openstack token issue after exporting the neutron environment varibles i get the following output

Failed to discover available identity versions when contacting http://controller:35357. Attempting to parse version from URL. Could not determine a suitable URL for the plugin

I checked and the port 35357 isn't even open at the controller node. But at the controller node installation there isn't any step configuring such port

UPDATE1

I checked open ports on controller node and 23750 isn't open. I followed the directions at the guide, any recommendation?

Also in the compute node when i run systemctl status kuryr-libnetwork this is the output

● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for Neutron Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code ... (more)

2019-04-26 11:22:24 -0500 answered a question kvm instance launch error

I was lacking the neutron configuration on the compute node. I followed the instrucion for this in the guide and everything went fine

2019-04-26 10:58:41 -0500 asked a question kvm instance launch error

I'm launching the first kvm instance in an Openstack Queens deployment (manually) and i'm having the next error message

{u'message': u'Build of instance 9fe336c2-ada7-43cb-87e9-7e65bb25fb6c aborted: Unknown auth type: None', u'code': 500, u'details': u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1841, in _do_build_and_run_instance\n filter_properties, request_spec)\n File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2063, in _build_and_run_instance\n bdms=block_device_mapping)\n File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__\n self.force_reraise()\n File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise\n six.reraise(self.type_, self.value, self.tb)\n File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2035, in _build_and_run_instance\n instance=instance)\n File "/usr/lib/python2.7/contextlib.py", line 35, in __exit__\n self.gen.throw(type, value, traceback)\n File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2279, in _build_resources\n reason=six.text_type(exc))\n', u'created': u'2019-04-26T15:47:00Z'} |

I guess it is a keystone configuration error but don't know where to fix it. Can someone help please

2019-04-15 12:27:57 -0500 received badge  Popular Question (source)
2019-04-03 11:06:27 -0500 asked a question openstack-ansible setup-openstack error

I'm setting up Openstack Queens using the openstack-ansible deployment guide at the official docs site. I have 3 phisical hosts as the guide required, and already finished with the setup-host.yml and setup-infraestructure.yml playbooks without any failure (i'm fallowing the test environment user guide, 1 network interface for each node)

When i run the setup-openstack.yml playbook. Specifically at the TASK [os_nova : Get package from git] i'm getting the following error

fatal: [infra1_nova_api_container-e7b4cc16]: FAILED! => {"attempts": 5, "changed": false, "cmd": "/usr/bin/git clone --origin origin git://172.29.236.11/spice-html5 /usr/share/spice-html5", "failed": true, "msg": "Cloning into '/usr/share/spice-html5'...\nfatal: remote error: access denied or repository not exported: /spice-html5", "rc": 128, "stderr": "Cloning into '/usr/share/spice-html5'...\nfatal: remote error: access denied or repository not exported: /spice-html5\n", "stderr_lines": ["Cloning into '/usr/share/spice-html5'...", "fatal: remote error: access denied or repository not exported: /spice-html5"], "stdout": "", "stdout_lines": []}

This IP address (172.29.236.11) is the one from my infrastructure physical node. I checked and this file ( /usr/share/spice-html5) doesn't exist

The nova_api_container have network connection with the infra host and can login via ssh

Any help to fix this problem is very appreciated

2019-04-03 09:26:51 -0500 received badge  Famous Question (source)
2019-03-28 21:48:54 -0500 received badge  Notable Question (source)
2019-03-11 17:16:46 -0500 received badge  Famous Question (source)
2019-03-11 10:53:45 -0500 commented answer multi-hypervisor deployment

then attaching block volumes means adding additional volumes??. This is what the matrix says: The attach volume operation provides a means to hotplug additional block storage to a running instance

2019-03-11 10:53:45 -0500 received badge  Commentator
2019-03-11 09:41:16 -0500 commented answer multi-hypervisor deployment

according to the support matrix Openstack don't have support erither to attach virtual network interfaces, then what is the use of an LXC instance in it???

2019-03-11 09:38:01 -0500 received badge  Scholar (source)
2019-03-11 09:37:54 -0500 received badge  Supporter (source)
2019-03-11 09:37:35 -0500 commented answer multi-hypervisor deployment

so that mans that lxc can't attach volumes to instance on Openstack, so how do they work? Can i launch an instance without a block volume?? PD: i tried with a flavor with ephemeral volume and 0 Disk and didn't work either

2019-03-11 08:42:19 -0500 answered a question How to launch an instance on specific host

You can use Host Aggregates for that, i had a similar problem here is a link with the solution that worked for me https://ask.openstack.org/en/question/120253/selecting-compute-node-to-deploy-an-instance/ (https://ask.openstack.org/en/question...)

2019-03-11 08:30:38 -0500 asked a question cinder instance launch trouble

Hi i recently added a lxc compute node to my Openstack Queens enviroment running in Ubuntu 18.04. When i try to deploy an instance in this compute node i'm getting this messages

2019-03-08 16:13:58.022 2438 WARNING nova.virt.libvirt.driver [req-78f6ee93-7554-48c0-9ed9-8457b674347c a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: e6bd1d65-f77c-482e-bda5-31df539b3e06] Ignoring supplied device name: /dev/vda. Libvirt can't honour user-supplied dev names

2019-03-08 16:13:58.375 2438 INFO nova.virt.block_device [req-78f6ee93-7554-48c0-9ed9-8457b674347c a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: e6bd1d65-f77c-482e-bda5-31df539b3e06] Booting with blank volume at /dev/vda

I think i have a problem with the name of the block device Libvirt is using for the instance, and because of that it is failing to spawn.

Any idea how can i fix this trouble??

2019-03-09 12:58:15 -0500 commented question multi-hypervisor deployment

but how do i analyse isciadm volumes. I haven't done any configuration about iscsi in my lxc compute node (but either in the kvm one). The nova.conf file from my kvm node and the lxc one are almost the same (with the exceptions of the modification done to use lxc). I can launch instances in the kvm

2019-03-06 19:36:36 -0500 received badge  Notable Question (source)
2019-03-06 12:08:16 -0500 edited question multi-hypervisor deployment

i have a minimal deployment with 4 nodes (controller, compute(kvm), object storage, block storage) wich i made manually fallowing the official openstack docs , and im adding a new compute node (lxc), i fallowed the instructions of the Compute Service installation section in the docs and added my new compute node, but when i run nova-status upgrade check i'm having this output

Check: Resource Providers
| Result: Warning
| Details: There are 1 compute resource providers and 2 compute nodes | in the deployment. Ideally the number of compute resource
| providers should equal the number of enabled compute nodes
| otherwise the cloud may be underutilized

Also i am trying to deploy a new instance on the lxc hypervisor.

For doing this I added an image from the official ubuntu image repository and used this command to load it to my environment

openstack image create --public --disk-format raw --container-format bare --file bionic-server-cloudimg-amd64.img bionic

Also i already made the flavor corresponding to the host aggregate i made for lxc

openstack flavor set 89cedbec-0eaf-4d75-953d-571932428611 --property aggregate_instance_extra_specs:compute-type=lxc

i'm think that the scheduler is working fine and is trying to deploy my instance in the lxc compute node, but don't know what i'm missing

I really preciate any help or use case of a multi-hypervisor deployment

Second UPDATE

Ok this is crazy, you where right i have a trouble with the quotas and i fixed it, but now it is giving me another error in /var/log/nova/nova-compute.log

Hi, just now i tried creating an instance with an ephemeral volume and didn't work either, i already checked the configs files on my lxc compute node and my cinder node and i can't see any problem there.

I previously apologize for the length of the question, but I really don't know where is the problem in my configuration. The only odd line on the logs for me is this one

2019-03-08 16:14:58.569 2438 ERROR nova.compute.manager [req-78f6ee93-7554-48c0-9ed9-8457b674347c a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: e6bd1d65-f77c-482e-bda5-31df539b3e06] Instance failed to spawn: TypeError: mount() takes exactly 4 arguments (3 given)

Just now i tried to create a new instance on the lxc compute node and checked the logs from /var/log/nova/nova-compute.log and the /var/log/cinder/cinder-volume.log (in the cinder node) and it seems there are any problem there. This is the output for the instance (e6bd1d65-f77c-482e-bda5-31df539b3e06) from the compute node. Basically as the conclusion of the analysis of both logs, show me that cinder didn't detect any error.

root@nova-lxc /h/team# tail -n 100 /var/log/nova/nova-compute.log | grep e6bd1d65-f77c-482e-bda5-31df539b3e06
2019-03-08 16:13:57.273 2438 INFO nova.compute.claims [req-78f6ee93-7554-48c0-9ed9-8457b674347c a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: e6bd1d65-f77c-482e-bda5-31df539b3e06] Attempting claim on node nova-lxc: memory 2048 MB, disk 5 GB, vcpus 1 CPU
2019-03-08 16:13:57.274 2438 INFO nova.compute.claims [req-78f6ee93-7554-48c0-9ed9-8457b674347c a16c6ef0319b4643a4ec8e56a1d025cb 59065d8f970b467aa94ef7b35f1edab5 - default default] [instance: e6bd1d65-f77c-482e-bda5-31df539b3e06] Total memory: 16039 MB, used: 512.00 MB
2019-03-08 16:13:57 ...
(more)