Bug 1645174
| Summary: | Reimporting the existing CV version should have more refined validation message | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jitendra Yejare <jyejare> |
| Component: | Inter Satellite Sync | Assignee: | Chris Roberts <chrobert> |
| Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5.0 | CC: | bkearney, chrobert, egolov, ehelms, zhunting |
| Target Milestone: | 6.5.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://projects.theforeman.org/issues/25932 | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-katello-3.10.0,tfm-rubygem-hammer_cli_katello-0.16.0.6-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:38:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1644596 | ||
|
Description
Jitendra Yejare
2018-11-01 14:24:16 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24569 has been resolved. need to make a new upstream issue for this The validation message is fixed, but still, satellite tries to resync the repositories(recreation of symlinks I believe) and while publishing it throws a message. It would be great if we throw this message to user, even before resyncing(recreating symlink) and by first checking what version it is going to import and match with the existing one. This will save the users time. Logs may help here, what I wanted to say : ``` # hammer content-view version import --organization-id 19 --export-tar /var/lib/pulp/katello-export/export-30.tar [................................................................................................] [100%] No new packages. Could not import the content view.: A CV version already exists with the same major and minor version (1.0) ``` If you see above, first it resynced and then throw the message. It would be good if we throw the message first and abort resyncing. After talking to beav about this and i will make a pr to move the check first so we dont try to resync I will use the same redmine issue and just create a 'Refs' PR Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25406 has been resolved. @Toledo, Even after the fix, the behavior from hammer looks same: # hammer -u admin -p changeme content-view version import --export-tar /var/lib/pulp/katello-export/export-cvexpo_cv-401.tar --organization-id 304 [................................................................................................] [100%] No new packages. Could not import the content view.: A CV version already exists with the same major and minor version (1.0) So if have fixed resyncing of repo, Can we have somehow remove the progress bar. As per discussion with DEV on irc ... moving this back to the assigned state. Verified! As per Comment 5 and comment 9, I verified the said part in a comment. The first part is already verified in comment 5. Steps: Same as per bug description Behavior(Expected): The validation message is only shown and the re-sync is avoided: # hammer content-view version import --export-tar /var/lib/pulp/katello-export/export-custom_cv-10.tar --organization-id 3 Could not import the content view: Error: The latest version (1.0) of the Content View 'custom_cv' is greater or equal to the version you are trying to import (1.0) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222 |