Hello all,
We are running oVirt 4.3.10.4-1.0.22.el7. I noticed an interesting issue or a possible bug
yesterday. I was trying to add a host when I noticed that it was failing and the host
status was going into 'unassigned' state.
I saw the below error in the engine log.
/var/log/ovirt-engine/engine.log
2022-04-07 15:17:07,739+04 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-24723) [4917a348] HostName = olvsrv005u
2022-04-07 15:17:07,739+04 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataAfterInstallationVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-24723) [4917a348] Failed in
'CollectVdsNetworkDataAfterInstallationVDS' method, for vds: 'olvsrv005u';
host: '10.119.6.232': CallableStatementCallback; SQL [{call insertnameserver(?, ?,
?)}ERROR: duplicate key value violates unique constraint "name_server_pkey"
Detail: Key (dns_resolver_configuration_id,
address)=(459b68e6-b684-4cf6-8834-755249a6bd3a, 10.119.10.212) already exists.
Where: SQL statement "INSERT INTO
name_server(
address,
position,
dns_resolver_configuration_id)
VALUES (
v_address,
v_position,
v_dns_resolver_configuration_id)"
PL/pgSQL function insertnameserver(uuid,character varying,smallint) line 3 at SQL
statement; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key
value violates unique constraint "name_server_pkey"
Detail: Key (dns_resolver_configuration_id,
address)=(459b68e6-b684-4cf6-8834-755249a6bd3a, 10.119.10.212) already exists.
Then I checked the resolv.conf on the host
[root@olvsrv005u ~]# cat /etc/resolv.conf
# Version: 1.00
search
uat.abc.com
nameserver 10.119.10.212
nameserver 10.119.10.212
Well, ideally it's of no use having duplicate nameserver. But it was not affecting the
functionality of the host. However it was failing the addition of the host, probably
because it was failing when updating the host's config in the engine DB due to the
duplicate nameserver.
To test this I commented the duplicate value and checked. The host is now added
successfully.
2022-04-07 15:33:37,301+04 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [] START,
GetHardwareInfoAsyncVDSCommand(HostName = olvsrv005u, VdsIdA
ndVdsVDSCommandParametersBase:{hostId='459b68e6-b684-4cf6-8834-755249a6bd3a',
vds='Host[olvsrv005u,459b68e6-b684-4cf6-8834-755249a6bd3a]'}), log id: 52e7ec52
2022-04-07 15:33:37,301+04 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoAsyncVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [] FINISH,
GetHardwareInfoAsyncVDSCommand, return: , log id: 52e7ec52
2022-04-07 15:33:37,356+04 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [3de72cb7] Running command:
SetNonOperationalVdsCommand internal: true. Entities affected :
ID: 459b68e6-b684-4cf6-8834-755249a6bd3a Type: VDS
2022-04-07 15:33:37,360+04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [3de72cb7] START,
SetVdsStatusVDSCommand(HostName = olvsrv005u, SetVdsStatusVDSCommandPa
rameters:{hostId='459b68e6-b684-4cf6-8834-755249a6bd3a',
status='NonOperational', nonOperationalReason='NETWORK_UNREACHABLE',
stopSpmFailureLogged='false', maintenanceReason='null'}), log id:
1bfc90a3
2022-04-07 15:33:37,363+04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [3de72cb7] FINISH,
SetVdsStatusVDSCommand, return: , log id: 1bfc90a3
2022-04-07 15:33:37,404+04 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [3de72cb7] Host 'olvsrv005u'
is set to Non-Operational, it is missing the following networks
Should I raise this as a bug? I'm of the opinion that it should be because if it's
not breaking the host's functionality then it should be ok.
Regards,
Ravi