Skip to content
New issue

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

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

Already on GitHub? # to your account

changed to cosmic-version so the api error page will show cosmic #71

Merged
merged 1 commit into from
Sep 16, 2016

Conversation

ddegoede
Copy link
Contributor

@ddegoede ddegoede commented Sep 2, 2016

changed to cosmic-version so the api error page will show cosmic instead of cloud-stack this way there is way to distinguish between cloudstack and cosmic in using the api

@remibergsma
Copy link
Member

go build

1 similar comment
@ddegoede
Copy link
Contributor Author

ddegoede commented Sep 5, 2016

go build

@miguelaferreira
Copy link
Contributor

I've made this one!
Test says: "Timeout reached while waiting for system VM to be Stopped, actual state is Running"

Do you guys thing it's a time out thing?
The management server log for this build is not good...
cosmic_ 0600-collect-artifacts-and-cleanup__198__jenkins

@ddegoede
Copy link
Contributor Author

ddegoede commented Sep 7, 2016

Hi @miguelaferreira, I not sure, mainly because we had the test run three times now and every time something else failed... 😞
It could explain why random tests fail, if it is a timing issue, any suggestions where to start looking?

@miguelaferreira
Copy link
Contributor

miguelaferreira commented Sep 7, 2016

Well, when I changed this test the last time it was because the test assumed the VM would stop and automatically be started again. But in fact it did never stop (due to an error with exception on management server log) and the test would pass because it never checked that it actually had stopped.

Now it does wait until the VM stops and breaks if timeout is reached. What you could do, while running it in a bubble, is:

  1. check the management server logs for exceptions
  2. if you can manually stop a system vm, then increase the timeout in the test to see if that fixes it.

However, when random weirdness starts to happen, rebooting the slaves is usually a solution too.

@ddegoede
Copy link
Contributor Author

ddegoede commented Sep 7, 2016

Rebooting the slaves is exactly what @remibergsma did last weekend, and still it does fail at random tests

BTW thanks for you help @miguelaferreira

@ddegoede
Copy link
Contributor Author

ddegoede commented Sep 7, 2016

go build

@remibergsma remibergsma force-pushed the cosmic_api_version_label branch from 00347f2 to b8812b9 Compare September 15, 2016 12:50
@remibergsma
Copy link
Member

@ddegoede Rebased with latest master

Copy link
Member

@remibergsma remibergsma left a comment

Choose a reason for hiding this comment

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

All green, merging

@remibergsma remibergsma merged commit 43208e5 into master Sep 16, 2016
@remibergsma remibergsma deleted the cosmic_api_version_label branch September 16, 2016 20:43
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants