Bug 915028 - [RHEVM] Failed upgrade RHEVM with remote DB installation
Summary: [RHEVM] Failed upgrade RHEVM with remote DB installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.2.0
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: 3.2.0
Assignee: Alex Lourie
QA Contact: Leonid Natapov
URL:
Whiteboard: integration
Depends On:
Blocks: 915779 917401
TreeView+ depends on / blocked
 
Reported: 2013-02-24 09:10 UTC by vvyazmin@redhat.com
Modified: 2015-09-22 13:09 UTC (History)
13 users (show)

Fixed In Version: sf-9
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 915779 (view as bug list)
Environment:
Last Closed:
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
## Logs engine-upgrade (25.48 KB, application/octet-stream)
2013-02-24 09:10 UTC, vvyazmin@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 12381 0 None None None Never

Description vvyazmin@redhat.com 2013-02-24 09:10:20 UTC
Created attachment 701953 [details]
## Logs engine-upgrade

Description of problem: Failed upgrade RHEVM with remote DB installation


Version-Release number of selected component (if applicable):
RHEVM 3.2 - SF07 environment:

RHEVM: rhevm-3.2.0-8.el6ev.noarch
VDSM: vdsm-4.10.2-8.0.el6ev.x86_64
LIBVIRT: libvirt-0.10.2-18.el6.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
SANLOCK: sanlock-2.6-2.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create RHEVM environment with remote DB installation
2. Upgrade RHEVM 3.2 from SF07 to SF08
  
Actual results:
Failed upgrade RHEVM, because upgrade action think that DB install locally 

Expected results:
Succeed  upgrade RHEVM

Additional info:

/var/log/ovirt-engine/ovirt-engine-upgrade_2013_02_24_10_15_25.log

psql: could not connect to server: Connection refused
        Is the server running on host "localhost" and accepting
        TCP/IP connections on port 5432?
could not create socket: Address family not supported by protocol

2013-02-24 10:15:52:EBUG::common_utils::475::root:: retcode = 0
2013-02-24 10:15:52:EBUG::common_utils::435::root:: Executing command --> '/usr/share/ovirt-engine/scripts/taskcleaner/taskcleaner.sh -u postgres -d engine -z -R -C -J -q' in working directory '/'
2013-02-24 10:15:52:EBUG::common_utils::473::root:: output =
2013-02-24 10:15:52:EBUG::common_utils::474::root:: stderr = psql: could not connect to server: Connection refused
        Is the server running on host "localhost" and accepting
        TCP/IP connections on port 5432?
could not create socket: Address family not supported by protocol
psql: could not connect to server: Connection refused
        Is the server running on host "localhost" and accepting
        TCP/IP connections on port 5432?
could not create socket: Address family not supported by protocol

2013-02-24 10:15:52:EBUG::common_utils::475::root:: retcode = 0
2013-02-24 10:15:52:EBUG::rhevm-upgrade::852::root:: Checking active system tasks
2013-02-24 10:15:52:EBUG::common_utils::435::root:: Executing command --> '/usr/bin/psql -U postgres -f /usr/share/ovirt-engine/scripts/add_fn_db_get_async_tasks_function.sql -d engine' in working directory '/'
2013-02-24 10:15:52:EBUG::common_utils::473::root:: output =
2013-02-24 10:15:52:EBUG::common_utils::474::root:: stderr = psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

2013-02-24 10:15:52:EBUG::common_utils::475::root:: retcode = 2
2013-02-24 10:15:52:EBUG::common_utils::1264::root:: Service was not stopped. there for we're not starting it





/var/log/ovirt-engine/engine.log

/var/log/vdsm/vdsm.log

Comment 4 Leonid Natapov 2013-03-05 14:32:01 UTC
sf9. fixed.

Comment 5 Itamar Heim 2013-06-11 08:44:13 UTC
3.2 has been released

Comment 6 Itamar Heim 2013-06-11 08:44:14 UTC
3.2 has been released

Comment 7 Itamar Heim 2013-06-11 08:44:45 UTC
3.2 has been released

Comment 8 Itamar Heim 2013-06-11 08:50:50 UTC
3.2 has been released

Comment 9 Itamar Heim 2013-06-11 09:21:51 UTC
3.2 has been released


Note You need to log in before you can comment on or make changes to this bug.