Cannot create services named 'foo-N' where N is an integer?

Bug #1229883 reported by Sidnei da Silva
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

Had a couple services named 'foo-1', 'foo-2', and so on deployed on pyjuju. When trying to re-deploy with the same names in gojuju got back an error saying 'Invalid service name'. Renaming to 'foo-a', 'foo-b' worked, but annoying to say the least.

Tags: deploy docs
Revision history for this message
John A Meinel (jameinel) wrote :

This might be a Won't Fix because internally we use names like "foo-1" to be clear what unit of a service we are talking about. So we would be confused by "foo-1-1" . (or you could deploy a service foo and one foo-1, and then the foo-1 unit would have the same name as the foo-1 service.)

Changed in juju-core:
importance: Undecided → Low
status: New → Triaged
Curtis Hovey (sinzui)
tags: added: deploy doc
Curtis Hovey (sinzui)
tags: added: docs
removed: doc
Changed in juju-core:
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.