| 2018-12-04 17:02:59 |
Emilien Macchi |
description |
Environment: master (Stein)
How to reproduce:
1) Deploy an undercloud with "container_cli = podman" in undercloud.conf
2) Run "openstack undercloud upgrade"
Results: it hangs at step3 when starting containers.
Looking at containers states, HAproxy isn't running.
[root@undercloud ~]# podman logs haproxy
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Deleting /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src/etc/haproxy/haproxy.cfg to /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src-tls/etc/pki/tls/private/overcloud_endpoint.pem to /etc/pki/tls/private/overcloud_endpoint.pem
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/lib/haproxy
++ cat /run_command
+ CMD='/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
+ echo 'Running command: '\''/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'\'''
Running command: '/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ exec /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg
<7>haproxy-systemd-wrapper: executing /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -Ds
[WARNING] 337/132458 (12) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear.
<7>haproxy-systemd-wrapper: SIGTERM -> 13.
<5>haproxy-systemd-wrapper: exit, haproxy RC=0 |
Environment: master (Stein)
How to reproduce:
1) Deploy an undercloud with "container_cli = podman" in undercloud.conf
2) Run "openstack undercloud upgrade"
Results: it hangs at step3 when starting containers.
Looking at containers states, HAproxy isn't running.
[root@undercloud ~]# podman logs haproxy
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Deleting /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src/etc/haproxy/haproxy.cfg to /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src-tls/etc/pki/tls/private/overcloud_endpoint.pem to /etc/pki/tls/private/overcloud_endpoint.pem
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/lib/haproxy
++ cat /run_command
+ CMD='/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
+ echo 'Running command: '\''/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'\'''
Running command: '/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ exec /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg
<7>haproxy-systemd-wrapper: executing /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -Ds
[WARNING] 337/132458 (12) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear.
<7>haproxy-systemd-wrapper: SIGTERM -> 13.
<5>haproxy-systemd-wrapper: exit, haproxy RC=0
We need to investigate why the HAproxy container receives a SIGPIPE signal. |
|
| 2018-12-04 17:04:24 |
Emilien Macchi |
description |
Environment: master (Stein)
How to reproduce:
1) Deploy an undercloud with "container_cli = podman" in undercloud.conf
2) Run "openstack undercloud upgrade"
Results: it hangs at step3 when starting containers.
Looking at containers states, HAproxy isn't running.
[root@undercloud ~]# podman logs haproxy
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Deleting /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src/etc/haproxy/haproxy.cfg to /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src-tls/etc/pki/tls/private/overcloud_endpoint.pem to /etc/pki/tls/private/overcloud_endpoint.pem
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/lib/haproxy
++ cat /run_command
+ CMD='/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
+ echo 'Running command: '\''/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'\'''
Running command: '/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ exec /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg
<7>haproxy-systemd-wrapper: executing /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -Ds
[WARNING] 337/132458 (12) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear.
<7>haproxy-systemd-wrapper: SIGTERM -> 13.
<5>haproxy-systemd-wrapper: exit, haproxy RC=0
We need to investigate why the HAproxy container receives a SIGPIPE signal. |
Environment: master (Stein)
How to reproduce:
1) Deploy an undercloud with "container_cli = podman" in undercloud.conf
2) Run "openstack undercloud upgrade"
Results: it hangs at step3 when starting containers.
Looking at containers states, HAproxy isn't running.
[root@undercloud ~]# podman logs haproxy
+ sudo -E kolla_set_configs
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Copying service configuration files
INFO:__main__:Deleting /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src/etc/haproxy/haproxy.cfg to /etc/haproxy/haproxy.cfg
INFO:__main__:Copying /var/lib/kolla/config_files/src-tls/etc/pki/tls/private/overcloud_endpoint.pem to /etc/pki/tls/private/overcloud_endpoint.pem
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/lib/haproxy
++ cat /run_command
+ CMD='/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ ARGS=
+ [[ ! -n '' ]]
+ . kolla_extend_start
+ echo 'Running command: '\''/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'\'''
Running command: '/usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg'
+ exec /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg
<7>haproxy-systemd-wrapper: executing /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -Ds
[WARNING] 337/132458 (12) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear.
<7>haproxy-systemd-wrapper: SIGTERM -> 13.
<5>haproxy-systemd-wrapper: exit, haproxy RC=0
We need to investigate why the HAproxy container receives a SIGPIPE signal.
Note: the bug can't be reproduced when running a re-deploy with "openstack undercloud install". |
|
