New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing data in Automate UI #199

Closed
scarolan opened this Issue Mar 10, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@scarolan

scarolan commented Mar 10, 2017

Cookbook version

2.3.5 and 2.4.0

Chef-client version

12.13.37

Platform Details

Ubuntu

Scenario:

Demonstrate Chef Automate. No data shows up in the UI for chef runs.

Steps to Reproduce:

Contact SA team in Chef Slack. We have an environment quarantined that is showing the problem.

Expected Result:

You'll see the UI has no data.

Actual Result:

No Data in the UI

@vjeffrey

This comment has been minimized.

Collaborator

vjeffrey commented Mar 10, 2017

issue is intermittent.

scar-pto-in-nyc [1:06 PM] 
@vj actually it looks like both 2.3.5 and 2.4.0 are intermittently broken
we've had four instances of 2.3.5 break in the past two days
i think i'm the only one who tested 2.4.0 so far, also fails
what's really odd is it's intermittent 
we haven't tracked down what is choking up the data collector

vj [1:11 PM] 
do you have a sample role you’re using so we can try to reproduce?  is it always on the same certain profiles?

scar-pto-in-nyc [1:11 PM] 
so with the one i just did upgraded to 2.4.0, ran chef client over, still no data.
spun up a fresh environment, worked out of the box
they are bit-for-bit identical

scar-pto-in-nyc [1:12 PM] 
i suspect some kind of variable data
a date stamp or random number perhaps
is sneaking into the data stream
or i could just be talking out of my butt, i have no idea
thats where we could use some help
@alexpop

This comment has been minimized.

Collaborator

alexpop commented Mar 14, 2017

Sean, my research showed no issue in the audit cookbook here.
I added more details in the internal ticket(CMP-166), but this issue is related to ElasticSearch missing our defined mapping for index insights-2017.03.10.

@alexpop alexpop closed this Mar 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment