[ovirt-users] Re: Emulex OneConnect 10Gb NICs on Ovirt 4.4.10

2022-04-16 Thread Roberto Nunin
And also used the be2net With Rocky 8.5 on Gen9.

Works as expected, until now.


Roberto

Il Sab 16 Apr 2022, 20:36 Roberto Nunin  ha scritto:

> Hi Thomas
>
> I've also checked 4.4.9 with "additional" drivers grabbed from ElRepo, on
> both Gen8/9.
>
> I'm still on 4.4.9, on RHVH hosts and oVirt nodes.
>
> No problems until now, since November.
>
>
> Roberto
>
> Il Sab 16 Apr 2022, 20:23 Thomas Kamalakis  ha scritto:
>
>> Hi Roberto
>>
>>   We also used the ElRepo drivers in production - most of our e-learning
>> servers including BBB are on oVirt Gen8 hosts. No problems whatsoever
>>
>>   The problem is that I could not find drivers for the kernel version of
>> the 4.4.10 release.
>>
>>   Thomas
>>
>>
>> On Sat, 16 Apr 2022, 19:58 Roberto Nunin,  wrote:
>>
>>> My cent.
>>>
>>> I've used both Gen8 and Gen9 with ElRepo drivers, in light production,
>>> without any problem, more than 2 years.
>>>
>>> Also qla2xxx driver was from ElRepo, being cluster with FC storage.
>>>
>>>
>>> Roberto
>>>
>>> Il Gio 14 Apr 2022, 08:04 Thomas Kamalakis  ha scritto:
>>>
>>>> Thanks Darrell
>>>>
>>>>   I think I understand your point, but it looks to me like such a
>>>> bother to have to do things like this. I will try starting from 4.4.9.
>>>>
>>>>   Could a solution be to install Debian and run kvm to install the
>>>> ovirt-node? I guess you waste some resources doing this but maybe worth it
>>>> if you can skip all this kernel business.
>>>>
>>>>   BR
>>>>
>>>>   Thomas
>>>>
>>>>
>>>>
>>>> On Wed, Apr 13, 2022 at 10:35 PM Darrell Budic 
>>>> wrote:
>>>>
>>>>> I hit this too, RH appears to have limited the supported PCI ids in
>>>>> their be2net and no longer includes the Emulex OneConnect in the list of
>>>>> supported IDs. I switched to the EL repo mainline kernels to resolve the
>>>>> issue on existing systems, it was a bit more fun on systems needing new
>>>>> installs of 8.x. I think I settled on installing an older system, 
>>>>> switching
>>>>> kernels, and then upgrading to current.
>>>>>
>>>>> Good luck,
>>>>>
>>>>>   -Darrell
>>>>>
>>>>> > On Apr 13, 2022, at 12:12 AM, th...@hua.gr wrote:
>>>>> >
>>>>> > Hi
>>>>> >
>>>>> >  We have a large number of HP servers where we use Ovirt and we are
>>>>> having problems upgrading the nodes to Ovirt 4.4.10
>>>>> >
>>>>> >  More specifically the servers have the Emulex OneConnect 10Gb NICs
>>>>> and what we did in previous Ovirt node installations was to download the
>>>>> driver rpm (e.g. kmod-be2net-12.0.0.0-8.el8_5.elrepo.x86_64.rpm) and then
>>>>> install it using "rpm -ivh ... " and carrying out "modprobe be2net"
>>>>> >
>>>>> >  For 4.18.0-365 we could not find a separate rpm but it looks like
>>>>> this was included in kernel-modules-4.18.0-365.el8.x86_64.rpm (
>>>>> https://centos.pkgs.org/8-stream/centos-baseos-x86_64/kernel-modules-4.18.0-365.el8.x86_64.rpm.html)
>>>>> which is already installed. "modprobe be2net" produces no errors but the
>>>>> network interfaces do not show up in "ip -a" even after reboot.
>>>>> >
>>>>> >  Are we missing something here, or is our infrastructure unusable
>>>>> with 4.4.10? Things were working for 4.4.9.
>>>>> >
>>>>> >  Thanks!
>>>>> > ___
>>>>> > Users mailing list -- users@ovirt.org
>>>>> > To unsubscribe send an email to users-le...@ovirt.org
>>>>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>>> > oVirt Code of Conduct:
>>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>>> > List Archives:
>>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/AFSJ76ZGLMM7RVNTNIK7L6PIKG2X2HSV/
>>>>>
>>>>>
>>>>
>>>> --
>>>> Dr. Thomas Kamalakis
>>>> Professor and Dean of the School of Digital Technology
>>>> Department of Informatics and Telematics, Harokopio University of
>>>> Athens, Greece
>>>> Omirou 9, Tavros, Athens, GR17778, Tel: +302109549406,
>>>> Web: https://galaxy.hua.gr/~thkam, Github:
>>>> https://github.com/thomaskamalakis/
>>>>
>>>> ___
>>>> Users mailing list -- users@ovirt.org
>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D7LC6BMGWM4DXRDDVZLOJHPEZ5PKGWXB/
>>>>
>>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/74MHZDV6Z2CUMPQRCLEKTPQLEYPFGGH4/


[ovirt-users] Re: Emulex OneConnect 10Gb NICs on Ovirt 4.4.10

2022-04-16 Thread Roberto Nunin
Hi Thomas

I've also checked 4.4.9 with "additional" drivers grabbed from ElRepo, on
both Gen8/9.

I'm still on 4.4.9, on RHVH hosts and oVirt nodes.

No problems until now, since November.


Roberto

Il Sab 16 Apr 2022, 20:23 Thomas Kamalakis  ha scritto:

> Hi Roberto
>
>   We also used the ElRepo drivers in production - most of our e-learning
> servers including BBB are on oVirt Gen8 hosts. No problems whatsoever
>
>   The problem is that I could not find drivers for the kernel version of
> the 4.4.10 release.
>
>   Thomas
>
>
> On Sat, 16 Apr 2022, 19:58 Roberto Nunin,  wrote:
>
>> My cent.
>>
>> I've used both Gen8 and Gen9 with ElRepo drivers, in light production,
>> without any problem, more than 2 years.
>>
>> Also qla2xxx driver was from ElRepo, being cluster with FC storage.
>>
>>
>> Roberto
>>
>> Il Gio 14 Apr 2022, 08:04 Thomas Kamalakis  ha scritto:
>>
>>> Thanks Darrell
>>>
>>>   I think I understand your point, but it looks to me like such a bother
>>> to have to do things like this. I will try starting from 4.4.9.
>>>
>>>   Could a solution be to install Debian and run kvm to install the
>>> ovirt-node? I guess you waste some resources doing this but maybe worth it
>>> if you can skip all this kernel business.
>>>
>>>   BR
>>>
>>>   Thomas
>>>
>>>
>>>
>>> On Wed, Apr 13, 2022 at 10:35 PM Darrell Budic 
>>> wrote:
>>>
>>>> I hit this too, RH appears to have limited the supported PCI ids in
>>>> their be2net and no longer includes the Emulex OneConnect in the list of
>>>> supported IDs. I switched to the EL repo mainline kernels to resolve the
>>>> issue on existing systems, it was a bit more fun on systems needing new
>>>> installs of 8.x. I think I settled on installing an older system, switching
>>>> kernels, and then upgrading to current.
>>>>
>>>> Good luck,
>>>>
>>>>   -Darrell
>>>>
>>>> > On Apr 13, 2022, at 12:12 AM, th...@hua.gr wrote:
>>>> >
>>>> > Hi
>>>> >
>>>> >  We have a large number of HP servers where we use Ovirt and we are
>>>> having problems upgrading the nodes to Ovirt 4.4.10
>>>> >
>>>> >  More specifically the servers have the Emulex OneConnect 10Gb NICs
>>>> and what we did in previous Ovirt node installations was to download the
>>>> driver rpm (e.g. kmod-be2net-12.0.0.0-8.el8_5.elrepo.x86_64.rpm) and then
>>>> install it using "rpm -ivh ... " and carrying out "modprobe be2net"
>>>> >
>>>> >  For 4.18.0-365 we could not find a separate rpm but it looks like
>>>> this was included in kernel-modules-4.18.0-365.el8.x86_64.rpm (
>>>> https://centos.pkgs.org/8-stream/centos-baseos-x86_64/kernel-modules-4.18.0-365.el8.x86_64.rpm.html)
>>>> which is already installed. "modprobe be2net" produces no errors but the
>>>> network interfaces do not show up in "ip -a" even after reboot.
>>>> >
>>>> >  Are we missing something here, or is our infrastructure unusable
>>>> with 4.4.10? Things were working for 4.4.9.
>>>> >
>>>> >  Thanks!
>>>> > ___
>>>> > Users mailing list -- users@ovirt.org
>>>> > To unsubscribe send an email to users-le...@ovirt.org
>>>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> > oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> > List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/AFSJ76ZGLMM7RVNTNIK7L6PIKG2X2HSV/
>>>>
>>>>
>>>
>>> --
>>> Dr. Thomas Kamalakis
>>> Professor and Dean of the School of Digital Technology
>>> Department of Informatics and Telematics, Harokopio University of
>>> Athens, Greece
>>> Omirou 9, Tavros, Athens, GR17778, Tel: +302109549406,
>>> Web: https://galaxy.hua.gr/~thkam, Github:
>>> https://github.com/thomaskamalakis/
>>>
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D7LC6BMGWM4DXRDDVZLOJHPEZ5PKGWXB/
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WB2TVEGYNYEKR2SZVFBOPLZRMUC56VV2/


[ovirt-users] Re: Emulex OneConnect 10Gb NICs on Ovirt 4.4.10

2022-04-16 Thread Roberto Nunin
My cent.

I've used both Gen8 and Gen9 with ElRepo drivers, in light production,
without any problem, more than 2 years.

Also qla2xxx driver was from ElRepo, being cluster with FC storage.


Roberto

Il Gio 14 Apr 2022, 08:04 Thomas Kamalakis  ha scritto:

> Thanks Darrell
>
>   I think I understand your point, but it looks to me like such a bother
> to have to do things like this. I will try starting from 4.4.9.
>
>   Could a solution be to install Debian and run kvm to install the
> ovirt-node? I guess you waste some resources doing this but maybe worth it
> if you can skip all this kernel business.
>
>   BR
>
>   Thomas
>
>
>
> On Wed, Apr 13, 2022 at 10:35 PM Darrell Budic 
> wrote:
>
>> I hit this too, RH appears to have limited the supported PCI ids in their
>> be2net and no longer includes the Emulex OneConnect in the list of
>> supported IDs. I switched to the EL repo mainline kernels to resolve the
>> issue on existing systems, it was a bit more fun on systems needing new
>> installs of 8.x. I think I settled on installing an older system, switching
>> kernels, and then upgrading to current.
>>
>> Good luck,
>>
>>   -Darrell
>>
>> > On Apr 13, 2022, at 12:12 AM, th...@hua.gr wrote:
>> >
>> > Hi
>> >
>> >  We have a large number of HP servers where we use Ovirt and we are
>> having problems upgrading the nodes to Ovirt 4.4.10
>> >
>> >  More specifically the servers have the Emulex OneConnect 10Gb NICs and
>> what we did in previous Ovirt node installations was to download the driver
>> rpm (e.g. kmod-be2net-12.0.0.0-8.el8_5.elrepo.x86_64.rpm) and then install
>> it using "rpm -ivh ... " and carrying out "modprobe be2net"
>> >
>> >  For 4.18.0-365 we could not find a separate rpm but it looks like this
>> was included in kernel-modules-4.18.0-365.el8.x86_64.rpm (
>> https://centos.pkgs.org/8-stream/centos-baseos-x86_64/kernel-modules-4.18.0-365.el8.x86_64.rpm.html)
>> which is already installed. "modprobe be2net" produces no errors but the
>> network interfaces do not show up in "ip -a" even after reboot.
>> >
>> >  Are we missing something here, or is our infrastructure unusable with
>> 4.4.10? Things were working for 4.4.9.
>> >
>> >  Thanks!
>> > ___
>> > Users mailing list -- users@ovirt.org
>> > To unsubscribe send an email to users-le...@ovirt.org
>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> > oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> > List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/AFSJ76ZGLMM7RVNTNIK7L6PIKG2X2HSV/
>>
>>
>
> --
> Dr. Thomas Kamalakis
> Professor and Dean of the School of Digital Technology
> Department of Informatics and Telematics, Harokopio University of Athens,
> Greece
> Omirou 9, Tavros, Athens, GR17778, Tel: +302109549406,
> Web: https://galaxy.hua.gr/~thkam, Github:
> https://github.com/thomaskamalakis/
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D7LC6BMGWM4DXRDDVZLOJHPEZ5PKGWXB/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ORQXYUJOL4GSJQMEKRJDFZVRGF32HC4V/


[ovirt-users] Re: oVirt 4.4.3 - some hosts in unassigned state - Get Host Capabilities failed: PKIX path building failed

2021-11-19 Thread Roberto Nunin
Il giorno mar 16 nov 2021 alle ore 11:34 Roberto Nunin 
ha scritto:

> Hi all
>
> We have an (old) installation with two DC in two different locations.
>
> Hosts where hosted engine is running are regularly reported UP (DC 1)
> Host into the other DC (connected by WAN lines) are reported as Unassigned
> (DC 2)
>
> Connection between DC is working.
>
> In events we can find lot of errors like:
>
> VDSM itmilu0xx-mng.example.com command Get Host Capabilities failed: PKIX
> path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
>
> We are NOT using a thirdy party SSL certificate.
>
> In engine.log these are recurring errors:
>
> 2021-11-16 10:28:49,370+01 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
> Unable to process messages PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> 2021-11-16 10:28:49,372+01 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-100)
> [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException:
> VDSNetworkException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
>
> Thanks in advance for any suggestion
>

Update on the case .
It was solved. Between two DC an SSL inspection was activated, creating
problems in communication between manager and HOSTS and VDSMD.
Solution was to stop the SSL inspection.
Further analysis will be done to permit again the inspection, due to
security requirements.

Thanks for reading,

Roberto

>
>
>
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/57BXH5VVLT6YR3NKD6HZFOE4GWFG54GN/


[ovirt-users] oVirt 4.4.3 - some hosts in unassigned state - Get Host Capabilities failed: PKIX path building failed

2021-11-16 Thread Roberto Nunin
Hi all

We have an (old) installation with two DC in two different locations.

Hosts where hosted engine is running are regularly reported UP (DC 1)
Host into the other DC (connected by WAN lines) are reported as Unassigned
(DC 2)

Connection between DC is working.

In events we can find lot of errors like:

VDSM itmilu0xx-mng.example.com command Get Host Capabilities failed: PKIX
path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target

We are NOT using a thirdy party SSL certificate.

In engine.log these are recurring errors:

2021-11-16 10:28:49,370+01 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
Unable to process messages PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
2021-11-16 10:28:49,372+01 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-100)
[] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException:
VDSNetworkException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target

Thanks in advance for any suggestion

Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3TGUC6KNF3RAHRL5LLLKNEPNNPXNG2CX/


[ovirt-users] Failed upgrade from SHE 4.3.10 to 4.4.3 - Host set to Non-Operational - missing networks

2020-12-01 Thread Roberto Nunin
We are following both oVirt upgrade guide [1] and RHV 4.4 upgrade guide [2].

aps-te62-mng.corporate.it ---> host resinatlled with oVirt Node 4.4.3
aps-te61-mng.corporate.it ---> host where previous ovirt-engine 4.3.10 VM
was running when backup was taken.

hosted-engine --deploy  --restore-from-file= fails with
following errors in ovirt-hosted-engine-setup:

2020-12-01 15:53:37,534+0100 ERROR
otopi.ovirt_hosted_engine_setup.ansible_utils
ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
{"changed": false, "msg": "The host has been set in non_operational status,
please check engine logs, more info can be found in the engine logs, fix
accordingly and re-deploy."}
2020-12-01 15:56:30,414+0100 ERROR
otopi.ovirt_hosted_engine_setup.ansible_utils
ansible_utils._process_output:109 fatal: [localhost]: FAILED! =>
{"changed": false, "msg": "The system may not be provisioned according to
the playbook results: please check the logs for the issue, fix accordingly
or re-deploy from scratch.\n"}
2020-12-01 15:56:33,731+0100 ERROR otopi.context context._executeMethod:154
Failed to execute stage 'Closing up': Failed executing ansible-playbook
2020-12-01 15:57:08,663+0100 ERROR
otopi.ovirt_hosted_engine_setup.ansible_utils
ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! =>
{"changed": false, "msg": "Failed to connect to the host via ssh: ssh:
connect to host itte1lv51-mng.comifar.it port 22: Connection timed out",
"skip_reason": "Host localhost is unreachable", "unreachable": true}
2020-12-01 15:58:22,179+0100 ERROR otopi.plugins.gr_he_common.core.misc
misc._terminate:167 Hosted Engine deployment failed: please check the logs
for the issue, fix accordingly or re-deploy from scratch.

while within the HostedEngineLocal engine.log:

2020-12-01 15:52:42,161+01 ERROR
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedThreadFactory-engine-Thread-96) [11f50ce0] Host '
aps-te62-mng.corporate.it' is set to Non-Operational, it is missing the
following networks:
'migration,traffic_11,traffic_202,traffic_5,traffic_555,traffic_9'
2020-12-01 15:52:48,474+01 ERROR
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledTh
readPool-Thread-12) [41688fc7] Host 'aps-te62-mng.corporate.it' is set to
Non-Operational, it is missing the following networks:
'migration,traffic_11,traffic_202,traffic_5,traffic_555,traffic_9'
2020-12-01 15:52:53,734+01 ERROR
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-6)
[5fc7257] Host 'aps-te62-mng.corporate.it' is set to Non-Operational, it is
missing the following networks:
'migration,traffic_11,traffic_202,traffic_5,traffic_555,traffic_9'
2020-12-01 15:52:54,567+01 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring]
(ForkJoinPool-1-worker-13) [] Rerun VM
'f9249e06-237e-412c-91e9-7b0fa0b6ec2a'. Called from VDS '
aps-te62-mng.corprorate.it'
2020-12-01 15:52:54,676+01 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-361) [] EVENT_ID:
VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed  (VM:
external-HostedEngineLocal, Source: aps-te62-mng.corporate.it, Destination:
aps-te61-mng.corporate.it).

