Ask Your Question

Spoorthi Vaidya's profile - activity

2020-06-06 19:25:27 -0500 received badge  Self-Learner (source)
2020-05-14 15:18:55 -0500 received badge  Famous Question (source)
2020-05-14 15:18:55 -0500 received badge  Notable Question (source)
2020-02-28 20:05:19 -0500 received badge  Notable Question (source)
2020-02-28 20:05:19 -0500 received badge  Popular Question (source)
2020-01-22 11:40:29 -0500 received badge  Self-Learner (source)
2020-01-20 17:10:31 -0500 received badge  Famous Question (source)
2019-12-02 00:32:39 -0500 received badge  Famous Question (source)
2019-12-02 00:32:39 -0500 received badge  Notable Question (source)
2019-09-18 22:59:33 -0500 received badge  Famous Question (source)
2019-09-18 22:59:33 -0500 received badge  Notable Question (source)
2019-09-18 22:59:33 -0500 received badge  Popular Question (source)
2019-09-13 14:15:45 -0500 received badge  Necromancer (source)
2019-08-21 14:42:53 -0500 received badge  Famous Question (source)
2019-08-21 14:42:53 -0500 received badge  Popular Question (source)
2019-08-21 14:42:53 -0500 received badge  Notable Question (source)
2019-08-15 08:20:11 -0500 marked best answer --os-compute-api-version 2.11 or later is required

When i run

openstack compute service set --up compute nova-compute

i get following output:

--os-compute-api-version 2.11 or later is required

openstack compute service list outputs:-

+----+----------------+------------+----------+---------+-------+----------------------------+
| ID | Binary         | Host       | Zone     | Status  | State | Updated At                 |
+----+----------------+------------+----------+---------+-------+----------------------------+
|  1 | nova-scheduler | controller | internal | enabled | up    | 2019-05-14T10:34:47.000000 |
|  7 | nova-conductor | controller | internal | enabled | up    | 2019-05-14T10:34:44.000000 |
| 17 | nova-compute   | compute    | nova     | enabled | down  | 2019-05-14T07:56:44.000000 |
+----+----------------+------------+----------+---------+-------+----------------------------+

when i try to restart nova-compute using

systemctl start openstack-nova-compute.service i got output:-

Failed to start openstack-nova-compute.service: Unit not found.

So i tried to make state up through the command

openstack compute service set --up compute nova-compute

but got the above output please help me.

2019-07-24 06:47:35 -0500 received badge  Famous Question (source)
2019-07-20 02:08:44 -0500 received badge  Famous Question (source)
2019-07-20 02:08:44 -0500 received badge  Notable Question (source)
2019-06-21 11:02:46 -0500 received badge  Self-Learner (source)
2019-06-21 11:02:46 -0500 received badge  Teacher (source)
2019-06-21 11:01:30 -0500 received badge  Famous Question (source)
2019-06-06 03:01:25 -0500 received badge  Notable Question (source)
2019-05-23 20:22:12 -0500 received badge  Famous Question (source)
2019-05-22 17:25:05 -0500 received badge  Notable Question (source)
2019-05-22 06:09:42 -0500 commented question Stein : Unable to ping ip of instance

above is for compute node... same as controller..

2019-05-22 06:09:42 -0500 commented question Stein : Unable to ping ip of instance

[linux_bridge]

    physical_interface_mappings = provider:ens192
[vxlan]
enable_vxlan = true
local_ip = 10.65.156.12
l2_population = true

[securitygroup]
enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
2019-05-22 06:09:38 -0500 commented question Stein : Unable to ping ip of instance

both are ens192... in controller as well as compute... did that led to confusion in network bridging?

2019-05-22 06:09:38 -0500 commented question Stein : Unable to ping ip of instance

above is the configuration in /etc/neutron/plugins/ml2/linuxbridge_agent.ini file in controller.

2019-05-22 06:09:38 -0500 commented question Stein : Unable to ping ip of instance

[linux_bridge]

    physical_interface_mappings = provider:ens192

    [vxlan]
    enable_vxlan = true
    local_ip = 10.65.156.13
    l2_population = true

    [securitygroup]
    enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
2019-05-22 06:09:37 -0500 commented question Stein : Unable to ping ip of instance

