Bug 1035171

Summary: test_broker_cache_permissions failure is seen when running oo-diagnostics after update ose from 1.2 to 2.0
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: Cluster Version OperatorAssignee: Jason DeTiberus <jdetiber>
Status: CLOSED ERRATA QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0.0CC: jdetiber, libra-onpremise-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-15 14:40:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Johnny Liu 2013-11-27 08:33:19 UTC
Description of problem:
Setup ose-1.2 env, create some app, then update env to 2.0, run oo-diagnostics, get the following error:
<--snip-->
FAIL: test_broker_cache_permissions
        Broker application cache contains files belonging to root. This will probably
        result in cache items that can't expire. Please clear the cache by executing:
            # oo-admin-broker-cache --clear
<--snip-->

Version-Release number of selected component (if applicable):
Always

How reproducible:
openshift-enterprise-upgrade-node-2.0.0b-1.git.16.a0bff65.el6op.noarch
openshift-enterprise-release-2.0.0b-1.git.16.a0bff65.el6op.noarch

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Jason DeTiberus 2013-12-03 00:20:30 UTC
This is fixed in the latest upgrade puddle: http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-02

Please note that this pad has changed the upgrade steps to use a puddle, so there are a few workarounds that need to be done to make sure the right bits are installed during the upgrade.

The post migration was loading the rails environment as root causing the incorrect permissions in the cache, I moved the cache clear step from the end_maintenance_mode step to the post step to make sure we are clearing the cache properly.

Comment 3 Johnny Liu 2013-12-03 05:54:35 UTC
Verified this bug with http://etherpad.corp.redhat.com/ose-2-0-upgrade-2013-12-02, and PASS.