Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionPrashant Waghmare
2016-10-21 20:43:59 UTC
Description of problem:
Unable to view activation keys in satellite web-ui since upgrade
Version-Release number of selected component (if applicable):
Satellite 6.2.2
How reproducible:
Always
Steps to Reproduce:
1. After upgrade to satellite 6.2 unable to view activation keys
2.$ sudo hammer activation-key list --organization Test
undefined method `products' for nil:NilClass
3.
Actual results:
After upgrade to satellite 6.2 unable to view activation keys
Expected results:
After upgrade to satellite 6.2 should be able to view activation keys
Additional info:
After application of following patch, this issue got resolved, and cu is able to view the activation keys in satellite web-ui
PR: https://github.com/Katello/katello/pull/6396 which is for patch : https://patch-diff.githubusercontent.com/raw/Katello/katello/pull/6396.patch
# find / -name activation_key.rb | grep katello
then among the out-put you got in above command, select the following path from it:
a) vi /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.*/app/models/katello/activation_key.rb
@@ -98,7 +98,11 @@ def products
if cp_pools
pools = cp_pools.collect { |cp_pool| Pool.find_by(:cp_id => cp_pool['id']) }
pools.each do |pool|
(-) all_products << pool.subscription.products
(+) if pool.subscription
(+) all_products << pool.subscription.products
(+) else
(+) Rails.logger.error("Pool #{pool.id} is missing its subscription id.")
(+) end
end
end
all_products.flatten!
Note: Sign (-) indicates comment the concern line and (+) sign indicates add the concern line.
Lukas,
I believe you have to have to have repositories that are no longer supported with a valid subscription (i.e. delete your manifest) on the activation key. Re-flag needinfo if this doesn't work.
Andrew,
yet before the upgrade I deleted a manifest, but still no luck reproducing this issue - AKs after the upgrade are all visible. (I associated 3 AKs to different subs in the manifest - 1 to all, 1 to employee only, 1 to atomic only)
Lukas,
I see what you're saying (just tried it on 6.2.7). One way to definitely reproduce this issue is to remove the relationship manually:
```
foreman-rake console
User.current = User.find_by(login: 'admin')
ak = Katello::ActivationKey.find(1)
pools = ak.get_key_pools.collect { |cp_pool| Katello::Pool.find_by(:cp_id => cp_pool['id']) }
pools.first.subscription_id = nil
pools.first.save
```
hammer activation-key list --organization-id 1
On 6.1.z, you would need to change the find_by calls to find_by_<field>, like this:
```
foreman-rake console
User.current = User.find_by_login('admin')
ak = Katello::ActivationKey.find(1)
pools = ak.get_key_pools.collect { |cp_pool| Katello::Pool.find_by_cp_id( cp_pool['id']) }
pools.first.subscription_id = nil
pools.first.save
```
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-2017:0447