Bug 1073487 - Upgrade from 3.3.4 to 3.4 RC failed
Summary: Upgrade from 3.3.4 to 3.4 RC failed
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.4
Hardware: Unspecified
OS: Linux
urgent
high
Target Milestone: ---
: 3.4.0
Assignee: Alon Bar-Lev
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 14:11 UTC by Eli Mesika
Modified: 2014-03-10 12:57 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-10 12:57:59 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
Log file (193.52 KB, text/x-log)
2014-03-06 14:12 UTC, Eli Mesika
no flags Details

Description Eli Mesika 2014-03-06 14:11:14 UTC
Description of problem:
Upgrade from 3.3.4 to 3.4 RC failed 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. install ovirt-engine with the following repo
[ovirt-3.3.4]
name=oVirt 3.3.4 release
baseurl=http://ovirt-mirror.eng.lab.tlv.redhat.com/releases/3.3.4/rpm/EL/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0

2. Installation succeeded 
3. Run engine-setup
4. engine-setup completes OK (test by opening webadmin)
5. set enabled=0 for the repo definition in 1)
6. Add another entry to this repo :
[ovirt-3.4.0-prerelease]
name=Pre release builds of the oVirt 3.4 project
#baseurl=http://resources.ovirt.org/releases/3.4.0_pre/rpm/EL/$releasever/
baseurl=http://ovirt-mirror.eng.lab.tlv.redhat.com/releases/3.4.0_pre/rpm/EL/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0
7. run : yum update ovirt-engine-setup
8. run engine-setup


[root@localhost yum.repos.d]# engine-setup 
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
          Configuration files: ['/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-20140306085756.log
          Version: otopi-1.2.0_beta (otopi-1.2.0-0.1.beta.el6)
[ 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...
          Setup has found updates for some packages, do you wish to update them now? (Yes, No) [Yes]: 
[ INFO  ] Checking for an update for Setup...
          Setup will not be able to rollback new packages in case of a failure, because installed ones were not found in enabled repositories.
          Do you want to abort Setup? (Yes, No) [Yes]: 
[ ERROR ] Failed to execute stage 'Environment customization': Package rollback information is unavailable
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140306085756.log
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed



Actual results:
Upgrade from 3.3.4 to 3.4 fails

Expected results:
Upgrade from 3.3.4 to 3.4 should succeed 

Additional info:

log file

Comment 1 Eli Mesika 2014-03-06 14:12:28 UTC
Created attachment 871469 [details]
Log file

Comment 2 Eli Mesika 2014-03-06 14:18:29 UTC
Additional comment for bug description :

I had a VM made from a template that already installed 3.4 on CentOS so my first step before getting to 1) was 

0) yum remove ovirt-* -y

Comment 3 Eli Mesika 2014-03-06 14:33:40 UTC
repeating the same scenario with step 6) from bug description installing the 3.4 beta worked without any problem :

[ovirt-3.4.0-Beta-2-tlv-mirror]
name=Beta 2 tlv mirror for the oVirt 3.4 project
baseurl=http://ovirt-mirror.eng.lab.tlv.redhat.com/releases/3.4.0-beta2/rpm/EL/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0

Comment 4 Sandro Bonazzola 2014-03-06 14:34:43 UTC
You aborted setup...

Comment 5 Sandro Bonazzola 2014-03-06 14:35:08 UTC
          Do you want to abort Setup? (Yes, No) [Yes]: 
[ ERROR ] Failed to execute stage 'Environment customization': Package rollback information is unavailable

Comment 6 Sandro Bonazzola 2014-03-06 14:42:06 UTC
Alon, seems like the dialog sent the question but aborted without waiting the answer. May it be an otopi bug?

Comment 7 Alon Bar-Lev 2014-03-06 14:48:25 UTC
(In reply to Sandro Bonazzola from comment #6)
> Alon, seems like the dialog sent the question but aborted without waiting
> the answer. May it be an otopi bug?

ha?!?! are you sure? where can I see this?

Comment 8 Sandro Bonazzola 2014-03-06 14:56:59 UTC
(In reply to Alon Bar-Lev from comment #7)
> (In reply to Sandro Bonazzola from comment #6)
> > Alon, seems like the dialog sent the question but aborted without waiting
> > the answer. May it be an otopi bug?
> 
> ha?!?! are you sure? where can I see this?

Eli said he didn't hit enter on 
Do you want to abort Setup? (Yes, No) [Yes]:

and in the attached logs I see the DIALOG:SEND but not the answer to the dialog.

Comment 9 Alon Bar-Lev 2014-03-06 15:00:33 UTC
(In reply to Sandro Bonazzola from comment #8)
> (In reply to Alon Bar-Lev from comment #7)
> > (In reply to Sandro Bonazzola from comment #6)
> > > Alon, seems like the dialog sent the question but aborted without waiting
> > > the answer. May it be an otopi bug?
> > 
> > ha?!?! are you sure? where can I see this?
> 
> Eli said he didn't hit enter on 
> Do you want to abort Setup? (Yes, No) [Yes]:
> 
> and in the attached logs I see the DIALOG:SEND but not the answer to the
> dialog.

we need a place to reproduce this, except of EOF/enter it should not happen, it is plain read from stdin.

eli, please try to reproduce, send machine details.

Comment 10 Eli Mesika 2014-03-09 09:22:46 UTC
(In reply to Alon Bar-Lev from comment #9)

> eli, please try to reproduce, send machine details.

Details provided via IRC

Comment 11 Alon Bar-Lev 2014-03-09 10:38:19 UTC
We cannot reproduce this in same machine that was left as-is.

Very strange.


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