Tuesday, 2018-12-18

*** itlinux has quit IRC00:02
*** jamesmcarthur has joined #openstack-trove01:14
*** jamesmcarthur has quit IRC01:19
*** rcernin has quit IRC03:25
*** zhangfei has joined #openstack-trove03:26
*** rcernin has joined #openstack-trove03:27
*** rcernin has quit IRC03:28
*** rcernin has joined #openstack-trove03:28
*** zhangfei has quit IRC04:10
*** Bhujay has joined #openstack-trove04:20
*** Bhujay has quit IRC04:21
*** Bhujay has joined #openstack-trove04:21
*** Bhujay has quit IRC04:22
*** Bhujay has joined #openstack-trove04:23
*** zhangfei has joined #openstack-trove04:30
*** itlinux has joined #openstack-trove05:45
*** zhangfei has quit IRC08:02
*** zhangfei has joined #openstack-trove08:24
bzurkowskitomtom: Sorry for late response09:06
bzurkowskiWhat I suspected was that you had wrong image reference set for your datastore ("in datastore tables")09:06
bzurkowskiThis is why I asked whether image reference on VM is correct09:07
bzurkowskiAfter you cleared datastore tables and reloaded image into Trove, the image was set correctly and the VM booted successfully09:10
bzurkowskiNow, Trove boots VMs with correct image instead of obsolete one that was loaded initialy09:10
bzurkowskiThis is one possible scenario09:10
bzurkowskiAnyway, the VM booted and we are one step foreward09:13
bzurkowskiGood news :)09:13
bzurkowskiRegarding access to Trove instance09:16
bzurkowski"keys not staged by host"09:17
bzurkowskiWhat is the context of this error?09:17
bzurkowskiDoes it occur while building VM image using diskimage builder?09:17
*** rcernin has quit IRC09:18
*** Bhujay has quit IRC09:24
*** dkehn has quit IRC09:57
*** maciejjozefczyk has quit IRC10:01
*** Bhujay has joined #openstack-trove10:02
*** maciejjozefczyk has joined #openstack-trove10:03
*** Bhujay has quit IRC10:03
*** Bhujay has joined #openstack-trove10:04
*** Bhujay has quit IRC10:05
*** Bhujay has joined #openstack-trove10:05
*** Bhujay has quit IRC10:06
*** Bhujay has joined #openstack-trove10:07
*** maciejjozefczyk has quit IRC10:25
*** maciejjozefczyk has joined #openstack-trove10:36
*** zhangfei has quit IRC11:19
*** Bhujay has quit IRC11:46
*** Bhujay has joined #openstack-trove11:52
*** Bhujay has quit IRC11:53
*** Bhujay has joined #openstack-trove11:53
*** Bhujay has quit IRC11:54
*** Bhujay has joined #openstack-trove11:55
*** Bhujay has quit IRC11:56
*** Bhujay has joined #openstack-trove11:56
*** Bhujay has quit IRC11:57
*** Bhujay has joined #openstack-trove11:58
*** Bhujay has quit IRC11:59
*** Bhujay has joined #openstack-trove11:59
*** Bhujay has quit IRC12:00
*** Bhujay has joined #openstack-trove12:01
*** dkehn has joined #openstack-trove12:52
*** zhangfei has joined #openstack-trove13:42
*** zhangfei has quit IRC13:52
*** pgodek has joined #openstack-trove14:07
*** Bhujay has quit IRC14:53
tomtom001bzurkowski: so the context of the error is during the diskimage builder process.  The script I showed you seems to always fail no matter what.  I've read the bash script and I don't see where any failures should come into play, however, I can verify that the script doesn't seem to create the ssh keys as it should.14:59
*** itlinux has quit IRC15:00
*** jamesmcarthur has joined #openstack-trove15:59
*** jamesmcarthur has quit IRC15:59
*** jamesmcarthur has joined #openstack-trove15:59
*** itlinux has joined #openstack-trove16:04
*** itlinux_ has joined #openstack-trove16:08
*** itlinux has quit IRC16:12
*** spa-87 has joined #openstack-trove16:27
tomtom001bzurkowski: now I'm getting sudo unable to resolve hostname: <servername>16:42
*** tosky has joined #openstack-trove17:06
*** jamesmcarthur has quit IRC17:16
*** spa-87 has quit IRC17:20
*** jamesmcarthur has joined #openstack-trove17:52
bzurkowskiI found some archival content that may be helpful for your situation18:11
bzurkowskiThe same "keys not staged by host" issue was reported on our channel a while ago:18:11
bzurkowskihttp://eavesdrop.openstack.org/irclogs/%23openstack-trove/%23openstack-trove.2017-05-18.log.html18:11
bzurkowskiAbove conversation links to the following page:18:12
bzurkowskihttps://www.mail-archive.com/openstack-dev@lists.openstack.org/msg20137.html18:12
bzurkowskiOne of our colleagues prepared a detailed note on building guest images and installing Trove via Devstack:18:14
bzurkowskihttps://docs.google.com/document/d/17jQYV0X-qy6s1NwgU-bYJVt6oQBsaNSn5TZZkr1SQsg/edit?usp=sharing18:14
bzurkowskiIt might be helpful as well18:15
bzurkowskiWhat's more, Trove team is currently working on adding image image building support to Trove Devstack plugin:18:16
bzurkowskihttps://review.openstack.org/#/c/606960/18:16
bzurkowskiIt is ready and awaits review18:16
bzurkowskiLet me know if any of the provided resources was helpful for you ;)18:16
*** itlinux_ has quit IRC18:21
*** itlinux has joined #openstack-trove18:21
tomtom001dd: failed to open '/openstack/trove_images/backup/trove_guest/authorized_keys'18:43
tomtom001no matter where I put that file or how I permission it, that file cannot be found by the script: vi trove/integration/scripts/files/elements/ubuntu-guest/install.d/62-ssh-key18:44
tomtom001bzurkowski: I reviewed the documentation, but the devstack setup seems to be much different than a production setup, so it doesn't seem I can follow it to well.  and that bug didn't see any activity and after searching the trove documentation I could not find anything on ssh keygen18:50
*** jamesmcarthur has quit IRC20:58
*** rcernin has joined #openstack-trove21:22
*** jamesmcarthur has joined #openstack-trove21:26
*** jamesmcarthur has quit IRC21:27
*** jamesmcarthur has joined #openstack-trove21:27
*** jamesmcarthur has quit IRC21:30
*** rcernin has quit IRC21:37
*** cezary_zukowski_ has joined #openstack-trove21:45
cezary_zukowski_tomtom001: responding to your concerns, I created some debuging information that might help you understand what is going under the hood, https://drive.google.com/drive/folders/1Owog_d4cNA4RaJIlcsMBXPgmiJVd5Fec?usp=sharing21:46
cezary_zukowski_please start with how_to_debug.txt21:47
cezary_zukowski_then, you can understand how ssh keys are copied around, i.e. I used checksums to verify whether the keyfiles are identical21:48
cezary_zukowski_examine the *.log files to understand that:21:48
cezary_zukowski_a0388e7a9d7177347e2637385a2c7ebd  /tmp/dib_build.pjaUtqhs/hooks/id_rsa  2018-12-18 21:20:30.098 | + md5sum /home/ubuntu/.ssh/id_rsa 2018-12-18 21:20:30.101 | a0388e7a9d7177347e2637385a2c7ebd  /home/ubuntu/.ssh/id_rsa21:48
cezary_zukowski_tomtom001: ^21:48
cezary_zukowski_tomtom001: i.e. the checksums are equal21:49
cezary_zukowskitomtom001: also, pay attention to the fact that extra.d is run before install.d and that install.d is in chroot environment (e.g. run as "inside" image, as far as I understand correctly)21:51
tomtom001bzurkowski, cezary_zukowski_  so I got an image to build.  The issues that I ran into were 1) Don't run as root user:  while the image is successfully built I believe it is built incorrectly;  2) Since it's running in a chroot environment, I believe not all directories such as ones in / and in /home are not necessarily available.  By copying my .ssh files to a directory that is in chroot such21:55
tomtom001as /root (in my case) now the files can be found.  3) Whatever user is running the disk-image-create command should have write access to the directory from where it is run because the qcow2 image and manifest will be written there.21:55
cezary_zukowskitomtom001: that's great, lets continue chat tomorrow :)22:00
tomtom001no problem, I appreciate your help.22:01
tomtom001I now need to get the image to update in trove and get it to boot without no bootable device error22:01
*** rcernin has joined #openstack-trove22:04
*** jamesmcarthur has joined #openstack-trove22:11
*** jamesmcarthur has quit IRC22:16
*** rcernin has quit IRC22:37
*** dkehn has quit IRC22:40
*** dkehn has joined #openstack-trove22:41
*** rcernin has joined #openstack-trove22:41
*** rcernin has quit IRC22:43
*** rcernin has joined #openstack-trove22:45
*** itlinux has quit IRC22:56
*** tosky has quit IRC23:40

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