Bug 1468711 - openshift-logging deployer creates an empty project called mux-undefined
Summary: openshift-logging deployer creates an empty project called mux-undefined
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-07 17:08 UTC by Mike Fiedler
Modified: 2019-11-21 12:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-21 12:47:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Fiedler 2017-07-07 17:08:00 UTC
Description of problem:

Version-Release number of the following components:

root@ip-172-31-31-187: /tmp # rpm -q openshift-ansible
openshift-ansible-3.6.136-1.git.0.ac6bb62.el7.noarch
root@ip-172-31-31-187: /tmp # rpm -q ansible
ansible-2.2.3.0-1.el7.noarch
root@ip-172-31-31-187: /tmp # ansible --version
ansible 2.2.3.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides


How reproducible: Always

Steps to Reproduce:
1.  Run byo/openshift-cluster/openshift-logging.yaml with inventory below

Actual results:

Empty project names mux-undefined is created

Expected results:

No unexpected projects with odd names

Comment 1 Scott Dodson 2017-07-07 19:08:44 UTC
Looks like the inventory is missing. Marking this as 3.7, move it to 3.6.1 if you think it's more critical than that.

Comment 2 Mike Fiedler 2017-07-07 19:26:27 UTC
[oo_first_master]
ip-172-31-31-187

[oo_first_master:vars]
openshift_deployment_type=openshift-enterprise
openshift_release=v3.6.0

openshift_logging_install_logging=true
openshift_logging_use_ops=false
openshift_logging_master_url=https://ec2-34-212-83-5.us-west-2.compute.amazonaws.com:8443
openshift_logging_master_public_url=https://ec2-34-212-83-5.us-west-2.compute.amazonaws.com:8443
openshift_logging_kibana_hostname=kibana.example.com
openshift_logging_namespace=logging
openshift_logging_image_prefix=registry.ops.openshift.com/openshift3/
openshift_logging_image_version=v3.6.136
openshift_logging_es_cluster_size=3
openshift_logging_es_pvc_dynamic=true
openshift_logging_es_pvc_size=10Gi
openshift_logging_fluentd_use_journal=true
openshift_logging_use_mux=true
openshift_logging_use_mux_client=true

Comment 3 Mike Fiedler 2017-09-06 17:54:50 UTC
I think this should go to the logging guys.   They are actually using mux-undefined I believe.  This might not be a bug or might need that (IMO) bad name changed.

Comment 4 Jeff Cantrill 2017-09-20 13:44:18 UTC
Rich, I'm assigning for comment here.

Comment 5 Rich Megginson 2017-09-20 14:04:06 UTC
required by mux - see https://github.com/openshift/origin-aggregated-logging/blob/master/docs/mux-logging-service.md

I guess we just need to document this

Comment 6 Anping Li 2018-01-25 10:25:15 UTC
The project name may be changed https://bugzilla.redhat.com/show_bug.cgi?id=1538560

Comment 7 Stephen Cuppett 2019-11-21 12:47:13 UTC
OCP 3.6-3.10 is no longer on full support [1]. Marking un-triaged bugs CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Version to the appropriate version where reproduced.

[1]: https://access.redhat.com/support/policy/updates/openshift


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