9:06 a.m.
When I am starting a VM, it is not able to connect to the metadata service.
My layout is a three node setup, with a controller (where the metadata
service is), a network node, and a compute node.
The VM is starting and getting a IP address from the nova network service
on the network node. While watching the VM start, it then tries to connect
to the metadata on the 169.254.169.254 address. After a bit it switches to
10.34.106.1 address, which is our privet address space for the VMs.
Has anyone seen this problem before?
--Brian
10:05 a.m.
Packstack does 3 node RDO Kilo deployment with no problems. See for instance ( case CentOS
7.1) :-
http://bderzhavets.blogspot.com/2015/05/rdo-kilo-set-up-three-kvms-nodes....
as well as on Fedora 22
http://bderzhavets.blogspot.com/2015/08/rdo-kilo-set-up-for-three-fedora-...
Could you ,please, upload somewhere your answer-file
Boris.
Date: Thu, 13 Aug 2015 09:06:34 -0500
From: brian(a)brianlee.org
To: rdo-list(a)redhat.com
Subject: [Rdo-list] Unable to access metadata service
When I am starting a VM, it is not able to connect to the metadata service. My layout is a
three node setup, with a controller (where the metadata service is), a network node, and a
compute node.
The VM is starting and getting a IP address from the nova network service on the network
node. While watching the VM start, it then tries to connect to the metadata on the
169.254.169.254 address. After a bit it switches to 10.34.106.1 address, which is our
privet address space for the VMs.
Has anyone seen this problem before?--Brian
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
10:16 a.m.
Sorry I should have said this in the first email, I am using nova
networking for this setup. The error that I shows when the VM is boot is:
unexpected error ['ConnectionError' object has no arrribute 'response']
--Brian
On Thu, Aug 13, 2015 at 10:05 AM, Boris Derzhavets <bderzhavets(a)hotmail.com>
wrote:
Packstack does 3 node RDO Kilo deployment with no problems. See for
instance ( case CentOS 7.1) :-
http://bderzhavets.blogspot.com/2015/05/rdo-kilo-set-up-three-kvms-nodes....
as well as on Fedora 22
http://bderzhavets.blogspot.com/2015/08/rdo-kilo-set-up-for-three-fedora-...
Could you ,please, upload somewhere your answer-file
Boris.
------------------------------
Date: Thu, 13 Aug 2015 09:06:34 -0500
From: brian(a)brianlee.org
To: rdo-list(a)redhat.com
Subject: [Rdo-list] Unable to access metadata service
When I am starting a VM, it is not able to connect to the metadata
service. My layout is a three node setup, with a controller (where the
metadata service is), a network node, and a compute node.
The VM is starting and getting a IP address from the nova network service
on the network node. While watching the VM start, it then tries to connect
to the metadata on the 169.254.169.254 address. After a bit it switches to
10.34.106.1 address, which is our privet address space for the VMs.
Has anyone seen this problem before?
--Brian
_______________________________________________ Rdo-list mailing list
Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To
unsubscribe: rdo-list-unsubscribe(a)redhat.com
10:26 a.m.
Date: Thu, 13 Aug 2015 10:16:00 -0500
Subject: Re: [Rdo-list] Unable to access metadata service
From: brian(a)brianlee.org
To: bderzhavets(a)hotmail.com
CC: rdo-list(a)redhat.com
Sorry I should have said this in the first email, I am using nova
networking for this setup.
I guess nova network was deprecated in RDO releases a while ago. I believe in Havana or
IceHouse.
If I am wrong about that. Somebody will correct me here.
I just advise you to activate Neutron networking (L2 , L3 layers + Neutron routers).
Samples of standard answer-files along with picture explains architecture in general may
be
found in links provided.
Boris.
The error that I shows when the VM is boot is: > unexpected error
['ConnectionError' object has no arrribute 'response']
--Brian
On Thu, Aug 13, 2015 at 10:05 AM, Boris Derzhavets <bderzhavets(a)hotmail.com> wrote:
Packstack does 3 node RDO Kilo deployment with no problems. See for instance ( case CentOS
7.1) :-
http://bderzhavets.blogspot.com/2015/05/rdo-kilo-set-up-three-kvms-nodes....
as well as on Fedora 22
http://bderzhavets.blogspot.com/2015/08/rdo-kilo-set-up-for-three-fedora-...
Could you ,please, upload somewhere your answer-file
Boris.
Date: Thu, 13 Aug 2015 09:06:34 -0500
From: brian(a)brianlee.org
To: rdo-list(a)redhat.com
Subject: [Rdo-list] Unable to access metadata service
When I am starting a VM, it is not able to connect to the metadata service. My layout is a
three node setup, with a controller (where the metadata service is), a network node, and a
compute node.
The VM is starting and getting a IP address from the nova network service on the network
node. While watching the VM start, it then tries to connect to the metadata on the
169.254.169.254 address. After a bit it switches to 10.34.106.1 address, which is our
privet address space for the VMs.
Has anyone seen this problem before?--Brian
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
2:18 a.m.
On 13/08/15 17:16, brian lee wrote:
Sorry I should have said this in the first email, I am using nova
networking for this setup. The error that I shows when the VM is boot is:
unexpected error ['ConnectionError' object has no arrribute 'response']
this rings a bell for me. I used such a setup in Juno and had to toggle
service_metadata_proxy
in /etc/nova/nova.conf.
As far as I remember, this didn't work for me in Kilo any more, thus I
switched to neutron.
Matthias
9:12 a.m.
I figured it out. On the controller node I had to add a route to the
network node for the private IP addresses. When the metadata request is
sent, it does not NAT the address because the metadata service needs to
know the IP. Once I put that route in place it started to work.
--Brian
On Fri, Aug 14, 2015 at 2:18 AM, Matthias Runge <mrunge(a)redhat.com> wrote:
On 13/08/15 17:16, brian lee wrote:
> Sorry I should have said this in the first email, I am using nova
> networking for this setup. The error that I shows when the VM is boot is:
> unexpected error ['ConnectionError' object has no arrribute
'response']
>
>
>
this rings a bell for me. I used such a setup in Juno and had to toggle
service_metadata_proxy
in /etc/nova/nova.conf.
As far as I remember, this didn't work for me in Kilo any more, thus I
switched to neutron.
Matthias
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
7:50 a.m.
On 8/14/2015 10:12, brian lee wrote:
I figured it out. On the controller node I had to add a route to the
network node for the private IP addresses. When the metadata request
is sent, it does not NAT the address because the metadata service
needs to know the IP. Once I put that route in place it started to work.
Can you link the guide in the docs (if any) that you followed? If it's
not there, a bug should be filed. Others probably will bump into the
same issue.
Regards,
Daniel Speichert
10:16 a.m.
Date: Thu, 13 Aug 2015 09:06:34 -0500
From: brian(a)brianlee.org
To: rdo-list(a)redhat.com
Subject: [Rdo-list] Unable to access metadata service
When I am starting a VM, it is not able to connect to the metadata service. My layout is a
three node setup, with a controller (where the metadata service is), a network node, and a
compute node.
The VM is starting and getting a IP address from ==> the nova network service on the
network node.
Are you using Nova Network or Neutron (L2,L3 layers with router) ?
Boris.
While watching the VM start, it then tries to connect to the metadata on the
169.254.169.254 address. After a bit it switches to 10.34.106.1 address, which is our
privet address space for the VMs.
Has anyone seen this problem before?--Brian
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
3373
days inactive
3384
days old
7 comments
4 participants
participants (4)
-
Boris Derzhavets -
brian lee -
Daniel Speichert -
Matthias Runge