Why is the playbook trying to migrate HostedEngineLocal from reinstalled
4.4.3 oVirt node to an existing one that is still running oVirt Node 4.3.x ?
How can we manage this issue and proceed with the upgrade ?

[1]
https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3
[2]
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/she_upgrading_from_4-3


Thanks is advance for support.
Best regards

-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EGANL54AX3URDKV5NDKFCYKRJAWRD3O7/


[ovirt-users] Re: oVirt node 4.4.1 deploy FQDN not reachable

2020-08-07 Thread Roberto Nunin
Il giorno ven 7 ago 2020 alle ore 12:59 Roberto Nunin 
ha scritto:

> Hi all
>
> I have an issue while trying to deploy hyperconverged solution on three
> ovirt node boxes.
> ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.
>
> When from cockpit I choose gluster deployment, I have a form where I can
> insert both gluster fqdn names and public fqdn names (that is what I need,
> due to distinct network cards & networks)
>
> If I insert right names, that are resolved by nodes, I receive, anyway,
> FQDN is not reachable below Host1 entries.
>
> As already stated, these names are certainly resolved by DNS used.
> Any hints about ?
>
>
Using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso (4.4.2 RC2) the same
issue do not happen.


-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PFBLFLDWWZKL5ENPW6B6JXLOEQ7UT6LK/


