Error executing Hpe-vm Manager

[Edgar3]

I'm unable to complete the Manager's configuration; the logs don't go beyond what's shown below. It reaches 99% and then stops there.

Unable to connect to https//my.dominio.local/ping. Trying again in 15 seconds...java.net.ConnectException: Connection refused
at java.base@21.0.4/sun.nio.ch.Net.connect0(Native Method)
at java.base@21.0.4/sun.nio.ch.Net.connect(Net.java:589)
at java.base@21.0.4/sun.nio.ch.Net.connect(Net.java:578)
at java.base@21.0.4/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:583)
at java.base@21.0.4/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base@21.0.4/java.net.Socket.connect(Socket.java:751)
at java.base@21.0.4/java.net.Socket.connect(Socket.java:686)
at java.base@21.0.4/java.net.Socket.<init>(Socket.java:555)
at java.base@21.0.4/java.net.Socket.<init>(Socket.java:324)
at com.morpheusdata.mvm.console.util.MvmUtility.waitForWebappSocket(MvmUtility.java:566)
at com.morpheusdata.mvm.console.InstallMorpheus.lambda$show$8(InstallMorpheus.java:454)
at java.base@21.0.4/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base@21.0.4/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base@21.0.4/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base@21.0.4/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base@21.0.4/java.lang.Thread.runWith(Thread.java:1596)
at java.base@21.0.4/java.lang.Thread.run(Thread.java:1583)
at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.j>
at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.j>

[pkbin]

Hi @Edgar3 
Could you please check if  your Manager name is resolvable ?
#nslookup  my.dominio.local
// Also try to check following details.
#virsh list   <== Check if the Manager VM is running
#ping my.dominio.local  <== Check if the Manager's IP is accessible, if it is running

Based on the above results, we can check further on this.

Thanks

[Edgar3]

When executing virsh list --all, the tests with ping and nslookup show the state as 'shut off'. The DNS name resolution and ping are successful

[pkbin]

Are you sure, the ping is successful ?
When the VM is in shut-off state, I would not expect ping for the manager VM should be happening.
Anyway kindly start the VM manually and see what exact error being reported?
#virsh start  VMEMANAGER_NAME
Provide the below outputs as well
#virsh list --all
#virsh net-list --all
#ovs-vsctl show
#ip a
#cat /etc/netplan/*.yaml

[Edgar3]

root@hvme:~# virsh list --all
Id Name State
--------------------------
- hvme shut off
- vme shut off
- vmecass shut off

root@hvme:~# virsh net-list --all
Name State Autostart Persistent
-------------------------------------------------
default inactive yes yes
Management inactive yes yes

root@hvme:~# ovs-vsctl show
5cc6b8b8-7019-4dd0-9692-c3b413a71646
ovs_version: "3.3.0"

root@hvme:/etc/netplan# cat 60-mvm.yaml
network:
version: 2
ethernets:
eno4:
# dhcp4: true
addresses:
- 192.168.0.36/24
routes:
- to: default
via: 192.168.0.254
nameservers:
addresses:
- 192.168.0.6
- 192.168.0.4
search:
- CASS.local

[Edgar3]

root@hvme:/etc/netplan# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 28:80:23:a1:b2:5c brd ff:ff:ff:ff:ff:ff
altname enp3s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 28:80:23:a1:b2:5d brd ff:ff:ff:ff:ff:ff
altname enp3s0f1
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 28:80:23:a1:b2:5e brd ff:ff:ff:ff:ff:ff
altname enp3s0f2
5: eno4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 28:80:23:a1:b2:5f brd ff:ff:ff:ff:ff:ff
altname enp3s0f3
inet 192.168.0.36/24 brd 192.168.0.255 scope global eno4
valid_lft forever preferred_lft forever
inet6 fe80::2a80:23ff:fea1:b25f/64 scope link
valid_lft forever preferred_lft forever

[pkbin]

Hi  @Edgar3 

Thank you so much for providing the requested output. It is clear that, we have network issue here. The Management bridge is not created correctly and I see multiple VMs are being created ( seems you have tried with different name everytime).

I would recomend to clean it and try freshly.

1. Make sure, you mount the HPE Morpheus VM Essential Software ISO file ( example: /mnt/iso )

2. Clean the existing VME setup
#for vm in `virsh list --all --name`; do virsh destroy $vm; done
#for vm in `virsh list --all --name`; do virsh undefine $vm; done
#for vm in `virsh net-list --all --name`; do virsh net-destroy $vm; done
#for vm in `virsh net-list --all --name`; do virsh net-undefine $vm; done
#/opt/hpe-vm/scripts/reset_host.sh

3.  Install HPE Morpheus VM Essential Console ( from mounted ISO image)
#cd /mnt/iso
#apt install -y -f ./hpe-vm_1.0.X-1_amd64.deb     <== This is just an example. Kindly use the correct file. OR replace the X with actual version number

4. Now deploy the  VM Essential manager VM
#hpe-vm

// Make sure, you use the unique and correct IP for this VM ( which is in same subnet of 192.168.0.XX) and mention eno4 in Management network section.  And IP must be resolvable.

Please let me know, how this goes ?

Thanks

[Edgar3]

Thank you for the information provided. I have a question regarding the IP configuration. In the Manager's configurator, should I enter the IP address that the Ubuntu server currently has, or should it be a free IP address for the VM that will be created?

[Edgar3]

By clearing the configuration and correctly pointing the IP to the host, it was resolved. Thank you for your support and the information provided

[Johanna_e]

Hi, I'm having the same problem as you. What IP address did you end up entering in VME Manager? The same one as your Ubuntu server, or a free one on the same segment?

[Edgar3]

@pkbin,

That was precisely part of my mistake; in the end, I understood that a different IP address must be set in the VM Essentials administrator than the one I had set on the Ubuntu server. In other words, they must be two distinct IP addresses.