Bug 1400624
| Summary: | capsule sync (after capsule ran out of disk-space) says: "wrong number of arguments (2 for 1)" | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jan Hutař <jhutar> |
| Component: | Foreman Proxy | Assignee: | Justin Sherrill <jsherril> |
| Status: | CLOSED ERRATA | QA Contact: | jcallaha |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.2.5 | CC: | bbuckingham, bkearney, jcallaha, pondrejk, psuriset |
| Target Milestone: | Unspecified | Keywords: | Performance, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-katello-3.0.0.89-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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
Jan Hutař
2016-12-01 16:08:33 UTC
Workaround: On Satellite by editing capsule remove "Library" from "Lifecycle Environments" selected items. On Capsule: [root@capsule4 ~]# pulp-admin -u admin -p $pulpAdminPassword rpm repo list | tr '\n' ';' | sed "s/; //g" | tr ';' '\n' +----------------------------------------------------------------------+ RPM Repositories +----------------------------------------------------------------------+ Id: Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_-_RH_Common_RPMs_x86_64_7Server Display Name: Red Hat Enterprise Linux 7 Server - RH Common RPMs x86_647Server Description: None Content Unit Counts: Erratum: 35 Rpm: 209 Id: Default_Organization-Red_Hat_Satellite_Capsule-Red_Hat_Satellite_Capsule_6_2_for_RHEL_7_Server_RPMs_x86_64 Display Name: Red Hat Satellite Capsule 6.2 for RHEL 7 Server RPMs x86_64 Description: None Content Unit Counts: Id: Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server Display Name: Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server Description: None Content Unit Counts: [root@capsule4 ~]# pulp-admin -u admin -p $pulpAdminPassword rpm repo delete --repo-id Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_-_RH_Common_RPMs_x86_64_7Server [root@capsule4 ~]# pulp-admin -u admin -p $pulpAdminPassword rpm repo delete --repo-id Default_Organization-Red_Hat_Satellite_Capsule-Red_Hat_Satellite_Capsule_6_2_for_RHEL_7_Server_RPMs_x86_64 [root@capsule4 ~]# pulp-admin -u admin -p $pulpAdminPassword rpm repo delete --repo-id Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server [root@capsule4 ~]# pulp-admin -u admin -p $pulpAdminPassword orphan remove --all Now again on Satellite assign "Library" back and sync. Unfortunately what is in the comment #3 does not seem to be a permanent fix, I'm getting the issue again. *** Bug 1400903 has been marked as a duplicate of this bug. *** FYI this issue really has nothing to do with running out of disk space, I guess that was an unfortunate coincidence. You just have to sync a capsule twice (the first time it will work fine). Verified in Satellite 6.2.5 Snap 3
No longer seeing the issue in the areas it is reported to affect:
Repeated Capsule Sync
* Tested by syncing a capsule 10 times in a row with and without changes.
Repo Sync
* Tested by sync'ing ~20 repos multiple times
Repeated Content View Publishing
* Tested by publishing 5 content views multiple times.
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/RHBA-2016:2940 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/RHBA-2016:2940 |