Comment 27 for bug 1827692

After setting up the proper hardware. It looks that the issue is no longer present in the following ISO image:

controller-0:/home/sysadmin# cat /etc/build.info
###
### StarlingX
### Release 19.01
###

OS="centos"
SW_VERSION="19.01"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="r/stx.2.0"

JOB="STX_BUILD_2.0"
<email address hidden>"
BUILD_NUMBER="14"
BUILD_HOST="starlingx_mirror"
BUILD_DATE="2019-08-08 01:30:00 +0000"

controller-0:/home/sysadmin# openstack server create --image cirros --flavor my_tiny --network public-net0 --security-group security1 richo1
+-------------------------------------+------------------------------------------------+
| Field | Value |
+-------------------------------------+------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | |
| OS-EXT-SRV-ATTR:host | None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | |
| OS-EXT-STS:power_state | NOSTATE |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | None |
| OS-SRV-USG:terminated_at | None |
| accessIPv4 | |
| accessIPv6 | |
| addresses | |
| adminPass | pjPqYs7jfCPJ |
| config_drive | |
| created | 2019-08-13T09:39:39Z |
| flavor | my_tiny (200d48ce-52bb-4ce5-9768-113c1ff0926a) |
| hostId | |
| id | 68a88f0c-65c7-499a-8e7e-aa16ddc47a47 |
| image | cirros (2c56b5dc-109e-44c5-b0c1-f3d611814abd) |
| key_name | None |
| name | richo1 |
| progress | 0 |
| project_id | c863ebfbbcbc4683859acbf4dc5f8d6b |
| properties | |
| security_groups | name='dd393bca-b9c7-4f86-8594-7ff80b8b40b3' |
| status | BUILD |
| updated | 2019-08-13T09:39:39Z |
| user_id | 78cb551a797c4c72ada6cd0e44114b8e |
| volumes_attached | |
+-------------------------------------+------------------------------------------------+

+--------------------------------------+--------+--------+----------------------------+--------+---------+
| ID | Name | Status | Networks | Image | Flavor |
+--------------------------------------+--------+--------+----------------------------+--------+---------+
| 68a88f0c-65c7-499a-8e7e-aa16ddc47a47 | richo1 | ACTIVE | public-net0=192.168.101.43 | cirros | my_tiny |
+--------------------------------------+--------+--------+----------------------------+--------+---------+

The VM is up and running, marked as ACTIVE status.

So the issue is no longer present.

Thanks