2:15 p.m.
Hello.
I updated my test self hosted engine vm to 3.6.1 and to CentOS 7.2.
Now it seems it isn't able to to login to webadmin due to this in engine.log
(field is empty in web admin gui)
2015-12-19 13:59:05,182 ERROR
[org.ovirt.engine.core.bll.aaa.LoginBaseCommand] (default task-17) []
Can't login because authentication profile 'internal' doesn't exist.
Is it an already known problem?
The first ERRROR message I find in it is dated 13:34 and it is an SQL one:
2015-12-19 13:34:39,882 ERROR [org.ovirt.engine.core.bll.Backend]
(ServerService Thread Pool -- 42) [] Failed to run compensation on startup
for Command
'org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand',
Command Id 'bb7ee4a3-6b35-4c62-9823-a434a40e5b38':
CallableStatementCallback; SQL [{call insertstorage_domain_dynamic(?, ?,
?)}]; ERROR: insert or update on table "storage_domain_dynamic" violates
foreign key constraint "fk_storage_domain_dynamic_storage_domain_static"
Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present in
table "storage_domain_static".
Where: SQL statement "INSERT INTO
storage_domain_dynamic(available_disk_size, id, used_disk_size)
VALUES(v_available_disk_size, v_id, v_used_disk_size)"
PL/pgSQL function insertstorage_domain_dynamic(integer,uuid,integer) line 3
at SQL statement; nested exception is org.postgresql.util.PSQLException:
ERROR: insert or update on table "storage_domain_dynamic" violates foreign
key constraint "fk_storage_domain_dynamic_storage_domain_static"
Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present in
table "storage_domain_static".
Where: SQL statement "INSERT INTO
storage_domain_dynamic(available_disk_size, id, used_disk_size)
VALUES(v_available_disk_size, v_id, v_used_disk_size)"
PL/pgSQL function insertstorage_domain_dynamic(integer,uuid,integer) line 3
at SQL statement
2015-12-19 13:34:39,882 ERROR [org.ovirt.engine.core.bll.Backend]
(ServerService Thread Pool -- 42) [] Exception:
org.springframework.dao.DataIntegrityViolationException:
CallableStatementCallback; SQL [{call insertstorage_domain_dynamic(?, ?,
?)}]; ERROR: insert or update on table "storage_domain_dynamic" violates
foreign key constraint "fk_storage_domain_dynamic_storage_domain_static"
Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present in
table "storage_domain_static".
I think it is not related to update from CentOS 7.1 to 7.2 that generates
an update of PostgreSQL too because it is 10 minutes later:
from installed one
Nov 04 12:55:30 Installed: postgresql-server-9.2.13-1.el7_1.x86_64
to 7.2 one
Dec 19 13:45:51 Updated: postgresql-server-9.2.14-1.el7_1.x86_64
BTW: my order was
yum update "ovirt-engine-setup-*"
engine-setup
the engine-setup completed successfully with
...
[ INFO ] Stage: Misc configuration
[ INFO ] Backing up database localhost:engine to
'/var/lib/ovirt-engine/backups/engine-20151219132925.5OoFQA.dump'.
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating/refreshing Engine 'internal' domain database schema
[ INFO ] Upgrading 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 ==--
SSH fingerprint: 19:56:8d:3e:50:fc:90:37:5a:ba:6c:57:30:b1:7d:93
Internal CA
DA:E6:04:34:99:A0:DB:CE:3F:0A:7B:A2:96:67:4C:7F:19:CA:95:5F
Note! If you want to gather statistical information you can
install Reports and/or DWH:
http://www.ovirt.org/Ovirt_DWH
http://www.ovirt.org/Ovirt_Reports
Web access is enabled at:
http://ractorshe.mydomain:80/ovirt-engine
https://ractorshe.mydomain:443/ovirt-engine
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting ovirt-vmconsole proxy service
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151219132415-2pfee1.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20151219133045-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
Strangely the VM was shutdown...
In /var/log/libvirt/qemu/HostedEngine.log I saw (in UTC)
2015-12-19 12:31:19.494+0000: shutting down
So I exited from global maintenance, the VM was started and I verified that
admin web gui was ok with new version.
Then I put maintenance again and run on engine VM
systemctl stop ovirt-engine
yum update (I forgot to also shutdown POstgreSQL before... )
shutdown -r now
As it was in maintenance it wasn't started again so I exited from
maintenance and VM was started, but now I'm not able to see the internal
profile....
Let me know if you need further info.
Gianluca
6 p.m.
On Sat, Dec 19, 2015 at 2:15 PM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
Hello.
I updated my test self hosted engine vm to 3.6.1 and to CentOS 7.2.
Now it seems it isn't able to to login to webadmin due to this in
engine.log
(field is empty in web admin gui)
2015-12-19 13:59:05,182 ERROR
[org.ovirt.engine.core.bll.aaa.LoginBaseCommand] (default task-17) []
Can't login because authentication profile 'internal' doesn't exist.
Is it an already known problem?
Here the output of the engine-setup run today and completead at 13:30.
https://drive.google.com/file/d/0BwoPbcrMv8mveWlPdmh6MkV5cDA/view?usp=sha...
Last lines in messages something like this:
Dec 19 13:30:45 ractorshe ovirt-websocket-proxy.py:
ovirt-websocket-proxy[21225] INFO msg:824 - Deny non-SSL/TLS connections
Dec 19 13:30:45 ractorshe journal: 2015-12-19 13:30:45,958
ovirt-websocket-proxy: INFO msg:824 - proxying from *:6100 to targets in
/dummy
Dec 19 13:30:45 ractorshe ovirt-websocket-proxy.py:
ovirt-websocket-proxy[21225] INFO msg:824 - proxying from *:6100 to
targets in /dummy
Dec 19 13:30:55 ractorshe systemd: serial-getty(a)ttyS0.service holdoff time
over, scheduling restart.
Dec 19 13:30:55 ractorshe systemd: Stopping Serial Getty on ttyS0...
Dec 19 13:30:55 ractorshe systemd: Starting Serial Getty on ttyS0...
Dec 19 13:30:55 ractorshe systemd: Started Serial Getty on ttyS0.
Dec 19 13:31:05 ractorshe systemd: serial-getty(a)ttyS0.service holdoff time
over, scheduling restart.
Dec 19 13:31:05 ractorshe systemd: Stopping Serial Getty on ttyS0...
Dec 19 13:31:05 ractorshe systemd: Starting Serial Getty on ttyS0...
Dec 19 13:31:05 ractorshe systemd: Started Serial Getty on ttyS0.
Then I see a seven lines of this sequence:
^@^@^@^@^@^@^@^@^@^@
and then the start of the VM (cause d by leaving maintenance)
Dec 19 13:34:14 ractorshe rsyslogd: [origin software="rsyslogd"
swVersion="7.4.7" x-pid="484"
x-info="http://www.rsyslog.com"] s
tart
Dec 19 13:34:14 ractorshe rsyslogd-2307: warning: ~ action is deprecated,
consider using the 'stop' statement instead [try
http://www.rsyslog.com/e/2307 ]
Dec 19 13:34:09 ractorshe journal: Runtime journal is using 8.0M (max
794.3M, leaving 1.1G of free 7.7G, current limit 794.3M).
Dec 19 13:34:09 ractorshe kernel: Initializing cgroup subsys cpuset
Dec 19 13:34:09 ractorshe kernel: Initializing cgroup subsys cpu
..
the shutdown was not clean because I see also this during the start
Dec 19 13:34:10 ractorshe kernel: input: ImExPS/2 Generic Explorer Mouse as
/devices/platform/i8042/
serio1/input/input2
Dec 19 13:34:10 ractorshe kernel: tsc: Refined TSC clocksource calibration:
2260.990 MHz
Dec 19 13:34:12 ractorshe systemd-fsck: /dev/vda1: Clearing orphaned inode
272353 (uid=0, gid=0, mode=0100600, size=43056)
Dec 19 13:34:12 ractorshe systemd-fsck: /dev/vda1: Clearing orphaned inode
272352 (uid=0, gid=0, mode=0100600, size=16)
first lines of postgresql-Sat.log in /var/lib/pgsql/data/pg_log are:
WARNING: column "user_role_title" has type "unknown"
DETAIL: Proceeding with relation creation anyway.
LOG: database system was interrupted; last known up at 2015-12-19 12:28:54
UTC
FATAL: the database system is starting up
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 1/1FDFCAC8
LOG: record with zero length at 1/20A06E50
LOG: redo done at 1/20A06E20
LOG: last completed transaction was at log time 2015-12-19
12:31:19.33468+00
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
ERROR: insert or update on table "storage_domain_dynamic" violates foreign
key constraint "fk_storage_domain_dynamic_storage_domain_static"
DETAIL: Key (id)=(00000000-0000-0000-0000-000000000000) is not present in
table "storage_domain_static".
CONTEXT: SQL statement "INSERT INTO
storage_domain_dynamic(available_disk_size, id, used_disk_size)
VALUES(v_available_disk_size, v_id, v_used_disk_size)"
PL/pgSQL function
insertstorage_domain_dynamic(integer,uuid,integer) line 3 at SQL statement
STATEMENT: select * from insertstorage_domain_dynamic($1, $2, $3) as result
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
FATAL: terminating connection due to administrator command
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2015-12-19 12:47:22 UTC
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_4"."tt_temp22" in
database "engine"
LOG: autovacuum: found orphan temp table "pg_temp_7"."tt_temp22" in
database "engine"
LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2015-12-19 12:55:07 UTC
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: insert or update on table "storage_domain_dynamic" violates foreign
key constraint "fk_storage_domain_dynamic_storage_domain_static"
DETAIL: Key (id)=(00000000-0000-0000-0000-000000000000) is not present in
table "storage_domain_static".
CONTEXT: SQL statement "INSERT INTO
storage_domain_dynamic(available_disk_size, id, used_disk_size)
VALUES(v_available_disk_size, v_id, v_used_disk_size)"
SO I think something wrong has remained inside the database, even if I
don't understand what and why...
What I see in messages of hypervisor around the time the engine VM went
down:
Dec 19 13:30:01 ractor systemd: Starting Session 1636 of user root.
Dec 19 13:31:19 ractor sanlock[1239]: 2015-12-19 13:31:19+0100 827362
[1239]: s1 kill 3110 sig 9 count 1
Dec 19 13:31:19 ractor sanlock[1239]: 2015-12-19 13:31:19+0100 827362
[1239]: dead 3110 ci 3 count 1
Dec 19 13:31:19 ractor journal: internal error: End of file from monitor
Dec 19 13:31:19 ractor kernel: ovirtmgmt: port 2(vnet0) entered disabled
state
Dec 19 13:31:19 ractor kernel: device vnet0 left promiscuous mode
Dec 19 13:31:19 ractor kernel: ovirtmgmt: port 2(vnet0) entered disabled
state
Dec 19 13:31:19 ractor kvm: 2 guests now active
Dec 19 13:31:19 ractor systemd-machined: Machine qemu-HostedEngine
terminated.
Dec 19 13:31:21 ractor journal: ovirt-ha-broker
cpu_load_no_engine.EngineHealth ERROR Failed to read vm stats: [Errno 2] No
such file or directory: '/proc/3110/stat'
Dec 19 13:31:21 ractor journal: vdsm root WARNING File:
/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.com.redhat.rhevm.vdsm
already removed
Dec 19 13:31:21 ractor journal: vdsm root WARNING File:
/var/lib/libvirt/qemu/channels/7b0ff898-0a9e-4b97-8292-1d9f2a0a6683.org.qemu.guest_agent.0
already removed
Gianluca
7:58 p.m.
Reading it again, I'm not sure the engine was even tested with centos 7.
As far as I know only centos 6 is supported/tested for the engine machine.
CC-ing Eli to try and help with the DB issue, but if you have any backup I
guess it would be safer.
Oved
On Dec 19, 2015 15:15, "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
wrote:
Hello.
I updated my test self hosted engine vm to 3.6.1 and to CentOS 7.2.
Now it seems it isn't able to to login to webadmin due to this in
engine.log
(field is empty in web admin gui)
2015-12-19 13:59:05,182 ERROR
[org.ovirt.engine.core.bll.aaa.LoginBaseCommand] (default task-17) []
Can't login because authentication profile 'internal' doesn't exist.
Is it an already known problem?
The first ERRROR message I find in it is dated 13:34 and it is an SQL one:
2015-12-19 13:34:39,882 ERROR [org.ovirt.engine.core.bll.Backend]
(ServerService Thread Pool -- 42) [] Failed to run compensation on startup
for Command
'org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand',
Command Id 'bb7ee4a3-6b35-4c62-9823-a434a40e5b38':
CallableStatementCallback; SQL [{call insertstorage_domain_dynamic(?, ?,
?)}]; ERROR: insert or update on table "storage_domain_dynamic" violates
foreign key constraint "fk_storage_domain_dynamic_storage_domain_static"
Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present
in table "storage_domain_static".
Where: SQL statement "INSERT INTO
storage_domain_dynamic(available_disk_size, id, used_disk_size)
VALUES(v_available_disk_size, v_id, v_used_disk_size)"
PL/pgSQL function insertstorage_domain_dynamic(integer,uuid,integer) line
3 at SQL statement; nested exception is org.postgresql.util.PSQLException:
ERROR: insert or update on table "storage_domain_dynamic" violates foreign
key constraint "fk_storage_domain_dynamic_storage_domain_static"
Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present
in table "storage_domain_static".
Where: SQL statement "INSERT INTO
storage_domain_dynamic(available_disk_size, id, used_disk_size)
VALUES(v_available_disk_size, v_id, v_used_disk_size)"
PL/pgSQL function insertstorage_domain_dynamic(integer,uuid,integer) line
3 at SQL statement
2015-12-19 13:34:39,882 ERROR [org.ovirt.engine.core.bll.Backend]
(ServerService Thread Pool -- 42) [] Exception:
org.springframework.dao.DataIntegrityViolationException:
CallableStatementCallback; SQL [{call insertstorage_domain_dynamic(?, ?,
?)}]; ERROR: insert or update on table "storage_domain_dynamic" violates
foreign key constraint "fk_storage_domain_dynamic_storage_domain_static"
Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present
in table "storage_domain_static".
I think it is not related to update from CentOS 7.1 to 7.2 that generates
an update of PostgreSQL too because it is 10 minutes later:
from installed one
Nov 04 12:55:30 Installed: postgresql-server-9.2.13-1.el7_1.x86_64
to 7.2 one
Dec 19 13:45:51 Updated: postgresql-server-9.2.14-1.el7_1.x86_64
BTW: my order was
yum update "ovirt-engine-setup-*"
engine-setup
the engine-setup completed successfully with
...
[ INFO ] Stage: Misc configuration
[ INFO ] Backing up database localhost:engine to
'/var/lib/ovirt-engine/backups/engine-20151219132925.5OoFQA.dump'.
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating/refreshing Engine 'internal' domain database schema
[ INFO ] Upgrading 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 ==--
SSH fingerprint: 19:56:8d:3e:50:fc:90:37:5a:ba:6c:57:30:b1:7d:93
Internal CA
DA:E6:04:34:99:A0:DB:CE:3F:0A:7B:A2:96:67:4C:7F:19:CA:95:5F
Note! If you want to gather statistical information you can
install Reports and/or DWH:
http://www.ovirt.org/Ovirt_DWH
http://www.ovirt.org/Ovirt_Reports
Web access is enabled at:
http://ractorshe.mydomain:80/ovirt-engine
https://ractorshe.mydomain:443/ovirt-engine
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting ovirt-vmconsole proxy service
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151219132415-2pfee1.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20151219133045-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
Strangely the VM was shutdown...
In /var/log/libvirt/qemu/HostedEngine.log I saw (in UTC)
2015-12-19 12:31:19.494+0000: shutting down
So I exited from global maintenance, the VM was started and I verified
that admin web gui was ok with new version.
Then I put maintenance again and run on engine VM
systemctl stop ovirt-engine
yum update (I forgot to also shutdown POstgreSQL before... )
shutdown -r now
As it was in maintenance it wasn't started again so I exited from
maintenance and VM was started, but now I'm not able to see the internal
profile....
Let me know if you need further info.
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
8:16 p.m.
On Sat, Dec 19, 2015 at 7:58 PM, Oved Ourfali <oourfali(a)redhat.com> wrote:
Reading it again, I'm not sure the engine was even tested with
centos 7.
As far as I know only centos 6 is supported/tested for the engine machine.
Our ovirt-engine-appliance is already based on Centos 7 so I think that a
consistent part of our 3.6 upstream user is already on that.
[root@enginevm ~]# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)
CC-ing Eli to try and help with the DB issue, but if you have any
backup I
guess it would be safer.
Oved
On Dec 19, 2015 15:15, "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
wrote:
> Hello.
>
> I updated my test self hosted engine vm to 3.6.1 and to CentOS 7.2.
>
> Now it seems it isn't able to to login to webadmin due to this in
> engine.log
> (field is empty in web admin gui)
>
> 2015-12-19 13:59:05,182 ERROR
> [org.ovirt.engine.core.bll.aaa.LoginBaseCommand] (default task-17) []
> Can't login because authentication profile 'internal' doesn't exist.
>
> Is it an already known problem?
>
> The first ERRROR message I find in it is dated 13:34 and it is an SQL one:
>
> 2015-12-19 13:34:39,882 ERROR [org.ovirt.engine.core.bll.Backend]
> (ServerService Thread Pool -- 42) [] Failed to run compensation on startup
> for Command
> 'org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand',
> Command Id 'bb7ee4a3-6b35-4c62-9823-a434a40e5b38':
> CallableStatementCallback; SQL [{call insertstorage_domain_dynamic(?, ?,
> ?)}]; ERROR: insert or update on table "storage_domain_dynamic" violates
> foreign key constraint "fk_storage_domain_dynamic_storage_domain_static"
> Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present
> in table "storage_domain_static".
> Where: SQL statement "INSERT INTO
> storage_domain_dynamic(available_disk_size, id, used_disk_size)
> VALUES(v_available_disk_size, v_id, v_used_disk_size)"
> PL/pgSQL function insertstorage_domain_dynamic(integer,uuid,integer) line
> 3 at SQL statement; nested exception is org.postgresql.util.PSQLException:
> ERROR: insert or update on table "storage_domain_dynamic" violates foreign
> key constraint "fk_storage_domain_dynamic_storage_domain_static"
> Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present
> in table "storage_domain_static".
> Where: SQL statement "INSERT INTO
> storage_domain_dynamic(available_disk_size, id, used_disk_size)
> VALUES(v_available_disk_size, v_id, v_used_disk_size)"
> PL/pgSQL function insertstorage_domain_dynamic(integer,uuid,integer) line
> 3 at SQL statement
> 2015-12-19 13:34:39,882 ERROR [org.ovirt.engine.core.bll.Backend]
> (ServerService Thread Pool -- 42) [] Exception:
> org.springframework.dao.DataIntegrityViolationException:
> CallableStatementCallback; SQL [{call insertstorage_domain_dynamic(?, ?,
> ?)}]; ERROR: insert or update on table "storage_domain_dynamic" violates
> foreign key constraint "fk_storage_domain_dynamic_storage_domain_static"
> Detail: Key (id)=(00000000-0000-0000-0000-000000000000) is not present
> in table "storage_domain_static".
>
>
> I think it is not related to update from CentOS 7.1 to 7.2 that generates
> an update of PostgreSQL too because it is 10 minutes later:
> from installed one
> Nov 04 12:55:30 Installed: postgresql-server-9.2.13-1.el7_1.x86_64
> to 7.2 one
> Dec 19 13:45:51 Updated: postgresql-server-9.2.14-1.el7_1.x86_64
>
> BTW: my order was
>
> yum update "ovirt-engine-setup-*"
> engine-setup
>
> the engine-setup completed successfully with
> ...
> [ INFO ] Stage: Misc configuration
> [ INFO ] Backing up database localhost:engine to
> '/var/lib/ovirt-engine/backups/engine-20151219132925.5OoFQA.dump'.
> [ INFO ] Creating/refreshing Engine database schema
> [ INFO ] Creating/refreshing Engine 'internal' domain database schema
> [ INFO ] Upgrading 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 ==--
>
> SSH fingerprint: 19:56:8d:3e:50:fc:90:37:5a:ba:6c:57:30:b1:7d:93
> Internal CA
> DA:E6:04:34:99:A0:DB:CE:3F:0A:7B:A2:96:67:4C:7F:19:CA:95:5F
> Note! If you want to gather statistical information you can
> install Reports and/or DWH:
> http://www.ovirt.org/Ovirt_DWH
> http://www.ovirt.org/Ovirt_Reports
> Web access is enabled at:
> http://ractorshe.mydomain:80/ovirt-engine
> https://ractorshe.mydomain:443/ovirt-engine
>
> --== END OF SUMMARY ==--
>
> [ INFO ] Starting engine service
> [ INFO ] Restarting httpd
> [ INFO ] Restarting ovirt-vmconsole proxy service
> [ INFO ] Stage: Clean up
> Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-setup-20151219132415-2pfee1.log
> [ INFO ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20151219133045-setup.conf'
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ INFO ] Execution of setup completed successfully
>
> Strangely the VM was shutdown...
> In /var/log/libvirt/qemu/HostedEngine.log I saw (in UTC)
> 2015-12-19 12:31:19.494+0000: shutting down
>
> So I exited from global maintenance, the VM was started and I verified
> that admin web gui was ok with new version.
>
> Then I put maintenance again and run on engine VM
>
> systemctl stop ovirt-engine
> yum update (I forgot to also shutdown POstgreSQL before... )
> shutdown -r now
>
> As it was in maintenance it wasn't started again so I exited from
> maintenance and VM was started, but now I'm not able to see the internal
> profile....
>
> Let me know if you need further info.
>
> Gianluca
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
8:57 p.m.
On Sat, Dec 19, 2015 at 8:16 PM, Simone Tiraboschi <stirabos(a)redhat.com>
wrote:
On Sat, Dec 19, 2015 at 7:58 PM, Oved Ourfali <oourfali(a)redhat.com> wrote:
> Reading it again, I'm not sure the engine was even tested with centos 7.
> As far as I know only centos 6 is supported/tested for the engine machine.
>
Our ovirt-engine-appliance is already based on Centos 7 so I think that a
consistent part of our 3.6 upstream user is already on that.
[root@enginevm ~]# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)
Yes, for engine VM in HE I used the oVirt shipped appliance that was
already in CentOS 7.1 and the flow I was trying to complete was to update
it to 7.2 as supported.
From the last output I sent it seems in some way sanlock was
responsible
for the detath of engineVM right after completion of engine-setup.
And possibly causing any corruption inside the db
If it can be of any help, here the contents of the two tables involved
storage_domain_static
and
storage_domain_dynamic
https://drive.google.com/file/d/0BwoPbcrMv8mvU0RoZjFZSzRKbzQ/view?usp=sha...
If you have any othr quey to run against db....
but I don't understand how this can influence the fact that inside the web
ui login I don't see any selectable value for the profile field: the
"internal" default domain is missing.... I didn't implement any other
https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sha...
Gianluca
9:14 p.m.
On Sat, Dec 19, 2015 at 8:57 PM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
but I don't understand how this can influence the fact that inside the web
ui login I don't see any selectable value for the profile field: the
"internal" default domain is missing.... I didn't implement any other
https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sha...
Gianluca
the culprit could be related to these lines in engine.log
2015-12-19 13:57:22,403 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Extension 'internal-authn' loaded
2015-12-19 13:57:22,406 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Loading extension 'internal-authz'
2015-12-19 13:57:22,408 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Extension 'internal-authz' loaded
2015-12-19 13:57:22,409 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Initializing extension 'internal-authn'
2015-12-19 13:57:22,447 ERROR
[org.ovirt.engine.extension.aaa.jdbc.binding.api.AuthnExtension]
(ServerService Thread Pool -- 41) [] Unexpected Exception invoking:
EXTENSION_INITIALIZE[e5ae1b7f-9104-4f23-a444-7b9175ff68d2]
2015-12-19 13:57:22,447 ERROR
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Error in activating extension 'internal-authn':
Database schema is older than required by currently installed
ovirt-engine-extension-aaa-jdbc package version. Please upgrade profile
database schema before proceeding (for more info about upgrade please take
a look at README.admin file contained in ovirt-engine-extension-aaa-jdbc
package).
2015-12-19 13:57:22,448 ERROR
[org.ovirt.engine.core.utils.extensionsmgr.EngineExtensionsManager]
(ServerService Thread Pool -- 41) [] Could not initialize extension
'internal-authn'. Exception message is: Class: class
org.ovirt.engine.core.extensions.mgr.ExtensionInvokeCommandFailedException
Input:
{Extkey[name=EXTENSION_INVOKE_COMMAND;type=class
org.ovirt.engine.api.extensions.ExtUUID;uuid=EXTENSION_INVOKE_COMMAND[485778ab-bede-4f1a-b823-77b262a2f28d];]=EXTENSION_INITIALIZE[e5ae1b7f-9104-4f23-a444-7b9175ff68d2],
Extkey[name=EXTENSION_INVOKE_CONTEXT;type=class
org.ovirt.engine.api.extensions.E
Full engine.log for today is here:
https://drive.google.com/file/d/0BwoPbcrMv8mvVGVxNVN4TUdQR2c/view?usp=sha...
if you can give it an eye.
I fear that the "yum update" command I executed after "engine-setuo"
completed successfully, to update the OS to CentOS 7.2 has pulled in the
package
Dec 19 13:46:48 Updated: ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
and has created my problems... and create similar ones to other guys...
what do you think?
Gianluca
11:45 p.m.
On Sat, Dec 19, 2015 at 9:14 PM, Gianluca Cecchi wrote:
I fear that the "yum update" command I executed after "engine-setuo"
completed successfully, to update the OS to CentOS 7.2 has pulled in the
package
Dec 19 13:46:48 Updated: ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
and has created my problems... and create similar ones to other guys...
what do you think?
Gianluca
It was indeed the main reason for not being able to authenticate in
webadmin portal:
I reverted to the previous version of the package. After putting env in
maintenance global I executed:
# systemctl stop ovirt-engine
Previous version:
Nov 04 12:52:20 Installed:
ovirt-engine-extension-aaa-jdbc-1.0.1-1.el7.noarch
# yum downgrade ovirt-engine-extension-aaa-jdbc
...
Dependencies Resolved
====================================================================================================
Package Arch Version
Repository Size
====================================================================================================
Downgrading:
ovirt-engine-extension-aaa-jdbc noarch 1.0.1-1.el7
ovirt-3.6 165 k
# systemctl start ovirt-engine
and I'm able to connect again. In engine.log now
2015-12-19 23:38:31,352 INFO
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
Loaded file
'/etc/ovirt-engine/engine.conf.d/50-ovirt-engine-extension-aaa-jdbc.conf'.
...
2015-12-19 23:38:31,357 INFO
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
Value of property 'ENGINE_JAVA_MODULEPATH' is
'/usr/share/ovirt-engine-wildfly-overlay/modules:/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules'.
...
2015-12-19 23:38:34,355 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 37) [] Instance name: 'internal-authn', Extension name:
'"ovirt-engine-extension-aaa-jdbc".authn', Version:
'"1.0.1"', Notes:
'Display name: "ovirt-engine-extension-aaa-jdbc"', License: 'ASL
2.0',
Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface
Version: '0', File:
'/etc/ovirt-engine/extensions.d/internal-authn.properties', Initialized:
'true'
2015-12-19 23:38:34,355 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 37) [] Instance name: 'internal-authz', Extension name:
'"ovirt-engine-extension-aaa-jdbc".authz', Version:
'"1.0.1"', Notes:
'Display name: "ovirt-engine-extension-aaa-jdbc"', License: 'ASL
2.0',
Home: 'http://www.ovirt.org', Author 'The oVirt Project', Build interface
Version: '0', File:
'/etc/ovirt-engine/extensions.d/internal-authz.properties', Initialized:
'true'
10:50 a.m.
On Sun, Dec 20, 2015 at 12:45 AM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
On Sat, Dec 19, 2015 at 9:14 PM, Gianluca Cecchi wrote:
>
>
> I fear that the "yum update" command I executed after
"engine-setuo"
> completed successfully, to update the OS to CentOS 7.2 has pulled in the
> package
> Dec 19 13:46:48 Updated:
> ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
>
> and has created my problems... and create similar ones to other guys...
> what do you think?
>
> Gianluca
It was indeed the main reason for not being able to authenticate in webadmin
portal:
I reverted to the previous version of the package. After putting env in
maintenance global I executed:
# systemctl stop ovirt-engine
Previous version:
Nov 04 12:52:20 Installed:
ovirt-engine-extension-aaa-jdbc-1.0.1-1.el7.noarch
# yum downgrade ovirt-engine-extension-aaa-jdbc
...
Dependencies Resolved
====================================================================================================
Package Arch Version
Repository Size
====================================================================================================
Downgrading:
ovirt-engine-extension-aaa-jdbc noarch 1.0.1-1.el7
ovirt-3.6 165 k
# systemctl start ovirt-engine
and I'm able to connect again. In engine.log now
2015-12-19 23:38:31,352 INFO
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
Loaded file
'/etc/ovirt-engine/engine.conf.d/50-ovirt-engine-extension-aaa-jdbc.conf'.
...
2015-12-19 23:38:31,357 INFO
[org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
Value of property 'ENGINE_JAVA_MODULEPATH' is
'/usr/share/ovirt-engine-wildfly-overlay/modules:/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules'.
...
2015-12-19 23:38:34,355 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 37) [] Instance name: 'internal-authn', Extension name:
'"ovirt-engine-extension-aaa-jdbc".authn', Version:
'"1.0.1"', Notes:
'Display name: "ovirt-engine-extension-aaa-jdbc"', License: 'ASL
2.0', Home:
'http://www.ovirt.org', Author 'The oVirt Project', Build interface
Version:
'0', File: '/etc/ovirt-engine/extensions.d/internal-authn.properties',
Initialized: 'true'
2015-12-19 23:38:34,355 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 37) [] Instance name: 'internal-authz', Extension name:
'"ovirt-engine-extension-aaa-jdbc".authz', Version:
'"1.0.1"', Notes:
'Display name: "ovirt-engine-extension-aaa-jdbc"', License: 'ASL
2.0', Home:
'http://www.ovirt.org', Author 'The oVirt Project', Build interface
Version:
'0', File: '/etc/ovirt-engine/extensions.d/internal-authz.properties',
Initialized: 'true'
On Sat, Dec 19, 2015 at 10:14 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
On Sat, Dec 19, 2015 at 8:57 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com>
wrote:
>
>
>
> but I don't understand how this can influence the fact that inside the web
> ui login I don't see any selectable value for the profile field: the
> "internal" default domain is missing.... I didn't implement any other
>
> https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sha...
>
> Gianluca
the culprit could be related to these lines in engine.log
2015-12-19 13:57:22,403 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Extension 'internal-authn' loaded
2015-12-19 13:57:22,406 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Loading extension 'internal-authz'
2015-12-19 13:57:22,408 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Extension 'internal-authz' loaded
2015-12-19 13:57:22,409 INFO
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Initializing extension 'internal-authn'
2015-12-19 13:57:22,447 ERROR
[org.ovirt.engine.extension.aaa.jdbc.binding.api.AuthnExtension]
(ServerService Thread Pool -- 41) [] Unexpected Exception invoking:
EXTENSION_INITIALIZE[e5ae1b7f-9104-4f23-a444-7b9175ff68d2]
2015-12-19 13:57:22,447 ERROR
[org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
Thread Pool -- 41) [] Error in activating extension 'internal-authn':
Database schema is older than required by currently installed
ovirt-engine-extension-aaa-jdbc package version. Please upgrade profile
database schema before proceeding (for more info about upgrade please take a
look at README.admin file contained in ovirt-engine-extension-aaa-jdbc
package).
README.admin there [1] says, among other things:
===================================================================
IV. Upgrading 'internal' profile
ATTENTION: aaa-jdbc extension is not upgraded automatically during oVirt
engine upgrade and it needs to be upgraded manually!
...
stop engine
...
yum update extension package
...
engine-setup
===================================================================
So you should run engine-setup after you update this package.
Martin - is this intentional? Why not update the package automatically
during engine-setup?
Or even version-lock it? I do not think people should expect their engine
to not allow logins after they run 'yum update'. Adding also Sandro.
[1]
https://gerrit.ovirt.org/gitweb?p=ovirt-engine-extension-aaa-jdbc.git;a=b...
--
Didi
8:50 p.m.
----- Original Message -----
From: "Yedidyah Bar David" <didi(a)redhat.com>
To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>, "Martin
Perina" <mperina(a)redhat.com>, "Sandro Bonazzola"
<sbonazzo(a)redhat.com>
Cc: "Simone Tiraboschi" <stirabos(a)redhat.com>, "users"
<users(a)ovirt.org>
Sent: Sunday, December 20, 2015 10:50:43 AM
Subject: Re: [ovirt-users] After update to 3.6.1 profile internal does not exist message
On Sun, Dec 20, 2015 at 12:45 AM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
> On Sat, Dec 19, 2015 at 9:14 PM, Gianluca Cecchi wrote:
>>
>>
>> I fear that the "yum update" command I executed after
"engine-setuo"
>> completed successfully, to update the OS to CentOS 7.2 has pulled in the
>> package
>> Dec 19 13:46:48 Updated:
>> ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
>>
>> and has created my problems... and create similar ones to other guys...
>> what do you think?
>>
>> Gianluca
>
>
>
> It was indeed the main reason for not being able to authenticate in
> webadmin
> portal:
>
> I reverted to the previous version of the package. After putting env in
> maintenance global I executed:
>
> # systemctl stop ovirt-engine
>
> Previous version:
> Nov 04 12:52:20 Installed:
> ovirt-engine-extension-aaa-jdbc-1.0.1-1.el7.noarch
>
> # yum downgrade ovirt-engine-extension-aaa-jdbc
> ...
> Dependencies Resolved
>
>
====================================================================================================
> Package Arch Version
> Repository Size
>
====================================================================================================
> Downgrading:
> ovirt-engine-extension-aaa-jdbc noarch 1.0.1-1.el7
> ovirt-3.6 165 k
>
> # systemctl start ovirt-engine
>
> and I'm able to connect again. In engine.log now
>
> 2015-12-19 23:38:31,352 INFO
> [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
> Loaded file
> '/etc/ovirt-engine/engine.conf.d/50-ovirt-engine-extension-aaa-jdbc.conf'.
> ...
> 2015-12-19 23:38:31,357 INFO
> [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
> Value of property 'ENGINE_JAVA_MODULEPATH' is
>
'/usr/share/ovirt-engine-wildfly-overlay/modules:/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules'.
> ...
> 2015-12-19 23:38:34,355 INFO
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 37) [] Instance name: 'internal-authn', Extension name:
> '"ovirt-engine-extension-aaa-jdbc".authn', Version:
'"1.0.1"', Notes:
> 'Display name: "ovirt-engine-extension-aaa-jdbc"', License:
'ASL 2.0',
> Home:
> 'http://www.ovirt.org', Author 'The oVirt Project', Build interface
> Version:
> '0', File:
'/etc/ovirt-engine/extensions.d/internal-authn.properties',
> Initialized: 'true'
> 2015-12-19 23:38:34,355 INFO
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 37) [] Instance name: 'internal-authz', Extension name:
> '"ovirt-engine-extension-aaa-jdbc".authz', Version:
'"1.0.1"', Notes:
> 'Display name: "ovirt-engine-extension-aaa-jdbc"', License:
'ASL 2.0',
> Home:
> 'http://www.ovirt.org', Author 'The oVirt Project', Build interface
> Version:
> '0', File:
'/etc/ovirt-engine/extensions.d/internal-authz.properties',
> Initialized: 'true'
On Sat, Dec 19, 2015 at 10:14 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
> On Sat, Dec 19, 2015 at 8:57 PM, Gianluca Cecchi
> <gianluca.cecchi(a)gmail.com>
> wrote:
>>
>>
>>
>> but I don't understand how this can influence the fact that inside the web
>> ui login I don't see any selectable value for the profile field: the
>> "internal" default domain is missing.... I didn't implement any
other
>>
>> https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sha...
>>
>> Gianluca
>
>
>
> the culprit could be related to these lines in engine.log
>
> 2015-12-19 13:57:22,403 INFO
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 41) [] Extension 'internal-authn' loaded
> 2015-12-19 13:57:22,406 INFO
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 41) [] Loading extension 'internal-authz'
> 2015-12-19 13:57:22,408 INFO
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 41) [] Extension 'internal-authz' loaded
> 2015-12-19 13:57:22,409 INFO
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 41) [] Initializing extension 'internal-authn'
> 2015-12-19 13:57:22,447 ERROR
> [org.ovirt.engine.extension.aaa.jdbc.binding.api.AuthnExtension]
> (ServerService Thread Pool -- 41) [] Unexpected Exception invoking:
> EXTENSION_INITIALIZE[e5ae1b7f-9104-4f23-a444-7b9175ff68d2]
> 2015-12-19 13:57:22,447 ERROR
> [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> Thread Pool -- 41) [] Error in activating extension 'internal-authn':
> Database schema is older than required by currently installed
> ovirt-engine-extension-aaa-jdbc package version. Please upgrade profile
> database schema before proceeding (for more info about upgrade please take
> a
> look at README.admin file contained in ovirt-engine-extension-aaa-jdbc
> package).
README.admin there [1] says, among other things:
===================================================================
IV. Upgrading 'internal' profile
ATTENTION: aaa-jdbc extension is not upgraded automatically during oVirt
engine upgrade and it needs to be upgraded manually!
...
stop engine
...
yum update extension package
...
engine-setup
===================================================================
So you should run engine-setup after you update this package.
Martin - is this intentional? Why not update the package automatically
during engine-setup?
Or even version-lock it? I do not think people should expect their engine
to not allow logins after they run 'yum update'. Adding also Sandro.
Hi,
there are several reasons for this:
1. aaa-jdbc is an engine 3.6 extension, engine requires its presence to
provide 'internal' domain but it doesn't require any specific version,
so users may update aaa-jdbc independently on engine if they need
features provided provided by new version
2. engine-setup automatically configures/upgrades 'internal' domain, but
users may define manually other domains (as described in README.admin)
and those domains are not touched by engine-setup at all
3. Due to 1. and 2. we decided not to define version specific requirement
between engine and aaa-jdbc in engine-setup (same behaviour as already
exists for other engine extensions). So users may for example upgrade
engine, but leave aaa-jdbc as is or leave engine as is and upgrade
aaa-jdbc if they need it. Users just need to get used to read doc
before doing upgrade.
Martin
2:10 p.m.
On Sun, Dec 20, 2015 at 9:50 PM, Martin Perina <mperina(a)redhat.com> wrote:
----- Original Message -----
> From: "Yedidyah Bar David" <didi(a)redhat.com>
> To: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>, "Martin
Perina" <mperina(a)redhat.com>, "Sandro Bonazzola"
> <sbonazzo(a)redhat.com>
> Cc: "Simone Tiraboschi" <stirabos(a)redhat.com>, "users"
<users(a)ovirt.org>
> Sent: Sunday, December 20, 2015 10:50:43 AM
> Subject: Re: [ovirt-users] After update to 3.6.1 profile internal does not exist
message
>
> On Sun, Dec 20, 2015 at 12:45 AM, Gianluca Cecchi
> <gianluca.cecchi(a)gmail.com> wrote:
> > On Sat, Dec 19, 2015 at 9:14 PM, Gianluca Cecchi wrote:
> >>
> >>
> >> I fear that the "yum update" command I executed after
"engine-setuo"
> >> completed successfully, to update the OS to CentOS 7.2 has pulled in the
> >> package
> >> Dec 19 13:46:48 Updated:
> >> ovirt-engine-extension-aaa-jdbc-1.0.4-1.el7.noarch
> >>
> >> and has created my problems... and create similar ones to other guys...
> >> what do you think?
> >>
> >> Gianluca
> >
> >
> >
> > It was indeed the main reason for not being able to authenticate in
> > webadmin
> > portal:
> >
> > I reverted to the previous version of the package. After putting env in
> > maintenance global I executed:
> >
> > # systemctl stop ovirt-engine
> >
> > Previous version:
> > Nov 04 12:52:20 Installed:
> > ovirt-engine-extension-aaa-jdbc-1.0.1-1.el7.noarch
> >
> > # yum downgrade ovirt-engine-extension-aaa-jdbc
> > ...
> > Dependencies Resolved
> >
> >
====================================================================================================
> > Package Arch Version
> > Repository Size
> >
====================================================================================================
> > Downgrading:
> > ovirt-engine-extension-aaa-jdbc noarch 1.0.1-1.el7
> > ovirt-3.6 165 k
> >
> > # systemctl start ovirt-engine
> >
> > and I'm able to connect again. In engine.log now
> >
> > 2015-12-19 23:38:31,352 INFO
> > [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
> > Loaded file
> >
'/etc/ovirt-engine/engine.conf.d/50-ovirt-engine-extension-aaa-jdbc.conf'.
> > ...
> > 2015-12-19 23:38:31,357 INFO
> > [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (default task-1) []
> > Value of property 'ENGINE_JAVA_MODULEPATH' is
> >
'/usr/share/ovirt-engine-wildfly-overlay/modules:/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules'.
> > ...
> > 2015-12-19 23:38:34,355 INFO
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 37) [] Instance name: 'internal-authn', Extension name:
> > '"ovirt-engine-extension-aaa-jdbc".authn', Version:
'"1.0.1"', Notes:
> > 'Display name: "ovirt-engine-extension-aaa-jdbc"', License:
'ASL 2.0',
> > Home:
> > 'http://www.ovirt.org', Author 'The oVirt Project', Build
interface
> > Version:
> > '0', File:
'/etc/ovirt-engine/extensions.d/internal-authn.properties',
> > Initialized: 'true'
> > 2015-12-19 23:38:34,355 INFO
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 37) [] Instance name: 'internal-authz', Extension name:
> > '"ovirt-engine-extension-aaa-jdbc".authz', Version:
'"1.0.1"', Notes:
> > 'Display name: "ovirt-engine-extension-aaa-jdbc"', License:
'ASL 2.0',
> > Home:
> > 'http://www.ovirt.org', Author 'The oVirt Project', Build
interface
> > Version:
> > '0', File:
'/etc/ovirt-engine/extensions.d/internal-authz.properties',
> > Initialized: 'true'
>
> On Sat, Dec 19, 2015 at 10:14 PM, Gianluca Cecchi
> <gianluca.cecchi(a)gmail.com> wrote:
> > On Sat, Dec 19, 2015 at 8:57 PM, Gianluca Cecchi
> > <gianluca.cecchi(a)gmail.com>
> > wrote:
> >>
> >>
> >>
> >> but I don't understand how this can influence the fact that inside the
web
> >> ui login I don't see any selectable value for the profile field: the
> >> "internal" default domain is missing.... I didn't implement
any other
> >>
> >>
https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sha...
> >>
> >> Gianluca
> >
> >
> >
> > the culprit could be related to these lines in engine.log
> >
> > 2015-12-19 13:57:22,403 INFO
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 41) [] Extension 'internal-authn' loaded
> > 2015-12-19 13:57:22,406 INFO
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 41) [] Loading extension 'internal-authz'
> > 2015-12-19 13:57:22,408 INFO
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 41) [] Extension 'internal-authz' loaded
> > 2015-12-19 13:57:22,409 INFO
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 41) [] Initializing extension 'internal-authn'
> > 2015-12-19 13:57:22,447 ERROR
> > [org.ovirt.engine.extension.aaa.jdbc.binding.api.AuthnExtension]
> > (ServerService Thread Pool -- 41) [] Unexpected Exception invoking:
> > EXTENSION_INITIALIZE[e5ae1b7f-9104-4f23-a444-7b9175ff68d2]
> > 2015-12-19 13:57:22,447 ERROR
> > [org.ovirt.engine.core.extensions.mgr.ExtensionsManager] (ServerService
> > Thread Pool -- 41) [] Error in activating extension 'internal-authn':
> > Database schema is older than required by currently installed
> > ovirt-engine-extension-aaa-jdbc package version. Please upgrade profile
> > database schema before proceeding (for more info about upgrade please take
> > a
> > look at README.admin file contained in ovirt-engine-extension-aaa-jdbc
> > package).
>
> README.admin there [1] says, among other things:
> ===================================================================
> IV. Upgrading 'internal' profile
>
> ATTENTION: aaa-jdbc extension is not upgraded automatically during oVirt
> engine upgrade and it needs to be upgraded manually!
> ...
> stop engine
> ...
> yum update extension package
> ...
> engine-setup
> ===================================================================
>
> So you should run engine-setup after you update this package.
>
> Martin - is this intentional? Why not update the package automatically
> during engine-setup?
>
> Or even version-lock it? I do not think people should expect their engine
> to not allow logins after they run 'yum update'. Adding also Sandro.
Hi,
there are several reasons for this:
1. aaa-jdbc is an engine 3.6 extension, engine requires its presence to
provide 'internal' domain but it doesn't require any specific version,
so users may update aaa-jdbc independently on engine if they need
features provided provided by new version
2. engine-setup automatically configures/upgrades 'internal' domain, but
users may define manually other domains (as described in README.admin)
and those domains are not touched by engine-setup at all
3. Due to 1. and 2. we decided not to define version specific requirement
between engine and aaa-jdbc in engine-setup (same behaviour as already
exists for other engine extensions). So users may for example upgrade
engine, but leave aaa-jdbc as is or leave engine as is and upgrade
aaa-jdbc if they need it. Users just need to get used to read doc
before doing upgrade.
Now filed: https://bugzilla.redhat.com/show_bug.cgi?id=1293338
Best,
--
Didi
3:52 p.m.
On Mon, Dec 21, 2015 at 2:10 PM, Yedidyah Bar David wrote:
On Sun, Dec 20, 2015 at 9:50 PM, Martin Perina wrote:
>
>
[snip]
>>
>> So you should run engine-setup after you update this package.
>>
>> Martin - is this intentional? Why not update the package automatically
>> during engine-setup?
>>
>> Or even version-lock it? I do not think people should expect their
engine
>> to not allow logins after they run 'yum update'. Adding also Sandro.
>
> Hi,
>
> there are several reasons for this:
>
> 1. aaa-jdbc is an engine 3.6 extension, engine requires its presence to
> provide 'internal' domain but it doesn't require any specific
version,
> so users may update aaa-jdbc independently on engine if they need
> features provided provided by new version
>
> 2. engine-setup automatically configures/upgrades 'internal' domain, but
> users may define manually other domains (as described in README.admin)
> and those domains are not touched by engine-setup at all
>
> 3. Due to 1. and 2. we decided not to define version specific requirement
> between engine and aaa-jdbc in engine-setup (same behaviour as already
> exists for other engine extensions). So users may for example upgrade
> engine, but leave aaa-jdbc as is or leave engine as is and upgrade
> aaa-jdbc if they need it. Users just need to get used to read doc
> before doing upgrade.
Now filed: https://bugzilla.redhat.com/show_bug.cgi?id=1293338
Best,
--
Didi
Thanks, I gave my contribute inside the bugzilla.
I personally felt this behavior could potentially break many oVirt and
possibly RHEV installations based on the internal profile and your action
seems to confirm it.
As a user I disagree with Martin point in 3. as I'm usually inclined to
read the docs but not all the READMEs provided by any single package in the
system. I didn't find a clear reference to this step inside the oVirt web
documentation, but I could be wrong. I rememebr about it only when I played
with FreeIPA authentication in oVirt, but not in internal usage.
But if this problem can become an opportunity to make both docs and users
better entities it's not a problem for me...
Gianluca
5:29 p.m.
On Mon, Dec 21, 2015 at 3:52 PM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Mon, Dec 21, 2015 at 2:10 PM, Yedidyah Bar David wrote:
> On Sun, Dec 20, 2015 at 9:50 PM, Martin Perina wrote:
> >
> >
>
[snip]
> >>
> >> So you should run engine-setup after you update this package.
> >>
> >> Martin - is this intentional? Why not update the package automatically
> >> during engine-setup?
> >>
> >> Or even version-lock it? I do not think people should expect their
> engine
> >> to not allow logins after they run 'yum update'. Adding also
Sandro.
> >
> > Hi,
> >
> > there are several reasons for this:
> >
> > 1. aaa-jdbc is an engine 3.6 extension, engine requires its presence to
> > provide 'internal' domain but it doesn't require any specific
> version,
> > so users may update aaa-jdbc independently on engine if they need
> > features provided provided by new version
> >
> > 2. engine-setup automatically configures/upgrades 'internal' domain,
but
> > users may define manually other domains (as described in
> README.admin)
> > and those domains are not touched by engine-setup at all
> >
> > 3. Due to 1. and 2. we decided not to define version specific
> requirement
> > between engine and aaa-jdbc in engine-setup (same behaviour as
> already
> > exists for other engine extensions). So users may for example upgrade
> > engine, but leave aaa-jdbc as is or leave engine as is and upgrade
> > aaa-jdbc if they need it. Users just need to get used to read doc
> > before doing upgrade.
>
> Now filed: https://bugzilla.redhat.com/show_bug.cgi?id=1293338
>
> Best,
> --
> Didi
>
Thanks, I gave my contribute inside the bugzilla.
I personally felt this behavior could potentially break many oVirt and
possibly RHEV installations based on the internal profile and your action
seems to confirm it.
As a user I disagree with Martin point in 3. as I'm usually inclined to
read the docs but not all the READMEs provided by any single package in the
system. I didn't find a clear reference to this step inside the oVirt web
documentation, but I could be wrong. I rememebr about it only when I played
with FreeIPA authentication in oVirt, but not in internal usage.
But if this problem can become an opportunity to make both docs and users
better entities it's not a problem for me...
Gianluca
In the mean time I was "able" to solve the problems following what already
asked some days ago:
http://lists.ovirt.org/pipermail/users/2015-December/036601.html
- verified no tasks on hypervisor as what found in business_entity_snapshot
are failed attempts to import hosted engine storage domain
[root@ractor ~]# vdsClient -s 0 getAllTasksStatuses
{'status': {'message': 'OK', 'code': 0},
'allTasksStatus': {}}
- stop engine
systemctl stop ovirt-engine
- delete on db
engine=# delete from business_entity_snapshot ;
DELETE 3
engine=# commit;
COMMIT
engine=# exit
engine-# \q
-bash-4.2$ exit
logout
- start engine
systemctl start engine
- update ovirt-engine-extension-aaa-jdbc
---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.1-1.el7 will be
updated
---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.4-1.el7 will be
an update
- engine-setup now completes ok
(based on /usr/share/doc/ovirt-engine-extension-aaa-jdbc-1.0.4/README.admin
as I have only internal profile)
[root@ractorshe ovirt-engine]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
'/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151222171311-pad6e4.log
Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos)
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
--== PACKAGES ==--
[ INFO ] Checking for product updates...
[ INFO ] No product updates found
--== ALL IN ONE CONFIGURATION ==--
--== NETWORK CONFIGURATION ==--
[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be
resolved only locally
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]: Yes
[ INFO ] firewalld will be configured as firewall manager.
[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be
resolved only locally
[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be
resolved only locally
--== DATABASE CONFIGURATION ==--
--== OVIRT ENGINE CONFIGURATION ==--
--== STORAGE CONFIGURATION ==--
--== PKI CONFIGURATION ==--
--== APACHE CONFIGURATION ==--
--== SYSTEM CONFIGURATION ==--
--== MISC CONFIGURATION ==--
--== END OF CONFIGURATION ==--
[ INFO ] Stage: Setup validation
During execution engine service will be stopped (OK, Cancel)
[OK]:
[ INFO ] Cleaning stale zombie tasks and commands
--== CONFIGURATION PREVIEW ==--
Default SAN wipe after delete : False
Firewall manager : firewalld
Update Firewall : True
Host FQDN : ractorshe.my.domain
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
Engine installation : True
PKI organization : my.domain
Configure VMConsole Proxy : True
Engine Host FQDN : ractorshe.my.domain
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 websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Backing up database localhost:engine to
'/var/lib/ovirt-engine/backups/engine-20151222171352.J1P6M4.dump'.
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating/refreshing Engine 'internal' domain database schema
[ INFO ] Upgrading 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 ==--
SSH fingerprint: 19:56:8d:3e:50:fc:90:37:5a:ba:6c:57:30:b1:7d:93
Internal CA
DA:E6:04:34:99:A0:DB:CE:3F:0A:7B:A2:96:67:4C:7F:19:CA:95:5F
Note! If you want to gather statistical information you can
install Reports and/or DWH:
http://www.ovirt.org/Ovirt_DWH
http://www.ovirt.org/Ovirt_Reports
Web access is enabled at:
http://ractorshe.my.domain:80/ovirt-engine
https://ractorshe.my.domain:443/ovirt-engine
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting ovirt-vmconsole proxy service
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151222171311-pad6e4.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20151222171439-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
- Test with success login to webadmin portal with admin@internal and lates
ovirt-engine-extension-aaa-jdbc applied
Gianluca
6:21 p.m.
On Tue, Dec 22, 2015 at 5:29 PM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Mon, Dec 21, 2015 at 3:52 PM, Gianluca Cecchi <
gianluca.cecchi(a)gmail.com> wrote:
> On Mon, Dec 21, 2015 at 2:10 PM, Yedidyah Bar David wrote:
>
>> On Sun, Dec 20, 2015 at 9:50 PM, Martin Perina wrote:
>> >
>> >
>>
>
> [snip]
>
>
>> >>
>> >> So you should run engine-setup after you update this package.
>> >>
>> >> Martin - is this intentional? Why not update the package automatically
>> >> during engine-setup?
>> >>
>> >> Or even version-lock it? I do not think people should expect their
>> engine
>> >> to not allow logins after they run 'yum update'. Adding also
Sandro.
>> >
>> > Hi,
>> >
>> > there are several reasons for this:
>> >
>> > 1. aaa-jdbc is an engine 3.6 extension, engine requires its presence to
>> > provide 'internal' domain but it doesn't require any
specific
>> version,
>> > so users may update aaa-jdbc independently on engine if they need
>> > features provided provided by new version
>> >
>> > 2. engine-setup automatically configures/upgrades 'internal'
domain,
>> but
>> > users may define manually other domains (as described in
>> README.admin)
>> > and those domains are not touched by engine-setup at all
>> >
>> > 3. Due to 1. and 2. we decided not to define version specific
>> requirement
>> > between engine and aaa-jdbc in engine-setup (same behaviour as
>> already
>> > exists for other engine extensions). So users may for example
>> upgrade
>> > engine, but leave aaa-jdbc as is or leave engine as is and upgrade
>> > aaa-jdbc if they need it. Users just need to get used to read doc
>> > before doing upgrade.
>>
>> Now filed: https://bugzilla.redhat.com/show_bug.cgi?id=1293338
>>
>> Best,
>> --
>> Didi
>>
>
> Thanks, I gave my contribute inside the bugzilla.
> I personally felt this behavior could potentially break many oVirt and
> possibly RHEV installations based on the internal profile and your action
> seems to confirm it.
> As a user I disagree with Martin point in 3. as I'm usually inclined to
> read the docs but not all the READMEs provided by any single package in the
> system. I didn't find a clear reference to this step inside the oVirt web
> documentation, but I could be wrong. I rememebr about it only when I played
> with FreeIPA authentication in oVirt, but not in internal usage.
> But if this problem can become an opportunity to make both docs and users
> better entities it's not a problem for me...
> Gianluca
>
>
In the mean time I was "able" to solve the problems following what already
asked some days ago:
http://lists.ovirt.org/pipermail/users/2015-December/036601.html
It just happened another time to me so it seams quite systematic and it's
worth to open a bug on it:
https://bugzilla.redhat.com/show_bug.cgi?id=1293689
- verified no tasks on hypervisor as what found in
business_entity_snapshot are failed attempts to import hosted engine
storage domain
[root@ractor ~]# vdsClient -s 0 getAllTasksStatuses
{'status': {'message': 'OK', 'code': 0},
'allTasksStatus': {}}
- stop engine
systemctl stop ovirt-engine
- delete on db
engine=# delete from business_entity_snapshot ;
DELETE 3
engine=# commit;
COMMIT
engine=# exit
engine-# \q
-bash-4.2$ exit
logout
- start engine
systemctl start engine
- update ovirt-engine-extension-aaa-jdbc
---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.1-1.el7 will be
updated
---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.4-1.el7 will be
an update
- engine-setup now completes ok
(based
on /usr/share/doc/ovirt-engine-extension-aaa-jdbc-1.0.4/README.admin as I
have only internal profile)
[root@ractorshe ovirt-engine]# engine-setup
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
'/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
Log file:
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151222171311-pad6e4.log
Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos)
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
--== PACKAGES ==--
[ INFO ] Checking for product updates...
[ INFO ] No product updates found
--== ALL IN ONE CONFIGURATION ==--
--== NETWORK CONFIGURATION ==--
[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be
resolved only locally
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]: Yes
[ INFO ] firewalld will be configured as firewall manager.
[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be
resolved only locally
[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be
resolved only locally
--== DATABASE CONFIGURATION ==--
--== OVIRT ENGINE CONFIGURATION ==--
--== STORAGE CONFIGURATION ==--
--== PKI CONFIGURATION ==--
--== APACHE CONFIGURATION ==--
--== SYSTEM CONFIGURATION ==--
--== MISC CONFIGURATION ==--
--== END OF CONFIGURATION ==--
[ INFO ] Stage: Setup validation
During execution engine service will be stopped (OK, Cancel)
[OK]:
[ INFO ] Cleaning stale zombie tasks and commands
--== CONFIGURATION PREVIEW ==--
Default SAN wipe after delete : False
Firewall manager : firewalld
Update Firewall : True
Host FQDN : ractorshe.my.domain
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
Engine installation : True
PKI organization : my.domain
Configure VMConsole Proxy : True
Engine Host FQDN : ractorshe.my.domain
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 websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Backing up database localhost:engine to
'/var/lib/ovirt-engine/backups/engine-20151222171352.J1P6M4.dump'.
[ INFO ] Creating/refreshing Engine database schema
[ INFO ] Creating/refreshing Engine 'internal' domain database schema
[ INFO ] Upgrading 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 ==--
SSH fingerprint: 19:56:8d:3e:50:fc:90:37:5a:ba:6c:57:30:b1:7d:93
Internal CA
DA:E6:04:34:99:A0:DB:CE:3F:0A:7B:A2:96:67:4C:7F:19:CA:95:5F
Note! If you want to gather statistical information you can
install Reports and/or DWH:
http://www.ovirt.org/Ovirt_DWH
http://www.ovirt.org/Ovirt_Reports
Web access is enabled at:
http://ractorshe.my.domain:80/ovirt-engine
https://ractorshe.my.domain:443/ovirt-engine
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ INFO ] Restarting ovirt-vmconsole proxy service
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20151222171311-pad6e4.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20151222171439-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
- Test with success login to webadmin portal with admin@internal and
lates ovirt-engine-extension-aaa-jdbc applied
Gianluca
3354
days inactive
3357
days old
12 comments
5 participants
participants (5)
-
Gianluca Cecchi -
Martin Perina -
Oved Ourfali -
Simone Tiraboschi -
Yedidyah Bar David