[Starlingx-discuss] StarlingX R4.0 Baremetal Duplex standard controller storage ironic deployment mode: Baremetal node not creation issue.

[Liu, ZhipengS]

Hi Akshay,
It seems related to the centos8 image you downloaded.
You can try to find another centos8 image and make sure it can work first.
If still fail, you need check specific log and did some comparative analysis.
You can refer to
https://bugs.launchpad.net/kolla-ansible/+bug/1873951
Thanks!
Zhipeng

From: Akki yadav <yadav.akshay58 at gmail.com>
Sent: 2020年10月15日 15:04
To: Liu, ZhipengS <zhipengs.liu at intel.com>
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] StarlingX R4.0 Baremetal Duplex standard controller storage ironic deployment mode: Baremetal node not creation issue.

Hi ZhipengS,

I used Centos 8 qcow2 which I downloaded from the official website. Link to the image is : https://cloud.centos.org/centos/8/x86_64/images/CentOS-8-GenericCloud-8.2.2004-20200611.2.x86_64.qcow2
With the above centos 8 image, the baremetal node stucks in probing state.

But with Centos7 qcow2, baremetal node came up smoothly.

Any idea what can be the issue and how can I use centos8 without being stuck at probing state ?

Sure I will raise one to track this issue after this mails reply in case we still want it to be created.

Regards
Akshay.

On Thu, Oct 15, 2020 at 6:20 AM Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>> wrote:
Hi Akshay,

Which image are you using to create server?
Does this image work on R3.0?
You can also retry it with other centos image, make sure it is not the image issue first.
Do we have one LP to track this issue?  If not, could you help raise one and upload key logs so that
Some guys to further check the detail info.

Thanks!
Zhipeng

From: Akki yadav <yadav.akshay58 at gmail.com<mailto:yadav.akshay58 at gmail.com>>
Sent: 2020年10月8日 17:25
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] StarlingX R4.0 Baremetal Duplex standard controller storage ironic deployment mode: Baremetal node not creation issue.

Hello Team,

I hope all are well.

Setup: StarlingX R4.0 Baremetal Duplex standard controller storage ironic deployment mode. (I followed the official starlingX documentation for deploying the setup.)

Issue:  At the time of "openstack server create" for launching baremetal node, I came across the following multiple observations:

- Sometimes when I launch baremetal node on openstack, after one time pxe booting, the baremetal node goes down again and then comes up and goes into second time booting and gets stuck there in "Probing" state ( Seen on node's console) BUT according to openstack horizon, it is up and running and according to "openstack baremetal node show", it is in "Active" state.


- And sometimes when i launch  baremetal node on openstack, after one time pxe booting, the baremetal node goes down again and then comes up, the "spawning" state on openstack horizon  goes into ERROR.
Error seen in "nova-compute-ironic-0" container is :
"ERROR nova.compute.manager [instance: edd447c6-12ac-49ba-b0bc-f419aff4892a] nova.exception.InstanceDeployFailure: Failed to provision instance edd447c6-12ac-49ba-b0bc-f419aff4892a: Timeout reached while waiting for callback for node 75210cc4-ad98-442d-ace1-89ce69467580"


- The baremetal node always takes near about 2 hours to be in "available" state from "cleaning" and "clean-wait". Is it correct behaviour ?

Please guide me how to resolve this.


Regards
Akshay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20201016/e6fcf587/attachment.html>