10:06 a.m.
Hello,
using this on CentOS 6.5 to configure AIO with ita branch for translation,
updated at 1608
[root@ovirtita ~]# rpm -qa|egrep "engine|vdsm|ovirt"
vdsm-xmlrpc-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-websocket-proxy-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-yajsonrpc-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-jboss-as-7.1.1-1.el6.x86_64
ovirt-engine-restapi-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-jsonrpc-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-release-master-001-0.0.master.noarch
ovirt-engine-lib-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-extensions-api-impl-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-1.3.0-0.0.master.20140811115624.git89155f8.el6.noarch
ovirt-image-uploader-3.6.0-0.0.master.20140808125503.git066ed25.el6.noarch
ovirt-engine-setup-base-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-jsonrpc-java-1.0.1-0.0.master.20140812113145.git7d15fda.el6.noarch
ovirt-host-deploy-java-1.3.0-0.0.master.20140811115624.git89155f8.el6.noarch
ovirt-engine-userportal-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-backend-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-offline-1.3.0-0.0.master.20140811115624.git89155f8.el6.x86_64
ovirt-iso-uploader-3.6.0-0.0.master.20140812133505.gita6b721e.el6.noarch
vdsm-python-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-cli-3.6.0.0-1.20140718.gite0c7d55.el6.noarch
ovirt-engine-dbscripts-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-tools-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-allinone-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-sdk-python-3.6.0.0-1.20140811.git56f9da6.el6.noarch
vdsm-python-zombiereaper-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-extensions-api-impl-javadoc-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-cli-4.16.0-206.gitdd70c9e.el6.noarch
ovirt-engine-setup-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-4.16.0-206.gitdd70c9e.el6.x86_64
SELinux is set to permissive, iptables and ip6tables are stopped and set to
off.
In setup I say not to configure firewall.
It aborts at nfs share stage with
[ INFO ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': [Errno 111] Connection
refused
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140820084948-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
NOTE: I set to "enabled=0" the rows
in /etc/yum.repos.d/ovirt-master-snapshot.repo so that I'm not forced to
update engine-setup itself or other packages.
Whole output:
[root@ovirtita ~]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
Version: otopi-1.3.0_master
(otopi-1.3.0-0.0.master.20140728.git336a22e.el6)
[ INFO ] Hardware supports virtualization
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
Configure Engine on this host (Yes, No) [Yes]:
Configure WebSocket Proxy on this host (Yes, No) [Yes]:
--== PACKAGES ==--
[ INFO ] Checking for product updates...
[ INFO ] No product updates found
--== ALL IN ONE CONFIGURATION ==--
Configure VDSM on this host? (Yes, No) [No]: Yes
Local storage domain path [/var/lib/images]:
Local storage domain name [local_storage]:
--== NETWORK CONFIGURATION ==--
Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite
current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]: No
Host fully qualified DNS name of this server
[ovirtita.localdomain.local]:
[WARNING] Failed to resolve ovirtita.localdomain.local using DNS, it can be
resolved only locally
--== DATABASE CONFIGURATION ==--
Where is the Engine database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for
the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and
create Engine database, or prefer to perform that manually? (Automatic,
Manual) [Automatic]:
--== OVIRT ENGINE CONFIGURATION ==--
Engine admin password:
Confirm engine admin password:
[WARNING] Password is weak: it is based on a dictionary word
Use weak password? (Yes, No) [No]: Yes
Application mode (Both, Virt, Gluster) [Both]:
Default storage type: (NFS, FC, ISCSI, POSIXFS, GLUSTERFS) [NFS]:
--== PKI CONFIGURATION ==--
Organization name for certificate [localdomain.local]:
--== APACHE CONFIGURATION ==--
Setup can configure the default page of the web server to present
the application home page. This may conflict with existing applications.
Do you wish to set the application as the default page of the web
server? (Yes, No) [Yes]:
Setup can configure apache to use SSL using a certificate issued
from the internal CA.
Do you wish Setup to configure that, or prefer to perform that
manually? (Automatic, Manual) [Automatic]:
--== SYSTEM CONFIGURATION ==--
Configure an NFS share on this server to be used as an ISO
Domain? (Yes, No) [Yes]:
Local ISO domain path [/var/lib/exports/iso]:
Local ISO domain ACL - note that the default will restrict access
to ovirtita.localdomain.local only, for security reasons
[ovirtita.localdomain.local(rw)]:
Local ISO domain name [ISO_DOMAIN]:
--== MISC CONFIGURATION ==--
--== END OF CONFIGURATION ==--
[ INFO ] Stage: Setup validation
[WARNING] Less than 16384MB of memory is available
--== CONFIGURATION PREVIEW ==--
Application mode : both
Update Firewall : False
Host FQDN :
ovirtita.localdomain.local
Datacenter storage type : nfs
Engine database name : engine
Engine database secured connection : False
Engine database host : localhost
Engine database user name : engine
Engine database host name validation : False
Engine database port : 5432
Engine installation : True
NFS setup : True
PKI organization : localdomain.local
NFS mount point : /var/lib/exports/iso
NFS export ACL :
ovirtita.localdomain.local(rw)
Configure VDSM on this host : True
Local storage domain directory : /var/lib/images
Configure local Engine database : True
Set application as default page : True
Configure Apache SSL : True
Configure WebSocket Proxy : True
Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping ovirt-fence-kdump-listener service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL 'engine' database
[ INFO ] Configuring PostgreSQL
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating CA
[ INFO ] Configuring WebSocket Proxy
[ 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
--== SUMMARY ==--
[WARNING] Less than 16384MB of memory is available
SSH fingerprint: F9:B1:16:C1:85:72:1B:C5:3C:35:9E:45:A0:A2:4C:C3
Internal CA
78:3E:BB:BD:9D:A3:AE:20:9E:7A:44:BB:01:1F:87:13:E4:7B:FE:7D
Web access is enabled at:
http://ovirtita.localdomain.local:80/ovirt-engine
https://ovirtita.localdomain.local:443/ovirt-engine
Please use the user "admin" and password specified in order to
login
In order to configure firewalld, copy the files from
/etc/ovirt-engine/firewalld to /etc/firewalld/services
and execute the following commands:
firewall-cmd -service ovirt-postgres
firewall-cmd -service ovirt-https
firewall-cmd -service ovirt-aio
firewall-cmd -service ovirt-fence-kdump-listener
firewall-cmd -service ovirt-websocket-proxy
firewall-cmd -service ovirt-nfs
firewall-cmd -service ovirt-http
The following network ports should be opened:
tcp:111
tcp:2049
tcp:32803
tcp:443
tcp:49152-49216
tcp:5432
tcp:5900-6923
tcp:6100
tcp:662
tcp:80
tcp:875
tcp:892
udp:111
udp:32769
udp:662
udp:7410
udp:875
udp:892
An example of the required configuration for iptables can be
found at:
/etc/ovirt-engine/iptables.example
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': [Errno 111] Connection
refused
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140820084948-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
[root@ovirtita ~]#
Do I miss any basic package? I installed this CentOS 6.5 server specifying
"basic server" in anaconda.
In mesages I have these lines during setup:
Aug 20 08:49:13 ovirtita dbus: avc: received policyload notice (seqno=2)
Aug 20 08:49:13 ovirtita dbus: [system] Reloaded configuration
Aug 20 08:49:14 ovirtita dbus: avc: received policyload notice (seqno=3)
Aug 20 08:49:14 ovirtita dbus: [system] Reloaded configuration
Aug 20 08:49:20 ovirtita dbus: avc: received policyload notice (seqno=4)
Aug 20 08:49:20 ovirtita dbus: [system] Reloaded configuration
Aug 20 08:49:26 ovirtita dbus: avc: received policyload notice (seqno=5)
Aug 20 08:49:26 ovirtita dbus: [system] Reloaded configuration
Aug 20 08:49:30 ovirtita kernel: RPC: Registered named UNIX socket
transport module.
Aug 20 08:49:30 ovirtita kernel: RPC: Registered udp transport module.
Aug 20 08:49:30 ovirtita kernel: RPC: Registered tcp transport module.
Aug 20 08:49:30 ovirtita kernel: RPC: Registered tcp NFSv4.1 backchannel
transport module.
Aug 20 08:49:31 ovirtita kernel: Installing knfsd (copyright (C) 1996
okir(a)monad.swb.de).
Aug 20 08:49:31 ovirtita rpc.mountd[12397]: Version 1.2.3 starting
Aug 20 08:49:31 ovirtita kernel: NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
Aug 20 08:49:31 ovirtita kernel: NFSD: starting 90-second grace period
Now
[root@ovirtita ~]# exportfs -v
/var/lib/exports/iso
ovirtita.localdomain.local(rw,wdelay,root_squash,no_subtree_check)
And if I run a mount on the share on the server itself it succeeds...
[root@ovirtita ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_ovirtita-lv_root
29G 3.6G 24G 14% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
/dev/sda1 485M 67M 393M 15% /boot
[root@ovirtita ~]# mkdir /tmp/p
[root@ovirtita ~]# mount ovirtita.localdomain.local:/var/lib/exports/iso
/tmp/p
[root@ovirtita ~]# df -h /tmp/p
Filesystem Size Used Avail Use% Mounted on
ovirtita.localdomain.local:/var/lib/exports/iso
29G 3.6G 24G 14% /tmp/p
Does it cause any problem the name resolution that is only local with
/etc/hosts and not with dns?
What should I put in this case for AIO when input requests:
Local ISO domain ACL - note that the default will restrict
access to ovirtita.localdomain.local only, for security reasons
[ovirtita.localdomain.local(rw)]:
??
In setup log I have:
2014-08-20 08:49:48 DEBUG otopi.ovirt_engine_setup.engine_common.database
database.execute:214 Result: [{'version': 'general',
'option_value':
'3.0,3.1,3.2,3.3,3.4,3.5'}]
2014-08-20 08:49:48 DEBUG
otopi.plugins.ovirt_engine_setup.ovirt_engine.all-in-one.vdsmi
vdsmi._closeup:208 engine SupportedClusterLevels [3.0,3.1,3.2,3.3,3.4,3.5],
PACKAGE_VERSION [3.6.0_master],
2014-08-20 08:49:48 DEBUG otopi.context context._executeMethod:152 method
exception
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in
_executeMethod
method['method']()
File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/all-in-one/vdsmi.py",
line 212, in _closeup
result = vdscli.connect().getVdsCapabilities()
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
connection.endheaders()
File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
self._send_output()
File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
self.send(msg)
File "/usr/lib64/python2.6/httplib.py", line 739, in send
self.connect()
File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line 181, in
connect
sock = socket.create_connection((self.host, self.port), self.timeout)
File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
raise error, msg
error: [Errno 111] Connection refused
2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161 Failed
to execute stage 'Closing up': [Errno 111] Connection refused
What kind of mount test does engine-setup perform?
Full engine log here:
https://drive.google.com/file/d/0BwoPbcrMv8mvWkxEZllSNnFzRTg/edit?usp=sha...
Thanks,
Gianluca
10:17 a.m.
On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
result = vdscli.connect().getVdsCapabilities()
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
connection.endheaders()
File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
self._send_output()
File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
self.send(msg)
File "/usr/lib64/python2.6/httplib.py", line 739, in send
self.connect()
File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line 181, in
connect
sock = socket.create_connection((self.host, self.port), self.timeout)
File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
raise error, msg
error: [Errno 111] Connection refused
2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161 Failed
to execute stage 'Closing up': [Errno 111] Connection refused
Sorry, rereading better, it seems not an nfs problem but with getting host
capabilities...
Probably it should be better to put an echo in setup to confirm nfs part
has finished and that we are in another part of setup...
The server is a kvm guest on Fedora 20 system
Indeed when running manually I get
[root@ovirtita host-deploy]# vdsClient -s 0 getVdsCaps
Connection to 0.0.0.0:54321 refused
what to check?
[root@ovirtita host-deploy]# lsmod|grep kvm
kvm_intel 54317 0
kvm 333734 1 kvm_intel
Thanks,
Gianluca
7:43 p.m.
Il 20/08/2014 09:17, Gianluca Cecchi ha scritto:
On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com
<mailto:gianluca.cecchi@gmail.com>> wrote:
result = vdscli.connect().getVdsCapabilities()
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
connection.endheaders()
File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
self._send_output()
File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
self.send(msg)
File "/usr/lib64/python2.6/httplib.py", line 739, in send
self.connect()
File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line 181, in
connect
sock = socket.create_connection((self.host, self.port), self.timeout)
File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
raise error, msg
error: [Errno 111] Connection refused
2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161 Failed to execute
stage 'Closing up': [Errno 111] Connection refused
Sorry, rereading better, it seems not an nfs problem but with getting host
capabilities...
Probably it should be better to put an echo in setup to confirm nfs part has finished and
that we are in another part of setup...
The server is a kvm guest on Fedora 20 system
Indeed when running manually I get
[root@ovirtita host-deploy]# vdsClient -s 0 getVdsCaps
Connection to 0.0.0.0:54321 <http://0.0.0.0:54321> refused
what to check?
Maybe the vdsmd daemon is not running.
check if it's up with "service vdsmd status". Looks like the vdsmd daemon is
not responding
[root@ovirtita host-deploy]# lsmod|grep kvm
kvm_intel 54317 0
kvm 333734 1 kvm_intel
Thanks,
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10:59 a.m.
On Thu, Aug 21, 2014 at 6:43 PM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Il 20/08/2014 09:17, Gianluca Cecchi ha scritto:
>
> On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi <
gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote:
>
>
> result = vdscli.connect().getVdsCapabilities()
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
> return self.__send(self.__name, args)
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
> verbose=self.__verbose
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
> self.send_content(h, request_body)
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in
send_content
> connection.endheaders()
> File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
> self._send_output()
> File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
> self.send(msg)
> File "/usr/lib64/python2.6/httplib.py", line 739, in send
> self.connect()
> File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line
181, in connect
> sock = socket.create_connection((self.host, self.port),
self.timeout)
> File "/usr/lib64/python2.6/socket.py", line 567, in
create_connection
> raise error, msg
> error: [Errno 111] Connection refused
> 2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161
Failed to execute stage 'Closing up': [Errno 111] Connection refused
>
>
>
> Sorry, rereading better, it seems not an nfs problem but with getting
host capabilities...
> Probably it should be better to put an echo in setup to confirm nfs part
has finished and that we are in another part of setup...
>
> The server is a kvm guest on Fedora 20 system
> Indeed when running manually I get
> [root@ovirtita host-deploy]# vdsClient -s 0 getVdsCaps
> Connection to 0.0.0.0:54321 <http://0.0.0.0:54321> refused
>
> what to check?
Maybe the vdsmd daemon is not running.
check if it's up with "service vdsmd status". Looks like the vdsmd daemon
is not responding
This is in the middle of install itself....
What is the workflow for engine-setup
in AIO install?
At the beginning of engine-setup process I have:
[ INFO ] Hardware supports virtualization
Then in configuration preview I have:
Configure VDSM on this host : True
Then I see
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping ovirt-fence-kdump-listener service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL 'engine' database
[ INFO ] Configuring PostgreSQL
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating CA
[ INFO ] Configuring WebSocket Proxy
[ 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
and
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': [Errno 111] Connection
refused
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140820084948-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
So where is the vdsmd part configuration information?
DO I have to check vdsm logs or host-deploy logs for this kind of problem?
Gianluca
11:24 a.m.
Il 22/08/2014 09:59, Gianluca Cecchi ha scritto:
On Thu, Aug 21, 2014 at 6:43 PM, Sandro Bonazzola
<sbonazzo(a)redhat.com <mailto:sbonazzo@redhat.com>> wrote:
Il 20/08/2014 09:17, Gianluca Cecchi ha scritto:
>
> On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com
<mailto:gianluca.cecchi@gmail.com> <mailto:gianluca.cecchi@gmail.com
<mailto:gianluca.cecchi@gmail.com>>> wrote:
>
>
> result = vdscli.connect().getVdsCapabilities()
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in
__call__
> return self.__send(self.__name, args)
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in
__request
> verbose=self.__verbose
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
> self.send_content(h, request_body)
> File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in
send_content
> connection.endheaders()
> File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
> self._send_output()
> File "/usr/lib64/python2.6/httplib.py", line 780, in
_send_output
> self.send(msg)
> File "/usr/lib64/python2.6/httplib.py", line 739, in send
> self.connect()
> File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line
181, in connect
> sock = socket.create_connection((self.host, self.port), self.timeout)
> File "/usr/lib64/python2.6/socket.py", line 567, in
create_connection
> raise error, msg
> error: [Errno 111] Connection refused
> 2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161 Failed to
execute stage 'Closing up': [Errno 111] Connection refused
>
>
>
> Sorry, rereading better, it seems not an nfs problem but with getting host
capabilities...
> Probably it should be better to put an echo in setup to confirm nfs part has
finished and that we are in another part of setup...
>
> The server is a kvm guest on Fedora 20 system
> Indeed when running manually I get
> [root@ovirtita host-deploy]# vdsClient -s 0 getVdsCaps
> Connection to 0.0.0.0:54321 <http://0.0.0.0:54321>
<http://0.0.0.0:54321> refused
>
> what to check?
Maybe the vdsmd daemon is not running.
check if it's up with "service vdsmd status". Looks like the vdsmd
daemon is not responding
This is in the middle of install itself....
What is the workflow for engine-setup in AIO install?
It first configure and run ovirt-engine, then use the SDK for creating the local
datacenter and add the host to it.
At the beginning of engine-setup process I have:
[ INFO ] Hardware supports virtualization
Then in configuration preview I have:
Configure VDSM on this host : True
Then I see
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping ovirt-fence-kdump-listener service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL 'engine' database
[ INFO ] Configuring PostgreSQL
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating CA
[ INFO ] Configuring WebSocket Proxy
[ 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
and
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': [Errno 111] Connection refused
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140820084948-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
So where is the vdsmd part configuration information?
DO I have to check vdsm logs or host-deploy logs for this kind of problem?
Both of them I guess.
Gianluca
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
1:29 p.m.
On Fri, Aug 22, 2014 at 10:24 AM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
>
> So where is the vdsmd part configuration information?
> DO I have to check vdsm logs or host-deploy logs for this kind of
problem?
Both of them I guess.
>
> Gianluca
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
ok, I think I have understood the problem.
I remember I successfully completed an AIO install on the same environment
around 10 or11 of August so there had to be something different in my way
of proceeding.
In order to rerun many times engine-setup and with different options I
setup an environment where on a clean CentOS 6.5 I installed the necessary
oVirt packages.
Then I shutdown the server and save its disk to use it as a starting point
for recurring installations.
It seems that the workflow
- install ovirt packages
- shutdown and reboot server
- run engine-setup
creates this kind of problem.
Possibly because as part of the install I have services marked to be
started at boot, even if no configuration has been made for them yet....
So as soon as the packages are installed the services have not been started
yet, but they will do on next reboot both if you will run engine-setup
before shutdown or not....
As soon as installation completes I have these new services configured at
boot
cgconfig 0:off 1:off 2:on 3:on 4:on 5:on 6:off
iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off
iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ksm 0:off 1:off 2:off 3:on 4:on 5:on 6:off
ksmtuned 0:off 1:off 2:off 3:on 4:on 5:on 6:off
libvirt-guests 0:off 1:off 2:on 3:on 4:on 5:on 6:off
libvirtd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
sanlock 0:off 1:off 2:on 3:on 4:on 5:on 6:off
supervdsmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
vdsmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
wdmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
so after restart of the server, this creates problems.....
Instead if I run engine-setup right after install I don't get this error.
But now I get
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': No permission to read file:
/etc/pki/vdsm/keys/vdsmkey.pem
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140822110116-nwyf6c.log
and in fact, also executing from command line
[root@ovirtita setup]# vdsClient -s 0 getVdsCapabilities
Traceback (most recent call last):
File "/usr/share/vdsm/vdsClient.py", line 2744, in <module>
serv.do_connect(hostPort)
File "/usr/share/vdsm/vdsClient.py", line 187, in do_connect
self.s = vdscli.connect(hostPort, self.useSSL, self.truststore)
File "/usr/lib64/python2.6/site-packages/vdsm/vdscli.py", line 108, in
connect
raise Exception("No permission to read file: %s" % f)
Exception: No permission to read file: /etc/pki/vdsm/keys/vdsmkey.pem
The file actually is not there, there is no problem of permissions....
[root@ovirtita setup]# ll /etc/pki/vdsm/keys/
total 4
-rw-------. 1 vdsm kvm 10 Aug 21 22:34 libvirt_password
Which part should have created the file?
After failure:
# service vdsmd status
VDS daemon is not running
no logs from vdsm (probably never started yet because of the above problem):
[root@ovirtita exported-artifacts]# ll /var/log/vdsm/
total 4
drwxr-xr-x. 2 vdsm kvm 4096 Aug 21 22:34 backup
-rw-r--r--. 1 vdsm kvm 0 Aug 22 12:18 connectivity.log
-rw-r--r--. 1 vdsm kvm 0 Aug 22 12:18 mom.log
-rw-r--r--. 1 root root 0 Aug 22 12:18 supervdsm.log
-rw-r--r--. 1 vdsm kvm 0 Aug 22 12:18 vdsm.log
[root@ovirtita exported-artifacts]# ll /var/log/vdsm/backup/
total 0
Also,
[root@ovirtita exported-artifacts]# ll /var/log/ovirt-engine/host-deploy/
total 0
engine-setup log here
https://drive.google.com/file/d/0BwoPbcrMv8mvaWNqakhnS19jZTQ/edit?usp=sha...
my current setup of packages is:
[root@ovirtita setup]# rpm -qa|egrep "engine|vdsm|ovirt"
vdsm-python-zombiereaper-4.16.0-231.git7f489da.el6.noarch
vdsm-xmlrpc-4.16.0-231.git7f489da.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-java-1.3.0-0.0.master.20140821183616.git82dce3c.el6.noarch
ovirt-engine-setup-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-release-master-001-0.0.master.noarch
ovirt-engine-sdk-python-3.6.0.0-1.20140820.gitc625968.el6.noarch
ovirt-engine-userportal-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-backend-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-1.3.0-0.0.master.20140821183616.git82dce3c.el6.noarch
ovirt-image-uploader-3.6.0-0.0.master.20140808125503.git066ed25.el6.noarch
ovirt-engine-lib-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-extensions-api-impl-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-dbscripts-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-tools-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-host-deploy-offline-1.3.0-0.0.master.20140821183616.git82dce3c.el6.x86_64
ovirt-iso-uploader-3.6.0-0.0.master.20140812133505.gita6b721e.el6.noarch
vdsm-python-4.16.0-231.git7f489da.el6.noarch
ovirt-engine-setup-base-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-yajsonrpc-4.16.0-231.git7f489da.el6.noarch
vdsm-jsonrpc-java-1.0.3-0.0.master.20140821162323.git93bec39.el6.noarch
ovirt-engine-jboss-as-7.1.1-1.el6.x86_64
ovirt-engine-restapi-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-jsonrpc-4.16.0-231.git7f489da.el6.noarch
ovirt-engine-setup-plugin-allinone-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-extensions-api-impl-javadoc-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-cli-4.16.0-231.git7f489da.el6.noarch
ovirt-engine-websocket-proxy-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
ovirt-engine-cli-3.6.0.0-1.20140820.gite160c94.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.6.0-0.0.master.20140816103500.gitb920a2d.el6.noarch
vdsm-4.16.0-231.git7f489da.el6.x86_64
Gianluca
4:29 p.m.
My previous tests were made with local rpm packages released by jenkins
jobs for ita translation from master (tried with both 16/08 and 18/08 no
other successfull jobs for CentOS 6.x after).
Now, to verify if this could influence the problem I actually confirmed to
get the same error and behavior with pure master tree.
See engine log here:
https://drive.google.com/file/d/0BwoPbcrMv8mvanZwYWR5X2tWRGs/edit?usp=sha...
Instead with current 3.5 repo just tried on the same re-cleaned environment
I have:
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ INFO ] Waiting for VDSM host to become operational. This may take
several minutes...
[ INFO ] The VDSM Host is now operational
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140822150237-13m6av.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140822150621-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
and
[root@ovirtita setup]# ll /etc/pki/vdsm/keys/
total 8
-rw-------. 1 vdsm kvm 10 Aug 21 10:34 libvirt_password
-r--r-----. 1 vdsm kvm 1679 Aug 22 15:05 vdsmkey.pem
[root@ovirtita ~]# service vdsmd status
VDS daemon server is running
see engine log for 3.5 here:
https://drive.google.com/file/d/0BwoPbcrMv8mvQWg3ZkRTQl9GQ3c/edit?usp=sha...
For both environments I have used:
yum localinstall http://resources.ovirt.org/pub/yum-repo/repo-name.rpm
(where "repo-name" is ovirt-release35 for 3.5 or ovirt-release-master.rpm
for master)
yum install ovirt-engine-setup-plugin-allinone
engine-setup
with all default to answers (except for Yes for vdsm and weak password for
admin user).
So I think there is some sort of regression between the current 3.5 and 3.6
master for AIO setup...
I'm sure that on 13/08 I successfully used jenkins package for ita
(generated on 11th) with master tree as of 13/08 without this failure
problems (apart that vdsmd wasn't able to start during engine-setup; I had
only 6Gb of ram on the VM and the host went into "Unissigned" state)
so I don't now what happened in the middle...
Gianluca
------ engine-setup output for master: --------
[root@ovirtita ~]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140822133624-0qjxbv.log
Version: otopi-1.3.0_master
(otopi-1.3.0-0.0.master.20140728.git336a22e.el6)
[ INFO ] Hardware supports virtualization
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
Configure Engine on this host (Yes, No) [Yes]:
Configure WebSocket Proxy on this host (Yes, No) [Yes]:
--== PACKAGES ==--
[ INFO ] Checking for product updates...
[ INFO ] No product updates found
--== ALL IN ONE CONFIGURATION ==--
Configure VDSM on this host? (Yes, No) [No]: Yes
Local storage domain path [/var/lib/images]:
Local storage domain name [local_storage]:
--== NETWORK CONFIGURATION ==--
Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite
current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]:
[ INFO ] iptables will be configured as firewall manager.
Host fully qualified DNS name of this server
[ovirtita.localdomain.local]:
[WARNING] Failed to resolve ovirtita.localdomain.local using DNS, it can be
resolved only locally
--== DATABASE CONFIGURATION ==--
Where is the Engine database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for
the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and
create Engine database, or prefer to perform that manually? (Automatic,
Manual) [Automatic]:
--== OVIRT ENGINE CONFIGURATION ==--
Engine admin password:
Confirm engine admin password:
[WARNING] Password is weak: it is based on a dictionary word
Use weak password? (Yes, No) [No]: Yes
Application mode (Both, Virt, Gluster) [Both]:
Default storage type: (NFS, FC, ISCSI, POSIXFS, GLUSTERFS) [NFS]:
--== PKI CONFIGURATION ==--
Organization name for certificate [localdomain.local]:
--== APACHE CONFIGURATION ==--
Setup can configure the default page of the web server to present
the application home page. This may conflict with existing applications.
Do you wish to set the application as the default page of the web
server? (Yes, No) [Yes]:
Setup can configure apache to use SSL using a certificate issued
from the internal CA.
Do you wish Setup to configure that, or prefer to perform that
manually? (Automatic, Manual) [Automatic]:
--== SYSTEM CONFIGURATION ==--
Configure an NFS share on this server to be used as an ISO
Domain? (Yes, No) [Yes]:
Local ISO domain path [/var/lib/exports/iso]:
Local ISO domain ACL - note that the default will restrict access
to ovirtita.localdomain.local only, for security reasons
[ovirtita.localdomain.local(rw)]:
Local ISO domain name [ISO_DOMAIN]:
--== MISC CONFIGURATION ==--
--== END OF CONFIGURATION ==--
[ INFO ] Stage: Setup validation
[WARNING] Less than 16384MB of memory is available
--== CONFIGURATION PREVIEW ==--
Application mode : both
Update Firewall : True
Host FQDN :
ovirtita.localdomain.local
Datacenter storage type : nfs
Firewall manager : iptables
Engine database name : engine
Engine database secured connection : False
Engine database host : localhost
Engine database user name : engine
Engine database host name validation : False
Engine database port : 5432
Engine installation : True
NFS setup : True
PKI organization : localdomain.local
NFS mount point : /var/lib/exports/iso
NFS export ACL :
ovirtita.localdomain.local(rw)
Configure VDSM on this host : True
Local storage domain directory : /var/lib/images
Configure local Engine database : True
Set application as default page : True
Configure Apache SSL : True
Configure WebSocket Proxy : True
Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping ovirt-fence-kdump-listener service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL 'engine' database
[ INFO ] Configuring PostgreSQL
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating CA
[ INFO ] Configuring WebSocket Proxy
[ 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
--== SUMMARY ==--
[WARNING] Less than 16384MB of memory is available
SSH fingerprint: 99:79:48:8B:A8:83:7B:83:CC:5B:D3:6A:C9:B0:49:28
Internal CA
6E:D4:C3:B8:E9:7E:BC:95:B2:EB:91:CE:7F:E7:54:E0:43:23:EE:18
Web access is enabled at:
http://ovirtita.localdomain.local:80/ovirt-engine
https://ovirtita.localdomain.local:443/ovirt-engine
Please use the user "admin" and password specified in order to
login
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ ERROR ] Failed to execute stage 'Closing up': No permission to read file:
/etc/pki/vdsm/keys/vdsmkey.pem
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140822133624-0qjxbv.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140822133918-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
------ engine-setup output for 3.5: -----
[root@ovirtita ~]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140822150237-13m6av.log
Version: otopi-1.3.0_master
(otopi-1.3.0-0.0.master.20140728.git336a22e.el6)
[ INFO ] Hardware supports virtualization
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
Configure Engine on this host (Yes, No) [Yes]:
Configure WebSocket Proxy on this host (Yes, No) [Yes]:
--== PACKAGES ==--
[ INFO ] Checking for product updates...
[ INFO ] No product updates found
--== ALL IN ONE CONFIGURATION ==--
Configure VDSM on this host? (Yes, No) [No]: Yes
Local storage domain path [/var/lib/images]:
Local storage domain name [local_storage]:
--== NETWORK CONFIGURATION ==--
Setup can automatically configure the firewall on this system.
Note: automatic configuration of the firewall may overwrite
current settings.
Do you want Setup to configure the firewall? (Yes, No) [Yes]:
[ INFO ] iptables will be configured as firewall manager.
Host fully qualified DNS name of this server
[ovirtita.localdomain.local]:
[WARNING] Failed to resolve ovirtita.localdomain.local using DNS, it can be
resolved only locally
--== DATABASE CONFIGURATION ==--
Where is the Engine database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for
the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and
create Engine database, or prefer to perform that manually? (Automatic,
Manual) [Automatic]:
--== OVIRT ENGINE CONFIGURATION ==--
Engine admin password:
Confirm engine admin password:
[WARNING] Password is weak: it is based on a dictionary word
Use weak password? (Yes, No) [No]: Yes
Application mode (Both, Virt, Gluster) [Both]:
Default storage type: (NFS, FC, ISCSI, POSIXFS, GLUSTERFS) [NFS]:
--== PKI CONFIGURATION ==--
Organization name for certificate [localdomain.local]:
--== APACHE CONFIGURATION ==--
Setup can configure the default page of the web server to present
the application home page. This may conflict with existing applications.
Do you wish to set the application as the default page of the web
server? (Yes, No) [Yes]:
Setup can configure apache to use SSL using a certificate issued
from the internal CA.
Do you wish Setup to configure that, or prefer to perform that
manually? (Automatic, Manual) [Automatic]:
--== SYSTEM CONFIGURATION ==--
Configure an NFS share on this server to be used as an ISO
Domain? (Yes, No) [Yes]:
Local ISO domain path [/var/lib/exports/iso]:
Local ISO domain ACL - note that the default will restrict access
to ovirtita.localdomain.local only, for security reasons
[ovirtita.localdomain.local(rw)]:
Local ISO domain name [ISO_DOMAIN]:
--== MISC CONFIGURATION ==--
--== END OF CONFIGURATION ==--
[ INFO ] Stage: Setup validation
[WARNING] Less than 16384MB of memory is available
--== CONFIGURATION PREVIEW ==--
Application mode : both
Update Firewall : True
Host FQDN :
ovirtita.localdomain.local
Datacenter storage type : nfs
Firewall manager : iptables
Engine database name : engine
Engine database secured connection : False
Engine database host : localhost
Engine database user name : engine
Engine database host name validation : False
Engine database port : 5432
Engine installation : True
NFS setup : True
PKI organization : localdomain.local
NFS mount point : /var/lib/exports/iso
NFS export ACL :
ovirtita.localdomain.local(rw)
Configure VDSM on this host : True
Local storage domain directory : /var/lib/images
Configure local Engine database : True
Set application as default page : True
Configure Apache SSL : True
Configure WebSocket Proxy : True
Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping ovirt-fence-kdump-listener service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL 'engine' database
[ INFO ] Configuring PostgreSQL
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating CA
[ INFO ] Configuring WebSocket Proxy
[ 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
--== SUMMARY ==--
[WARNING] Less than 16384MB of memory is available
SSH fingerprint: 2D:C6:E2:B1:FC:C8:D6:FF:60:C0:26:88:F0:55:69:96
Internal CA
4F:91:A1:21:E5:F3:08:07:30:13:9E:18:E7:CE:63:8C:71:AC:61:3D
Web access is enabled at:
http://ovirtita.localdomain.local:80/ovirt-engine
https://ovirtita.localdomain.local:443/ovirt-engine
Please use the user "admin" and password specified in order to
login
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting nfs services
[ INFO ] Waiting for VDSM host to become operational. This may take
several minutes...
[ INFO ] The VDSM Host is now operational
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140822150237-13m6av.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140822150621-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
A diff between rpm on the system after install is here:
$ diff rpm_3.6master.txt rpm_3.5.txt
180a181
ovirt-engine-extensions-api-impl-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
466,484c467,485
< ovirt-engine-lib-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
< ovirt-engine-restapi-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
< ovirt-engine-sdk-python-3.6.0.0-1.20140820.gitc625968.el6.noarch
< ovirt-engine-setup-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-setup-base-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-setup-plugin-allinone-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-setup-plugin-ovirt-engine-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-setup-plugin-ovirt-engine-common-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-setup-plugin-websocket-proxy-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
< ovirt-engine-tools-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-userportal-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-webadmin-portal-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-websocket-proxy-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
< ovirt-host-deploy-1.3.0-0.0.master.20140821183616.git82dce3c.el6.noarch
<
ovirt-host-deploy-java-1.3.0-0.0.master.20140821183616.git82dce3c.el6.noarch
<
ovirt-host-deploy-offline-1.3.0-0.0.master.20140821183616.git82dce3c.el6.x86_64
< ovirt-image-uploader-3.6.0-0.0.master.20140808125503.git066ed25.el6.noarch
< ovirt-iso-uploader-3.6.0-0.0.master.20140812133505.gita6b721e.el6.noarch
< ovirt-release-master-001-0.0.master.noarch
---
> ovirt-engine-lib-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
> ovirt-engine-restapi-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
> ovirt-engine-sdk-python-3.5.0.5-1.20140820.gitc47c189.el6.noarch
> ovirt-engine-setup-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-setup-base-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-setup-plugin-allinone-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
> ovirt-engine-tools-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-userportal-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-webadmin-portal-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-websocket-proxy-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
> ovirt-host-deploy-1.3.0-0.0.master.20140820115650.git89155f8.el6.noarch
ovirt-host-deploy-java-1.3.0-0.0.master.20140820115650.git89155f8.el6.noarch
ovirt-host-deploy-offline-1.3.0-0.0.master.20140820115650.git89155f8.el6.x86_64
gpg-pubkey-fe590cb7-533d77ee
460,464c461,465
< ovirt-engine-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
< ovirt-engine-backend-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
< ovirt-engine-cli-3.6.0.0-1.20140820.gite160c94.el6.noarch
<
ovirt-engine-dbscripts-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
<
ovirt-engine-extensions-api-impl-3.6.0-0.0.master.20140821172440.gitde6660d.el6.noarch
---
ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-backend-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-engine-cli-3.5.0.4-1.20140820.git374a657.el6.noarch
ovirt-engine-dbscripts-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch
ovirt-image-uploader-3.5.0-0.1.master.20140811110806.git321a491.el6.noarch
ovirt-iso-uploader-3.5.0-0.1.master.20140812133501.gita818d93.el6.noarch
ovirt-release35-001-0.4.rc1.noarch
739,746c740,747
< vdsm-4.16.0-231.git7f489da.el6.x86_64
< vdsm-cli-4.16.0-231.git7f489da.el6.noarch
< vdsm-jsonrpc-4.16.0-231.git7f489da.el6.noarch
< vdsm-jsonrpc-java-1.0.3-0.0.master.20140821162323.git93bec39.el6.noarch
< vdsm-python-4.16.0-231.git7f489da.el6.noarch
< vdsm-python-zombiereaper-4.16.0-231.git7f489da.el6.noarch
< vdsm-xmlrpc-4.16.0-231.git7f489da.el6.noarch
< vdsm-yajsonrpc-4.16.0-231.git7f489da.el6.noarch
---
vdsm-4.16.2-1.gite8cba75.el6.x86_64
vdsm-cli-4.16.2-1.gite8cba75.el6.noarch
vdsm-jsonrpc-4.16.2-1.gite8cba75.el6.noarch
vdsm-jsonrpc-java-1.0.1-0.0.master.20140817113605.git8e0b2b3.el6.noarch
vdsm-python-4.16.2-1.gite8cba75.el6.x86_64
vdsm-python-zombiereaper-4.16.2-1.gite8cba75.el6.noarch
vdsm-xmlrpc-4.16.2-1.gite8cba75.el6.noarch
vdsm-yajsonrpc-4.16.2-1.gite8cba75.el6.noarch
I also have contents of whole /var/log for both 3.6 and 3.5 environments as
after engine-setup ran.
3559
days inactive
3561
days old
6 comments
2 participants
participants (2)
-
Gianluca Cecchi -
Sandro Bonazzola