[ovirt-users] oVirt node 4.4.1 deploy FQDN not reachable

2020-08-07 Thread Roberto Nunin
Hi all

I have an issue while trying to deploy hyperconverged solution on three
ovirt node boxes.
ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso.

When from cockpit I choose gluster deployment, I have a form where I can
insert both gluster fqdn names and public fqdn names (that is what I need,
due to distinct network cards & networks)

If I insert right names, that are resolved by nodes, I receive, anyway,
FQDN is not reachable below Host1 entries.

As already stated, these names are certainly resolved by DNS used.
Any hints about ?

-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GI5S22M3PZHJB22IXKSZ6ZAC6U33HGP7/


[ovirt-users]Fwd: Re: Can ovirt-node support multiple network cards ?

2019-10-22 Thread Roberto Nunin
If I've understood clearly, your goal is to have two physical network
interfaces connected to one logical  network in ovirt-engine.
If this is the case, you can use bonding/teaming physical interfaces into
one and then connect that aggregation to the ovirt-engine logical network.

Moreover, as Jeremy stated, you can use that aggregated physical interfaces
to transfer VLANs, taking advantages on redundancy/resilience and
configuration flexibility.


Il giorno lun 21 ott 2019 alle ore 16:33  ha
scritto:

> I am unable to tell from your question what research you have done or what
> you have tried so far.  Anyway, review this-
> https://ovirt.org/documentation/admin-guide/chap-Logical_Networks.html.
> Generally speaking, the checkbox for "Connect to physical network" should
> not be needed for your example.  You most likely will need to set up VLANs
> when you create the logical network.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D5IJME6AMGGH5UU62TJHPXNKMMPCMFMX/
>








