Both links show the conductor log. It tells us that no valid host was found. The scheduler log should show why no valid host was found. From: open infra <openinfradn@gmail.com> Sent: Thursday, June 17, 2021 2:02 AM To: Braden, Albert <C-Albert.Braden@charter.com> Cc: openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: [EXTERNAL] Error creating VMs CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance. Found nova-conductor and nova-scheduler logs [1],[2]. But I have no idea about what caused this issue. [1] http://paste.openstack.org/show/806720/ [2] http://paste.openstack.org/show/806721/ On Wed, Jun 16, 2021 at 8:08 PM Braden, Albert <C-Albert.Braden@charter.com<mailto:C-Albert.Braden@charter.com>> wrote: Someone will need to dig through the starlingx documentation and figure out where the log files are located. Do you want to do that? https://docs.starlingx.io/ From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Wednesday, June 16, 2021 9:12 AM To: Braden, Albert <C-Albert.Braden@charter.com<mailto:C-Albert.Braden@charter.com>> Cc: openstack-discuss <openstack-discuss@lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> Subject: Re: [EXTERNAL] Error creating VMs CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance. I can see sm-scheduler.log not sure if its the correct log file you mentioned, but I can't see conductor log. This environment have been deployed using starlingx. On Wed, Jun 16, 2021 at 6:16 PM Braden, Albert <C-Albert.Braden@charter.com<mailto:C-Albert.Braden@charter.com>> wrote: Can you check the scheduler and conductor logs on the controllers? There should be entries describing why the instance failed to schedule. You may need to set “debug=true” in nova.conf to get more details. From: open infra <openinfradn@gmail.com<mailto:openinfradn@gmail.com>> Sent: Wednesday, June 16, 2021 1:36 AM To: openstack-discuss <openstack-discuss@lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> Subject: [EXTERNAL] Error creating VMs CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance. Hi After setting up OpenStack environment using STX R5 (two controllers, two storage nodes and one worker), I have deployed a VM. VM ended up with ERROR status. I highly appreciate if someone can guide to dig further (what logs to check ) or to fix this issue. http://paste.openstack.org/show/806626/ Regards Danishka The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited. The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.