Ask Your Question

rrottach's profile - activity

2019-05-07 05:59:18 -0500 received badge  Great Answer (source)
2018-04-10 09:17:51 -0500 received badge  Nice Question (source)
2018-03-20 05:03:02 -0500 received badge  Famous Question (source)
2018-02-20 16:15:56 -0500 commented answer Can I do a live upgrade from Newton to Pike?

I will look into those links. Thank you

2018-02-20 06:01:48 -0500 received badge  Notable Question (source)
2018-02-14 09:05:10 -0500 received badge  Popular Question (source)
2018-02-13 15:25:52 -0500 asked a question Can I do a live upgrade from Newton to Pike?

I currently have a controller and 2 compute nodes on Newton and I have 13 instances running and being used daily. I have seen other people having issues when upgrading from one version to another and I can't afford any issues going from Newton to Pike. Is this possible? Should I just do fresh installs on different machines?

2017-11-15 16:53:57 -0500 received badge  Associate Editor (source)
2017-11-15 16:50:33 -0500 answered a question Unauthorized: The request you have made requires authentication. (HTTP 401)

I am in the process of installing Pike and when I logged into Horizon and selected an item in the tree on the left such as instances. I would get logged out stating that was not authorized. I figured out that the auth_uri is wrong in the [keystone_authtoken]

Original line: auth_uri = http://controller:5000

Update line: auth_uri = http://controller:5000/v3

You can see in the admin-openrc and demo-openrc files they use the http://controller:5000/v3 for authentication.

Once I made this change in all of the appropriate files and rebooted i was able to log into Horizon and navigate as expected. This is an error in their documentation for installing Pike.

I am not sure if this will fix your problem but it sounds like a similiar authentication issue to me.

2017-04-18 17:01:04 -0500 received badge  Famous Question (source)
2017-04-18 05:18:25 -0500 received badge  Good Answer (source)
2017-04-11 17:30:19 -0500 commented question Cant ping self-service network

I am going to close this question based on the troubleshooting links I think things are working as expected

2017-04-11 17:30:19 -0500 received badge  Commentator
2017-04-07 02:00:46 -0500 received badge  Notable Question (source)
2017-04-05 11:36:58 -0500 received badge  Popular Question (source)
2017-03-31 19:03:05 -0500 asked a question Cant ping self-service network

I am installing newton on a 2 node setup, a controller and a compute node using neutron networking. I have it up and running and I can launch instances on both the provider and self service networks, I can ssh/ping the provider interface on the router but I cannot ssh/ping the self service interface on the router. I have verified that the bridges, tap interfaces, and the vxlan are all being created and added as networks, and routers are being created. I can ssh into the instances I create on the provider network and I can NAT the provider network to public facing ip's.

The problem is on the self service network, I created a cirros vm (vm1) and logged in via the horizon console and I can ping another vm (vm2) on the self service network but not the interface on the router or any external ip such as 8.8.8.8.

vm1 - 192.168.2.15

vm2 - 192.168.2.10

self service interface on router - 192.168.2.5

I have no errors in my logs that I can find so I have no place to start. I know this isnt a lot of information to start off with so any ideas or suggestions would be greatly appreciated.

UPDATE:

I think i have been looking at neutron networking wrong so I redid the networking as follows

Networks

Provider network - 10.5.0.0/24

Selfservice network - 10.0.0.0/16

Router Interfaces

Provider interface - 10.5.0.12

SelfService interface - 10.0.0.5

Instances

VM1 - 10.0.0.11 - (cirros image)

VM2 - 10.0.0.11 - (ubuntu 16.04 image)

Additional Ports

network:dhcp - 10.0.0.6

I created the cirros vm first and verified that I could ping vm1, vm2, selfservice network router interface, provider network router interface, network:dhcp, and the internet.

I could not connect to the vms through the selfservice network so I added a floating ip to vm1 (10.5.0.11) and I was able to connect. I repeated that with both vms and i can connect to both vms through the provider network.

Since I could not ping the selfservice router interface (10.0.0.5) or the vm's (10.0.0.9,10.0.0.11) from the controller I added a route in my untangle router and now I can ping the selfservice router interface (10.0.0.5) but I cannot ping the vms (10.0.0.9,10.0.0.11).

I think there is a problem between the selfservice router interface and the VM's, is this true or am I attempting to do something that openstack is not designed to do? I have added a screen shot to help explain this

C:\fakepath\Capture 2017-04-04 at 15.47.15.png

2017-03-29 15:05:54 -0500 received badge  Supporter (source)
2017-03-29 15:05:52 -0500 commented answer Mitaka Glance 503 Service Unavailable: The server is currently unavailable. Please try again at a later time. (HTTP 503)

I ran into this problem and I set the wrong password and used openstack user set --password [new glance password] glance and it fixed my issue.

