Just clarifying:

I have created an external network (including a subnet).
openstack network create --share --external --provider-network-type vlan provider-external --provider-physical-network physnet0

Then I have created internal network using GUI. Used 'Networks' tab under Projects > Network.
But it failed with the following error.

"Failed to create network "internal-net": Unable to create the network. No tenant network is available for allocation."

But when I try to create internal network under "Admin > Network > Networks", still I need to provide physical network like in external network creation.
So, do I need to create both external and internal network using the same physical network?



On Wed, Jun 16, 2021 at 8:57 PM open infra <openinfradn@gmail.com> wrote:



worker-0 contin following under /var/log/pods


kube-system_calico-node-brhq2_b3e3c8d7-ebeb-405a-af83-a19240d82997                         openstack_neutron-metadata-agent-worker-0-13cc482d-6tgrf_88f4f98d-4526-4148-b99c-4e2ee9072995

kube-system_kube-multus-ds-amd64-k4pr4_1b0342da-641c-4248-a3ad-c67a9f8bcce5                openstack_neutron-ovs-agent-worker-0-13cc482d-6m9sw_0bc04a1a-8d36-4a37-99b3-19f6ebba9856

kube-system_kube-proxy-8hv88_dc495497-b346-4b28-ac5d-5aec9848f886                          openstack_neutron-sriov-agent-worker-0-13cc482d-22rsz_a09c060e-3c4b-4aae-ad7f-ec2f96c0fcc3

kube-system_kube-sriov-cni-ds-amd64-5rpfv_02eab05d-eb1b-4a17-8559-8e6809d830d7             openstack_nova-compute-worker-0-13cc482d-27k2r_dcdd6855-b3e3-4137-b582-2fb665569490

openstack_libvirt-libvirt-default-4dcqc_c29b390b-7b69-4661-b0ac-cfc7b8c2d175               openstack_openvswitch-db-pnvcp_2855de13-37a7-4045-8444-0bbb54a6d8f3

openstack_neutron-dhcp-agent-worker-0-13cc482d-7pt4l_219e142a-1277-4b29-b4b5-dd365db4efb8  openstack_openvswitch-vswitchd-scrmc_c9eb3f17-9383-4f04-80bf-1cb63550d092

openstack_neutron-l3-agent-worker-0-13cc482d-7sfnp_ee272908-5710-4d2d-9206-8ec20a91ff10    openstack_osh-openstack-garbd-garbd-58dc7995cf-7hrd9_0366de80-b0d7-428e-8e6f-a9206231fd7a


On Wed, Jun 16, 2021 at 8:08 PM Braden, Albert <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>
Sent: Wednesday, June 16, 2021 9:12 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.

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> 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>
Sent: Wednesday, June 16, 2021 1:36 AM
To: openstack-discuss <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.

 

 

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.