[tripleo] Re: Need help deploying Openstack

John Fulton johfulto at redhat.com
Wed Aug 18 15:39:21 UTC 2021


On Wed, Aug 18, 2021 at 11:29 AM wodel youchi <wodel.youchi at gmail.com>
wrote:

> Thanks John,
>
> My idea is to learn how to deploy openstack with tripleO like what will be
> with physical nodes, my goal is not to get openstack up and running to lean
> how to use it, my goal is to install it in the same way as if it was a
> physical implementation.
>

I use tripleo lab for the same reasons while I'm working on TripleO.
Tripleo-lab creates the virtual hardware, adds it to Ironic and then
installs the undercloud. But that's where I stop using it and then deploy
the overcloud myself. In this way I can pretend I'm using physical nodes. I
just don't have to deal with the environmental issues from setting up the
simulation with VMs myself (e.g. the second issue below /dev/vda does not
have a valid MBR).

My notes on using tripleo-lab to run the commands like the ones below
(though I didn't have the errors you had) are here if it's useful to you:

  https://github.com/fultonj/xena/tree/main/networkv2

  John


> About Wallaby, I have tried, but I got other errors :
>
> I followed these documents :
>
> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/network_isolation.html
>
> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/custom_networks.html#custom-networks
>
> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/provisioning/baremetal_provision.html#network-config-properties
>
> At the end I tried these two commands :
> 1) openstack overcloud node provision  --stack overcloud  --network-config
> --output ~/overcloud-baremetal-deployed.yaml  ~/templates/
> *baremetal-node-net.yaml*
>
> And I this error message :
>
>> 2021-08-15 15:59:32.402435 | 52540075-9baf-2b0b-5fc8-000000000017 |
>> FATAL | Provision instances | localhost | error={"changed": false,
>> "logging": "Deploy attempt failed on node computeHCI2
>> (UUID 9440e769-9634-4015-82b0-97b8c1921ef5),
>> cleaning up\nTraceback (most recent call last):\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_provisioner.py\", line 392,
>> in provision_node\n    nics.validate()\n
>> File \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 60,
>> in validate\n
>> result.append(('network', self._get_network(nic)))\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 128, in
>> _get_network\n
>> 'Unexpected fields for a network: %s' % ',
>> '.join(unexpected))\nmetalsmith.exceptions.InvalidNIC:
>> Unexpected fields for a network: subnet\nDeploy attempt failed on node
>> computeHCI0 (UUID 31eecc38-7d80-4ddd-9cc4-a76edf00ec3a),
>> cleaning up\nTraceback (most recent call last):\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_provisioner.py\", line 392,
>> in provision_node\n
>>  nics.validate()\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 60, in
>> validate\n
>>  result.append(('network', self._get_network(nic)))\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 128, in
>> _get_network\n
>>  'Unexpected fields for a network: %s' % ',
>> '.join(unexpected))\nmetalsmith.exceptions.InvalidNIC:
>>  Unexpected fields for a network: subnet\nDeploy attempt failed on node
>> controller2 (UUID f62f8cb5-40e4-4e40-805d-852c2a2f7e00),
>>  cleaning up\nTraceback (most recent call last):\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_provisioner.py\", line 392,
>>  in provision_node\n    nics.validate()\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 60, in
>> validate\n
>>  result.append(('network', self._get_network(nic)))\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 128, in
>> _get_network\n
>>  'Unexpected fields for a network: %s' % ',
>> '.join(unexpected))\nmetalsmith.exceptions.InvalidNIC:
>>  Unexpected fields for a network: subnet\nDeploy attempt failed on node
>> computeHCI1 (UUID 2798b208-4842-4083-9b3f-c46953b52928),
>>  cleaning up\nTraceback (most recent call last):\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_provisioner.py\", line 392,
>>  in provision_node\n    nics.validate()\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 60, in
>> validate\n
>>  result.append(('network', self._get_network(nic)))\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 128, in
>> _get_network\n
>>  'Unexpected fields for a network: %s' % ',
>> '.join(unexpected))\nmetalsmith.exceptions.InvalidNIC: Unexpected fields
>> for a network: subnet\n
>>  Deploy attempt failed on node controller1 (UUID
>> df87e5c7-32b0-4bfa-9ef9-f0a98666e7de), cleaning up\nTraceback (most recent
>> call last):\n
>>  File \"/usr/lib/python3.6/site-packages/metalsmith/_provisioner.py\",
>> line 392, in provision_node\n
>>  nics.validate()\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 60, in
>> validate\n
>>  result.append(('network', self._get_network(nic)))\n  File
>> \"/usr/lib/python3.6/site-packages/metalsmith/_nics.py\", line 128, in
>> _get_network\n
>>  'Unexpected fields for a network: %s' % ',
>> '.join(unexpected))\nmetalsmith.exceptions.InvalidNIC: Unexpected fields
>> for a network: subnet\nDeploy attempt failed on node controller0 (UUID
>> af75122c-a6e8-42d7-afd2-571738c42061), cleaning up\nTraceback (most recent
>> call last):\n  File \"/usr/lib/python3.6/site-packages/metalsmith/_*provisioner.py\",
>> line 392, in provision_node\n    nics.validate()\n  File
>> \"/usr/lib/python3.6/site-**packages/metalsmith/_nics.py\"**, line 60,
>> in validate\n    result.append(('network', self._get_network(nic)))\n  File
>> \"/usr/lib/python3.6/site-**packages/metalsmith/_nics.py\"**, line 128,
>> in _get_network\n    'Unexpected fields for a network: %s' % ',
>> '.join(unexpected))\**nmetalsmith.exceptions.**InvalidNIC: Unexpected
>> fields for a network: subnet\n", "msg": "Unexpected fields for a network:
>> subnet"}*
>>
>
>
>
> 2) openstack overcloud node provision  --stack overcloud --output ~/
> overcloud-baremetal-deployed.yaml  ~/templates/*baremetal-node**.yaml*
>
> This time I got this error :
>
>> 2021-08-16 13:47:02.156021 | 52540075-9baf-0672-d7b8-000000000017 |
>>  FATAL | Provision instances | localhost | error={"changed": false,
>> "logging": "Created port overcloud-computehci-1-ctlplane (UUID
>> 17e55729-b44b-40a8-9361-9e36e8527de5) for node controller0 (UUID
>> 61bc6512-9c4e-4199-936a-754801f7cffa) with {'network_id':
>> '1c8c5e86-79ac-4ec6-9616-3c965cab6e88', 'name':
>> 'overcloud-computehci-1-ctlplane'}\nCreated port
>> overcloud-controller-0-ctlplane (UUID 0a09bbb5-934d-4d34-ab5b-7c14518d06c6)
>> for node controller1 (UUID 03915e7c-a314-41d9-be8c-46291879692a) with
>> {'network_id': '1c8c5e86-79ac-4ec6-9616-3c965cab6e88', 'name':
>> 'overcloud-controller-0-ctlplane'}\nCreated port
>> overcloud-computehci-2-ctlplane (UUID 76ef56f1-4dbb-453e-a344-968b0da95823)
>> for node computeHCI2 (UUID a5d3552b-ab79-404e-8a52-48dc53a3aa45) with
>> {'network_id': '1c8c5e86-79ac-4ec6-9616-3c965cab6e88', 'name':
>> 'overcloud-computehci-2-ctlplane'}\nCreated port
>> overcloud-computehci-0-ctlplane (UUID 79967f38-90ee-49e6-8716-b09cc9460afe)
>> for node computeHCI1 (UUID 3534309b-c11f-48d4-b23d-3ed9f2dcbf79) with
>> {'network_id': '1c8c5e86-79ac-4ec6-9616-3c965cab6e88', 'name':
>> 'overcloud-computehci-0-ctlplane'}\nCreated port
>> overcloud-controller-1-ctlplane (UUID c70b7c8c-31a6-460e-aa77-ea37b8e332f6)
>> for node controller2 (UUID 83f47771-9f82-4437-8df4-de32bcd6fc63) with
>> {'network_id': '1c8c5e86-79ac-4ec6-9616-3c965cab6e88', 'name':
>> 'overcloud-controller-1-ctlplane'}\nCreated port
>> overcloud-controller-2-ctlplane (UUID 2b74c4e3-705c-4bf1-85de-a5e0a9cdb591)
>> for node computeHCI0 (UUID 3924529b-44a7-4c74-b1e1-2175d6313a3e) with
>> {'network_id': '1c8c5e86-79ac-4ec6-9616-3c965cab6e88', 'name':
>> 'overcloud-controller-2-ctlplane'}\nAttached port
>> overcloud-controller-0-ctlplane (UUID 0a09bbb5-934d-4d34-ab5b-7c14518d06c6)
>> to node controller1 (UUID 03915e7c-a314-41d9-be8c-46291879692a)\nAttached
>> port overcloud-computehci-1-ctlplane (UUID
>> 17e55729-b44b-40a8-9361-9e36e8527de5) to node controller0 (UUID
>> 61bc6512-9c4e-4199-936a-754801f7cffa)\nProvisioning started on node
>> controller1 (UUID 03915e7c-a314-41d9-be8c-46291879692a)\nAttached port
>> overcloud-computehci-2-ctlplane (UUID 76ef56f1-4dbb-453e-a344-968b0da95823)
>> to node computeHCI2 (UUID a5d3552b-ab79-404e-8a52-48dc53a3aa45)\nAttached
>> port overcloud-computehci-0-ctlplane (UUID
>> 79967f38-90ee-49e6-8716-b09cc9460afe) to node computeHCI1 (UUID
>> 3534309b-c11f-48d4-b23d-3ed9f2dcbf79)\nProvisioning started on node
>> controller0 (UUID 61bc6512-9c4e-4199-936a-754801f7cffa)\nAttached port
>> overcloud-controller-1-ctlplane (UUID c70b7c8c-31a6-460e-aa77-ea37b8e332f6)
>> to node controller2 (UUID
>> 83f47771-9f82-4437-8df4-de32bcd6fc63)\nProvisioning started on node
>> computeHCI2 (UUID a5d3552b-ab79-404e-8a52-48dc53a3aa45)\nProvisioning
>> started on node computeHCI1 (UUID
>> 3534309b-c11f-48d4-b23d-3ed9f2dcbf79)\nAttached port
>> overcloud-controller-2-ctlplane (UUID 2b74c4e3-705c-4bf1-85de-a5e0a9cdb591)
>> to node computeHCI0 (UUID
>> 3924529b-44a7-4c74-b1e1-2175d6313a3e)\nProvisioning started on node
>> controller2 (UUID 83f47771-9f82-4437-8df4-de32bcd6fc63)\nProvisioning
>> started on node computeHCI0 (UUID 3924529b-44a7-4c74-b1e1-2175d6313a3e)\n",
>> "msg": "Node *a5d3552b-ab79-404e-8a52-**48dc53a3aa45 reached failure
>> state \"deploy failed\"; the last error is Agent returned error for deploy
>> step {'step': 'write_image', 'priority': 80, 'argsinfo': None, 'interface':
>> 'deploy'} on node a5d3552b-ab79-404e-8a52-**48dc53a3aa45 : Error
>> performing deploy_step write_image: Command execution failed: Failed to
>> check the number of primary partitions present on /dev/vda for node
>> a5d3552b-ab79-404e-8a52-**48dc53a3aa45. Error: The device /dev/vda does
>> not have a valid MBR partition table."}*
>>
>
> Any ideas? thanks in advance.
>
> Regards.
>
> Le mer. 18 août 2021 à 16:01, John Fulton <johfulto at redhat.com> a écrit :
>
>> Hi Wodel,
>>
>> Yes, it's possible to deploy openstack with tripleo using VMs and
>> nested-KVM for the compute node. I personally use this tool on my
>> hypervisor to do it.
>>
>>   https://github.com/cjeanner/tripleo-lab
>>
>> By trying to get tripleo working with nested KVM without using a tool
>> like the above you might eventually create your own version of the same
>> tool though using the above helps you skip those steps.
>>
>> The issue you're hitting from the error message below looks like the Nova
>> scheduler on the undercloud not finding an Ironic node that satisfies the
>> scheduling criteria. This can be debugged but you might find it easier to
>> just not have the problem by letting another tool deal with this for you.
>> Also, with wallaby and newer tripleo does not use Nova on the undercloud
>> and instead the recommended deployment process is to use metalsmith as
>> described here:
>>
>>
>> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/provisioning/baremetal_provision.html
>>
>> You also have the standalone option of using tripleo on a single VM:
>>
>>
>> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/standalone.html
>>
>>   John
>>
>> On Wed, Aug 18, 2021 at 10:28 AM wodel youchi <wodel.youchi at gmail.com>
>> wrote:
>>
>>> Hi,
>>> I am trying to deploy openstack with tripleO using VMs and nested-KVM
>>> for the compute node. This is for test and learning purposes.
>>>
>>> I am using the Train version and following some tutorials.
>>> I prepared my different template files and started the deployment, but I
>>> got these errors :
>>>
>>> *Failed to provision instance fc40457e-4b3c-4402-ae9d-c528f2c2ad30:
>>> Asynchronous exception: Node failed to deploy. Exception: Agent API for
>>> node 6d3724fc-6f13-4588-bbe5-56bc4f9a4f87 returned HTTP status code 404
>>> with error: Not found: Extension with id iscsi not found. for node*
>>>
>>> and
>>>
>>> *Got HTTP 409: {"errors": [{"status": 409, "title": "Conflict",
>>> "detail": "There was a conflict when trying to complete your request.\n\n
>>> Unable to allocate inventory: Unable to create allocation for
>>> 'CUSTOM_BAREMETAL' on resource provider
>>> '6d3724fc-6f13-4588-bbe5-56bc4f9a4f87'. The requested amount would exceed
>>> the capacity. ",*
>>>
>>> Could you help understand what those errors mean? I couldn't find
>>> anything similar on the net.
>>>
>>> Thanks in advance.
>>>
>>> Regards.
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210818/7994ce7c/attachment-0001.html>


More information about the openstack-discuss mailing list