← Back to team overview

openstack team mailing list archive

Re: Grizzly G3+RC1 - Quantum DHCP problem...

 

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 20:09, Martinx - ジェームズ <thiagocmartinsc@xxxxxxxxx> wrote:

> Guys,
>
>  My /var/log/quantum/dhcp-agent.log file shows:
>
> 2013-03-19 20:04:48    DEBUG [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-b7a0-94eee95f5f91.pid',
> '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91',
> '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug',
> '--verbose',
> '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log',
> '--log-dir=/var/log/quantum']
> 2013-03-19 20:04:48    DEBUG [quantum.agent.linux.utils]
> 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-b7a0-94eee95f5f91.pid',
> '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91',
> '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug',
> '--verbose',
> '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log',
> '--log-dir=/var/log/quantum']
> Exit code: 1
> Stdout: ''
> Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: 3 incorrect password attempts\n'
> 2013-03-19 20:04:48    ERROR [quantum.agent.dhcp_agent] Unable to sync
> network state.
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py",
> line 154, in sync_state
>     self.refresh_dhcp_helper(network_id)
>   File "/usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py",
> line 208, in refresh_dhcp_helper
>     return self.enable_dhcp_helper(network_id)
>   File "/usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py",
> line 187, in enable_dhcp_helper
>     self.enable_isolated_metadata_proxy(network)
>   File "/usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py",
> line 321, in enable_isolated_metadata_proxy
>     pm.enable(callback)
>   File
> "/usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py",
> line 55, in enable
>     ip_wrapper.netns.execute(cmd)
>   File "/usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py",
> line 407, in execute
>     check_exit_code=check_exit_code)
>   File "/usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py",
> line 61, in execute
>     raise RuntimeError(m)
> RuntimeError:
>  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-b7a0-94eee95f5f91.pid',
> '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91',
> '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug',
> '--verbose',
> '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log',
> '--log-dir=/var/log/quantum']
> Exit code: 1
> Stdout: ''
> Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: no tty present and no askpass program specified\nSorry, try
> again.\nsudo: 3 incorrect password attempts\n'
>
>  Tips?
>
>  It is a fresh installation to test Grizzly...
>
>  I'm not using GRE or L3, only Quantum Single FLAT... With Folsom and
> previous Grizzly my Quantum was fine...
>
>  quantum-dhcp-agent
> 1:2013.1+git201303190501~precise-0ubuntu1
>
> Tks,
> Thiago
>

References