Bug 1073487
| Summary: | Upgrade from 3.3.4 to 3.4 RC failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Eli Mesika <emesika> | ||||
| Component: | ovirt-engine-installer | Assignee: | Alon Bar-Lev <alonbl> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Pavel Stehlik <pstehlik> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 3.4 | CC: | acathrow, alonbl, didi, emesika, gklein, iheim, sbonazzo, s.kieske, yeylon | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | 3.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | integration | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-03-10 12:57:59 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Eli Mesika
2014-03-06 14:11:14 UTC
Created attachment 871469 [details]
Log file
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 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 You aborted setup... Do you want to abort Setup? (Yes, No) [Yes]: [ ERROR ] Failed to execute stage 'Environment customization': Package rollback information is unavailable Alon, seems like the dialog sent the question but aborted without waiting the answer. May it be an otopi bug? (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? (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. (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. (In reply to Alon Bar-Lev from comment #9) > eli, please try to reproduce, send machine details. Details provided via IRC We cannot reproduce this in same machine that was left as-is. Very strange. |