ashishjain: yest. I did not get around to running your patch
was busy trying to fix the gate
tried two different approaches but still the gate is not yeilding
today, I am thinking of reaching out to folks from the tempest team
hopefully they will be able to provide some clues
lets chat during the meeting of others have any ideas
ashishjain
Yeah sure
What is the error we are hitting
devkulkarni
basically none of the solum services are starting up
ashishjain
Ohhj
devkulkarni
we are using the new devstack plugin model
which is what the devstack team has advised all the teams to use
we converted to using this sometime in november
and things have been working
but something must have changed in the devstack setup in early december
alright.. lets chat during the meeting
ashishjain
Yeah sure
I m on mobile todau
Some problem with my broadband
devkulkarni
oh I see
dimtruck, vijendar: solum team meeting has started in openstack-meeting-3
blomquisg joined the channel
phiche has quit
phiche joined the channel
kebray has quit
kebray joined the channel
gpilz joined the channel
ashishjain has quit
ashishjain joined the channel
kebray has quit
sabeen1 joined the channel
ashishjain has quit
will be back after lunch in 30 mins
james_li has quit
james_li joined the channel
devkulkarni has quit
sabeen1 has quit
james_li has quit
devkulkarni joined the channel
james_li joined the channel
sabeen1 joined the channel
dimtruck: started the devstack setup
dimtruck
me too
vijendar has quit
sabeen3 joined the channel
devkulkarni
dimtruck: from here: https://etherpad.openstack.org/p/solum_devstack... .. in line 60 there is 'solum' at the start of the list of services.. we don't have any service with that name. I am wondering if that is tripping the devstack gate.. in the run-patch script, I have removed 'solum' from that list and have only kept the actual solum services (solum-api, solum-conductor, solum-deployer, solum-worker)