'juju status' output when no env is non-intuitive

Bug #1183116 reported by Jono Bacon
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core
New
Undecided
Unassigned
juju-core (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

When I have just detroyed my environment (or have no environment) and run 'juju status' I get:

   error: The specified bucket does not exist

This doesn't make any sense.

It should say something like this instead:

  No environment available. See http://juju.ubuntu.com/XYZ for how to create one.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: juju-core 1.10.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu1
Architecture: i386
Date: Wed May 22 14:17:11 2013
InstallationDate: Installed on 2013-05-05 (17 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130504)
MarkForUpload: True
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jono Bacon (jonobacon) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-core (Ubuntu):
status: New → Confirmed
James Page (james-page)
Changed in juju-core (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Wishlist
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.