Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-08-21

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

All times shown according to UTC.

Time Nick Message
00:20 rmoe joined #fuel
01:16 KodiakF2 hrm - getting 500 errors when I try to pull http://10.0.10.100/cblr/svc/op/ks/profile/centos-x86_64 - I started digging into it because hosts can't pull their KS profiles for the centos build on a new Fuel deployment
01:16 KodiakF2 So as the regular RHEL + Apache guy I am I head on down to /var/log/nginx looking for something akin to error_log, but there's nada in that folder - I'm suspecting it's all in a docker somewhere
01:17 KodiakF2 I don't get where the logs for nginix in the container might be...
01:45 Kupo24z1 joined #fuel
01:47 ilbot3 joined #fuel
01:47 Topic for #fuel is now Fuel 5.0.1 for Openstack: https://wiki.openstack.org/wiki/Fuel | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
02:04 christopheraedo joined #fuel
03:08 mattgriffin joined #fuel
03:50 geekinutah joined #fuel
04:03 ArminderS joined #fuel
05:36 nimion joined #fuel
05:57 adanin joined #fuel
05:58 lordd_ joined #fuel
06:40 tatyana joined #fuel
06:48 tuvenen joined #fuel
07:15 pasquier-s joined #fuel
07:41 hyperbaba joined #fuel
08:05 nimissa left #fuel
08:05 nimissa joined #fuel
08:10 Longgeek joined #fuel
08:12 Longgeek joined #fuel
08:20 juniorlinux joined #fuel
08:38 e0ne joined #fuel
08:59 lordd_ joined #fuel
09:07 Havard joined #fuel
09:07 HeOS joined #fuel
09:25 bookwar joined #fuel
09:28 e0ne joined #fuel
10:24 aepifanov joined #fuel
10:26 aepifanov joined #fuel
10:27 eshumkher joined #fuel
10:34 e0ne joined #fuel
10:35 Longgeek joined #fuel
10:36 Havard hello there guys, we are new to fuel and openstack, i have just completed the fuel setup according to the docs, but it does not seem like the dhcp and pxe is configured, is that something we have to do in addition to the fuel setup?
10:36 Havard and, yes, call me a greenhorn ;-)
10:39 evg Havard: hello, usially it works out of the box
10:40 Havard strange, since our did not
10:40 evg Havard: What have you done?
10:40 Havard one moment
10:40 Havard i have followed this guide:
10:40 Havard http://docs.mirantis.com/openstack/fuel/fuel-5.0/pdf/Mirantis-OpenStack-5.0.1-UserGuide.pdf
10:41 kaliya Havard: dhcp and pxe should be configured after the master node has booted properly. Could you please run `dockerctl list -l` on the master and see if all containers are running?
10:41 Havard and completed everything until page 15
10:41 Havard kaliya: hm, thanks, moment
10:41 Havard [root@cloud /]# dockerctl list -l
10:41 Havard Invalid selection.
10:41 Havard Usage:
10:41 Havard /usr/bin/dockerctl command
10:41 Havard it might be that i need to boot it again
10:42 Havard after completed install with fuel setup
10:42 evg Havard: the first please sure then the instalation process is done
10:43 evg Havard: it takes some time
10:43 Havard evg: yeah i completed the setup and saved settings
10:43 Havard than after that i got the login details to the root account
10:43 Havard but let me try to reboot that cloud server again before i check
10:45 evg Havard: ok
10:47 evg Havard: note, in the most cases you don't need console-based fuel setup
10:48 evg Havard: if you are trying it the first time you can just let the install process do all the work
10:49 Havard i did it on the fuel setup in the console to be able to set the correct public IP etc for the system
10:50 Havard and also my CTO did assign me some specific internal IPs to use
10:51 Havard so if i understand this correct fuel+openstack is suppose to work out of the box? just like the OnApp (that we did try for a while)
10:53 kaliya Havard: Fuel master is intended to be a deploying tool to deploy Openstack environment. OnApp (that I used for a while) is an already configured environment to work with VMs
10:53 Havard kaliya: thanks :-)
10:54 Havard OnApp seems to have a lot of bugs, that is why we did not pay for their license
10:56 kaliya Havard: you can have a look to this video, even if it covers an older release it could give you an idea about Fuel http://www.youtube.com/watch?v=fVk9tZ2uJiM
10:59 Havard thanks a lot
10:59 lordd_ joined #fuel
11:00 kaliya Havard: np ;)
11:06 Longgeek joined #fuel
11:08 Havard strange, the server did not boot:
11:08 Havard https://www.dropbox.com/s/a11kycf3ei3xtl3/Screenshot%202014-08-21%2013.08.14.png
11:08 Havard it stopped like that image above
11:09 Longgeek joined #fuel
11:10 evg Havard: it takes a time to configure docker conteiners. Let's wait a bit.
11:13 Havard ok, has been like this for 10-15 minutes now
11:20 e0ne joined #fuel
11:26 evg Havard: you just don't see login prompt. Press Enter.
11:26 evg Havard: in console
11:27 Havard ah :-)
11:27 Havard hm, strange, it did not get eth0 up with the IP from the fuel setup
11:31 evg Havard: yes, you broke something
11:31 evg Havard: is eth0 up?
11:32 Havard hehe, actually i only have access with IPMI now, and the IPMI does not allow me to insert the root password since i have to many special carathers in the password, like: Þ, Ú, Ý and á    :-)
11:32 Havard characters**
11:34 evg Havard: :)
11:35 evg but what have you changed via fuel setup?
11:35 Havard smart ass :-)
11:35 Havard no, i changed it after finish the installation
11:35 Havard when logged into ssh
11:35 Havard i am running the install again now from the ISO
11:35 Havard showmenu=yes to get the fuel setup tool
11:36 Havard and i will leave the root password for a while to make sure it is working :-P
11:38 evg Havard: if the only thing you want is changing the public IP you can just set it before iso boot (pressing tab)
11:39 evg Havard: or you can set it as a secondary ip on eth0 after installation
11:39 Havard yeah, but i also have a range of IPs from my CTO to use for the internal network
11:39 Havard to not get any problem with other equipment in our network running on internal IPs
11:40 evg Havard: ah, ok then
11:40 Havard so need to use the fuel setup tool to get this information correct
11:40 Havard but after the reboot it seems that all that information was gone
11:40 Havard so i am trying again with a fresh install
11:41 evg Havard: may be you haven't press save in fuelmenu
11:42 Havard i thought i did, but it might be possible that i missed that :-P
11:51 eshumkher joined #fuel
11:51 ganso Hello guys, does anybody experience some failing health check tests on a default fuel 5.0 setup? for me "Check stack autoscaling" always fails with "Image with cfntools package sould be imported" message
11:53 evg ganso: hello, may be it'll help you http://docs.mirantis.com/openstack/fuel/fuel-5.0/operations.html#preparing-heat-for-testing
11:55 ganso evg thanks a lot!
12:03 adanin_ joined #fuel
12:05 ganso Does anyone here have tempest experience? I have only 1 volume test failing on a default fuel 5.0 setup, it is a tempest.api.volume.admin.test_volume_quotas test and it gives "ResponseNotReady" error on a "create-tenant" operation... all other 232 tests succeed.
12:12 Longgeek joined #fuel
12:14 Longgeek joined #fuel
12:14 aepifanov joined #fuel
12:18 pasquier-s joined #fuel
12:33 lordd_ joined #fuel
12:39 aepifanov joined #fuel
12:52 eshumkher_ joined #fuel
13:07 jaypipes joined #fuel
13:11 aepifanov joined #fuel
13:15 Havard strange, i did a fresh install, but seems like dhcpd is still not running
13:15 Havard so when i am booting one of my host/nodes it does not get any IP from the fuel server
13:22 kaliya Havard: please run `dockerctl check` to see if all containers are ready?
13:22 Havard mcollective is ready <-- that is the last one
13:22 Havard bbl, dinner now in this house :-P
13:23 kaliya and cobbler, postgres etc?
13:27 jobewan joined #fuel
13:29 racingferret joined #fuel
13:55 kaliya joined #fuel
14:01 Havard kaliya: yes, all the containers are ready
14:04 evg Havard: i've may be got you wrong but the first your host/node should boot from network
14:05 Havard evg: i am trying to boot one of my nodes now, but it does not get any IP from the DHCP
14:05 evg Havard: you have to configure network booting on your host
14:05 Havard an i guess that the DHCP is suppose to run on the server where i did install fuel
14:05 Havard i have done so, it is searching for DHCP server
14:06 Havard and on my fuel server i get this:
14:06 Havard [root@cloud ~]# service dhcpd status
14:06 Havard dhcpd is stopped
14:06 evg Havard: it's ok.
14:06 Havard let me try to boot my node again
14:07 evg Havard: dhcp and cobbler are running inside lxc conteiner
14:07 Havard ah
14:07 evg Havard: Your node has to boot from  network and then it'll get ip via dhcp
14:07 Havard https://www.dropbox.com/s/vla9ihy791swhay/Screenshot%202014-08-21%2016.07.50.png
14:08 Havard yeah, i am trying to boot it over network with both the 1G NICs in the nodes
14:08 evg Havard: ah, ok.
14:09 evg Havard: I've got you now
14:09 evg Havard: network problems?
14:09 Havard :-)
14:09 Havard i am not sure since the same nodes where pxebooting from the onapp server just a few days ago
14:09 Havard than we installed the onapp on the server we now have named cloud
14:10 Havard and tftp, pxe and dhcp on the "cloud" server, and the nodes where booting from that
14:13 evg Havard: and what eth nic have you configured for pxe?
14:13 Havard eth1
14:13 eshumkher joined #fuel
14:14 Havard eth0 is the one for public access to the system
14:14 evg Havard: are you sure it's on the same network with your nodes?
14:14 Havard yeah
14:14 Havard evg, as i said this did work with onapp and we did not do any changes in the network configuration
14:15 evg Havard: try tcpdump eth1 for pxe then
14:16 Havard evg: like this: 'tcpdump eth1'
14:16 Havard ?
14:16 Havard i am not very techy ;-)
14:16 evg Havard: I really know nothing about network configuration omapp uses
14:16 evg Havard: moment...
14:21 evg Havard: tcpdump -n -i eth1 ether host <mac address of your node from your sceenshot>
14:24 Havard [root@cloud ~]# tcpdump -n -i eth1 ether host 0C:C4:7A:04:82:CC
14:24 Havard tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
14:24 Havard listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
14:24 Havard 14:23:22.198538 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:04:82:cc, length 548
14:24 Havard 14:23:24.238008 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:04:82:cc, length 548
14:24 Havard 14:23:28.237438 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:04:82:cc, length 548
14:24 Havard 14:23:36.256146 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:c4:7a:04:82:cc, length 548
14:24 Havard thats what i got
14:25 mattgriffin joined #fuel
14:28 lordd_ joined #fuel
14:30 evg Havard: then "dockerctl shell cobbler"
14:30 evg Havard: "yum install tcpdump"
14:31 evg Havard: and tcpdum again in cobbler container
14:37 evg Havard: actually, I suspect you haven't set eth1 as pxe NIC in fuelmenu
14:37 evg Havard: ah, nope, you seem set it
14:44 eshumkher joined #fuel
14:45 lordd_ joined #fuel
15:25 ArminderS joined #fuel
15:52 blahRus joined #fuel
15:54 jaypipes joined #fuel
16:01 angdraug joined #fuel
16:14 xarses joined #fuel
16:30 aepifanov joined #fuel
16:35 Havard evg, yeah, i did set that in the menu, trying the tcpdump now in the cobbler container
16:36 Havard in cobbler nothing happens:
16:36 Havard [root@5055177bc03e ~]# tcpdump -n -i eth0 ether host 0C:C4:7A:04:82:CC
16:36 Havard tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
16:36 Havard listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
16:37 Havard i had to change to eth0 since that is the only NIC in the cobbler
16:55 miroslav_ joined #fuel
16:55 jaypipes joined #fuel
17:17 gregory_pmd joined #fuel
17:17 rmoe joined #fuel
17:19 ArminderS- joined #fuel
17:42 lordd_ joined #fuel
17:56 mattgriffin joined #fuel
17:59 e0ne joined #fuel
18:09 geekinutah joined #fuel
18:34 kupo24z xarses: who can spin up a new ISO from https://fuel-jenkins.mirantis.com/view/ISO/job/publish_fuel_community_iso/ ? Preferably if it has https://bugs.launchpad.net/fuel/+bug/1356954 & https://bugs.launchpad.net/fuel/+bug/1352335 implemented
18:40 MiroslavAnashkin What is ISO number? And can you see the links to the ISO, IMG and upgrade tarball near the selected ISO build numbers?
18:40 kupo24z MiroslavAnashkin: oh just wondering if an updated one can be created, current iso number is 51
18:43 MiroslavAnashkin OK, do you need ISO build 51 or newer one? And there are now 2 branches, 5.1 and master.
18:43 kupo24z Whats the difference from 5.1 and master?
18:43 xarses kupo24z: nothing at the moment
18:44 xarses untill we enter hard code freeze and create stable/5.1 branch
18:44 kupo24z then master would be 6.0 code?
18:44 xarses yes
18:44 aepifanov joined #fuel
18:44 kupo24z 5.1 then
18:45 kupo24z isnt HCF scheduled for today?
18:47 xarses it looks like it's pushed again, still waiting for some of these high and critical bugs
18:47 MiroslavAnashkin Hmm, HCF exact time is not so exact...
18:48 xarses HCF ~= when it's ready
18:48 MiroslavAnashkin Well, new community builds are created by timer and by DevOps team. I cannot launch new one.
18:48 xarses its a release quality gate
18:48 kupo24z valve time
18:49 xarses not quite
18:49 xarses but i feel the jab
18:49 xarses =)
19:00 kupo24z MiroslavAnashkin: what is the timer set to?
19:00 xarses kupo24z: once a day normally
19:01 MiroslavAnashkin Should trigger in ~7 hours
19:01 xarses kupo24z: https://fuel-jenkins.mirantis.com/view/ISO/job/fuel_community_master_iso/
19:02 xarses it's building 85 now
19:02 kupo24z cool thanks
19:02 xarses I poked one of the guys
19:32 mattgriffin joined #fuel
20:03 jobewan joined #fuel
20:24 kupo24z Looks like its finishing up now
20:24 kupo24z ill download and retest in my env
20:46 xarses joined #fuel
21:02 adanin joined #fuel
21:03 mattgriffin joined #fuel
21:29 kupo24z joined #fuel
21:55 geekinutah joined #fuel
22:03 aepifanov joined #fuel
22:28 lordd_ joined #fuel
22:33 xarses joined #fuel
22:39 kupo24z xarses: is there any issues with running fuelmenu post puppet vs pre?
22:41 xarses only that it will likely nuke your database
22:41 xarses no
22:41 xarses you might need to destroy your containers first, I'm not sure if they rebuild
22:44 kupo24z meh ill just reinstall
22:46 xarses its not that bad
22:46 xarses just destroy the containers and it will be the same as first run
23:58 Llew joined #fuel

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