Hi Chris,
many thanks for your answer.
It solved the issue.
Regards
Ignazio
Il giorno mar 13 nov 2018 alle ore 03:46 Chris Apsey <
bitskr...@bitskrieg.net> ha scritto:
> Did you change the nova_metadata_ip option to nova_metadata_host in
> metadata_agent.ini? The former value was deprecated
Hello, I am going to check it.
Thanks
Ignazio
Il giorno Mar 13 Nov 2018 03:46 Chris Apsey ha
scritto:
> Did you change the nova_metadata_ip option to nova_metadata_host in
> metadata_agent.ini? The former value was deprecated several releases ago
> and now no longer functions as of pike. The
Did you change the nova_metadata_ip option to nova_metadata_host in
metadata_agent.ini? The former value was deprecated several releases ago
and now no longer functions as of pike. The metadata service will throw
500 errors if you don't change it.
On November 12, 2018 19:00:46 Ignazio
Any other suggestion ?
It does not work.
Nova metatada is on port 8775 in listen but no way to solve this issue.
Thanks
Ignazio
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
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 w
> dniu 12.11.2018, o godz. 22:55:
> >
> > Hello,
> > the
I tried 1 minute ago to create another instance.
Nova api reports the following:
RROR oslo_db.sqlalchemy.engines [req-cac96dee-d91b-48cb-831b-31f95cffa2f4
89f76bc5de5545f381da2c10c7df7f15 59f1f232ce28409593d66d8f6495e434 - default
default] Database connection was found disconnected;
Hi,
> Wiadomość napisana przez Ignazio Cassano 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
Hello again, ath the same time I tried to create an instance nova-api log
reports:
2018-11-12 21:30:42.225 4226 ERROR oslo_db.sqlalchemy.engines
[req-e4799f40-eeab-482d-9717-cb41be8ffde2 89f76bc5de5545f381da2c10c7df7f15
59f1f232ce28409593d66d8f6495e434 - default default] Database connection was
Hello,
the nova api in on the same controller on port 8774 and it can be reached
from the metadata agent
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
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 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
PS
Thanks for your help
Il giorno lun 12 nov 2018 alle ore 22:15 Ignazio Cassano <
ignaziocass...@gmail.com> ha scritto:
> Hello,
> attached here there is the log file.
>
> Connecting to an instance created befor upgrade I also tried:
> wget
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 w dniu
> 12.11.2018, o godz. 19:49:
>
> Hi All,
> I upgraded manually my centos 7
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.
14 matches
Mail list logo
