| *** diablo_rojo has quit IRC | 00:43 | |
| *** diablo_rojo has joined #storyboard | 00:45 | |
| *** fatema_ has quit IRC | 00:50 | |
| *** udesale has joined #storyboard | 04:03 | |
| *** persia has quit IRC | 04:13 | |
| *** persia has joined #storyboard | 04:14 | |
| *** udesale_ has joined #storyboard | 05:36 | |
| *** udesale__ has joined #storyboard | 05:37 | |
| *** udesale has quit IRC | 05:39 | |
| *** udesale_ has quit IRC | 05:41 | |
| *** udesale_ has joined #storyboard | 06:48 | |
| *** udesale__ has quit IRC | 06:50 | |
| *** jtomasek has joined #storyboard | 07:18 | |
| *** diablo_rojo has quit IRC | 07:25 | |
| *** sparkycollier has quit IRC | 07:25 | |
| *** sparkycollier has joined #storyboard | 07:27 | |
| *** diablo_rojo has joined #storyboard | 07:28 | |
| *** tosky has joined #storyboard | 08:19 | |
| *** fatema_ has joined #storyboard | 09:08 | |
| *** udesale_ has quit IRC | 10:16 | |
| fatema_ | ok I followed the steps mentioned but got stuck | 10:54 |
|---|---|---|
| fatema_ | mentioned int the readme in github* | 10:54 |
| persia | fatema_: Where did you get stuck? Also, which steps? | 10:54 |
| persia | Ah. One of the persistent problems we have is that the github mirrors are easy to find, but not actually used by the project :) | 10:55 |
| fatema_ | aha | 10:55 |
| fatema_ | but the thing is that It got fine | 10:56 |
| fatema_ | and I double-clicked run | 10:56 |
| persia | Am I correct that you were looking at a prettily rendered version of http://git.openstack.org/cgit/openstack-infra/storyboard/tree/README.rst ? | 10:56 |
| fatema_ | The GUI showed then the menus aren't clickable | 10:57 |
| fatema_ | I guess not | 10:57 |
| fatema_ | I was looking into detailed steps to build the project as gradle in intellij | 10:58 |
| persia | Could you share the URL from which you started, and the one on which you got stuck? | 10:58 |
| fatema_ | https://github.com/opendatakit/briefcase | 10:59 |
| fatema_ | it's all in the same url | 11:00 |
| fatema_ | but this is totally different from the URL you sent me | 11:01 |
| persia | Yes. I thought you started form https://github.com/openstack-infra/storyboard | 11:01 |
| persia | I don't actually know anything about ODK. | 11:02 |
| persia | But if you're looking for storyboard stuff, I wouldn't start from https://github.com/opendatakit/briefcase :) | 11:02 |
| fatema_ | Oh my wrong link | 11:03 |
| persia | https://docs.openstack.org/contributors/code-and-documentation/index.html is perhaps a good general overview document about setting up accounts, etc. to work with OpenStack | 11:03 |
| fatema_ | ok I will go with the link and thanks for help | 11:03 |
| persia | Please ask if you have any issues along the way. | 11:05 |
| *** udesale has joined #storyboard | 11:46 | |
| fatema_ | so I have stumbled in step "Run a local development server, which uses the production API." | 12:11 |
| fatema_ | and all the terminal says | 12:12 |
| fatema_ | ERROR: venv: commands failed | 12:13 |
| tosky | fatema_: only that? Can you please paste the command that you executed and the full output? | 12:14 |
| fatema_ | tox -e venv -- storyboard-db-manage --config-file ./etc/storyboard.conf upgrade head | 12:15 |
| tosky | did you also execute the API service, as described into the previous section? ("Start the API server:") | 12:15 |
| tosky | so you are one or two steps before "Run a local development server" | 12:15 |
| fatema_ | this command should Upgrade DB schema to the latest version | 12:18 |
| fatema_ | should the API service start before, I have been walking through the command line series | 12:18 |
| tosky | no, the API should run after the upgrade | 12:20 |
| tosky | but iirc the command should be a bit more verbose | 12:20 |
| tosky | so do you only get the line "ERROR: venv: commands failed" after you run that tox -e venv command? | 12:21 |
| fatema_ | It loaded for a while then error occurred | 12:24 |
| fatema_ | File "/home/fatema/GSoC/storyboard/.tox/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/__init__.py", line 386, in create_engine | 12:24 |
| fatema_ | return strategy.create(*args, **kwargs) | 12:24 |
| fatema_ | File "/home/fatema/GSoC/storyboard/.tox/venv/local/lib/python2.7/site-packages/sqlalchemy/engine/strategies.py", line 51, in create | 12:24 |
| fatema_ | dialect_cls = u.get_dialect() | 12:24 |
| fatema_ | AttributeError: 'NoneType' object has no attribute 'get_dialect' | 12:24 |
| fatema_ | ERROR: InvocationError: '/home/fatema/GSoC/storyboard/.tox/venv/bin/storyboard-db-manage --config-file etc/storyboard.conf upgrade head' | 12:24 |
| fatema_ | this is the last part of it | 12:24 |
| tosky | need to go away for ~30 minutes, but please paste the full output on a pastebin site (like paste.openstack.org) | 12:34 |
| tosky | not just the last part - there is a reason if I asked for the full output | 12:34 |
| fatema_ | http://paste.openstack.org/raw/708944/ | 12:40 |
| fatema_ | I did as you asked | 12:40 |
| SotK | fatema_: what does the `connection = ...` line in your etc/storyboard.conf file look like? (don't paste the password though) | 12:48 |
| fatema_ | No etc/storyboard.conf exists | 12:50 |
| SotK | ah, thats likely the issue then | 12:56 |
| SotK | steps 4 and 5 on https://docs.openstack.org/infra/storyboard/install/development.html describe what it needs to contain | 12:56 |
| *** udesale has quit IRC | 13:00 | |
| *** udesale has joined #storyboard | 13:18 | |
| *** dmsimard has quit IRC | 13:21 | |
| fatema_ | I can't seem to find this file./etc/storyboard.conf.sample | 13:26 |
| fatema_ | NVM was looking in the root directory | 13:30 |
| fatema_ | SotK, thank you | 13:34 |
| fatema_ | I added the Public IP address | 13:53 |
| fatema_ | http://paste.openstack.org/show/708956/ | 13:53 |
| fatema_ | still there is the error | 13:53 |
| tosky | fatema_: so did you both copy the file as ./etc/storyboard.conf inside the repository, fixed valid_oauth_clients AND also fixed the connection key? | 14:00 |
| fatema_ | yes | 14:02 |
| fatema_ | valid_oauth_clients = storyboard.openstack.org, localhost 41.35.56.0 | 14:02 |
| fatema_ | and the pass | 14:02 |
| tosky | and uncommented the connection line? | 14:03 |
| fatema_ | yes | 14:03 |
| tosky | just to add few more details, which distribution are using? | 14:05 |
| fatema_ | Ubuntu 16.04 lts | 14:06 |
| tosky | ok, then that should work | 14:07 |
| SotK | that valid_oauth_clients line is missing a comma after `localhost` | 14:09 |
| tosky | oh, right | 14:10 |
| SotK | though, I'm not sure that would cause the error | 14:10 |
| fatema_ | I tried that before and got the same result | 14:11 |
| fatema_ | well I should use my public IP address right | 14:11 |
| fatema_ | ? | 14:11 |
| SotK | that only affects where login requests are accepted from, so you need to use whichever IP address or hostname you're planning to go to in the browser to see storyboard | 14:12 |
| persia | fatema_: You should use an IP you can reach from your workstation. If you are on a purely private network with private access to the machine you are using, you can use a private IP. Otherwise the public IP is correct. | 14:12 |
| tosky | uhm, but do you think that the incorrect IP would produce that backtrace? | 14:13 |
| SotK | no | 14:14 |
| fatema_ | What could be the cause, something with the configuration or the machine ? | 14:17 |
| tosky | I did the same steps on that version of ubuntu 3 weeks ago | 14:18 |
| tosky | apart from rechecking if the required packages are installed, could try cloning the storyboard repository again and trying again the changes? | 14:19 |
| fatema_ | ok I'll start the steps again | 14:20 |
| fatema_ | ok error is in the same step but different | 14:29 |
| fatema_ | http://paste.openstack.org/show/708964/ | 14:29 |
| tosky | fatema_: that looks like a syntax error in the conf file | 14:30 |
| persia | fatema_: What do you have in line 63 of the configuration file? | 14:30 |
| fatema_ | # A list of valid client id's that may connect to StoryBoard. | 14:35 |
| fatema_ | this is a comment it can't cause an error! | 14:39 |
| tosky | it may be something related to the previous line too | 14:41 |
| tosky | for sure there is something fishy there, or the parser wouldn't explode | 14:42 |
| fatema_ | when I ran the command again it returned the old error | 14:45 |
| fatema_ | I can't understand its behavior | 14:45 |
| fatema_ | almost all the file is commented | 14:46 |
| tosky | if you start again with a clean etc/storyboard.conf file and only change the connection key, without touching the other value, does it work? | 14:46 |
| fatema_ | I redo the cp step again and try | 14:46 |
| fatema_ | I have redone it and it's finally successful | 14:54 |
| fatema_ | this way I lack only one step | 14:55 |
| fatema_ | Thank you | 14:58 |
| SotK | I'm glad you got it working, that was an unusual error | 14:59 |
| fungi | following mordred's thread on the -dev ml, looks like not only openstacksdk but also python-openstackclient are both interested in migrating their bugs to storyboard.o.o now | 14:59 |
| fatema_ | well it shouldn't give me 404 not found error ! | 15:01 |
| tosky | fatema_: who exactly is returning 404? The browser? | 15:02 |
| fatema_ | yes | 15:02 |
| tosky | fatema_: how did you start the web part? | 15:02 |
| fatema_ | I have cloned web-client | 15:02 |
| fatema_ | but should the server wait for the client ?? | 15:03 |
| tosky | and how did you start the webclient? | 15:03 |
| fatema_ | I didn't start it yet | 15:03 |
| fatema_ | I started the server first | 15:04 |
| tosky | you started the API server then; you need to start the webclient, that provides the web interface | 15:04 |
| tosky | according the instructions | 15:04 |
| fatema_ | while starting the client I should run : "tox -egrunt_no_api -- serve", right ? | 15:24 |
| SotK | yeah | 15:26 |
| tosky | and probably I would add also --hostname 0.0.0.0 | 15:29 |
| tosky | at the end of the command line | 15:30 |
| fatema_ | http://paste.openstack.org/show/708975/ | 15:35 |
| fatema_ | It's giving me this error | 15:35 |
| fatema_ | I hope it's not related to pyhton version as I read | 15:36 |
| tosky | what is 'Already using interpreter /home/fatema/anaconda3/bin/python' ? | 15:36 |
| tosky | it should work with the default python | 15:36 |
| *** jamesmcarthur has joined #storyboard | 15:39 | |
| fatema_ | should I configure it to work with the default python instead | 15:41 |
| fatema_ | ? | 15:42 |
| tosky | I would change the question: is there a special reason for configuring a custom python? (maybe for some other reasons) | 15:42 |
| fatema_ | for my machine I didn't do it for a special purpose | 15:42 |
| fatema_ | I guess anaconda does this by default | 15:42 |
| tosky | I know anaconda the installer of the Fedora distribution, is this another anaconda? | 15:43 |
| persia | Also, is this machine a live-boot environment, or the result of a completed installation? | 15:44 |
| fatema_ | yes it is an environment to develop with python it has jypter and spydir as IDEs | 15:45 |
| persia | In that case, you may find things more likely to work if you configure to use system python. | 15:46 |
| *** udesale has quit IRC | 16:03 | |
| *** udesale has joined #storyboard | 16:18 | |
| *** udesale has quit IRC | 16:23 | |
| fungi | is storyboard known to run successfully under python 3.6? | 17:05 |
| fungi | i think in production we've still got it deployed under 2.7 but i should check that assertion | 17:06 |
| SotK | iirc my test instance is running 3.6 | 17:06 |
| fungi | yeah, we're still running it under 2.7, but if someone has successfully run it under 3.6 then i expect it must work | 17:07 |
| SotK | I hit one issue when logging in, but I think the fix for that merged | 17:07 |
| *** mridu has joined #storyboard | 17:07 | |
| fungi | fatema_: looks like this bug, perhaps: https://github.com/conda/conda/issues/6026 | 17:08 |
| fungi | which seems to have actually been https://bugs.python.org/issue30065 if i'm following all the breadcrumbs correctly | 17:12 |
| mridu | Hi, I have cloned storyboard project. As discussed with Kendall I am working on test_tasks.py file. To improve the test case coverage. But, I wanted to know how to start running the tests. | 17:12 |
| mridu | I don't see any module import of pytest or unittest either | 17:12 |
| fungi | fatema_: so anyway, using a newer build of python (or an older one) may solve this | 17:13 |
| fungi | mridu: looks like we may not (yet) do a great job of documenting inside the repo how to initiate its unit tests | 17:14 |
| fungi | the short story is that you can run tests like `tox -e py27` (if you have tox installed and in your path) | 17:15 |
| mridu | no I don't have tox installed. Aren't the tests using pytest? I could have run the pytest command. | 17:15 |
| fungi | the underlying testrunner is "testr" (invoked via a setuptools entrypoint provided courtesy of pbr) | 17:15 |
| tosky | right now the ostestr wrapper is used | 17:17 |
| fungi | here are some testr-related notes/tips: https://wiki.openstack.org/wiki/Testr | 17:17 |
| fungi | tosky: oh, you're right, looking in tox.ini i see it's indeed invoking via ostestr (except for `tox -e cover` which calls testr through setuptools/pbr) | 17:18 |
| fungi | but anyway, you could invoke ostestr or testr (or stestr presumably) to run tests directly without relying on tox | 17:19 |
| *** diablo_rojo has quit IRC | 17:19 | |
| clarkb | chances are you can even run pytest too | 17:20 |
| fungi | we generally recommend running tests under tox, however, as this helps ensure you're using appropriate versions of the test dependencies installed into a clean virtualenv | 17:20 |
| clarkb | testr (and friends) use a fairly bland stdlib standardish set of expectations so tests that work with it should work with other runners | 17:20 |
| fungi | presumably even nosetest? | 17:20 |
| * fungi shudders | 17:20 | |
| mordred | it should work with any test runner | 17:21 |
| mordred | although we don't test that anywhere, and there are no guarantees | 17:21 |
| fungi | and for our automated testing we also invoke tox, so if you use tox locally you're getting an experience much more consistent with what our ci system will run when your patches get proposed | 17:22 |
| * mordred should get storyboard migrated over to stestr | 17:22 | |
| *** diablo_rojo has joined #storyboard | 17:24 | |
| mridu | sure. Will read through the notes. | 17:28 |
| mridu | And try using tox. | 17:29 |
| mridu | Also, any specific reason for using Python2.7? | 17:32 |
| mridu | Do we plan to port it to Python 3? | 17:32 |
| mordred | I don't know if we have plans to do so yet - but the latest versions of our other things are actually python3 only ... I know *I* would be in favor of such a thing | 17:33 |
| diablo_rojo | mridu, yeah the plan is to move forward, but we are all kind of overworked and have bigger fish to fry. If you wanted to work on porting things over, that would be an easy way to get some patches in. | 17:33 |
| mordred | ++ | 17:33 |
| * mordred was just about to add "but you should talk to diablo_rojo" :) | 17:34 | |
| * diablo_rojo had to do a lappy restart else she would have butted into the conversation sooner :) | 17:34 | |
| mridu | Sure, in either case I have no issues helping with that as well. Provided something else does not break. | 17:35 |
| diablo_rojo | mridu, I think most changes should be pretty straight forward from what I saw of the other projects switching over. | 17:37 |
| * diablo_rojo tries to remember the name of who went through many of the other OpenStack projects switching them to python3.. | 17:38 | |
| diablo_rojo | he could probably give you some pointers | 17:38 |
| diablo_rojo | If I can remember his name. | 17:38 |
| fungi | yeah, basically the tests (and storyboard in general) should ideally run with both python 2.7 and 3.5 for now (these are what we test in our ci system) | 17:38 |
| fungi | our production instance of storyboard for the openstack community (storyboard.openstack.org) is installed under python 2.7 but may be rebuilt under 3.something in the near future | 17:39 |
| fungi | where "near" is likely sometimes before or around the 2020 end of life for python 2.x | 17:40 |
| diablo_rojo | It would be great to get things moving though so that we are looking ahead a little bit. | 17:41 |
| fungi | absolutely | 17:41 |
| fungi | sounds like it already works under 3.6, and we're testing every commit against 3.5, so we're probably in okay shape | 17:42 |
| *** tosky has quit IRC | 17:44 | |
| mordred | woot | 17:48 |
| *** tosky has joined #storyboard | 17:48 | |
| mridu | sure. Anything to me is fine | 17:49 |
| mridu | Will start off with the tests | 17:50 |
| diablo_rojo | mridu, sounds good to me :) | 17:50 |
| mridu | :) | 17:52 |
| openstackgerrit | Monty Taylor proposed openstack-infra/storyboard master: Switch to using stestr for tests https://review.openstack.org/555397 | 18:01 |
| mordred | diablo_rojo: ^^ merry christmas | 18:01 |
| diablo_rojo | mordred, thank you :) Opened the tab to review. | 18:06 |
| diablo_rojo | Will get to it after I am done digging out from all the emails I need to reply to lol | 18:06 |
| *** fatema_ has quit IRC | 18:10 | |
| mridu | I installed tox. But, on running 'tox -e venv $TESTS_YOU_ARE_TRYING_TO_RUN' getting an error https://pastebin.com/sP1Q3u6D | 18:18 |
| mordred | mridu: "ReadTimeoutError: HTTPSConnectionPool(host='pypi.python.org', port=443): Read timed out." is, I believe, the salient piece | 18:19 |
| mordred | mridu: pip seems unable to talk to pypi.python.org from where you're executing it | 18:19 |
| *** fatema_ has joined #storyboard | 18:35 | |
| *** diablo_rojo has quit IRC | 18:38 | |
| *** mridu has quit IRC | 18:40 | |
| *** diablo_rojo has joined #storyboard | 18:40 | |
| *** mridu has joined #storyboard | 18:45 | |
| fungi | yes, the first time you run tox for a given environment name, it will want to retrieve and install all declared dependencies into the associated virtualenv it creates. subsequent runs will reuse that virtualenv and so won't redownload them every time (unless you add -r to recreate) | 18:48 |
| mridu | installing netifaces is giving me error | 18:52 |
| mridu | not all requirements are getting installed | 18:52 |
| fatema_ | fungi, thank you I have been trying to uninstall anaconda but it will result in more complex, so I will change used python on my machine hopefully it'll work just fine | 18:53 |
| fungi | mridu: the bindep.txt file in the storyboard repository describes the system packages you may need separately install to be able to run some tests | 18:56 |
| mridu | will have a look. thanks | 18:56 |
| fungi | mridu: if you run `tox -e bindep` it will hopefully be parsed and compared to your installed list of system packages to tell you which ones are missing | 18:56 |
| fungi | in the case of netifaces failing to build, odds are it's one of the c header (-dev or -devel depending on your distro) packages which the c extensions in netifaces need to complile | 18:57 |
| mridu | Missing packages: gawk libcurl4-gnutls-dev libmysqlclient-dev postgresql-client python-lxml python-zmq python3-all-dev uuid-dev xvfb ERROR: InvocationError: '/home/mridu/openstack-outreachy/storyboard/.tox/bindep/bin/bindep test' ____________________________________________________________________________ summary _____________________________________________________________________________ ERROR: bindep: commands failed | 18:59 |
| *** jamesmcarthur has quit IRC | 19:04 | |
| fungi | mridu: yeah, the "ERROR: InvocationError: [...] bindep: commands failed" is normal. that's because bindep exits nonzero (failure) if you are missing some packages and exits 0 (success) if you have all the packages installed | 19:05 |
| fungi | so tox is reporting failure in the same way that it would report failure ofr, say, failed tests in a test run | 19:05 |
| fungi | so basically you want to use your package manager of choice to install: gawk libcurl4-gnutls-dev libmysqlclient-dev postgresql-client python-lxml python-zmq python3-all-dev uuid-dev | 19:06 |
| fungi | (probably with apt, judging by the names of the packages you listed there) | 19:06 |
| fungi | `sudo apt install gawk libcurl4-gnutls-dev libmysqlclient-dev postgresql-client python-lxml python-zmq python3-all-dev uuid-dev` | 19:07 |
| fungi | something like that | 19:07 |
| fungi | without the quotes, of course | 19:07 |
| mridu | yeah. just now did the same. | 19:08 |
| mridu | again it came package missing. but finally command ran successfully | 19:08 |
| mridu | netifaces still fails bt | 19:09 |
| *** jamesmcarthur has joined #storyboard | 19:10 | |
| fungi | can you put the full output on paste.openstack.org and link it in here? | 19:17 |
| fungi | i can hopefully discern from the pip and/or gcc errors what's missing (and get our bindep.txt updated accordingly if it's wrong) | 19:17 |
| mridu | fungi: http://paste.openstack.org/show/708992/ here it is | 19:20 |
| fungi | mridu: looks like you also need the python-dev package installed | 19:21 |
| mridu | I install it using sudo apt-get install | 19:21 |
| fungi | right | 19:21 |
| fungi | our ci images probably have that preinstalled which is why we haven't noticed it missing from the bindep.txt but i'll add it | 19:21 |
| fungi | hrm, no it's in the bindep.txt already so you presumably have it installed | 19:22 |
| fungi | i wonder why gcc can't find it | 19:23 |
| tosky | uhm, it's also documented in the installation guide | 19:23 |
| fungi | oh, this is python3.6 complaining it can't find Python.h | 19:24 |
| mridu | I reinstalled python-dev. then re ran requirements.txt but it still fails with the same error | 19:24 |
| fungi | mridu: what tox env were you invoking? py36? | 19:25 |
| mridu | py35 | 19:26 |
| fungi | weird | 19:26 |
| fungi | it's doing -I/usr/include/python3.6m which indicates it's trying to build against python 3.6 i think | 19:27 |
| mridu | Just rechecked. I have python3.6 installed | 19:28 |
| mridu | so I guess py36 had to be done | 19:28 |
| fungi | and what version does `dpkg -l|grep python3-all-dev` say is installed? | 19:28 |
| mridu | no idea | 19:28 |
| mridu | have re run tox command now. | 19:28 |
| mridu | once it's done will check this | 19:28 |
| fungi | okay | 19:28 |
| fungi | my guess is that python3-all-dev installed headers for python 3.5.something so invoking `tox -e py36` failed to find any c headers for the running python | 19:29 |
| mridu | for 3.6 it says | 19:32 |
| mridu | http://paste.openstack.org/show/708995/ | 19:32 |
| fungi | that's even more strange. so when getting you're getting "netifaces.c:1:20: fatal error: Python.h: No such file or directory" and it's running gcc with "-I/usr/include/python3.6m" that's from invoking `tox -e py35` ? | 19:34 |
| fungi | mordred: any chance you've seen that ^ before? | 19:34 |
| fungi | i'm trying to imagine what would cause -e py35 to install netifaces in such a way that it attempts to link against headers for python 3.6 | 19:35 |
| mridu | I ran tox -e venv py36 | 19:38 |
| mridu | after checking that I am using 3.6 and not 35 | 19:39 |
| mridu | 3.5* | 19:39 |
| mordred | fungi: uhm. | 19:40 |
| mordred | fungi: why is py35 pulling in /usr/include/python3.6 ? | 19:40 |
| mordred | fungi: (I know you said that already ... I'm just impressed) | 19:41 |
| fungi | mridu: i thought the error 3.6 was goving you was "ERROR: InvocationError: could not find executable 'py36' | 19:41 |
| mridu | ERROR: InvocationError: could not find executable 'py36' yes | 19:42 |
| fungi | right, that suggests you _don't_ have python3.6 installed | 19:45 |
| fungi | that's the generic error from tox when it can't find a matching python interpreter version for the requested env name | 19:47 |
| mridu | strange. but on terminal when I write python and press enter | 19:49 |
| mridu | it gives python 3.6.2 | 19:50 |
| fungi | that is definitely strange | 19:51 |
| mridu | on deactivating virtualenv it gives python 2.7.12 | 19:53 |
| fungi | oh! you have done an activate in a virtualenv | 19:53 |
| fungi | this might have been seriously confusing tox | 19:53 |
| mridu | but on deactivating virtualenv and typing python3 as command | 19:54 |
| mridu | it gives python 3.6.2 | 19:54 |
| fungi | if your tox is installed in a virtualenv, you don't need to activate the virtualenv to run it, just invoke it by its full path... e.g., `/home/mridu/openstack-outreachy/storyboard/venv/bin/tox -e py36` | 19:55 |
| fungi | and see if that helps at all | 19:55 |
| mridu | a cd you mean? | 19:56 |
| fungi | don't cd, just run it by calling the full path to the tox executable | 19:57 |
| fungi | i have a similar setup (though for convenience i use a symlink to mine from a directory in by executable search path) | 19:58 |
| mridu | without cd | 20:00 |
| mridu | it gives an error | 20:00 |
| mridu | no such file or directory | 20:00 |
| fungi | i was guessing at the path to it (based on some earlier errors where it looked like you had a virtualenv created at /home/mridu/openstack-outreachy/storyboard/venv). what virtualenv had you activated when you installed tox? | 20:01 |
| fungi | i need to disappear for a bit and eat, but will be back soon | 20:09 |
| mridu | I had activated the same that you are referring to | 20:09 |
| fungi | so i guess that's not where you had installed tox | 20:11 |
| fungi | if you installed tox globally, then you can continue to run it normally now that you don't have a virtualenv activated | 20:11 |
| mridu | sure | 20:18 |
| mridu | but then it would use python2.7 I guess | 20:18 |
| tosky | iirc the version python used to run tox does not affect the test environments created and executed by tox | 20:29 |
| tosky | version of python* | 20:29 |
| tosky | so you should be able to safely install tox from packages and still run tox -e py35 | 20:29 |
| *** mcnanci has quit IRC | 20:33 | |
| mridu | should I run the tox venv command again? | 20:34 |
| dhellmann | diablo_rojo : maybe talk to bnemec about moving oslo over to storyboard next? | 20:34 |
| fungi | mridu: yes, try it again just as `tox -e py35` and see what it does | 20:36 |
| fungi | with no virtualenv activated | 20:37 |
| fungi | er, sorry, `tox -e py36` i guess | 20:37 |
| fungi | since that's what you seem to have installed | 20:37 |
| mridu | by default it says python2.7 | 20:37 |
| mridu | on typing python3 and enter it says 3.6 | 20:38 |
| tosky | unrelated to the problem above: if I create a story, shouldn't I be automatically subscribed to it? | 20:40 |
| mridu | on doing tox -e py36 got error http://paste.openstack.org/show/709008/ | 20:43 |
| mridu | :( | 20:44 |
| tosky | mridu: I've got a bit lost in the past history: did you say that python3-all-dev is installed? | 20:51 |
| mridu | I said python-all-dev is installed | 20:52 |
| mridu | damn does everything need to be done using python3 now | 20:52 |
| tosky | well, if you want to run py36 tests, you need the python3 headers :) | 20:53 |
| tosky | so please install python3-all-dev too | 20:53 |
| tosky | (if you just need to run the tests with python 2.7, you don't need it) | 20:53 |
| mridu | it shows http://paste.openstack.org/show/709016/ | 20:55 |
| mridu | no error but shows 0 upgraded, 0 newly installed | 20:55 |
| tosky | and it's the python3.5 version | 20:56 |
| fungi | this is why i requested the output from `dpkg -l|grep python3-all-dev` earlier | 20:56 |
| mridu | python3 and enter shows 3.6 on my terminal | 20:56 |
| fungi | yeah, your python headers package and interpreter aren't for the same versions | 20:56 |
| mridu | sorry in the middle of rest commands I missed out on it | 20:57 |
| mridu | just doing it | 20:57 |
| diablo_rojo | dhellmann, yeah I can definitely run the test migration and talk to ben | 20:57 |
| fungi | mridu: if you `sudo apt-get install python3` does that get you a python3.5 interpreter? | 20:58 |
| tosky | mridu: when you can, also, what does `which python3.6` say? And also, and sorry if you already wrote it, which version of ubuntu do you use? | 20:58 |
| mridu | fungi: http://paste.openstack.org/show/709017/ | 20:58 |
| mridu | which python gives the output as /usr/bin/python3 | 20:59 |
| mridu | which python3 | 20:59 |
| tosky | and `which python3.6` ? | 20:59 |
| fungi | try `which python3.6` like tosky saud | 20:59 |
| mridu | which python3.6 gives output /usr/bin/python3.6 | 20:59 |
| mridu | I am using ubuntu 16.04 | 21:00 |
| tosky | and `dpkg -S /usr/bin/python3.6` ? | 21:00 |
| * fungi bets this is the python3.6 package from backports | 21:00 | |
| tosky | yep, no python3.6 in xenial | 21:00 |
| fatema_ | which step was to create './etc/superusers.yaml' ?? | 21:01 |
| mridu | http://paste.openstack.org/show/709018/ | 21:01 |
| tosky | fatema_: this one: https://docs.openstack.org/infra/storyboard/install/development.html#optional-steps-seed-database-with-base-data | 21:01 |
| mridu | above mentioned link contains output of dpkg -S /usr/bin/python3.6 | 21:01 |
| tosky | mridu: can you please also execute this other command: | 21:02 |
| tosky | apt-cache policy python3.6-minimal | 21:02 |
| *** jamesmcarthur has quit IRC | 21:02 | |
| mridu | tosky: output of last command you mentioned is http://paste.openstack.org/show/709019/ | 21:03 |
| tosky | mridu: so apparently there is an additional repository added to the system | 21:04 |
| tosky | and python3.6 comes from that | 21:04 |
| mridu | oh.... | 21:04 |
| fungi | yeah, the "deadsnakes" ppa is a popular one for getting alternate python interpreter builds from | 21:04 |
| mridu | I think instead of python3.5 getting upgraded to 3.6 new python3.6 has got installed | 21:05 |
| tosky | do you need python3.6 specifically for something? | 21:05 |
| tosky | most of openstack projects target 3.5 | 21:05 |
| tosky | if you don't need for other stuff, I would suggest to remove python3.6-minimal | 21:05 |
| tosky | in one month, Ubuntu 18.04 is out, so in the worst case you can upgrade | 21:06 |
| mridu | No, I am as such now using any specific python3.6 features explicitly in any of my projects | 21:06 |
| mridu | not* | 21:06 |
| mridu | I am fine working with 3.5 as well no issues | 21:06 |
| tosky | oki, so it's simple then :) | 21:06 |
| tosky | (hopefully) | 21:06 |
| mridu | haha yeah I too hope so | 21:07 |
| fungi | i would suggest, if you don't need alternative python builds, deactivating the fkrull/deadsnakes ppa, purging the python3.6-minimal package, and then installing the python3 package (which should pull in the normal python3.5 interpreter for ubuntu 16.04) | 21:10 |
| mridu | how to do that? | 21:11 |
| *** jamesmcarthur has joined #storyboard | 21:13 | |
| fungi | this should deactivate the extra ppa: | 21:13 |
| fungi | sorry, just a sec, making sure i have the syntax correct | 21:15 |
| fungi | sudo add-apt-repository --remove ppa:fkrull/deadsnakes | 21:15 |
| fungi | after you do that, i would recommend removing the python3.6-minimal package with: | 21:16 |
| fungi | sudo apt-get purge python3.6-minimal | 21:16 |
| fungi | then update your sources with: | 21:16 |
| fungi | sudo apt-get update | 21:16 |
| fungi | and finally, install the normal python3 package via: | 21:16 |
| fungi | sudo apt-get install python3 | 21:16 |
| mridu | do I need to replace sudo add-apt-repository --remove ppa:fkrull/deadsnakes repository with something else in this command? | 21:17 |
| mridu | I mean replacing keyword repository | 21:18 |
| fungi | i don't believe so, though if you added that ppa through a different command than add-apt-repository we may need to use more manual methods to remove the sources.list entry for it | 21:18 |
| mridu | http://paste.openstack.org/show/709020/ | 21:19 |
| mridu | output of sudo add-apt-repository --remove ppa:fkrull/deadsnakes | 21:19 |
| fungi | weird, that should be provided by the software-properties-common package on xenial, which i thought was priority standard | 21:21 |
| fungi | sudo apt-get install software-properties-common | 21:21 |
| mridu | http://paste.openstack.org/show/709021/ | 21:23 |
| fungi | which add-apt-repository | 21:24 |
| fungi | oh! | 21:25 |
| fungi | i know the problem... that's a misleading error | 21:25 |
| fungi | the shebang line for /usr/bin/add-apt-repository is "#! /usr/bin/python3" and i bet it's /usr/bin/python3 which is what's missing | 21:25 |
| fungi | so see if you can `sudo apt-get install python3` first | 21:26 |
| mridu | http://paste.openstack.org/show/709022/ | 21:27 |
| fungi | oh, and you did also say earlier that `which python3` says /usr/bin/python3 so maybe it's a broken symlink. try `ls -l /usr/bin/python3` and we'll see what that points to | 21:30 |
| mridu | http://paste.openstack.org/show/709023/ | 21:31 |
| fungi | oh, right, alternatives redirection. so we need to then `ls -l /etc/alternatives/python3` and see what that's linked to in turn | 21:32 |
| mridu | http://paste.openstack.org/show/709025/ | 21:33 |
| fungi | and then `ls -l /usr/bin/python3.6` shows you a file? | 21:35 |
| mridu | http://paste.openstack.org/show/709026/ | 21:36 |
| fungi | okay, so now i'm extra baffled as to why you got the error you did in http://paste.openstack.org/show/709020/ | 21:37 |
| mridu | hmm... | 21:37 |
| mridu | I am surprised seeing what chaos can multiple versions create | 21:38 |
| fungi | yeah, messing with the default system python can get weird since some of the system tools are themselves written in python | 21:39 |
| fungi | so let's go abotu the ppa removal manually | 21:39 |
| fungi | do a `ls -l /etc/apt/sources.list.d/` and we'll see if it has its own file | 21:39 |
| mridu | http://paste.openstack.org/show/709028/ | 21:42 |
| fungi | there is is... so you can remove it now with `sudo rm /etc/apt/sources.list.d/fkrull-ubuntu-deadsnakes-xenial.list` | 21:43 |
| fungi | after that, update your package sources with `sudo apt-get update` | 21:45 |
| fungi | this wat the index will no longer see packages from that ppa as being available to you | 21:45 |
| fungi | er, after that | 21:45 |
| fungi | "this way" is what i meant to type, sorry. fingers are starting to give up on me | 21:47 |
| *** jamesmcarthur has quit IRC | 21:47 | |
| *** jamesmcarthur has joined #storyboard | 21:48 | |
| mridu | ran both the commands | 21:48 |
| mridu | no errors | 21:48 |
| fungi | now this is the point where we try installing python3.5 which will probably complain about downgrading the python3 package, but we'll see what it grumbles about | 21:49 |
| fungi | `sudo apt-get install python3.5` | 21:49 |
| mridu | http://paste.openstack.org/show/709038/ | 21:51 |
| fungi | okay, so it was already installed just not what /etc/alternatives was pointed to | 21:51 |
| mridu | ok | 21:52 |
| *** jamesmcarthur has quit IRC | 21:52 | |
| mridu | should I install requirements.txt now? | 21:52 |
| fungi | in that case, we can presumably just `sudo apt-get purge python3.6` and it will correct the alternative link (assuming it's been left at auto) | 21:53 |
| fungi | however it may now complain that its python3 package depends on that because it got an updated dummy package for it from the ppa. if so we can work around that too | 21:54 |
| mridu | cool. should I run the command you mentioned then | 21:54 |
| fungi | yes | 21:54 |
| fungi | that will uninstall the old python3.6 from the ppa, hopefully | 21:55 |
| mridu | done | 21:55 |
| fungi | if you run `python3 --version` now what does it say? | 21:55 |
| mridu | sad 3.6.2 | 21:56 |
| fungi | do `dpkg -l|grep python3.6` and see what packages it says you have matching that | 21:57 |
| fungi | it's possible the package providing the interpreter wasn't just called "python3.6" but maybe something like "python3.6.2" | 21:59 |
| mridu | http://paste.openstack.org/show/709048/ | 22:01 |
| fungi | oh, right-o... so `sudo apt-get purge python3.6-minimal libpython3.6-stdlib libpython3.6-minimal` | 22:03 |
| mridu | done | 22:06 |
| mridu | Ah.... now python3 gives no such file or directory | 22:07 |
| mridu | phew | 22:07 |
| fungi | do `sudo apt-get install python3==3.5.1-3` | 22:07 |
| fungi | that should hopefully set up the correct dummy package again, though we may still need to more directly correct the alternatives link for that executable name after | 22:08 |
| mridu | http://paste.openstack.org/show/709061/ | 22:11 |
| mridu | unable to locate package python3 | 22:11 |
| fungi | oh, sorry, it's probably just `sudo apt-get install python3=3.5.1-3` (not ==) | 22:13 |
| fungi | hard to remember the differences in syntax for package version specifiers across multiple package managers | 22:14 |
| mridu | http://paste.openstack.org/show/709072/ | 22:16 |
| fungi | okay, also a good sign, we have the version we wanted already there | 22:17 |
| fungi | so we should probably just correct the python3 alternative linking | 22:18 |
| mridu | what next? | 22:18 |
| fungi | aha, so checking on another ubuntu 16.04 system, the symlink from /usr/bin/python3 to python3.5 doesn't rely on the alternatives system | 22:20 |
| fungi | it's just directly provided by the python3-minimal package | 22:20 |
| fungi | so do `sudo apt-get install --reinstall python3-minimal` | 22:20 |
| fungi | that should hopefully replace the missing symlink that the deadsnakes ppa package blew away | 22:21 |
| mridu | done | 22:23 |
| fungi | does `python3 --version` say 3.5.1 now? | 22:23 |
| fatema_ | should the server still have 404 error eve I had ran the client ? | 22:25 |
| fatema_ | even after* | 22:25 |
| fungi | fatema_: the server shouldn't have a 404 error as long as you started the webclient. what url did you use to get to it? | 22:27 |
| mridu | 3.5.2 it is :) | 22:27 |
| fatema_ | http://127.0.0.1:8080/ | 22:28 |
| fungi | mridu: you should be ready to run tox again, but this time to `tox -e py35` | 22:29 |
| mridu | without virtualenv? | 22:30 |
| fungi | mridu: correct, tox will create a virtualenv automatically and install python dependencies (requirements and test-requirements) into it for you | 22:31 |
| mridu | cool | 22:32 |
| mridu | hey fungi, thanks a lot for helping out. here it's 4:02 am. Need to sleep. Once this command runs will ping again in morning. | 22:33 |
| fungi | diablo_rojo: SotK: i'm not super familiar with running storyboard-webclient standalone (only really ran it in production behind apache via wsgi). have any tips for fatema_? | 22:33 |
| fungi | mridu: oh! yes you should pick this up another time. i didn't mean to keep you up late | 22:33 |
| mridu | haha. no problem. I actually wanted to complete it :) | 22:33 |
| persia | fungi: fatema_: I've only done it a couple times, but my memory is that one points the browser at the address configured in grunt, and it loads. | 22:33 |
| fungi | fatema_: presumably the webclient daemon logs somewhere, so if it's actually returning a 404 error page there should hopefully be a corresponding error log entry for that request | 22:34 |
| mridu | it has ran the tests it seems. lots of errors. let's debug tomorrow | 22:36 |
| persia | fatema_: To confirm, if you visit http://127.0.0.1:8080/aip/v1 do you get an API response? | 22:36 |
| mridu | bye. thanks again :) | 22:36 |
| persia | (https is expected to fail in a development environment) | 22:36 |
| fungi | mridu: you're welcome. thanks for pitching in! | 22:36 |
| persia | fatema_: If so, I *think* http://127.0.0.1:8080/ should load the javascript UI (if I'm reading Gruntfile.js correctly) | 22:39 |
| tosky | uhm, doesn't the the web client listens to port 9000 by default? | 22:39 |
| fungi | oh, yes if 8080 is the api listening socket then i wouldn't be surprised at all by a 404 response to get / | 22:40 |
| persia | tosky: Yes. Thank you. I'm not reading it correctly. | 22:40 |
| persia | http://127.0.0.1:8080/api/v1/ should return an API response and http://127.0.0.1:9000/ should return the Javascript UI. | 22:40 |
| tosky | fatema_: how did you start the web client? | 22:40 |
| tosky | fatema_: also, what does it happen if you go to http://127.0.0.1:9000/ ? | 22:41 |
| fatema_ | The client is on port 9000 | 22:43 |
| fatema_ | and it's working | 22:43 |
| fatema_ | not logged in | 22:43 |
| fatema_ | but working | 22:43 |
| fatema_ | but 8080 is giving me 404 server not found | 22:44 |
| persia | So, when the client loads on 9000, it should connect to the Grunt proxy that connects to 8080 and let things work. | 22:47 |
| persia | It you run `netstat -ntl | grep 8080` do you see a response? | 22:48 |
| diablo_rojo | fungi, I fear I have as much or less knowledge than you. | 22:49 |
| *** fatema_ has quit IRC | 22:54 | |
| SotK | http://127.0.0.1:9000/ will take you to the webclient, https://127.0.0.1:8080/ is the root of the API, a 404 there is expected as we don't actually return anything there | 23:24 |
| SotK | erm, s/https/http/ | 23:24 |
| SotK | http://127.0.0.1:8080/v1/stories should be an xml document that looks something like `<result/>` in-browser usually, unless you've created some stories | 23:26 |
| SotK | the available API endpoints are documented here: https://docs.openstack.org/infra/storyboard/webapi/v1.html | 23:26 |
| SotK | the API is also exposed at http://127.0.0.1:9000/api/ (i.e. that is equivalent to http://127.0.0.1:8080/) | 23:28 |
| SotK | I feel like I should probably add a basic explanation of that and related stuff to the developer docs | 23:33 |
| *** jtomasek has quit IRC | 23:42 | |
| diablo_rojo | I think fatema_ is gone sadly :/ But yes, put a patch to the developer docs and I will gladly review :) | 23:42 |
| *** tosky has quit IRC | 23:43 | |
| diablo_rojo | fungi, looks like osc is another one that hits the same issue as Mistral and Heat. | 23:47 |
| diablo_rojo | Their test migration fails today. | 23:48 |
| SotK | :/ I always forget I have joins/parts ignored | 23:49 |
| SotK | I'll create a patch tomorrow when I should finally have some free time back | 23:49 |
| diablo_rojo | SotK, cool. I will try to remember to keep an eye out. | 23:49 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!