Bug 1004675 - [Admin Portal] Attempt to add a 3.2 host into 3.3 env fails but the host cannot be removed
[Admin Portal] Attempt to add a 3.2 host into 3.3 env fails but the host cann...
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: 3.3.0
Assigned To: Ravi Nori
Tareq Alayan
: Triaged
Depends On:
Blocks: 881055
  Show dependency treegraph
Reported: 2013-09-05 04:07 EDT by Jiri Belka
Modified: 2016-02-10 14:41 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
engine.log, server.log, vdsm.log (100.00 KB, application/x-tar)
2013-09-05 04:07 EDT, Jiri Belka
no flags Details
logs.tar.gz (846.62 KB, application/gzip)
2013-11-14 12:34 EST, Tareq Alayan
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 19301 None None None Never
oVirt gerrit 19483 None None None Never
oVirt gerrit 19543 None None None Never

  None (edit)
Description Jiri Belka 2013-09-05 04:07:54 EDT
Created attachment 794070 [details]
engine.log, server.log, vdsm.log

Description of problem:

I tried to add second host into 3.3 setup (is13). This host is 3.2 with sf20.1. The atempt to add this host fails and the host is in 'Non Operational' state in Admin Portal. I cannot remove this host as neither 'Remove' nor 'Maintenance' buttons/actions are active, thus I cannot do anything with this host.

While adding this host there's following event:

2013-Sep-05, 09:49
Host dell-r210ii-03 is compatible with versions (3.0,3.1,3.2) and cannot join Cluster Default which is set to version 3.3.

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

How reproducible:

Steps to Reproduce:
1. is13 setup with 3.3 host and nfs storage
2. add 3.2 host (sf20.1)
3. try to delete 3.2 host

Actual results:
3.2 host is in 'Non Operational' state and cannot be deleted from the setup

Expected results:
if adding a host fails it should be always possible to remove such host

Additional info:
Comment 1 Tareq Alayan 2013-11-14 12:34:32 EST
Created attachment 824076 [details]
Comment 2 Tareq Alayan 2013-11-14 12:38:14 EST
tested on rhevm-3.3.0-0.33.beta1.el6ev.noarch

failed qa. reassigning.

add 3.2 vdsm to 3.3 engine to DC with 3.3 compatibility mode.
the host becane non operational. 
remove button was disabled.
Maintanece buttom was enabled. I pressed to put host into maintenance it stayed in preparing for maintenance and didn't move to maintence state.  

log.tar.gz attached.
Comment 3 Ravi Nori 2013-11-14 12:45:02 EST
The problem reported in FailedQA is different from the original bug. The original bug was that both maintenance and remove buttons were disabled, the new problem is that the host doesn't move to maintenance after clicking the maintenance button.

Is this 100% reproducible
Comment 4 Barak 2013-11-18 03:57:41 EST
Per comment #14 moving this bug back to ON_QA.

And opened a different bug on the different issue reported on comment #2 
Bug 1031536
Comment 5 Tareq Alayan 2013-11-21 06:21:41 EST
verified on rhevm-3.3.0-0.33.beta1.el6ev.noarch

1. Create 3.3 DC and Cluster
2. Add 3.3 host (vdsm from is23.1)
3. Setup NFS storage on DC
5. Add 3.2 host (vdsm from sf21.1)
6. After installation 3.2 host became Non-operational
7. Move 3.2 host to Maintenance -> host successfully moved to Maintenance
8. remove 3.2 host ---OK
Comment 6 Itamar Heim 2014-01-21 17:31:23 EST
Closing - RHEV 3.3 Released
Comment 7 Itamar Heim 2014-01-21 17:31:24 EST
Closing - RHEV 3.3 Released
Comment 8 Itamar Heim 2014-01-21 17:34:08 EST
Closing - RHEV 3.3 Released

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