[ovirt-users] Re: new host addition to OVN cluster fails with Connectivity check failed, rolling back

[Sandro Bonazzola]

Il giorno mar 26 apr 2022 alle ore 07:33 ravi k  ha
scritto:

> Hi Sandro,
> Thanks for that. I remember you mentioned this in another post too :) I
> posted about this as there might be some users using 4.3 and might pitch in
> with some ideas. We're starting out with a greenfield setup. Would you
> suggest that we rather go with 4.4 directly?
>

I would suggest to rather go with 4.5 directly.


>
> Regards,
> Ravi
> ___
> 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/LO42OOBSIL5W5BUC2DGDCJNIEMSBLSPG/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/NTLZCVPABQUXMQ4OP2564YQOKNM376VQ/

[ovirt-users] Re: new host addition to OVN cluster fails with Connectivity check failed, rolling back

[ravi k]

Hi Sandro,
Thanks for that. I remember you mentioned this in another post too :) I posted 
about this as there might be some users using 4.3 and might pitch in with some 
ideas. We're starting out with a greenfield setup. Would you suggest that we 
rather go with 4.4 directly?

Regards,
Ravi
___
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/LO42OOBSIL5W5BUC2DGDCJNIEMSBLSPG/

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

[Abe E]

Also, I checked for the postgresql-jdbc version on engine and it did not 
upgrade, it is on 42.2.3.
___
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/NEU6VFHPNSTU5HYYRY5FJ7B24A53N7JR/

[ovirt-users] Issue upgrading 4.4 to 4.5 Gluster HCG

[Abe E]

Hey All, 

I am having an issue upgrading from 4.4 to 4.5.
My setup
3 Node Gluster (Cluster 1) + 3 Node Cluster (Cluster 2)

If i recall the process correctly, the process I did last week:

On all my Nodes:
dnf install -y centos-release-ovirt45 --enablerepo=extras

On Ovirt Engine:
dnf install -y centos-release-ovirt45
dnf update -y --nobest
engine-setup

Once the engine was upgraded successfully I ran the upgrade from the GUI on the 
Cluster 2 Nodes one by one although when they came back, they complained of 
"Host failed to attach one of the Storage Domains attached to it." which is the 
"hosted_storage", "data" (gluster).

I thought maybe its due to the fact that 4.5 brings an update to the glusterfs 
version, so I decided to upgrade Node 3 in my Gluster Cluster and it booted to 
emergency mode after the install "succeeded". 

I feel like I did something wrong, aside from my bravery of upgrading so much 
before realizing somethings not right.

My VDSM Logs from one of the nodes that fails to connect to storage (FYI I have 
2 Networks, one for Mgmt and 1 for storage that are up):

[root@ovirt-4 ~]# tail -f /var/log/vdsm/vdsm.log
2022-04-25 22:41:31,584-0600 INFO  (jsonrpc/3) [vdsm.api] FINISH repoStats 
return={} from=:::172.17.117.80,38712, 
task_id=8370855e-dea6-4168-870a-d6235d9044e9 (api:54)
2022-04-25 22:41:31,584-0600 INFO  (jsonrpc/3) [vdsm.api] START 
multipath_health() from=:::172.17.117.80,38712, 
task_id=14eb199a-7fbf-4638-a6bf-a384dfbb9d2c (api:48)
2022-04-25 22:41:31,584-0600 INFO  (jsonrpc/3) [vdsm.api] FINISH 
multipath_health return={} from=:::172.17.117.80,38712, 
task_id=14eb199a-7fbf-4638-a6bf-a384dfbb9d2c (api:54)
2022-04-25 22:41:31,602-0600 INFO  (periodic/1) [vdsm.api] START 
repoStats(domains=()) from=internal, 
task_id=08a5c00b-1f66-493f-a408-d4006ddaa959 (api:48)
2022-04-25 22:41:31,603-0600 INFO  (periodic/1) [vdsm.api] FINISH repoStats 
return={} from=internal, task_id=08a5c00b-1f66-493f-a408-d4006ddaa959 (api:54)
2022-04-25 22:41:31,606-0600 INFO  (jsonrpc/3) [api.host] FINISH getStats 
return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} 
from=:::172.17.117.80,38712 (api:54)
2022-04-25 22:41:35,393-0600 INFO  (jsonrpc/5) [api.host] START getAllVmStats() 
from=:::172.17.117.80,38712 (api:48)
2022-04-25 22:41:35,393-0600 INFO  (jsonrpc/5) [api.host] FINISH getAllVmStats 
return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} 
from=:::172.17.117.80,38712 (api:54)
2022-04-25 22:41:39,366-0600 INFO  (jsonrpc/2) [api.host] START getAllVmStats() 
from=::1,53634 (api:48)
2022-04-25 22:41:39,366-0600 INFO  (jsonrpc/2) [api.host] FINISH getAllVmStats 
return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} 
from=::1,53634 (api:54)
2022-04-25 22:41:46,530-0600 INFO  (jsonrpc/1) [api.host] START getStats() 
from=:::172.17.117.80,38712 (api:48)
2022-04-25 22:41:46,568-0600 INFO  (jsonrpc/1) [vdsm.api] START 
repoStats(domains=()) from=:::172.17.117.80,38712, 
task_id=30404767-9761-4f8c-884a-5561dd0d82fe (api:48)
2022-04-25 22:41:46,568-0600 INFO  (jsonrpc/1) [vdsm.api] FINISH repoStats 
return={} from=:::172.17.117.80,38712, 
task_id=30404767-9761-4f8c-884a-5561dd0d82fe (api:54)
2022-04-25 22:41:46,569-0600 INFO  (jsonrpc/1) [vdsm.api] START 
multipath_health() from=:::172.17.117.80,38712, 
task_id=8dbfa47f-e1b7-408c-a060-8d45012f0b90 (api:48)
2022-04-25 22:41:46,569-0600 INFO  (jsonrpc/1) [vdsm.api] FINISH 
multipath_health return={} from=:::172.17.117.80,38712, 
task_id=8dbfa47f-e1b7-408c-a060-8d45012f0b90 (api:54)
2022-04-25 22:41:46,574-0600 INFO  (jsonrpc/1) [api.host] FINISH getStats 
return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} 
from=:::172.17.117.80,38712 (api:54)
2022-04-25 22:41:46,651-0600 INFO  (periodic/0) [vdsm.api] START 
repoStats(domains=()) from=internal, 
task_id=92c69020-d0b1-4813-8610-3f3e1892c20b (api:48)
2022-04-25 22:41:46,652-0600 INFO  (periodic/0) [vdsm.api] FINISH repoStats 
return={} from=internal, task_id=92c69020-d0b1-4813-8610-3f3e1892c20b (api:54)
2022-04-25 22:41:50,397-0600 INFO  (jsonrpc/6) [api.host] START getAllVmStats() 
from=:::172.17.117.80,38712 (api:48)
2022-04-25 22:41:50,397-0600 INFO  (jsonrpc/6) [api.host] FINISH getAllVmStats 
return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} 
from=:::172.17.117.80,38712 (api:54)
2022-04-25 22:41:52,533-0600 INFO  (jsonrpc/4) [api.host] START 
getCapabilities() from=:::172.17.117.80,38712 (api:48)
2022-04-25 22:41:54,382-0600 INFO  (jsonrpc/0) [api.host] START getAllVmStats() 
from=::1,53634 (api:48)
2022-04-25 22:41:54,382-0600 INFO  (jsonrpc/0) [api.host] FINISH getAllVmStats 
return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} 
from=::1,53634 (api:54)
2022-04-25 22:41:55,037-0600 INFO  (jsonrpc/4) [root] 
/usr/libexec/vdsm/hooks/after_get_caps/ovirt_provider_ovn_hook: rc=0 err=b'' 
(hooks:123)
2022-04-25 

[ovirt-users] Re: AMD Ryzen 5600G unsupported?

[Gilboa Davara]

On Mon, Apr 25, 2022 at 12:17 PM  wrote:

> Please remember to enable tha AMD-V support in the bios, every time you
> upgrade bios they normally reset to "disabled".
> You can find this issue when in logs appears something like:
>

> Apr 20 11:45:11 ovirt-node3 journal[2011]: Unable to open /dev/kvm: No
> such file or directory
>
> to resolve remember to launch the command:
> virt-host-validate
> it checks the host environment to verify qemu support
>

I would add that if AMD-SVM is disabled, you should see "KVM is disabled in
the BIOS" message in the kernel log. (This is what I saw before the reset).

- Gilboa


>
> ___
> 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/WRBSFTMFYUEW3URJUOXFOTAZJY7YO2DV/
>
___
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/FJRY7ZD62MAEYQHCOG44JMQMSZFABNWK/

[ovirt-users] Re: Unable to remove host from ovirt engine

[Strahil Nikolov via Users]