-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZG7UNMO6ECBKHLYSLD4GLSVCWYQMQZJV/


[ovirt-users] Re: NVMe disk cause kernel panic in installer

2019-07-18 Thread Roberto Nunin
Yes, already identified. Happen with some NVME (not all, to be honest).

Targeted to be fixed in CentOS 7.7 (already fixed in centosplus kernel, but
centosplus isn't used in oVirt builds)

Il giorno gio 18 lug 2019 alle ore 11:27  ha scritto:

> Hey,
>
> I have problems with running oVirt installer on my H370M-ITX mobo. I have
> installed NVMe disk in it (which I want to use to install oVirt there) and
> installer crashes with kernel panic:
>
> https://photos.app.goo.gl/AY9T93bEs8sCQzRF7
>
> Is there any issues with compatibility oVirt and NVMe?
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IV46QA35KBCMX4RUXJJYAP5Q23OMNKEU/
>


-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/I5BEI5S6IB5JG5AZ6DBJ2HWJM5EH5NZ4/


[ovirt-users] Re: Broken dependencies in CentOS7 hosts upgrading to 4.2.8 from 4.2.7

2019-03-17 Thread Roberto Nunin
Hi Strahil
Thanks for feedback.

My CentOS Updates repo (part of the Base one) was disabled, as far as I
remember, to avoid conflicts with same packages and/or dependencies with
packages coming from ovirt* repositories.

Enabling the Updates repo, do the trick.
BR




Il giorno dom 17 mar 2019 alle 11:55 Strahil  ha
scritto:

> Here is my repolist:
>
> Last login: Sun Mar 17 12:42:53 2019 from 192.168.1.43
> [root@ovirt1 ~]# yum repolist
> Loaded plugins: enabled_repos_upload, fastestmirror, package_upload,
> product-  : id, search-disabled-repos, subscription-manager,
> vdsmupgrade
> This system is not registered with an entitlement server. You can use
> subscription-manager to register.
> Loading mirror speeds from cached hostfile
> * base: mirror.wwfx.net
> * extras: mirror.wwfx.net
> * ovirt-4.3: ftp.nluug.nl
> * ovirt-4.3-epel: mirror.t-home.mk
> * updates: mirror.wwfx.net
> repo id  repo name
> statusbase/7/x86_64CentOS-7 -
> Base   10,019centos-sclo-rh-release/x86_64CentOS-7
> - SCLo rh 8,113extras/7/x86_64
> CentOS-7 - Extras
> 371ovirt-4.3/7  Latest oVirt 4.3
> Release 265ovirt-4.3-centos-gluster5/x86_64 CentOS-7 -
> Gluster 5 112ovirt-4.3-centos-opstools/x86_64 CentOS-7
> - OpsTools - release853ovirt-4.3-centos-ovirt43/x86_64
> CentOS-7 - oVirt 4.3
> 287ovirt-4.3-centos-qemu-ev/x86_64  CentOS-7 - QEMU
> EV71ovirt-4.3-epel/x86_64Extra Packages
> for Enterprise Linux 7 12,981ovirt-4.3-virtio-win-latest  virtio-win
> builds roughly matching wh 40sac-gluster-ansible/x86_64   Copr repo
> for gluster-ansible owned b 18updates/7/x86_64 CentOS-7
> - Updates 1,163repolist: 34,293
> Uploading Enabled Repositories Report
> Cannot upload enabled repos report, is this client registered?
> [root@ovirt1 ~]#
>
> As you can see my CentOS7  - Updates is enabled.
> So far I have managed to upgrade 4.2.7  -> 4.2.8 -> 4.3.0 -> 4.3.1
>
> There were some issues ,  but nothing related to the repos.
>
> Best Regards,
> Strahil Nikolov
> On Mar 15, 2019 18:57, Roberto Nunin  wrote:
>
> Hi
> I have some oVirt clusters, in various config.
>
> One cluster based on CentOS7 hosts, another based on ovirt-node-ng.
> While the second was successfully updated from 4.2.7 to 4.2.8, attempts to
> update hosts of the first one ends with:
>
> Error: Package: vdsm-4.20.46-1.el7.x86_64 (ovirt-4.2)
>Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.3
>Installed: libvirt-daemon-kvm-4.5.0-10.el7.x86_64 (@base)
>libvirt-daemon-kvm = 4.5.0-10.el7
>
> Being a CentOS7 installation and not an ovirt-node-ng, I cannot follow the
> notice in :
>
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/AJUBXAIGXVD5U5O2VYHO3BONVROSGWNW/
>
> The only way to have libvirt-daemon-kvm release 4-5-0.10_6.4 (and not
> 6.3)  is to enable CentOS Updates repo. Looking at host-deploy log looks
> fine, but It's safe to enable that repo ? There is another, safest method
> to update these hosts to the latest version of 4.2 ?
>
> Thanks in advance
>
> --
> Roberto Nunin
>
>
>
> --
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MX5IJSX3NJRL4KB7TPHW7RAJRJ475HMX/


[ovirt-users] Broken dependencies in CentOS7 hosts upgrading to 4.2.8 from 4.2.7

2019-03-15 Thread Roberto Nunin
Hi
I have some oVirt clusters, in various config.

One cluster based on CentOS7 hosts, another based on ovirt-node-ng.
While the second was successfully updated from 4.2.7 to 4.2.8, attempts to
update hosts of the first one ends with:

Error: Package: vdsm-4.20.46-1.el7.x86_64 (ovirt-4.2)
   Requires: libvirt-daemon-kvm >= 4.5.0-10.el7_6.3
   Installed: libvirt-daemon-kvm-4.5.0-10.el7.x86_64 (@base)
   libvirt-daemon-kvm = 4.5.0-10.el7

Being a CentOS7 installation and not an ovirt-node-ng, I cannot follow the
notice in :
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AJUBXAIGXVD5U5O2VYHO3BONVROSGWNW/

The only way to have libvirt-daemon-kvm release 4-5-0.10_6.4 (and not 6.3)
is to enable CentOS Updates repo. Looking at host-deploy log looks fine,
but It's safe to enable that repo ? There is another, safest method to
update these hosts to the latest version of 4.2 ?

Thanks in advance

-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XX76B7KHT5TVX675UMLSDEHE4NEB4E4P/


[ovirt-users] Re: 4.2.7 & centos 7.6 dependency problems

2018-12-06 Thread Roberto Nunin
Hi

I had a similar problem just yesterday.
I've disabled all three sources within CentOS-Base.repo.

My nodes are still 7.5, but hope that this can help anyway.
My update process, done from hested-engine gui, has completed after the
change.

BR



Il giorno gio 6 dic 2018 alle 20:19 Demeter Tibor  ha
scritto:

> Dear All,
> I would like to upgrade my ovirt 4.2.5 to 4.2.7.
>
> The hosted engine upgrade was success, but on the nodes i've got an
> dependency error:
>
> ---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed
> --> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package:
> mesa-libgbm-18.0.5-3.el7.x86_64
> --> Processing Dependency: libwayland-server.so.0()(64bit) for package:
> mesa-libgbm-18.0.5-3.el7.x86_64
> ---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed
> ---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed
> --> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for
> package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> ---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed
> ---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed
> --> Running transaction check
> ---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed
> ---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed
> ---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be
> installed
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> --> Finished Dependency Resolution
> --> Running transaction check
> ---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased
> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed
> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package:
> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64
> --> Finished Dependency Resolution
> Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates)
>Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2
>Available: nbdkit-1.2.6-1.el7.x86_64 (base)
>nbdkit(x86-64) = 1.2.6-1.el7
>Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates)
>nbdkit(x86-64) = 1.2.6-1.el7_6.2
>Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel)
>nbdkit(x86-64) = 1.2.7-2.el7
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
>
>
> How can I solve this?
>
> Thanks in advance,
>
> Regards,
>
> Tibor
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/AUAO3LNG2LY56K37ARWH6ORSC6MZL5CA/
>
-- 
Roberto Nunin
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AHPXAMQPTLTHTNZLBAYZROT3NIXA67VS/


