Ask Your Question

VonGoofy's profile - activity

2019-09-16 23:29:57 -0500 received badge  Notable Question (source)
2019-04-08 04:14:09 -0500 received badge  Popular Question (source)
2019-02-08 02:39:30 -0500 asked a question Openstack external network subnet issue

We have multinode openstack deployed in production. We have tenant networks (openvswitch) and an external network with multiple PUBLIC subnets in it. One of the subnets has issues. We launch a VM, associate a public IP from that subnet. VM can reach internet, internet can reach VM. The problem is that VM can't reach any of the IP's in the public subnets in our external network, and vice versa. It can reach everything outside our subnets, and everything from outside can reach the VM. Anyone have any idea what is the issue with this subnet? We use distributed routers for each project that uses external network and it's public IP's. Openstack version is Liberty.

2016-05-11 05:11:56 -0500 received badge  Famous Question (source)
2016-03-18 06:46:20 -0500 received badge  Student (source)
2016-03-01 03:47:57 -0500 commented question Can't ping floating IP's and instances can't ping each other

Thanks guys, but I resolved the problem. The issue was that I had multiple networks, and since openstack as a cloud software has troubles with anything other than 1 network, I have deleted the extra network(s). I'm now moving to the flat network design.

2016-03-01 03:46:41 -0500 received badge  Notable Question (source)
2016-02-27 23:40:52 -0500 received badge  Popular Question (source)
2016-02-26 10:02:35 -0500 asked a question Can't ping floating IP's and instances can't ping each other

Hello,

The problem is usual problem we encounter in openstack, and I had it before, but I can't resolve the current one.

My setup is multinode Openstack Liberty installation on Ubuntu 14.04 servers. I have created private block of network, subnet router and L3 agent. Then I have added a public IP subnet (floating IPs) and connect it to the private block so my instances can be reached from outside world. This setup worked just fine with the default openstack settings per their documentation for openstack liberty.

Recently I have updated servers and everything works except I cannot access VM's from outside or inside the cloud. I can't even ping other instances in the private block. None of the settings had changed since everything worked. I just updated the servers and rebooted them (kernel update).

Any suggestion on what might happened?

Thanks!

2016-01-19 20:48:37 -0500 received badge  Notable Question (source)
2016-01-19 20:48:37 -0500 received badge  Famous Question (source)
2016-01-19 20:48:37 -0500 received badge  Popular Question (source)
2016-01-01 11:22:25 -0500 received badge  Teacher (source)
2015-12-31 06:09:56 -0500 answered a question Where is a successfull OpenStack Liberty implementation?

I have a production installation of Openstack Liberty running in a multi-node environment. Even the basic setup in official documentation should work out of the box if you follow it.

2015-12-31 06:08:15 -0500 commented question kilo neutron : neutron agent-list showing nothing

If clock are not in sync then the rabbitmq messages are not received since the nodes are out of sync. That is if your neutron configs are correct. You can fix it by setting up the correct times in BIOS on each node.

2015-12-04 04:25:11 -0500 commented question vif_type=binding_failed and can't launch instances. Error message : Could not clean up failed build, not rescheduling

[ovs] section is not in the right place. It moved to openswitch_agent.ini along with some other configuration options.

2015-12-03 01:20:31 -0500 answered a question vif_type=binding_failed and can't launch instances. Error message : Could not clean up failed build, not rescheduling

Check your neutron configuration files especially ml2_conf.ini and your chosen neutron plugin configuration.

I had the same problem when upgrading to liberty and didn't notice that all openvswitch configuration in ml2 switched to a dedicated configuration in ml2 folder.

So this is most likely a configuration problem in neutron.

2015-11-26 04:07:38 -0500 received badge  Famous Question (source)
2015-11-25 07:44:52 -0500 asked a question Liberty Failed to bind port on host compute

Hi,

Another problem emerged with my openstack installation. I'm trying to launch an instance in dashboard and I'm getting this error:

No valid host was found. There are not enough hosts available

Which is the result of nova(nova-conductor) error:

RescheduledException: Build of instance 9e1028f2-6431-4749-8cec-382ffc18d33c was re-scheduled: Unexpected vif_type=binding_failed

And finally the error that produces the above:

ERROR neutron.plugins.ml2.managers [req-8fdbdd94-8383-4d32-aa30-7971edb80310 f87f19de72374188ba32b4f404d1e624 b014c389ece04289aed99576e92b7c11 - - -] Failed to bind port 9de21762-5aac-45d7-bd9f-9d665c7dfd22 on host compute

How to resolve this neutron error and ultimately the instance launch error?

Thanks!

2015-11-22 09:59:52 -0500 received badge  Enthusiast
2015-11-19 13:16:03 -0500 answered a question The keystone CLI is deprecated in favor of python-openstackclien

Yes keystone is going away in Mitaka version, replaced by openstack app/package. This is just a deprecation warning.

2015-11-19 07:44:36 -0500 answered a question Liberty on Ubuntu 14.04 Nova service-list Error 401

I have deleted nova user and create new one using the offical documentation and I still get error 401.

http://docs.openstack.org/liberty/install-guide-ubuntu/nova-controller-install.html

Edit:

Problem resolved, there was a wrong entry in api-paste.ini in /etc/nova.

Everything works without a problem now.

