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.
Bug 874160 - [upgrade] 1.0 to 1.1 upgrades brings UI error on Organizations edit page
Summary: [upgrade] 1.0 to 1.1 upgrades brings UI error on Organizations edit page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Hayk Hovsepyan
URL:
Whiteboard:
Depends On:
Blocks: sam12-tracker 874737
TreeView+ depends on / blocked
 
Reported: 2012-11-07 15:54 UTC by Garik Khachikyan
Modified: 2019-09-25 21:12 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
An old database index causes errors when editing an Organization after upgrading from 1.0 to 1.1. This fix adds a re-indexation as part of the upgrade process.
Clone Of:
: 874737 (view as bug list)
Environment:
Last Closed: 2012-12-04 19:57:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
logs (121.49 KB, application/x-gzip)
2012-11-07 15:54 UTC, Garik Khachikyan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Garik Khachikyan 2012-11-07 15:54:36 UTC
Created attachment 640170 [details]
logs

Description of problem:
doing upgrade of 1.0 to 1.1 one can see UI error on visiting Organizations Edit page. 
https://<FQDN>/cfse/organizations#panel=organization_&panelpage=edit

Version-Release number of selected component (if applicable):
katello-1.1.12-20.el6cf.noarch
katello-configure-1.1.9-11.el6cf.noarch

How reproducible:
always

Steps to Reproduce:
1.preupgrade: create org "CFSE QE Team" + an environment "Testing" for that org
2.upgrade according recent: https://fedorahosted.org/katello/wiki/Upgrade
3.visit the UI page above. Click on any org
  
Actual results:
Error
There was an error retrieving that row:Not Found

Expected results:
no error. 

Additional info:
Following i found in production log:
---
[ WARN: 2012-11-07 16:24:27 #22471] Unable to decrypt password, returning encrypted version No such file or directory - /etc/katello/secure/passphrase
[ WARN: 2012-11-07 16:24:27 #22471] Unable to decrypt password, returning encrypted version No such file or directory - /etc/katello/secure/passphrase
[ WARN: 2012-11-07 16:24:27 #22471] Unable to decrypt password, returning encrypted version No such file or directory - /etc/katello/secure/passphrase
[FATAL: 2012-11-07 16:37:33 #25660]
AbstractController::ActionNotFound (The action 'show' could not be found for OrganizationsController):

Logs are attached.

Comment 1 Lukas Zapletal 2012-11-07 16:14:17 UTC
Justin ping me if you need help with this - the /etc/katello/secure/passphrase warning does not seem to be related, but I should definitely look on hit. I dont want to see warnings like that in upgraded box. Will look.

Comment 2 Ivan Necas 2012-11-07 16:47:13 UTC
The main issue: showing the org, is caused by old index of the database. Running

rake reindex

fixes the issue

Comment 3 Justin Sherrill 2012-11-07 19:44:21 UTC
Hey Ivan, 

So is the plan to run rake reindex as part of the upgarde?  

and if so, is that being done as part of some other bug, or do you want me to add it as part of this bz?

-Justin

Comment 4 Lukas Zapletal 2012-11-08 08:44:30 UTC
Taking, will do the patch.

Comment 5 Lukas Zapletal 2012-11-08 09:32:27 UTC
https://github.com/Katello/katello/pull/1017

Comment 6 Lukas Zapletal 2012-11-08 11:43:46 UTC
I have investigated "Unable to decrypt password" and it is written only during upgrade, then Katello works without this warning fine. I will put a note in the release notes.

Comment 7 Lukas Zapletal 2012-11-08 11:44:16 UTC
Clearing NEEDINFO flag. This is solved.

Comment 10 Hayk Hovsepyan 2012-11-09 13:21:05 UTC
Verified on revision:

katello-certs-tools-1.1.8-1.el6cf.noarch
katello-configure-1.1.9-12.el6cf.noarch
katello-glue-candlepin-1.1.12-22.el6cf.noarch
katello-common-1.1.12-22.el6cf.noarch
katello-glue-pulp-1.1.12-22.el6cf.noarch
katello-agent-1.1.2-1.el6cf.noarch
katello-glue-foreman-0.1.311-1.el6_2.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-12.el6cf.noarch
katello-selinux-1.1.1-2.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-1.1.8-12.el6cf.noarch
katello-1.1.12-22.el6cf.noarch

Now it does not show error and is possible to edit org.

Comment 12 errata-xmlrpc 2012-12-04 19:57:55 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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html


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