Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
RHEVM crashed when upgraded rhevh on it
Version-Release number of selected component (if applicable):
rhevm-3.1.0-16.el6ev.noarch.rpm
How reproducible:
Always
Steps to Reproduce:
1. Install rhevm-3.1.0-16.el6ev.noarch.rpm
2. upgrade rhevh6.2 to rhev-hypervisor6-6.3-20120913.0.el6_3 via RHEVM
3. This could not be fixed by re-login or restart RHEVM
Actual results:
RHEVM jump to error page as attached figure shows.
Log 'more information' was provided. see attached as well.
Expected results:
rhevh should be upgrade successfully without error message
Additional info:
exception from log:
Startup URI: http://rhevm-ic-104-240.rhevm.englab.nay.redhat.com:8080/RHEVManager/WPFClient.xbap
Application Identity: http://rhevm-ic-104-240.rhevm.englab.nay.redhat.com:8080/RHEVManager/WPFClient.xbap#WPFClient.xbap, Version=4.6.0.52, Culture=neutral, PublicKeyToken=6673332c7e4bb4b7, processorArchitecture=msil/WPFClient.exe, Version=4.6.0.52, Culture=neutral, PublicKeyToken=6673332c7e4bb4b7, processorArchitecture=msil, type=win32
System.ArgumentException: Version string portion was too short or too long.
at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)
at org.ovirt.engine.ui.uicommon.models.hosts.HostGeneralModel.GetVersionFromOS(String os)
at org.ovirt.engine.ui.uicommon.models.hosts.HostGeneralModel.Install()
at org.ovirt.engine.ui.uicommon.models.hosts.HostGeneralModel.ExecuteCommand(UICommand command)
at org.ovirt.engine.ui.uicommon.UICommand.Execute(Object parameter)
Thanks for the information.
I was able to reproduce and see this happens due to the addition of the rhev31
part in the version, and it may only happen on WPF code.
Can you please verify this does not happen in rhevm 3.1?