[2.4, master] Unable to connect to ws://<ip>/ws

Bug #1739499 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Critical
Unassigned

Bug Description

While using the UI, I noticed the ID constantly disconnects from the websockets, and in the logs I see similar stuff to:

regiond.log
2017-12-20 22:57:05 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 36968)
2017-12-20 22:57:20 -: [info] Forcibly timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 36968)
2017-12-20 22:57:31 -: [info] Timing out client: IPv6Address(TCP, '::ffff:127.0.0.1', 48450)
2017-12-20 22:57:38 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 37006)
2017-12-20 22:57:38 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 37010)
2017-12-20 22:57:38 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 36942)
2017-12-20 22:57:38 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 37012)
2017-12-20 22:57:38 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 37014)
2017-12-20 22:57:38 -: [info] Timing out client: IPv6Address(TCP, '::ffff:10.172.194.101', 37008)

summary: - [2.4, master] Constant ws disconnection
+ [2.4, master] Unable to connect to ws://<ip>/ws
Changed in maas:
milestone: none → 2.4.0alpha1
importance: Undecided → Critical
status: New → Triaged
Changed in maas:
milestone: 2.4.0alpha1 → 2.4.0alpha2
Changed in maas:
milestone: 2.4.0alpha2 → 2.4.0beta1
Changed in maas:
milestone: 2.4.0beta1 → 2.4.0beta2
Changed in maas:
status: Triaged → Invalid
milestone: 2.4.0beta2 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.