Ah, my bad. I originally looked at --deregister-sc options and tried
both host and IP with what appeared to be success (but really was doing
nothing), filed the bug, and then tried --deregister-cluster <IP>,
thinking it would obey the same option...

Fixing description to reflect that this is a doc bug.

** Summary changed:

- CCs or SCs cannot be deregistered
+ Doc bug: euca_conf --deregister-sc must be used with a cluster name

** Description changed:

- Installing CLC+Walrus+CC+SC, everything autoregisters properly.
+ According to man page, --deregister-sc takes a "host" as a parameter.
  
- However, if I try to deregister the SC, it doesn't work:
+ Trying:
+ $ sudo euca_conf --deregister-sc <HOSTorIP>
+ SUCCESS: Storage controller for cluster '<HOSTorIP>' successfully 
deregistered.
  
- $ sudo euca_conf --deregister-sc <IP>
- SUCCESS: Storage controller for cluster '<IP>' successfully deregistered.
- $ sudo euca_conf --list-scs
- registered storage controllers:
-     vcloud <IP>
+ However it appears to not change anything.
  
- and no, it's not because autoregistration re-registers it in between :)
- The same goes for a CC (--deregister-cluster and --list-clusters)
- 
- If deregistering a CC or a SC is not supported, then euca_conf should
- not expose --deregister-{sc,cluster}, or should fail with an explanation
- if you try to do so. Note that --deregister-walrus or --deregister-node
- seem to work properly.
+ According to Dan (comment 1) this is a documentation bug (parameter
+ should be the cluster name and not the host). I find the euca_conf
+ SUCCESS message is kinda misleading, since it seems to imply SUCCESS in
+ the deregistration operation, but I can live with that :)

** Changed in: eucalyptus (Ubuntu)
   Importance: Undecided => Low

** Also affects: eucalyptus
   Importance: Undecided
       Status: New

** Changed in: eucalyptus (Ubuntu)
       Status: New => Triaged

-- 
Doc bug: euca_conf --deregister-sc must be used with a cluster name
https://bugs.launchpad.net/bugs/551778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to