I think you can use 'hosted-engine --clean-metadata --host-id=1'
In my case I had to use --force-cleanup, but I wouldn't recommend using it.
Best Regards,Strahil Nikolov
 
 
  On Mon, Apr 25, 2022 at 18:08, Joseph Gelinas wrote:   
Recently our host and ovirt engine certificates expired and with some ideas 
from Strahil we were able to get 2 of the 3 ovirt hosts updated with usable 
certificates and move all of our VMs to those two nodes.

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/QCFPKQ3OKPOUV266MFJUMVTNG2OHLJVW/

Not having any luck with the last host we figured we'd just try to remove it 
from ovirt engine and re-add it. While it seems `hosted-engine --vm-status` on 
one node no longer shows the removed host, the other good host and the web 
interface still show ovirt-1 in the mix. What is the best way to remove a 
NonRespnsive host from ovirt and re-add it?


[root@ovirt-1 ~]# hosted-engine --vm-status
The hosted engine configuration has not been retrieved from shared storage. 
Please ensure that ovirt-ha-agent is running and the storage server is 
reachable.



[root@ovirt-2 ~]# hosted-engine --vm-status


!! Cluster is in GLOBAL MAINTENANCE mode !!



--== Host ovirt-3.x.com (id: 2) status ==--

Host ID                            : 2
Host timestamp                    : 12515451
Score                              : 3274
Engine status                      : {"vm": "down", "health": "bad", "detail": 
"unknown", "reason": "vm not running on this host"}
Hostname                          : ovirt-3.x.com
Local maintenance                  : False
stopped                            : False
crc32                              : 9cf92792
conf_on_shared_storage            : True
local_conf_timestamp              : 12515451
Status up-to-date                  : True
Extra metadata (valid at timestamp):
    metadata_parse_version=1
    metadata_feature_version=1
    timestamp=12515451 (Mon Apr 25 14:08:51 2022)
    host-id=2
    score=3274
    vm_conf_refresh_time=12515451 (Mon Apr 25 14:08:51 2022)
    conf_on_shared_storage=True
    maintenance=False
    state=GlobalMaintenance
    stopped=False


--== Host ovirt-2.x.com (id: 3) status ==--

Host ID                            : 3
Host timestamp                    : 12513269
Score                              : 3400
Engine status                      : {"vm": "up", "health": "good", "detail": 
"Up"}
Hostname                          : ovirt-2.x.com
Local maintenance                  : False
stopped                            : False
crc32                              : 4a89d706
conf_on_shared_storage            : True
local_conf_timestamp              : 12513269
Status up-to-date                  : True
Extra metadata (valid at timestamp):
    metadata_parse_version=1
    metadata_feature_version=1
    timestamp=12513269 (Mon Apr 25 14:09:00 2022)
    host-id=3
    score=3400
    vm_conf_refresh_time=12513269 (Mon Apr 25 14:09:00 2022)
    conf_on_shared_storage=True
    maintenance=False
    state=GlobalMaintenance
    stopped=False


!! Cluster is in GLOBAL MAINTENANCE mode !!





[root@ovirt-3 ~]# hosted-engine --vm-status


!! Cluster is in GLOBAL MAINTENANCE mode !!



--== Host ovirt-1.x.com (id: 1) status ==--

Host ID                            : 1
Host timestamp                    : 6750990
Score                              : 0
Engine status                      : unknown stale-data
Hostname                          : ovirt-1.x.com
Local maintenance                  : False
stopped                            : True
crc32                              : 5290657b
conf_on_shared_storage            : True
local_conf_timestamp              : 6750950
Status up-to-date                  : False
Extra metadata (valid at timestamp):
    metadata_parse_version=1
    metadata_feature_version=1
    timestamp=6750990 (Thu Feb 17 22:17:53 2022)
    host-id=1
    score=0
    vm_conf_refresh_time=6750950 (Thu Feb 17 22:17:12 2022)
    conf_on_shared_storage=True
    maintenance=False
    state=AgentStopped
    stopped=True


--== Host ovirt-3.x.com (id: 2) status ==--

Host ID                            : 2
Host timestamp                    : 12515501
Score                              : 3279
Engine status                      : {"vm": "down", "health": "bad", "detail": 
"unknown", "reason": "vm not running on this host"}
Hostname                          : ovirt-3.x.com
Local maintenance                  : False
stopped                            : False
crc32                              : 0845cd93
conf_on_shared_storage            : True
local_conf_timestamp              : 12515501
Status up-to-date                  : True
Extra metadata (valid at timestamp):
    metadata_parse_version=1
    metadata_feature_version=1
    timestamp=12515501 (Mon Apr 25 14:09:42 2022)
    host-id=2
    score=3279
    vm_conf_refresh_time=12515501 (Mon Apr 25 14:09:42 2022)
    conf_on_shared_storage=True
    maintenance=False
    

[ovirt-users] Re: Installing new self-hosted engine v4.5.0 on gluster 10

[Strahil Nikolov via Users]

Would you be able to open a issue for that ?
@Sandro Bonazzola, as far as I remember, we started using github, right ?
Best Regards,Strahil Nikolov
 
 
  On Mon, Apr 25, 2022 at 14:16, Alessandro De 
Salvo wrote:   
___
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/TDWHLUQUPRYNKL4BH2IDDMAR5EPCCKJ3/
  
___
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/RKE7TB5GNUHCUQO4CJ5RIP6N5CD6VMTT/

[ovirt-users] Re: Error 500 on Hosted Engine admin portal!!!

[Strahil Nikolov via Users]

The exclude option takes not only a package but package with version, so you 
can block a specific version of package without blocking future updates.
Best Regards,Strahil Nikolov
 
 
  On Mon, Apr 25, 2022 at 11:24, Alessandro De 
Salvo wrote:   Hi,
I’m not sure if it works with the web installer, but if you deploy with CLI you 
can use the following to ask the installer to pause before running engine-setup:

hosted-engine --deploy --ansible-extra-vars=he_pause_before_engine_setup=true

This gives you the time to ssh and exclude the offending package before the 
installer attempts to upgrade any package.
Cheers,

  Alessandro

> Il giorno 25 apr 2022, alle ore 09:27, lpat...@siriusag.com ha scritto:
> 
> This is the cause, yes Martin - but it wont help since the 
> Installer/deployment does an update while running, so "almost" no way to 
> bypass that
> 
> WORKAROUND:
> preparation: 
> - ssh login to the node, prepare ssh root@
> - copy paste buffer ready: echo exclude=postgresql-jdbc >> /etc/dnf/dnf.conf
> 
> when the webinstaller is running, the moment when the ip of the hosted engine 
> vm is displayed (something like 192.168.222.208) immediately ssh to that vm 
> from the host
> and execute the copy paste buffer before the dnf update takes place
> 
> uggly workaround, maybe there's another better option, but hey, it describes 
> the problem and works :)
> 
> Cheers
> Luis
> ___
> 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/ULUGCT73FOPPAY7EVBIJC4KBDGU22GDM/
___
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/UZALUJRVR4E7RABUGTSQJT6YYY7LQYK7/
  
___
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/V3B3PFDKAFSBPQX4KQ5JUZF3TYY7VUQ3/

[ovirt-users] Unable to remove host from ovirt engine

[Joseph Gelinas]

Recently our host and ovirt engine certificates expired and with some ideas 
from Strahil we were able to get 2 of the 3 ovirt hosts updated with usable 
certificates and move all of our VMs to those two nodes.

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/QCFPKQ3OKPOUV266MFJUMVTNG2OHLJVW/

Not having any luck with the last host we figured we'd just try to remove it 
from ovirt engine and re-add it. While it seems `hosted-engine --vm-status` on 
one node no longer shows the removed host, the other good host and the web 
interface still show ovirt-1 in the mix. What is the best way to remove a 
NonRespnsive host from ovirt and re-add it?


[root@ovirt-1 ~]# hosted-engine --vm-status
The hosted engine configuration has not been retrieved from shared storage. 
Please ensure that ovirt-ha-agent is running and the storage server is 
reachable.



[root@ovirt-2 ~]# hosted-engine --vm-status


!! Cluster is in GLOBAL MAINTENANCE mode !!



--== Host ovirt-3.x.com (id: 2) status ==--

Host ID: 2
Host timestamp : 12515451
Score  : 3274
Engine status  : {"vm": "down", "health": "bad", "detail": 
"unknown", "reason": "vm not running on this host"}
Hostname   : ovirt-3.x.com
Local maintenance  : False
stopped: False
crc32  : 9cf92792
conf_on_shared_storage : True
local_conf_timestamp   : 12515451
Status up-to-date  : True
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=12515451 (Mon Apr 25 14:08:51 2022)
host-id=2
score=3274
vm_conf_refresh_time=12515451 (Mon Apr 25 14:08:51 2022)
conf_on_shared_storage=True
maintenance=False
state=GlobalMaintenance
stopped=False


--== Host ovirt-2.x.com (id: 3) status ==--

Host ID: 3
Host timestamp : 12513269
Score  : 3400
Engine status  : {"vm": "up", "health": "good", "detail": 
"Up"}
Hostname   : ovirt-2.x.com
Local maintenance  : False
stopped: False
crc32  : 4a89d706
conf_on_shared_storage : True
local_conf_timestamp   : 12513269
Status up-to-date  : True
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=12513269 (Mon Apr 25 14:09:00 2022)
host-id=3
score=3400
vm_conf_refresh_time=12513269 (Mon Apr 25 14:09:00 2022)
conf_on_shared_storage=True
maintenance=False
state=GlobalMaintenance
stopped=False


!! Cluster is in GLOBAL MAINTENANCE mode !!





[root@ovirt-3 ~]# hosted-engine --vm-status


!! Cluster is in GLOBAL MAINTENANCE mode !!



--== Host ovirt-1.x.com (id: 1) status ==--

Host ID: 1
Host timestamp : 6750990
Score  : 0
Engine status  : unknown stale-data
Hostname   : ovirt-1.x.com
Local maintenance  : False
stopped: True
crc32  : 5290657b
conf_on_shared_storage : True
local_conf_timestamp   : 6750950
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=6750990 (Thu Feb 17 22:17:53 2022)
host-id=1
score=0
vm_conf_refresh_time=6750950 (Thu Feb 17 22:17:12 2022)
conf_on_shared_storage=True
maintenance=False
state=AgentStopped
stopped=True


--== Host ovirt-3.x.com (id: 2) status ==--

Host ID: 2
Host timestamp : 12515501
Score  : 3279
Engine status  : {"vm": "down", "health": "bad", "detail": 
"unknown", "reason": "vm not running on this host"}
Hostname   : ovirt-3.x.com
Local maintenance  : False
stopped: False
crc32  : 0845cd93
conf_on_shared_storage : True
local_conf_timestamp   : 12515501
Status up-to-date  : True
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=12515501 (Mon Apr 25 14:09:42 2022)
host-id=2
score=3279
vm_conf_refresh_time=12515501 (Mon Apr 25 14:09:42 2022)
conf_on_shared_storage=True
maintenance=False
state=GlobalMaintenance
stopped=False


--== Host 

[ovirt-users] Re: Notified that Engine's certification is about to expire but no documentation to renew it

[Guillaume Pavese]

Thank you Didi,

I can confirm that engine-setup detected the approaching expiration of the
engine certificate and proposed to renew it.
We'll try proposing a documentation fix

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group


On Mon, Apr 25, 2022 at 9:02 PM Yedidyah Bar David  wrote:

> On Mon, Apr 25, 2022 at 2:45 PM Guillaume Pavese
>  wrote:
> >
> > Hello
> >
> > We are receiving the following notifications from our ovirt manager  :
> >
> > Message:Engine's certification is about to expire at 2022-05-03. Please
> renew the engine's certification.
> > Severity:WARNING
> >
> >
> > Effectively :
> >
> > # openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -startdate
> -enddate -noout
> > notBefore=Mar 30 04:48:15 2021 GMT
> > notAfter=May  3 04:48:15 2022 GMT
> >
> >
> > However I can not find any documentation on how to renew this
> certificate.
> > The following doc only convers changing apache-ca.pem & apache.cer, and
> not engine.cer
> >
> > Doc oVirt :
> https://ovirt.org/documentation/administration_guide/index.html#Replacing_the_Manager_CA_Certificate
> > Doc RHV :
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/administration_guide/index#Replacing_the_Manager_CA_Certificate
> >
> >
> > Any help ?
>
> Please try running 'engine-setup'. If you want to prevent it from
> upgrading the engine, you can try 'engine-setup --offline'.
>
> You might want to create a github issue about the documentation
> missing this information. If you do, please clarify where you expected
> it to appear and what you searched for when looking for it.
> Alternatively, patches are welcome :-), the oVirt documentation is
> managed in a github repo, with a link in each page "Edit this page".
>
> Good luck and best regards,
> --
> Didi
>
>

-- 


Ce message et toutes les pièces jointes (ci-après le “message”) sont 
établis à l’intention exclusive de ses destinataires et sont confidentiels. 
Si vous recevez ce message par erreur, merci de le détruire et d’en avertir 
immédiatement l’expéditeur. Toute utilisation de ce message non conforme a 
sa destination, toute diffusion ou toute publication, totale ou partielle, 
est interdite, sauf autorisation expresse. L’internet ne permettant pas 
d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) 
décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse 
ou il aurait été modifié. IT, ES, UK.  

___
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/BN23FQXEWIMIPT5N5B3GH3SZ3IYIX2KP/

[ovirt-users] Re: failed to mount hosted engine gluster storage - how to debug?

[diego . ercolani]

yes it seem it worked thank you very much
___
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/EAM5CVMHLWTI4EK2VJFYFN5BANOZAO3R/

[ovirt-users] Re: Notified that Engine's certification is about to expire but no documentation to renew it

[Martin Perina]

Hi Guillaume,

to renew host certificates you need to perform following actions in
webadmin or RESTAPI:

1. Move the host to Maintenance status
2. Execute Enroll Certificates for the host
3. Watch Events on the host to see if Enroll Certificates finished
successfully
4. Execute Activate for the host

Regards,
Martin

On Mon, Apr 25, 2022 at 1:46 PM Guillaume Pavese <
guillaume.pav...@interactiv-group.com> wrote:

> Hello
>
> We are receiving the following notifications from our ovirt manager  :
>
> Message:Engine's certification is about to expire at 2022-05-03. Please
> renew the engine's certification.
> Severity:WARNING
>
>
> Effectively :
>
> # openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -startdate
> -enddate -noout
> notBefore=Mar 30 04:48:15 2021 GMT
> notAfter=May  3 04:48:15 2022 GMT
>
>
> However I can not find any documentation on how to renew this certificate.
> The following doc only convers changing apache-ca.pem & apache.cer, and
> not engine.cer
>
> Doc oVirt :
> https://ovirt.org/documentation/administration_guide/index.html#Replacing_the_Manager_CA_Certificate
> Doc RHV :
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/administration_guide/index#Replacing_the_Manager_CA_Certificate
>
>
> Any help ?
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
> Ce message et toutes les pièces jointes (ci-après le “message”) sont
> établis à l’intention exclusive de ses destinataires et sont confidentiels.
> Si vous recevez ce message par erreur, merci de le détruire et d’en avertir
> immédiatement l’expéditeur. Toute utilisation de ce message non conforme a
> sa destination, toute diffusion ou toute publication, totale ou partielle,
> est interdite, sauf autorisation expresse. L’internet ne permettant pas
> d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales)
> décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse
> ou il aurait été modifié. IT, ES, UK.
> 
> ___
> 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/HWHBRHZDCHKRTMV7SK63URREVPHIZQTI/
>


-- 
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
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/ROJDGIDLQRMQ6E7HQINUVATYDPLR65QI/

[ovirt-users] Re: Notified that Engine's certification is about to expire but no documentation to renew it

[Yedidyah Bar David]

On Mon, Apr 25, 2022 at 2:45 PM Guillaume Pavese
 wrote:
>
> Hello
>
> We are receiving the following notifications from our ovirt manager  :
>
> Message:Engine's certification is about to expire at 2022-05-03. Please renew 
> the engine's certification.
> Severity:WARNING
>
>
> Effectively :
>
> # openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -startdate -enddate 
> -noout
> notBefore=Mar 30 04:48:15 2021 GMT
> notAfter=May  3 04:48:15 2022 GMT
>
>
> However I can not find any documentation on how to renew this certificate.
> The following doc only convers changing apache-ca.pem & apache.cer, and not 
> engine.cer
>
> Doc oVirt : 
> https://ovirt.org/documentation/administration_guide/index.html#Replacing_the_Manager_CA_Certificate
> Doc RHV : 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/administration_guide/index#Replacing_the_Manager_CA_Certificate
>
>
> Any help ?

Please try running 'engine-setup'. If you want to prevent it from
upgrading the engine, you can try 'engine-setup --offline'.

You might want to create a github issue about the documentation
missing this information. If you do, please clarify where you expected
it to appear and what you searched for when looking for it.
Alternatively, patches are welcome :-), the oVirt documentation is
managed in a github repo, with a link in each page "Edit this page".

Good luck and best regards,
-- 
Didi
___
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/FEHKW6RTOOVQUBUH2RZUFG3GUTGETQQP/

[ovirt-users] Re: Cannot remove geo-replication session

[simon]

I removed the slave volumes and recreated them - manually removing entries in 
/etc/fstab that weren't removed.
Recreated geo-rep session and all data replicated to other oVirt Datacenter.
One issue with one of the Master nodes reporting it's status as Faulty - so not 
completely resolved but the Data is now synced.
___
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/XGE5FOH5QPRFBNZFYD56NJ5OMIR4VGMN/

