Open Stack

Seems your master node can't talk to your keystone, can you confirm that?



On 13/12/18 11:08 AM, Ignazio Cassano wrote:
> Hello Feilong, this forwarding contains logs.
> Thanks
>
> ---------- Forwarded message ---------
> From: *Ignazio Cassano* <ignaziocassano at gmail.com
> <mailto:ignaziocassano at gmail.com>>
> Date: Mer 12 Dic 2018 10:06
> Subject: openstack queens magnum error
> To: OpenStack Operators <openstack-operators at lists.openstack.org
> <mailto:openstack-operators at lists.openstack.org>>
>
>
> Hello Everyone,
>
> I installed queens on centos with magnum and I am trying to create a
> swarm cluster with one muster and one node. The image I used is
> fedora-atomic 27 update 04
>
> The stack generated end with an error and magnum conductor reports:
> ec 12 09:51:17 tst2-osctrl01 magnum-conductor: 2018-12-12 09:51:17.304
> 17964 WARNING magnum.drivers.heat.template_def
> [req-bfa19294-5671-47a0-b0ac-9e544f0e5e38 - - - - -] stack does not
> have output_key api_address
> Dec 12 09:51:17 tst2-osctrl01 magnum-conductor: 2018-12-12
> 09:51:17.305 17964 WARNING magnum.drivers.heat.template_def
> [req-bfa19294-5671-47a0-b0ac-9e544f0e5e38 - - - - -] stack does not
> have output_key swarm_masters
> Dec 12 09:51:17 tst2-osctrl01 magnum-conductor: 2018-12-12
> 09:51:17.306 17964 WARNING magnum.drivers.heat.template_def
> [req-bfa19294-5671-47a0-b0ac-9e544f0e5e38 - - - - -] stack does not
> have output_key swarm_nodes
> Dec 12 09:51:17 tst2-osctrl01 magnum-conductor: 2018-12-12
> 09:51:17.306 17964 WARNING magnum.drivers.heat.template_def
> [req-bfa19294-5671-47a0-b0ac-9e544f0e5e38 - - - - -] stack does not
> have output_key discovery_url
> Dec 12 09:51:17 tst2-osctrl01 magnum-conductor: 2018-12-12
> 09:51:17.317 17964 ERROR magnum.drivers.heat.driver
> [req-bfa19294-5671-47a0-b0ac-9e544f0e5e38 - - - - -] Cluster error,
> stack status: CREATE_FAILED, stack_id:
> 306bd83a-7878-4d94-8ed0-1d297eec9768, reason: Resource CREATE failed:
> WaitConditionFailure:
> resources.swarm_nodes.resources[0].resources.node_wait_condition:
> swarm-agent service failed to start.
>
>
>
> I connected to the master node for verifyng if swarm agent is running.
> In the cloud init log I found:
> requests.exceptions.ConnectionError:
> HTTPConnectionPool(host='10.102.184.190', port=5000): Max retries
> exceeded with url: /v3//auth/tokens (Caused by
> NewConnectionError('<urllib3.connection.HTTPConnection object at
> 0x7f0814d4d250>: Failed to establish a new connection: [Errno 110]
> Connection timed out',))
> Cloud-init v. 0.7.9 running 'modules:final' at Wed, 12 Dec 2018
> 08:45:31 +0000. Up 55.54 seconds.
> 2018-12-12 08:47:45,858 - util.py[WARNING]: Failed running
> /var/lib/cloud/instance/scripts/part-005 [1]
> /var/lib/cloud/instance/scripts/part-006: line 13:
> /etc/etcd/etcd.conf: No such file or directory
> /var/lib/cloud/instance/scripts/part-006: line 26:
> /etc/etcd/etcd.conf: No such file or directory
> /var/lib/cloud/instance/scripts/part-006: line 38:
> /etc/etcd/etcd.conf: No such file or directory
> 2018-12-12 08:47:45,870 - util.py[WARNING]: Failed running
> /var/lib/cloud/instance/scripts/part-006 [1]
> Configuring docker network ...
> Configuring docker network service ...
> Removed
> /etc/systemd/system/multi-user.target.wants/docker-storage-setup.service.
>   New size given (1280 extents) not larger than existing size (4863
> extents)
> ERROR: There is not enough free space in volume group atomicos to
> create data volume of size MIN_DATA_SIZE=2G.
> 2018-12-12 08:47:46,206 - util.py[WARNING]: Failed running
> /var/lib/cloud/instance/scripts/part-010 [1]
> + systemctl stop docker
> + echo 'starting services'
> starting services
> + systemctl daemon-reload
> + for service in etcd docker.socket docker swarm-manager
> + echo 'activating service etcd'
> activating service etcd
> + systemctl enable etcd
> Failed to enable unit: Unit file etcd.service does not exist.
> + systemctl --no-block start etcd
> Failed to start etcd.service: Unit etcd.service not found.
> + for service in etcd docker.socket docker swarm-manager
> + echo 'activating service docker.socket'
> activating service docker.socket
> + systemctl enable docker.socket
>
>
> 1) Seems etcd service is not installed ,
>
> 2) the instance required to contact controller on port 5000 (is it
> correct ?)
>
>
> Please help me.
>
> Regards
> Ignazio
>
>
-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flwang at catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
-------------------------------------------------------------------------- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181213/ff25a01c/attachment.html>