Bug 2187481

Summary: hammer command, `hammer content-export incremental version ` fails after a new version is published
Product: Red Hat Satellite Reporter: Benjamin Kielhold <bkielhol>
Component: Inter Satellite SyncAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: aruzicka, jpasqual, ofedoren, paji, sajha
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged, WorkAround
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:13:10 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:

Description Benjamin Kielhold 2023-04-17 17:45:02 UTC
Description of problem: 
~~~
  Attempting to export an incremental version of a content-view results with the following error output:
    ---
    Could not export the content view version:
      Missing arguments for '--id'.
    ---


Version-Release number of selected component (if applicable):
~~~
Satellite versions: 6.11 and 6.12


How reproducible:
~~~
100%


Steps to Reproduce:
~~~
1. Set the download policy to `immediate` for repository(s) to be used.
2. Create a CV with desired repository(s)
3. Publish/Promote the CV to the LCE
4. Execute the command to export the CV:

    # hammer content-export complete version --content-view-id=<id> --lifecycle-environment-id=<id>
[................................................................................................................] [100%]
Generated /var*

5. Publish new version of the CV
6. Execute the command to export the CV incrementally:

    # hammer content-export incremental version --content-view-id=<id> --lifecycle-environment-id=<id>

  ** Will be met with the below error even after verifying that all repositories are set to `immediate` DL policy**

    Could not export the content view version:
      Missing arguments for '--id'.


Actual results:
~~~

Example:

   // Exporting the complete initial version
   [root@sat ~]# hammer content-export complete version --content-view-id=19 --lifecycle-environment-id=1
[................................................................................................................] [100%]
Generated /var/lib/pulp/exports/Org/AnsibleDisconnnectedTest/1.0/2023-04-17T11-25-36-04-00/metadata.json


   // Attempting to export the CV incrementally
   # hammer content-export incremental version --content-view-id=19 --lifecycle-environment-id=1
Could not export the content view version:
  Missing arguments for '--id'.



Expected results:
~~~

# hammer content-export complete version --content-view-id=21 --lifecycle-environment-id=2
[.......................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/DefaultOrg/CVTest/1.0/2023-04-17T13-39-14-04-00/metadata.json

# hammer content-export incremental version --content-view-id=21 --lifecycle-environment-id=2
[.......................................................................................................................................................................] [100%]
Generated /var/lib/pulp/exports/DefaultOrg/CVTest/2.0/2023-04-17T13-39-47-04-00/metadata.json


Thanks,
Benjamin Kielhold

Comment 6 Eric Helms 2024-06-06 16:13:10 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.