[ovirt-users] Notified that Engine's certification is about to expire but no documentation to renew it

[Guillaume Pavese]

Hello

We are receiving the following notifications from our ovirt manager  :

Message:Engine's certification is about to expire at 2022-05-03. Please
renew the engine's certification.
Severity:WARNING


Effectively :

# openssl x509 -in /etc/pki/ovirt-engine/certs/engine.cer -startdate
-enddate -noout
notBefore=Mar 30 04:48:15 2021 GMT
notAfter=May  3 04:48:15 2022 GMT


However I can not find any documentation on how to renew this certificate.
The following doc only convers changing apache-ca.pem & apache.cer, and
not engine.cer

Doc oVirt :
https://ovirt.org/documentation/administration_guide/index.html#Replacing_the_Manager_CA_Certificate
Doc RHV :
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/administration_guide/index#Replacing_the_Manager_CA_Certificate


Any help ?

Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group

-- 


Ce message et toutes les pièces jointes (ci-après le “message”) sont 
établis à l’intention exclusive de ses destinataires et sont confidentiels. 
Si vous recevez ce message par erreur, merci de le détruire et d’en avertir 
immédiatement l’expéditeur. Toute utilisation de ce message non conforme a 
sa destination, toute diffusion ou toute publication, totale ou partielle, 
est interdite, sauf autorisation expresse. L’internet ne permettant pas 
d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) 
décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse 
ou il aurait été modifié. IT, ES, UK.  

___
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/HWHBRHZDCHKRTMV7SK63URREVPHIZQTI/

[ovirt-users] Re: failed to mount hosted engine gluster storage - how to debug?

[Alessandro De Salvo]

Hi,

please try this workaround, replace the following line in 
/usr/lib/python3.6/site-packages/vdsm/gluster/cli.py



value['stripeCount'] = el.find('stripeCount').text


with:

if (el.find('stripeCount')): value['stripeCount'] = 
el.find('stripeCount').text



Then restart vdsmd and supervdmsd and retry. It worked for me, and it 
looks like a serious bug for people upgrading to glusterfs 10.


Cheers,


    Alessandro


Il 25/04/22 10:58, diego.ercol...@ssis.sm ha scritto:

I saw your report infact, they suggested to downgrade jdbc, for completeness I found also 
error report in vdsm.log while issuing "hosted-engine --connect-storage" 
corresponding to what you are noticing. I report the log except here if it can be useful.
by the way, why vdsm it's searching for the storage engine storage UUID in a 
lvm volumegroup name?


2022-04-25 10:53:35,506+0200 INFO  (Reactor thread) 
[ProtocolDetector.AcceptorImpl] Accepted connection from ::1:47350 
(protocoldetector:61)
2022-04-25 10:53:35,510+0200 INFO  (Reactor thread) [ProtocolDetector.Detector] 
Detected protocol stomp from ::1:47350 (protocoldetector:125)
2022-04-25 10:53:35,510+0200 INFO  (Reactor thread) [Broker.StompAdapter] 
Processing CONNECT request (stompserver:95)
2022-04-25 10:53:35,512+0200 INFO  (JsonRpc (StompReactor)) 
[Broker.StompAdapter] Subscribe command received (stompserver:124)
2022-04-25 10:53:35,518+0200 INFO  (jsonrpc/3) [vdsm.api] START 
getStorageDomainInfo(sdUUID='7b8f1cc9-e3de-401f-b97f-8c281ca30482') 
from=::1,47350, task_id=1803abb2-9e9a-4292-8349-678c793f7264 (api:48)
2022-04-25 10:53:35,518+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Refreshing storage domain cache (resize=True) (sdc:80)
2022-04-25 10:53:35,518+0200 INFO  (jsonrpc/3) [storage.iscsi] Scanning iSCSI 
devices (iscsi:462)
2022-04-25 10:53:35,532+0200 INFO  (jsonrpc/3) [storage.iscsi] Scanning iSCSI 
devices: 0.01 seconds (utils:390)
2022-04-25 10:53:35,532+0200 INFO  (jsonrpc/3) [storage.hba] Scanning FC 
devices (hba:59)
2022-04-25 10:53:35,565+0200 INFO  (jsonrpc/3) [storage.hba] Scanning FC 
devices: 0.03 seconds (utils:390)
2022-04-25 10:53:35,565+0200 INFO  (jsonrpc/3) [storage.multipath] Waiting 
until multipathd is ready (multipath:112)
2022-04-25 10:53:37,556+0200 INFO  (periodic/3) [vdsm.api] START 
repoStats(domains=()) from=internal, 
task_id=f4266860-9162-417e-85a5-087f9cb5cd51 (api:48)
2022-04-25 10:53:37,556+0200 INFO  (periodic/3) [vdsm.api] FINISH repoStats 
return={} from=internal, task_id=f4266860-9162-417e-85a5-087f9cb5cd51 (api:54)
2022-04-25 10:53:37,558+0200 WARN  (periodic/3) [root] Failed to retrieve 
Hosted Engine HA info, is Hosted Engine setup finished? (api:168)
2022-04-25 10:53:37,584+0200 INFO  (jsonrpc/3) [storage.multipath] Waited 2.02 
seconds for multipathd (tries=2, ready=2) (multipath:139)
2022-04-25 10:53:37,584+0200 INFO  (jsonrpc/3) [storage.multipath] Resizing 
multipath devices (multipath:220)
2022-04-25 10:53:37,586+0200 INFO  (jsonrpc/3) [storage.multipath] Resizing 
multipath devices: 0.00 seconds (utils:390)
2022-04-25 10:53:37,586+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Refreshing storage domain cache: 2.07 seconds (utils:390)
2022-04-25 10:53:37,586+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Looking up domain 7b8f1cc9-e3de-401f-b97f-8c281ca30482 (sdc:171)
2022-04-25 10:53:37,643+0200 WARN  (jsonrpc/3) [storage.lvm] All 1 tries have failed: LVM command 
failed: 'cmd=[\'/sbin/lvm\', \'vgs\', \'--devices\', 
\'/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300064E,/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300066N,/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300067L,/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300230B\',
 \'--config\', \'devices {  preferred_names=["^/dev/mapper/"]  ignore_suspended_devices=1  
write_cache_state=0  disable_after_error_count=3hints="none"  
obtain_device_list_from_udev=0 } global {  prioritise_write_locks=1  wait_for_locks=1  use_lvmpolld=1 } 
backup {  retain_min=50  retain_days=0 }\', \'--noheadings\', \'--units\', \'b\', \'--nosuffix\', 
\'--separator\', \'|\', \'--ignoreskippedcluster\', \'-o\', 
\'uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name\',
 \'7b8f1cc9-e3de-401f-b97f-8c281ca30482\'] rc=5 out=[] err=[\'  Volume group "7b8f1cc9-e3de-401f
  -b97f-8c281ca30482" not found\', \'  Cannot process volume group 
7b8f1cc9-e3de-401f-b97f-8c281ca30482\']' (lvm:482)
2022-04-25 10:53:37,643+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Looking up domain 7b8f1cc9-e3de-401f-b97f-8c281ca30482: 0.06 seconds (utils:390)
2022-04-25 10:53:37,643+0200 INFO  (jsonrpc/3) [vdsm.api] FINISH 
getStorageDomainInfo error=Storage domain does not exist: 
('7b8f1cc9-e3de-401f-b97f-8c281ca30482',) from=::1,47350, 
task_id=1803abb2-9e9a-4292-8349-678c793f7264 (api:52)
2022-04-25 10:53:37,643+0200 ERROR (jsonrpc/3) [storage.taskmanager.task] 
(Task='1803abb2-9e9a-4292-8349-678c793f7264') Unexpected 

[ovirt-users] Re: Windows VMs randomly wont boot after compatibility change

[David Sekne]

Hello,

I played around a bit with the emulated machine option and I see we have a
slight misunderstanding. We upgraded the cluster compatibility level to 4.5
last year at which time indeed we had to reconfigure most of the NIC's on
Windows VM's (I forgot we had to do this as it wasnt my task). We changed
from 4.5 to 4.6 not long ago and there were no changes needed on VMs at
that time.

The problem we are seeing and started after the update to 4.5 is that VMs
randomly won't boot at all (reboot is initiated through OS). The VM is
stuck at the boot screen (picture attached) indefinitely and the VM can
only be booted if you stop/start it.

[image: image.png]

Have you seen any similar issues?

Regards,
David

On Fri, Apr 22, 2022 at 7:06 PM Erez Zarum  wrote:

