Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1651250

Summary: [OSP14] add openstack-minimal image to OSP
Product: Red Hat OpenStack Reporter: Jon Schlueter <jschluet>
Component: rhosp-director-imagesAssignee: Thierry Vignaud <tvignaud>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: arkady_kanevsky, aschultz, bfournie, cdevine, christopher_dearborn, dbecker, dcain, gfidente, jjoyce, johfulto, john_terpstra, John_walsh, jschluet, jslagle, kurt_hey, mburns, morazi, ohochman, pgrist, rajini.karthik, randy_perryman, rhel-osp-director-maint, rheslop, shdunne, slinaber, tvignaud, yrabl
Target Milestone: z1Keywords: FutureFeature, Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhosp-director-images-14.0-20190221.1.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1476282 Environment:
Last Closed: 2019-04-30 17:52:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1476282, 1677777    
Bug Blocks: 1458798, 1476900, 1654309, 1667013    

Description Jon Schlueter 2018-11-19 14:27:01 UTC
+++ This bug was initially created as a clone of Bug #1476282 +++

Description of problem:
Currently overcloud images in OpenStack solution (outside HCI) do not require OpenStack bits.
However, in order to create new overcloud images OSPd required OpenStack subscription.

The side effect of that is that Customers must buy OpenStack subscription for overcloud images when there is no OpenStack running on them.

The ask is for overcloud images and OSPd deploying them in overcloud handles it correctly.

Version-Release number of selected component (if applicable):
All

How reproducible:
Always

Comment 11 Yogev Rabl 2019-02-26 19:35:49 UTC
The deployment failed during the network configuration with the error:

                "Traceback (most recent call last):", 
                "  File \"/bin/os-net-config\", line 10, in <module>", 
                "    sys.exit(main())", 
                "  File \"/usr/lib/python2.7/site-packages/os_net_config/cli.py\", line 259, in main", 
                "    obj = objects.object_from_json(iface_json)", 
                "  File \"/usr/lib/python2.7/site-packages/os_net_config/objects.py\", line 47, in object_from_json", 
                "    return OvsBridge.from_json(json)", 
                "  File \"/usr/lib/python2.7/site-packages/os_net_config/objects.py\", line 597, in from_json", 
                "    fail_mode=fail_mode)", 
                "  File \"/usr/lib/python2.7/site-packages/os_net_config/objects.py\", line 522, in __init__", 
                "    check_ovs_installed(self.__class__.__name__)", 
                "  File \"/usr/lib/python2.7/site-packages/os_net_config/objects.py\", line 218, in check_ovs_installed", 
                "    raise InvalidConfigException(msg)", 
                "os_net_config.objects.InvalidConfigException: OvsBridge cannot be created as OpenvSwitch is not installed.", 

on all of the overcloud nodes

Comment 13 Bob Fournier 2019-02-28 14:33:58 UTC
In this minimal image openvswitch is not included so nic config files can't use ovs_bridges, ovs_bonds etc.  It looks like an ovs_bridge is being used, that should be changed to a linux_bridge.  

Note the patch that now checks for OVS being included - https://review.openstack.org/#/c/579683/.

Comment 14 Bob Fournier 2019-03-01 13:32:31 UTC
After updating the templates to use a linux_bridge instead of a ovs_bridge the issue in Comment 11 doesn't occur and networking appears to be set up correctly. The deployment didn't succeed however, it looks like a nova config issue.

nova/nova-placement-api.log:2019-02-28 13:06:44.740 30428 DEBUG nova.api.openstack.placement.wsgi_wrapper [req-6c2e6de5-7aa0-4c04-9270-d8d09cfbfc5c 761983ec6c1e4f6192e5141fc78fb30b 2c4a6cca55be4b159f93c0b8237e345b - default default] Placement API returning an error response: Unable to allocate inventory: Unable to create allocation for 'CUSTOM_CEPH' on resource provider '3478277d-2039-4114-b03c-53568bfc3fd1'. The requested amount would exceed the capacity. call_func /usr/lib/python2.7/site-packages/nova/api/openstack/placement/wsgi_wrapper.py:31
nova/nova-placement-api.log:2019-02-28 13:06:44.851 30433 DEBUG 
nova.api.openstack.placement.wsgi_wrapper [req-86df4dc2-2106-4586-8695-be3b9ee69f98 761983ec6c1e4f6192e5141fc78fb30b 2c4a6cca55be4b159f93c0b8237e345b - default default] Placement API returning an error response: Unable to allocate inventory: Unable to create allocation for 'CUSTOM_CONTROLLER' on resource provider '3170ddab-ed39-46a2-b5ba-5a0a3829a801'. The requested amount would exceed the capacity. call_func /usr/lib/python2.7/site-packages/nova/api/openstack/placement/wsgi_wrapper.py:31
nova/nova-placement-api.log:2019-02-28 13:06:44.889 30424 DEBUG nova.api.openstack.placement.wsgi_wrapper [req-785fb737-8e0f-49d7-ad5a-7f6844dd9f40 761983ec6c1e4f6192e5141fc78fb30b 2c4a6cca55be4b159f93c0b8237e345b - default default] Placement API returning an error response: Unable to allocate inventory: Unable to create allocation for 'CUSTOM_CONTROLLER' on resource provider '3170ddab-ed39-46a2-b5ba-5a0a3829a801'. The requested amount would exceed the capacity. call_func /usr/lib/python2.7/site-packages/nova/api/openstack/placement/wsgi_wrapper.py:31
nova/nova-placement-api.log:2019-02-28 13:06:45.459 30432 DEBUG nova.api.openstack.placement.wsgi_wrapper [req-70a97989-64ea-4a96-aa44-b259f4cebe7f 761983ec6c1e4f6192e5141fc78fb30b 2c4a6cca55be4b159f93c0b8237e345b - default default] Placement API returning an error response: Unable to allocate inventory: Unable to create allocation for 'CUSTOM_CONTROLLER' on resource provider 'dddb3457-ccdd-4a11-86b9-1c429682c2d0'. The requested amount would exceed the capacity. call_func /usr/lib/python2.7/site-packages/nova/api/openstack/placement/wsgi_wrapper.py:31
nova/nova-placeme

Comment 22 Yogev Rabl 2019-03-12 12:59:13 UTC
Verified, please note that in order to use minimal image one needs to use linux_bridge instead of ovs_bridge.

worked on rhosp-director-images-14.0-20190304.2.el7ost.noarch

Comment 25 errata-xmlrpc 2019-04-30 17:52:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0953

Comment 26 Red Hat Bugzilla 2023-09-14 04:42:30 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days