Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Ubuntu 14.04 won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

Thanks, Marc

Ubuntu 14.04 won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

This is nova-compute.log from that the time that it is launched until it hangs:

2014-06-06 14:32:14.571 2019 AUDIT nova.compute.manager [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Starting instance...
2014-06-06 14:32:14.680 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Attempting claim: memory 4096 MB, disk 40 GB, VCPUs 2
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total memory: 32127 MB, used: 512.00 MB
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] memory limit: 48190.50 MB, free: 47678.50 MB
2014-06-06 14:32:14.682 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total disk: 426 GB, used: 0.00 GB
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] disk limit not specified, defaulting to unlimited
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total CPUs: 24 VCPUs, used: 0.00 VCPUs
2014-06-06 14:32:14.684 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] CPUs limit not specified, defaulting to unlimited
2014-06-06 14:32:14.685 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Claim successful
2014-06-06 14:32:15.374 2019 INFO nova.virt.libvirt.driver [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Creating image
2014-06-06 14:32:15.575 2019 WARNING nova.virt.disk.vfs.guestfs [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-06 14:32:22.050 2019 INFO nova.virt.libvirt.driver [-] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Instance spawned successfully.
2014-06-06 14:32:35.106 2019 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2014-06-06 14:32:35.904 2019 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 27519
2014-06-06 14:32:35.905 2019 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 386
2014-06-06 14:32:35.906 2019 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22
2014-06-06 14:32:35.937 2019 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1.XXXXXXX.com

Thanks, Marc

Ubuntu 14.04 cloud image won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

This is nova-compute.log from that the time that it is launched until it hangs:

2014-06-06 14:32:14.571 2019 AUDIT nova.compute.manager [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Starting instance...
2014-06-06 14:32:14.680 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Attempting claim: memory 4096 MB, disk 40 GB, VCPUs 2
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total memory: 32127 MB, used: 512.00 MB
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] memory limit: 48190.50 MB, free: 47678.50 MB
2014-06-06 14:32:14.682 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total disk: 426 GB, used: 0.00 GB
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] disk limit not specified, defaulting to unlimited
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total CPUs: 24 VCPUs, used: 0.00 VCPUs
2014-06-06 14:32:14.684 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] CPUs limit not specified, defaulting to unlimited
2014-06-06 14:32:14.685 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Claim successful
2014-06-06 14:32:15.374 2019 INFO nova.virt.libvirt.driver [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Creating image
2014-06-06 14:32:15.575 2019 WARNING nova.virt.disk.vfs.guestfs [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-06 14:32:22.050 2019 INFO nova.virt.libvirt.driver [-] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Instance spawned successfully.
2014-06-06 14:32:35.106 2019 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2014-06-06 14:32:35.904 2019 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 27519
2014-06-06 14:32:35.905 2019 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 386
2014-06-06 14:32:35.906 2019 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22
2014-06-06 14:32:35.937 2019 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1.XXXXXXX.com

Thanks, Marc

Ubuntu 14.04 cloud image won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

This is nova-compute.log from that the time that it is launched until it hangs:

2014-06-06 14:32:14.571 2019 AUDIT nova.compute.manager [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Starting instance...
2014-06-06 14:32:14.680 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Attempting claim: memory 4096 MB, disk 40 GB, VCPUs 2
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total memory: 32127 MB, used: 512.00 MB
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] memory limit: 48190.50 MB, free: 47678.50 MB
2014-06-06 14:32:14.682 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total disk: 426 GB, used: 0.00 GB
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] disk limit not specified, defaulting to unlimited
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total CPUs: 24 VCPUs, used: 0.00 VCPUs
2014-06-06 14:32:14.684 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] CPUs limit not specified, defaulting to unlimited
2014-06-06 14:32:14.685 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Claim successful
2014-06-06 14:32:15.374 2019 INFO nova.virt.libvirt.driver [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Creating image
2014-06-06 14:32:15.575 2019 WARNING nova.virt.disk.vfs.guestfs [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-06 14:32:22.050 2019 INFO nova.virt.libvirt.driver [-] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Instance spawned successfully.
2014-06-06 14:32:35.106 2019 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2014-06-06 14:32:35.904 2019 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 27519
2014-06-06 14:32:35.905 2019 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 386
2014-06-06 14:32:35.906 2019 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22
2014-06-06 14:32:35.937 2019 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1.XXXXXXX.com

Thanks, Marc

Ubuntu 14.04 cloud image won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

Update:

I found this question which exihibited the same problem I'm having. However, I believe my metadata service is functioning properly as from a cirros instance I can curl http://169.254.169.254/ properly.

This is nova-compute.log from that the time that it is launched until it hangs:

2014-06-06 14:32:14.571 2019 AUDIT nova.compute.manager [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Starting instance...
2014-06-06 14:32:14.680 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Attempting claim: memory 4096 MB, disk 40 GB, VCPUs 2
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total memory: 32127 MB, used: 512.00 MB
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] memory limit: 48190.50 MB, free: 47678.50 MB
2014-06-06 14:32:14.682 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total disk: 426 GB, used: 0.00 GB
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] disk limit not specified, defaulting to unlimited
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total CPUs: 24 VCPUs, used: 0.00 VCPUs
2014-06-06 14:32:14.684 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] CPUs limit not specified, defaulting to unlimited
2014-06-06 14:32:14.685 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Claim successful
2014-06-06 14:32:15.374 2019 INFO nova.virt.libvirt.driver [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Creating image
2014-06-06 14:32:15.575 2019 WARNING nova.virt.disk.vfs.guestfs [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-06 14:32:22.050 2019 INFO nova.virt.libvirt.driver [-] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Instance spawned successfully.
2014-06-06 14:32:35.106 2019 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2014-06-06 14:32:35.904 2019 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 27519
2014-06-06 14:32:35.905 2019 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 386
2014-06-06 14:32:35.906 2019 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22
2014-06-06 14:32:35.937 2019 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1.XXXXXXX.com

Thanks, Marc

Ubuntu 14.04 cloud image won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

Update:Update 1:

I found this question which exihibited the same problem I'm having. However, I believe my metadata service is functioning properly as from a cirros instance I can curl http://169.254.169.254/ properly.

Update 2:

I finally found something! From a cirros instance I can query the metadata service:

$ curl http://169.254.169.254/2009-04-04/meta-data/placement/availability-zone
nova$

However, running the following query hangs forever:

$ curl http://169.254.169.254/openstack/2013-10-17/meta_data.json

Which is where I'm thinking the difference is between 14.04 and 12.04 or cirros. Is that an API that I don't have enabled?

This is nova-compute.log from that the time that it is launched until it hangs:

2014-06-06 14:32:14.571 2019 AUDIT nova.compute.manager [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Starting instance...
2014-06-06 14:32:14.680 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Attempting claim: memory 4096 MB, disk 40 GB, VCPUs 2
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total memory: 32127 MB, used: 512.00 MB
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] memory limit: 48190.50 MB, free: 47678.50 MB
2014-06-06 14:32:14.682 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total disk: 426 GB, used: 0.00 GB
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] disk limit not specified, defaulting to unlimited
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total CPUs: 24 VCPUs, used: 0.00 VCPUs
2014-06-06 14:32:14.684 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] CPUs limit not specified, defaulting to unlimited
2014-06-06 14:32:14.685 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Claim successful
2014-06-06 14:32:15.374 2019 INFO nova.virt.libvirt.driver [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Creating image
2014-06-06 14:32:15.575 2019 WARNING nova.virt.disk.vfs.guestfs [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-06 14:32:22.050 2019 INFO nova.virt.libvirt.driver [-] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Instance spawned successfully.
2014-06-06 14:32:35.106 2019 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2014-06-06 14:32:35.904 2019 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 27519
2014-06-06 14:32:35.905 2019 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 386
2014-06-06 14:32:35.906 2019 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22
2014-06-06 14:32:35.937 2019 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1.XXXXXXX.com

Thanks, Marc

Ubuntu 14.04 cloud image won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

Update 1:

I found this question which exihibited the same problem I'm having. However, I believe my metadata service is functioning properly as from a cirros instance I can curl http://169.254.169.254/ properly.

Update 2:

I finally found something! From a cirros instance I can query the metadata service:

$ curl http://169.254.169.254/2009-04-04/meta-data/placement/availability-zone
nova$

However, running the following query hangs forever:

$ curl http://169.254.169.254/openstack/2013-10-17/meta_data.json

Which is where I'm thinking the difference is between 14.04 and 12.04 or cirros. Is that an API that I don't have enabled?

This is nova-compute.log from that the time that it is launched until it hangs:

2014-06-06 14:32:14.571 2019 AUDIT nova.compute.manager [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Starting instance...
2014-06-06 14:32:14.680 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Attempting claim: memory 4096 MB, disk 40 GB, VCPUs 2
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total memory: 32127 MB, used: 512.00 MB
2014-06-06 14:32:14.681 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] memory limit: 48190.50 MB, free: 47678.50 MB
2014-06-06 14:32:14.682 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total disk: 426 GB, used: 0.00 GB
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] disk limit not specified, defaulting to unlimited
2014-06-06 14:32:14.683 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Total CPUs: 24 VCPUs, used: 0.00 VCPUs
2014-06-06 14:32:14.684 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] CPUs limit not specified, defaulting to unlimited
2014-06-06 14:32:14.685 2019 AUDIT nova.compute.claims [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Claim successful
2014-06-06 14:32:15.374 2019 INFO nova.virt.libvirt.driver [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Creating image
2014-06-06 14:32:15.575 2019 WARNING nova.virt.disk.vfs.guestfs [req-3af2489c-23ed-4b5e-9480-9a2ac2839270 b0e6759357334a92bd7a7cb4a7e23e0c 66904b47fddc4aeb95b973596467c596] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-06 14:32:22.050 2019 INFO nova.virt.libvirt.driver [-] [instance: 2cdf6990-b356-47c6-a7a8-bbf5ce34db7e] Instance spawned successfully.
2014-06-06 14:32:35.106 2019 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2014-06-06 14:32:35.904 2019 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 27519
2014-06-06 14:32:35.905 2019 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 386
2014-06-06 14:32:35.906 2019 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 22
2014-06-06 14:32:35.937 2019 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1.XXXXXXX.com

Thanks, Marc

Ubuntu 14.04 cloud image won't boot

I have a new Icehouse environment setup. I can't seem to boot any instances from the Ubuntu Server 14.04 cloud image. I am able to bring up CirrOS and 12.04 just fine. There's no error but it never gets past cloud-init:

Cloud-init v. 0.7.5 running 'init' at Thu, 05 Jun 2014 20:51:10 +0000. Up 7.76 seconds.
ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: |   lo   | True |  127.0.0.1   |   255.0.0.0   |         .         |
ci-info: |  eth0  | True | 192.168.1.19 | 255.255.255.0 | fa:16:3e:ae:ae:72 |
ci-info: +--------+------+--------------+---------------+-------------------+
ci-info: +++++++++++++++++++++++++++++++Route info++++++++++++++++++++++++++++++++
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+
ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    eth0   |   UG  |
ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    eth0   |   U   |
ci-info: +-------+-------------+-------------+---------------+-----------+-------+

Update 1:

I found this question which exihibited the same problem I'm having. However, I believe my metadata service is functioning properly as from a cirros instance I can curl http://169.254.169.254/ properly.

Update 2:

I finally found something! From a cirros instance I can query the metadata service:

$ curl http://169.254.169.254/2009-04-04/meta-data/placement/availability-zone
nova$

However, running the following query hangs forever:

$ curl http://169.254.169.254/openstack/2013-10-17/meta_data.json

Which is where I'm thinking the difference is between 14.04 and 12.04 or cirros. Is that an API that I don't have enabled?

Thanks, Marc