> Hey,
> This only happens to Windows VMs mostly, when you update the cluster
> compatibility level it should alert you on VMs that might have this issues
> and let you know before you resume the upgrade.
>
>
> On Fri, Apr 22, 2022 at 8:04 PM David Sekne  wrote:
>
>> Hello,
>>
>> I followed the documentation on updating the compatibility version. We
>> had no issues with NIC's, all VMs just needed a reboot. No other issues
>> were displayed for VM's after the reboot (we have around 400 VMs) so not
>> sure which changes we would need to do on VM's themselves?
>>
>> I will try to change the emulated machine for Windows VMs to see if it
>> helps (other OS's have no issues).
>>
>> Thank you for the help.
>>
>> Regards,
>> David
>>
>> On Fri, Apr 22, 2022 at 3:02 PM Erez Zarum  wrote:
>>
>>> Hey,
>>> This is noted in the documents:
>>> https://www.ovirt.org/documentation/upgrade_guide/index.html#Changing_the_Cluster_Compatibility_Version_minor_updates
>>> I recommend if you can't cope with it (i.e: logging to console and
>>> reconfiguring the NICs/Disks) it to change the VM custom emulated machine
>>> to "pc-q35-rhel8.1.0", this is the default emulated machine when cluster
>>> compatibility level is set to 4.4.
>>> Also note, if you heavily rely on VNC, there's a bug introduced in
>>> libvirt 8 that won't allow to set password length longer than 8 chars,
>>> oVirt by default tries to set a password length of 12 chars but up until
>>> now libvirt simply ignored that and set the password based on the first 8
>>> chars, i don't know from which version that happened but in 4.4.10 you
>>> won't be able to use VNC so i recommend to use SPICE (which is actually
>>> much better).
>>>
>>>
>>>
>>> On Fri, Apr 22, 2022 at 2:57 PM David Sekne 
>>> wrote:
>>>
 Hello,

 I have noticed that some of our Windows VM's (2012 - 2022)
 randomly won't boot when reboot is initiated from guest OS. As far as I can
 tell this started happening after we raised the cluster compatibility from
 4.4 to 4.5 (it's 4.6 now). To fix it a VM needs to be stopped and started.

 We are running oVirt 4.4.10.

 I cannot really see much from the logs if grepping for a specific VM
 that had these issues.

 Example VM ID is: daf33e97-a76f-4b82-b4f2-20fa4891c88b

 Im attaching logs:

 - Initial hypervisor where VM was running on (reboot is initiated at
 4:06:38 AM): vdsm-1.log
 - Second hypervisor where VM was started after it was stopped and
 started back (this was done 7:45:43 AM): vdsm-2.log
 - Engine log: engine.log

 Has someone noticed any similar issues and can provide some feedback /
 help?

 Regards,
 David
 ___
 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/GGAVCU7PPGITPAPZVABJEROFSF3CKXUD/

>>>
___
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/HFBVMLXES3ACDM7JFTREMPLQEGUJ3F3A/

[ovirt-users] Re: Installing new self-hosted engine v4.5.0 on gluster 10

[Alessandro De Salvo]

Hi,

I think I've found the root of the problem, it is a bug in vdsm. Gluster 
10 produces xml description without the stripeCount tag, while vdsm 
expects it to be present.


I've tried to fix it simply adding a check in 
/usr/lib/python3.6/site-packages/vdsm/gluster/cli.py


429c429
< if (el.find('stripeCount')): value['stripeCount'] = 
el.find('stripeCount').text

---
> value['stripeCount'] = el.find('stripeCount').text

In this way, after restarting vdsmd and supervdsmd, I'm able to connect 
to gluster 10 volumes.


I guess this should be fixed in possibly a more proper way upstream.

Cheers,


    Alessandro


Il 25/04/22 09:41, Alessandro De Salvo ha scritto:

Hi,
thanks, unfortunately I’ve done it already, otherwise it would not 
even start the engine. This error appears after the engine is up with 
the downgraded postgresql-jdbc.

Cheers,

   Alessandro

Il giorno 25 apr 2022, alle ore 06:11, Strahil Nikolov 
 ha scritto:


Mybe it's worth trying to downgrade postgresql-jdbc and try again.

Best Regards,
Strahil Nikolov

On Mon, Apr 25, 2022 at 4:52, Alessandro De Salvo
 wrote:
To complete the diagnosis, in vdsm.log I see the following error:


vdsm.gluster.exception.GlusterXmlErrorException: XML error: rc=0
out=()
err=[b'\n 0\n 0\n
\n \n \n \n
vm-01\n d77d9a24-5f30-4acb-962c-559e63917229\n
1\n Started\n
0\n 3\n
1\n 3\n
1\n 0\n
0\n 2\n
Replicate\n 0\n
\n  host1:/gluster/vm/01/datahost1:/gluster/vm/01/data09e78070-4d55-4a96-ada7-658e7e2799a60\n

host2:/gluster/vm/01/datahost2:/gluster/vm/01/datafb9eb3ab-a260-4ef7-94cf-f03c630d7b970\n

host3:/gluster/vm/01/datahost3:/gluster/vm/01/datacabe4f02-eb45-486e-97e0-3e2466415fd01\n

\n 24\n \n 
\n
nfs.disable\n on\n \n
\n transport.address-family\n
inet\n
\n  \n
performance.quick-read\n
off\n \n  \n
performance.read-ahead\n off\n
\n  \n performance.io-cache\n
off\n \n  \n
performance.stat-prefetch\n off\n
\n  \n
performance.low-prio-threads\n 32\n
\n  \n network.remote-dio\n
enable\n \n  \n
cluster.eager-lock\n enable\n
\n  \n cluster.quorum-type\n
auto\n \n  \n
cluster.server-quorum-type\n server\n
\n  \n
cluster.data-self-heal-algorithm\n
full\n
\n  \n
cluster.locking-scheme\n
granular\n \n  \n
cluster.shd-max-threads\n 8\n
\n \n cluster.shd-wait-qlength\n
1\n \n  \n
features.shard\n on\n \n
\n user.cifs\n off\n
\n  \n
features.shard-block-size\n
512MB\n \n  \n
storage.owner-uid\n 36\n
\n  \n storage.owner-gid\n
36\n \n  \n
features.cache-invalidation\n off\n
\n  \n
performance.client-io-threads\n off\n
\n  \n nfs-ganesha\n
disable\n \n  \n
cluster.enable-shared-storage\n
disable\n
\n    \n \n  1\n
\n \n']


Thanks,


    Alessandro


Il 25/04/22 01:02, Alessandro De Salvo ha scritto:
> Hi,
>
> I'm trying to install a new self-hosted engine 4.5.0 on an
upgraded
> gluster v10.1, but the deployment fails at the domain activation
> stage, with this error:
>
>
> [ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Activate storage
> domain]
> [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed".
Fault
> detail is "[]". HTTP response code is 400.
>
>
> Looking at the server.log in the engine I see the follwing error:
>
>
> 2022-04-25 00:55:58,266+02 ERROR
> [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1)
> RESTEASY002010: Failed to execute:
> javax.ws.rs.WebApplicationException: HTTP 404 Not Found
>     at
>

org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BaseBackendResource.handleError(BaseBackendResource.java:236)
>     at
>

org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendResource.getEntity(BackendResource.java:119)
>     at
>

org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendResource.getEntity(BackendResource.java:99)
>     at
>

org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.performGet(AbstractBackendSubResource.java:34)
>     at
>

org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.performGet(AbstractBackendSubResource.java:30)
>     at
>

org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainResource.get(BackendAttachedStorageDomainResource.java:35)
>     at
>

[ovirt-users] Re: Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update

[Patrick Hibbs]

That error typically means you don't have the correct DUD for the
kernel you are using. Each DUD is kernel specific, and will only work
on the kernel it was built for.

You need to find whatever DUD matches the kernel used in oVirt Node
4.4.10.

Alternatively, to quote the inevitable response from Sandro Bonazzola:
"oVirt Node 4.4 is now EOL. Please upgrade to oVirt Node 4.5 as soon as
practical."

-Patrick Hibbs

On Fri, 2022-04-22 at 22:19 +, peter...@guest-tek.com wrote:
> Hello, 
> 
> I'm trying to install Ovirt Node 4.4.10 to my server and it gets an
> error when I'm trying to install iso for my MPT SAS driver by using
> DUD. 
> In the boot menu, I pressed tab to enter Kernel and added "inst,dd".
> After that I got a screen shows a list of disk devices and selected
> USB that has iso file for MPT SAS :
> "Device : sda1 / Type : Vfat / Label : OEMDRV / UUDI : 6837-8481"
> 
> Then, I selected drivers to install : 
> "/media/DD-2/rpms/x86_64/kmod-mptsas-3.04.20-
> 6.e18_5.elrepo.x86_64.rpm"
> 
> And I pressed "C" to continue and gets an error message below :
> 
> "modprobe : ERROR : could not insert 'mptsas' : invalid argument"
> 
> Could you please help me what's the next step I can try to fix the
> issue? 
> 
> Thank you
> ___
> 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/ARCK2NHPQ4AQK7I5EUISUCSQCTHXIV7Q/

___
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/YPK6NWVAMJWELMLDGABQLOMCVURAROJP/

[ovirt-users] Re: AMD Ryzen 5600G unsupported?

[diego . ercolani]

Please remember to enable tha AMD-V support in the bios, every time you upgrade 
bios they normally reset to "disabled".
You can find this issue when in logs appears something like:

Apr 20 11:45:11 ovirt-node3 journal[2011]: Unable to open /dev/kvm: No such 
file or directory

to resolve remember to launch the command: 
virt-host-validate
it checks the host environment to verify qemu support

___
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/WRBSFTMFYUEW3URJUOXFOTAZJY7YO2DV/

[ovirt-users] Re: failed to mount hosted engine gluster storage - how to debug?

[diego . ercolani]

I saw your report infact, they suggested to downgrade jdbc, for completeness I 
found also error report in vdsm.log while issuing "hosted-engine 
--connect-storage" corresponding to what you are noticing. I report the log 
except here if it can be useful.
by the way, why vdsm it's searching for the storage engine storage UUID in a 
lvm volumegroup name?


2022-04-25 10:53:35,506+0200 INFO  (Reactor thread) 
[ProtocolDetector.AcceptorImpl] Accepted connection from ::1:47350 
(protocoldetector:61)
2022-04-25 10:53:35,510+0200 INFO  (Reactor thread) [ProtocolDetector.Detector] 
Detected protocol stomp from ::1:47350 (protocoldetector:125)
2022-04-25 10:53:35,510+0200 INFO  (Reactor thread) [Broker.StompAdapter] 
Processing CONNECT request (stompserver:95)
2022-04-25 10:53:35,512+0200 INFO  (JsonRpc (StompReactor)) 
[Broker.StompAdapter] Subscribe command received (stompserver:124)
2022-04-25 10:53:35,518+0200 INFO  (jsonrpc/3) [vdsm.api] START 
getStorageDomainInfo(sdUUID='7b8f1cc9-e3de-401f-b97f-8c281ca30482') 
from=::1,47350, task_id=1803abb2-9e9a-4292-8349-678c793f7264 (api:48)
2022-04-25 10:53:35,518+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Refreshing storage domain cache (resize=True) (sdc:80)
2022-04-25 10:53:35,518+0200 INFO  (jsonrpc/3) [storage.iscsi] Scanning iSCSI 
devices (iscsi:462)
2022-04-25 10:53:35,532+0200 INFO  (jsonrpc/3) [storage.iscsi] Scanning iSCSI 
devices: 0.01 seconds (utils:390)
2022-04-25 10:53:35,532+0200 INFO  (jsonrpc/3) [storage.hba] Scanning FC 
devices (hba:59)
2022-04-25 10:53:35,565+0200 INFO  (jsonrpc/3) [storage.hba] Scanning FC 
devices: 0.03 seconds (utils:390)
2022-04-25 10:53:35,565+0200 INFO  (jsonrpc/3) [storage.multipath] Waiting 
until multipathd is ready (multipath:112)
2022-04-25 10:53:37,556+0200 INFO  (periodic/3) [vdsm.api] START 
repoStats(domains=()) from=internal, 
task_id=f4266860-9162-417e-85a5-087f9cb5cd51 (api:48)
2022-04-25 10:53:37,556+0200 INFO  (periodic/3) [vdsm.api] FINISH repoStats 
return={} from=internal, task_id=f4266860-9162-417e-85a5-087f9cb5cd51 (api:54)
2022-04-25 10:53:37,558+0200 WARN  (periodic/3) [root] Failed to retrieve 
Hosted Engine HA info, is Hosted Engine setup finished? (api:168)
2022-04-25 10:53:37,584+0200 INFO  (jsonrpc/3) [storage.multipath] Waited 2.02 
seconds for multipathd (tries=2, ready=2) (multipath:139)
2022-04-25 10:53:37,584+0200 INFO  (jsonrpc/3) [storage.multipath] Resizing 
multipath devices (multipath:220)
2022-04-25 10:53:37,586+0200 INFO  (jsonrpc/3) [storage.multipath] Resizing 
multipath devices: 0.00 seconds (utils:390)
2022-04-25 10:53:37,586+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Refreshing storage domain cache: 2.07 seconds (utils:390)
2022-04-25 10:53:37,586+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Looking up domain 7b8f1cc9-e3de-401f-b97f-8c281ca30482 (sdc:171)
2022-04-25 10:53:37,643+0200 WARN  (jsonrpc/3) [storage.lvm] All 1 tries have 
failed: LVM command failed: 'cmd=[\'/sbin/lvm\', \'vgs\', \'--devices\', 
\'/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300064E,/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300066N,/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300067L,/dev/mapper/Samsung_SSD_870_EVO_4TB_S6BCNG0R300230B\',
 \'--config\', \'devices {  preferred_names=["^/dev/mapper/"]  
ignore_suspended_devices=1  write_cache_state=0  disable_after_error_count=3
hints="none"  obtain_device_list_from_udev=0 } global {  
prioritise_write_locks=1  wait_for_locks=1  use_lvmpolld=1 } backup {  
retain_min=50  retain_days=0 }\', \'--noheadings\', \'--units\', \'b\', 
\'--nosuffix\', \'--separator\', \'|\', \'--ignoreskippedcluster\', \'-o\', 
\'uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name\',
 \'7b8f1cc9-e3de-401f-b97f-8c281ca30482\'] rc=5 out=[] err=[\'  Volume group 
"7b8f1cc9-e3de-401f
 -b97f-8c281ca30482" not found\', \'  Cannot process volume group 
7b8f1cc9-e3de-401f-b97f-8c281ca30482\']' (lvm:482)
2022-04-25 10:53:37,643+0200 INFO  (jsonrpc/3) [storage.storagedomaincache] 
Looking up domain 7b8f1cc9-e3de-401f-b97f-8c281ca30482: 0.06 seconds (utils:390)
2022-04-25 10:53:37,643+0200 INFO  (jsonrpc/3) [vdsm.api] FINISH 
getStorageDomainInfo error=Storage domain does not exist: 
('7b8f1cc9-e3de-401f-b97f-8c281ca30482',) from=::1,47350, 
task_id=1803abb2-9e9a-4292-8349-678c793f7264 (api:52)
2022-04-25 10:53:37,643+0200 ERROR (jsonrpc/3) [storage.taskmanager.task] 
(Task='1803abb2-9e9a-4292-8349-678c793f7264') Unexpected error (task:877)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in 
_run
return fn(*args, **kargs)
  File "", 
line 2, in getStorageDomainInfo
  File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method
ret = func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2463, in 
getStorageDomainInfo
dom = self.validateSdUUID(sdUUID)
  File 

[ovirt-users] Re: AMD Ryzen 5600G unsupported?

[Gilboa Davara]

... Thanks.

Same here. Worked in the end following a BIOS reset.

- Gilboa

On Mon, Apr 25, 2022 at 10:30 AM  wrote:

> In my system is correctly recognized:
> Manufacturer:
> Gigabyte Technology Co., Ltd.
> Family:
> B550 MB
> Product Name:
> B550 AORUS ELITE V2
> Version:
> Default string
> UUID:
> 03C00218-044D-05AE-3406-0D0700080009
> Serial Number:
> Default string
> CPU Model Name:
> AMD Ryzen 7 5700G with Radeon Graphics
> Tipo CPU:
> Secure AMD EPYC
> CPU Sockets:
> 1
> CPU Cores per Socket:
> 8
> CPU Threads per Core:
> 2 (SMT Abilitato)
> TSC Frequency:
> 3819092000 (scaling enabled)
>
>
> (ovirt-engine: 4.5.0.4-1.el8, ovirt-node: 4.5.0)
> ___
> 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/NN7QLJJ6ZGQAHYQBKIQWVYDKW7GOGSEK/
>
___
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/GZS7X6OVZIO7ZSEOITOUBJCBGXQZ26C6/

[ovirt-users] Re: failed to mount hosted engine gluster storage - how to debug?

[Alessandro De Salvo]

Hi,
I think it may be a problem with vdsm and gluster 10, I’ve reported a similar 
issue in another thread. Vdsm is throwing an exception when parsing the XML 
from the gluster volume info when using the latest gluster version 10. This is 
particularly bad when the gluster server updates have been completed by moving 
the op-version, as it’s basically irreversible and it’s not even possible to 
easily downgrade gluster. If you downgrade to or use a gluster 8 works in fact.
I’m digging the code of vdsm to see if I can find the root cause.
Cheers,

   Alessandro

> Il giorno 25 apr 2022, alle ore 09:24, diego.ercol...@ssis.sm ha scritto:
> 
> Hello, I have an issue probably related to my particular implementation but 
> I think some controls are missing
> Here is the story.
> I have a cluster of two nodes 4.4.10.3 with an upgraded kernel as the cpu 
> (Ryzen 5) suffer from an incompatibility issue with the kernel provided by 
> 4.4.10.x series.
> On each node there are three glusterfs "partitions" in replica mode, one for 
> the hosted_engine, the other two are for user usage.
> The third node was an old i3 workstation only used to provide the arbiter 
> partition to the glusterfs cluster.
> I installed a new server (ryzen processor) with 4.5.0 and successfully 
> installed glusterfs 10.1 and inserted the arbiter bricks implemented on 
> glusterfs 10.1 while the replica bricks are 8.6 after removing the old i3 
> provided bricks.
> I successfully imported the new node in the ovirt engine (after updating the 
> engine to 4.5)
> The problem is that the ovirt-ha-broker doesn't start complaining that is not 
> possible to connect the storage. (I suppose the hosted_engine storage) so I 
> did some digs that I'm going to show here:
> 
> 
> 1. The node seem to be correctly configured:
> [root@ovirt-node3 devices]# vdsm-tool validate-config   
> SUCCESS: ssl configured to true. No conflicts
> [root@ovirt-node3 devices]# vdsm-tool configure   
> 
> Checking configuration status...
> 
> libvirt is already configured for vdsm
> SUCCESS: ssl configured to true. No conflicts
> sanlock is configured for vdsm
> Managed volume database is already configured
> lvm is configured for vdsm
> Current revision of multipath.conf detected, preserving
> 
> Running configure...
> 
> Done configuring modules to VDSM.
> [root@ovirt-node3 devices]# vdsm-tool validate-config 
> SUCCESS: ssl configured to true. No conflicts
> 
> 
> 2. the node refuses to mount via hosted-engine (same error in broker.log)
> [root@ovirt-node3 devices]# hosted-engine --connect-storage
> Traceback (most recent call last):
>  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
>"__main__", mod_spec)
>  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
>exec(code, run_globals)
>  File 
> "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py",
>  line 30, in 
>timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT,
>  File 
> "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", 
> line 312, in connect_storage_server
>sserver.connect_storage_server(timeout=timeout)
>  File 
> "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py",
>  line 451, in connect_storage_server
>'Connection to storage server failed'
> RuntimeError: Connection to storage server failed
> 
> #
> 3. manually mount of glusterfs work correctly
> [root@ovirt-node3 devices]# grep storage 
> /etc/ovirt-hosted-engine/hosted-engine.conf   
> storage=ovirt-node2.ovirt:/gveng
> # The following are used only for iSCSI storage
> [root@ovirt-node3 devices]# 
> [root@ovirt-node3 devices]# mount -t glusterfs ovirt-node2.ovirt:/gveng 
> /mnt/tmp/
> [root@ovirt-node3 devices]# ls -l /mnt/tmp
> total 0
> drwxr-xr-x. 6 vdsm kvm 64 Dec 15 19:04 7b8f1cc9-e3de-401f-b97f-8c281ca30482
> 
> 
> What else should I control? Thank you and sorry for the long message
> Diego
> ___
> 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/4LGBUOEBV7YNESM7N2TJSXOC4ERN3W23/
___
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/T5Y6XKFJ5X3CVZQF3SSFQK2HS7ZSTVMA/

[ovirt-users] Re: Error 500 on Hosted Engine admin portal!!!

[Alessandro De Salvo]

Hi,
I’m not sure if it works with the web installer, but if you deploy with CLI you 
can use the following to ask the installer to pause before running engine-setup:

hosted-engine --deploy --ansible-extra-vars=he_pause_before_engine_setup=true

This gives you the time to ssh and exclude the offending package before the 
installer attempts to upgrade any package.
Cheers,

   Alessandro

> Il giorno 25 apr 2022, alle ore 09:27, lpat...@siriusag.com ha scritto:
> 
> This is the cause, yes Martin - but it wont help since the 
> Installer/deployment does an update while running, so "almost" no way to 
> bypass that
> 
> WORKAROUND:
> preparation: 
> - ssh login to the node, prepare ssh root@
> - copy paste buffer ready: echo exclude=postgresql-jdbc >> /etc/dnf/dnf.conf
> 
> when the webinstaller is running, the moment when the ip of the hosted engine 
> vm is displayed (something like 192.168.222.208) immediately ssh to that vm 
> from the host
> and execute the copy paste buffer before the dnf update takes place
> 
> uggly workaround, maybe there's another better option, but hey, it describes 
> the problem and works :)
> 
> Cheers
> Luis
> ___
> 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/ULUGCT73FOPPAY7EVBIJC4KBDGU22GDM/
___
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/UZALUJRVR4E7RABUGTSQJT6YYY7LQYK7/

