Bug 1455171 - undefined method `default_capsule?' for true:TrueClass when manipulating Repository
Summary: undefined method `default_capsule?' for true:TrueClass when manipulating Repo...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.2.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Roman Plevka
: 1455035 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-24 12:14 UTC by Peter Ondrejka
Modified: 2019-09-26 16:15 UTC (History)
6 users (show)

Fixed In Version: rubygem-katello-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-06-20 17:24:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
prodlog (199.08 KB, text/plain)
2017-05-24 12:14 UTC, Peter Ondrejka
no flags Details
screenshot (57.24 KB, image/png)
2017-05-24 12:15 UTC, Peter Ondrejka
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1553 0 normal SHIPPED_LIVE Satellite 6.2.10 Async Bug Release 2017-06-20 21:19:07 UTC

Description Peter Ondrejka 2017-05-24 12:14:13 UTC
Description of problem:

When publishing a new version of a content view via UI, a box pops up saying:

undefined method `default_capsule?' for true:TrueClass

See attached screenshot. Production log attached.

How reproducible:
Does not occur on the initial publish of a CV, only when publishing a new version

Steps to Reproduce:
1. create a CV, add some repository, publish a cv
2. optionally add another repo and publish a new verison of a cv

Checking or unchecking "Force Yum Metadata Regeneration" has no effect on this (btw. the question mark next to the option shows no context help)

Actual results:

Expected results:
cv should publish successfully

Additional info:

Occurs only if the original cv has some repository enabled, empty cv can be published multiple times without complications.

Comment 1 Peter Ondrejka 2017-05-24 12:14:58 UTC
Created attachment 1281942 [details]

Comment 2 Peter Ondrejka 2017-05-24 12:15:42 UTC
Created attachment 1281943 [details]

Comment 3 Evgeni Golov 2017-05-24 13:06:55 UTC
I wonder if this is a "dupe" of https://bugzilla.redhat.com/show_bug.cgi?id=1455035
Same error, just other place where it happens.

Comment 4 Roman Plevka 2017-05-24 13:27:06 UTC
This actually happens on updating Repositorties.

e.g. updating repository download policy.
# hammer repository update --id 1 --download-policy background

Comment 5 Brad Buckingham 2017-05-24 13:56:58 UTC
Looking at the code, this one may have also been introduced by bug 1375075.  Justin, can you take a look?

Comment 8 Justin Sherrill 2017-05-24 21:01:11 UTC
*** Bug 1455035 has been marked as a duplicate of this bug. ***

Comment 9 Roman Plevka 2017-05-29 10:39:14 UTC
this has been fixed in 6.2.10-2

Comment 11 errata-xmlrpc 2017-06-20 17:24:11 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.


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