Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-10-28

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

All times shown according to UTC.

Time Nick Message
00:14 mattgriffin joined #fuel
00:49 rmoe joined #fuel
01:13 Longgeek joined #fuel
01:16 xarses joined #fuel
02:26 emagana joined #fuel
03:04 emagana joined #fuel
03:21 Longgeek joined #fuel
03:25 emagana joined #fuel
04:23 ArminderS joined #fuel
04:56 anand_ts joined #fuel
05:26 monester_laptop joined #fuel
05:39 Longgeek joined #fuel
06:45 HeOS joined #fuel
07:01 e0ne joined #fuel
07:38 e0ne joined #fuel
07:50 e0ne joined #fuel
07:50 dancn joined #fuel
07:52 helgin joined #fuel
08:04 pasquier-s joined #fuel
08:10 HeOS joined #fuel
08:22 warpc__ joined #fuel
08:23 hyperbaba joined #fuel
08:34 pal_bth joined #fuel
08:36 hyperbaba Hi there, I know this is not to place to ask but how do I create a "reseller" in horizon. I mean a user with quota and privilege to create users and follow the quota limitations of the "reseller"?
08:50 bhi Hello again,
08:51 bhi I had an issue yesterday and asked a lot of stuff.
08:54 Longgeek joined #fuel
08:55 bhi The UI of Mirantis 5.1 Fuel is not starting properly and the docker-postgres log says the login for user nailgun failed.
08:55 bhi I have Mirantis 5.1 build_number: "11" build_id: "2014-09-17_21-40-34"
08:56 bhi Is this the actual stable version?
08:56 baboune joined #fuel
08:57 baboune Fuel 5.1, centOS, neutron vlan, when launching an instance: "2014-10-28 13:54:30,876 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Request timed out. (timeout=50.0)]", metadata agent is running.  config seems ok. What could be wrong?
09:02 baboune neutron agent-list -> f5f30136-0159-4186-a4de-337c29128e4a | Metadata agent     | node-48.rnd.ki.sw.ericsson.se | :-)   | True           |
09:03 baboune we have not touched any of the generated config files for neutron, and this happens on every deployment
09:04 baboune when logged on the controller though I can see: wget http://169.254.169.254/2009-04-04/meta-data/instance-id --2014-10-28 10:05:11--  http://169.254.169.254/2009-04-04/meta-data/instance-id Connecting to 169.254.169.254:80... failed: No route to host.
09:05 baboune is that a known issue?
09:07 erct joined #fuel
09:10 azemlyanov joined #fuel
09:11 kaliya bhi: yes, 5.1 is the stable now
09:12 bhi Okay and the build id 2014-09-17_21-40-34 is correct
09:12 bhi ?
09:12 kaliya bhi: seems a community ISO
09:12 bhi Maybe I accidentially installed a beta version
09:12 kaliya bhi: did you download it from software.mirantis.com or from jenkins?
09:13 bhi from mirantis
09:13 bhi the iso file
09:14 bhi So a reinstall with a fresh ISO wouldn't help
09:14 kaliya bhi: dockerctl check shows all containers are fine?
09:15 bhi Yes
09:15 bhi It takes a while to curl the naily_service
09:16 bhi I also restarted and rebuilt all containers
09:17 kaliya and still doesn't work? please try `fuel nodes` to assure the APIs are working
09:19 bhi fuel nodes returns 502 bad gateway
09:20 kaliya bhi: did you run fuelmenu?
09:20 bhi Yes
09:20 kaliya which settings did you change?
09:20 bhi I can connect from outside via ssh
09:21 bhi all three nics
09:21 kaliya please pastebin your `docker ps`
09:23 bhi http://paste.openstack.org/show/125790/
09:24 bhi I had to issue fuelmenu manually after the installation.
09:24 kaliya did you restart keystone?
09:25 kaliya did you run `build all` again?
09:25 kaliya what's your hardware?
09:25 bhi no I didn't
09:25 bhi I'll give it a try
09:28 bhi I restarted
09:28 bhi sthere is still no UI I only see an animated cloud but no login
09:30 kaliya crazy
09:30 kaliya bhi: let's look in /var/log/docker
09:30 kaliya if something strange is logged
09:33 bhi There is nothing strange
09:33 bhi I'll be right back, have a meeting
09:38 baboune no ideas on meta data problem?  Why can it not find the route?
09:39 kaliya baboune: do you suspect some network issue?
09:46 baboune kaliya: it is possible but I dont know how to troubleshoot is.  This address and its resolution remains a bit mysterious
09:46 baboune it should locally resolve to the metadata agent
09:53 aliemieshko_ hello, how can i add new puppet module ?
09:54 kaliya aliemieshko_: http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html?highlight=packages#adding-new-modules
09:55 hyperbaba I am trying to connect "Portal" app from stackops to newly deployed openstack (from 5.1 fuel).  The problem is with identity service. I was using admin user to connect "portal" but it fails . What port shoud i use for identity service for admin 5000 or 35357?
09:56 aliemieshko_ Yes that's right but where i should add a line like this:   “tools”: [ “htop”,  “tmux”,]
09:56 pasquier-s joined #fuel
10:01 kaliya aliemieshko_: it's written below
10:01 ddmitriev joined #fuel
10:04 Longgeek joined #fuel
10:09 aliemieshko_ if i add :  “tools”: [ “htop”, “tmux”,] in for example compute_1.yaml and then run: fuel --env 1 deployment upload , i get error
10:09 aliemieshko_ what i do wrong
10:10 bhi I'm back.
10:11 bhi A colleague told me that he had a similiar issue with fuel and that it worked for him if the fuelmanu was run during the installation instead of afterwards.
10:12 bhi I suggest to try this. I'll give you an update once I'm through
10:14 kaliya thanks bhi
10:14 kaliya aliemieshko_: better to ask in #fuel-dev
10:14 aliemieshko_ ok, thx
10:18 f13o_f13o joined #fuel
10:23 adanin joined #fuel
10:34 e0ne joined #fuel
10:39 teran joined #fuel
10:44 teran_ joined #fuel
10:59 teran joined #fuel
11:01 teran_ joined #fuel
11:02 helgin in HA env. shoud I run neutron-metadata-agen or nova-metadata-api ?
11:02 teran_ joined #fuel
11:09 baboune bhi: we always install fuel with the fuelmenu=on option in the fuel install
11:09 monester_laptop joined #fuel
11:10 baboune bhi: And we avoid modifying any fuelmenu options untill all the containers are deployed.  Fuelmenu tends to freeze otherwise
11:17 baboune bhi: Sorry some typos above, we do the following:     1. Create an usb with the Mirantis fuel ISO (make it bootable). Refer to Mirantis documentation for doing this.     2. Press the <TAB> key on the very first installation screen which says "Welcome to Fuel Installer!" and update the kernel option to have 'showmenu=yes'     3. After rebooting the installation configuration menu will be prompt, quit w/o changing anything
11:24 baboune anout the metadata agent pb: There is following method in nova/network/linux_net.py, but it's only called while using Flat DHCP Manager or VLAN Manager.def metadata_forward():     """Create forwarding rule for metadata"""     _confirm_rule("PREROUTING", "-t nat -s 0.0.0.0/0 "              "-d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT "              "--to-destination %s:%s" % (FLAGS.ec2_dmz_host, FLAGS.ec2_port))
11:24 baboune Should those rules be added on neutron vlan?
11:36 baboune It might be related to this: https://answers.launchpad.net/nova/+question/145062, and if so it should tied to the openstack config/nw and thus a fuel issue
11:46 HeOS joined #fuel
12:01 teran joined #fuel
12:02 HeOS joined #fuel
13:08 monester_laptop joined #fuel
13:10 erct1 joined #fuel
13:19 ilbot3 joined #fuel
13:19 Topic for #fuel is now Fuel 5.1 for Openstack: https://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
13:22 teran_ joined #fuel
13:22 Guest____ joined #fuel
13:22 ArminderS joined #fuel
13:34 thehybridtech joined #fuel
13:35 bleachin joined #fuel
13:49 TVR_ joined #fuel
13:52 jobewan joined #fuel
13:59 mpetason joined #fuel
14:02 bleachin joined #fuel
14:12 ArminderS joined #fuel
14:20 dklepikov joined #fuel
14:39 stamak joined #fuel
14:49 mattgriffin joined #fuel
14:59 bleachin joined #fuel
15:05 blahRus joined #fuel
15:17 xarses joined #fuel
15:20 bhi fuelmenu=on and schowmenu=yes did the trick. Last Time I missed the time period to interrupt and I thought I could do the config afterwards.
15:22 bhi also this time fresh docker images were downloaded from the net, which might have failed the last time due to wrong network setting.
15:22 bhi Thanks for your help!
15:27 bleachin1 joined #fuel
15:55 rmoe joined #fuel
15:55 xarses joined #fuel
16:15 emagana joined #fuel
16:56 artem_panchenko joined #fuel
17:02 jobewan joined #fuel
17:16 xarses bhi: the docker images are stored on the iso, so that should have not been a problem. sometimes they don't build correctly.
17:16 mattgriffin joined #fuel
17:42 artem_panchenko joined #fuel
17:47 blahRus joined #fuel
17:53 emagana joined #fuel
17:54 cfelix joined #fuel
17:57 emagana_ joined #fuel
18:16 jobewan joined #fuel
18:38 angdraug joined #fuel
19:03 emagana joined #fuel
19:05 emagana_ joined #fuel
19:12 artem_panchenko left #fuel
19:12 artem_panchenko joined #fuel
19:22 jobewan joined #fuel
19:29 teran joined #fuel
19:38 bleachin joined #fuel
20:00 HeOS joined #fuel
20:02 emagana joined #fuel
20:11 emagana joined #fuel
20:14 emagana_ joined #fuel
20:31 bleachin joined #fuel
20:46 e0ne joined #fuel
20:52 teran joined #fuel
20:56 bleachin joined #fuel
21:15 adanin joined #fuel
21:20 jobewan joined #fuel
21:32 jetole joined #fuel
21:35 jetole Hey guys. The timeout time for the dashboard seems too low to me. I set SESSION_TIMEOUT in /etc/openstack-dashboard/local_settings and I tested to verify this was valid (setting a low value and seeing it log me out quickly) but a high value doesn't seem to be affecting it and I have read this may have something to do with Keystone but I am not sure what
21:38 emagana joined #fuel
21:41 emagana_ joined #fuel
21:51 teran joined #fuel
22:09 mihgen jetole: hi, can you report a bug about it?
22:15 e0ne joined #fuel
22:17 jetole I don't think it's a bug
22:17 jetole mihgen: it's just the auto logout time is too short for my preference
22:17 jetole horizon but I think it may be from the keystone auth token expiration. I'm doing some googling and trying to find out
22:33 mihgen jetole: ok. how long is it now? If it affects user experience, it's something we want to fix anyway
22:33 mihgen regardless of whether it's horizon or keystone thing
22:34 jetole mihgen: I think it's about 30 minutes. We're doing some v2v migration and conversion and there have been some issues with being auto logged out during file upload
22:34 jetole mihgen: IIRC the default auto logout for Django is two weeks but I don't know much about how this affects keystone
22:36 mihgen jetole: 30 min is short to me too
22:36 mihgen I'm wondering if it's Fuel confuguration or common upstream openstack issue
22:36 jetole mihgen: if it matters, I'm using mirantis / fuel
22:36 jetole oh wait...
22:36 jetole this is the #fuel room
22:36 jetole lol
22:36 mihgen =)
22:36 jetole I asked in two chans
22:37 jetole I set the expiration for keystone to 86400 (one day) and will let you know if this has resolved it
22:37 jetole but need a while to know for sure
22:55 emagana joined #fuel
22:58 angdraug joined #fuel
23:12 mattgriffin joined #fuel
23:12 teran_ joined #fuel
23:17 emagana joined #fuel
23:21 emagana_ joined #fuel
23:23 emagana joined #fuel
23:28 emagana joined #fuel
23:30 teran joined #fuel
23:37 artem_panchenko joined #fuel
23:48 artem_panchenko joined #fuel

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