Hi Mohammad, On Thu, Jan 19, 2012 at 5:49 PM, Mohammad Banikazemi <m...@us.ibm.com> wrote: > Is there a requirement to use DHCP with quantum?
Nope. Quantum should work fine with or without DHCP. Even when I do not specify > the "--quantum_use_dhcp" flag, my vm which gets spawned successfully (and an > IP address is assigned to it and it's /etc/network/interfaces gets created > to use that IP address) tries to get its IP address using udhcpc but fails > and does not get an IP address (ipv4 address that is). I would guess that whether the VM issues DHCP queries when it boots is a property of disk image you select. I'm not super familiar with the net-injection code though, so perhaps that code will sometimes determine whether DHCP is used by manipulating /etc/network/interfaces. I see exactly the > same thing happening when I specify the "--quantum_use_dhcp" flag. > Any suggestions as to what I may be doing incorrectly? Why dhcp is used > without the "--quantum_use_dhcp" flag, and why dhcp server does not respond > even when the "--quantum_use_dhcp" flag is specified. I am using a single > node install with devstack. The quantum_use_dhcp flag currently only controls whether a DHCP server is attached to each L2 network. QuantumManager currently always defaults to setting 'injected' to true on a network (we should probably have a separate flag for this, or borrow the flat_injected flag... that has been on my TODO list for a while). If you have --quantum_use_dhcp set, and you are not getting responses to DHCP queries, there's probably something else wrong with the base connectivity in your setup (I would look through logs for nova-network, quantum, and the quantum agent). Dan > Thanks. > > > > ... > ... > > info: initramfs: up at 0.63 > [ 0.664224] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 > info: copying initramfs to /dev/vda > info: initramfs loading root from /dev/vda > info: /etc/init.d/rc.sysinit: up at 2.04 > Starting logging: OK > Initializing random number generator... done. > Starting network... > udhcpc (v1.18.5) started > Sending discover... > Sending discover... > Sending discover... > No lease, failing > WARN: /etc/rc3.d/S40-network failed > cloud-setup: checking > http://169.254.169.254/2009-04-04/meta-data/instance-id > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 1/30: up 11.21. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 2/30: up 12.22. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 3/30: up 13.23. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 4/30: up 14.24. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 5/30: up 15.25. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 6/30: up 16.25. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 7/30: up 17.26. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 8/30: up 18.27. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 9/30: up 19.28. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 10/30: up 20.28. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 11/30: up 21.29. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 12/30: up 22.30. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 13/30: up 23.30. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 14/30: up 24.31. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 15/30: up 25.32. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 16/30: up 26.33. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 17/30: up 27.33. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 18/30: up 28.34. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 19/30: up 29.35. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 20/30: up 30.35. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 21/30: up 31.36. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 22/30: up 32.37. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 23/30: up 33.38. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 24/30: up 34.38. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 25/30: up 35.39. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 26/30: up 36.40. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 27/30: up 37.41. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 28/30: up 38.41. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 29/30: up 39.42. request failed > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-setup: failed 30/30: up 40.43. request failed > cloud-setup: after 30 fails, debugging > cloud-setup: running debug (30 tries reached) > ############ debug start ############## > ### /etc/rc.d/init.d/sshd start > /etc/rc3.d/S45-cloud-setup: line 66: /etc/rc.d/init.d/sshd: not found > route: fscanf > ### ifconfig -a > eth0 Link encap:Ethernet HWaddr 02:16:3E:66:2C:7F > inet6 addr: fe80::16:3eff:fe66:2c7f/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:1434 (1.4 KiB) > Interrupt:11 Base address:0xa000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > ### route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > route: fscanf > ### cat /etc/resolv.conf > cat: can't open '/etc/resolv.conf': No such file or directory > ### gateway not found > /etc/rc3.d/S45-cloud-setup: line 66: can't open /etc/resolv.conf: no such > file > ### pinging nameservers > ### uname -a > Linux cirros 3.0.0-12-virtual #20-Ubuntu SMP Fri Oct 7 18:19:02 UTC 2011 > x86_64 GNU/Linux > ### lsmod > Module Size Used by Not tainted > vfat 17585 0 > fat 61475 1 vfat > isofs 40253 0 > ip_tables 27473 0 > x_tables 29846 1 ip_tables > pcnet32 42078 0 > 8139cp 27412 0 > ne2k_pci 13691 0 > 8390 18856 1 ne2k_pci > e1000 108573 0 > acpiphp 24080 0 > ### dmesg | tail > [ 0.690966] kjournald starting. Commit interval 5 seconds > [ 0.690982] EXT3-fs (vda): mounted filesystem with ordered data mode > [ 0.703180] EXT3-fs: barriers not enabled > [ 0.703298] kjournald starting. Commit interval 5 seconds > [ 0.706462] EXT3-fs (vda): using internal journal > [ 0.706468] EXT3-fs (vda): mounted filesystem with ordered data mode > [ 1.353050] Refined TSC clocksource calibration: 2931.842 MHz. > [ 2.049597] EXT3-fs (vda): using internal journal > [ 2.180522] 8139cp 0000:00:03.0: eth0: link up, 100Mbps, full-duplex, lpa > 0x05E1 > [ 12.256052] eth0: no IPv6 routers present > ### tail -n 25 /var/log/messages > Jan 19 12:54:24 cirros kern.info kernel: [ 0.000000] KERNEL supported > cpus: > Jan 19 12:54:24 cirros kern.info kernel: [ 0.000000] Intel GenuineIntel > Jan 19 12:54:24 cirros kern.info kernel: [ 0.000000] AMD AuthenticAMD > Jan 19 12:54:24 cirros kern.info kernel: [ 0.000000] Centaur > CentaurHauls > Jan 19 12:54:24 cirros kern.info kernel: [ 0.000000] BIOS-provided > physical RAM map: > Jan 19 12:54:24 cirros kern.info kernel: [ 0.000000] BIOS-e820: > 0000000000000000 - 000000000009dc00 (usable) > Jan 19 12:54:24 cirros kern.info kernel: [ 0.660038] ne2k-pci.c:v1.03 > 9/22/2003 D. Becker/P. Gortmaker > Jan 19 12:54:24 cirros kern.info kernel: [ 0.663940] 8139cp: 8139cp: > 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) > Jan 19 12:54:24 cirros kern.warn kernel: [ 0.664224] ACPI: PCI Interrupt > Link [LNKC] enabled at IRQ 11 > Jan 19 12:54:24 cirros kern.info kernel: [ 0.665091] 8139cp 0000:00:03.0: > PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 > Jan 19 12:54:24 cirros kern.info kernel: [ 0.668545] 8139cp 0000:00:03.0: > eth0: RTL-8139C+ at 0xffffc9000015a000, 02:16:3e:66:2c:7f, IRQ 11 > Jan 19 12:54:24 cirros kern.debug kernel: [ 0.668577] 8139cp > 0000:00:03.0: setting latency timer to 64 > Jan 19 12:54:24 cirros kern.info kernel: [ 0.672910] pcnet32: > pcnet32.c:v1.35 21.Apr.2008 tsbog...@alpha.franken.de > Jan 19 12:54:24 cirros kern.info kernel: [ 0.677414] ip_tables: (C) > 2000-2006 Netfilter Core Team > Jan 19 12:54:24 cirros kern.info kernel: [ 0.690817] EXT3-fs: barriers > not enabled > Jan 19 12:54:24 cirros kern.info kernel: [ 0.690966] kjournald starting. > Commit interval 5 seconds > Jan 19 12:54:24 cirros kern.info kernel: [ 0.690982] EXT3-fs (vda): > mounted filesystem with ordered data mode > Jan 19 12:54:24 cirros kern.info kernel: [ 0.703180] EXT3-fs: barriers > not enabled > Jan 19 12:54:24 cirros kern.info kernel: [ 0.703298] kjournald starting. > Commit interval 5 seconds > Jan 19 12:54:24 cirros kern.info kernel: [ 0.706462] EXT3-fs (vda): using > internal journal > Jan 19 12:54:24 cirros kern.info kernel: [ 0.706468] EXT3-fs (vda): > mounted filesystem with ordered data mode > Jan 19 12:54:24 cirros kern.info kernel: [ 1.353050] Refined TSC > clocksource calibration: 2931.842 MHz. > Jan 19 12:54:24 cirros kern.info kernel: [ 2.049597] EXT3-fs (vda): using > internal journal > Jan 19 12:54:24 cirros kern.info kernel: [ 2.180522] 8139cp 0000:00:03.0: > eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 > Jan 19 12:54:34 cirros kern.debug kernel: [ 12.256052] eth0: no IPv6 > routers present > ############ debug end ############## > cloud-setup: failed to read iid from metadata. tried 30 > WARN: /etc/rc3.d/S45-cloud-setup failed > Starting dropbear sshd: generating rsa key... generating dsa key... OK > ===== cloud-final: system completely up in 41.89 seconds ==== > wget: can't connect to remote host (169.254.169.254): Network is unreachable > wget: can't connect to remote host (169.254.169.254): Network is unreachable > wget: can't connect to remote host (169.254.169.254): Network is unreachable > instance-id: > public-ipv4: > local-ipv4 : > wget: can't connect to remote host (169.254.169.254): Network is unreachable > cloud-userdata: failed to read instance id > WARN: /etc/rc3.d/S99-cloud-userdata failed > ____ ____ ____ > / __/ __ ____ ____ / __ \/ __/ > / /__ / // __// __// /_/ /\ \ > \___//_//_/ /_/ \____/___/ > http://launchpad.net/cirros > > > > login as 'cirros' user. default password: 'cubswin:)'. use 'sudo' for root. > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp