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.
When updater.exe sucessfully obtain version.json, it stdout:
"new version file obtained [path] old version [int] new version [int]"
On network error it prints out "http/network error + real_error".
Maybe additional info to this network error is worthy
"http/network error + real_error. But file [path] already exists version [int]"
and
"http/network error + real_error. no old file [path] exists"
On addition IO error during saving should be catched. eg:
"new version obtained [version] but can not be saved [path] real_error"
if older version already exists, may be mentiond and even with [version]
Where real error may version.json already protected against writeing or dtarget directory can not be writteable at all.
the reason for path everywhere is that path contains NVR which may be hard to guess.
Initial report contained also need for stdoouted trace.json (if created)
But that got already fixed: https://github.com/ojdkbuild/contrib_update-notifier/commit/9635e80168f9e6a13621a347c5d28b3f91f94497
I think heaving similarly detailed error messages for it is overkill, but may be worthy.
(In reply to jiri vanek from comment #0)
> "http/network error + real_error. But file [path] already exists version
> [int]"
> and
> "http/network error + real_error. no old file [path] exists"
>
> On addition IO error during saving should be catched. eg:
> "new version obtained [version] but can not be saved [path] real_error"
> if older version already exists, may be mentiond and even with [version]
>
> Where real error may version.json already protected against writeing or
> dtarget directory can not be writteable at all.
I can add a "unified" postfix to error messages like this:
[err...]; local version, path: [<expected_or_actual_path>], version_number: [<actual_or_zero>]