juju-core

Some EC2 instance prices specified in octal

Bug #1203935 reported by Jeroen T. Vermeulen on 2013-07-23

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	juju-core	Fix Released	Medium	Andrew Wilkins	juju-core 1.14.0

Bug Description

Some of the "t1.micro" prices in environs/ec2/instancetype.go, in the allRegionCosts array, are specified in octal. In some regions it's listed as 020 (i.e. 1.6¢/h) and in others as 027 (i.e. 2.3¢/h). I suspect the leading zero was meant as padding, but it changes the meaning of the numbers.

Related branches

lp://staging/~axwalk/juju-core/lp1203935-ec2-octal-prices

Merged into lp://staging/~go-bot/juju-core/trunk at revision 1519

Juju Engineering: Pending requested 2013-07-23

Andrew Wilkins (axwalk) on 2013-07-23

Changed in juju-core:
assignee:	nobody → Andrew Wilkins (axwalk)
status:	New → Confirmed

Tim Penhey (thumper) on 2013-07-24

Changed in juju-core:
status:	In Progress → Fix Committed
importance:	Undecided → Medium

Curtis Hovey (sinzui) on 2013-09-25

Changed in juju-core:
milestone:	none → 1.14.0
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.