On Thu, Aug 11, 2016 at 3:39 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Wed, Aug 10, 2016 at 4:20 PM, Amit Aviram <aaviram@redhat.com> wrote:
It seems like you have an early version of ovirt-4.0, if you'll update your version it might solve some of your problems (such as the exception in the screenshot). soon, the size and format will be deduced from the image as well, so many things will be clearer.
If you want to stay with your version, you'll need to do the following steps in order to upload the file: - At the engine's host, yum install ovirt-imageio-proxy - Then, run engine-setup. - Add the engine's CA to the Authorities list in your browser. (you can download it from https://%your_engine%/ovirt-engine/services/pki-resourc e?resource=ca-certificate&format=X509-PEM-CA <https://engineaaviram.usersys.redhat.com:8443/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA> )
regarding the size- you can choose a bigger size than the original file's size.
Hope that works out for you!
Hello, I updated both engine and host to 4.0.2 RC4 and during the engine-setup phase I indeed see this:
...
PACKAGE: [install] ovirt-imageio-common-0.3.0-1.el7.noarch PACKAGE: [install] ovirt-imageio-proxy-0.3.0-0. 201606191345.git9f3d6d4.el7.centos.noarch PACKAGE: [install] ovirt-imageio-proxy-setup-0.3. 0-0.201606191345.git9f3d6d4.el7.centos.noarch
and the configuration preview appeared as
--== CONFIGURATION PREVIEW ==--
Default SAN wipe after delete : False Firewall manager : firewalld Update Firewall : True Host FQDN : ractorshe.mydomain Upgrade packages : True Engine database secured connection : False Engine database host : localhost Engine database user name : engine Engine database name : engine Engine database port : 5432 Engine database host name validation : False DWH database secured connection : False DWH database host : localhost DWH database user name : ovirt_engine_history DWH database name : ovirt_engine_history DWH database port : 5432 DWH database host name validation : False Engine installation : True PKI organization : mydomain DWH installation : True Backup DWH database : True Engine Host FQDN : ractorshe.mydomain Configure VMConsole Proxy : True Configure WebSocket Proxy : True
Should I have seen anything related to image proxy in engine-setup configuration preview above?
The version installed is: ovirt-imageio-proxy-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch
I don't get anymore the exception in the GUI but again the upload goes into paused mode as soon as it starts
I see that part of the new package there is also a service
[root@ractorshe log]# systemctl status ovirt-imageio-proxy.service ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; disabled; vendor preset: disabled) Active: inactive (dead) [root@ractorshe log]#
Do I have to enable and start it? What TCP ports does the upload use? Does the client communicate with the engine or directly with the host?
Thanks, Gianluca
Probably I have to run engine-setup two times: the first installs the package and the second configures it. But, at the second run, I do get a new answer --== PRODUCT OPTIONS ==-- Configure Image I/O Proxy on this host? (Yes, No) [Yes]: then --== CONFIGURATION PREVIEW ==-- Default SAN wipe after delete : False Firewall manager : firewalld Update Firewall : True Host FQDN : ractorshe.mydomain Engine database secured connection : False Engine database host : localhost Engine database user name : engine Engine database name : engine Engine database port : 5432 Engine database host name validation : False DWH database secured connection : False DWH database host : localhost DWH database user name : ovirt_engine_history DWH database name : ovirt_engine_history DWH database port : 5432 DWH database host name validation : False Engine installation : True PKI organization : mydomain DWH installation : True Backup DWH database : True Engine Host FQDN : ractorshe.mydomain Configure Image I/O Proxy : True Configure VMConsole Proxy : True Configure WebSocket Proxy : True Please confirm installation settings (OK, Cancel) [OK]: [ INFO ] Cleaning async tasks and compensations [ INFO ] Unlocking existing entities [ INFO ] Checking the Engine database consistency [ INFO ] Stage: Transaction setup [ INFO ] Stopping engine service [ INFO ] Stopping ovirt-fence-kdump-listener service [ INFO ] Stopping dwh service [ INFO ] Stopping Image I/O Proxy service [ INFO ] Stopping websocket-proxy service [ INFO ] Stage: Misc configuration [ INFO ] Stage: Package installation [ INFO ] Stage: Misc configuration [ INFO ] Upgrading CA [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20160811161431.XgUmV1.dump'. [ INFO ] Creating/refreshing Engine database schema [ INFO ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20160811161505.h8lDcR.dump'. [ INFO ] Creating/refreshing DWH database schema [ INFO ] Configuring Image I/O Proxy [ INFO ] Configuring WebSocket Proxy [ INFO ] Creating/refreshing Engine 'internal' domain database schema [ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' [ INFO ] Stage: Transaction commit [ INFO ] Stage: Closing up [ INFO ] Starting engine service [ INFO ] Starting dwh service [ ERROR ] Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio-proxy' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160811161247-y37b3y.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160811161529-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed And in log file 2016-08-11 16:15:29 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting service ovirt-imageio- proxy 2016-08-11 16:15:29 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute: ('/bin/systemctl', 'start', 'ovirt-imageio-proxy.service'), executable='None', cwd='None', env=None 2016-08-11 16:15:29 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863 execute-result: ('/bin/syst emctl', 'start', 'ovirt-imageio-proxy.service'), rc=1 2016-08-11 16:15:29 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921 execute-output: ('/bin/systemc tl', 'start', 'ovirt-imageio-proxy.service') stdout: 2016-08-11 16:15:29 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/bin/systemc tl', 'start', 'ovirt-imageio-proxy.service') stderr: Job for ovirt-imageio-proxy.service failed because the control process exited with error code. See "systemctl st atus ovirt-imageio-proxy.service" and "journalctl -xe" for details. 2016-08-11 16:15:29 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio_proxy/config.py", line 351, in _closeup state=state, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'ovirt-imageio-proxy' 2016-08-11 16:15:29 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio-proxy' 2016-08-11 16:15:29 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN 2016-08-11 16:15:29 DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/error=bool:'True' 2016-08-11 16:15:29 DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Failed to start service 'ovirt-imageio-proxy'",), <traceback object at 0x3676290>)]' 2016-08-11 16:15:29 DEBUG otopi.context context.dumpEnvironment:774 ENVIRONMENT DUMP - END 2016-08-11 16:15:29 INFO otopi.context context.runSequence:687 Stage: Clean up 2016-08-11 16:15:29 DEBUG otopi.context context.runSequence:691 STAGE cleanup 2016-08-11 16:15:29 DEBUG otopi.context context._executeMethod:128 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.misc.Plugin._cleanup 2016-08-11 16:15:29 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160811161247-y37b3y.log Any hint? Do I have to run engine-setup again and disable image io proxy? The engine seems to be working.....