Hi Julia, Thanks for your response. I have used "iscsi" as deploy_interface and installed sgdisk (gdisk) on both ironic_conductors and then tried to spawn a BM node. Then it failed stating about "parted is missing". Then I installed "parted" on both ironic_conductors and then tried again. This time it failed stating: 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Command: parted -a optimal -s /dev/disk/by-path/ip-10.10.20.62:3260-iscsi-iqn.2008-10.org.openstack:b40ef46f-e754-401f-b414-2c8ce05cdfec-lun-1 -- unit MiB mklabel msdos mkpart primary 1 481281 set 1 boot on 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Exit code: 1 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Stdout: '' 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Stderr: 'Error: The location 481281 is outside of the device /dev/sdc.\n' About my BM node: It has 2 physical disks only. Do you have any idea about this ? Thanks Akshay -----Original Message----- From: Julia Kreger <juliaashleykreger@gmail.com> Sent: Wednesday, December 2, 2020 4:26 AM To: Akshay 346 <Akshay.346@hsc.com> Cc: openstack-discuss@lists.openstack.org Subject: Re: IRONIC BAREMETAL partitioned image not spawning. ** External Email- Treat hyperlink and attachment with caution. ** Greetings, If your deploy_interface is set to "iscsi", then sgdisk needs to be installed and available to the ironic-conductor process and user. If your deploy_interface is set to "direct", then sgdisk needs to be present with-in the ironic-python-agent ramdisk. The error you pasted into your email suggests, and the logs confirm that you're using the iscsi deployment interface. You will need to ensure your conductor process can execute sgdisk and it is available with-in the environment PATH that the ironic-conductor process is executing with-in. This is not with-in the qcow you're deploying as the commands are executed remotely before the image is written in this case. -Julia On Tue, Dec 1, 2020 at 10:19 AM Akshay 346 <Akshay.346@hsc.com> wrote:

Hello Team,

I hope you all are keeping safe and doing good.

I have a OpenStack setup up and running with ironic enabled.

I am able to spawn a bare metal node with centos8.2 whole-disk image but when I spawn bare metal with partitioned image, it fails to spawn it stating the following trace ( Full trace back attached in the email):

“2020-12-01 12:35:34.603 1 ERROR ironic.conductor.utils [req-0d3a375e-90a3-485d-a7c3-895c97c88006 - - - - -] Deploy failed for instance 463bd844-7f80-4c57-98dd-6ca8cfdb6121. Error: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk': FileNotFoundError: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk'”.

I have also installed sgdisk (yum install gdisk) on the qcow2 from which I build the partitioned image.

Can anyone please guide how to debug it?

Regards

Akshay

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

You may want to consult the bindep file for binary dependencies[0] since it sounds like you installed Ironic manually. That or the dependencies you encountered are just not expressed for some odd reason. Anyhow, Unfortunately what is happening is the iscsi device is being offered by the agent to the conductor, the system partition utilities is somehow addressing beyond the size of the volume on the system which is a little surprising. This could also mean that the disk in the system is defective or faulty. What you're ultimately going to need is the logging data from the agent. If you look in /var/log/ironic/deploy_logs (this is the standard location, you may have defined elsewhere in ironic.conf), you should be able to identify the compress tar archive of what the agent uploaded, in that should be a journal/log file which should provide all of the details needed from the agent logs. That log will indicate what disk was chosen and offered to the conductor and so on and so forth. Ultimately if you're already using a root device hint[1], you may have the wrong hint and it should be noted that the hints can override automatic device selection and the exclusion of invalid devices. You likely ought to re-evaluate one if one is present, or add one pointing to the required disk on the remote system, or possibly remove any existing hint. Depending on your boot mode and disk image it may work out just fine. Hope that helps! -Julia [0]: https://opendev.org/openstack/ironic/src/branch/master/bindep.txt [1] https://docs.openstack.org/ironic/pike/install/include/root-device-hints.htm... On Wed, Dec 2, 2020 at 5:22 AM Akshay 346 <Akshay.346@hsc.com> wrote:

Hi Julia,

Thanks for your response.

I have used "iscsi" as deploy_interface and installed sgdisk (gdisk) on both ironic_conductors and then tried to spawn a BM node. Then it failed stating about "parted is missing". Then I installed "parted" on both ironic_conductors and then tried again.

This time it failed stating:

2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Command: parted -a optimal -s /dev/disk/by-path/ip-10.10.20.62:3260-iscsi-iqn.2008-10.org.openstack:b40ef46f-e754-401f-b414-2c8ce05cdfec-lun-1 -- unit MiB mklabel msdos mkpart primary 1 481281 set 1 boot on 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Exit code: 1 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Stdout: '' 2020-12-02 17:08:39.508 1 ERROR ironic.drivers.modules.agent_base Stderr: 'Error: The location 481281 is outside of the device /dev/sdc.\n'

About my BM node: It has 2 physical disks only.

Do you have any idea about this ?

Thanks Akshay

-----Original Message----- From: Julia Kreger <juliaashleykreger@gmail.com> Sent: Wednesday, December 2, 2020 4:26 AM To: Akshay 346 <Akshay.346@hsc.com> Cc: openstack-discuss@lists.openstack.org Subject: Re: IRONIC BAREMETAL partitioned image not spawning.

** External Email- Treat hyperlink and attachment with caution. **

Greetings,

If your deploy_interface is set to "iscsi", then sgdisk needs to be installed and available to the ironic-conductor process and user. If your deploy_interface is set to "direct", then sgdisk needs to be present with-in the ironic-python-agent ramdisk.

The error you pasted into your email suggests, and the logs confirm that you're using the iscsi deployment interface. You will need to ensure your conductor process can execute sgdisk and it is available with-in the environment PATH that the ironic-conductor process is executing with-in. This is not with-in the qcow you're deploying as the commands are executed remotely before the image is written in this case.

-Julia

On Tue, Dec 1, 2020 at 10:19 AM Akshay 346 <Akshay.346@hsc.com> wrote:

...

Hello Team,

I hope you all are keeping safe and doing good.

I have a OpenStack setup up and running with ironic enabled.

I am able to spawn a bare metal node with centos8.2 whole-disk image but when I spawn bare metal with partitioned image, it fails to spawn it stating the following trace ( Full trace back attached in the email):

“2020-12-01 12:35:34.603 1 ERROR ironic.conductor.utils [req-0d3a375e-90a3-485d-a7c3-895c97c88006 - - - - -] Deploy failed for instance 463bd844-7f80-4c57-98dd-6ca8cfdb6121. Error: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk': FileNotFoundError: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk'”.

I have also installed sgdisk (yum install gdisk) on the qcow2 from which I build the partitioned image.

Can anyone please guide how to debug it?

Regards

Akshay

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.