Oneiric: Upgrade to 2.0.1+bzr1256 blocks

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I think that I might be seeing the same issue on a fresh install;

In my case I can see "wget -q -T10 -t1 -O- --no-check-certificate https://192.168.1.52:8443/register" in the process listing - which appears to be what is causing the hang.

This is in the post-start upstart configuration for eucalyptus-cloud.

I can get a response from it manually either.

/can/can't/

I confirm James finding, I have the wget running as well.

For the record, I killed the post instll script 'eucalyptus-common.postinst', leaving eucalyptus unconfigured to proceed working on the system.

This issue might be related:

  https://features.opensuse.org/311066

OpenSUSE have had compatibility issues between openssl 1.0 and eucalyptus - potentially related to bouncycastle.

  https://bugzilla.redhat.com/show_bug.cgi?id=663136

This would align with some of the behaviour I have seen - after a period of time I can connect to https://hostnane:8443 using a browser or using curl/wget on a natty install.

However wget/curl won't work on the euca install itself.

Graziano

Any comment on #13 relating to compatibility between eucalyptus and openssl1.0?

Hello James,

indeed that rings a bell: OpenSUSE proposed a patch. I am looking for their page, but right now I cannot find it. I will update the ticket later on with the full link to it. But for now I seem to recall that using the option --secure-protocol= with wget may solve the problem.

James,

I found the link https://build.opensuse.org/package/view_file?file=eucalyptus-force-sslv3.patch&package=eucalyptus&project=Virtualization%3ACloud%3AEucalyptus&srcmd5=603fc985140105bd4ed7a079a4dc7258

James,

going through the bugs now, and I noticed that in 851900 you used curl. The patch here is for wget, but I assume you already know that with curl you could use the --sslv3 to force the use of a specific protocol.

Hi Graziano

I hacked this into my broken install and it appears todo the trick.

I'll work on a update to the packaging.

This bug was fixed in the package eucalyptus - 2.0.1+bzr1256-0ubuntu8

---------------
eucalyptus (2.0.1+bzr1256-0ubuntu8) oneiric; urgency=low

  * Fix compatibility issues with SSLv3 (LP: #851611):
    - d/patches/29-euca_conf-sslv3.patch: Use --secure-protocol=SSLv3
      with wget when communicating with CLC.
    - d/eucalyptus-cloud.upstart: Use --secure-protocol=SSLv3 with wget
      when checking for CLC startup complete.
  * d/patches/30-clock_drift.patch: Resolve issue with rampart blocking
    communication between CC and NC when time is fractionally in the
    future (LP: #854946):
 -- James Page <email address hidden> Wed, 21 Sep 2011 09:57:58 +0100

I just updated and still have a hanging wget:

...
Setting up kdepim-runtime (4:4.7.1-0ubuntu3) ...
Setting up libcouchdb-glib-1.0-2 (0.7.4-0ubuntu2) ...
Setting up libdesktopcouch-glib-1.0-2 (0.7.4-0ubuntu2) ...
Setting up oneconf (0.2.6.4) ...
Setting up software-center (4.1.23.4) ...
Updating software catalog...this may take a moment.
Software catalog update was successful.
Setting up eucalyptus-admin-tools (2.0.1+bzr1256-0ubuntu8) ...
Setting up eucalyptus-common (2.0.1+bzr1256-0ubuntu8) ...
eucalyptus start/running, process 8050

$ ps aux | grep wget
root 8873 0.0 0.0 27720 2304 ? S 08:29 0:00 wget -q -T10 -t1 -O- --no-check-certificate https://192.168.1.122:8443/register
spindler 10716 0.0 0.0 12040 900 pts/2 S+ 10:00 0:00 grep --color=auto wget

Unfortunately killing the wget in a loop is now not continuing the eucalyptus start job. Also calling 'sudo stop eucalyptus' failed to change anything, the eucalyptus start job is hanging.

It seems that the patch was not applied: wget should be called with --secure-protocol=SSLv3 and in your ps it didn't show.

Is any log produced?

The error seems to have been transient. I killed the hanging eucalyptus postinst process and I got no further hang.

If you see it again, please check if logs are generated and if there are errors. I wonder if this is a race condition, so it would be interesting to see at which level is this happening.