Bug 1368030 - Upgrade manager: log for failure is not well phrased: with message 'java.nio.channels.UnresolvedAddressException'."
Summary: Upgrade manager: log for failure is not well phrased: with message 'java.nio....
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.0.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0
Assignee: Ravi Nori
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-18 07:32 UTC by Yaniv Kaul
Modified: 2017-02-15 14:52 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-15 14:52:54 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
mperina: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 63546 0 master MERGED core : Upgrade manager: log for failure is not well phrased 2020-02-17 11:33:11 UTC

Description Yaniv Kaul 2016-08-18 07:32:42 UTC 
Description of problem:
Seen on RHEV.TLV right now:
"Failed to check for available updates on host monster01 with message 'java.nio.channels.UnresolvedAddressException'."

Version-Release number of selected component (if applicable):
4.0.1.1-0.1.el7ev

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Perina 2016-08-19 05:21:22 UTC 
Ravi, please take a look how we can make such errors more understandable to users
Comment 2 Ravi Nori 2016-09-08 14:40:28 UTC 
When exception message is null the code uses the root cause resulting in the message seen above.

Pushed a patch to add more debug log messages when such a situation occurs so the user can debug the issue using the stacktrace in the logs.
Comment 3 Sandro Bonazzola 2016-12-12 13:56:21 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Comment 4 Jiri Belka 2017-02-01 10:54:55 UTC 
Are there any user-doable reproduceable steps withough modifying the code? Thx.
Comment 5 Ravi Nori 2017-02-07 13:49:33 UTC 
Turning of a host should be sufficient to verify this BZ. In the logs UnresolvedAddressException should no longer appear for the host when Upgrade check is invoked. Instead there should be additional messages in the debug log about the exception.
Comment 6 Jiri Belka 2017-02-08 15:50:51 UTC 
ok, based on descr in #5

ovirt-engine-4.1.0.4-0.1.el7.noarch
Note You need to log in before you can comment on or make changes to this bug.