openstack subnet create --network provider \ --allocation-pool start=10.65.156.4,end=10.65.156.6 \ --dns-nameserver 10.65.32.40 --gateway 10.65.156.1 \ --subnet-range 10.65.156.0/23 provider

2019-05-22 06:09:37 -0500 commented question Stein : Unable to ping ip of instance

openstack network create --share --external \ --provider-physical-network provider \ --provider-network-type flat provider

this command i used to create external network..

2019-05-22 03:30:08 -0500 commented question Stein : Unable to ping ip of instance

the instance with ip address 10.65.156.5 is not able to reach any ip address other than 192.168.122.1..... after i created a new self service network...with ip range 192.168.122.0/24

2019-05-22 03:01:02 -0500 answered a question Stein : Unable to ping ip of instance

I have mentioned the routing table here...since i couldnt paste in comment section and question was under previous moderation @Bernd Bausch

routing table of controller:----------

   [root@controller openstackusr]# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         10.65.156.1     0.0.0.0         UG    95     0        0 brqcff3d573-e4
    10.65.156.0     0.0.0.0         255.255.254.0   U     0      0        0 brqcff3d573-e4
    192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0

Routing table of compute is:-----------

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.65.156.1     0.0.0.0         UG    98     0        0 ens192
10.65.156.0     0.0.0.0         255.255.254.0   U     0      0        0 ens192
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0

after i created the new self service network with subnet created using following command..

openstack subnet create --network selfservice \
  --dns-nameserver 8.8.4.4 --gateway 192.168.122.1 \
  --subnet-range 192.168.122.0/24 selfservice

i can ping only 192.168.122.1 from instance...

the instance couldnt ping its own floating ip...nor controller's nor computes...

2019-05-22 03:01:01 -0500 commented question Stein : Unable to ping ip of instance

controller ip address is 10.65.156.13 compute 10.65.156.12both can reach each other when pinged... .i have configured controller and compute on cloud vms. my instance floating ip is 10.65.156.5 which can be pinged through only controller.... not through compute.

2019-05-22 03:01:01 -0500 commented question Stein : Unable to ping ip of instance

brqcff3d573-e4 8000.005056a7986f no ens192

2019-05-22 03:01:01 -0500 commented question Stein : Unable to ping ip of instance

tapc3cc2398-fc virbr0 8000.5254008b918a yes virbr0-nic

2019-05-22 03:01:01 -0500 commented question Stein : Unable to ping ip of instance

[root@controller openstackusr]# brctl show

bridge name     bridge id               STP enabled     interfaces
brqc168df54-11          8000.2273c2208fa8       no              tap53e67b39-17
2019-05-22 03:01:01 -0500 commented question Stein : Unable to ping ip of instance

when i run ip a command on controller... one of the output is 3: virbr0: <no-carrier,broadcast,multicast,up> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:8b:91:8a brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 va

2019-05-22 03:01:01 -0500 commented question Stein : Unable to ping ip of instance

i have updated the question.... please help me.

2019-05-22 03:01:01 -0500 edited question Stein : Unable to ping ip of instance

Hi i have built a OpenStack cloud on RHEL 7. I have used networking option 2.

After creating the instance i'm able to ping the floating ip address of instance on controller but not on compute or on any hosts on provider network.

according to this link , in the verification section,

https://docs.openstack.org/install-guide/launch-instance-networks-selfservice.html

after running the command openstack port list --router router

output: IP ADDRESS I was able to ping ip address on controller but not on any other host on the provider network.

and

i was not able to ping any ip address on the instance, only controller ip address was able to ping.

ALLOW IPv6 to ::/0
ALLOW IPv4 from default
ALLOW IPv6 from default
ALLOW IPv4 22/tcp from 0.0.0.0/0
ALLOW IPv4 to 0.0.0.0/0
ALLOW IPv4 icmp from 0.0.0.0/0
ALLOW IPv4 80/tcp from 0.0.0.0/0
ALLOW IPv4 53/tcp from 0.0.0.0/0

above is the security group applied for instance.