[ovirt-users] Re: oVirt node 4.2.x - custom multipath.conf and external storage availability

2018-08-13 Thread Roberto Nunin
Hi all

any  feedback about ?

Thanks

Il giorno mar 31 lug 2018 alle ore 13:45 Roberto Nunin 
ha scritto:

> HI all
>
> How can I provide to my oVirt hosts a custom multipath.conf, considering
> that we are using shared/mirrored FC storage from HPE 3PAR with high
> availability of provided LUNs, using peer-persistance feature ?
>
> To configure correctly this require  a custom multipath.conf is required.
> How I can avoid it will be overwritten during upgrades ?
>
> Second topic:
> Is ALUA feature supported also in oVirt nodes, like for standard RHEL 6/7
> and/or CentOS 6/7 ?
>
> I was digging  for a while into user's digest, but not able to find
> focused informations.
>
> This is the feature needed by peer-persistance, allowing two different
> volumes to be masked toward a given host with the same WWN and LUN number.
>
> Thanks in advance
>
> --
> Roberto
>
>
>
>

-- 
Roberto
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CLA4ZANSIXQHEPOQGEIFTSTDDHRT742X/


[ovirt-users] oVirt node 4.2.x - custom multipath.conf and external storage availability

2018-07-31 Thread Roberto Nunin
HI all

