Re: [Openstack] 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 - ジェームズ thiagocmarti...@gmail.com wrote: 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-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:48DEBUG [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:48ERROR [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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 secure_path=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on #include directives: #includedir /etc/sudoers.d --- My /etc/sudoers.d/cinder_sudoers --- Defaults:cinder !requiretty cinder ALL = (root) NOPASSWD: /usr/bin/cinder-rootwrap --- My /etc/sudoers.d/nova_sudoers --- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap --- My /etc/sudoers.d/quantum_sudoers --- Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap --- Tks, Thiago On 20 March 2013 15:41, Leandro Reox leandro.r...@mercadolibre.com wrote: Please paste all your sudoers files ** * * *Leandro Reox * *#melicloud CloudBuilders* *Arias 3751, Piso 7 (C1430CRG) * *Ciudad de Buenos Aires - Argentina* *Cel: +549(11) 15-3770-1938* *Tel : +54(11) 4640-8726* On Wed, Mar 20, 2013 at 3:35 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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:48ERROR [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
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
What about adding: Defaults:ALL !requiretty in /etc/sudoers? Just to check Cheers On Wed, Mar 20, 2013 at 3:54 PM, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: 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 secure_path=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on #include directives: #includedir /etc/sudoers.d --- My /etc/sudoers.d/cinder_sudoers --- Defaults:cinder !requiretty cinder ALL = (root) NOPASSWD: /usr/bin/cinder-rootwrap --- My /etc/sudoers.d/nova_sudoers --- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap --- My /etc/sudoers.d/quantum_sudoers --- Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap --- Tks, Thiago On 20 March 2013 15:41, Leandro Reox leandro.r...@mercadolibre.comwrote: Please paste all your sudoers files ** * * *Leandro Reox * *#melicloud CloudBuilders* *Arias 3751, Piso 7 (C1430CRG) * *Ciudad de Buenos Aires - Argentina* *Cel: +549(11) 15-3770-1938* *Tel : +54(11) 4640-8726* On Wed, Mar 20, 2013 at 3:35 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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:48ERROR [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',
[Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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-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:48DEBUG [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:48ERROR [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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 - ジェームズ thiagocmarti...@gmail.com wrote: 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-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:48DEBUG [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:48ERROR [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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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', '/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports', 'br-int'] Exit code: 242 Stdout: '' Stderr: '' Don't know how to fix it... Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.com 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 - ジェームズ thiagocmarti...@gmail.com wrote: 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-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:48DEBUG [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:48ERROR [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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 - ジェームズ thiagocmarti...@gmail.com 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 - ジェームズ thiagocmarti...@gmail.com wrote: 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-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:48DEBUG [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:48ERROR [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',
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 http://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 - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com 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 - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com wrote: 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-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:48DEBUG [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:48ERROR [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
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 gong...@linux.vnet.ibm.com 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 - ジェームズ thiagocmarti...@gmail.com 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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:48ERROR [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
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com 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 http://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 - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com 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 - ジェームズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com 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,
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.com 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 gong...@linux.vnet.ibm.comwrote: 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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:48ERROR [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,
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 - ジェ�`ムズ thiagocmarti...@gmail.com User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.comwrote: 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 gong...@linux.vnet.ibm.comwrote: 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 - ジェ�`ムズ thiagocmarti...@gmail.comwrote: 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 - ジェ�`ムズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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:48ERROR [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
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 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 - ジェ�`ムズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com 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 gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com 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 http://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 - ジェ�`ムズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com 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 - ジェ�`ムズ thiagocmarti...@gmail.com mailto:thiagocmarti...@gmail.com 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',
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
i mean VMs traffic can though different dhcpl3 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 gong...@linux.vnet.ibm.com 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 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 - ジェ�`ムズ thiagocmarti...@gmail.com User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.comwrote: 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 gong...@linux.vnet.ibm.comwrote: 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 - ジェ�`ムズ thiagocmarti...@gmail.comwrote: 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 - ジェ�`ムズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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'
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
https://blueprints.launchpad.net/quantum/+spec/quantum-multihost it'r very cool. 2013/3/20 tommy(小包) bychya...@gmail.com i mean VMs traffic can though different dhcpl3 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 gong...@linux.vnet.ibm.com 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 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 - ジェ�`ムズ thiagocmarti...@gmail.com User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.comwrote: 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 gong...@linux.vnet.ibm.comwrote: 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 - ジェ�`ムズ thiagocmarti...@gmail.comwrote: 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 - ジェ�`ムズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
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 something missing with sudo... Tks, Thiago On 19 March 2013 22:52, Martinx - ジェームズ thiagocmarti...@gmail.com 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 gong...@linux.vnet.ibm.comwrote: 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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 - ジェームズ thiagocmarti...@gmail.comwrote: 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-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:48DEBUG [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:48ERROR [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
