"build_id": "2014-02-17_01-17-30",
"build_number": "128",
"release": "4.1"
1. Create new environment (Havana on Ubuntu, Multi-Node without HA, KVM hypervisor, Neutron with GRE network)
2. Add controller, compute
3. Start deployment. it was successful
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
4. Start Instance with Ubuntu system:
Cluster gets state "Active", but in log:
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.111.1 | 0.0.0.0 | eth0 | UG |
ci-info: | 1 | 192.168.111.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
ci-info: +-------+---------------+---------------+---------------+-----------+-------+
2014-02-18 17:39:29,721 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: bad status code [500]
.
.
.
2014-02-18 17:41:26,509 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [116/120s]: bad status code [500]
2014-02-18 17:41:33,517 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 123 seconds
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5. Start Instance with Cirros system:
Cluster gets state "Active", but in log:
cirros-ds 'net' up at 0.69
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 0.69. iid had '<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1>500 Internal Server Error</h1>
Remote metadata server experienced an internal server error.<br /><br />
</body>
</html>'
failed 2/20: up 2.76. iid had '<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1>500 Internal Server Error</h1>
Remote metadata server experienced an internal server error.<br /><br />
.
.
.
failed to get http://169.254.169.254/2009-04-04/meta-data// <head>/openssh-key
warning: no ec2 metadata for public-keys
failed to get http://169.254.169.254/2009-04-04/meta-data/instance-id
warning: no ec2 metadata for instance-id
failed to get http://169.254.169.254/2009-04-04/meta-data// <head>/openssh-key
warning: no ec2 metadata for public-keys
failed to get http://169.254.169.254/2009-04-04/meta-data/hostname
please test for network issues between the compute and controller running metadata.
Please attach support bundle