← Back to team overview

openstack team mailing list archive

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

 

User "quantum" running `python /usr/bin/quantum-dhcp-agent'...


On 19 March 2013 22:55, gong yong sheng <gongysh@xxxxxxxxxxxxxxxxxx> 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
>
>  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 <gongysh@xxxxxxxxxxxxxxxxxx>wrote:
>
>>  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 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/quantum/dhcp-agent.log:
>>
>>  ---
>> ...
>> 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'
>> ---
>>
>>   I tried everything I could... But this message persist...
>>
>>   The namespaces are enabled, look:
>>
>>   ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r
>> 10.33.14.0/24 dev tapeb27823a-5e  proto kernel  scope link  src
>> 10.33.14.2
>>
>>   What can I do?
>>
>>  Tks,
>> Thiago
>>
>>
>> On 19 March 2013 20:35, Martinx - ジェームズ <thiagocmartinsc@xxxxxxxxx>wrote:
>>
>>>  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, without disabling namespaces explicitly...
>>>
>>>   If I add the Instance IP by hand, I can reach the Internet / gateway
>>> from it.
>>>
>>>   I'm finishing my Grizzly Quantum Single Flat PoC environment,
>>> planning to publish a nice guide soon!
>>>
>>>   I appreciate any help!
>>>
>>>  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
>>>>
>>>
>>>
>>
>>
>>  _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>
>

Follow ups

References