Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2016-11-08

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:13 fedruantine joined #fuel
00:14 johnavp19891 joined #fuel
00:28 Egyptian[Home] joined #fuel
00:46 Julien-zte joined #fuel
00:49 Egyptian[Home] joined #fuel
00:54 masterjcool joined #fuel
01:00 Samos123 joined #fuel
01:48 johnavp1989 joined #fuel
01:52 sam_wan joined #fuel
02:30 diogogmt joined #fuel
03:06 raunak joined #fuel
03:17 Egyptian[Home] joined #fuel
03:24 Egyptian[Home] joined #fuel
13:06 ilbot3 joined #fuel
13:06 Topic for #fuel is now Fuel 9.0 (Mitaka) https://www.fuel-infra.org/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
13:17 masterjcool aglarendil: sorry, not sure what you mean. manifest path?
13:18 Liuqing joined #fuel
13:20 Liuqing joined #fuel
13:22 aglarendil puppet manifest path: it should be something like /etc/puppet/shell_manifests/rsync_core_puppet_manifest.pp
13:28 masterjcool aglarendil: So if I run that it will essentially try to redeploy, and this way we can maybe see where it fails?
13:36 aglarendil it will basically run rsync and you will see where it fails
13:39 masterjcool aglarendil: Won't this further break this node?
13:39 masterjcool I mean the node is in error state, but the vms on it are still working.
13:40 aglarendil nope. It will just rsync puppet manifests if you do not run anything else
13:42 khamtamtun joined #fuel
13:50 masterjcool Running the command now. It's mostly loading facts but now hangs (or just takes a long time). Last thing it did was loading facts from iptables_version.rb.
13:50 masterjcool I'll wait for a bit to see if it spits out more.
13:51 masterjcool aglarendil: And what if the job just succeeded? No warnings or errors
14:11 Liuqing joined #fuel
14:13 ralfba hey - aglarendil / sorry, no experience with docker, how am i supposed to do it?
14:14 ralfba what i want to achieve is just a trusty-bootstrap with an actual or latest kernel
14:14 ralfba i am utilizing usb-connected ethernet dongles within my dev-env, and those don't get recognized under the older kernels
14:21 ralfba_ joined #fuel
14:46 Kimmo__ joined #fuel
14:49 kaslcrof joined #fuel
15:05 Julien-zte joined #fuel
15:14 masterjcool What are reasons for the task "rsync_core_puppet" to fail?
15:14 masterjcool I confirmed I can reach all my nodes from the master node and other way around.
15:21 dmitryme Hey library team, can you please review a couple changes to RabbitMQ OCF script https://review.openstack.org/#/c/378600/ and https://review.openstack.org/#/c/384412/ They are hanging on the review for a couple weeks and I’d like to see them in 9.2.
15:29 aglarendil ralfba_: well, docker is just an example - you need just to test the set of repositories that you provided with a vanilla ubuntu trusty bootstrap chroot. you can use any chroot technology of your choice
15:29 aglarendil masterjcool: I do not know - we need to figure it out. So what does running of rsync manually tell you?
15:37 diogogmt joined #fuel
16:14 Julien-zte joined #fuel
16:15 Julien-zte joined #fuel
16:15 Julien-zte joined #fuel
16:16 Julien-zte joined #fuel
16:17 Julien-zte joined #fuel
16:18 Julien-zte joined #fuel
16:19 Julien-zte joined #fuel
16:19 Julien-zte joined #fuel
16:23 vkulanov joined #fuel
16:33 soerens joined #fuel
17:02 Ahharu joined #fuel
17:02 Ahharu @here is there any way to get verbose output for fuel upgrade?
17:02 Ahharu its been quite a long time and it is stuck at INFO  [alembic.runtime.migration] Running upgrade 675105097a69 -> f2314e5d63c9, Fuel 9.1
17:04 evgenyl @ogelbukh ^
17:05 evgenyl Ahharu: Hm, probably something locked the database.
17:05 evgenyl Ahharu: are you sure that you stopped all fuel-web related services?
17:05 Ahharu https://docs.mirantis.com/openstack/fuel/fuel-9.1/release-notes/update-product.html don't say anything about stopping
17:07 evgenyl Ahharu: ok, let's wait for ogelbukh's answer, I'm wondering if the script which runs update, stops the services not to lock the database.
17:07 evgenyl Ahharu: could you please run `ps aux` and copy the output to http://paste.openstack.org/ ?
17:09 Ahharu I followed the answer here
17:09 Ahharu https://ask.openstack.org/en/question/98002/mirantis-fuel-9-update-to-91-result-in-an-error/
17:09 Ahharu and it worked
17:09 Ahharu but fuel fuel-version still says '9.0' which is weird
17:10 ogelbukh evgenyl: it's another update script, not octane
17:10 Ahharu nailgun
17:11 ogelbukh evgenyl: I can't tell much about it, unfortunately
17:33 Zer0Byte__ joined #fuel
17:43 Ahharu how can I force stop a task?
17:56 Miouge joined #fuel
18:02 aglarendil Ahharu: you can stop the deployment of the environment by running fuel stop --env <env_id>
18:02 aglarendil it will wait for puppet to finish execution
18:02 Ahharu it got stuck
18:03 Ahharu and I cannot remove the task
18:03 Ahharu or the env
18:03 aglarendil Ahharu: use fuel stop --env 2
18:03 aglarendil Ahharu: use fuel stop --env <env_id>
18:03 Ahharu 400 Client Error: Bad Request for url: http://10.20.0.2:8000/api/v1/clusters/17/stop_deployment/ (Stopping deployment task is already launched) [root@fuel fuel.domain.tld]#
18:03 Ahharu there is a stuck task like this
18:03 Ahharu 1069 | running | deploy             | 17      | 100      | ef93fded-323a-478c-953a-7366fcea8584
18:03 Ahharu after the MOS 9.1 update
18:04 Ahharu can I wipe it somehow?
18:04 aglarendil okay, so you can see which particular deployment tasks are being run
18:04 aglarendil by using
18:04 aglarendil fuel2 task history show <env_id> --status running
18:04 Ahharu 1073 | running | stop_deployment    | 17      |          | 28a23af0-f146-4578-b918-7d7f2a96f684
18:04 Ahharu and previous one
18:04 Ahharu can't stop them
18:04 aglarendil it will show you which deployment tasks are running on which nodes
18:04 Ahharu 400 Client Error: Bad Request for url: http://10.20.0.2:8000/api/v1/transactions/1073/?force=0 (You cannot delete running task manually)
18:05 aglarendil Ahharu: let's pause for a bit and figure out what went wrong
18:05 aglarendil could you please fetch the list of deployment tasks that are running?
18:05 aglarendil with fuel2 task history show <deployment_supertask> --status running?
18:06 aglarendil deployment_supertask is the id of 'deployment' task right after fuel2 task list
18:06 aglarendil it is 1071 apparently
18:14 Miouge joined #fuel
18:37 Miouge joined #fuel
19:15 jobewan joined #fuel
19:25 zhsj joined #fuel
19:39 Miouge joined #fuel
20:20 Miouge joined #fuel
20:29 Zer0Byte__ joined #fuel
20:53 Zer0Byte__ joined #fuel
22:11 Samos123 joined #fuel
22:43 Egyptian[Home] joined #fuel
22:54 cr0wrx joined #fuel
22:56 cr0wrx Hi Fuel magicians! Anyone know how failure is handled in fuel? what happens if you try and deploy a controller and it fails - all nodes switch to the 'error' state for me. I'm not sure what happens if I hit deploy again - will my existing nodes be wiped and redone if they are flagged as error?
22:56 cr0wrx fuel 8 which just has 1 provision/deploy step, since I know some of that has changed in 9

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary