Almalinux 9.1 Openebula 6.6.0

I have two community edition Opennebula servers:

  • One 6.4.0 running on Ubuntu 20.04
  • One 6.6.0 running on Almalinux 9.1

I use terraform opennebula provider v1.1.0 to create infrastructure and services which works fine. I have a few issues creating VNF and virtual routes but that’s another story.

The public network I create and attach to VM’s in v6.4.0 works fine but the same in opennebula 6.6.0 running on Almalinux 9.1 cannot cannot ping the outside world. I get name resolution errors. I’m using the Ubuntu 20.04 KVM image downloaded from the Marketplace…

Has anyone else been had any networking issues with Almalinux 9.1?

Another point, opennebula 6.6 cannot be installed on Almalinux 9.1 without first installing mysql libraries.

Lastly in both one v6.4.0 and v6.6.0 I’m not able to open VNC/Guac via sunstone:9869 but I can open via fireedge:2616

drwxr-x---   2 oneadmin oneadmin    286 Jan  9 12:28 .
drwxr-xr-x. 16 root     root       4096 Jan  8 15:03 ..
-rw-r--r--   1 oneadmin oneadmin   4602 Jan  9 12:29 11.log
-rw-r--r--   1 oneadmin oneadmin      0 Jan  9 12:10 fireedge.error
-rw-r--r--   1 oneadmin oneadmin  16502 Jan  9 12:29 fireedge.log
-rw-r--r--   1 oneadmin oneadmin   3574 Jan  9 12:32 monitor.log
-rw-r--r--   1 oneadmin oneadmin    409 Jan  9 12:10 novnc.log
-rw-r--r--   1 oneadmin oneadmin 193863 Jan  9 12:35 oned.log
-rw-r--r--   1 oneadmin oneadmin    225 Jan  9 12:10 oneflow.log
-rw-r--r--   1 oneadmin oneadmin     67 Jan  9 12:10 onegate.log
-rw-r--r--   1 oneadmin oneadmin    170 Jan  9 12:10 onehem.log
-rw-r--r--   1 oneadmin oneadmin   1425 Jan  9 12:29 sched.log
-rw-r--r--   1 oneadmin oneadmin  34803 Jan  9 12:29 sunstone.log
-rw-r--r--   1 oneadmin oneadmin     64 Jan  9 12:10 vcenter_monitor.log

[oneadmin@one-mast-00 one]$ grep -rnwiI -e "ERROR" -e "WARN"

oned.log:324:Mon Jan  9 12:10:14 2023 [Z0][ONE][I]: Log level:3 [0=ERROR,1=WARNING,2=INFO,3=DEBUG,4=DDEBUG,5=DDDEBUG]
fireedge.log:2:[HPM] Subscribed to http-proxy events: [ 'error', 'close' ]
fireedge.log:4: invalid: Error: Token expired
fireedge.log:5:error: 192.168.1.144 - - [09/Jan/2023:12:29:22 +0000] "GET /fireedge/api/user/info HTTP/1.1" 401 35 "http://192.168.1.40:2616/fireedge/sunstone/vm" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36"
[oneadmin@one-mast-00 one]$

If I can’t get it working I suppose I’ll have to revert back to Ubuntu.

Hi,

I’m starting now to test OpenNebula 6.6.0 in a AlmaLinux-9.1 and, as you said, ONE doesn’t install. I get this “mysql libraries” error:


[root@servidor ~]# yum install opennebula opennebula-sunstone opennebula-fireedge opennebula-gate opennebula-flow opennebula-provision
Última comprobación de caducidad de metadatos hecha hace 0:09:05, el jue 19 ene 2023 14:57:35.
Error: 
 Problema 1: conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-6.6.0-1.el9.x86_64
 Problema 2: package opennebula-sunstone-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
 Problema 3: package opennebula-provision-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
 Problema 4: package opennebula-gate-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
 Problema 5: package opennebula-flow-6.6.0-1.el9.noarch requires opennebula-rubygems = 6.6.0, but none of the providers can be installed
  - conflicting requests
  - nothing provides libmysqlclient.so.21()(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
  - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by opennebula-rubygems-6.6.0-1.el9.x86_64
(pruebe a añadir '--skip-broken' para descartar los paquetes que no se pueden instalar o '--nobest' para no tener en cuenta sólo los mejores candidatos)

I think this is a big problem, because I’m running this “fresh install” to test if OpenNebula runs well in a AlmaLinux-9.x, because my OpenNebula cluster runs, now, CentOS7 and there are no “secure” upgrade process to arrive to AlmaLinux-9.x.
I have though in running a “complete fresh installation” but…

Did you resolve compiling manually “mysql libraries”?

Thanks.

Hi,

I add a new comentary in my own question. Finally, it is possible to install OpenNebula 6.6.0 in a AlmaLinux-9.x if you enable “crb” repo in this way:
dnf --enablerepo=crb install opennebula opennebula-sunstone opennebula-fireedge opennebula-gate opennebula-flow opennebula-provision

Bye!

To get past the mysql issue you need to install the following:

First download rpm
mysql80-community-release-el9-1.noarch.rpm

Install using the following commands:
sudo rpm -Uvh mysql80-community-release*rpm
dnf --enablerepo=mysql80-community install mysql80-community-release
sudo dnf --enablerepo=mysql80-community install mysql80-community-release
sudo dnf update

Opennebula should now install
sudo yum -y install opennebula opennebula-sunstone opennebula-fireedge opennebula-gate opennebula-flow opennebula-provision

1 Like

Hi, I’ve setup a public network attached to a running VM but can’t ping the outside world with Opennebula 6.6.0 running on Almalinux 9.1.
Have you been able to get a running vm to ping opennebula.org ?
I just get a name resolution error.

On Almalinux 9.1 the virbr0 bridge is missing and the interface is not a network interface, seems to be the vm instance name

Almalinux 9.1
linux@one-mast-00 ~]$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.fe091a000099 no one-17-0
docker0 8000.02429cfb4f8b no
[linux@one-mast-00 ~]$

Ubuntu 20.04
linux@one-mast-01:~$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.7085c2a64071 yes eno2
docker0 8000.02423db95dbb no
virbr0 8000.52540096a93b yes virbr0-nic
linux@one-mast-01:~$

Any ideas, is this a bug?

I think the issue is with the bridge I have created.
I have used the following link to create the bridge br0 via nmcli command, the bridge is created but I don’t have virbr0.

[linux@one-mast-00 ~]$ nmcli conn show --active
NAME UUID TYPE DEVICE
enp0s31f6 10049f52-c7ee-3ed4-8e71-9779ee6f7eb5 ethernet enp0s31f6
br0 79dd43b5-ae0a-49c4-bad7-9615dcfc0888 bridge br0
docker0 7cff5935-166c-477c-8a2b-aa55cabe9cc2 bridge docker0