Possibly related, we are seeing placement go into a blocked state during deployment after the Vault charm is unsealed, as seen in this test run: https://solutions.qa.canonical.com/testruns/testRun/a3e2b793-4a42-4be3-9b60-c7b2e0b333bd Artifacts here: https://oil-jenkins.canonical.com/artifacts/a3e2b793-4a42-4be3-9b60-c7b2e0b333bd/generated/generated/openstack/juju-crashdump-openstack-2021-01-12-20.33.06.tar.gz
placement/0 blocked idle 4/lxd/19 10.244.41.52 8778/tcp Services not running that should be: apache2; Ports which should be open, but are not: 8768 hacluster-placement/2 active idle 10.244.41.52 Unit is ready and clustered logrotated/45 active idle 10.244.41.52 Unit is ready. placement-mysql-router/2 active idle 10.244.41.52 Unit is ready public-policy-routing/33 active idle 10.244.41.52 Unit is ready placement/1 blocked idle 6/lxd/9 10.244.41.23 8778/tcp Services not running that should be: apache2; Ports which should be open, but are not: 8768 hacluster-placement/1 active idle 10.244.41.23 Unit is ready and clustered logrotated/33 active idle 10.244.41.23 Unit is ready. placement-mysql-router/1 active idle 10.244.41.23 Unit is ready public-policy-routing/23 active idle 10.244.41.23 Unit is ready placement/2* blocked idle 8/lxd/10 10.244.41.17 8778/tcp Services not running that should be: apache2; Ports which should be open, but are not: 8768 hacluster-placement/0* active idle 10.244.41.17 Unit is ready and clustered logrotated/9 active idle 10.244.41.17 Unit is ready. placement-mysql-router/0* active idle 10.244.41.17 Unit is ready public-policy-routing/4 active idle 10.244.41.17 Unit is ready Apache2 is failing due to a missing cert (or symlink): Jan 12 05:41:32 juju-590c2a-0-lxd-10 systemd[1]: Starting The Apache HTTP Server... -- Subject: A start job for unit apache2.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit apache2.service has begun execution. -- -- The job identifier is JOB_ID. Jan 12 05:41:32 juju-590c2a-0-lxd-10 apachectl[80457]: AH00526: Syntax error on line 13 of /etc/apache2/sites-enabled/openstack_https_frontend.conf: Jan 12 05:41:32 juju-590c2a-0-lxd-10 apachectl[80457]: SSLCertificateFile: file '/etc/apache2/ssl/placement/cert_10.244.8.95' does not exist or is empty Jan 12 05:41:32 juju-590c2a-0-lxd-10 apachectl[80457]: Action 'start' failed. Jan 12 05:41:32 juju-590c2a-0-lxd-10 apachectl[80457]: The Apache error log may have more information. Jan 12 05:41:32 juju-590c2a-0-lxd-10 systemd[1]: apache2.service: Control process exited, code=exited status=1 Jan 12 05:41:32 juju-590c2a-0-lxd-10 systemd[1]: apache2.service: Failed with result 'exit-code'. Jan 12 05:41:32 juju-590c2a-0-lxd-10 systemd[1]: Failed to start The Apache HTTP Server. -- Subject: A start job for unit apache2.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit apache2.service has finished with a failure. ** Tags added: cdo-release-blocker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889665 Title: Apache2 is not running after charm config changed To manage notifications about this bug go to: https://bugs.launchpad.net/charm-octavia/+bug/1889665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
