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

Bug 1581385

Summary: Neutron-sriov-agent container missing when using OpenDaylight + SRIOV environment file
Product: Red Hat OpenStack Reporter: Ricardo Noriega <rnoriega>
Component: documentationAssignee: Joanne O'Flynn <joflynn>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aadam, aschultz, dbecker, dcadzow, itbrown, joflynn, mburns, mkolesni, morazi, rnoriega, sbandyop, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-13 17:02:17 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:
Attachments:
Description Flags
THT
none
New THT none

Description Ricardo Noriega 2018-05-22 15:36:35 UTC
Description of problem:

Creating the local registry adding the following environment files:

environments/services-docker/neutron-opendaylight.yaml
environments/services-docker/neutron-opendaylight-sriov.yaml

won't add the neutron-sriov-agent container image to the list.

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

OSP13

How reproducible:

Always

Steps to Reproduce:

In order to create a local registry to deploy OSP13 with OpenDaylight and SRIOV agent:


 openstack overcloud container image prepare   --namespace=docker-registry.engineering.redhat.com/rhosp13   --prefix=openstack-   --tag=2018-05-07.2 --output-images-file /home/stack/local_registry_images.yaml -e /home/stack/templates/environments/services-docker/neutron-opendaylight.yaml -e /home/stack/templates/environments/services-docker/neutron-opendaylight-sriov.yaml

openstack overcloud container image prepare   --namespace=192.168.24.1:8787/rhosp13   --prefix=openstack-   --tag=2018-05-07.2 -e /home/stack/templates/environments/services-docker/neutron-opendaylight.yaml -e /home/stack/templates/environments/services-docker/neutron-opendaylight-sriov.yaml --output-env-file=/home/stack/templates/overcloud_images.yaml


Actual results:

neutron-sriov-agent container is missing in the deployment.


Expected results:

neutron-sriov-agent should be available by using neutron-opendaylight-sriov.yaml 

Additional info:

Comment 1 Mike Kolesnik 2018-05-23 07:13:50 UTC
Itzik, can you please check if you hit this?

Comment 2 Ricardo Noriega 2018-05-23 10:00:30 UTC
Created attachment 1440540 [details]
THT

Comment 3 Ricardo Noriega 2018-05-23 11:13:32 UTC
Created attachment 1440548 [details]
New THT

Comment 4 Ricardo Noriega 2018-05-23 11:14:38 UTC
(undercloud) [stack@undercloud13 ~]$ cat deploy_overcloud.sh 
#!/bin/bash
time openstack overcloud deploy \
    --templates ~/templates/ \
    -t 60 \
    --ntp-server clock.corp.redhat.com \
    -e ~/templates/node-info.yaml \
    -e ~/templates/environments/docker.yaml \
    -e ~/templates/overcloud_images.yaml \
    -e ~/templates/environments/network-isolation.yaml \
    -e ~/templates/environments/network-environment.yaml \
    -e ~/templates/environments/services-docker/neutron-opendaylight.yaml \
    -e ~/templates/environments/services-docker/neutron-opendaylight-sriov.yaml \
    -e ~/templates/environments/services-docker/neutron-l2gw-opendaylight.yaml \
    -r ~/templates/roles_data.yaml \
    --log-file overcloud_install.log

Comment 5 Ricardo Noriega 2018-05-25 08:50:06 UTC
Finally I've figured out what was the issue. It doesn't look like a bug, but a lack of documentation around creating the local registry.

Creating the container repository takes into account, not only the services that the user picks via environment files, but also if those services are present in any of the roles located in roles_data.yaml.

In my environment, I created a single custom role (all-in-one). That role file can be passed as argument when creating the local registry like this:

openstack overcloud container image prepare   --namespace=192.168.24.1:8787/rhosp13   --prefix=openstack-   --tag=2018-05-07.2 -e /home/stack/templates/environments/services-docker/neutron-opendaylight.yaml -e /home/stack/templates/environments/services-docker/neutron-opendaylight-sriov.yaml --output-env-file=/home/stack/templates/overcloud_images.yaml --roles-file /home/stack/templates/roles_data.yaml

If the roles that are defined in this file --roles-file /home/stack/templates/roles_data.yaml, contain the following services:

    - OS::TripleO::Services::NeutronSriovAgent
    - OS::TripleO::Services::NeutronSriovHostConfig

The container neutron-sriov-agent will be pulled into the local registry, and deployed.

This argument should be explained in the official documentation.

Comment 6 Itzik Brown 2018-05-29 10:03:31 UTC
Removing the Needinfo. Doc issue.