How can I provide to my oVirt hosts a custom multipath.conf, considering
that we are using shared/mirrored FC storage from HPE 3PAR with high
availability of provided LUNs, using peer-persistance feature ?

To configure correctly this require  a custom multipath.conf is required.
How I can avoid it will be overwritten during upgrades ?

Second topic:
Is ALUA feature supported also in oVirt nodes, like for standard RHEL 6/7
and/or CentOS 6/7 ?

I was digging  for a while into user's digest, but not able to find focused
informations.

This is the feature needed by peer-persistance, allowing two different
volumes to be masked toward a given host with the same WWN and LUN number.

Thanks in advance

-- 
Roberto
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LCKGIS3C5D5JP5B4ELDFTLCSQMKMLILM/


[ovirt-users] GUI trouble when adding FC datadomain

2018-02-02 Thread Roberto Nunin
Hi all

I'm trying to setup ad HE cluster, with FC domain.
HE is also on FC.

When I try to add the first domain in the datacenter, I've this form:

[image: Immagine incorporata 1]

So I'm not able to choose any of the three volumes currently masked towards
the chosen host.
I've tried all browser I've: Firefox 58, Chrome 63, IE 11, MS Edge, with no
changes.

Tried to click in the rows, scrolling etc.  with no success.

Someone has found the same issue ?
Thanks in advance

-- 
Roberto Nunin
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Storage Hardware for Hyperconverged oVirt: Gluster best practice

2018-01-10 Thread Roberto Nunin
Il 10 Gen 2018 20:40,  ha scritto:

oVirt + Gluster (hyperconverged) RAID question:
I have 3 nodes of SuperMicro hardware, each node has 1x SATADOM (boot drive
for o/s install) and 6x 1TB SSD (to be used for Gluster).
For the SSDs, is hardware or software RAID preferred or do I use an HBA?
The RedHat docs seem to suggest hardware RAID, others on the forum say HBA
or software RAID.

What are other folks using?


I'm using hardware raid.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Host has not default route

2017-12-19 Thread Roberto Nunin
Hi all

I'm doing further tests deploying from scratch, with the same hardware, one
Gluster based hyperconverged  LAB.

I'm deploying ovirt-node'ng with ISO image:
ovirt-node-ng-installer-ovirt-4.2-pre-2017121416.

All the process works fine, no more hangs when HE deploy is at the end.

Hosts 2 and 3 now can be imported (insted to be added).
Storage main domain is added and HE storage automatically imported.

One issue: Host 2 and 3 show me:

Host has no default route

In Host> General tab.
Moreover I'm not able to migrate HE, even if the hosted-engine --vm-status
looks good, like in the attachment.

Could the issue of "Host has no default route" blocking migrations ?
Hosts are online, all of three.

How to work around the "Host has no default route" message ?
I've seen a bug, 1477589, but no solution, till now.

Any hints ?



-- 
Roberto Nunin


--== Host 1 status ==--

