Re: Unable to import Server from Eucalyptus 3.2

[Sebastian Stadil]

Welcome to the community, Colby!

To everyone else: Colby is part of the Eucalyptus team, and if there's someone on this list that wants to hit him up with questions, feel free to do so.

To Scalr team: the problem Colby ran into was encountered on the latest code running on hosted Scalr.

On Thu, Feb 28, 2013 at 11:40 AM, Colby Dyess <colby...@eucalyptus.com> wrote:

The goal this afternoon was to validate that Scalr works with Eucalyptus 3.2. I am using the Community Cloud to do this. The first task was to create a Role, which required that I import a Server. This task failed.

A snapshot of the Bundle Task screen shows below. The instance on which I executed the scalarizr command appears to be stuck waiting to complete the scalarizr work. I assume I can kill the process.

Any advice on how to debug / resolve this?

--
You received this message because you are subscribed to the Google Groups "scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalr-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Follow us: Twitter - Facebook - Blog

[Colby Dyess]

Hoping to get some sort of response, even a RTFM kind of pointer.

Thanks,

- Colby

[Nick Toursky]

Hi Colby,

An error message you see means that Scalr was unable to send a message to Scalarizr running on the server you're trying to import.

Usual checklist would be to check connectivity from Scalr server to instance's port tcp/8013, then looking through Scalarizr logs (especially debug one, /var/log/scalarizr_debug.log). Also, I've found out that after unsuccessful import attempt Scalarizr leaves some config files which prevent server from importing on further attempts. Solution would be to remove Scalarizr packages completely (e.g. `dpkg -p` on Debian/Ubuntu) and reinstall.

Let me know if that helps.

Regards,

Nick

[Igor Savchenko]

Hi Colby,

Welcome to the community. I want to mention that Eucalyptus support is a bit outdated. During the last couple month we were focused on internals refactoring and adding new clouds. During this refactoring sprint, we focused on the clouds we had customers and users for, which unfortunately did not include Eucalyptus  So right now managing cloud based on Euca can be a bit unstable.

Within the next couple months we will be focused on our current roadmap - Audit Logs, Collaboration tools, etc. After this we have plans to get back to the Eucalyptus support if will see a demand for this.

Regards,

Igor

[Colby Dyess]

Nick,

I will retry later today, making sure to verify that the required port is open. Thank you for the suggestion. 

- Colby

m: 617.615.6528

You received this message because you are subscribed to a topic in the Google Groups "scalr-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scalr-discuss/1_Ey9Q4pULQ/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to scalr-discus...@googlegroups.com.

[Colby Dyess]

Igor,

Yep, I understand that the Euca support went stale. My goal was to see what, if anything, still works. Hopefully if the gap is small we might collaborate on bringing things back to full support. Or maybe there could be a community supported option.

- Colby

m: 617.615.6528

You received this message because you are subscribed to a topic in the Google Groups "scalr-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scalr-discuss/1_Ey9Q4pULQ/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to scalr-discus...@googlegroups.com.

[Sebastian Stadil]

Would love for that to happen. :-)

[Colby Dyess]

Hi all,

Just a quick update. We opened the ports per the documentation and Nick's advice. We then discovered that the clock on our instance was out of whack and installed NTP to correct it. Then we uninstalled and re-installed scalrizer, also per Nick.

Scalr still failed to import a Eucalyptus server, but at least a different message appeared in the log (see snippet below).

Is there something more that can be done from our side to help resolve this?

--------------------------------------------------------------------------------

2013-03-12 21:48:12,040 - DEBUG - scalarizr.messaging.p2p.producer - Sending message 'RebundleLog' into queue 'log'

2013-03-12 21:48:12,157 - DEBUG - scalarizr.messaging.p2p.producer - Delivering message 'RebundleLog' <?xml version="1.0" encoding="utf-8"?><message id="9f55600b-a02d-4286-9a3e-c3c7114994bf" name="RebundleLog"><meta><szr_version>0.13.7</szr_version><server_id>be972ce1-d249-4c62-b54f-1b5482b82896</server_id><timestamp>Wed 13 Mar 2013 01:48:12 EST</timestamp></meta><body><message>Failed to find instance %s. If you are importing this server, check that you are doing it from the right Scalr environment</message><bundle_task_id>41939</bundle_task_id></body></message>

2013-03-12 21:48:12,157 - DEBUG - scalarizr.messaging.p2p.security - Encrypting message

2013-03-12 21:48:12,518 - DEBUG - scalarizr.messaging.p2p.producer - Message 'RebundleLog' delivered (message_id: 9f55600b-a02d-4286-9a3e-c3c7114994bf)

2013-03-12 21:48:12,040 - ERROR - scalarizr.handlers.rebundle - Failed to find instance %s. If you are importing this server, check that you are doing it from the right Scalr environment

Traceback (most recent call last):

  File "/usr/lib/python2.6/site-packages/scalarizr/handlers/rebundle.py", line 120, in on_Rebundle

    self.before_rebundle()

  File "/usr/lib/python2.6/site-packages/scalarizr/handlers/ec2/rebundle.py", line 105, in before_rebundle

    raise HandlerError(msg)

HandlerError: Failed to find instance %s. If you are importing this server, check that you are doing it from the right Scalr environment

2013-03-12 21:48:12,585 - DEBUG - scalarizr.messaging.p2p.producer - Sending message 'RebundleResult' into queue 'control'

2013-03-12 21:48:12,701 - DEBUG - scalarizr.messaging.p2p.producer - Delivering message 'RebundleResult' <?xml version="1.0" encoding="utf-8"?><message id="2614a618-948f-4d74-bced-3dd3f6d6e270" name="RebundleResult"><meta><szr_version>0.13.7</szr_version><server_id>be972ce1-d249-4c62-b54f-1b5482b82896</server_id><timestamp>Wed 13 Mar 2013 01:48:12 EST</timestamp></meta><body><status>error</status><last_error>Failed to find instance %s. If you are importing this server, check that you are doing it from the right Scalr environment</last_error><bundle_task_id>41939</bundle_task_id></body></message>

2013-03-12 21:48:12,701 - DEBUG - scalarizr.messaging.p2p.security - Encrypting message

2013-03-12 21:48:13,050 - DEBUG - scalarizr.messaging.p2p.producer - Message 'RebundleResult' delivered (message_id: 2614a618-948f-4d74-bced-3dd3f6d6e270)

2013-03-12 21:48:13,166 - DEBUG - scalarizr.handlers.hooks - Hook on 'rebundle_error'() {'last_error': 'Failed to find instance %s. If you are importing this server, check that you are doing it from the right Scalr environment', 'role_name': 'EucaFirstRole'}

2013-03-12 21:48:13,167 - DEBUG - scalarizr.messaging.p2p.consumer - Mark message (message_id: ec23272c-a579-4e4a-a974-60f34355cf51) as handled

2013-03-12 21:48:19,076 - DEBUG - scalarizr.messaging.p2p.producer - Sending message 'Log' into queue 'log'

2013-03-12 21:48:19,193 - DEBUG - scalarizr.messaging.p2p.security - Encrypting message

-------------------------------------------------------------------------------------------------

To unsubscribe from this group and stop receiving emails from it, send an email to scalr-discuss+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to a topic in the Google Groups "scalr-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scalr-discuss/1_Ey9Q4pULQ/unsubscribe?hl=en-US.

To unsubscribe from this group and all its topics, send an email to scalr-discuss+unsubscribe@googlegroups.com.