Bug 1400624 - capsule sync (after capsule ran out of disk-space) says: "wrong number of arguments (2 for 1)"
Summary: capsule sync (after capsule ran out of disk-space) says: "wrong number of arg...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.2.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: jcallaha
URL:
Whiteboard:
: 1400903 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-01 16:08 UTC by Jan Hutař
Modified: 2019-09-25 21:20 UTC (History)
5 users (show)

Fixed In Version: rubygem-katello-3.0.0.89-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2016-12-01 16:08:33 UTC
Description of problem:
Capsule sync (after capsule ran out of disk-space - I'm not exactly sure if it worked before or not) says: "wrong number of arguments (2 for 1)"


Version-Release number of selected component (if applicable):
Sat: satellite-6.2.5-1.0.el7sat.noarch
Capsule: satellite-capsule-6.2.5-1.0.el7sat.noarch


How reproducible:
Seen on 4 of 4 capsules


Steps to Reproduce:
1. Install Sat and Capsule (capsule had 30GB HDD only by accident)
2. Sync RHEL7 to Sat and Capsules, see Capsules to run out of disk space
3. Migrate /var/lib/pulp of the capsule to new 70GB volume
4. Retry sync


Actual results:
Clicking "Synchronize" in webUI throws error "wrong number of arguments (2 for 1)"


Expected results:
Should work or should provide meaningful error message

Comment 3 Jan Hutař 2016-12-01 16:39:51 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.

Comment 5 Jan Hutař 2016-12-01 22:04:31 UTC
Unfortunately what is in the comment #3 does not seem to be a permanent fix, I'm getting the issue again.

Comment 6 Brad Buckingham 2016-12-05 14:28:46 UTC
*** Bug 1400903 has been marked as a duplicate of this bug. ***

Comment 7 Justin Sherrill 2016-12-05 16:55:55 UTC
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).

Comment 9 jcallaha 2016-12-07 16:34:33 UTC
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.

Comment 10 Bryan Kearney 2016-12-12 18:48:17 UTC
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

Comment 11 Bryan Kearney 2016-12-12 18:48:18 UTC
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


Note You need to log in before you can comment on or make changes to this bug.