conf_on_shared_storage : True
Status up-to-date  : True
Hostname   : aps-te61-mng.example.com
Host ID: 1
Engine status  : {"health": "good", "vm": "up", "detail": 
"Up"}
Score  : 3400
stopped: False
Local maintenance  : False
crc32  : 4705f6fc
local_conf_timestamp   : 324678
Host timestamp : 324678
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=324678 (Tue Dec 19 14:08:40 2017)
host-id=1
score=3400
vm_conf_refresh_time=324678 (Tue Dec 19 14:08:40 2017)
conf_on_shared_storage=True
maintenance=False
state=EngineUp
stopped=False


--== Host 2 status ==--

conf_on_shared_storage : True
Status up-to-date  : True
Hostname   : aps-te68-mng.example.com
Host ID: 2
Engine status  : {"reason": "vm not running on this host", 
"health": "bad", "vm": "down", "detail": "unknown"}
Score  : 3400
stopped: False
Local maintenance  : False
crc32  : 6d1cf17d
local_conf_timestamp   : 321992
Host timestamp : 321991
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=321991 (Tue Dec 19 14:08:36 2017)
host-id=2
score=3400
vm_conf_refresh_time=321992 (Tue Dec 19 14:08:37 2017)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False


--== Host 3 status ==--

conf_on_shared_storage : True
Status up-to-date  : True
Hostname   : aps-te64-mng.example.com
Host ID: 3
Engine status  : {"reason": "vm not running on this host", 
"health": "bad", "vm": "down", "detail": "unknown"}
Score  : 3400
stopped: False
Local maintenance  : False
crc32  : 7c56e053
local_conf_timestamp   : 321982
Host timestamp : 321982
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=321982 (Tue Dec 19 14:08:38 2017)
host-id=3
score=3400
vm_conf_refresh_time=321982 (Tue Dec 19 14:08:38 2017)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] 4-2rc hosted-engine don't boot error:cannot allocate kernel buffer

2017-12-07 Thread Roberto Nunin
Hi

after successfully deployed fresh 4.2_rc with ovirt node, I'm facing with a
blocking problem.

hosted-engine won't boot. Reaching the console via vnc hook, I can see that
it is at initial boot screen, but for any OS release available, I receive:

[image: Immagine incorporata 1]
then
[image: Immagine incorporata 2]

​googling around, I'm not able to find suggestions. Any hints ?

Thanks​

-- 
Roberto
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Failed deply of ovirt-engine using ovirt-node-ng-installer-ovirt-4.2-pre-2017120512.iso

2017-12-06 Thread Roberto Nunin
Yes, both times on Cockpit.

2017-12-06 11:43 GMT+01:00 Simone Tiraboschi <stira...@redhat.com>:

>
>
> On Wed, Dec 6, 2017 at 11:38 AM, Roberto Nunin <robnu...@gmail.com> wrote:
>
>> Ciao Simone
>> thanks for really quick answer.
>>
>> 2017-12-06 11:05 GMT+01:00 Simone Tiraboschi <stira...@redhat.com>:
>>
>>> Ciao Roberto,
>>>
>>> On Wed, Dec 6, 2017 at 10:02 AM, Roberto Nunin <robnu...@gmail.com>
>>> wrote:
>>>
>>>> I'm having trouble to deploy one three host hyperconverged lab using
>>>> iso-image named above.
>>>>
>>>
>>> Please note that ovirt-node-ng-installer-ovirt-4.2-pre-2017120512
>>> <(201)%20712-0512>.iso is still a pre-release software.
>>> Your contribute testing it is really appreciated!
>>>
>>
>> ​It's a pleasure !.​
>>
>>
>>>
>>>
>>>
>>>>
>>>> My test environment is based on HPE BL680cG7 blade servers.
>>>> These servers has 6 physical 10GB network interfaces (flexNIC), each
>>>> one with four profiles (ethernet,FCoE,iSCSI,etc).
>>>>
>>>> I choose one of these six phys interfaces (enp5s0f0) and assigned it a
>>>> static IPv4 address, for each node.
>>>>
>>>> After node reboot, interface ONBOOT param is still set to no.
>>>> Changed via iLO interface to yes and restarted network. Fine.
>>>>
>>>> After gluster setup, with gdeploy script under Cockpit interface,
>>>> avoiding errors coming from :
>>>> /usr/share/gdepply/scripts/blacklist_all_disks.sh, start hosted-engine
>>>> deploy.
>>>>
>>>> With the new version, I'm having an error never seen before:
>>>>
>>>> The Engine VM (10.114.60.117) and this host (10.114.60.134/24) will
>>>> not be in the same IP subnet. Static routing configuration are not
>>>> supported on automatic VM configuration.
>>>>  Failed to execute stage 'Environment customization': The Engine VM
>>>> (10.114.60.117) and this host (10.114.60.134/24) will not be in the
>>>> same IP subnet. Static routing configuration are not supported on automatic
>>>> VM configuration.
>>>>  Hosted Engine deployment failed.
>>>>
>>>> There's no input field for HE subnet mask. Anyway in our class-c ovirt
>>>> management network these ARE in the same subnet.
>>>> How to recover from this ? I cannot add /24 CIDR in HE Static IP
>>>> address field, it isn't allowed.
>>>>
>>>
>>> 10.114.60.117 and 10.114.60.134/24 are in the same IPv4 /24 subnet so
>>> it should't fail.
>>> The issue here seams different:
>>>
>>> From hosted-engine-setup log I see that you passed the VM IP address via
>>> answerfile:
>>> 2017-12-06 09:14:30,195+0100 DEBUG otopi.context
>>> context.dumpEnvironment:831 ENV OVEHOSTED_VM/cloudinitVMStatic
>>> CIDR=str:'10.114.60.117'
>>>
>>> while the right syntax should be:
>>> OVEHOSTED_VM/cloudinitVMStaticCIDR=str:10.114.60.117/24
>>>
>>> Did you wrote the answerfile by yourself or did you entered the IP
>>> address in the cockpit wizard? if so we probably have a regression there.
>>>
>>
>> ​I've inserted it while providing data for setup, using Cockpit
>> interface. Tried to add CIDR (/24), but it isn't allowed from Cockpit web
>> interface.​ No manual update of answer file.
>>
>>>
>>>
>>>
>>>>
>>>> Moreover, VM FQDN is asked two times during the deploy process. It's
>>>> correct ?
>>>>
>>>
>>> No, I don't think so but I don't see it from you logs.
>>> Could you please explain it?
>>>
>>
>> ​Yes: first time is requested during initial setup of HE VM deploy
>>
>> The second one, instead, is asked (at least to me ) in this step, after
>> initial setup:
>>
>
> So both on cockpit side?
>
>
>>
>> [image: Immagine incorporata 1]​
>>
>>>
>>>
>>>>
>>>> Some additional, general questions:
>>>> NetworkManager: must be disabled deploying HCI solution ? In my
>>>> attempt, wasn't disabled.
>>>>
>>>
>> ​Simone, could you confirm or not that NM must stay in place while
>> deploying ? This qustion was struggling since 3.6.. what is the "best
>> practice" ?
>> All of mine RHV environments (3.6 - 4.0.1 - 4.1.6 ) have it disabled, but
>> I wasn't able to find any mandatory rule.
>>
>
> In early 3.6 you had to disable it but now you can safely keep it on.
>
>
>
>> ​
>>
>>> There's some document to follow to perform a correct deploy ?
>>>> Is this one still "valid" ? : https://ovirt.org/blog/2017/
>>>> 04/up-and-running-with-ovirt-4.1-and-gluster-storage/
>>>>
>>>> Attached hosted-engine-setup log.
>>>> TIA
>>>>
>>>>
>>>>
>>>> --
>>>> Roberto
>>>> 110-006-970​
>>>>
>>>> ___
>>>> Users mailing list
>>>> Users@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>
>>
>> --
>> Roberto Nunin
>>
>>
>>
>>
>


