On 07-09-2015 10:29, Eren Türkay wrote:
> I am still stuck at this problem. Has anyone experienced it? I would be really
> happy if someone can give a tip regarding to the issue.
Hello all,
Sorry for the inconvenience. I misinterpreted the actual error. Instances could
reach to the namespace and
On 07-09-2015 11:52, Ihar Hrachyshka wrote:
> See metadata_access_mark option in etc/l3_agent.ini
Hello,
This option is set 0x1 by default. The debug log prints:
metadata_access_mark = 0x1
Should I change this value to another one?
--
Eren Türkay, System Administrator
https://skyatl
> On 07 Sep 2015, at 09:29, Eren Türkay wrote:
>
> On 31-08-2015 14:56, Eren Türkay wrote:
>> Hello,
>
> Hello agiain,
>
>> I installed Kilo neutron. I can create networks, namespaces are created and
>> neutron-ns-metadata-proxy is running. However, VM's cannot get SSH keys. I've
>> isolated th
On 31-08-2015 14:56, Eren Türkay wrote:
> Hello,
Hello agiain,
> I installed Kilo neutron. I can create networks, namespaces are created and
> neutron-ns-metadata-proxy is running. However, VM's cannot get SSH keys. I've
> isolated the problem down the network namespace and a particular iptables
