Wednesday, 2017-08-16

*** brault has quit IRC00:00
*** brault has joined #openstack-dib04:16
*** brault has quit IRC04:21
*** brault has joined #openstack-dib04:46
*** brault has quit IRC04:50
hwoarangclarkb: i am going to provide that info on the bug right now04:54
*** chhavi has joined #openstack-dib04:58
*** chhavi has quit IRC05:00
*** aparnav has joined #openstack-dib05:08
*** brault has joined #openstack-dib05:44
*** aparnav has quit IRC05:48
*** brault has quit IRC05:48
*** brault has joined #openstack-dib06:05
*** brault has quit IRC06:10
*** aparnav has joined #openstack-dib06:38
*** isaacb has joined #openstack-dib07:19
*** brault has joined #openstack-dib07:25
*** brault has quit IRC07:40
*** brault has joined #openstack-dib07:49
*** isaacb has quit IRC08:14
*** isaacb has joined #openstack-dib08:27
*** tumbarka has joined #openstack-dib09:40
tumbarkaHi All09:42
tumbarkaWhere to find the find the default usernam/ paswword for instnace created using DIB image09:43
tumbarka?09:43
openstackgerritMerged openstack/diskimage-builder master: Increase timeout for removal  https://review.openstack.org/49302609:45
*** aparnav has quit IRC10:57
ianwtumbarka: you'll need cloud-init or something to set it up.  or see the devuser documentation to bake in a user11:01
tumbarkaianw : ok11:08
tumbarkaI am looking into DIB image creation steps..where I can add the default credentials11:09
*** isaacb has quit IRC11:09
*** isaacb has joined #openstack-dib11:10
tumbarkaianw : before that I am facing one issue in  our third party CI setup11:10
tumbarkaThe DIB is created in CI setup on daily basis, the problem  is the instances created using latest DIB image are not accessible(ping and ssh is not working). Using old DIB image (5 -6 days old) I can create the instance which is accessible11:12
tumbarkaYou have any idea are there any changes in any repository which is causing this failure?11:13
*** aparnav has joined #openstack-dib11:16
*** brault has quit IRC11:31
*** aparnav has quit IRC11:34
*** aparnav has joined #openstack-dib11:34
*** brault has joined #openstack-dib11:56
*** farosas has joined #openstack-dib12:16
*** aparnav has quit IRC12:17
*** aparnav has joined #openstack-dib12:18
*** isaacb has quit IRC13:04
*** isaacb has joined #openstack-dib13:04
*** brault has quit IRC13:09
*** brault has joined #openstack-dib13:09
*** aparnav has quit IRC14:30
*** aparnav has joined #openstack-dib14:36
clarkbtumbarka: a list of the elements you are using to build the image would be useful when debugging that sort of problem15:13
*** aparna has joined #openstack-dib15:21
*** aparnav has quit IRC15:23
*** appu103 has joined #openstack-dib15:25
*** aparna has quit IRC15:28
*** aparnav has joined #openstack-dib15:38
*** appu103 has quit IRC15:40
*** brault has quit IRC15:41
*** yolanda has quit IRC15:44
*** yolanda has joined #openstack-dib15:44
*** brault has joined #openstack-dib15:45
*** isaacb has quit IRC15:52
*** Sukhdev_ has joined #openstack-dib15:53
*** tumbarka_ has joined #openstack-dib15:53
*** isaacb has joined #openstack-dib16:27
*** aparnav has quit IRC16:30
tumbarka_clarkb: Here is the list of elements in our CI setup - https://gist.github.com/anonymous/a3d1e58abe8cb55937127ef28a8929cb16:38
clarkbtumbarka_: ok so there are two ways things can be set up. First is using dib to bake in a user. The second is passing ssh key metadata via config drive which glean/simple-init will use to set up ssh access for the root user16:39
tumbarka_clarkb : The DIB image which was built using same elements was working before Friday...after that we are facing this issue16:39
clarkbtumbarka_: the nodepool base element will attempt to use the NODEPOOL_SSH_KEY variable to set that if available16:41
clarkbmy guess is you were setting that env var at one time and now are not16:41
tumbarka_clarkb : now also  we are setting this NODEPOOL_SSH_KEY env variable16:43
tumbarka_I have verified this16:43
clarkbtumbarka_: have you double checked it is in the process env via /proc?16:44
clarkbif so then the other thing I would check is that the private ssh key you have matches the public ssh key set inthat variable16:44
tumbarka_I have verified in nodepool logs..the NODEPOOL_SSH_KEY is set   also it is matching with the private key16:51
clarkbtumbarka_: ok the next thing I would check is mount your image and see if the key is in the user's authorized_keys file as expected16:51
tumbarka_One more I would like to add here...the nodes which re launched with this new image are not pingable16:51
clarkbtumbarka_: could it be possible that you updated your security groups?16:52
tumbarka_means they are not reachable16:52
tumbarka_nope....I have checked security group  rules for both tcp and icmp are added16:52
clarkbtumbarka_: I would try booting a vanilla ubuntu image just to confirm general cloud connectivity works as expected and go from there16:54
clarkbif it doesn't work then look at the cloud if it does work then look at the image16:54
tumbarka_I was trying to access the instance's console  from dashboard but it requires the username and password..16:54
tumbarka_One more thing which I tested here is - I have launched the instance using old DIB image which was present in provider , this instance is pingable and able to ssh as well16:56
*** strigazi_OFF is now known as strigazi17:00
*** aparnav has joined #openstack-dib17:02
*** isaacb has quit IRC17:07
*** Sukhdev_ has quit IRC17:09
tumbarka_clarkb : with vanilla (plane) ubuntu created VM which accessible too17:09
clarkbtumbarka_: ok then I would mount the image then and start poking at it17:10
tumbarka_Is there any way to access the instance (created using DIB image ) without ssh key....I mean using username password , just to dig more inside the instance17:13
tumbarka_clarkb : I found one solution ...using devuser element...but I think this element is very old and it is not present ow17:14
tumbarka_now*17:14
clarkbit is still in use I use it locally all the time17:15
clarkband yes that is one way.17:15
tumbarka_clarkb : to add this element devuser , I need to  modify the nodepool.yaml and also need to add one folder in /etc/nodepool/element/  ...right?17:21
tumbarka_But didnt found anything related to devuser , which we to modify in /etc/nodepool/element/17:22
clarkbtumbarka_: devuser is built in to dib so you don't have to modify /etc/nodepool/element17:23
clarkbtumbarka_: you just have to update nodepool.yaml17:23
tumbarka_then , how will it set the environment variable  related to devuser?17:26
tumbarka_all the variables  mentioned here are mandatory?  - https://docs.openstack.org/diskimage-builder/latest/elements/devuser/README.html17:28
clarkbnot all of them are mandatory, you only have to set those that you want, say a password and sudo17:34
clarkb(not sure if sshd config will allow password login though)17:35
clarkband you set the env vars in the nodepool.yaml17:35
clarkbhttps://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/nodepool.yaml#n1234 is an example17:35
tumbarka_clarkb : ok. will try that. Thank  you17:37
*** strigazi is now known as strigazi_OFF17:55
*** Sukhdev has joined #openstack-dib18:51
*** aparnav has quit IRC18:56
*** Sukhdev has quit IRC19:43
*** tumbarka_ has quit IRC20:12
*** Sukhdev has joined #openstack-dib20:13
*** brault has quit IRC20:49
*** farosas has quit IRC21:34
*** brault has joined #openstack-dib22:49
*** brault has quit IRC22:54

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