Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2016-04-20

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

All times shown according to UTC.

Time Nick Message
00:28 fatdragon joined #fuel
00:38 rongze joined #fuel
01:09 adam_g xarses, you still around?
01:21 fatdragon joined #fuel
01:58 kur1j joined #fuel
02:11 rongze joined #fuel
02:32 kur1j is it possible to upgrade/update Sahara versions of HDP?
02:37 fedexo joined #fuel
03:17 rongze joined #fuel
04:35 javeriak joined #fuel
05:45 zefciu joined #fuel
05:50 javeriak joined #fuel
06:00 kszukielojc joined #fuel
06:03 javeriak joined #fuel
06:38 e0ne joined #fuel
06:44 e0ne joined #fuel
06:45 e0ne_ joined #fuel
06:48 zefciu joined #fuel
06:52 ramon joined #fuel
06:54 Guest57587 hi!
06:54 Guest57587 left #fuel
07:00 permalac joined #fuel
07:01 magicboiz joined #fuel
07:21 rongze_ joined #fuel
07:29 fatdragon joined #fuel
07:29 LanceHaig joined #fuel
08:02 elo joined #fuel
08:12 HeOS joined #fuel
08:32 eric_lopez joined #fuel
08:34 magicboiz joined #fuel
08:35 yassine joined #fuel
08:36 elo joined #fuel
08:58 eric_lopez joined #fuel
08:59 javeriak joined #fuel
09:20 hkominos joined #fuel
09:29 fatdragon joined #fuel
09:52 magicboiz joined #fuel
10:04 abohanif joined #fuel
10:04 abohanif hi all..
10:05 abohanif wanna ask, what is the limitations using mirantis fuel 8.0 without subscription to mirantis?
10:09 magicboiz joined #fuel
10:21 rongze joined #fuel
10:22 hkominos technically i think there is no limitation
10:22 hkominos its just about the support i thikn
10:22 rongze_ joined #fuel
10:46 hkominos joined #fuel
10:57 abohanif thanks hkominos
11:04 rongze joined #fuel
11:10 elo joined #fuel
11:30 fatdragon joined #fuel
11:58 javeriak joined #fuel
12:59 claflico joined #fuel
13:15 byrdog55 joined #fuel
13:18 kdavyd joined #fuel
13:31 fatdragon joined #fuel
13:33 jobewan joined #fuel
14:12 v1k0d3n joined #fuel
14:21 xarses joined #fuel
14:24 gomarivera joined #fuel
14:31 srwilkers joined #fuel
14:41 magicboiz joined #fuel
14:56 fatdragon joined #fuel
14:59 blahRus joined #fuel
15:02 claflico joined #fuel
15:18 e0ne joined #fuel
15:27 thingee left #fuel
15:31 Mike_G__ joined #fuel
15:37 xarses adam_g: sorry, didn't see that
16:08 magicboiz joined #fuel
16:12 esikachev joined #fuel
16:15 magicboiz joined #fuel
16:15 esikachev Hi all! I have a one question about deploying fuel. Can we disable SWAP as default on computes/controllers? Many services cannot correctly work if SWAP used
16:58 thumpba joined #fuel
17:06 javeriak joined #fuel
17:11 adam_g http://paste.openstack.org/show/494859/
17:11 adam_g my deploys keep failing in keystone.pp, tho sometimes they do make it through
17:11 adam_g thats the error-does it look like something obvious to anyone?
17:12 adam_g 2016-04-20 17:05:05 WARNING [793] Puppet agent 4 didn't respond within the allotted time
17:12 mwhahaha adam_g: is there something in the puppet logs?
17:14 adam_g mwhahaha, nothing that looks like an error
17:14 adam_g does the astute log mean that the actual puppet agent process timed out with a response, or the application of the manifest took too long?
17:15 mwhahaha well it might have exceeded the 3600minute time
17:15 mwhahaha or the response got lost
17:15 mwhahaha so you'd need to check the mcollective logs as well
17:16 mwhahaha my assumption is that the keystone task is waiting for something that never returned
17:16 mwhahaha ie haproxy or ping check or something
17:16 adam_g yeah it looked like it was polling
17:16 mwhahaha i'd have to go poke in the code
17:16 adam_g http://paste.ubuntu.com/15953760/
17:16 adam_g thats the last 500 ln of the pupet log
17:17 adam_g mwhahaha, is there  suggested min. ram for fuel-devops slave nodes?
17:17 mwhahaha 2g
17:17 mwhahaha i think
17:17 mwhahaha maybe 2.5
17:18 adam_g ok ive got 3.somethng
17:18 mwhahaha well that was a success
17:18 mwhahaha you sure keystone failed?
17:19 adam_g mwhahaha, no, im not sure of anything at this point :)
17:19 adam_g ive got all the component pieces of my plugin done, now just trying to get the deployment to role out correct. keep failing on problems that look unrelated to anything ive done
17:20 adam_g keystone is running on the failed node
17:20 adam_g http://paste.ubuntu.com/15953864/ pacemaker's got some stuff
17:21 mwhahaha yea i assume it's an issue with the response of the success getting lost
17:21 adam_g hmm
17:21 adam_g 2016-04-20 17:05:05 WARNING [793] Puppet agent 4 didn't respond within the allotted time
17:21 adam_g 2016-04-20 17:05:05 ERROR [793] Task '{"priority"=>4700, "type"=>"puppet", "id"=>"primary-keystone", "parameters"=>{"puppet_modules"=>"/etc/puppet/modules", "puppet_manifest"=>"/etc/puppet/modules/osnailyfacter/modular/keystone/keystone.pp", "timeout"=>3600, "cwd"=>"/"}, "uids"=>["4"]}' failed on node 4
17:22 adam_g 2016-04-20 17:05:05 DEBUG [793] Task time summary: primary-keystone with status error on node 4 took 15:46:56
17:22 mwhahaha yea it errored because it timed out waiting on a response
17:22 adam_g mwhahaha, whats 'it' in this case? mcollective? astute?
17:23 mwhahaha yes
17:23 * mwhahaha waves hands and is more vague
17:23 mwhahaha so mcollective is the mechanism for communication between astute and the end node
17:23 mwhahaha so it broke down somewhere between mcollective/astute
17:23 mwhahaha if that's the true cause of the failure
17:24 adam_g ok
17:24 adam_g thanks
17:25 adam_g oh
17:25 adam_g let me try bumping ram on the admin node. it only has 1.5g
17:25 ron____ joined #fuel
17:26 mwhahaha oh yea the master needs like 3
17:27 mwhahaha that's be a problem
17:27 mwhahaha that'd
17:28 mwhahaha docs list at least 2 for testing, https://docs.mirantis.com/openstack/fuel/fuel-8.0/mos-planning-guide.html#fuel-sys-req-pg
17:30 adam_g i blame fuel-devops bad defaults!
17:30 mwhahaha i would not be shocked
17:34 ericjwolf joined #fuel
17:34 adam_g left #fuel
17:34 adam_g joined #fuel
17:37 StanKardach joined #fuel
17:40 StanKardach hello guys, I'm playing around with modifying Fuel and I am trying to add a configuration parameter to the nailgun openstack.yaml fixture. So I've added a node there with a radio button but I'm wondering how can I then get to this setting from puppet scripts in fuel-library?
17:42 mwhahaha depends on where you added it
17:42 StanKardach I can see that some settings are actually parsed in nailgun's SQLAlchemy mappings but if I'm not mistaken that is just for strictly nailgun scripts
17:44 StanKardach mwhahaha: then my question should be, where should I add it? So far I've put it next to "attributes_metadata/additional_components"
17:44 StanKardach the goal is to have it appear in Settings->OpenStack services under a new label
17:45 mwhahaha that's a better question for #fuel-dev
17:45 mwhahaha but i know the ones under common show up as top level items in astute.yaml
17:46 mwhahaha Do you have specifically what you changed?
17:48 StanKardach in terms of what have I added to the openstack.yaml fixture?
17:48 mwhahaha yea
17:48 StanKardach http://pastebin.com/1ARNbUH4http://pastebin.com/1ARNbUH4
17:48 ericjwolf Good day....  Simple question.  In fuel 6.1 all the nodes where named node-xx  and I wrote a script that can go in use the name names ssh/do a bunch of config no issues.  But in 8.0 I am using the real names but it looks like the alais of the node-xx is not there anymore.  Where is the dns info stored in fuel for the nodes?
17:49 mwhahaha ericjwolf: it's not a db, it's dnsmasq and node-# should still work
17:49 mwhahaha node-<nodeid>
17:49 mwhahaha StanKardach: if you create a section udner attibutes_metadata i think it should get passed
17:51 ericjwolf Does not appear to work:
17:51 ericjwolf http://paste.openstack.org/show/494866/
17:51 mwhahaha dnsmasq might be broken
17:51 mwhahaha there's a fix on review for it
17:52 mwhahaha https://bugs.launchpad.net/fuel/+bug/1567957
17:54 ericjwolf will that get patched back to FUEL8.0?
17:56 mwhahaha not sure as it's currently not listed, but if you can verify it's occuring on 8.0 we could probably get it addressed
17:56 mwhahaha in the mean time you could try the patch out
17:57 mwhahaha under fuel8 it was in the nailgun module not the fuel module
17:57 mwhahaha seems to be just disable network manager
17:57 adam_g mwhahaha, just curious, would lossy messaging like i was seeing cause instructions to missed and deployment tasks to be skipped? was seeing this yesterday and thought it was an issue with my deployment_Tasks
17:57 mwhahaha adam_g: possibly
17:58 StanKardach mwhahaha: thanks for your help
17:59 mwhahaha lunch time
17:59 * mwhahaha wanders off
18:07 ericjwolf Enjoy your lunch...
18:16 javeriak_ joined #fuel
18:19 derrickb joined #fuel
18:21 derrickb Hi all... I have inherited a Mirantis 5.1 installation, and the postgres docker container is not there. So I've lost all my configs. I've resigned to rebuilding the server, but is there a way to repopulate the nodes with proper roles without manually going into the database? I know the network layout and am able to rebuild the configs....
18:23 rmoe joined #fuel
18:25 LanceHaig joined #fuel
18:36 EZPZ joined #fuel
18:52 xarses adam_g: you might want to check `mco ping` and rabbitmq health
18:52 xarses if it's loosing messages, it will be a problem like you see above
18:52 xarses so will not enough ram on the fuel node
18:53 xarses derrickb: I'm guessing you didn't have a backup? do you have a diagnostic snapshot? their is a db dump in it
18:54 xarses ericjwolf: you can always use `fuel node` output and awk to use the ip address in the response to ssh into the nodes
18:56 v1k0d3n joined #fuel
18:58 adam_g xarses, thanks
19:03 ericjwolf Yeap.  I am a script "duffus" so it takes me much longer to modify scripts than the average bear once I get them working.  I am more of an engineer than a programer.  I can do it just takes awhile.
19:09 derrickb joined #fuel
19:33 e0ne joined #fuel
19:34 kdebnath joined #fuel
19:34 kdebnath Hello Experts
19:34 Guest53952 joined #fuel
19:34 kdebnath My Fuel UI does not discover the nodes
19:34 kdebnath Mirantis 7.0
19:34 kdebnath Cisco UCS M3 Blades
19:35 mwhahaha what do you mean does not discover the nodes
19:35 kdebnath After I login to the bootstrap
19:35 kdebnath Is see there is no eth0 IP
19:35 kdebnath This could be the reason why the nodes are not discovered
19:35 mwhahaha probably need a custom bootstrap as the ethernet driver may not be in it
19:35 kdebnath But, is there a workaround i can do to make this work ?
19:36 kdebnath But Mirantis 7.0 should support this. Isnt it ?
19:36 mwhahaha not sure if UCA m3 blades are on the supported list of hardware
19:36 kdebnath Thanks mwhahaha, for your response
19:36 mwhahaha there is a way in 7 to turn on an ubuntu bootstrap image
19:36 mwhahaha which might work
19:37 kdebnath How do we do that ?
19:37 kdebnath Can you please help ?
19:37 kdebnath Other guys have done this without issues, on M4 blades
19:37 mwhahaha https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#enable-ubuntu-bootstrap-experimental
19:37 kdebnath Also, How can we make sure, if Cisco UCS M3 are on the supported list of hardware ?
19:38 mwhahaha not sure let me see if i can find a hardware support matrix
19:39 kdebnath Thanks a lot
19:39 kdebnath That will be great
19:39 mwhahaha https://www.mirantis.com/validated-solution-integrations/hardware-compatibility/
19:39 mwhahaha m3 is listed but i have no idea, not my world
19:41 kdebnath I see
19:42 mwhahaha i'd try the ubuntu bootstrap and see if that works for you
19:42 kdebnath The one listed is B220 M3
19:42 kdebnath Mine is B200 M3
19:46 xarses kdebnath: is there a reason you can't use fuel 8? We changed the default discovery image from the older Cent 6.5 image, to Ubuntu 14.04, and you can more easily rebuild it to inject drivers if needed.
19:50 kdebnath I need to confirm if I can use Mirantis 8.0
19:57 kdebnath Another question is - CISCO UCS M4 blades are not on the list for hardware compatibility. Doesnt that mean it may or may not support Mirantis ?
20:02 HeOS joined #fuel
20:04 mwhahaha it might work, but we haven't validated it
20:19 kdebnath joined #fuel
20:20 kdebnath Hello mwhahaha
20:20 kdebnath If you are still there
20:20 kdebnath [root@fuel ~]# fuel-bootstrap-image-set ubuntu fuel-bootstrap-image-set: WARNING: Ubuntu based bootstrap is EXPERIMENTAL. fuel-bootstrap-image-set: WARNING: Use at your own risk. fuel-bootstrap-image-set: info: Ubuntu bootstrap image does not exist, building one fuel-bootstrap-image-set: info: build log is available at /var/log/fuel-bootstrap-image-build.log fuel-bootstrap-image-set: error: failed to build Ubuntu bootstrap image fue
20:20 kdebnath My experimental bootstrap image set is failing
20:21 mwhahaha what's in that log?
20:22 kdebnath 78 I: Retrieving Release      79 E: Failed getting release file http://archive.ubuntu.com/ubuntu/dists/trusty/Release
20:22 kdebnath I am able to wet this file though
20:23 mwhahaha do you not have access to the internet?
20:23 kdebnath Yes
20:23 kdebnath I believe if I can wget this file, I should be good
20:23 kdebnath wit hthe internet
20:23 kdebnath Is there anything else that we are trying to get
20:23 kdebnath ?
20:24 mwhahaha well it basically has to go build it from scratch and we use the internet repositories to pull down the packages
20:24 mwhahaha i'm not completely sure what's failing
20:26 javeriak joined #fuel
20:27 kdebnath Is there a way I can send you the logs for /var/log/fuel-bootstrap-image-build.log
20:28 mwhahaha probably only need the last bit of it if you want to use paste.openstack.org
20:29 kdebnath Paste #494887
20:31 kdebnath Are you able to find with the above number
20:33 kdebnath http://paste.openstack.org/show/494887/
20:34 mwhahaha and you can curl http://archive.ubuntu.com/ubuntu/dists/trusty/Release from your master?
20:35 kdebnath Yes
20:36 mwhahaha you could try building it again but i'm not sure cause that error really is not very descriptive
20:37 kdebnath It fails
20:37 kdebnath Is there a manual way of doing this
20:37 kdebnath Building the bootstrap image
20:40 mwhahaha oh you have a proxy
20:40 mwhahaha i wonder if that's why it's failing
20:41 kdebnath Is there a workaround for this?
20:42 mwhahaha i have no idea
20:48 Reepicheep joined #fuel
20:49 jobewan joined #fuel
21:29 xek joined #fuel
21:40 anddrew21 joined #fuel
21:41 e0ne joined #fuel
22:13 xarses export the proxy env args?
23:03 mwhahaha it was that's how i spotted the proxy
23:38 thumpba joined #fuel
23:42 xarses ah
23:42 xarses should be all that is needed

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