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

2022-04-23 Thread Patrick Lomakin 
Hi everyone! Did the oVirt team check the 4.5 update before release? I've 
update my production latest 4.4.10 version and get Error 500 on admin page. 
Clean installation on another bare-metal node using Ovirt Node 4.5 and 
hosted-engine console setup (installing through the web installer several 
versions of Ovirt traditionally makes the connection break and disconnects 
access to the host by means of the IP address) get an error 500 after 
healthcheck. What I will do in this situation?
Httpd log:
[Sat Apr 23 15:54:59.826076 2022] [core:notice] [pid 1526:tid 140201844767040] 
AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Sat Apr 23 15:55:05.685872 2022] [proxy:error] [pid 2125:tid 140201102243584] 
(111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 
(127.0.0.1) failed
[Sat Apr 23 15:55:05.685924 2022] [proxy_ajp:error] [pid 2125:tid 
140201102243584] [client 192.168.0.14:43194] AH00896: failed to make connection 
to backend: 127.0.0.1
[Sat Apr 23 15:55:15.831754 2022] [proxy:error] [pid 2125:tid 140201110636288] 
(111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 
(127.0.0.1) failed
[Sat Apr 23 15:55:15.831811 2022] [proxy_ajp:error] [pid 2125:tid 
140201110636288] [client 192.168.0.14:43196] AH00896: failed to make connection 
to backend: 127.0.0.1
[Sat Apr 23 16:21:57.720678 2022] [proxy:error] [pid 7761:tid 140200894203648] 
(111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 
(127.0.0.1) failed
[Sat Apr 23 16:21:57.720745 2022] [proxy_ajp:error] [pid 7761:tid 
140200894203648] [client 192.168.0.14:43516] AH00896: failed to make connection 
to backend: 127.0.0.1
[Sat Apr 23 16:30:57.738971 2022] [proxy:error] [pid 7761:tid 140200877418240] 
(111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 
(127.0.0.1) failed
[Sat Apr 23 16:30:57.739043 2022] [proxy_ajp:error] [pid 7761:tid 
140200877418240] [client 192.168.0.14:43640] AH00896: failed to make connection 
to backend: 127.0.0.1
[Sat Apr 23 16:32:27.838795 2022] [proxy:error] [pid 7761:tid 140200978130688] 
(111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 
(127.0.0.1) failed
[Sat Apr 23 16:32:27.838881 2022] [proxy_ajp:error] [pid 7761:tid 
140200978130688] [client 192.168.0.14:43658] AH00896: failed to make connection 
to backend: 127.0.0.1
[Sat Apr 23 16:37:49.357585 2022] [core:notice] [pid 1497:tid 139855753558336] 
SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Sat Apr 23 16:37:49.361573 2022] [suexec:notice] [pid 1497:tid 
139855753558336] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Apr 23 16:37:49.388188 2022] [so:warn] [pid 1497:tid 139855753558336] 
AH01574: module proxy_module is already loaded, skipping
[Sat Apr 23 16:37:49.391763 2022] [lbmethod_heartbeat:notice] [pid 1497:tid 
139855753558336] AH02282: No slotmem from mod_heartmonitor
[Sat Apr 23 16:37:49.399281 2022] [mpm_event:notice] [pid 1497:tid 
139855753558336] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1k 
mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6 configured -- resuming normal 
operations
[Sat Apr 23 16:37:49.399320 2022] [core:notice] [pid 1497:tid 139855753558336] 
AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Sat Apr 23 23:20:37.254289 2022] [proxy:error] [pid 6183:tid 139854109198080] 
(111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 
(127.0.0.1) failed
[Sat Apr 23 23:20:37.254354 2022] [proxy_ajp:error] [pid 6183:tid 
139854109198080] [client 192.168.0.13:52982] AH00896: failed to make connection 
to backend: 127.0.0.1

server.log:
2022-04-23 16:38:20,655+03 ERROR [org.jboss.as.controller.management-operation] 
(Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: 
([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed 
services" => 
{"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" 
=> "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
instance
2022-04-23 16:38:20,752+03 ERROR [org.jboss.as] (Controller Boot Thread) 
WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started 
(with errors) in 22155ms - Started 1670 of 1890 services (6 services failed or 
missing dependencies, 393 services are lazy, passive or on-demand)
2022-04-23 23:20:50,622+03 ERROR [org.jboss.msc.service.fail] (ServerService 
Thread Pool -- 47) MSC01: Failed to start service 
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: 
org.jboss.msc.service.StartException in service 
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: 
java.lang.IllegalStateException: WFLYEE0042: Failed to construct component 
instance
2022-04-23 23:20:50,630+03 ERROR [org.jboss.as.controller.management-operation] 
(Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: 
([("deployment" => "engine.ear")]) - failure des

[ovirt-users] Re: oVirt Node 4.5 - Installing gluster single node stops immediately

2022-04-23 Thread Patrick Lomakin 
> Hi guys! I've tried to deploy ovirt single node with gluster via GUI but have 
> a
> problem immediately. A log file that shows after installation was empty. But 
> in journalctl
> I found that:
> 
> Apr 23 20:06:45 host1 cockpit-ws[22948]: ERROR! couldn't resolve module/action
> 'vdo'. This often indicates a misspelling, missing collection, or incorrect 
> module
> path.
> Apr 23 20:06:45 host1 cockpit-ws[22948]: The error appears to be in
> '/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml': 
> line
> 53, column 3, but may
> Apr 23 20:06:45 host1 cockpit-ws[22948]: be elsewhere in the file depending 
> on the exact
> syntax problem.
> Apr 23 20:06:45 host1 cockpit-ws[22948]: The offending line appears to be:
> Apr 23 20:06:45 host1 cockpit-ws[22948]: - name: Create VDO with specified 
> size
> Apr 23 20:06:45 host1 cockpit-ws[22948]:   ^ here

I've resolved problems via installing missing ansible collections. To resolve 
this try to install on ovirt-node:  
"ansible-galaxy collection install community.general" and "ansible-galaxy 
collection install gluster.gluster"
Regards!
___
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/D7XVVP7VEXLQBPCSU3LTROHDO5IZQMVM/

[ovirt-users] oVirt Node 4.5 - Installing gluster single node stops immediately

2022-04-23 Thread Patrick Lomakin 
Hi guys! I've tried to deploy ovirt single node with gluster via GUI but have a 
problem immediately. A log file that shows after installation was empty. But in 
journalctl I found that:

Apr 23 20:06:45 host1 cockpit-ws[22948]: ERROR! couldn't resolve module/action 
'vdo'. This often indicates a misspelling, missing collection, or incorrect 
module path.
Apr 23 20:06:45 host1 cockpit-ws[22948]: The error appears to be in 
'/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml': 
line 53, column 3, but may
Apr 23 20:06:45 host1 cockpit-ws[22948]: be elsewhere in the file depending on 
the exact syntax problem.
Apr 23 20:06:45 host1 cockpit-ws[22948]: The offending line appears to be:
Apr 23 20:06:45 host1 cockpit-ws[22948]: - name: Create VDO with specified size
Apr 23 20:06:45 host1 cockpit-ws[22948]:   ^ here
___
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/27TOMN4KBWECMYV4QQ6XFVX5ALFWZELH/

[ovirt-users] Re: Command line management and ansible error

2022-04-23 Thread Strahil Nikolov via Users 
If you imported the engine's cert correctly into the system executing ansible, 
then a curl https://engine should not give any cert errors and thus ansible 
should not complain.
Best Regards,Strahil Nikolov
 
 
  On Thu, Apr 21, 2022 at 18:09, fs3000--- via Users wrote:   
> Hello, ovirt ansible modules have insecure parameter in auth.
> 
> See definition here 
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_...

I embarassly say, thanks for that tip! No idea how i miss that... It works 
great now.
___
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/QM5SBDENPTZ4OHURVNWLDUPY3YED37D7/
  
___
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/26BUC5GEVG5QTSL4W43CWLOPHLYNIEQL/