[ovirt-users] Re: Installing new self-hosted engine v4.5.0 on gluster 10

[Alessandro De Salvo]

Hi,
thanks, unfortunately I’ve done it already, otherwise it would not even start 
the engine. This error appears after the engine is up with the downgraded 
postgresql-jdbc.
Cheers,

   Alessandro

> Il giorno 25 apr 2022, alle ore 06:11, Strahil Nikolov 
>  ha scritto:
> 
> Mybe it's worth trying to downgrade postgresql-jdbc and try again.
> 
> Best Regards,
> Strahil Nikolov
> 
> On Mon, Apr 25, 2022 at 4:52, Alessandro De Salvo
>  wrote:
> To complete the diagnosis, in vdsm.log I see the following error:
> 
> 
> vdsm.gluster.exception.GlusterXmlErrorException: XML error: rc=0 out=() 
> err=[b'\n  0\n 0\n  
> \n \n\n \n
> vm-01\n d77d9a24-5f30-4acb-962c-559e63917229\n 
> 1\n Started\n 
> 0\n 3\n 
> 1\n 3\n 
> 1\n 0\n 
> 0\n 2\n 
> Replicate\n 0\n 
> \n   uuid="09e78070-4d55-4a96-ada7-658e7e2799a6">host1:/gluster/vm/01/datahost1:/gluster/vm/01/data09e78070-4d55-4a96-ada7-658e7e2799a60\n
>  
>  uuid="fb9eb3ab-a260-4ef7-94cf-f03c630d7b97">host2:/gluster/vm/01/datahost2:/gluster/vm/01/datafb9eb3ab-a260-4ef7-94cf-f03c630d7b970\n
>  
>  uuid="cabe4f02-eb45-486e-97e0-3e2466415fd0">host3:/gluster/vm/01/datahost3:/gluster/vm/01/datacabe4f02-eb45-486e-97e0-3e2466415fd01\n
>  
> \n 24\n \n  \n 
> nfs.disable\n on\n \n  
> \n transport.address-family\n inet\n 
> \n  \n performance.quick-read\n 
> off\n \n  \n 
> performance.read-ahead\n off\n 
> \n  \n performance.io-cache\n 
> off\n \n  \n 
> performance.stat-prefetch\n off\n 
> \n  \n 
> performance.low-prio-threads\n 32\n 
> \n  \n network.remote-dio\n 
> enable\n \n  \n 
> cluster.eager-lock\n enable\n 
> \n  \n cluster.quorum-type\n 
> auto\n \n  \n 
> cluster.server-quorum-type\n server\n 
> \n  \n 
> cluster.data-self-heal-algorithm\n full\n 
> \n  \n cluster.locking-scheme\n
> granular\n \n  \n 
> cluster.shd-max-threads\n 8\n  
> \n \n cluster.shd-wait-qlength\n 
> 1\n \n  \n 
> features.shard\n on\n \n  
> \n user.cifs\n off\n 
> \n  \n features.shard-block-size\n 
> 512MB\n \n  \n 
> storage.owner-uid\n 36\n 
> \n  \n storage.owner-gid\n 
> 36\n \n  \n 
> features.cache-invalidation\n off\n 
> \n  \n 
> performance.client-io-threads\n off\n 
> \n  \n nfs-ganesha\n 
> disable\n \n  \n 
> cluster.enable-shared-storage\n disable\n 
> \n\n \n  1\n 
> \n  \n']
> 
> 
> Thanks,
> 
> 
> Alessandro
> 
> 
> Il 25/04/22 01:02, Alessandro De Salvo ha scritto:
> > Hi,
> >
> > I'm trying to install a new self-hosted engine 4.5.0 on an upgraded 
> > gluster v10.1, but the deployment fails at the domain activation 
> > stage, with this error:
> >
> >
> > [ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Activate storage 
> > domain]
> > [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault 
> > detail is "[]". HTTP response code is 400.
> >
> >
> > Looking at the server.log in the engine I see the follwing error:
> >
> >
> > 2022-04-25 00:55:58,266+02 ERROR 
> > [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) 
> > RESTEASY002010: Failed to execute: 
> > javax.ws.rs.WebApplicationException: HTTP 404 Not Found
> > at 
> > org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BaseBackendResource.handleError(BaseBackendResource.java:236)
> > at 
> > org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendResource.getEntity(BackendResource.java:119)
> > at 
> > org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendResource.getEntity(BackendResource.java:99)
> > at 
> > org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.performGet(AbstractBackendSubResource.java:34)
> > at 
> > org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.performGet(AbstractBackendSubResource.java:30)
> > at 
> > org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainResource.get(BackendAttachedStorageDomainResource.java:35)
> > at 
> > org.ovirt.engine.api.restapi-definition//org.ovirt.engine.api.resource.AttachedStorageDomainResource.doGet(AttachedStorageDomainResource.java:81)
> > at 
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> > Method)
> > at 
> > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at 
> > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> >
> >
> > The gluster volume itself is working fine and has the storage uid/gid 
> > set to 36 as it should be, and if I use a server with gluster 8 the 
> > installation works, while it 

[ovirt-users] Re: AMD Ryzen 5600G unsupported?

[diego . ercolani]

In my system is correctly recognized:
Manufacturer:
Gigabyte Technology Co., Ltd.
Family:
B550 MB
Product Name:
B550 AORUS ELITE V2
Version:
Default string
UUID:
03C00218-044D-05AE-3406-0D0700080009
Serial Number:
Default string
CPU Model Name:
AMD Ryzen 7 5700G with Radeon Graphics
Tipo CPU:
Secure AMD EPYC
CPU Sockets:
1
CPU Cores per Socket:
8
CPU Threads per Core:
2 (SMT Abilitato)
TSC Frequency:
3819092000 (scaling enabled) 


(ovirt-engine: 4.5.0.4-1.el8, ovirt-node: 4.5.0)
___
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/NN7QLJJ6ZGQAHYQBKIQWVYDKW7GOGSEK/

[ovirt-users] Re: How to configure oVirt for OKD 4.10

[Avital Pinnick]

Sandro and Marcellus,

The "Installing on oVirt" section does not appear in the 4.10 or 4.11 topic
maps. The section was probably overlooked when the original topic map was
split into multiple files. I created an issue
 to fix this.

Avital

On Thu, Apr 21, 2022 at 11:14 AM Sandro Bonazzola 
wrote:

> Il giorno gio 21 apr 2022 alle ore 09:52 marcellus major <
> marcellusmajo...@gmail.com> ha scritto:
>
>> Recently,
>>
>> I watched a video made by Gal Zadman detailing how to install OKD on oVirt
>> Is there any documentation detailing how Gal configured the oVirt
>> environment prior to installation
>> of OKD?
>>
>
> Looping in +Janos Bonic  , +Evgeny Slutsky
>  and +Avital Pinnick  .
> Apparently, https://docs.okd.io/4.10/installing/index.html is not listing
> ovirt anymore, sounds like a bug in OKD docs.
>
> Marcellus, you can follow 4.9 documentation:
> https://docs.okd.io/4.9/installing/installing_rhv/installing-rhv-default.html#installing-rhv-requirements_installing-rhv-default
> and use oVirt 4.5 instead of oVirt 4.4.
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>
___
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/RKDXZQNRCXYHY7B3GU7U73UHLWBAC7BC/

[ovirt-users] Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update

[peter . yu]

Hello, 

I'm trying to install Ovirt Node 4.4.10 to my server and it gets an error when 
I'm trying to install iso for my MPT SAS driver by using DUD. 
In the boot menu, I pressed tab to enter Kernel and added "inst,dd".
After that I got a screen shows a list of disk devices and selected USB that 
has iso file for MPT SAS :
"Device : sda1 / Type : Vfat / Label : OEMDRV / UUDI : 6837-8481"

Then, I selected drivers to install : 
"/media/DD-2/rpms/x86_64/kmod-mptsas-3.04.20-6.e18_5.elrepo.x86_64.rpm"

And I pressed "C" to continue and gets an error message below :

"modprobe : ERROR : could not insert 'mptsas' : invalid argument"

Could you please help me what's the next step I can try to fix the issue? 

Thank you
___
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/ARCK2NHPQ4AQK7I5EUISUCSQCTHXIV7Q/

[ovirt-users] Re: Error 500 on Hosted Engine admin portal!!!

[lpatsch]

This is the cause, yes Martin - but it wont help since the Installer/deployment 
does an update while running, so "almost" no way to bypass that

WORKAROUND:
preparation: 
- ssh login to the node, prepare ssh root@
- copy paste buffer ready: echo exclude=postgresql-jdbc >> /etc/dnf/dnf.conf

when the webinstaller is running, the moment when the ip of the hosted engine 
vm is displayed (something like 192.168.222.208) immediately ssh to that vm 
from the host
and execute the copy paste buffer before the dnf update takes place

uggly workaround, maybe there's another better option, but hey, it describes 
the problem and works :)

Cheers
Luis
___
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/ULUGCT73FOPPAY7EVBIJC4KBDGU22GDM/

[ovirt-users] failed to mount hosted engine gluster storage - how to debug?

[diego . ercolani]

Hello, I have an issue probably related to my particular implementation but I 
think some controls are missing
Here is the story.
I have a cluster of two nodes 4.4.10.3 with an upgraded kernel as the cpu 
(Ryzen 5) suffer from an incompatibility issue with the kernel provided by 
4.4.10.x series.
On each node there are three glusterfs "partitions" in replica mode, one for 
the hosted_engine, the other two are for user usage.
The third node was an old i3 workstation only used to provide the arbiter 
partition to the glusterfs cluster.
I installed a new server (ryzen processor) with 4.5.0 and successfully 
installed glusterfs 10.1 and inserted the arbiter bricks implemented on 
glusterfs 10.1 while the replica bricks are 8.6 after removing the old i3 
provided bricks.
I successfully imported the new node in the ovirt engine (after updating the 
engine to 4.5)
The problem is that the ovirt-ha-broker doesn't start complaining that is not 
possible to connect the storage. (I suppose the hosted_engine storage) so I did 
some digs that I'm going to show here:


1. The node seem to be correctly configured:
[root@ovirt-node3 devices]# vdsm-tool validate-config   
SUCCESS: ssl configured to true. No conflicts
[root@ovirt-node3 devices]# vdsm-tool configure   

