the exec needs root perms. just add a sudo and you should be good.
jason@devstack:~$ ip netns list
qdhcp-c6333eca-6fe4-40af-ad61-c1435a4701ef
qrouter-840c0ae7-ef5b-4be2-b496-b8a53080976b
jason@devstack:~$ ip netns exec
qrouter-840c0ae7-ef5b-4be2-b496-b8a53080976b ping 10.0.0.1
seting the ne
Hi Frank, I have to say ownCloud is really nicely done. i have been in
need of a file share which has native linux client support and a really
robust storage backend. ownCloud with swift meets the requirements. I do
have a comment which mirrors Hugo's comments I think. Is it feasible to
have th
that happened to me too. maybe same root cause?
see http://ubuntuforums.org/showthread.php?t=2223789
cheers
jason
On Mon, May 19, 2014 at 10:59 PM, Martinx - ジェームズ wrote:
> I managed to login into a Ubuntu Instance via `SPICE Console` and there is
> more network outages from within it, take
I had same symptom (trusty/icehouse). hitting metadata via the 169 address
generated the same error. I turned on debug for metadata service and found
I had my auth_url pointing to wrong place in metadata_agent.ini. I suspect
you have checked all of these things already. If you suspect v4/v6 pro
