Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: UEC broken with upgrade.

  1. #1
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    UEC broken with upgrade.

    Hi guys,

    I've been directed here from the Meerkat forum...

    I just upgraded my UEC cloud to meerkat to try and use the eucalyptus 2.0 tools that are installed within it (as I couldn't find them in a 10.04 package).

    The install appears to have gone OK, but now my cloud in broken..

    I can't seem to register any clusters even though the logs seem to indicate that they are working OK and are being seen by the CC.

    When I try and log into the front end on the CC I get an error:

    "The call failed on the server; see server logs for details"

    I've looked in the logs and can't really see anything that makes sense, however, when I do a

    euca-describe-clusters

    I get..

    Traceback (most recent call last):
    File "/usr/sbin/euca-describe-clusters", line 4, in <module>
    from euca_admin.clusters import Cluster
    ImportError: No module named euca_admin.clusters

    and other describe-* commands return similar problems. This looks like an issue to me.. but I'm not sure where to start looking to try get tis going again.

    I have got around the front end error by resetting my password, but I still can't seem to register the nodes. There are no "VM Types" on the configuration page either but, I'm assuming that this is because of the nodes not being registered correctly.

    The odd thing is that when I do a

    sudo euca_conf --no-rsync --discover-nodes

    The two node controllers are discovered, but they are reported by IPV6 address rather that IPV4 as they were in UEC 1.6. Is that causing the issues?

    Ta

    Peter.

  2. #2
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    Re: UEC broken with upgrade.

    Testing testing 123? Anyone home??

  3. #3
    Join Date
    Apr 2010
    Beans
    92

    Re: UEC broken with upgrade.

    I'd like to help. I have not tried nor downloaded Meerkat yet. I assume installs are fresh and clean. I'll try looking at it today. Is the UEC install the same as Lucid (from the CD/live or must you install UEC over an existing system)?

  4. #4
    Join Date
    Sep 2010
    Beans
    6

    Re: UEC broken with upgrade.

    I have never tried Meerkat but I read that it is officially released in October 2010, maybe you have a RC?
    In any case, I would never upgrade and will just do a new install. Please let us know how it goes.
    Vahid.

  5. #5
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    Re: UEC broken with upgrade.

    OK, thanks guys.

    These were done as updates to the existing systems, so I will blow them away and try again.

    It seems the CC and Walrus is up OK but I simply cannot get the nodes to register.

    Peter.

  6. #6
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    Re: UEC broken with upgrade.

    OK, this is totally broken.

    I have just re-installed the CC and NC's afresh from the 10.10 disk and I shill have no nodes registered.

    The front end seems to work, although I can't download any images from the store (it comes up with "Bad request signature" on any image I try to install).

    When I do sudo euca_conf --no-rsync --discover-nodes on the CC I get the nodes appearing with IP6 addresses (most of the time, its not consistent) but the keys cannot be installed, even though I tried adding the credentials manually (doesn't seem to be setting up the eucalyptus user correctly).

    I tried disabling IP6 on the CC and NC's, but now I don't even see the nodes when I don the discover-nodes.

    Did anyone actually test this before pushing out the Beta? Is there a way I can upgrade a 10.04 (which mostly works) to 2.0 without breaking it? Or.. do I give up on UEC entirely and go to a supported (by eucalyptus) distro?

    I'm really starting to take some heat on this now.. any help would be GREATLY appreciated.

    Peter.

  7. #7
    Join Date
    Apr 2010
    Beans
    92

    Re: UEC broken with upgrade.

    Peter,
    What a bummer. Here are a few guesses: using euca_conf try:
    --deregister-nodes "host host ..." remove nodes from EUCALYPTUS
    --deregister-cluster <clustername> remove cluster from EUCALYPTUS
    --register-cluster <clustername> <host> add new cluster to EUCALYPTUS
    You reinstalled the CC and NC, but you did not say anything about the CLC. It might still be holding on to something.
    Keep us posted.

  8. #8
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    Re: UEC broken with upgrade.

    OK, slow progress...

    I've managed to get the nodes registered using

    euca_conf --register-nodes "192.168.123.82"

    I have now restored my bukkits and volumes from the 1.6 version, BUT, how do I register the images in these bukkits. The xml file is now in some compressed? format in the bukkit so I can't use register-image etc...

    Ta.

    Peter.

  9. #9
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    Re: UEC broken with upgrade.

    OK, I've decided to give up on the restore of the images (not that important anyway).

    I've managed to install an image from the store (had to log in as Admin to do it) and now have an image running... but I can't connect to it.. sigh.

    I can ping it from the CC (not from elsewere in the network) but I can't connect to it.

    ssh -vvv -i id-pnunn ubuntu@192.168.124.101
    OpenSSH_5.5p1 Debian-4ubuntu3, OpenSSL 0.9.8o 01 Jun 2010
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for *
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to 192.168.124.101 [192.168.124.101] port 22.
    debug1: Connection established.
    debug3: Not a RSA1 key file id-pnunn.
    debug2: key_type_from_name: unknown key type '-----BEGIN'
    debug3: key_read: missing keytype
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug2: key_type_from_name: unknown key type '-----END'
    debug3: key_read: missing keytype


    Been looking all over google for this one, but turning up a blank.

  10. #10
    Join Date
    Aug 2005
    Location
    Melbourne Australia
    Beans
    34

    Re: UEC broken with upgrade.

    OK.. this is still crazy.. got the keys working by removing the old keys from authorized_keys.. but now I can't see any volumes attached to the running instance.

    It says its attached, but it doesn't appear in /dev/

    Now what??

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •