Skip to content

Conversation

@arm4b
Copy link
Member

@arm4b arm4b commented May 10, 2017

Reverts #3372

For now just a PR to experiment if pip packages might be related to re-appeared Ubuntu16 regression (even with timeouts) StackStorm/st2-packages#445.

@arm4b arm4b added the WIP label May 10, 2017
@Mierdin
Copy link
Member

Mierdin commented May 10, 2017

Good idea. Will keep an eye on this. Curious how you knew to look for this - how long has this been an issue? I was going to start looking through history last night but that was at about 1AM so I bailed

EDIT: nevermind, old build node thinking. Looking at history of new build node, clear that this wasn't working since its inception. So could have been broken before, but definitely broken as of #3372

@Mierdin
Copy link
Member

Mierdin commented May 10, 2017

Okay, u16 was passing with your reverts, so I set mongoengine back to 0.13 in 31c6065

@Mierdin
Copy link
Member

Mierdin commented May 10, 2017

Just changing mongoengine back to 0.13 re-broke things. So it seems pretty clear that this upgrade is the culprit

Matt Oswalt added 2 commits May 10, 2017 11:35
Signed-off-by: Matt Oswalt <oswaltm@brocade.com>
Signed-off-by: Matt Oswalt <oswaltm@brocade.com>
@Mierdin
Copy link
Member

Mierdin commented May 10, 2017

Okay I reverted the reverts except for the one for mongoengine. Will watch this make sure this passes, then we should consider merging this for now so that tests for other PRs can go through.

Someone knowledgeable about the database layer (not me) should review http://docs.mongoengine.org/changelog.html#changes-in-0-12-0 and see if anything impacts us; it seems obvious that it's something, but I am not sure.

@Mierdin Mierdin changed the title Revert "Upgrade dependencies" Revert mongoengine dependency upgrade May 10, 2017
@arm4b arm4b added bug RFR and removed WIP labels May 10, 2017
@arm4b arm4b requested a review from Kami May 10, 2017 19:50
@Kami
Copy link
Member

Kami commented May 10, 2017

👍

I did check the changelog before bumping, but nothing stood out and everything also passed locally and on Circle CI.

Having said that, it does look like some change is negatively impacting us so I will need to dig deeper in the mongoengine code.

@arm4b
Copy link
Member Author

arm4b commented May 10, 2017

As discussed with @Mierdin we 🚒 the 🔥 first and merge the fix to unblock the CI. According to the commit + CI green/red log, it's clearly mongoengine guilty.

And @Kami feel free to dig in deeper into the mongoengine changelog or ideally if you can, - please help investigate the StackStorm/st2-packages#445 which still remains the bug when we remove sleep 5 from the existing code (see https://github.com/StackStorm/st2-packages/blob/ffe4f7bb9addd777f0a5dd33602ff4d9e759378c/scripts/st2bootstrap-deb.sh#L331-L336) meaning manual install or configuration management install still has that problem.
You're more knowledgeable about st2 core mechanics & mongo.

@arm4b arm4b merged commit 337cca7 into master May 10, 2017
@arm4b arm4b deleted the revert-3372-upgrade_deps branch May 10, 2017 20:08
# Since states are being processed asynchronously, wait for the
# liveactions to go into scheduled states.
for i in range(0, 100):
eventlet.sleep(2)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was actually one because concurrency tests were failing, but if they are not failing anymore, it's fine.

That failure was probably related to Circle CI since it was failing on master as well, before any other stuff was merged.

@cognifloyd cognifloyd removed the RFR label Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants