Hello again! I have done some more research and discovered that the volume never gets attached to the instance. I tried to do this manually and got error message. I fixed the problem by starting tgtd service (it was disabled on my desktop).
Now the image successfully attaches, but the issue persists and creation does not proceed any further. In order to be able to see the actual error messages I set Debug = False for cinder, heat and magnum. Now the last messages in logs are: Cinder-volume: INFO cinder.volume.manager [req-c0bce579-5cb3-4c2e-9e47-809407899017 7d92d42ebf5c4c379b2e6f092c7863ba 141dbc1cd0154ae397a9b00371f99eaf] Attach volume completed successfully. Heat-engine: 2016-01-26 16:59:06.079 INFO heat.engine.resource [-] creating Server "kube_master" Stack "None-q6tmlfyzvrxr-kube_masters-3a2nhl5h7ugj-0-7bronij32gu2" [52d9f83a-c334-44b2-aa93-eec92ec5955b] 2016-01-26 16:59:16.536 INFO heat.engine.resource [-] creating CinderVolumeAttachment "docker_volume_attach" Stack "None-q6tmlfyzvrxr-kube_masters-3a2nhl5h7ugj-0-7bronij32gu2" [52d9f83a-c334-44b2-aa93-eec92ec5955b] 2016-01-26 16:59:17.359 INFO heat.engine.resource [-] creating HeatWaitCondition "master_wait_condition" Stack "None-q6tmlfyzvrxr-kube_masters-3a2nhl5h7ugj-0-7bronij32gu2" [52d9f83a-c334-44b2-aa93-eec92ec5955b] 2016-01-26 16:59:22.387 INFO heat.engine.clients.os.cinder [-] Attaching volume abce26c5-c460-4895-ae6d-d7772eeeb988 complete 2016-01-26 16:58:36.564 INFO magnum.common.cert_manager.barbican_cert_manager [req-2a45efe0-a458-483a-a573-40746d198c0b demo demo] Storing certificate container 'b9af5417-7294-40fe-9fe9-d7b8a08aa4d5' in Barbican . Magnum-engine: 2016-01-26 16:58:36.950 INFO magnum.common.cert_manager.barbican_cert_manager [req-2a45efe0-a458-483a-a573-40746d198c0b demo demo] Storing certificate container 'Magnum-Conductor' in Barbican. And that’s all. Complete silence after this. Any ideas? Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia From: Jay Lau [mailto:[email protected]] Sent: 26 января 2016 г. 12:08 To: Pavel Fedin Cc: [email protected] Subject: Re: [Openstack] Magnum bay takes forever to create I think that you can check heat log first to see if there are anything wrong with the stack creation, then check related component log such as cinder, neutron etc to see what is wrong. On Tue, Jan 26, 2016 at 3:53 PM, Pavel Fedin <[email protected] <mailto:[email protected]> > wrote: Hello everybody! I am quite new to OpenStack, and need to dive into it because of goals of our project. So far, I have installed devstack and tried to create Magnum bay. And I have hard time doing it. I successfully defeated "missing losetup" problem, and now I have the next one. Creation process never goes past "kube_masters create in progress" point. I see that Cinder volume is initialized and in "Available" state, but it seems to be not attached to anything (as far as I currently understand things, it has to be attached to VM instance holding my bay). There are no error messages in logs. How to debug this and does anybody know, what can be the reason ? Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] <mailto:[email protected]> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Thanks, Jay Lau (Guangya Liu)
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
