Haproxy goes into blocked state with TLS-related error message in non-TLS setup ( only TCP )

[Thanhphan1147]

Bug Description

under a TCP-only configuration, haproxy goes into a blocked state with No hostname configured or requested if it's related to a certificates provider. Although the haproxy config is still correctly written, this behavior is not correct and blocks deployments relying on the status of the haproxy charm.

Impact

High (major functionality broken, no workaround)

Impact Rationale

No response

To Reproduce

N/A

Environment

2.8/edge

Relevant log output

N/A

Additional context

No response

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/ISD-6219.

This message was autogenerated