Wednesday, 2016-03-30

*** openstack has joined #openstack-kolla17:04
sdakewow no idea where it went17:05
openstackgerritSteven Dake proposed openstack/kolla: Revert "Install master's version of an RDO keystone"  https://review.openstack.org/29954017:05
sdakeI wonder if I ereverted soething else by accident17:06
sdakechekcing git logs17:06
sdakethanks inc0 for the catch - that would have been emberrassing :)17:07
inc0yeah a bit17:08
inc0trying to get keystone to work :S17:08
*** jmccarthy has joined #openstack-kolla17:08
sdakenihilifer around?17:09
sdakejpeeler around?17:10
sdakeplease vote on the backport and if you intend to vote on the core nomination please do ;)17:10
* sdake wtb a voting service which sends the results automatically to the mailing list17:10
jpeelerwhere's this vote?17:11
sdakepolla] opentack-dev17:11
*** daneyon has joined #openstack-kolla17:15
vhosakotelemoine_: ping17:15
*** stvnoyes has left #openstack-kolla17:17
inc0so sdake way I want to deal with backport is same as with upgrade17:18
inc0once I'm done with ks let everyone take a service and make sure that it deploys both ways17:19
inc0and upgrades from L to M17:19
sdakeinco you need to do glance too17:19
inc0we need to do all17:19
vhosakotlot of doc gate failures today17:19
inc0but yeah17:19
sdakewhat i mean is if its distributed17:19
sdakewe need the basics done17:19
sdakelike rabbit/maria/keystone17:20
sdakei guess the rest can be distributed17:20
inc0so here's deal17:20
sdakethat wfm ;)17:20
sdakei like distributed backport idea17:20
inc0I don't do maria and rabbit17:20
*** daneyon has quit IRC17:20
inc0that we deploy from master17:20
sdakeinc0 a distributed backport is off the table until mitaka ships though17:20
inc0you are afraid for bandwidth?17:21
sdakeinc0 we have 36 bugs17:21
inc0kk17:21
sdakei am not sure which of them are actually crucial17:21
sdakebut I'd like as many bugs fixed as possible17:21
inc0fix these, there is good change that these will affect backport as well17:21
sdakeright17:21
sdakelets get mitaka fixed17:21
sdakeif you want to lay groundwork for backports by doing the base infra17:22
sdakethat sounds good17:22
sdakeand then we can distribute the workload17:22
sdakethat is actually areally fantastic idea ;)17:22
*** gfidente has quit IRC17:25
sdakegotta jet, doctors appointment17:25
sdakethen 2 hours of emetings17:25
sdakei may be out for 2-3 hours but will try to be responsive on irc as possible17:25
*** unicell has joined #openstack-kolla17:29
*** ayoung has joined #openstack-kolla17:30
*** salv-orlando has joined #openstack-kolla17:33
*** salv-orlando has quit IRC17:40
*** rajathagasthya has joined #openstack-kolla17:41
vhosakotsdake: the Member role should be added in Keystone bootstrap ? I see horizon does not have bootstraop17:41
*** sdake has quit IRC17:42
*** unicell has quit IRC18:02
*** unicell has joined #openstack-kolla18:02
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Making Mitaka deploying liberty  https://review.openstack.org/29956318:08
*** Marga__ has quit IRC18:17
*** Slower_ has joined #openstack-kolla18:19
* Slower_ cries about the channel change *sniff*18:19
*** Slower_ is now known as Slower18:19
inc0Slower, nostalgy after #kolla?18:23
Sloweryeah :)18:24
inc0yeah, she will be misse18:26
inc0d18:26
inc0but on the other hand, we now have younger channel18:26
*** mgoddard_ has joined #openstack-kolla18:28
*** mgoddard_ has quit IRC18:30
*** mgoddard_ has joined #openstack-kolla18:31
*** mgoddard has quit IRC18:31
*** mgoddard_ has quit IRC18:35
vhosakotlonger channel as well.... #openstack-kolla  is longer than  #kolla18:36
*** Marga_ has joined #openstack-kolla18:42
*** shardy has quit IRC18:45
*** dwalsh has quit IRC18:49
*** sdake has joined #openstack-kolla18:57
sdakevhosakot add a bootstrap to horizon then18:57
sdakemanjeets any data for me ? :)18:58
vhosakotsdake: I was planning to add  "OpenStack role create Member"  in keystone's bootstrap   in     https://github.com/openstack/kolla/blob/master/docker/keystone/keystone_bootstrap.sh18:58
sdakenah18:58
sdakethe member requirement comes from horiozn18:59
sdakenot from keystone18:59
sdakelets double check in keystone channel now18:59
manjeetssdake working with heat stack18:59
manjeetsnot yet18:59
inc0sdake, https://review.openstack.org/29956319:00
sdakeinc0 its that simple?19:01
inc0question remains what breaks19:01
inc0but it did deploy aio19:01
manjeetssdake I have this reported to track https://bugs.launchpad.net/kolla/+bug/156400819:01
sdakei think deploy_liberty should be determined y openstack_release19:01
openstackLaunchpad bug 1564008 in kolla "Kolla should be able to handle connection limit for database according to infra " [Undecided,New]19:01
vhosakotsdake: I agree... since role is a keystone thing, I asked about it.... I see kolla-toolbox uses keystone_client to create new role     https://github.com/openstack/kolla/blob/master/docker/kolla-toolbox/kolla_keystone_user.py#L6919:02
ccesarioHey guys, I have  a little doubt... today, after kolla deployment, if I want add a new controller node or compute node ... or replace a node ... is it possible ?19:02
*** mgoddard has joined #openstack-kolla19:02
vhosakotsdake: I agree your point that Member is horizon's requirement...19:02
inc0ccesario, add new entry to inventory and re-run deploy19:02
inc0you might need to run kolla-ansible reconfigure as well19:02
inc0if you're adding controllers19:02
rhalliseyccesario, just need the node ip in the multinode inv19:02
inc0so rabbitmq, keepalived and such will change conf19:03
vhosakotsdake: let me know what you think19:03
*** salv-orlando has joined #openstack-kolla19:03
ccesarioall configs ... data... will be preserved!?!19:03
ccesarioright!?19:03
sdakehave meeting have to run19:03
sdakeccesario ye but reconfigure is broken atm19:04
*** rajathagasthya has quit IRC19:04
sdakejeffrey4l is working on it19:04
vhosakotdoes haproxy get updated when compute is added...  I agree about haproxy and keepalived needs to update their confs when new controller is added19:04
ccesariothanks by infos guys!!19:04
ccesarioI will try test it19:04
vhosakotsdake: after you come back, let me know... add horizon bootstrap with Member role   or    update keystone bootstrap ?19:05
ccesarioI suppose that if I lost one node (compute/controller) due hardware problem by example.... It is only change the inventory pointing to other node and re-configure/deploy  .... right!?19:07
openstackgerritMauricio Lima proposed openstack/kolla: Add precheck about nested environment  https://review.openstack.org/29958519:08
manjeetssdake i doubt steak-rg.yaml used by launch19:09
sdakemanjeets it works for me ;)19:11
sdakemanjeets try it unmodified19:11
manjeetsokay19:11
sdakeit just wont work with the way you have defiend networks19:11
sdakeit works the way networks are defined by init-runonce19:11
manjeetsdefined networks works by other ways though19:12
sdakewhat i suggest is copy the network defn by init-runonce but make them 65k ips19:12
sdakeand call the networks something else19:12
*** mgoddard has quit IRC19:12
sdakevhosakot add a bootstrap featue to horizon19:12
sdakevhosakot because apparently it needs one19:12
vhosakotcool.. done.. wanted to confirm before I start fixing cool19:13
sdakethis is concllusion of openstack-keystone devs19:13
vhosakotyou mean openstack-horizon devs right ?  we spoke to in horiozn channel this morning19:13
sdakeno keystone devs19:14
vhosakotah ok19:14
sdakekeystone devs said it doesn't make sens e to bootstrap horizon in keystone19:14
sdakebut in horizon19:14
vhosakotgot it19:14
sdakeand only member is used by horizon19:14
sdakeno other project19:14
sdake(at the moment)19:14
vhosakotyep.. ok19:14
*** dwalsh has joined #openstack-kolla19:15
vhosakotccesario: yes, so, you would need to add the new node in the inventory...if you replace a bad node with same IP address, no need to update inventory also...19:18
vhosakotI meant, if you replace a bad node with a good server and retain the old node's IP, then, inventory need not be changed19:19
ccesariovhosakot, in case of replace bad node to new node .... which option need I execute ?  reconfigure  or deploy?19:20
vhosakotI want to say deploy, reconfigure as well if you want to augemtn/update configs on the new code19:21
vhosakotwell, reconfigure for a _new_ node does not make sense as there will be no OpenStack serverice in the firsr place with old configs, right ?19:22
vhosakotso, replace bad server with good server, retain bad server's IP and hostname on good server, run deploy....19:23
ccesarioyes ... make sense.19:23
ccesariovhosakot, thanks again!!!19:23
*** achanda has quit IRC19:24
vhosakotccesario: haha, let me know the outcome.. it a great test... what are you replacing ? control, compute, storage, deploy node (on which kolla-ansible is run) ?19:24
ccesariovhosakot, for while I 'm  only trying understand the procedures.....  Because my  test env   is based on virtual machines, I can try replace any node :)19:31
vhosakotinc0: I was reviewing your PS (Making Mitaka deploying liberty)....  I see keystone_admin_token does not exist in Miataka... so, for liberty, keystone_admin_token must be set somewhere  or asked in  group_vars/all.yml when  deploy_liberty=yes19:32
vhosakotccesario: cool19:32
vhosakotinc0: I'll give this comment in the review19:32
ccesarioother thing..... today is it possible make kolla deploy several environments/projects?  .... because it read only /etc/kolla/(configs)  ....   and maybe /etc/kolla/projectname/(configs) would be needed ...19:35
inc0vhosakot, yeah forgot about this one19:36
inc0actually place for keytsone_admin_token is password.yml19:36
vhosakotinc0: Liberty has    keystone_admin_token: "password"    in   etc/kolla/passwords.yml19:36
inc0in mitaka we have generated password19:36
inc0but I'll add it to passwords.yml19:37
rhalliseyccesario, yes use node_templates_directory19:37
inc0with a comment19:37
vhosakotbut keystone_admin_token is not passwords.yml in Mitaka... shou;dn't it be added dfirst19:37
vhosakotonly to deploy Liberty case19:37
rhalliseyccesario, wrong var -> node_config_directory19:37
rhalliseyuse that one19:37
rhalliseyin all.yml19:37
vhosakotcool19:38
ccesariorhallisey, but in case of multiple projects!?19:40
vhosakotccesario: you mean multiple deploymetns/clouds ?19:40
ccesarioyes19:40
ccesario:)19:40
vhosakothmm19:41
rhalliseyccesario, just do that same thing you did with the first19:41
rhalliseyand point that the new config dir19:41
rhalliseythat variable*19:41
rhalliseyccesario, I don't see why it wouldn't work19:42
ccesarioyes,  changing it ansible/group_vars/all.yml  in each deploy it works .19:43
vhosakotccesario: are you using one deploy node for two clouds ?19:44
ccesariovhosakot, I 'm thinking about.... :)19:46
ccesariotests man19:46
ccesario:)19:46
rhalliseyccesario, I think it would still work19:47
rhalliseytry it :)19:47
vhosakothmmm... so, does that mean, you use the same kolla inputs (in globals.yml) for two clouds ? same IPs and VIPs for both clouds.. ?19:47
vhosakotyep.. try it :) great test...19:47
*** mbound has joined #openstack-kolla19:48
ccesariovhosakot, no no... what the rhallisey it would works.... but after the first deploy I will need chaange the "config" directory to read the new configs for new "cloud"19:48
vhosakotah cool!19:49
ccesariothe idea would be if kolla read automatically these configs :)19:50
*** achanda has joined #openstack-kolla19:51
vhosakotccesario: so, would "kolla-ansible deploy" use the same globals.yml to deploy services on both clouds ?19:51
ccesariovhosakot, no ..... like "kolla-ansible deploy project1"  "kolla-ansible deploy project2"    and each deploy read the var in each directory config ... eg. /etc/kolla/project1/globals.yml and /etc/kolla/project2/globals.yml .....19:54
ccesarioonly ideas... only :)19:54
ccesariowith this, the operator/admin only touch in globals config ..... no changes in "core" code19:55
rhalliseyccesario, also need to change the inventory file19:55
rhalliseybut right, no core code19:55
ccesariorhallisey, yes yes (I only put a short comment)19:55
rhallisey:)19:56
ccesariorhallisey, I think that you understood the idea :)19:57
rhalliseyccesario, ya I gotcha. Try it! Curious to see it work19:57
vhosakotrhallisey: ccesario: yes, I think it should work.. same _core_ code, different globals.yml files, different inventory files, _same_ deploy node, two clouds... nice20:00
vhosakotwhat about docker registry... will it be same for btoh clouds ?20:00
*** sdake_ has joined #openstack-kolla20:00
rhalliseyvhosakot, ya20:01
rhalliseyuse the same images20:01
rhalliseyonly the configs change per service20:01
vhosakotyep.. right20:02
*** sdake has quit IRC20:02
vhosakotcool20:02
ccesariorhallisey, vhosakot  maybe creating a kolla-ansible  script wrapper to receive the params like "project"  name and inventory can make this easy .... I think20:03
vhosakotbut, two gloabls.yml files means _two_ docker_registry pram for kolla...20:05
vhosakotccesario: I think keep docker_registry IP address same in both globals.yml so that the same registry is sued for both clouds20:07
ccesariovhosakot, necessarily the tw deploys don't need to be simultaneous ...20:08
ccesariowell ...  only ideas to make it more easy ... eheheh20:11
*** rajathagasthya has joined #openstack-kolla20:13
vhosakotyep20:13
vhosakotI think it should work...20:13
ccesariovhosakot, I will try test it20:17
*** banix_ has joined #openstack-kolla20:17
*** banix has quit IRC20:19
*** banix_ is now known as banix20:19
ccesariovhosakot, thinking in this.... the  kolla-genpw could have the option to specify the output directory :)20:20
sdake_inc0 can you get ahold of gammaha and let him know my schedule has changed20:23
manjeetssdake i think this solution to type of instances we want http://docs.openstack.org/developer/heat/template_guide/basic_resources.html#create-and-associate-security-groups-to-an-instance20:23
sdake_inc0 and come to irc to chat20:23
inc0manjeets, is Ganesh around?20:24
sdake_manjeets the templates work a sis20:24
sdake_if yuo can explain to me what precisely the problem is with them as they stnd i am open to listening ;)20:24
manjeetsinc0: i see he  is away20:25
*** dwalsh has quit IRC20:27
*** sdake has joined #openstack-kolla20:32
gmmahainc0: hey20:33
inc0gmmaha, sdake....talk;)20:33
sdakegmmaha hey my schedule changed20:33
sdakei am open now20:33
gmmahasdake: ohhh20:33
sdakebut may not be in about 1 hr or so20:33
gmmahacool.. i am game20:33
gmmahalets do it20:33
*** sdake_ has quit IRC20:33
sdakeok so lets get to it20:33
sdakecan you setup some screen sharing so we can talk rather then type - will be faster20:34
sdakegoogle groups or something20:34
gmmahasdake: definitely can do20:34
* gmmaha goes to get his google account 20:34
*** achanda has quit IRC20:37
*** jtriley has quit IRC20:37
*** openstackgerrit has quit IRC20:48
*** openstackgerrit has joined #openstack-kolla20:48
manjeetssdake https://github.com/openstack/kolla/blob/master/demos/heat/steak.yaml#L2420:51
*** daneyon has joined #openstack-kolla20:51
manjeetsi used defaults with updated network capacity still had issue with heat20:51
manjeetswhat is this key for20:52
*** daneyon has quit IRC20:56
*** achanda has joined #openstack-kolla20:56
*** achanda has quit IRC20:57
*** achanda has joined #openstack-kolla20:58
*** daneyon has joined #openstack-kolla21:04
*** daneyon_ has quit IRC21:07
*** jtriley has joined #openstack-kolla21:11
*** prithiv has joined #openstack-kolla21:11
gmmaharoot@3b2a0f3f8615:/# dpkg -l | grep libvirt21:12
gmmahaii  libvirt-bin                      1.3.1-1ubuntu4~cloud0                 amd64        programs for the libvirt library21:12
gmmahaii  libvirt0:amd64                   1.3.1-1ubuntu4~cloud0                 amd64        library for interfacing with different virtualization systems21:12
gmmahavhosakot: can you check if your libvirt containers are running the same versions of libvirt?21:12
sdakevhosakot can you erify the above is the same on our box?21:12
*** ccesario_ has joined #openstack-kolla21:12
vhosakotwhat command should I run ?21:12
vhosakotah dpkg.. 1 sec21:12
gmmahavhosakot: dpk -l | grep libvirt21:12
gmmahadpkg -l | grep libvirt21:12
sdakeinside container21:12
gmmaharoot@3b2a0f3f8615:/# dpkg -l | grep libvirt21:13
* manjeets saw a new minimum for sql connection today after re deploy21:13
manjeetssdake may want that 49221:14
vhosakotgmmaha: sdake: I dont have libvirt installed on the host.. on the host, "dpkg -l | grep libvirt"  is empty....I have libvirt installed inside the nova_libvirt container....21:15
vhosakot$ docker exec nova_libvirt dpkg -l | grep libvirt21:16
vhosakotii  libvirt-bin                      1.3.1-1ubuntu4~cloud0                 amd64        programs for the libvirt library21:16
vhosakotii  libvirt0:amd64                   1.3.1-1ubuntu4~cloud0                 amd64        library for interfacing with different virtualization systems21:16
gmmahavhosakot: thanks..21:16
gmmahamathes21:16
*** jtriley has quit IRC21:19
*** haplo37 has quit IRC21:19
vhosakotdo you have libvirt on the host ... ? it should be on the compute host... yes21:20
*** ccesario_ has quit IRC21:23
*** ccesario__ has joined #openstack-kolla21:27
*** jtriley has joined #openstack-kolla21:30
*** rhallisey has quit IRC21:31
gmmahavhosakot: yeah i d o libvirt on the host.. will be disabling it soon-ish21:31
*** ccesario__ has quit IRC21:31
vhosakotcool21:31
*** ccesario__ has joined #openstack-kolla21:31
*** achanda has quit IRC21:32
rajathagasthyaHas anyone seen this error before during kolla-build? "INFO:kolla.cmd.build:base:File contains no section headers.21:34
rajathagasthyaINFO:kolla.cmd.build:base:file: file:///etc/yum.repos.d/delorean-deps.repo, line: 121:34
rajathagasthyaINFO:kolla.cmd.build:base:'<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"\n'"21:34
rajathagasthyaI'm in a Vagrant setup with Virtualbox provider.21:34
*** ccesario__ has quit IRC21:38
gmmahavhosakot: how do you disable libvirt on ubuntu 14.04?21:38
vhosakotservice libvirt-bin stop21:39
vhosakotupdate-rc.d libvirt-bin disable21:39
gmmahavhosakot: sudo update-rc.d -f libvirtd remove21:42
gmmahavhosakot: aah.. thansk21:42
gmmahathanks21:42
*** banix has quit IRC21:44
*** jtriley has quit IRC21:47
vhosakotrajathagasthya: I'd ping manndre.. he is not around now.. ping SiRiuS_ if he is around21:47
rajathagasthyavhosakot: Thanks, will do.21:48
vhosakotrajathagasthya: you could refer http://docs.openstack.org/developer/kolla/quickstart.html to install kolla without vagrant... but, you'd need to create the VM youself21:49
*** jtriley has joined #openstack-kolla21:51
rajathagasthyavhosakot: I think it's not a Vagrant problem. It's something I encounter during kolla-build.21:52
rajathagasthya"ERROR:kolla.cmd.build:base:The command '/bin/sh -c rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7     && yum install -y epel-release yum-plugin-priorities     && rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7     && yum clean all' returned a non-zero code: 1"21:52
vhosakotah, so vagrant is good ?21:52
rajathagasthyaYeah, vagrant is good.21:53
vhosakotjust rebuild multiple times... I have seen some images faul to build if repos are unavailable... rebuild fixes it for me21:53
*** jtriley has quit IRC21:56
*** dougs1 has joined #openstack-kolla21:57
manjeetshttp://paste.openstack.org/show/492504/21:59
*** dougs has quit IRC22:00
vhosakotmanjeets: awesome!22:00
gmmahahttps://bugs.launchpad.net/kolla/+bug/156410822:00
openstackLaunchpad bug 1564108 in kolla "Add libvirt disable at prechecks" [Undecided,New]22:00
* manjeets was warming up deployment horizon gave up22:00
vhosakotmanjeets: can you sent "neutron port-list | grep ip | wc -l"22:00
manjeets neutron port-list | grep ip | wc -l22:01
manjeets102322:01
*** mlima_ has joined #openstack-kolla22:01
vhosakotone network ?22:01
sdakemanjeets was that with heat?22:01
inc0do we have meeting now?22:02
manjeetsno horizon22:02
sdakeinc0 in 1 hour bro22:02
vhosakot58 more mins... DLS22:02
inc0DLS22:02
inc0-.-22:02
manjeetsit was 1000 last night22:02
sdakewe run on utc time in openstac k;-)22:02
manjeetssdake i see multiple ip issue need to debug that22:02
sdakemanjeets did yu figureou thow to dleete 1000 nova vms quickly?22:03
* manjeets will use re deploy 22:03
manjeetshe gave up with heat temprarily22:03
*** GonZo2000 has quit IRC22:03
manjeetsre deploy took 11 minutes22:04
*** mlima has quit IRC22:05
*** GonZo2000 has joined #openstack-kolla22:05
*** GonZo2000 has joined #openstack-kolla22:05
inc0keystone is strange22:05
inc0-.-22:05
inc0I almost forgot how I used to hate it22:06
vhosakotgmmaha: I see you filed https://bugs.launchpad.net/kolla/+bug/1564108...22:06
openstackLaunchpad bug 1564108 in kolla "Add libvirt disable at prechecks" [Undecided,New]22:06
vhosakotgmmaha: does precehcks pass for you when libvirt is enabled ?22:06
openstackgerritHui Kang proposed openstack/kolla: Add etcd Docker container  https://review.openstack.org/29845122:07
manjeetshttp://paste.openstack.org/show/492508/22:08
manjeetssome got 2 ips22:08
gmmahavhosakot: yeah.. if i have stopped the service, it passes.. but on reboot it gets restarted again..22:08
gmmahawould be nice to have it say 'go ahead and disable it with such commands'22:08
*** jtriley has joined #openstack-kolla22:09
gmmahaand ohh if you have cloud-init running the disable option that you shared or the remove option that i shared with update-rc.d doesnt work22:09
gmmahai had to force un-isntalled libvirt-bin from the machines22:09
vhosakotgmmaha: wait... I want to understand more22:11
vhosakotgmmaha: does precehecks pass if libvirt is enabled ?22:12
gmmahavhosakot: prechecks pass if libvirt is enabled and not running22:12
vhosakotok22:12
vhosakotgmmaha: does precehecks pass if libvirt is running ?22:12
sdakemeaning when you reboot, your deployment no longer works22:12
gmmahavhosakot: no.. they wont pass if its running on the host22:12
vhosakotgmmaha: ah that is good...22:13
vhosakotgmmaha:  the bug-fix would be flag an error if libvirt is enabled and not running ?22:13
gmmahavhosakot: right..22:13
vhosakotok22:13
gmmahaif its even enabled, lets fail precheck and ask them to remove it22:14
vhosakotgmmaha: do you run prechecs after every reboot22:14
sdakevhosakot you shouldn't need to run prechecks after a reboot ;-)22:14
gmmahavhosakot: no..22:14
*** jtriley has quit IRC22:15
vhosakotgmmaha: what happens if you reboot _before_ deploying ?22:16
vhosakotgmmaha: is libvirt enabled again after reboot ?22:16
gmmahavhosakot: libvirt would restart and deploy will happen, but VMs wont work22:16
vhosakotgmmaha: wait22:17
gmmahavhosakot: right.. it gets re-enabled *if* you have cloud-init on the machine.. which i think they will have22:17
*** ccesario_ has joined #openstack-kolla22:17
vhosakotyou reboot the compute node or deploy node ?22:17
gmmahacompute nodes..22:18
vhosakotgmmaha: you deploy kolla, reboot compute node, VM's dont work.. correct ?22:18
gmmahavhosakot: the cloud-init is a speculation.. i mgiht be wrong on why libvirt service gets restarted after reboot.. even after i disable using update-rc.d and even remove it22:19
gmmaharemove it == 'update-rc.d -f libvirt-bin remove'22:19
vhosakotand VMs work after removing ?22:20
gmmahavhosakot: not sure yet..22:21
gmmahatesting itnow22:21
*** diogogmt_ has quit IRC22:21
*** vishwanathj has quit IRC22:27
*** mbound has quit IRC22:28
*** unicell has quit IRC22:32
*** unicell1 has joined #openstack-kolla22:32
*** rhallisey has joined #openstack-kolla22:35
sdakeeven after removing libvirt, the shared object is still busted22:37
sdakei think the ld.so.cache may be busted22:37
sdakebut hard to tell22:37
sdakecontainers = magic ;)22:37
vhosakotha22:37
*** rajathagasthya has quit IRC22:42
*** sdake has quit IRC22:46
*** sdake has joined #openstack-kolla22:46
*** rajathagasthya has joined #openstack-kolla22:48
gmmahavhosakot: should the kolla_toolbox have 'bin/sleep infinity' on it? the container seems to be up with that command22:50
gmmahasdake: same error.. libvirt container is restarting22:51
gmmahaand the same libvirt-admin.so.0: cannot open shared object file: Permission denied22:51
sdakegamyes22:51
sdakegmmaha yes22:51
sdakegmmaha type dmessg and see if anytyhing pops up22:51
gmmahasdake: aah ok.. (guessing yes is about kolla_toolbox)22:51
sdakeyes toolbox22:52
gmmahaholy!!22:52
gmmahahttp://paste.openstack.org/show/492513/22:52
vhosakotkolla_toolbox has always had sleep infinity... it should not affect any containers...22:52
sdakeya apparmor22:53
sdakei suggested turning that off early on22:53
gmmahasdake: but its not running and i thought i had turned it off.22:53
sdakeclearly its not turned off ;-)22:53
gmmaha:)22:54
*** SiRiuS_ has quit IRC22:54
* gmmaha goes to go through the ritual 22:55
ntpttrgmmaha: when did apparmor start running? was it installed when we had a working deployment?22:55
gmmahantpttr: not sure whne it got isntalled..22:56
sdakei have heard reports kolla works with apparmor22:56
gmmahai for one, definitely did not install it22:56
sdakeapparmor is on by default22:56
sdakevhosakot do you run with apparmor?22:56
vhosakotno.. whatever is default22:56
vhosakotsudo apparmor_status22:57
vhosakot$ sudo apparmor_status | grep libvirt22:58
*** Jeffrey4l has joined #openstack-kolla22:59
*** prithiv1 has joined #openstack-kolla23:00
inc0meeting time?23:00
*** prithiv has quit IRC23:00
inc0or my clock lies to me again?23:00
asalkeld_yeah23:00
inc0(I don't trust this bastard any more)23:00
asalkeld_haha23:00
sdakeirc meeting now folks23:02
sdakefeel free to join us on #openstack-meeting-423:02
sdakejpeeler rhallisey23:03
gmmahavhosakot: http://paste.openstack.org/show/492514/23:04
vhosakotdont know if it affects23:04
gmmahavhosakot: it says its in enforce mode23:04
gmmahahttp://paste.openstack.org/show/492515/23:05
*** blahRus has quit IRC23:05
*** prithiv has joined #openstack-kolla23:07
*** prithiv1 has quit IRC23:08
*** Jeffrey4l_ has joined #openstack-kolla23:15
gmmahavhosakot: for now i will go and remove apparmor for our testing23:16
vhosakotyes, good test...23:16
*** Jeffrey4l has quit IRC23:16
vhosakotalthough I doubt default apparmour affects OpenStack23:16
*** banix has joined #openstack-kolla23:18
*** salv-orl_ has joined #openstack-kolla23:24
*** prithiv has quit IRC23:26
*** salv-orlando has quit IRC23:26
*** Jeffrey4l__ has joined #openstack-kolla23:32
*** Jeffrey4l__ is now known as Jeffrey4l23:32
*** Jeffrey4l_ has quit IRC23:33
*** prithiv has joined #openstack-kolla23:33
gmmahawooohoooo..23:36
vhosakot?23:36
gmmaharemove apparmor and things work now!23:36
vhosakotreally ?23:36
gmmahaatleast libvirt container hasnt died23:37
gmmahaohh yeah!23:37
vhosakotnova_libvirt container is up ?23:37
* gmmaha goes to check the dashboard23:37
gmmahavhosakot: yeah23:37
vhosakotcan you cehckt he VMs please ?23:37
gmmahavhosakot: yeah starting to create the role and will spin up a VM23:37
gmmahaohh hold on23:38
gmmahadeployment failed23:38
gmmahahttp://paste.openstack.org/show/492517/23:38
vhosakotre-deloy ?23:38
gmmahavhosakot: yeah23:38
gmmahadoing that now23:38
*** inc0 has quit IRC23:44
*** inc0 has joined #openstack-kolla23:44
*** achanda has joined #openstack-kolla23:45
*** Jeffrey4l_ has joined #openstack-kolla23:45
*** Jeffrey4l has quit IRC23:46
gmmahavhosakot: re-deployed nad still the same error..23:47
gmmahathere is definnitely somethign wrong in the patches since the last time i had23:47
gmmahawhere i could rdeploy consistently23:47
* gmmaha goes to look at the patch log23:48
*** rajathagasthya has quit IRC23:50
*** rajathagasthya has joined #openstack-kolla23:53
inc0ok, I'm going to grab a scotch, have a fun evening guys23:55
inc0I will23:55
vhosakotenjoy! :)23:55
gmmahahave fun inc023:55
*** inc0 has quit IRC23:55
Jeffrey4l_sdake, could u explain why kolla-toolbox need root privilege? https://review.openstack.org/#/c/298479/7/docker/kolla-toolbox/Dockerfile.j223:56
Jeffrey4l_vhosakot, ^23:56
openstackgerritSteven Dake proposed openstack/kolla: Fix gate by adding MariaDB-shared dependnecy  https://review.openstack.org/29968123:56
sdakeneeds workflow here plz23:56
sdakeJeffrey4l_ th patch thta merged removed that debug cruft23:57
sdakei needed root so i coudl debug the enironment temporarily23:58
sdakeand accidentially git reviewed that atch23:58
sdakedont look at changeset 7 look at changeset 823:58
Jeffrey4l_sdake, clearly. my bad. Thanks23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!