Ask Your Question

tland12's profile - activity

2017-06-17 08:51:02 -0600 received badge  Famous Question (source)
2017-06-11 12:45:34 -0600 received badge  Notable Question (source)
2017-06-10 05:23:15 -0600 commented question Newton and Ocata: can't ping VM on CentOS 7.3 and Ubuntu 17

AndyWbjo thank you for your comment.

Please check my updated question above about your question.

2017-06-09 17:26:31 -0600 received badge  Popular Question (source)
2017-06-09 03:23:03 -0600 asked a question Newton and Ocata: can't ping VM on CentOS 7.3 and Ubuntu 17

Hello OpenStack users, I stuck in OpenStack Neutron for a month. Please help me solve this problem.

My environment is below

  1. CentOS 7.3 + Newton + Linuxbridge + Flat type = failed to ping VM but successful for DHCP namespace

  2. Ubuntu 16.04.2 + Newton +Linuxbridge +Flat type = ping is successful for VM and DHCP namespace

  3. CentOS 7.3 +Ocata + Linuxbridge + Flat type = failed to ping VM but successful for DHCP namespace

  4. Ubuntu 17.04 + Ocata + Linuxbridge + Flat type = failed to ping VM but successful for DHCP namespace

Even if I copied all configuration files from Ubuntu 16.04 and Newton to CentOS 7.3 and Newton, ping did not work. It means that ping works well in Newton of Ubuntu 16.04.2 but does not work in Newton of CentOS 7.3 using same configurations and environments. I can not find any error messages on the log files from Nova and Neutron after creating VM.

I am using same OpenStack version (Newton) and ping works well on Ubuntu 16.04.2 but failed to ping on CentOS7.3.

I installed CentOS 7 on VMWare Workstation as a host and create 3 instances as guests. 3 instances are CentOS7 created using virt-install and CentOS7.3 created using CentOS cloud image and cirros.

In the log file '/var/log/messages' I found when sent ping 213.0.113.102 (Instance) on Controller node 'controller1 avahi-daemon[746]: Received response from host 169.254.145.82 with invalid source port 54663 on interface 'eno16777736.0' and eno16777736 is the interface name connected for Provider network.

In Compute Node I found same log from /var/log/messages

compute1 avahi-daemon[795]: Received response from host 169.254.145.82 with invalid source port 54663 on interface 'brq03f03b81-1c.0'
Here interface brq03f03b81-1c.0' is the interface name of bridge connected for Provider network on Compute node.

In the DHCP namespace I found these IP addresses

[root@network1 ~]# ip addr

ns-98a44388-21@if6: <broadcast,multicast,up,lower_up> mtu 1500 qdisc noqueue state UP qlen 1000 link/ether fa:16:3e:bb:61:d1 brd ff:ff:ff:ff:ff:ff link-netnsid 0

**inet 213.0.113.101/24 brd 213.0.113.255 scope global ns-98a44388-21 valid_lft forever preferred_lft forever

inet 169.254.169.254/16 brd 169.254.255.255 scope global ns-98a44388-21 valid_lft forever preferred_lft forever**

Thank you for your help in advance.

2017-06-09 03:11:42 -0600 received badge  Enthusiast
2017-03-24 09:17:50 -0600 received badge  Famous Question (source)
2017-03-24 09:17:50 -0600 received badge  Notable Question (source)
2017-03-24 09:17:50 -0600 received badge  Popular Question (source)
2017-02-06 00:06:12 -0600 answered a question openstack-cinder-api failed

I am successful to start cinder-api and cinder-scheduler after reboot controller node and start all openstack services such as glance, nova and neutron.

[root@controller1 ~]# lsof –i tcp:8776
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

cinder-ap 4922 cinder 7u IPv4 41293 0t0 TCP *:8776 (LISTEN)

cinder-ap 4958 cinder 7u IPv4 41293 0t0 TCP *:8776 (LISTEN)

cinder-ap 4959 cinder 7u IPv4 41293 0t0 TCP *:8776 (LISTEN)

[root@controller1 ~]# cinder service-list

+------------------+----------------------+------+---------+-------+------------------ | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | +------------------+----------------------+------+---------+-------+----------------------------+-----------------+ | cinder-scheduler | http://controller1.chul.com | nova | enabled | up | 2017-02-06T05:25:14.000000 | - |

2017-02-05 00:49:31 -0600 commented question openstack-cinder-api failed

However I could not find any error messages from /var/log/cinder/api.log and scheduler.log

2017-02-05 00:48:15 -0600 received badge  Editor (source)
2017-02-05 00:41:36 -0600 commented question openstack-cinder-api failed

[root@controller1 ~]# cinder service-list

