OpenNebula 5.8.2 RPM packages


so it seems that opennebula 5.8.2 has been released on github for 26 days now but there are still no RPM packages available on , what’s the planning on releasing these?


Hi Anton,

I’m trying to build from sources too, on CentOS 7, but I’ve got this error:

econe-stop-instances(1) -- Stops a set of virtual machines
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- AWS (LoadError)
        from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /tmp/tmp.tnCGC7iGih/lib/ruby/cloud/econe/EC2QueryClient.rb:25:in `<top (required)>'
        from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /tmp/tmp.tnCGC7iGih/bin/econe-stop-instances:32:in `<main>'
     roff: ./econe-stop-instances.1                   
     html: ./econe-stop-instances.1.html                     +man,toc

gem install aws doesn’t seem to fix that. Do you know what provides this AWS ? Not a big deal, it only concerns man pages. Who reads the doc anyway :wink:

And following the official documentation about building from sources, it is said to remove node_modules from public sunstone directory. But in the official rpm packages, they are still present. Which one is wrong ?

[ONE2][root@node01 ~]# rpm -ql opennebula-sunstone|grep node_modules|wc -l

it’s a lot of files !

Best regards,

Hi @madko

You should compile information from the docs, opennebula sources and the script that create the packages. The truth usually is somewhere between them :). Usually the procedure described in OpenNebula/packages repo and their scripts do the job. (But don’t forget to checkout the release of the packages that match OpenNebula’s release)

Hope this helps.

Best Regards,
Anton Todorov

I’m following information from is that correct ?


rm -rf node_modules/

So I don’t understand why those files are in the official RPM ?

should I open a ticket for that ?

There is also git:// in bower dependencies that is not a good idea. Because most of the companies are behind web proxies. So we are using this URL as an alternative.

Hi @madko,

If you feel something is not righ - just open an issue, the developers will followup with comments is this a bug or not :slight_smile:

Best Regards,
Anton Todorov