login doesn't prompt password

Bug #1634178 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Unassigned
2.0
Won't Fix
Medium
Unassigned
2.1
Won't Fix
Medium
Unassigned

Bug Description

After a successful logout, login sometimes does not prompt for password. This most likely indicates the logout was incomplete.

As seen here:
http://reports.vapour.ws/releases/issue/5804ea52749a56524a88cbd1

From the log, we can see that the test was execting a password prompt, but "login" replied with a message ending in 'troller" as "readuser".' This must be "You are now logged in to readuser_controller as readuser."

Presumably the user was not completely logged out when "juju logout" returned, and so they were recognized as already logged in, avoiding the need for a password. Probably "juju logout" should not return until the user is fully logged out.

2016-10-14 21:16:55 ERROR End Of File (EOF). Exception style platform.
<pexpect.pty_spawn.spawn object at 0x7fc262e91c90>
command: /var/lib/jenkins/workspace/functional-grant-revoke/extracted-bin/usr/lib/juju-2.0.1/bin/juju
args: ['/var/lib/jenkins/workspace/functional-grant-revoke/extracted-bin/usr/lib/juju-2.0.1/bin/juju', '--show-log', 'login', 'readuser', '-c', 'readuser_controller']
buffer (last 100 chars): ''
before (last 100 chars): 'troller" as "readuser".\r\n21:16:55 \x1b[94mINFO \x1b[0m cmd \x1b[94msupercommand.go:465 \x1b[0mcommand finished\r\n'
after: <class 'pexpect.exceptions.EOF'>
match: None
match_index: None
exitstatus: None
flag_eof: True
pid: 8474
child_fd: 6
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
    0: re.compile("(?i)password")

Changed in juju:
milestone: none → 2.0.1
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Changed in juju-core:
status: New → Won't Fix
no longer affects: juju-core
Revision history for this message
Tim Penhey (thumper) wrote :

This is actually very worrying to me. Working with Chris to get the info I need to replicate locally.

Changed in juju:
assignee: nobody → Tim Penhey (thumper)
status: Triaged → In Progress
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Marking as Won't Fix for 2.0 as we are not planning further 2.0.x releases.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I added this to the most effected test to isolate cookies from being changed by other tests.
    export GOCOOKIES=$WORKSPACE/gocookies

Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am marking this as Won't Fix for 2.1 as well since we are not planning any further 2.1.x releases...

@Tim Penhey,

Are actively working on this now or shall it go back into a common pool?

Revision history for this message
Tim Penhey (thumper) wrote :

I'm pretty sure this was fixed elsewhere.

Changed in juju:
assignee: Tim Penhey (thumper) → nobody
status: In Progress → Fix Released
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.