2017-02-25 19:08:15 -0500 received badge  Nice Answer (source)
2017-02-20 23:32:10 -0500 received badge  Self-Learner (source)
2017-02-20 23:32:10 -0500 received badge  Teacher (source)
2016-11-07 15:12:46 -0500 commented question Ubuntu 16.04.1 OpenStack Newton keystone installation problem

I see you have three spaces in your command between default and --description

openstack project create --domain default --description "Service Project" service

try without the extra spaces:

openstack project create --domain default --description "Service Project" ser

2016-06-10 17:36:58 -0500 marked best answer Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

UPDATE: The following is what i did to fix it and thanks to daikk115 for the solution.

Installed the package sudo apt-get install neutron-linuxbridge-agent
Edited neutron.conf sudo pico /etc/neutron/neutron.conf

Under [DEFAULT] rpc_backend = rabbit auth_strategy = keystone

Under [oslo_messaging_rabbit] rabbit_host = controller rabbit_userid = RABBIT_ID rabbit_password = RABBIT_PASSWORD
Under [keystone_authtoken] auth_uri = http://controller:5000 auth_url = http://controller:35357 memcached_servers = controller:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = neutron password = NEUTRON_PASS

Edited linuxbridge_agent.ini. sudo pico /etc/neutron/plugins/ml2/linuxbridge_agent.ini

under [linux_bridge] physical_interface_mappings = selfservice:eth0 provider:eth1 Under [vxlan] enable_vxlan = True local_ip = 10.0.0.41 l2_population = True Under [securitygroup] enable_security_group = True firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

Restarted the service sudo service neutron-linuxbridge-agent restart
Verified the agent list was active on the block node by running this on the controller neutron agent-list

I created a new share manila create NFS 1 --name share1 --description "Share One" --share-network selfservice-net-share1 --share-type generic_share_type I ran on the block node brctl show bridge name
bridge id STP enabled interfaces brq3b7178b7-53 8000.067f3102a858 no vxlan-24 Ifconfig returned (...)

ns-f649cd12-6b Link encap:Ethernet HWaddr fa:16:3e:21:e5:44
inet addr:10.254.0.4 Bcast:10.254.0.15 Mask:255.255.255.240 inet6 addr: fe80::f816:3eff:fe21:e544/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:44 errors:0 dropped:0 overruns:0 frame:0 TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6313 (6.3 KB) TX bytes:7391 (7.3 KB)

tapf649cd12-6b Link encap:Ethernet HWaddr 7e:b9:87:61:91:f6
inet6 addr: fe80::7cb9:87ff:fe61:91f6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:115 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7391 (7.3 KB) TX bytes:6313 (6.3 KB)

vxlan-24 Link encap:Ethernet HWaddr 06:7f:31:02:a8:58
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:46 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8251 (8.2 KB) TX bytes:4917 (4.9 KB)

I added the tap interface to the bridge sudo brctl addif brq3b7178b7-53 tapf649cd12-6b

At that point the share was created successfully

When I create a new share it goes to an error status after the SSH 300s timeout is exeeded. I attempted to locate the path_to_public_key and path_to_private_key variables with no luck. I have spent two days on this and all the services are up, no issues that I can find. I am going to wipe and redo the controller and block storage nodes in case something was not done in the right order/sequence. Any ideas would be appreciated.

Block1 storage node /var/log/manila/manila-share.log

2016-05-19 11:41:04.478 27439 WARNING manila.context ...
(more)
2016-06-10 17:36:58 -0500 received badge  Scholar (source)
2016-06-10 17:03:45 -0500 commented answer Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

After rebooting all nodes it started working. Thanks for all your help!

2016-06-10 16:27:39 -0500 commented answer Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

I installed the neutron-linuxbridge-agent on the block node and configured the neutron.conf and linuxbridge_agent.ini the same as the compute node. I see an entry in brctl show now and I added the tap interface to the bridge but I still have the same issue.

2016-06-10 11:29:29 -0500 commented answer Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

Yes and just in case any services were not running I rebooted all machines.

2016-06-09 11:16:45 -0500 commented answer Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

when I run brctl show on the block node there is nothing displayed.

2016-06-08 16:34:46 -0500 commented answer Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

I modified the object node /etc/neutron/plugins/ml2/linuxbridge_agent.ini file and made the same modifications as the controller and compute nodes. I get the same issue. I cannot ping the manila_service_network from any node and thats probably the issue.

2016-06-08 16:31:21 -0500 commented question Mitaka: Manila Share Create Error. No key path is available. May be non-existent key path is provided

I created public and private keys on the controller,and block nodes. I added the path_to_private_key = ~/.ssh/id_rsa and path_to_public_key = ~/.ssh/id_rsa to the /etc/manila/manila.conf files and I still get the error No key path is available. May be non-existent key path is provided. Check path_to