Bug 1299335 - playbook should configure cockpit on containerized env
Summary: playbook should configure cockpit on containerized env
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Andrew Butcher
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 07:16 UTC by Ma xiaoqiang
Modified: 2016-07-04 00:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 16:37:36 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1065 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-05-12 20:32:56 UTC

Description Ma xiaoqiang 2016-01-18 07:16:30 UTC
Description of problem:
playbook should configure cockpit on containerized env


Version-Release number of selected component (if applicable):
openshift-ansible-3.0.33-1.git.0.bb1f8aa.el7aos.noarch

How reproducible:
always

Steps to Reproduce:
1. Install contaierized environment on rhel7 or atomic with logrotate
<--snip-->
osm_use_cockpit=true
osm_cockpit_plugins=['cockpit-kubernetes']
<--snip-->

2.check the package
#rpm -qa|grep cockpit

3.check the service
service cockpit status

Actual results:
playbook skips configuring the cockpit on containerized env

Expected results:
playbook configuring the cockpit on both rhel and atomic when installing containerized env

Additional info:

Comment 1 Andrew Butcher 2016-01-27 16:03:56 UTC
Proposed fix: https://github.com/openshift/openshift-ansible/pull/1279

Cockpit will be installed on RHEL when configuring containerized env

Comment 6 Ma xiaoqiang 2016-02-01 01:56:08 UTC
This RP works fine, move this issue to VERIFIED.

Comment 8 errata-xmlrpc 2016-05-12 16:37:36 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:1065


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