nodes are no longer reported as tracked at the CLC
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eucalyptus |
Confirmed
|
Wishlist
|
chris grzegorczyk | ||
Bug Description
Not a functional problem. Below the node 'epic-fail-guy' has been removed from the system (e.g., it is turned off). Even though the timestamp indicates the last time the node was seen, expiry or current visibility would avoid confusion.
.euca2-kvm-deb> ec2-describe-
AVAILABILITYZONE a UP localhost
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0004 / 0004 1 128 1
AVAILABILITYZONE |- c1.medium 0004 / 0004 1 256 2
AVAILABILITYZONE |- m1.large 0002 / 0002 2 512 10
AVAILABILITYZONE |- m1.xlarge 0002 / 0002 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0001 / 0001 4 2048 20
AVAILABILITYZONE |- epic-fail-guy certs[cc=
AVAILABILITYZONE |- serious-cat certs[cc=
EDIT: As of 1.6.1 this information is not reported correctly.
| Changed in eucalyptus: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| assignee: | nobody → chris grzegorczyk (chris-grze) |
| summary: |
- nodes which are removed continue to be tracked at the CLC + nodes are no longer reported as tracked at the CLC |
| description: | updated |
| Andy Grimm (agrimm) wrote | #1 |
This issue is now being tracked upstream at http://
Please watch that issue for further updates.