Here is the log : https://pad.inria.fr/p/np_IvcpeIGM4BncZEM1
It's a complete 3 minutes start/run/stop.

Thanks for the info about "cs.vmware.api.version*". For 4.11.2, it seems that 
vSphere 6.7 is the target :
pom.xml:    <cs.vmware.api.version>6.7</cs.vmware.api.version>


Florent

----- Mail original -----
> De: "Suresh Kumar Anaparti" <sureshkumar.anapa...@gmail.com>
> À: "users" <users@cloudstack.apache.org>
> Envoyé: Mardi 16 Avril 2019 13:05:20
> Objet: Re: Problem with ACS 4.11.2 and vCenter server

> Hi Florent,
> 
> Log is missing. I think attachments are ignored. Either provide a link to
> access the log or paste the logs in email (few logs of the issue).
> 
> Irrespective of the vCenter version (hard coded in the build param
> *cs.vmware.api.version*), CS would try to connect to the vCenter server.
> 
> - Suresh
> 
> 
> On Tue, Apr 16, 2019 at 2:44 PM Florent Paillot <florent.pail...@inria.fr>
> wrote:
> 
>> Thanks for the answers,
>>
>> Paul : I know that the vCenter 6.7 is not officialy supported but my
>> colleague reported that it worked with 4.9.3 .
>> When you say "cloudstack won't recognise it", is it hard coded ? If the
>> the vCenter auth API doesn't change between 6.5 and 6.7 it should work or
>> at least try to connect to the vCenter.
>>
>> I'm agree with you Suresh, even if CS can't communicate with the vCenter
>> we should see something in the logs or in the packet capture.
>>
>> I am able to ping and telnet from the CS controller to the vCenter on port
>> 443 (and I see the packet with tcpdump).
>>
>> The log is in attachement.
>>
>> Florent
>>
>>
>> ----- Mail original -----
>> > De: "Suresh Kumar Anaparti" <sureshkumar.anapa...@gmail.com>
>> > À: "users" <users@cloudstack.apache.org>
>> > Envoyé: Lundi 15 Avril 2019 17:54:00
>> > Objet: Re: Problem with ACS 4.11.2 and vCenter server
>>
>> > Hi Florent, What was the CS behavior & vCenter/ESXi hosts connectivity
>> > status before upgrade to 4.11.2 from 4.9.3? Have you upgraded vCenter as
>> > well? Are you able to ping vCenter from CS management server?
>> >
>> > Even vCenter 6.7 is not recognised, CS would try to connect with the
>> > details specified, which is logged. Have you enabled debug logs?
>> >
>> > - Suresh
>> >
>> > On Mon, Apr 15, 2019 at 7:38 PM Paul Angus <paul.an...@shapeblue.com>
>> wrote:
>> >
>> >> Ah. vCenter 6.7 isn't supported yet, cloudstack won't recognise it.
>> >>
>> >> paul.an...@shapeblue.com
>> >> www.shapeblue.com
>> >> Amadeus House, Floral Street, London  WC2E 9DPUK
>> >> @shapeblue
>> >>
>> >>
>> >>
>> >>
>> >> -----Original Message-----
>> >> From: Florent Paillot <florent.pail...@inria.fr>
>> >> Sent: 15 April 2019 14:26
>> >> To: users <users@cloudstack.apache.org>
>> >> Subject: Re: Problem with ACS 4.11.2 and vCenter server
>> >>
>> >> Hi Suresh,
>> >> The vCenter is a 6.7u2 (last build).
>> >>
>> >> There is no issue log, that the problem... I don't see any error message
>> >> concerning a failed connection to the vCenter and CS does not seems to
>> send
>> >> any packet to the vCenter.
>> >>
>> >> Florent
>> >>
>> >>
>> >> ----- Mail original -----
>> >> > De: "Suresh Kumar Anaparti" <sureshkumar.anapa...@gmail.com>
>> >> > À: "users" <users@cloudstack.apache.org>
>> >> > Envoyé: Lundi 15 Avril 2019 15:10:44
>> >> > Objet: Re: Problem with ACS 4.11.2 and vCenter server
>> >>
>> >> > Hi Florent,
>> >> >
>> >> > Can you share the vCenter version and build details. Also, the
>> >> > cloudstack management server log with the issue logs while connecting
>> to
>> >> vCenter.
>> >> >
>> >> > - Suresh
>> >> >
>> >> > On Mon, Apr 15, 2019 at 6:24 PM Paul Angus <paul.an...@shapeblue.com>
>> >> wrote:
>> >> >
>> >> >> Assuming that you have updated the core code to recognise and use
>> >> 'newer'
>> >> >> libraries/SDKs than the ones currently in use (and thoroughly tested
>> >> >> it) then, please do create a pull request.  Otherwise, I personally
>> >> >> would advise that you leave things 'as-is' to get the most stable
>> >> experience.
>> >> >>
>> >> >> I don't *think* that you need to run
>> >> >>
>> >> >> mvn clean
>> >> >> mvn install -Dnoredist
>> >> >>
>> >> >> *After* installing the non-oss components.
>> >> >>
>> >> >> You might want to do a mvn clean before you start.
>> >> >>
>> >> >> It's been a while since I've done it manually now.
>> >> >>
>> >> >>
>> >> >>
>> >> >> paul.an...@shapeblue.com
>> >> >> www.shapeblue.com
>> >> >> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> -----Original Message-----
>> >> >> From: Florent Paillot <florent.pail...@inria.fr>
>> >> >> Sent: 15 April 2019 13:17
>> >> >> To: users <users@cloudstack.apache.org>
>> >> >> Subject: Re: Problem with ACS 4.11.2 and vCenter server
>> >> >>
>> >> >> Yes, this is the list of the files in deps/ :
>> >> >> cloud-iControl.jar  cloud-netscaler-sdx.jar  iControl-12.1.0.jar
>> >> >> install-non-oss.sh  manageontap.jar  vim25_51.jar  vim25_55.jar
>> >> >> vim25_60.jar  vim25_65.jar  vim25_67.jar
>> >> >>
>> >> >>
>> >> >> I had to add the following lines to "install-non-oss.sh" to get the
>> >> build
>> >> >> pass :
>> >> >>
>> >> >> mvn install:install-file -Dfile=vim25_67.jar
>> >> >> -DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim25
>> >> -Dversion=6.7
>> >> >>  -Dpackaging=jar
>> >> >> mvn install:install-file -Dfile=iControl-12.1.0.jar
>> >> >>  -DgroupId=com.cloud.com.f5     -DartifactId=icontrol
>> >> >> -Dversion=12.1  -Dpackaging=jar
>> >> >>
>> >> >> I can open a PR or an issue if it makes sense.
>> >> >>
>> >> >> Florent
>> >> >>
>> >> >> --
>> >> >> Florent PAILLOT
>> >> >> SESI - Cellule architecture
>> >> >>
>> >> >> INRIA Bordeaux -Sud-Ouest
>> >> >> 05.24.57.41.25
>> >> >>
>> >> >> ----- Mail original -----
>> >> >> > De: "Paul Angus" <paul.an...@shapeblue.com>
>> >> >> > À: "users" <users@cloudstack.apache.org>
>> >> >> > Envoyé: Lundi 15 Avril 2019 14:10:21
>> >> >> > Objet: RE: Problem with ACS 4.11.2 and vCenter server
>> >> >>
>> >> >> > When packaging, did you install all of the nonoss libraries  into
>> the
>> >> >> > build before packaging?  including vmware-vim25-6.5.jar
>> >> >> >
>> >> >> > paul.an...@shapeblue.com
>> >> >> > www.shapeblue.com
>> >> >> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > -----Original Message-----
>> >> >> > From: Dag Sonstebo <dag.sonst...@shapeblue.com>
>> >> >> > Sent: 15 April 2019 12:43
>> >> >> > To: users@cloudstack.apache.org
>> >> >> > Subject: Re: Problem with ACS 4.11.2 and vCenter server
>> >> >> >
>> >> >> > Florent,
>> >> >> >
>> >> >> > Not aware of any issues but I'm no packaging expert so will let
>> others
>> >> >> > respond to this.
>> >> >> >
>> >> >> > However - any reason you're not just using the RPM repositories
>> rather
>> >> >> > than packaging yourself?
>> >> >> >
>> >> >> > Regards,
>> >> >> > Dag Sonstebo
>> >> >> > Cloud Architect
>> >> >> > ShapeBlue
>> >> >> >
>> >> >> >
>> >> >> >On 15/04/2019, 11:46, "Florent Paillot" <florent.pail...@inria.fr>
>> >> >> wrote:
>> >> >> >
>> >> >> >    Hi everyone,
>> >> >> >    We have a problem with our test environment running ACS 4.11.2
>> on
>> >> >> CentOS 7, not
>> >> >> >    communicating with a vCenter (upgraded from 4.9.3 to 4.11.2 and
>> >> >> CentOS 6 o
>> >> >> >    CentOS 7). We have no problems with our KVM host.
>> >> >> >    Our production is using 4.9.3 o, Centos 6 and everything is OK.
>> >> >> >
>> >> >> >    I used tcpdump and see nothing going out from the management
>> server
>> >> >> to the
>> >> >> >    vCenter or the ESXi host.
>> >> >> >
>> >> >> >    Could it be a package building problem or a vmware module
>> loading?
>> >> >> >
>> >> >> >    I used the following commands to build the packages :
>> >> >> >    install-non-oss.sh
>> >> >> >    mvn clean
>> >> >> >    mvn install -Dnoredist
>> >> >> >    package.sh -p noredist -d centos7
>> >> >> >
>> >> >> >
>> >> >> >    On the production server I see a :
>> >> >> >
>> >> >>
>> >>
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vmware-vim25-6.0.jar
>> >> >> >    file.
>> >> >> >    I can't find it on the test environnement, is it linked to
>> jetty ?
>> >> >> >
>> >> >> >    Any help is welcome :)
>> >> >> >    Regards,
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > dag.sonst...@shapeblue.com
>> >> >> > www.shapeblue.com
>> >> >> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue

Reply via email to