Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

region not found #1

Open
onsDridi opened this issue Jun 30, 2017 · 4 comments
Open

region not found #1

onsDridi opened this issue Jun 30, 2017 · 4 comments

Comments

@onsDridi
Copy link

Hello,
I'm new with SFC, I tried to test your demo but when i launch this command
./openstack-scripts/simple_sfc_vms.sh
but i get the following error :
public endpoint for network service in RegionOne region not found
Do you have any idea about how to fix this ?
Thank you

@voyageur
Copy link
Owner

voyageur commented Jul 3, 2017

This sounds like some configuration issue on your deployment, what is your setup, devstack? Which config file?

First step would be to check basic CLI commands for neutron like (after sourcing credentials):

openstack network list
openstack port list

And maybe see if creating a VM works

Also attach full output if possible, to see where it fails exactly (though it looks like region not found would be a problem for most commands)

@onsDridi
Copy link
Author

onsDridi commented Jul 3, 2017

So, this is the vagrant script that i used to create the VM :
'VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "bento/ubuntu-16.04"
config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"
config.vm.network "forwarded_port", guest: 6080, host: 8081, host_ip: "127.0.0.1"
config.vm.provider "virtualbox" do |vb|
vb.customize ["modifyvm", :id, "--memory", "4096"]
vb.customize ["modifyvm", :id, "--cpus", "2"]
end
end`

My config file is :

`[[local|localrc]]
RECLONE=True
enable_service rabbit
disable_service zookeeper
HORIZON_BRANCH=stable/mitaka
KEYSTONE_BRANCH=stable/mitaka
NOVA_BRANCH=stable/mitaka
GLANCE_BRANCH=stable/mitaka
CINDER_BRANCH=stable/mitaka
NEUTRON_BRANCH=stable/mitaka
SWIFT_BRANCH=stable/mitaka
HEAT_BRANCH=stable/mitaka
TROVE_BRANCH=stable/mitaka

enable_service n-novnc
disable_service n-net
enable_service q-dhcp
enable_service q-svc
enable_service q-agt
enable_service q-l3
enable_service q-meta
#enable_service q-lbaas
#enable_service q-vpnaas
enable_service neutron
Q_PLUGIN=ml2
enable_plugin neutron https://github.com/openstack/neutron
enable_service q-qos
ENABLE_TENANT_TUNNELS=True
Q_ML2_TENANT_NETWORK_TYPE=vxlan
enable_plugin networking-sfc https://git.openstack.org/openstack/networking-sfc stable/mitaka
SFC_UPDATE_OVS=False
disable_service h-eng
disable_service h-api
disable_service h-api-cfn
disable_service h-api-cw
disable_service swift
MYSQL_PASSWORD=pass123456
SERVICE_TOKEN=pass123456
SERVICE_PASSWORD=pass123456
ADMIN_PASSWORD=pass123456
RABBIT_PASSWORD=pass123456
VOLUME_BACKING_FILE_SIZE=2048M
API_RATE_LIMIT=False
SCREEN_LOGDIR=$DEST/logs/screen
DATA_DIR=/opt/data
SUBNETPOOL_PREFIX_V4=192.168.0.0/24
VIRT_DRIVER=libvirt
LIBVIRT_TYPE=kvm
`

I used FORCE=yes ./stack.sh to install devstack environment and this is the error that i get
error_devstack.txt

Then i cloned the demo repository git clone https://github.com/voyageur/openstack-scripts.git -b sfc_mitaka_demo
and of course i got an error :
error2.txt

It's the same error for all the other commands

@onsDridi
Copy link
Author

onsDridi commented Jul 4, 2017

I changed the version of openstacksdk in /opt/stack/requirements/upper-constraints.txt file and I installed devstack but the result of this command is ./openstack-scripts/simple_sfc_vms.sh :
resgion_not_found.txt

I try to run these commands openstack network list , openstack port list and i get these errors :
port_error.txt

@voyageur
Copy link
Owner

voyageur commented Jul 8, 2017

Sorry, looks like "openstack port list" did not exist in mitaka :)
The python errors when running devstack should be looked in, the demo script will not work if these commands already fail. Though the config file looks OK... Was devstack on the stable/mitaka branch too? ("git checkout stable/mitaka" or something similar should do the trick)
Also, was the vagrant box a clean one? I know people had problems running a mitaka deployment on a box that had a newer devstack running before (even with cleaning steps)

An alternative would be to switch to current release, removing all stable/mitaka references, the master version works fine on it (well at least it worked 5 days ago when I redeployed). Especially as mitaka is now getting "old" ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants