Ticket #8156 (new defect)

Opened 6 years ago

Last modified 6 years ago

Sugar hangs forever trying to connect to WPA AP

Reported by: cjb Owned by: dcbw
Priority: high Milestone: 8.2.0 (was Update.2)
Component: network manager Version: not specified
Keywords: blocks-:8.2.0 Cc: dsd, joe
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

In joyride-2301, it looks like we get NetworkManager into a tight loop by trying to connect to our "canopy" WPA AP:

Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0/wireless): ac
cess point 'canopy' is encrypted, but NO valid key exists.  New key needed.
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) New wireless
 user key requested for network 'canopy'.
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5
 (Device Configure) complete.
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) New wireless
 user key for network 'canopy' received.
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5
 (Device Prepare) scheduled...
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5
 (Device Prepare) started...
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5
 (Device Configure) scheduled...
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5
 (Device Prepare) complete.
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5
 (Device Configure) starting...
Aug 25 23:04:48 localhost NetworkManager: <info>  Activation (eth0/wireless): ac
cess point 'canopy' is encrypted, but NO valid key exists.  New key needed.

Full logs attached.

Attachments

Change History

Changed 6 years ago by cjb

Changed 6 years ago by joe

It actually was joyride-2230.

Changed 6 years ago by kimquirk

  • keywords blocks-:8.2.0 added; blocks?:8.2.0 removed

With 8.2-767, latest firmware, I connected to canopy fine. Sugar was happy. If this shows up again, we can raise priority.

Changed 6 years ago by kimquirk

  • priority changed from blocker to high

Changed 6 years ago by cjb

Hrr, this kind of thing worries me. Why would we think this is fixed? Isn't the fact that NM is willing to infinite-loop instead of realizing that its key is failing worth fixing?

I think I would do a code review of this as blocker.

Changed 6 years ago by mbletsas

Just a note: Canopy is WEP (not WPA)

M.

Note: See TracTickets for help on using tickets.