Hi Carlos, Boris,
Carlos, thanks a lot for opening a ticket about it.
About the nokogiri gem version, it is the following one:
[oneadmin@cloud ~]$ gem list | grep nokogiri
nokogiri (1.5.10)
Yes, as Boris said, this is the only broken pool for us.
Please, let me know if you need anything else.
Thanks,
Esteban
On 30/06/14 10:59, Carlos Martín Sánchez wrote:
Hi,
On Thu, Jun 26, 2014 at 1:19 PM, Boris Parak <256...@mail.muni.cz
<mailto:256...@mail.muni.cz>> wrote:
Hi Javi, Esteban,
this issue might be related to the upgrade process from 4.4 (or 4.2)
to 4.6, I wasn't able to reproduce it in clean 4.6 installations.
Cheers, Boris
I just opened a ticket to solve this:
http://dev.opennebula.org/issues/3014
Boris, Esteban: Can you please tell me your nokogiri gem version?
Also, Esteban said this only happened for the group pool. Was this the
only broken pool for you too, Boris?
Thanks,
Carlos
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org <http://www.opennebula.org/> |
cmar...@opennebula.org <mailto:cmar...@opennebula.org> | @OpenNebula
<http://twitter.com/opennebula>
On Thu, Jun 26, 2014 at 1:16 PM, Esteban Freire <esfre...@cesga.es
<mailto:esfre...@cesga.es>> wrote:
> Hi Javi,
>
> No, we only have found this issue with onegroup list --xml
command, other
> pools seem to be OK . Boris Parak from CESNET (in CC) also have
found the
> same issue.
>
> I send you the required output :
>
> [oneadmin@cloud ~]$ ruby --version
> ruby 1.9.3p545 (2014-02-24 revision 45159) [x86_64-linux]
>
> [oneadmin@cloud ~]$ gem list
>
> *** LOCAL GEMS ***
>
> activesupport (3.2.14)
> amazon-ec2 (0.9.17)
> antlr3 (1.9.2)
> aws-sdk (1.15.0)
> backports (3.3.3)
> bigdecimal (1.1.0)
> builder (3.2.2)
> bundler (1.6.3, 1.5.3)
> bundler-unload (1.0.2)
> curb (0.8.5)
> daemon_controller (1.1.5)
> daemons (1.1.9)
> diff-lcs (1.2.4)
> erubis (2.7.0)
> eventmachine (1.0.3)
> executable-hooks (1.3.1)
> gem-wrappers (1.2.4)
> hashie (1.2.0)
> highline (1.6.19)
> httparty (0.11.0)
> i18n (0.6.5)
> io-console (0.3)
> json (1.8.0, 1.5.5)
> memcache-client (1.8.5)
> minitest (2.5.1)
> multi_json (1.7.9)
> multi_xml (0.5.5)
> mysql (2.9.1)
> net-ldap (0.6.0)
> nokogiri (1.5.10)
> oca (3.4.1)
> occi (2.5.19)
> ox (2.1.1)
> parse-cron (0.1.4)
> passenger (4.0.13)
> polyglot (0.3.4)
> rack (1.5.2)
> rack-protection (1.5.0)
> rack-test (0.6.2)
> rake (10.1.0, 0.9.2.2)
> rdoc (3.9.5)
> rspec (2.14.1)
> rspec-core (2.14.5)
> rspec-expectations (2.14.2)
> rspec-http (0.10.0)
> rspec-mocks (2.14.3)
> rubygems-bundler (1.4.2)
> rvm (1.11.3.9)
> sequel (4.9.0)
> simplecov (0.7.1)
> simplecov-html (0.7.1)
> sinatra (1.3.6)
> sinatra-contrib (1.3.2)
> sinatra-cross_origin (0.2.0)
> sqlite3 (1.3.9)
> thin (1.6.2)
> tilt (1.4.1)
> treetop (1.5.3)
> trollop (2.0)
> uuidtools (2.1.4)
> xml-simple (1.1.2)
> xmlparser (0.7.2.1)
> yard (0.8.7)
> yard-sinatra (1.0.0)
> [oneadmin@cloud ~]$
>
> Thanks in advance,
> Esteban
>
>
> On 06/26/2014 12:41 PM, Javier Fontan wrote:
>>
>> I am not able to reproduce it. Does it also happen with other pools
>> like VMs or images?
>>
>> We need the output of these commands to investigate further:
>>
>> $ ruby --version
>> $ gem list
>>
>> Cheers
>>
>> On Thu, Jun 26, 2014 at 11:36 AM, Esteban Freire
<esfre...@cesga.es <mailto:esfre...@cesga.es>>
>> wrote:
>>>
>>> Hi all,
>>>
>>> Probably, this is already a known bug, but in any case, I
would like to
>>> let
>>> you know that onegroup list --xml is not showing a valid XML
document
>>> after
>>> upgrading to 4.6.* from previous versions:
>>>
>>> If you take a look to the output for onegroup list --xml
command, it
>>> appears
>>> the following:
>>>
>>> <GROUP_POOL><?xml version="1.0"?>
>>>
>>> As you can see, it would have to be:
>>>
>>> <?xml version="1.0"?>
>>> <GROUP_POOL>
>>>
>>> Also, there are other "<?xml version="1.0"?>" in the output
which break
>>> its
>>> functionality.
>>>
>>> For now, we are executing the following workaround to get a
valid XML
>>> document:
>>>
>>> onegroup list --xml | sed 's/<?xml version="1.0"?>//'
>>>
>>> Do you know when it could be solved? I know it is not a
critical bug but
>>> it
>>> would be great if someone could take a look on it.
>>>
>>> Thanks in advance,
>>> Esteban
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users@lists.opennebula.org <mailto:Users@lists.opennebula.org>
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>>
>
>
> --
> ++-------------------------++
> Esteban Freire García
> Centro de supercomputación de Galicia
> Avda. de Vigo s/n. Campus Vida
> 15705 - Santiago de Compostela. Spain
> Tlfn.: 981 56 98 10 Extension:274
> Fax: 981 59 46 16
>
_______________________________________________
Users mailing list
Users@lists.opennebula.org <mailto:Users@lists.opennebula.org>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
++-------------------------++
Esteban Freire García
Centro de supercomputación de Galicia
Avda. de Vigo s/n. Campus Vida
15705 - Santiago de Compostela. Spain
Tlfn.: 981 56 98 10 Extension:274
Fax: 981 59 46 16
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
