Deployment failed with error: Primitive 'neutron-l3' with name 'neutron-l3-agent' was not found in CIB

[Timur Nurlygayanov]

Steps To Reproduce:
1. Take MOS 9.0 ISO #.
2. Deploy virtual environment with 3 slave nodes
3. Install plugins with the following detached services: RabbitMQ, Keystone, DataBase.
(how to install: - download rpm packages here http://jenkins-product.srt.mirantis.net:8080/view/plugins/job/build-fuel-plugins/ and install them with yum on fuel master node, then enable plugins in Fuel UI)
4. Configure the following configuration: on node with controller role, one node with separate Keystone, DataBase and RabbitMQ, one node with compute+cinder+ceph role. TLS, Neutron VLAN, Murano enabled, Ceph replication factor==1, Ubuntu, MOS packages.
5. Deploy environment

Expected Result:
Deployment passed, OSTF tests passed

Observed Result:
Deployment failed with many different errors (please see attached diagnostic snapshot for more detailed information):

(/Stage[main]/Neutron::Agents::L3/Service[neutron-l3]) Could not evaluate: Primitive 'neutron-l3' with name 'neutron-l3-agent' was not found in CIB!

[root@fuel ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 347
cat /etc/fuel_build_number:
 347
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6345.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8679.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-openstack-metadata-9.0.0-1.mos8679.noarch
 python-fuelclient-9.0.0-1.mos313.noarch
 fuel-9.0.0-1.mos6345.noarch
 fuel-nailgun-9.0.0-1.mos8679.noarch
 rubygem-astute-9.0.0-1.mos742.noarch
 fuel-library9.0-9.0.0-1.mos8338.noarch
 shotgun-9.0.0-1.mos88.noarch
 fuel-agent-9.0.0-1.mos276.noarch
 fuel-ui-9.0.0-1.mos2679.noarch
 fuel-setup-9.0.0-1.mos6345.noarch
 nailgun-mcagents-9.0.0-1.mos742.noarch
 fuel-misc-9.0.0-1.mos8338.noarch
 python-packetary-9.0.0-1.mos135.noarch
 fuel-bootstrap-cli-9.0.0-1.mos276.noarch
 fuel-migrate-9.0.0-1.mos8338.noarch
 fuel-mirror-9.0.0-1.mos135.noarch
 fuel-notify-9.0.0-1.mos8338.noarch
 fuel-ostf-9.0.0-1.mos933.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-utils-9.0.0-1.mos8338.noarch

[Timur Nurlygayanov (tnurlygayanov)]

Diagnostic snapshot ^^^

[Matthew Mosesohn (raytrac3r)]

I could not reproduce this. Moving back to sustaining team and marking incomplete

[Dmitry Pyzhov (dpyzhov)]

Timur agreed to invalidate the bug because it appeared only once and we cannot reproduce it.

[Jim Golden (jim-golden)]

I just ran into this bug in fuel 9 on single controller deployment after adding a controller and adding Neutron L3 HA to an existing deployment at the same time. I have the snapshot, but can't upload it due to production network configuration. I can upload individual logs if needed.

[Timur Nurlygayanov (tnurlygayanov)]

So status changed to Confirmed for MOS 9.1 since it reproduced on another environment with MOS 9.0.

We need to try to reproduce the issue on QA environment based on the steps which were described by Jim.

[Dmitry Pyzhov (dpyzhov)]

@Timur, could you help with reproduction?

[Timur Nurlygayanov (tnurlygayanov)]

Yes, sure. I'm going to reproduce the issue.

[Timur Nurlygayanov (tnurlygayanov)]

I can't reproduce the issue by the described steps on MOS 9.1.
Closed as Invalid.