Upstream has indicated that euca-describe-availability-zones verbose
is a hint of what the availability is, and not necessarily current.
Providing this is not a regression from 1.6.2 (waiting on upstream to
confirm), this requires a documentation fix. Therefore setting to low
priority.
**
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
--
euca-describe-availability-zones verbose incorrect output
https://bugs.launchpad.net/bugs/610987
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: New
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: (unassigned) = Dave Walker (davewalker)
--
euca-describe-availability-zones verbose incorrect output
https://bugs.launchpad.net/bugs/610987
You
** Changed in: eucalyptus (Ubuntu Maverick)
Milestone: maverick-alpha-3 = ubuntu-10.10-beta
** Changed in: eucalyptus (Ubuntu Maverick)
Importance: High = Medium
** Changed in: eucalyptus (Ubuntu Maverick)
Status: New = Confirmed
** Changed in: eucalyptus (Ubuntu Maverick)
milestoning to Alpha3, setting as High
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu)
Milestone: None = maverick-alpha-3
--
euca-describe-availability-zones verbose incorrect output
https://bugs.launchpad.net/bugs/610987
You received
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
euca-describe-availability-zones verbose incorrect output
https://bugs.launchpad.net/bugs/610987
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
I ran another test -- I thought it might have something to do with
'euca-run-instances -nxx'. So, starting with a just-booted cloud, I ran
a sequence of 'euca-run-instances -n10 ...' intermixed with 'euca-
describe-availability-zones verbose'. I then stopped for lunch, and then
ran two more
On the log above -- it is interesting to note that suddenly we lost a
whole NC (m1.small MAX went from 80 to 64) for a while. After lunch, the
NC was back in, as misteriously as it had disappeared.
--
euca-describe-availability-zones verbose incorrect output
full logs now available:
bzr+ssh://bazaar.launchpad.net/~hggdh2/%2Bjunk/uec-qa/
Pushed up to revision 24.
--
euca-describe-availability-zones verbose incorrect output
https://bugs.launchpad.net/bugs/610987
You received this bug notification because you are a member of Ubuntu
Server Team, which
whole log attached; the issue can be seem throughout the log, but it is
clearly visible on the very first runs.
** Attachment added: uec-testing-scripts log output
http://launchpadlibrarian.net/52647729/single_log_eucav2_200.log.2010-07-28_130937
--
euca-describe-availability-zones verbose
10 matches
Mail list logo
