Ask Your Question

Spoorthi Vaidya's profile - activity

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-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
2019-05-21 04:37:41 -0500 commented question Stein : Unable to ping ip of instance

above 2 comments shows the configuration of /etc/sysconfig/network-scripts/ifcfg-ens192 file...both for compute and controller.... only ip address is change

2019-05-21 04:37:41 -0500 commented question Stein : Unable to ping ip of instance

NAME=ens192

      UUID=b5cb7aab-4e08-43e8-992d-01a81bd644b5


        DEVICE=ens192


        ONBOOT=yes


        IPADDR=10.xx.xx.xx


        NETMASK=255.255.254.0
2019-05-21 04:37:41 -0500 commented question Stein : Unable to ping ip of instance

TYPE=Ethernet

PROXY_METHOD=none

BROWSER_ONLY=no

BOOTPROTO=none

DEFROUTE=yes
2019-05-21 03:40:32 -0500 asked a 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-20 01:34:19 -0500 received badge  Notable Question (source)
2019-05-19 10:15:18 -0500 received badge  Popular Question (source)
2019-05-19 06:51:09 -0500 answered a question Stein: failed to create resource provider

The problem is solved.

  2019-05-19 10:48:24.283 10518 ERROR nova.compute.resource_tracker [req-4d4dab18-2b5a-4d35-834c-d4a224fdb6be - - - - -] Skipping removal of allocations for deleted instances: Failed to retrieve allocations for resource provider 46e7f4c0-4592-4e90-ad12-21e503773131: {"errors": [{"status": 404, "request_id": "req-7b9ddbdb-83e3-4b91-b0f1-c74017e1d2dd", "detail": "The resource could not be found.\n\n Resource provider '46e7f4c0-4592-4e90-ad12-21e503773131' not found: No resource provider with uuid 46e7f4c0-4592-4e90-ad12-21e503773131 found  ", "title": "Not Found"}]}: ResourceProviderAllocationRetrievalFailed: Failed to retrieve allocations for resource provider 46e7f4c0-4592-4e90-ad12-21e503773131: {"errors": [{"status": 404, "request_id": "req-7b9ddbdb-83e3-4b91-b0f1-c74017e1d2dd", "detail": "The resource could not be found.\n\n Resource provider '46e7f4c0-4592-4e90-ad12-21e503773131' not found: No resource provider with uuid 46e7f4c0-4592-4e90-ad12-21e503773131 found  ", "title": "Not Found"}]}
    2019-05-19 10:48:24.331 10518 ERROR nova.scheduler.client.report [req-4d4dab18-2b5a-4d35-834c-d4a224fdb6be - - - - -] [req-4ef7b386-65ab-4da8-8028-63e4ec506ccd] Failed to create resource provider record in placement API for UUID 46e7f4c0-4592-4e90-ad12-21e503773131. Got 409: {"errors": [{"status": 409, "request_id": "req-4ef7b386-65ab-4da8-8028-63e4ec506ccd", "detail": "There was a conflict when trying to complete your request.\n\n Conflicting resource provider name: compute already exists.  ", "title": "Conflict"}]}.

I had the above error in the nova-compute log.

when i checked in the nova database, compute nodes table, UUID of compute node was different from UUID of resource providers in the placement table

  https://ask.openstack.org/en/question/115081/openstack-queen-instance-creation-error-no-valid-host-was-found/

according the ans provided by BERND in above link,

i followed the below steps:

  $ openstack catalog list
$ PLACEMENT_ENDPOINT=placement-endpoint-returned-by-previous-command
$ openstack token issue -f value -c id
$ TOKEN=the-token-returned-by-the-previous-command
$ curl ${PLACEMENT_ENDPOINT}/resource_providers -H "x-auth-token: $TOKEN" | python -m json.tool
$ UUID=uuid-of-resource-provider-named-openstack
$ curl ${PLACEMENT_ENDPOINT}/resource_providers/$UUID -H "x-auth-token: $TOKEN" -X DELETE

after performing above steps, when i checked the resource providers table in placement database, it updated UUID of resource_provider to UUID of compute node in the compute_nodes table of nova db. Now im able to launch instance with active status.

THANKS TO BERND BAUSCH @Bernd Bausch

2019-05-19 06:51:08 -0500 edited question Stein: failed to create resource provider

Hi when i tried to create the instance, it lauched with error status. i checked /var/log/nova/nova-compute.log, it shows following error.

