Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1512526 - [RFE]: Validate that "noop" networks are on the same interface with ControlPlane
Summary: [RFE]: Validate that "noop" networks are on the same interface with ControlPlane
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-validations
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Florian Fuchs
QA Contact: nlevinki
URL:
Whiteboard: NeedsAllocation
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-13 12:29 UTC by Udi
Modified: 2019-04-08 05:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Udi 2017-11-13 12:29:07 UTC
Description of problem:
In network-environment.yaml, I mapped some of the ports to noop and the networks to None. For example:

  OS::TripleO::Network::StorageMgmt:
    OS::Heat::None
  OS::TripleO::Network::Storage:
    OS::Heat::None

  OS::TripleO::Controller::Ports::StoragePort:
    ../network/ports/noop.yaml
  OS::TripleO::Controller::Ports::StorageMgmtPort:
    ../network/ports/noop.yaml

However, I did not make the necessary changes to the noc-configs and these networks would not be configured on the correct nic. If a network is mapped to None and the ports to noop - we need to validate that they are defined in the nic-configs on the ctlplane.


Version-Release number of selected component (if applicable):
openstack-tripleo-validations-7.4.1-2.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Map networks and ports to the ctlplane, but don't update the nic-configs accordingly.
2. Run the network-environment validator.


Actual results:
No error.


Expected results:
There should be an error message about the mismatch between network-environment and the nic-configs.


Note You need to log in before you can comment on or make changes to this bug.