Fix linter errors

Author: ashu-011

scenarios/uni05epsilon.yaml

@@ -154,4 +154,4 @@ stacks:
           stack: cell2
       - name: Multi-stack post all stacks deploy manage /etc/hosts
         type: playbook
-        source: adoption_multicell_post_stack_all.yml
+        source: adoption_multicell_post_stack_all.yml

scenarios/uni05epsilon/config_download_cell1.yaml

@@ -45,14 +45,14 @@ parameter_defaults:
   SshFirewallAllowAll: true
 
   # Specify that this is an additional cell
-  NovaAdditionalCell: True
+  NovaAdditionalCell: true
   # Disable network creation in order to use the `network_data.yaml` file from the overcloud stack,
   # and create ports for the nodes in the separate stacks on the existing networks.
   # NOTE(bogdando): might need to enable it, to deploy cells-specific subdomains from different network_data_cellX.yaml files.
   # Also, test RHOSO adoption for a metadata agent deployed per each cell, to see if it handles each one properly,
   # when transitioning all to a superconductor layoyt from a flat OSP17.1 layout
   ManageNetworks: false
-  NovaLocalMetadataPerCell: True
+  NovaLocalMetadataPerCell: true
 
   RedisVirtualFixedIPs:
     - ip_address: 192.168.122.111
@@ -118,4 +118,4 @@ parameter_defaults:
         gateway_ip: 192.168.122.1
         host_routes: []
         name: ctlplane-subnet
-        ip_version: 4
+        ip_version: 4

scenarios/uni05epsilon/config_download_cell2.yaml

@@ -45,14 +45,14 @@ parameter_defaults:
   SshFirewallAllowAll: true
 
   # Specify that this is an additional cell
-  NovaAdditionalCell: True
+  NovaAdditionalCell: true
   # Disable network creation in order to use the `network_data.yaml` file from the overcloud stack,
   # and create ports for the nodes in the separate stacks on the existing networks.
   # NOTE(bogdando): might need to enable it, to deploy cells-specific subdomains from different network_data_cellX.yaml files.
   # Also, test RHOSO adoption for a metadata agent deployed per each cell, to see if it handles each one properly,
   # when transitioning all to a superconductor layoyt from a flat OSP17.1 layout
   ManageNetworks: false
-  NovaLocalMetadataPerCell: True
+  NovaLocalMetadataPerCell: true
 
   RedisVirtualFixedIPs:
     - ip_address: 192.168.122.112
@@ -118,4 +118,4 @@ parameter_defaults:
         gateway_ip: 192.168.122.1
         host_routes: []
         name: ctlplane-subnet
-        ip_version: 4
+        ip_version: 4

scenarios/uni05epsilon/config_download_overcloud.yaml

@@ -100,4 +100,4 @@ parameter_defaults:
         gateway_ip: 192.168.122.1
         host_routes: []
         name: ctlplane-subnet
-        ip_version: 4
+        ip_version: 4

scenarios/uni05epsilon/network_data.yaml.j2

@@ -61,4 +61,4 @@
       vlan: 44
       gateway_ip: '172.21.0.2'
       ip_subnet: '172.21.0.0/24'
-      allocation_pools: [{'start': '172.21.0.160', 'end': '172.21.0.250'}]
+      allocation_pools: [{'start': '172.21.0.160', 'end': '172.21.0.250'}]

scenarios/uni05epsilon/roles.yaml

@@ -372,4 +372,4 @@
     - OS::TripleO::Services::TripleoFirewall
     - OS::TripleO::Services::TripleoPackages
     - OS::TripleO::Services::Tuned
-    - OS::TripleO::Services::Ptp
+    - OS::TripleO::Services::Ptp

scenarios/uni05epsilon/vips_data_cell1.yaml

@@ -18,4 +18,4 @@
 - name: external_vip
   network: external
   subnet: external_subnet
-  dns_name: overcloud
+  dns_name: overcloud

scenarios/uni05epsilon/vips_data_cell2.yaml

@@ -18,4 +18,4 @@
 - name: external_vip
   network: external
   subnet: external_subnet
-  dns_name: overcloud
+  dns_name: overcloud

scenarios/uni05epsilon/vips_data_overcloud.yaml

@@ -19,4 +19,4 @@
 - name: external_vip
   network: external
   subnet: external_subnet
-  dns_name: overcloud
+  dns_name: overcloud