Note, bug #1961192 looks to be related to the error that is reported around the "Error: no close frame received or sent." I am suspicious that the pylibjuju connection is not closing out the connection correctly as referenced in the bug - which then leads to this error that is seen.
Note, bug #1961192 looks to be related to the error that is reported around the "Error: no close frame received or sent." I am suspicious that the pylibjuju connection is not closing out the connection correctly as referenced in the bug - which then leads to this error that is seen.