Doesn't work but, now it is working better, no more errors at
dhcp-agent.log, I did:
visudo
---
quantum ALL=NOPASSWD: ALL
cinder ALL=NOPASSWD: ALL
nova ALL=NOPASSWD: ALL
---
Something goes wrong I enable `includedir /etc/sudoers.d' within
`/etc/sudores'...
I don't know if it is related but, my
What about adding:
Defaults:ALL !requiretty
in /etc/sudoers?
Just to check
Cheers
On Wed, Mar 20, 2013 at 3:54 PM, Martinx - ジェームズ
wrote:
> Leandro!
>
>
> My /etc/sudoers:
> ---
> #
> # This file MUST be edited with the 'visudo' command as root.
> #
> # Please consider adding local content i
Leandro!
My /etc/sudoers:
---
#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults env_reset
Defaults
secur
Guys,
This problem still persist... I tried everything...
Here is more error message from dhcp-agent.log:
http://paste.openstack.org/show/34167/
I really need help to fix this... It is a fresh installation of Grizzly
G3+RC1 from PPA, Ubuntu 12.04.2 64 bits...
Tks!
Thiago
On 19 March 2013
Also, my file `/etc/sudoers.d/quantum_sudoers' contains:
---
Defaults:quantum !requiretty
quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap
---
The error "sudo: no tty present and no askpass program specified" at
`/var/log/quantum/dhcp-agent.log' persist... :-/
I don't think it is some
https://blueprints.launchpad.net/quantum/+spec/quantum-multihost
it'r very cool.
2013/3/20 tommy(小包)
> i mean VMs traffic can though different dhcp&l3 agent(like loadbancing)
>
> https://review.openstack.org/#/c/24771/
> Application Error
> The page you requested was not found, or you do not h
i mean VMs traffic can though different dhcp&l3 agent(like loadbancing)
https://review.openstack.org/#/c/24771/
Application Error
The page you requested was not found, or you do not have permission to view
this page. f
Thanks,
Tommy
2013/3/20 gong yong sheng
> we can deploy many dhcp agents
we can deploy many dhcp agents and l3 agents.
for multihost, we are doing:
https://review.openstack.org/#/c/24771/
On 03/20/2013 10:13 AM, tommy(小包) wrote:
> i worry about performance of quantum use subnet in one dhcp & l3 agent
> work for it(more dhcp & l3 just for backup)
>
> if quantum have any
i worry about performance of quantum use subnet in one dhcp & l3 agent work
for it(more dhcp & l3 just for backup)
if quantum have any solution to performance about quantum dhcp & l3 (may be
one compute node have dhcp & l3 agent work for local VMs)
Thanks,
Tommy
2013/3/20 Martinx - ジェ�`ムズ
>
User "quantum" running `python /usr/bin/quantum-dhcp-agent'...
On 19 March 2013 22:55, gong yong sheng wrote:
> that depends what user is running the dhcp agent.
>
> On 03/20/2013 09:52 AM, Martinx - ジェームズ wrote:
>
> My /etc/sudoers.d/nova_sudoers contains:
>
> --
> Defaults:nova !requiretty
that depends what user is running the dhcp agent.
On 03/20/2013 09:52 AM, Martinx - ジェームズ wrote:
My /etc/sudoers.d/nova_sudoers contains:
--
Defaults:nova !requiretty
nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap
--
Do I need to change it?
Tks!
Thiago
On 19 March 2013 22:46, gong yong
My /etc/sudoers.d/nova_sudoers contains:
--
Defaults:nova !requiretty
nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap
--
Do I need to change it?
Tks!
Thiago
On 19 March 2013 22:46, gong yong sheng wrote:
> It seems be about sudo.
> to create one sudo file under /etc/sudoers.d
> mine is:
It seems be about sudo.
to create one sudo file under /etc/sudoers.d
mine is: nova_sudoers:
Defaults:gongysh !requiretty
gongysh ALL = (ALL) NOPASSWD: ALL
On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote:
Hi!
I just rollback to the default namespace options, my Instance now get
its IP without pro
Hi!
I just rollback to the default namespace options, my Instance now get its
IP without problem.
But, the message from my first e-mail on this thread, still persist...
I tried to enable quantum metadata proxy stuff but, nothing changes...
The following error keeps rolling at my /var/log/quantu
Also, my compute quantum node shows:
/var/log/quantum/openvswitch-agent.log:
Exit code: 242
Stdout: ''
Stderr: ''
2013-03-19 20:25:31ERROR [quantum.agent.linux.ovs_lib] Unable to
execute ['ovs-vsctl', '--timeout=2', 'list-ports', 'br-int']. Exception:
Command: ['sudo', 'quantum-rootwrap', '/e
After disabling namespaces, with:
`allow_overlapping_ips = False' in quantum.conf
and with:
`use_namespaces = False' in /etc/quantum/dhcp_agent.ini
The previous error message dissapear but, My Instance isn't getting its IP
via DHCP now... Weird thing is that it was working couple minutes ago,
Guys,
My /var/log/quantum/dhcp-agent.log file shows:
2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command:
['sudo', 'ip', 'netns', 'exec',
'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy',
'--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-
17 matches
Mail list logo
