Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1145127

Summary: [TEXT] SetStoragePoolStatus needs a human readable message under Tasks pane
Product: [oVirt] ovirt-engine Reporter: Gilad Lazarovich <glazarov>
Component: Frontend.WebAdminAssignee: Idan Shaby <ishaby>
Status: CLOSED WORKSFORME QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: low    
Version: 3.5.0CC: acanan, amureini, bugs, ecohen, gklein, glazarov, ishaby, laravot, lsurette, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon, ylavi
Target Milestone: ovirt-3.6.2Keywords: EasyFix
Target Release: 3.6.2Flags: ylavi: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-14 07:26:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
SetStoragePoolStatus showing up under the Tasks pane none

Description Gilad Lazarovich 2014-09-22 12:35:52 UTC
Created attachment 939985 [details]
SetStoragePoolStatus showing up under the Tasks pane

Description of problem:
SetStoragePoolStatus needs a human readable message under Tasks pane.  Here's a snippet from the engine.log that shows there is no message available:
2014-09-22 10:52:25,846 WARN  [org.ovirt.engine.core.dal.job.ExecutionMessageDirector] (org.ovirt.thread.pool-6-thread-44) [3f24acdb] The message key SetStoragePoolStatus is missing from bundles/ExecutionMessages

Version-Release number of selected component (if applicable):
3.5 vt3.1

How reproducible:
100%

Additional info:
This comes up when the SPM host is rebooted.  See the attached screenshot

Comment 1 Sandro Bonazzola 2015-10-26 12:42:44 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 2 Idan Shaby 2015-10-27 13:31:50 UTC
Hi Gilad,
Please add detailed steps to reproduce. I can't reproduce this bug.
Thanks

Comment 3 Gilad Lazarovich 2015-11-02 13:40:29 UTC
Hi Idan,
A restart of the SPM was the only step needed here.  I tried and this no longer reproduces, there is no storage related task now, just a reconnect for the non-responding host.  This is likely related to the decommissioning of the storage pool metadata (perhaps Federico Simoncelli or Liron Aravot would know).

Comment 4 Allon Mureinik 2015-11-11 09:39:07 UTC
This has nothing to do with the sp metadata. This command is simply called when an SP status changes.

Comment 5 Red Hat Bugzilla Rules Engine 2015-12-02 00:13:26 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 Red Hat Bugzilla Rules Engine 2015-12-02 00:13:26 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 7 Idan Shaby 2015-12-14 07:26:30 UTC
Actually, the fix is redundant if the bug can't be reproduced.