Bug 1391066 - No OpenShift discovery due to undefined rindex method called.
Summary: No OpenShift discovery due to undefined rindex method called.
Keywords:
Status: CLOSED DUPLICATE of bug 1387614
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: C&U Capacity and Utilization
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Beni Paskin-Cherniavsky
QA Contact: Dafna Ron
URL:
Whiteboard: container:discovery
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-02 13:59 UTC by Bruno Gillet
Modified: 2017-11-27 13:33 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 08:47:38 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bruno Gillet 2016-11-02 13:59:24 UTC
Description of problem:
With an OpenShift provider activated as well as C&U roles in CloudForms, No discovery may be achieved. Logs show an unknown method called rindex is called generating an exception. (typo?)
Here is an extract from evm.log :

...
ERROR -- : [NoMethodError]: undefined method `rindex' for nil:NilClass  Method:[rescue in block in start_event_monitor]
ERROR -- : /opt/rh/cfme-gemset/gems/kubeclient-2.1.0/lib/kubeclient/common.rb:129:in `parse_definition'
ERROR -- : MIQ(ManageIQ::Providers::OpenshiftEnterprise::ContainerManager::EventCatcher::Runner#start_event_monitor) EMS [ose.example.com] as [] Event Monitor Thread aborted because [undefined method `rindex' for nil:NilClass]
/opt/rh/cfme-gemset/gems/kubeclient-2.1.0/lib/kubeclient/common.rb:115:in `block in discover'
/opt/rh/cfme-gemset/gems/kubeclient-2.1.0/lib/kubeclient/common.rb:113:in `each'
/opt/rh/cfme-gemset/gems/kubeclient-2.1.0/lib/kubeclient/common.rb:113:in `discover'
/opt/rh/cfme-gemset/gems/kubeclient-2.1.0/lib/kubeclient/common.rb:78:in `method_missing'
/var/www/miq/vmdb/gems/pending/kubernetes/events/kubernetes_event_monitor.rb:32:in `each'
/var/www/miq/vmdb/app/models/manageiq/providers/kubernetes/container_manager/event_catcher_mixin.rb:41:in `monitor_events'
/var/www/miq/vmdb/app/models/manageiq/providers/base_manager/event_catcher/runner.rb:164:in `block in start_event_monitor'
...

Version-Release number of selected component (if applicable):
5.7.0.7-beta1.20161025153249_9376fbd


How reproducible:
Always

Steps to Reproduce:
1.Add an OSE provider and activate C&U roles in cfme appliance.
2.parse evm.log looking for ERROR

Actual results:
No discovery and error logged

Expected results:
Discovery should work, no error should raise.

Additional info:

Comment 2 Federico Simoncelli 2016-11-02 22:53:51 UTC
This could be a duplicate of bug 1387614.
Beni, Zahi, if so you could check this together.

Comment 3 Beni Paskin-Cherniavsky 2016-11-08 10:35:49 UTC
Bruno, which version of OpenShift did you encounter this with?

What do you mean by "No discovery"?  Do you mean provider inventory refresh fails, or something else?

Also, if you still have full evm.log, please attach it.  We still haven't reproduced this, so more info would help.

Comment 4 Bruno Gillet 2016-11-10 08:42:58 UTC
Hi Beni,
I believe OSE release was 3.2 - checking that with provider of the lab and will update accordingly.
Provider was correctly defined but no discovery was done.
This lab was provisioned for few days only and I did not kept the evm.log.
The error message I gave to you was the only one I could see, and was repeating several times each minutes.
Sorry not to help more but this is all input I can give to you.

Comment 5 Bruno Gillet 2016-11-10 13:14:34 UTC
After double check, OSE release was 3.1.
HTH

Comment 6 Federico Simoncelli 2016-11-14 15:40:12 UTC
If this is a duplicate of bug 1387614 can we CLOSE DUPLICATE one of the two bugs?
(If not clear yet, let's keep them both).

Comment 7 Beni Paskin-Cherniavsky 2016-11-15 08:47:38 UTC
I was hesitant because we don't yet have repro/understanding for either one,
but OTOH we don't have differenting info that could lead us to conclude "we explained/fixed this one but not that one".

=> Closing this one as the other is older and had more discussion.

P.S. Thanks Bruno for the details above.

*** This bug has been marked as a duplicate of bug 1387614 ***

Comment 8 Mooli Tayer 2016-11-15 10:07:33 UTC
If this bug keeps reproducing it could be very helpful to get the result of:

curl -k https://<openshift_master_url>:8443/api/v1

Comment 9 Bruno Gillet 2017-11-27 13:33:55 UTC
Please close that BZ as really outdated so far.
Cheers.
Bruno.


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