Yes, sorry. Also the 8775 port is reachable from neutron metadata agent Regards Ignazio
Il giorno lun 12 nov 2018 alle ore 23:08 Slawomir Kaplonski < skapl...@redhat.com> ha scritto: > Hi, > > > Wiadomość napisana przez Ignazio Cassano <ignaziocass...@gmail.com> w > dniu 12.11.2018, o godz. 22:55: > > > > Hello, > > the nova api in on the same controller on port 8774 and it can be > reached from the metadata agent > > Nova-metadata-api is running on port 8775 IIRC. > > > No firewall is present > > Regards > > > > Il giorno lun 12 nov 2018 alle ore 22:40 Slawomir Kaplonski < > skapl...@redhat.com> ha scritto: > > Hi, > > > > From logs which You attached it looks that Your neutron-metadata-agent > can’t connect to nova-api service. Please check if nova-metadata-api is > reachable from node where Your neutron-metadata-agent is running. > > > > > Wiadomość napisana przez Ignazio Cassano <ignaziocass...@gmail.com> w > dniu 12.11.2018, o godz. 22:34: > > > > > > Hello again, > > > I have another installation of ocata . > > > On ocata the metadata for a network id is displayed by ps -afe like > this: > > > /usr/bin/python2 /bin/neutron-ns-metadata-proxy > --pid_file=/var/lib/neutron/external/pids/c4731392-9b91-4663-adb3-b10b5ebcc4f1.pid > --metadata_proxy_socket=/var/lib/neutron/metadata_proxy > --network_id=c4731392-9b91-4663-adb3-b10b5ebcc4f1 > --state_path=/var/lib/neutron --metadata_port=80 --metadata_proxy_user=996 > --metadata_proxy_group=993 > --log-file=neutron-ns-metadata-proxy-c4731392-9b91-4663-adb3-b10b5ebcc4f1.log > --log-dir=/var/log/neutron > > > > > > On queens like this: > > > haproxy -f > /var/lib/neutron/ns-metadata-proxy/e8ba8c09-a7dc-4a22-876e-b8d4187a23fe.conf > > > > > > Is it the correct behaviour ? > > > > Yes, that is correct. It was changed some time ago, see > https://bugs.launchpad.net/neutron/+bug/1524916 > > > > > > > > Regards > > > Ignazio > > > > > > > > > > > > Il giorno lun 12 nov 2018 alle ore 21:37 Slawomir Kaplonski < > skapl...@redhat.com> ha scritto: > > > Hi, > > > > > > Can You share logs from Your haproxy-metadata-proxy service which is > running in qdhcp namespace? There should be some info about reason of those > errors 500. > > > > > > > Wiadomość napisana przez Ignazio Cassano <ignaziocass...@gmail.com> > w dniu 12.11.2018, o godz. 19:49: > > > > > > > > Hi All, > > > > I upgraded manually my centos 7 openstack ocata to pike. > > > > All worked fine. > > > > Then I upgraded from pike to Queens and instances stopped to reach > metadata on 169.254.169.254 with error 500. > > > > I am using isolated metadata true in my dhcp conf and in dhcp > namespace the port 80 is in listen. > > > > Please, anyone can help me? > > > > Regards > > > > Ignazio > > > > > > > > _______________________________________________ > > > > OpenStack-operators mailing list > > > > OpenStack-operators@lists.openstack.org > > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > — > > > Slawek Kaplonski > > > Senior software engineer > > > Red Hat > > > > > > > — > > Slawek Kaplonski > > Senior software engineer > > Red Hat > > > > — > Slawek Kaplonski > Senior software engineer > Red Hat > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
