stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "manas padegaonkar (JIRA)" <>
Subject [jira] [Resolved] (STRATOS-602) vCloud: Stratos Manager Unable To Push Payload to Cartridge VM
Date Tue, 15 Apr 2014 05:12:18 GMT


manas padegaonkar resolved STRATOS-602.

       Resolution: Done
    Fix Version/s: 4.0.0 RC1

I raised this jira because I was getting following error:--

"NullPointerException on node
java.lang.NullPointerException: no credential found for root on node"

The above error was due to unavailability of VMware Tools on the cartridge image (Stratos
Cartridge preparation document for vCloud never talks about such pre-requisite).

After installing VMware tools I land up on another blocker & started getting forllowing

"TID: [0] [STRATOS] [2014-04-12 09:23:28,875] DEBUG {jclouds.compute} -  >> blocking
on sockets [] for 600000 MILLISECONDS {jclouds.compute}
TID: [0] [STRATOS] [2014-04-12 09:23:28,879]  WARN {jclouds.compute} -  Error checking reachability
of ip:port {jclouds.compute}"

This error was because of the Java version (jdk7u51) installed on Stratos Manager. After downgrading
the java to jdk7u21 payload is getting pushed into the Cartridge VM using the customization


> vCloud: Stratos Manager Unable To Push Payload to Cartridge VM
> --------------------------------------------------------------
>                 Key: STRATOS-602
>                 URL:
>             Project: Stratos
>          Issue Type: Bug
>          Components: Stratos Manager
>    Affects Versions: 4.0.0 RC1
>         Environment: IaaS: vCloud
> Stratos Manager underlying OS: Ubuntu 12.04 Server
> Cartridge Underlying OS: Ubuntu 12.04 
>            Reporter: manas padegaonkar
>            Priority: Blocker
>              Labels: customization-script, payload, vcloud
>             Fix For: 4.0.0 RC1
>         Attachments: vcloud-wso2carbon.log
> Followed the documentation to configure Stratos Manager & Cartridge & successfully
subscribed to the tomcat cartridge but I can see that the customization script is not passing
the PAYLOAD information from Manager to the Cartridge VM.

This message was sent by Atlassian JIRA

View raw message