2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-

    packages/nova/scheduler/client/report.py", line 873, in get_provider_tree_and_ensure_root
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager     parent_provider_uuid=parent_provider_uuid)
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/scheduler/client/report.py", line 659, in _ensure_resource_provider
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager     parent_provider_uui

d=parent_provider_uuid)
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/scheduler/client/report.py", line 71, in wrapper
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager     return f(self, *a, **k)
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/scheduler/client/report.py", line 593, in _create_resource_provider
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager     raise exception.ResourceProviderCreationFailed(name=name)
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager ResourceProviderCreationFailed: Failed to create resource provider compute
    2019-05-17 10:02:58.328 10518 ERROR nova.compute.manager

when i run below command the output is as below.

[root@controller conf.d]# openstack service list
+----------------------------------+-----------+-----------+
| ID                               | Name      | Type      |
+----------------------------------+-----------+-----------+
| 2988099942a54a8bb011d5b90475ebfc | glance    | image     |
| 4e057bd2e7e74f9083637c46dfd9e13b | keystone  | identity  |
| 80e5c533b3924c3891ba674876c793a5 | placement | placement |
| b93d73ec4e574c589b1feaf33f1afde9 | neutron   | network   |
| e5497989ec2946d3866ad675767f94c4 | nova      | compute   |
+----------------------------------+-----------+-----------+

nova-sheduler.log has following content

[root@controller nova]# tail -f nova-scheduler.log
2019-05-17 09:58:41.740 22462 INFO nova.filters [req-a91178b7-dfd8-4c08-9dda-e100b798eada d1974e4832b54ba5a38a4534cc413020 cd08d7de6fc947baa4d7905134a7d011 - default default] Filter RetryFilter returned 0 hosts
2019-05-17 09:58:41.741 22462 INFO nova.filters [req-a91178b7-dfd8-4c08-9dda-e100b798eada d1974e4832b54ba5a38a4534cc413020 cd08d7de6fc947baa4d7905134a7d011 - default default] Filtering removed all hosts for the request with instance ID '424d011d-98c1-4545-b8a5-6af537fcce40'. Filter results: ['RetryFilter: (start: 0, end: 0)']

placement database's resource providers table has following content

MariaDB [placement]> select * from resource_providers;
+---------------------+---------------------+----+--------------------------------------+---------+------------+------------------+--------------------+
| created_at          | updated_at          | id | uuid                                 | name    | generation | root_provider_id | parent_provider_id |
+---------------------+---------------------+----+--------------------------------------+---------+------------+------------------+--------------------+
| 2019-05-16 08:56:23 | 2019-05-16 08:56:23 |  1 | fb1834e7-0f67-4bd1-abdf-5b4823f25243 | compute |          2 |                1 |               NULL |
+---------------------+---------------------+----+--------------------------------------+---------+------------+------------------+--------------------+

in controller's nova.conf i have configured:--

[placement]
region_name = RegionOne
project_domain_name = Default
project_name = service
auth_type = password
user_domain_name = Default
auth_url = http://controller:5000/v3
username = placement
password = PLACEMENT_DBPASS


[placement_database]
connection = mysql+pymysql://nova:NOVA_DBPASS@controller/nova_api

and in compute node's nova.conf

[placement]
region_name = RegionOne
project_domain_name = Default
project_name = service
auth_type = password
user_domain_name = Default
auth_url = http://controller:5000/v3
username = placement
password = PLACEMENT_DBPASS

BUT NOVA_API database has resource_providers table empty,

MariaDB [nova_api]> select * from resource_providers  ;
Empty set (0.000 sec)


[root@controller openstackusr]# su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
Found 2 cell mappings.
Skipping cell0 since it does not contain hosts.
Getting computes from cell 'cell1': 9f8dd40e-1fc4-4f5d-89bb-a48640069162
Found 0 unmapped computes in cell: 9f8dd40e-1fc4-4f5d-89bb-a48640069162

please help me out.

2019-05-19 01:22:19 -0500 commented answer Stein: failed to create resource provider
2019-05-19 01:22:19 -0500 answered a question Stein: failed to create resource provider

