To keep it registered, I've set up swift-proxy on Bionic containers (same configs as described on the main text of this bug).
After deployed, I've ran: juju run --application swift-proxy "add-apt-repository ppa:james-page/bug1817055" juju run --application swift-proxy "apt update" juju run --application swift-proxy "apt install python-eventlet=0.20.0-4ubuntu0.18.04.1~ubuntu18.04.1~ppa201902221457" juju run --application swift-proxy "apt -y install python-eventlet=0.20.0-4ubuntu0.18.04.1~ubuntu18.04.1~ppa201902221457" juju run --application swift-proxy "systemctl restart swift-proxy.service"
To keep it registered, I've set up swift-proxy on Bionic containers (same configs as described on the main text of this bug).
After deployed, I've ran: eventlet= 0.20.0- 4ubuntu0. 18.04.1~ ubuntu18. 04.1~ppa2019022 21457" eventlet= 0.20.0- 4ubuntu0. 18.04.1~ ubuntu18. 04.1~ppa2019022 21457" service"
juju run --application swift-proxy "add-apt-repository ppa:james-page/bug1817055"
juju run --application swift-proxy "apt update"
juju run --application swift-proxy "apt install python-
juju run --application swift-proxy "apt -y install python-
juju run --application swift-proxy "systemctl restart swift-proxy.