Hi Pedro,
Just to make sure I understand it correctly - you are able to SSH to
the overcloud nodes and restart cloud-init ?
Thanks,
Marius
On Fri, Jun 19, 2015 at 6:42 PM, Pedro Sousa <pgsousa(a)gmail.com> wrote:
 Hi Maruis,
 thank you for your reply. Yes the nodes can reach dhcp, but my understanding
 is that cloud init starts first than I get ip addresses.
 If I restart cloud-init I will see the routes tables being created properly.
 However, after I restart cloud-init nothing happens, I don't see the
 deployment to resume, I only see this in the logs:
 Jun 19 16:38:19 localhost os-collect-config: 2015-06-19 16:38:19.357 1518
 WARNING os_collect_config.heat [-] No auth_url configured.
 Jun 19 16:38:19 localhost os-collect-config: 2015-06-19 16:38:19.359 1518
 WARNING os_collect_config.request [-] No metadata_url configured.
 Jun 19 16:38:19 localhost os-collect-config: 2015-06-19 16:38:19.359 1518
 WARNING os-collect-config [-] Source [request] Unavailable.
 Jun 19 16:38:19 localhost os-collect-config: 2015-06-19 16:38:19.359 1518
 WARNING os_collect_config.local [-] /var/lib/os-collect-config/local-data
 not found. Skipping
 Jun 19 16:38:19 localhost os-collect-config: 2015-06-19 16:38:19.359 1518
 WARNING os_collect_config.local [-] No local metadata found
 (['/var/lib/os-collect-config/local-data'])
 I also see that it gets stuck here:
 [stack@instack ~]$ heat resource-show overcloud Controller
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
 | Property               | Value
 |
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
 | attributes             | {
 |
 |                        |   "attributes": null,
 |
 |                        |   "refs": null
 |
 |                        | }
 |
 | description            |
 |
 | links                  |
http://192.168.21.180:8004/v1/9fcf8994049b48d6af5ea6fe5323a21d/stacks/ove...
 (self)      |
 |                        |
http://192.168.21.180:8004/v1/9fcf8994049b48d6af5ea6fe5323a21d/stacks/ove...
 (stack)                          |
 |                        |
http://192.168.21.180:8004/v1/9fcf8994049b48d6af5ea6fe5323a21d/stacks/ove...
 (nested) |
 | logical_resource_id    | Controller
 |
 | physical_resource_id   | 89b52bb2-de3b-45c5-8ec4-43c2545b8d04
 |
 | required_by            | allNodesConfig
 |
 |                        | VipDeployment
 |
 |                        | ControllerAllNodesDeployment
 |
 |                        | ControllerIpListMap
 |
 |                        | CephClusterConfig
 |
 |                        | ControllerBootstrapNodeConfig
 |
 |                        | ControllerCephDeployment
 |
 |                        | ControllerBootstrapNodeDeployment
 |
 |                        | ControllerClusterConfig
 |
 |                        | ControllerSwiftDeployment
 |
 |                        | SwiftDevicesAndProxyConfig
 |
 |                        | ControllerNodesPostDeployment
 |
 |                        | ControllerClusterDeployment
 |
 | resource_name          | Controller
 |
 | resource_status        | CREATE_IN_PROGRESS
 |
 | resource_status_reason | state changed
 |
 | resource_type          | OS::Heat::ResourceGroup
 |
 | updated_time           | 2015-06-19T17:25:45Z
 |
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
 Regards,
 Pedro Sousa
 On Thu, Jun 18, 2015 at 9:16 PM, Marius Cornea <marius(a)remote-lab.net>
 wrote:
>
> Hi Pedro,
>
> Can you check if the nodes can reach the dhcp server on the undercloud
> node? Looks to me that the nodes can't get an IP address:
>
> systemctl status neutron-dhcp-agent.service # check service status
> ip netns list # check if dhcp namespace is there
> cat /var/lib/neutron/dhcp/<namespace_uuid>/leases # check if the file
> shows leases for your nodes nic mac addresses
>
> Thanks,
> Marius
>
>
> On Wed, Jun 17, 2015 at 7:17 PM, Pedro Sousa <pgsousa(a)gmail.com> wrote:
> > Hi all,
> >
> > I'm trying to deploy 2 nodes, one compute and one controller using RDO.
> > However my heat stack times out and I don't understand why, I see that
> > openstack doesn't get configured, checking the logs, I see this:
> >
> > Jun 17 16:44:12 localhost cloud-init: ci-info:
> > +++++++++++++++++++++++Net
> > device info+++++++++++++++++++++++
> > Jun 17 16:44:12 localhost cloud-init: ci-info:
> > +--------+------+-----------+-----------+-------------------+
> > Jun 17 16:44:12 localhost cloud-init: ci-info: | Device |  Up  |
> > Address  |
> > Mask   |     Hw-Address    |
> > Jun 17 16:44:12 localhost cloud-init: ci-info:
> > +--------+------+-----------+-----------+-------------------+
> > Jun 17 16:44:12 localhost cloud-init: ci-info: |  lo:   | True |
> > 127.0.0.1 |
> > 255.0.0.0 |         .         |
> > Jun 17 16:44:12 localhost cloud-init: ci-info: |  em2:  | True |     .
> > |
> > .     | d4:ae:52:a1:cd:80 |
> > Jun 17 16:44:12 localhost cloud-init: ci-info: |  em1:  | True |     .
> > |
> > .     | d4:ae:52:a1:cd:7f |
> > Jun 17 16:44:12 localhost cloud-init: ci-info: | p2p1:  | True |     .
> > |
> > .     | 68:05:ca:16:db:94 |
> > Jun 17 16:44:12 localhost cloud-init: ci-info:
> > +--------+------+-----------+-----------+-------------------+
> > Jun 17 16:44:12 localhost cloud-init: ci-info:
> > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!
> >
> >
> > os-collect-config: 2015-06-17 15:39:22.319 1663 WARNING
> > os_collect_config.cfn [-] 403 Client Error: AccessDenied
> >
> > Any hint?
> >
> > Thanks,
> > Pedro Sousa
> >
> >
> >
> > _______________________________________________
> > Rdo-list mailing list
> > Rdo-list(a)redhat.com
> > 
https://www.redhat.com/mailman/listinfo/rdo-list
> >
> > To unsubscribe: rdo-list-unsubscribe(a)redhat.com