2019-05-19 03:13:52.290 10518 ERROR nova.compute.resource_tracker [req-4d4dab18-2b5a-4d35-834c-d4a224fdb6be - - - - -] Skipping removal of allocations for deleted instances: Failed to retrieve allocations for resource provider 46e7f4c0-4592-4e90-ad12-21e503773131: {"errors": [{"status": 404, "request_id": "req-0b8e0658-e6ff-4c15-aca1-d78613d805c4", "detail": "The resource could not be found.\n\n Resource provider '46e7f4c0-4592-4e90-ad12-21e503773131' not found: No resource provider with uuid 46e7f4c0-4592-4e90-ad12-21e503773131 found ", "title": "Not Found"}]}: ResourceProviderAllocationRetrievalFailed: Failed to retrieve allocations for resource provider 46e7f4c0-4592-4e90-ad12-21e503773131: {"errors": [{"status": 404, "request_id": "req-0b8e0658-e6ff-4c15-aca1-d78613d805c4", "detail": "The resource could not be found.\n\n Resource provider '46e7f4c0-4592-4e90-ad12-21e503773131' not found: No resource provider with uuid 46e7f4c0-4592-4e90-ad12-21e503773131 found ", "title": "Not Found"}]} 2019-05-19 03:13:52.329 10518 ERROR nova.scheduler.client.report [req-4d4dab18-2b5a-4d35-834c-d4a224fdb6be - - - - -] [req-5fe269cd-53a9-4044-8535-304ebd1ff167] Failed to create resource provider record in placement API for UUID 46e7f4c0-4592-4e90-ad12-21e503773131. Got 409: {"errors": [{"status": 409, "request_id": "req-5fe269cd-53a9-4044-8535-304ebd1ff167", "detail": "There was a conflict when trying to complete your request.\n\n Conflicting resource provider name: compute already exists. ", "title": "Conflict"}]}.

I mention whole error in comment section... so i have put here... this is the error in nova-compute.log

https://ask.openstack.org/en/question/115081/openstack-queen-instance-creation-error-no-valid-host-was-found/

in the above link, as per your ans(@bernd), even in my cloud the UUID returned by nova hypervisor-list is different with the UUID obtained from the command

 curl ${PLACEMENT_ENDPOINT}/resource_providers -H "x-auth-token: $TOKEN" | python -m json.tool

but

The API to delete a resource provider:

$ UUID=uuid-of-resource-provider-named-openstack
$ curl ${PLACEMENT_ENDPOINT}/resource_providers/$UUID -H "x-auth-token: $TOKEN" -X DELETE

but u said to delete resource provider named openstack, what does it mean, R U SAYING to delete resource provider UUID obtained from the command

  curl ${PLACEMENT_ENDPOINT}/resource_providers -H "x-auth-token: $TOKEN" | python -m json.tool

or from nova hypervisor-list?

2019-05-19 01:22:19 -0500 commented question Stein: failed to create resource provider

how can i know which filter scheduler is rejecting the host?

2019-05-19 01:22:19 -0500 commented question Stein: failed to create resource provider

https://stackoverflow.com/questions/32200851/openstack-failed-to-launch-instances-error-no-valid-host-was-found?rq=1 (https://stackoverflow.com/questions/3...)

In this link ans is to increase the cpu allocation and ram and disk allocatiion.. i tried assigning 3 to them only in compute node,

but it dint work

2019-05-19 01:22:19 -0500 commented question openstack ocataļ¼šFilter RetryFilter returned 0 hosts

even i have same problem for stein version. Please help me out with the solution. i Checked the configuration many times there is no mistake.

2019-05-19 01:22:19 -0500 commented question Stein: failed to create resource provider

should i run yum install openstack-placement-api command and configure /etc/placement/placement.conf file even in compute node.???

2019-05-18 23:12:39 -0500 received badge  Popular Question (source)
2019-05-18 02:45:13 -0500 commented question Stein: failed to create resource provider

https://ask.openstack.org/en/question/115081/openstack-queen-instance-creation-error-no-valid-host-was-found/ (https://ask.openstack.org/en/question...) Will this help me?

2019-05-18 02:45:13 -0500 commented question Stein: failed to create resource provider

Why is it filtering all host---nova-scheduler.log?? No valid host found... Should I configure filter scheduler in Nova.conf

2019-05-17 06:04:10 -0500 commented question Stein: failed to create resource provider

And I have 00-placement-api.conf instead of 00-nova-placement-api.conf.... is this the reason?

2019-05-17 06:04:10 -0500 commented question Stein: failed to create resource provider

What might be the reason for such error? Its just related to placement service????