Bug 1323803 - WebAdmin: Host fedora_host2 cannot access the Storage Domain(s) <UNKNOWN> ...
Summary: WebAdmin: Host fedora_host2 cannot access the Storage Domain(s) <UNKNOWN> ...
Keywords:
Status: CLOSED DUPLICATE of bug 1222770
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Tal Nisan
QA Contact: Aharon Canan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 18:27 UTC by jniederm
Modified: 2016-04-05 08:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-05 08:36:46 UTC
oVirt Team: Storage
tnisan: ovirt-4.1?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
par of engine log (17.60 KB, text/plain)
2016-04-04 18:27 UTC, jniederm
no flags Details

Description jniederm 2016-04-04 18:27:30 UTC
Created attachment 1143412 [details]
par of engine log

Description of problem:
Message in Events (WebAdmin, very bottom) contains "<UNKNOWN>":Host fedora_host2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center Default. Setting Host state to Non-Operational.

Version-Release number of selected component (if applicable):
4.0 master, commit 4ffd5a4

How reproducible:
100% if you know how to the event

Steps to Reproduce:
1. ?, play with Storage

Actual results:
message ... Storage Domain(s) <UNKNOWN> ...

Expected results:
meaningful reference a particular storage domain

Additional info:
During debugging it turns out that:
SetNonOperationalVdsCommand.getStorageDomain() = null
SetNonOperationalVdsCommand.getStorageDomainId() = 00000000-0000-0000-0000-000000000000
SetNonOperationalVdsCommand.getStorageDomainName() = ""
SetNonOperationalVdsCommand.getCustomValues() = "storagepoolname" -> "Default"

Comment 1 Tal Nisan 2016-04-05 08:36:46 UTC

*** This bug has been marked as a duplicate of bug 1222770 ***


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