Checking configuration status...

libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts
sanlock is configured for vdsm
Managed volume database is already configured
lvm is configured for vdsm
Current revision of multipath.conf detected, preserving

Running configure...

Done configuring modules to VDSM.
[root@ovirt-node3 devices]# vdsm-tool validate-config 
SUCCESS: ssl configured to true. No conflicts


2. the node refuses to mount via hosted-engine (same error in broker.log)
[root@ovirt-node3 devices]# hosted-engine --connect-storage
Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py",
 line 30, in 
timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT,
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 312, in connect_storage_server
sserver.connect_storage_server(timeout=timeout)
  File 
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py",
 line 451, in connect_storage_server
'Connection to storage server failed'
RuntimeError: Connection to storage server failed

#
3. manually mount of glusterfs work correctly
[root@ovirt-node3 devices]# grep storage 
/etc/ovirt-hosted-engine/hosted-engine.conf   
storage=ovirt-node2.ovirt:/gveng
# The following are used only for iSCSI storage
[root@ovirt-node3 devices]# 
[root@ovirt-node3 devices]# mount -t glusterfs ovirt-node2.ovirt:/gveng 
/mnt/tmp/
[root@ovirt-node3 devices]# ls -l /mnt/tmp
total 0
drwxr-xr-x. 6 vdsm kvm 64 Dec 15 19:04 7b8f1cc9-e3de-401f-b97f-8c281ca30482


What else should I control? Thank you and sorry for the long message
Diego
___
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/4LGBUOEBV7YNESM7N2TJSXOC4ERN3W23/

[ovirt-users] Re: engine.rar

[Nazeem Durgahee]

Hi Sandro,

This what I am getting while trying to upgrade.

Complete!
[root@fscdrs-ovirt-001 ~]# dnf install -y centos-release-ovirt45
Last metadata expiration check: 0:02:50 ago on Fri 22 Apr 2022 01:51:06 PM +04.
No match for argument: centos-release-ovirt45
Error: Unable to find a match: centos-release-ovirt45

From: Sandro Bonazzola 
Sent: Thursday, April 21, 2022 12:17 PM
To: Nazeem Durgahee 
Cc: Veeroo Dowlut ; Govind Mooroogen 
; users@ovirt.org
Subject: Re: [ovirt-users] engine.rar



Il giorno gio 21 apr 2022 alle ore 10:13 Nazeem Durgahee 
mailto:nazeem.durga...@harelmallac.com>> ha 
scritto:

HI,

We have ovirt 4.4.10 running on oracle linux 8 but we are having issues with 
netbackup whereby it is not removing the snapshot after VM backup.

Kindly find attached engine log.

Can you please upgrade to 4.5.0 and try to reproduce?
More info:
* https://blogs.ovirt.org/2022/04/ovirt-4-5-0-is-now-generally-available/
* https://blogs.ovirt.org/2022/04/ovirt-4-4-end-of-life/

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA

sbona...@redhat.com
[https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]
Red Hat respects your work life balance. Therefore there is no need to answer 
this email out of your office hours.

___
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/QLLESB6QUUXSAR7HL7JN6Y5N6CLNNQ2Y/