-- 
Roberto Nunin
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Bad volume specification after hung migration

2017-10-26 Thread Roberto Nunin
We are running 4.0.1.1-1.el7.centos

After a frozen migration attempt, we have two VM that after shutdown, are
not anymore able to be started up again.

Message returned is :

Bad volume specification {'index': '0', u'domainID':
u'731d95a9-61a7-4c7a-813b-fb1c3dde47ea', 'reqsize': '0', u'format': u'cow',
u'optional': u'false', u'address': {u'function': u'0x0', u'bus': u'0x00',
u'domain': u'0x', u'type': u'pci', u'slot': u'0x05'}, u'volumeID':
u'cffc70ff-ed72-46ef-a369-4be95de72260', 'apparentsize': '3221225472',
u'imageID': u'3fe5a849-bcc2-42d3-93c5aca4c504515b', u'specParams': {},
u'readonly': u'false', u'iface': u'virtio', u'deviceId':
u'3fe5a849bcc2-42d3-93c5-aca4c504515b', 'truesize': '3221225472',
u'poolID': u'0001-0001-0001-0001-01ec', u'device': u'disk',
u'shared': u'false', u'propagateErrors': u'off',u'type':u'disk'}

Probably this is caused by a wrong pointer into the database that still
refer to the migration image-id.

If we search within all_disks view, we can find that parentid field
isn't ----
like all other running vm, but it has a value:

   vm_names   |   parentid
--+--
 working01.company.xx | ----
 working02.company.xx | ----
 working03.company.xx | ----
 working04.company.xx | ----
 broken001.company.xx | 30533842-2c83-4d0e-95d2-48162dbe23bd <
 working05.company.xx | ----


How we can recover from this ?

Thanks in advance
Regards,

-- 
Robert
​o​
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Add FC domain failed - but reported as used

2017-10-11 Thread Roberto Nunin
I've tried to add a second FC data domain to our oVirt remote infra, built
with 6 hosts in remote and 4 local, where hosted-engine is running.

Currently, we are using  4.0.1.1-1.el7.centos.

After FC storage setup (zoning/masking), tried to add the new volume to the
remote DC.

Process was failing with:

2017-10-11 12:57:31,174 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-5) [bfcbca2] Correlation ID: bfcbca2, Job ID:
0850b9ba-a898-472c-9dbd-3ae4f27b2992, Call Stack: null, Custom Event ID:
-1, Message: Failed to attach Storage Domain oVirt_datastore_2_NO to Data
Center CompanyDCoVirt4. (User: m...@srv-ldap-new.company.com-authz).

on SPM, vdsm log report:

jsonrpc.Executor/0::ERROR::2017-10-11
12:57:26,503::sdc::140::Storage.StorageDomainCache::(_findDomain) looking
for unfetched domain 17d3d910-3f79-468e-9ffb-a7bd2bd174aa
jsonrpc.Executor/0::ERROR::2017-10-11
12:57:26,503::sdc::157::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 17d3d910-3f79-468e-9ffb-a7bd2bd174aa
jsonrpc.Executor/0::ERROR::2017-10-11
12:57:26,505::sdc::146::Storage.StorageDomainCache::(_findDomain) domain
17d3d910-3f79-468e-9ffb-a7bd2bd174aa not found


After this attempt, I've double checket that all 6 hosts have identified
the new volume. All are ok.

Another attempt to add the volume to the remote DC, was failing blocking me
to chosse the volume ID into the GUI interface, because "the LUN is already
part of a Storage DOmain".

I think that something is still marking as used the new volume into the
host-engine DB, even if it isn't available into the GUI interface.
If this could be the reason, how to correctly manage this issue ? (apart
update the entire installation, planned :) )

Thanks in advance

-- 
Roberto
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users