2015-11-19 05:16:18 -0500 received badge  Notable Question (source)
2015-11-18 23:59:15 -0500 received badge  Popular Question (source)
2015-11-18 12:34:38 -0500 commented answer Liberty on Ubuntu 14.04 Nova service-list Error 401

Here is the paste of the debug output: http://paste.openstack.org/show/479317/

2015-11-18 06:54:24 -0500 commented answer Liberty on Ubuntu 14.04 Nova service-list Error 401

This problem is killing me, and I need it resolved very soon. I have made edits above. I can get a token using curl, but seems like keystone is not issuing token to nova so nova can't access the api.

2015-11-18 06:32:13 -0500 commented question No handlers could be found for logger "oslo_config.cfg"

Same problem here on Ubuntu 14.04 Liberty.

2015-11-18 05:31:18 -0500 received badge  Editor (source)
2015-11-18 05:26:24 -0500 answered a question Liberty on Ubuntu 14.04 Nova service-list Error 401

I have a creds file that I source, but it's the same thing.

export OS_PROJECT_DOMAIN_ID=default
export OS_USER_DOMAIN_ID=default
export OS_REGION_NAME=RegionOne
export OS_PROJECT_NAME=admin
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=adminpassword
export OS_AUTH_URL='http://10.0.0.1:5000/v3'
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_TYPE=password

I have added oslo rabbit settings to nova.conf and still the same error. I guess the problem could be here somewhere?

2015-11-17 09:56:12 -0500 answered a question Nova spice-html5 tls error

Maybe you will get a hint from this line in your config under spice:

insecure = True

2015-11-17 09:56:11 -0500 asked a question Liberty on Ubuntu 14.04 Nova service-list Error 401

I have upgraded multinode openstack liberty installation recently and I got all services running except the nova service. I have upgraded from icehouse to liberty and due to all the configuration changes I don't know if my nova.conf is correct anymore. I have update it to the latest config but it seems that it's not communicating with keystone. This is nova on Controller node to be clear.

When I do:

nova service-list
ERROR (Unauthorized): Unauthorized (HTTP 401) (Request-ID: req-b1816082-ba85-42f5-9d37-f8bdffeaa729)

nova.conf:

[DEFAULT]
log_dir = /var/log/nova
state_path = /var/lib/nova
verbose = True
api_paste_config = /etc/nova/api-paste.ini
compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
notify_nova_on_port_status_changes = True
notify_nova_on_port_data_changes = True
nova_url = http://10.0.0.1:8774/v2/
root_helper = sudo nova-rootwrap /etc/nova/rootwrap.conf
auto_assign_floating_ip = True
vif_plugging_is_fatal = False
vif_plugging_timeout = 0
multihost = True
compute_driver = libvirt.LibvirtDriver
allow_same_net_traffic = False
auth_strategy = keystone
my_ip = 10.0.0.1
enabled_apis = osapi_compute,metadata

# Vnc configuration
vnc_enabled = true
novnc_enabled = true
ssl_only = true
cert = /home/ubuntu/cert-ssl/cert.cer
key = /home/ubuntu/cert-ssl/private.key
novncproxy_port = 6080

linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver = nova.virt.firewall.NoopFirewallDriver
security_group_api = neutron
network_api_class = nova.network.neutronv2.api.API
compute_driver = libvirt.LibvirtDriver

# Cinder #
volume_api_class = nova.volume.cinder.API
osapi_volume_listen_port = 5900

# Network settings
[neutron]
url = http://10.0.0.1:9696
auth_uri = http://10.0.0.1:5000/v2.0/
identity_uri = http://10.0.0.1:35357
admin_tenant_name = service
admin_username = neutron
admin_password = adminPassword
metadata_proxy_shared_secret  =  sharedsecret
libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
service_metadata_proxy = True

[libvirt]
virt_type = kvm

[keystone_authtoken]
auth_uri = http://10.0.0.1:5000/v2.0/
identity_uri = http://10.0.0.1:35357
admin_tenant_name = service
admin_username = nova
admin_password = adminPassword

[glance]
api_servers = 10.0.0.1:9292
image_service = nova.image.glance.GlanceImageService

[cinder]
os_region_name = RegionOne

[database]
connection = mysql://nova:nova@10.0.0.1/nova

[vnc]
enabled = True
keymap = en-us
novncproxy_base_url = https://10.0.0.1:6080/vnc_auto.html
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = 10.0.0.1

[oslo_concurrency]
lock_path = /var/lib/nova/tmp

Edit (added rabbit settings to the nova.conf):

[oslo_messaging_rabbit]
rabbit_host = 10.0.0.1
rabbit_userid = openstack
rabbit_password = openstack
rabbit_virtual_host = /

Edit2:

I have a creds file that I source, but it's the same thing.

export OS_PROJECT_DOMAIN_ID=default
export OS_USER_DOMAIN_ID=default
export OS_REGION_NAME=RegionOne
export OS_PROJECT_NAME=admin
export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=adminpassword
export OS_AUTH_URL='http://10.0.0.1:5000/v3'
export OS_IDENTITY_API_VERSION=3
export OS_AUTH_TYPE=password

I have added oslo rabbit settings to nova.conf and still the same error. I guess the problem could be here somewhere? What am I missing here? Everything is exported correctly, all other services are running ok, neutron, keystone (issuing tokens without a problem), glance and cinder.

2015-11-17 08:09:50 -0500 received badge  Supporter (source)