Latest grimoirelab/full docker image not working with GitHub Enterprise backends

[chaoss]

Latest grimoirelab/full docker image not working with GitHub Enterprise backends

[valeriocos]

@filmaj thank you for reporting this issue. We will check it and let you know asap.

[jgbarah]

Thanks or the detailed report. I think at least a part of the problem is with this line (in the command lines for running the container):

-v $(pwd)/credentials.cfg:/mordred-override.cfg

In this version of the container, the right line should be:

-v $(pwd)/credentials.cfg:/override.cfg

This was a recent change, and now I realize the tutorial was not reflecting it. I just fixed it, sorry for causing you a wast of time.

Please, try it this way, and let us know if it works.

[jgbarah]

(not sure if the Can not configure kibiter error is serious or not, let me know if I should file that separately)

Yes, please. I cannot reproduce that. Let's wait, just in case, to see if somehow it is a cascading error from the previous one. But if it does not work after the /override.cfg case is fixed, yes please file a new bug report.

[filmaj]

Thanks so much for the help @jgbarah ! Changing the credential file binding definitely got rid of the Hungry Ocean bug ;)

As for the kibiter error - it is still there. I assume this is related to why my grimoirelab instance is asking for details on elasticsearch indices, and not displaying any data right away? See screenshot below.

I don't recall seeing this when I set up grimoire the first time around a few months ago.

And, as always: I am super appreciative of everyone's time and help thus far. I hope to contribute to grimoirelab as soon as I get my bearings! Thank you so much for the hand holding thus far.

[jgbarah]

Thanks so much for the help @jgbarah ! Changing the credential file binding definitely got rid of the Hungry Ocean bug ;)

Great!

As for the kibiter error - it is still there. I assume this is related to why my grimoirelab instance is asking for details on elasticsearch indices, and not displaying any data right away? See screenshot below.

Yes. Mordred takes care of creating an index and then defining a default index, which is something that must be done before panels can be uploaded. In your case, it seems Mordred is not being able of contacting Kibiter. Would you mind trying the container using a mapping for the Kibiter port to 127.0.0.1, instead of an specific IP address? Just to see if it works the same way it works for me in that case.

And, as always: I am super appreciative of everyone's time and help thus far. I hope to contribute to grimoirelab as soon as I get my bearings! Thank you so much for the hand holding thus far.

I think I'm going to take note of your comment for our appreciation quotes ;-) Seriously, thanks a lot for helping us to find and solve issues. Of course you're more than welcome to contribute as much as you may want ;-)

[filmaj]

Would you mind trying the container using a mapping for the Kibiter port to 127.0.0.1, instead of an specific IP address? Just to see if it works the same way it works for me in that case.

Looks like you nailed it, that seemed to be the issue with respect to the error:

Starting container: 2ae35bd31ced
Starting Elasticsearch
[ ok ] Starting Elasticsearch Server:.
Waiting for Elasticsearch to start...
tcp        0      0 0.0.0.0:9200            0.0.0.0:*               LISTEN      -
Elasticsearch started
Starting MariaDB
[ ok ] Starting MariaDB database server: mysqld.
Waiting for MariaDB to start...
tcp6       0      0 :::3306                 :::*                    LISTEN      -
MariaDB started
Starting Kibiter
Waiting for Kibiter to start...
..Kibiter started
Starting Mordred to build a GrimoireLab dashboard
This will usually take a while...
Kibiter/Kibana: version found is 6.1.0-3
Kibiter/Kibana: configured!
Dashboard panels, visualizations: uploading...
Dashboard panels, visualizations: uploaded!
Dashboard menu: uploading...
Dashboard menu: uploaded!
Collection for github: starting...
Collection for git: starting...
Username for 'https://git.corp.adobe.com': Collection for github: finished after 00:00:00 hours
Loading blacklist...

I suppose I could work around this temporarily by putting a proxy in front of mordred (like nginx or something).

[jgbarah]

Good! Now, tell me, why do you need to use an specific IP address, instead of 127.0.0.1? Is that because you want Kibiter to be browsable from hosts other than localhost, or something else?

In any case, I've tried using the public IP address of my host as the address in the mapping for the Kibiter port, and it works for me too...

[filmaj]

Now, tell me, why do you need to use an specific IP address, instead of 127.0.0.1? Is that because you want Kibiter to be browsable from hosts other than localhost, or something else?

Exactly this. It's not a critical thing because as I mentioned I can always stand nginx up in front of this.

In any case, I've tried using the public IP address of my host as the address in the mapping for the Kibiter port, and it works for me too...

Hmm, interesting, so it must be something on my side.

In any case, I will close this issue. Thanks so much for all the help!