Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Problems with full-stack testing:
- 1) tools/configure_for_func_testing.sh fails to configure mysql for me. It says
- the password is wrong. This is a fresh Fedora 21 VM. I installed devstack before
- and set all passwords to '1'. Once I set the mysql root password to secretmysql
- the script could finish successfully. At this point I could run the functional DB
- tests (But the postgres tests were still skipped, I suspect this is wrong as well).
- I could also switch back the mysql root password back to the Devstack password
- and still have the DB functional tests finish successfully.
- 2) Logging: It is assumed that /opt/stack/logs is the logs directory while in fact
- the logging directory is configurable in Devstack. That being said, /opt/stack is the
- default $DEST for devstack and the 'logs' subdirectory should exist after one's
- already used stack.sh. It was however kind of difficult to debug this: What happens
- if /opt/stack/logs doesn't exist is that the neutron-server process won't start
- and there's zero indication as to why. I think that the full-stack tests should make
- sure that the logs directory is there and writable by test user. If it's not there,
- create it. If it is but not writable, throw out an error and fail the test.
- 3) Rabbit: Once I got the neutron-server process to start it failed to connect to Rabbit.
- I changed the password of the 'stackrabbit' user to '127.0.0.1'. This killed the devstack
- environment as it uses the password set in local.conf. Should we use a unique username / password?
- 4) Concurrent testing: Unique vhost per test? This would require the startup of each test to
- add a vhost, and set_permissions on the test user to that vhost.
- metadata_proxy is left after successful runs
- I see different processes left after failed runs
- Are br-int and br-ex being deleted after successful runs? Failed runs? (Spoiler: No)
- After a while (Real helpful I know) rabbit completely jammed up. Every message
- send just froze, with no timeout. Queues were empty. Restarting the server or the VM
- did not help. unstack, clean, stack did not help. I did not try to stop_app, reset, start_app,
- add user, set permissions.
Advertisement
Add Comment
Please, Sign In to add comment