Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2017-01-10

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

All times shown according to UTC.

Time Nick Message
00:20 GMAzrael joined #fuel
00:31 Julien-zte joined #fuel
00:44 Egyptian[Home] joined #fuel
01:40 Egyptian[Home] joined #fuel
01:46 xarses joined #fuel
02:46 raunak joined #fuel
02:48 ilbot3 joined #fuel
02:48 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/
02:58 GMAzrael joined #fuel
03:35 raunak joined #fuel
03:53 mdnadeem joined #fuel
04:07 Egyptian[Home] joined #fuel
04:20 Connor__ joined #fuel
04:22 Connor joined #fuel
04:28 Connor__ I'm trying to deploy a 3 node lab environment with fuel v10. I keep getting dependency issues with Task[primary-keystone/1] I can't seem to find what dependency that is causing the errors... I may be looking in the wrong places as I've been doing this while I've been extremely tired... Any thoughts on what may be the cause? I'm assuming I'm missing something really simple but am over thinking it.
04:43 Chandra joined #fuel
05:06 raunak joined #fuel
05:25 Pluto joined #fuel
05:25 Pluto hello, there was a bug and a workaround to have mcollective starting on metal nodes...
05:26 Pluto because when you deploy in the bootstrap mcollective does not run and makes the network-test fail
05:26 Pluto can anyone address me to that bug/workaround?
05:26 Pluto I cannot start the service manually
05:26 Pluto root@bootstrap:~# systemctl status mcollective.service ● mcollective.service    Loaded: masked (/dev/null; bad)    Active: inactive (dead)  Jan 10 05:23:17 bootstrap systemd[1]: mcollective.service: Trying to enqueue job mcollective.service/restart/replace Warning: mcollective.service changed on disk. Run 'systemctl daemon-reload' to reload units.
05:27 AlexeyAbashkin joined #fuel
05:31 Pluto anyone can help?
05:47 xarses joined #fuel
05:56 Pluto unmasking does not work, restarting the service does not work
05:56 Pluto it looks almost the same to this bug (still not fixed in 10.0) https://bugs.launchpad.net/fuel/+bug/1455489
05:56 Pluto but the workaround of restarting mcollective does not work
06:05 xarses_ joined #fuel
06:06 xarses_ joined #fuel
06:34 raunak joined #fuel
07:09 AlexeyAbashkin joined #fuel
07:26 veena igorbelikov, Hi
07:27 veena SergK, Hi
08:27 xek joined #fuel
08:28 DavidRama joined #fuel
08:33 meshugga ok, so i've run fuel, but it's now (happily) in "partially deployed" state. there don't seem to be any openstack packages installed. also, there is no "deploy" button.
08:33 meshugga how do i find out what's missing for a complete openstack deployment?
08:33 meshugga (newton release, 10.0 community edition)
08:35 meshugga For Pluto, when he comes back: that problem went away for me when I regenerated the bootstrap iso and changed the kernel command line to   extend_kopts: "biosdevname=0 net.ifnames=1 ignore_loglevel log_buf_len=50M print_fatal_signals=1 LOGLEVEL=1"
08:35 meshugga extend_kopts: "biosdevname=0 net.ifnames=1 ignore_loglevel log_buf_len=50M print_fatal_signals=1 LOGLEVEL=1"
08:35 meshugga ouch, sorry
09:25 meshugga also, is there tooling to explore/debug the workflow graph?
09:35 abramley joined #fuel
09:37 akasatkin_ joined #fuel
09:37 holser_ joined #fuel
09:38 bapalm joined #fuel
09:38 asilenkov joined #fuel
09:38 jaranovich_ joined #fuel
09:39 meshugga_ joined #fuel
09:39 jianghuaw joined #fuel
09:39 zimboboyd joined #fuel
09:40 meow-nofer_ joined #fuel
09:41 fzhadaev akasatkin_, ikalnytskyi: could you please review/merge https://review.openstack.org/#/c/415430/ ?
09:41 evgenyl joined #fuel
09:42 Seafire joined #fuel
09:44 Seafire Hello fuelers, is there any way to change the MTU size in a deployed environment? I can easily do it manually on each node, but as soon as I reboot them they go back to the old value..
09:46 serverascode joined #fuel
10:07 winstonsullen joined #fuel
10:42 Julien-zte joined #fuel
11:51 Kdecherf Seafire: you should check the corresponding mtu values in the neutron ml2 plugin
12:01 GMAzrael joined #fuel
12:04 ekosareva joined #fuel
12:04 ekosareva_ joined #fuel
12:09 winstonsullen joined #fuel
12:33 DavidRama left #fuel
12:53 veena_ joined #fuel
13:28 GMAzrael joined #fuel
13:42 Seafire Kdecherf: thank you for your reply...in the end I was able to change it via the Fuel CLI (first by downloading the env settings and uploading them after having modified the MTU parameter)
13:42 Kdecherf Seafire: and the parameter was propagated after the initial deployment of the env?
13:42 Seafire yes
13:43 Seafire I get this in the Fuel UI: "Some deployment parameters for this environment have been modified using the Fuel CLI. Changes from the Fuel CLI precede the changes made using the Fuel web interface. Proceed with caution."
13:48 Seafire Now I'm facing another problem...The mysql cluster isn't running correctly I had this before in a previous environment, it happens after one Controller node crashes or gets rebooted. With Pacemaker I get the following error: p_mysqld_start_0 on node-61.vptt.ch 'insufficient privileges' (4): call=524, status=complete, exitreason='none'
13:50 Seafire has anyone had this problem before?
15:12 Julien-zte joined #fuel
15:16 AlexeyAbashkin joined #fuel
15:29 zinovik joined #fuel
15:43 Sketch joined #fuel
15:57 xarses joined #fuel
16:01 raunak joined #fuel
16:10 raunak joined #fuel
16:39 AlexAvadanii joined #fuel
16:47 thiagolib joined #fuel
17:07 raunak joined #fuel
17:15 jose-phillips joined #fuel
17:36 terje joined #fuel
17:37 terje hi, new fuel install and the UI isn't starting for me for some reason. Any suggestions on troubleshooting it?
17:37 terje the webUI that is
17:47 evgenyl terje: open js console in chrome and look for exceptions.
17:47 terje before I even get there..
17:48 evgenyl terje: Also what do you mean by "isn't starting"?
17:48 terje well, there's nothing listening on port 8443 or 8080
17:48 evgenyl terje: It's served by nginx, check that it's up and healthy.
17:48 terje it is not
17:48 terje (up and healthy)
17:49 johnavp1989 joined #fuel
17:50 terje I think perhaps puppet failed originally when I ran bootstrap_admin_node.sh
17:50 terje re-running
17:56 terje yea, that was it. I setup the network in fuelmenu, then re-ran bootstrap_admin_node.sh and all sorts services came up.
17:58 fatdragon joined #fuel
18:09 AlexeyAbashkin joined #fuel
18:53 xarses_ joined #fuel
20:05 AlexeyAbashkin joined #fuel
20:32 skolekonov joined #fuel
20:38 Connor Has anyone had dependency issues upon inital node deployment? I have a new fuel 10 install that when I go to deploy I get deployment failure at Task[primary-keystone/1] All I can find in the logs are dependency related errors but can't seem to track down wheat dependency is actually missing.
20:45 goldenfri I had that same problem, never figured out how to fix it
20:50 AlexeyAbashkin joined #fuel
20:53 Connor I've had it on 9 (after a successful deployment (different task)) and now on inital deployment... its starting to turn my management away from the idea of using Fuel for an up coming deployment. Which sucks IMO.
20:59 karthike1991 joined #fuel
21:00 karthike1991 what is fuel-noop-fixtures and what is noop test framework??
21:09 GMAzrael joined #fuel
21:12 Obi-Wan joined #fuel
21:34 jose-phillips joined #fuel
21:41 AlexeyAbashkin joined #fuel
22:26 jobewan joined #fuel
23:22 pbrzozowski joined #fuel
23:22 zefciu joined #fuel
23:22 dpyzhov joined #fuel
23:23 alex_didenko joined #fuel
23:24 asaprykin joined #fuel
23:26 skath joined #fuel
23:36 fzhadaev joined #fuel
23:39 holser_ joined #fuel
23:50 Egyptian[Home] joined #fuel

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