juju authorized-keys import fails without any output

Bug #1521020 reported by Richard Harding
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Won't Fix
High
Unassigned

Bug Description

I currently have three keys in a bootstrapped environment.

    juju authorized-keys list
    Keys for user admin:
    $fingerprint (juju-client-key)
    $fingerprint (rharding@stuff)
    $fingerprint (juju-system-key)

I then attempted to add ~bac to the environment with:

    juju authorized-keys import lp:bac

Which returned no error code or output. However, listing keys does not show bac's key added.

Tags: 2.0-count
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: 2.0-count
affects: juju-core → juju
Changed in juju:
milestone: none → 2.1.0
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I can reproduce in latest 2.1 (tip) suing newer commands:
juju ssh-keys
juju import-ssh-key ...

However, I am removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

juju import-ssh-key lp:<name> seems to be working now, tried with juju 2.9.15. Tried an invalid lp id as well.

$ juju import-ssh-key lp:asdfasrwafasdfwfsdfbergwr
cannot import key id "lp:asdfasrwafasdfwfsdfbergwr": exit status 1

$ juju import-ssh-key lp:hmlanigan
$ juju ssh-keys
Keys used in model: admin/default
<fingerprint> (<email> # ssh-import-id lp:hmlanigan)
<fingerprint> (<email2> # ssh-import-id lp:hmlanigan)

Changed in juju:
status: Triaged → Won't Fix
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.