Bug 1114657
| Summary: | yum packager is active while running with offline packager | ||
|---|---|---|---|
| Product: | [oVirt] otopi | Reporter: | rhev-integ |
| Component: | Plugins.packagers | Assignee: | Alon Bar-Lev <alonbl> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 1.0.0 | CC: | aberezin, acathrow, alonbl, bazulay, dougsland, iheim, lbopf, mkalinin, oourfali, pstehlik, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 1.3.0 | Flags: | alonbl:
devel_ack+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | infra | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
A fault introduced with "install while in version lock" caused offline packager, if it existed on the host during upgrade, to break. This issue has now been fixed.
|
Story Points: | --- |
| Clone Of: | 1112370 | Environment: | |
| Last Closed: | 2014-07-29 14:19:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1112370 | ||
| Bug Blocks: | |||
|
Comment 2
Jiri Belka
2014-07-16 13:48:51 UTC
Hi Jirji, This is what I did: (From bug description:) Steps to Reproduce: 1. Upgrade 3.2 version of rhevh. Even if take the latest 3.2 from RHN and do reinstall of the host with the same iso. 2. Remove the host from current rhevm. 3. Trying adding host to a new instance of RHEV-M (does not matter what rhevm - I tried on 3.2, 3.3, 3.4). Initiate this either from the TUI or from the Admin Portal->AddNewHost. Latest 3.2 hypervisor is available here: - rhev-hypervisor6-6.5-20140118.1.3.2.el6_5, available here: https://rhn.redhat.com/rhn/software/channel/downloads/Download.do?cid=12564 Let's check here the versioning you are talking about: https://mojo.redhat.com/docs/DOC-85835 you used: rhevh-6.4-20130528.0.el6_4 -> 3.2 GA and I see this: rhev-hypervisor6-6.5-20131204.0.3.2.el6_5 -> 3.2.4 but I was using: rhev-hypervisor6-6.5-20140118.1.3.2.el6_5 -> 3.2.6 I do not know why it does not reproduce on your setup - maybe you already have the fix? It reproduced here were steadily all the time. Try taking the version I used and do clean install on rhevm 3.4 GA. rhevh: 20140118.1.3.2.el6_5 rhevm 3.2: rhevm-3.2.6-0.50.el6ev.noarch rhevm 3.4: rhevm-3.4.0-0.21.el6ev.noarch (3.4 GA) 1. add host into rhevm 3.2 (successful) 2. maintenance (sucessful) 3. reinstalled with 20140118.1.3.2.el6_5 (same version) on rhevm 3.2 (successful) 4. maintenance & remove (successful) 5. attempt to add the host into clean rhevm 3.4 (3.2 DC/CL level) (successful) 6. host up without any issue qe is loosing time with experiments here... i cannot reproduce. provide _exact_ steps with all details (version, rhevm version, dc/cl level). fyi your steps are not very precise, you say "upgrade" (from which version to what? on which rhevm version)? also you state latest 3.2 hypervisor is rhev-hypervisor6-6.5-20140118.1.3.2.el6_5 which is wrong as Mojo pages displays rhev-hypervisor6-6.5-20140118.1.3.2.el6_5 (heartbleed fix) as latest version. in the end this BZ fixes otopi packages and there's no info about otopi packages at all. ok, verified with 20140118.1.3.2.el6_5 and rhevm 3.4 (otopi-1.2.2-1.el6ev.noarch). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0974.html |