<div dir="auto">Hello Tobias, swarm-mode solved etcd issue but the swarm stack Do es not terminate.<div dir="auto">Please:</div><div dir="auto">Which ports must be opened between external network used by magnum and controllers?</div><div dir="auto">Thanks</div><div dir="auto">ignazio</div><div dir="auto"><br></div><div class="gmail_quote" dir="auto"><div dir="ltr">Il giorno Gio 13 Dic 2018 09:54 Tobias Urdin <<a href="mailto:tobias.urdin@binero.se">tobias.urdin@binero.se</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Hello,<br>
    What swam driver are you using?<br>
    <br>
    We use the following image Fedora-Atomic-27-20180419.0.x86_64.qcow2
    and to get Kubernetes and Swarm-mode drivers working we use latest
    stable/rocky release which should<br>
    include the patches that fixes some issues.<br>
    <br>
    Make sure you got correct COE set on the swarm cluster template.<br>
    <br>
    $openstack coe cluster template show docker-swarm<br>
    | docker_storage_driver | devicemapper                         |<br>
    | network_driver        | docker                               <br>
    | coe                   | swarm-mode                           |<br>
    <br>
    These fixes should be released in latest stable/rocky:<br>
    <br>
    <a class="m_6197104805878734178moz-txt-link-freetext" href="https://review.openstack.org/#/c/598179/" target="_blank" rel="noreferrer">https://review.openstack.org/#/c/598179/</a><br>
    <a class="m_6197104805878734178moz-txt-link-freetext" href="https://review.openstack.org/#/c/607089/" target="_blank" rel="noreferrer">https://review.openstack.org/#/c/607089/</a><br>
    <a class="m_6197104805878734178moz-txt-link-freetext" href="https://review.openstack.org/#/c/611097" target="_blank" rel="noreferrer">https://review.openstack.org/#/c/611097</a><br>
    <br>
    Never got the "swarm" driver to work, you should use "swarm-mode"
    instead which uses native Docker clustering without etcd.<br>
    <br>
    For kubernetes there was no issues when using Fedora Atomic 27 but
    atomic 28 has a lot of changes so it cannot install etcd as a system
    service<br>
    so can't use 28 until that is fixed, maybe fixed in master though.<br>
    <br>
    Best regards<br>
    <br>
    <div class="m_6197104805878734178moz-cite-prefix">On 12/13/2018 06:39 AM, Ignazio Cassano
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="auto">Ps.
        <div dir="auto">Solving connection problem between master node
          and controller node allows stack to complete successfully. But
          remains the problem with the etcd package. </div>
        <div dir="auto">Regards </div>
        <div dir="auto">Ignazio</div>
        <div dir="auto"><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">Il giorno Mer 12 Dic 2018 23:55 Feilong Wang <<a href="mailto:feilong@catalyst.net.nz" target="_blank" rel="noreferrer">feilong@catalyst.net.nz</a>>
          ha scritto:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div text="#000000" bgcolor="#FFFFFF">
            <p>Seems your master node can't talk to your keystone, can
              you confirm that?</p>
            <p><br>
            </p>
            <p><br>
            </p>
            <div class="m_6197104805878734178m_398982226376816286moz-cite-prefix">On 13/12/18
              11:08 AM, Ignazio Cassano wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="auto">Hello Feilong, this forwarding contains
                logs.
                <div dir="auto">Thanks</div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr">---------- Forwarded message ---------<br>
                  From: <strong class="gmail_sendername" dir="auto">Ignazio
                    Cassano</strong> <span dir="ltr">
                    <<a href="mailto:ignaziocassano@gmail.com" rel="noreferrer noreferrer" target="_blank">ignaziocassano@gmail.com</a>></span><br>
                  Date: Mer 12 Dic 2018 10:06<br>
                  Subject: openstack queens magnum error<br>
                  To: OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org" rel="noreferrer noreferrer" target="_blank">openstack-operators@lists.openstack.org</a>><br>
                </div>
                <br>
                <br>
                <div dir="ltr">
                  <div dir="ltr">
                    <div dir="ltr">
                      <div>Hello Everyone,</div>
                      <div><br>
                      </div>
                      <div>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<br>
                      </div>
                      <div><br>
                      </div>
                      <div>The stack generated end with an error and
                        magnum conductor reports:</div>
                      <div>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<br>
                        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<br>
                        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<br>
                        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<br>
                        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.</div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div>I connected to the master node for verifyng
                        if swarm agent is running.</div>
                      <div>In the cloud init log I found:</div>
                      <div>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',))<br>
                        Cloud-init v. 0.7.9 running 'modules:final' at
                        Wed, 12 Dec 2018 08:45:31 +0000. Up 55.54
                        seconds.<br>
                        2018-12-12 08:47:45,858 - util.py[WARNING]:
                        Failed running
                        /var/lib/cloud/instance/scripts/part-005 [1]<br>
                        /var/lib/cloud/instance/scripts/part-006: line
                        13: /etc/etcd/etcd.conf: No such file or
                        directory<br>
                        /var/lib/cloud/instance/scripts/part-006: line
                        26: /etc/etcd/etcd.conf: No such file or
                        directory<br>
                        /var/lib/cloud/instance/scripts/part-006: line
                        38: /etc/etcd/etcd.conf: No such file or
                        directory<br>
                        2018-12-12 08:47:45,870 - util.py[WARNING]:
                        Failed running
                        /var/lib/cloud/instance/scripts/part-006 [1]<br>
                        Configuring docker network ...<br>
                        Configuring docker network service ...<br>
                        Removed
/etc/systemd/system/multi-user.target.wants/docker-storage-setup.service.<br>
                          New size given (1280 extents) not larger than
                        existing size (4863 extents)<br>
                        ERROR: There is not enough free space in volume
                        group atomicos to create data volume of size
                        MIN_DATA_SIZE=2G.<br>
                        2018-12-12 08:47:46,206 - util.py[WARNING]:
                        Failed running
                        /var/lib/cloud/instance/scripts/part-010 [1]<br>
                        + systemctl stop docker<br>
                        + echo 'starting services'<br>
                        starting services<br>
                        + systemctl daemon-reload<br>
                        + for service in etcd docker.socket docker
                        swarm-manager<br>
                        + echo 'activating service etcd'<br>
                        activating service etcd<br>
                        + systemctl enable etcd<br>
                        Failed to enable unit: Unit file etcd.service
                        does not exist.<br>
                        + systemctl --no-block start etcd<br>
                        Failed to start etcd.service: Unit etcd.service
                        not found.<br>
                        + for service in etcd docker.socket docker
                        swarm-manager<br>
                        + echo 'activating service docker.socket'<br>
                        activating service docker.socket<br>
                        + systemctl enable docker.socket</div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div>1) Seems etcd service is not installed ,</div>
                      <div><br>
                      </div>
                      <div>2) the instance required to contact
                        controller on port 5000 (is it correct ?)</div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div>Please help me.</div>
                      <div><br>
                      </div>
                      <div>Regards</div>
                      <div>Ignazio<br>
                      </div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </blockquote>
            <pre class="m_6197104805878734178m_398982226376816286moz-signature" cols="72">-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a class="m_6197104805878734178m_398982226376816286moz-txt-link-abbreviated" href="mailto:flwang@catalyst.net.nz" rel="noreferrer noreferrer" target="_blank">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
-------------------------------------------------------------------------- </pre>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </div>

</blockquote></div></div>