Bug 1654081 - Deployment exits with Connection is already closed.
Summary: Deployment exits with Connection is already closed.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: 14.0 (Rocky)
Assignee: Thomas Hervé
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks: 1654739
TreeView+ depends on / blocked
 
Reported: 2018-11-28 01:55 UTC by Marius Cornea
Modified: 2019-01-11 11:55 UTC (History)
13 users (show)

Fixed In Version: puppet-tripleo-9.3.1-0.20181010034752.157eaab.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1654739 (view as bug list)
Environment:
Last Closed: 2019-01-11 11:55:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1805647 0 None None None 2018-11-28 15:49:10 UTC
Launchpad 1805649 0 None None None 2018-11-28 15:49:43 UTC
OpenStack gerrit 620625 0 None MERGED Catch websocket connection close errors in cleanup 2020-09-02 15:48:07 UTC
OpenStack gerrit 620627 0 None MERGED Remove timeout in config-download 2020-09-02 15:48:07 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:55:15 UTC

Description Marius Cornea 2018-11-28 01:55:17 UTC
Description of problem:
Deployment exits with 'Connection is already closed' without running post deployment steps:


TASK [Run puppet host configuration for step 2] ********************************
Tuesday 27 November 2018  16:29:44 -0500 (0:00:00.290)       0:15:49.553 ****** 
changed: [openshift-infra-2] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-master-0] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-worker-2] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-infra-0] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-infra-1] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-worker-1] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-worker-0] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-master-2] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-master-1] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}

Connection is already closed.

real    95m51.391s
user    0m14.089s
sys     0m0.985s


Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-9.0.1-0.20181013060891.el7ost.noarch

How reproducible:
when registering nodes to portal(I am assuming deployment is slower because of this)

Steps to Reproduce:
1. Create a script /home/stack/overcloud_deploy.sh:

time openstack overcloud deploy \
--stack openshift \
--templates \
-r /home/stack/openshift_roles_data.yaml \
-n /home/stack/network_data.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/openshift.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/openshift-cns.yaml \
-e /home/stack/openshift_env.yaml \
-e /home/stack/nodes.yaml \
-e /home/stack/containers-prepare-parameter.yaml \
-e /home/stack/repo.yaml

2. Run script:
bash /home/stack/overcloud_deploy.sh

Actual results:
TASK [Run puppet host configuration for step 2] ********************************
Tuesday 27 November 2018  16:29:44 -0500 (0:00:00.290)       0:15:49.553 ****** 
changed: [openshift-infra-2] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-master-0] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-worker-2] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-infra-0] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-infra-1] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-worker-1] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-worker-0] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-master-2] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [openshift-master-1] => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}

Connection is already closed.

real    95m51.391s
user    0m14.089s
sys     0m0.985s


Expected results:
The deployment runs all the steps.

Additional info:
Attaching /var/lib/mistral/openshift and /var/log/containers.

Comment 6 Emilien Macchi 2018-11-29 14:46:50 UTC
Movin

Comment 18 errata-xmlrpc 2019-01-11 11:55:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045


Note You need to log in before you can comment on or make changes to this bug.