Removing cookies in browser causes internal server error
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.5 |
Won't Fix
|
Low
|
Unassigned | |||
3.6 |
Triaged
|
Low
|
Unassigned |
Bug Description
2019-06-21 21:06:44 regiond: [info] 192.168.1.203 GET /MAAS/ws HTTP/1.1 --> 500 INTERNAL_
2019-06-21 21:06:49 _GenericHTTPCha
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
File "/usr/lib/
body = resrc.render(self)
File "/usr/lib/
return orig_render(
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
cookies = self.transport.
Changed in maas: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in maas: | |
milestone: | none → 3.4.0 |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
Please note that I was using chrome
Since I could no longer use Chrome Version 74.0.3729.169 (Official Build) (64-bit), I opened the MaaS UI up in Firefox, which worked fine.
Some potentially good context here, too:
We're developing a Kubernetes operator that uses maas heavily. I've had a tab open in Chrome to our maas lab for weeks. The k8s operator we're developing instantiates and destroys maas machines regularly due to our testing. Today, I was running our operator bringing up and down maas nodes, however the UI was not updating in realtime the creation and release of the nodes I was working with unless I refreshed the browser tab manually. So, I cleared the cookies in an effort to "clean the pipes" as it were. Everything was hosed after that, and the error above ensued.