ERROR: Unable to establish connection to http://192.168.80.3:8776/v2/ba40e0d269db49fda3ab07438f36e1da/os-services (http://192.168.80.3:8776/v2/ba40e0d26...): HTTPConnectionPool(host='192.168.80.3', port=8776): Max retries exceeded with url: /v2/ba40e0d269db49fda3ab07438f36e1da/os-services (Caused by

2017-02-05 00:41:05 -0600 commented question openstack-cinder-api failed

Bernd thank you for your comment. This is the process I configured for openstack-cinder-api

  1. I was successful to start cinder-api and cinder-scheduler on Ubuntu 16.04 but failed on CentOS 7.2 with same configuration file
  2. The error messages above were repeated constantly on /var/log/messages
2017-02-04 05:38:12 -0600 asked a question openstack-cinder-api failed

Hi guys I tried to start openstack-cinder-api but failed. Please help me to solve this issue. Thank you for your help in advance.

[root@controller1 ~]# cat /etc/centos-release

CentOS Linux release 7.3.1611 (Core) 

[root@controller1 ~]# rpm -qa | grep newton

centos-release-openstack-newton-1-1.el7.noarch

[root@controller1 ~]# systemctl start opensack-cinder-api openstack-cinder-scheduler

[root@controller1 ~]# systemctl status openstack-cinder-api

openstack-cinder-api.service - OpenStack Cinder API Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-cinder-api.service; disabled; vendor preset: disabled)

Active: active (running) since Sat 2017-02-04 15:53:06 KST; 1ms ago
 Main PID: 16352 (systemd)
   CGroup: /system.slice/openstack-cinder-api.service
           16352 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
Feb 04 15:53:06 controller1.chul.com systemd[1]: openstack-cinder-api.service holdoff time over,...rt.

Feb 04 15:53:06 controller1.chul.com systemd[1]: Started OpenStack Cinder API Server.

[root@controller1 ~]# lsof -i tcp:8776

[root@controller1 ~]# tail -f /var/log/messages

Feb  4 15:54:25 controller1 cinder-api: 2017-02-04 15:54:25.313 16762 WARNING cinder.api [-] The v1 api is deprecated and is not under active development. You should set enable_v1_api=false and enable_v3_api=true in your cinder.conf file.

Feb  4 15:54:25 controller1 kernel: cinder-api[16762]: segfault at 7f414b8eb760 ip 00007f414b8eb760 sp 00007ffca6bc41b8 error 15 in multiarray.so[7f414b8ea000+d000]
Feb  4 15:54:25 controller1 systemd: openstack-cinder-api.service: main process exited, code=killed, status=11/SEGV
Feb  4 15:54:25 controller1 systemd: Unit openstack-cinder-api.service entered failed state.

Feb  4 15:54:25 controller1 systemd: openstack-cinder-api.service failed.

Feb  4 15:54:25 controller1 systemd: openstack-cinder-api.service holdoff time over, scheduling restart.

Feb  4 15:54:25 controller1 systemd: Started OpenStack Cinder API Server.

Feb  4 15:54:25 controller1 systemd: Starting OpenStack Cinder API Server...

Feb  4 15:54:25 controller1 cinder-scheduler: Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT".

Feb  4 15:54:25 controller1 cinder-scheduler: 2017-02-04 15:54:25.817 16764 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.

Feb  4 15:54:26 controller1 kernel: cinder-schedule[16764]: segfault at 7f749a4ba760 ip 00007f749a4ba760 sp 00007fffb21e1168 error 15 in multiarray.so[7f749a4b9000+d000]

Feb  4 15:54:26 controller1 systemd: openstack-cinder-scheduler.service: main process exited, code=killed, status=11/SEGV
Feb  4 15:54:26 controller1 systemd: Unit openstack-cinder-scheduler.service entered failed state.

Feb  4 15:54:26 controller1 systemd: openstack-cinder-scheduler.service failed.

Feb  4 15:54:26 controller1 systemd: openstack-cinder-scheduler.service holdoff time over, scheduling restart.

Feb  4 15:54:26 controller1 systemd: Started OpenStack Cinder Scheduler Server.

Feb  4 15:54:26 controller1 systemd: Starting OpenStack Cinder Scheduler Server...

[root@controller1 ~]# cinder service-list

ERROR: Unable to establish connection to http://192.168.80.3:8776/v2/ba40e0d269db49fda3ab07438f36e1da/os-services (http://192.168.80.3:8776/v2/ba40e0d26...): HTTPConnectionPool(host='192.168.80.3', port=8776): Max retries exceeded with url: /v2/ba40e0d269db49fda3ab07438f36e1da/os-services (Caused by NewConnectionError ... (more)