[root@controller openstackusr]# . admin-openrc
[root@controller openstackusr]# neutron agent-list
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
+--------------------------------------+--------------------+------------+-------------------+-------+----------------+---------------------------+
| id                                   | agent_type         | host       | availability_zone | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+------------+-------------------+-------+----------------+---------------------------+
| 80fa2650-9959-44f1-a87e-b12b5755b2b7 | L3 agent           | controller | nova              | :-)   | True           | neutron-l3-agent          |
| 9f7f4043-9d17-464c-8268-5f5b51102dc9 | Linux bridge agent | compute    |                   | :-)   | True           | neutron-linuxbridge-agent |
| a54e01e9-ecaa-4a3b-915e-8905a5450413 | Metadata agent     | controller |                   | :-)   | True           | neutron-metadata-agent    |
| a8a7dd11-2b19-4d59-8422-ea25a94c7819 | DHCP agent         | controller | nova              | :-)   | True           | neutron-dhcp-agent        |
| f29e3aaf-14b7-4bf9-bb71-e6c0f84e9e9d | Linux bridge agent | controller |                   | :-)   | True           | neutron-linuxbridge-agent |
+--------------------------------------+--------------------+------------+-------------------+-------+----------------+---------------------------+

[root@controller openstackusr]#

root@controller openstackusr]# openstack port list --router router
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+
| ID                                   | Name | MAC Address       | Fixed IP Addresses                                                         | Status |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+
| 60fbde00-287e-4898-a9ce-94931a416365 |      | fa:16:3e:b1:92:be | ip_address='172.16.1.1', subnet_id='cde52553-67ee-4f9a-b13e-abfb04eca743'  | ACTIVE |
| fd3e5cb5-d21e-42b3-93f4-ebbc21eedd73 |      | fa:16:3e:84:0d:c9 | ip_address='10.xx.xx.6', subnet_id='71ae2f89-29de-40c0-827c-bab1cd959ae0' | ACTIVE |
+------------------------

--------------+------+-------------------+----------------------------------------------------------------------------+--------+

when i ping IP 10.xx.xx.6 on controller, it pings... but not in compute or any other hosts on network provider.

tracerout 10.xx.xx.6 gives output in controller, but not on other hosts.

please help me out.

Following error is shown up in the log dashboard....of instance...

  === network info ===
    if-info: lo,up,127.0.0.1,8,,
    if-info: eth0,up,192.168.122.97,24,fe80::f816:3eff:fe88:3164/64,
    ip-route:default via 192.168.122.1 dev eth0 
    ip-route:169.254.169.254 via 192.168.122.1 dev eth0 
    ip-route:192.168.122.0/24 dev eth0  src 192.168.122.97 
    ip-route6:fe80::/64 dev eth0  metric 256 
    ip-route6:unreachable default dev lo  metric -1  error -101
    ip-route6:ff00::/8 dev eth0  metric 256 
    ip-route6:unreachable default dev lo  metric -1  error -101
    === datasource: None None ===
    === cirros: current=0.4.0 uptime=253.59 ===
  ____               ____  ____
2019-05-21 23:57:44 -0500 commented question Stein : Unable to ping ip of instance

For selfservice network subnet creation i haved following command:---

openstack subnet create --network selfservice \ --dns-nameserver 8.8.4.4 --gateway 172.16.1.1 \ --subnet-range 172.16.1.0/24 selfservice

i have randomly given as 172.16.1.x range........

2019-05-21 23:57:44 -0500 commented question Stein : Unable to ping ip of instance

I used the above command to create the provider network... I have put gateway as the ip address obtained from route -n command and dns nameserver to be the ip address in the file /etc/resolv.conf in the controller node... both controller and compute node has same gateway and dns ip addr.

2019-05-21 23:57:44 -0500 commented question Stein : Unable to ping ip of instance

openstack subnet create --network provider \ --allocation-pool start=10.xx.xx.4,end=10.xx.xx.6 \ --dns-nameserver 10.yy.yy.yy --gateway 10.xx.xx.1 \ --subnet-range 10.xx.xx.0/23 provider

2019-05-21 23:26:16 -0500 received badge  Popular Question (source)
2019-05-21 04:37:54 -0500 commented question Stein : Unable to ping ip of instance

content of /etc/neutron/l3_agent.ini is

[DEFAULT]
interface_driver = linuxbridge
2019-05-21 04:37:49 -0500 commented question Stein : Unable to ping ip of instance

i have followed the stein documentation for redhat rdo package.

https://docs.openstack.org/neutron/stein/install/controller-install-option2-rdo.html