May  9 23:10:07 cmp02 systemd-modules-load[426]: Inserted module 'iscsi_tcp'
May  9 23:10:07 cmp02 loadkeys[419]: Loading /etc/console-setup/cached.kmap.gz
May  9 23:10:07 cmp02 systemd[1]: Started LVM2 metadata daemon.
May  9 23:10:07 cmp02 systemd[1]: Starting Create Static Device Nodes in /dev...
May  9 23:10:07 cmp02 systemd[1]: Starting udev Coldplug all Devices...
May  9 23:10:07 cmp02 systemd[1]: Starting Initial cloud-init job (pre-networking)...
May  9 23:10:07 cmp02 systemd[1]: Starting Flush Journal to Persistent Storage...
May  9 23:10:07 cmp02 systemd[1]: Starting Load/Save Random Seed...
May  9 23:10:07 cmp02 systemd[1]: Started Set console keymap.
May  9 23:10:07 cmp02 systemd[1]: Started Load/Save Random Seed.
May  9 23:10:07 cmp02 systemd-modules-load[426]: Inserted module 'ib_iser'
May  9 23:10:07 cmp02 systemd[1]: Started Flush Journal to Persistent Storage.
May  9 23:10:07 cmp02 systemd[1]: Started Load Kernel Modules.
May  9 23:10:07 cmp02 systemd[1]: Mounting Configuration File System...
May  9 23:10:07 cmp02 systemd[1]: Starting Apply Kernel Variables...
May  9 23:10:07 cmp02 systemd[1]: Mounting FUSE Control File System...
May  9 23:10:07 cmp02 systemd[1]: Mounted Configuration File System.
May  9 23:10:07 cmp02 systemd[1]: Mounted FUSE Control File System.
May  9 23:10:07 cmp02 systemd[1]: Started Create Static Device Nodes in /dev.
May  9 23:10:07 cmp02 systemd[1]: Started udev Coldplug all Devices.
May  9 23:10:07 cmp02 systemd[1]: Starting udev Kernel Device Manager...
May  9 23:10:07 cmp02 systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May  9 23:10:07 cmp02 systemd[1]: Started Apply Kernel Variables.
May  9 23:10:07 cmp02 systemd[1]: Started udev Kernel Device Manager.
May  9 23:10:07 cmp02 systemd[1]: Reached target Local File Systems (Pre).
May  9 23:10:07 cmp02 systemd[1]: Reached target Local File Systems.
May  9 23:10:07 cmp02 systemd[1]: Starting Create Volatile Files and Directories...
May  9 23:10:07 cmp02 systemd[1]: Starting LSB: AppArmor initialization...
May  9 23:10:07 cmp02 systemd[1]: Starting Set console font and keymap...
May  9 23:10:07 cmp02 systemd[1]: Starting Commit a transient machine-id on disk...
May  9 23:10:07 cmp02 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
May  9 23:10:07 cmp02 systemd-tmpfiles[504]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
May  9 23:10:07 cmp02 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
May  9 23:10:07 cmp02 systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
May  9 23:10:07 cmp02 systemd[1]: Started Create Volatile Files and Directories.
May  9 23:10:07 cmp02 systemd[1]: Starting Network Time Synchronization...
May  9 23:10:07 cmp02 systemd[1]: Starting Update UTMP about System Boot/Shutdown...
May  9 23:10:07 cmp02 systemd[1]: Started Network Time Synchronization.
May  9 23:10:07 cmp02 systemd[1]: Reached target System Time Synchronized.
May  9 23:10:07 cmp02 systemd[1]: Started Update UTMP about System Boot/Shutdown.
May  9 23:10:07 cmp02 apparmor[507]:  * Starting AppArmor profiles
May  9 23:10:07 cmp02 systemd[1]: Started Commit a transient machine-id on disk.
May  9 23:10:07 cmp02 systemd[1]: Found device /dev/ttyS0.
May  9 23:10:07 cmp02 apparmor[507]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
May  9 23:10:07 cmp02 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
May  9 23:10:07 cmp02 apparmor[507]:    ...done.
May  9 23:10:07 cmp02 systemd[1]: Started LSB: AppArmor initialization.
May  9 23:10:07 cmp02 systemd[1]: Started Set console font and keymap.
May  9 23:10:07 cmp02 systemd[1]: Created slice system-getty.slice.
May  9 23:10:07 cmp02 cloud-init[456]: Cloud-init v. 18.2 running 'init-local' at Wed, 09 May 2018 23:10:02 +0000. Up 5.78 seconds.
May  9 23:10:07 cmp02 systemd[1]: Started Initial cloud-init job (pre-networking).
May  9 23:10:07 cmp02 systemd[1]: Reached target Network (Pre).
May  9 23:10:07 cmp02 systemd[1]: Starting Raise network interfaces...
May  9 23:10:07 cmp02 dhclient[947]: Internet Systems Consortium DHCP Client 4.3.3
May  9 23:10:07 cmp02 ifup[874]: Internet Systems Consortium DHCP Client 4.3.3
May  9 23:10:07 cmp02 ifup[874]: Copyright 2004-2015 Internet Systems Consortium.
May  9 23:10:07 cmp02 rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
May  9 23:10:07 cmp02 ifup[874]: All rights reserved.
May  9 23:10:07 cmp02 ifup[874]: For info, please visit https://www.isc.org/software/dhcp/
May  9 23:10:07 cmp02 dhclient[947]: Copyright 2004-2015 Internet Systems Consortium.
May  9 23:10:07 cmp02 rsyslogd-2007: action 'action 11' suspended, next retry is Wed May  9 23:10:37 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
May  9 23:10:07 cmp02 dhclient[947]: All rights reserved.
May  9 23:10:07 cmp02 dhclient[947]: For info, please visit https://www.isc.org/software/dhcp/
May  9 23:10:07 cmp02 dhclient[947]: 
May  9 23:10:07 cmp02 dhclient[947]: Listening on LPF/ens3/52:54:00:90:6f:f7
May  9 23:10:07 cmp02 ifup[874]: Listening on LPF/ens3/52:54:00:90:6f:f7
May  9 23:10:07 cmp02 ifup[874]: Sending on   LPF/ens3/52:54:00:90:6f:f7
May  9 23:10:07 cmp02 ifup[874]: Sending on   Socket/fallback
May  9 23:10:07 cmp02 ifup[874]: DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x59719608)
May  9 23:10:07 cmp02 dhclient[947]: Sending on   LPF/ens3/52:54:00:90:6f:f7
May  9 23:10:07 cmp02 dhclient[947]: Sending on   Socket/fallback
May  9 23:10:07 cmp02 dhclient[947]: DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x59719608)
May  9 23:10:07 cmp02 dhclient[947]: DHCPREQUEST of 192.168.11.50 on ens3 to 255.255.255.255 port 67 (xid=0x8967159)
May  9 23:10:07 cmp02 ifup[874]: DHCPREQUEST of 192.168.11.50 on ens3 to 255.255.255.255 port 67 (xid=0x8967159)
May  9 23:10:07 cmp02 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1164" x-info="http://www.rsyslog.com"] start
May  9 23:10:07 cmp02 ifup[874]: DHCPOFFER of 192.168.11.50 from 192.168.11.1
May  9 23:10:07 cmp02 ifup[874]: DHCPACK of 192.168.11.50 from 192.168.11.1
May  9 23:10:07 cmp02 dhclient[947]: DHCPOFFER of 192.168.11.50 from 192.168.11.1
May  9 23:10:07 cmp02 dhclient[947]: DHCPACK of 192.168.11.50 from 192.168.11.1
May  9 23:10:07 cmp02 dhclient[947]: bound to 192.168.11.50 -- renewal in 1387 seconds.
May  9 23:10:07 cmp02 ifup[874]: bound to 192.168.11.50 -- renewal in 1387 seconds.
May  9 23:10:07 cmp02 systemd[1]: Started Raise network interfaces.
May  9 23:10:07 cmp02 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
May  9 23:10:07 cmp02 rsyslogd: rsyslogd's groupid changed to 108
May  9 23:10:07 cmp02 rsyslogd: rsyslogd's userid changed to 104
May  9 23:10:07 cmp02 kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x42/0x507 with crng_init=0
May  9 23:10:07 cmp02 kernel: [    0.000000] Linux version 4.13.0-41-generic (buildd@lgw01-amd64-028) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #46~16.04.1-Ubuntu SMP Thu May 3 10:06:43 UTC 2018 (Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16)
May  9 23:10:07 cmp02 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=dfb884db-c6ad-4c7a-8075-98cf640a2892 ro console=tty1 console=ttyS0
May  9 23:10:07 cmp02 kernel: [    0.000000] KERNEL supported cpus:
May  9 23:10:07 cmp02 kernel: [    0.000000]   Intel GenuineIntel
May  9 23:10:07 cmp02 kernel: [    0.000000]   AMD AuthenticAMD
May  9 23:10:07 cmp02 kernel: [    0.000000]   Centaur CentaurHauls
May  9 23:10:07 cmp02 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May  9 23:10:07 cmp02 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May  9 23:10:07 cmp02 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May  9 23:10:07 cmp02 kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May  9 23:10:07 cmp02 kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
May  9 23:10:07 cmp02 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffdefff] usable
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000bffdf000-0x00000000bfffffff] reserved
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
May  9 23:10:07 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000023fffffff] usable
May  9 23:10:07 cmp02 kernel: [    0.000000] NX (Execute Disable) protection: active
May  9 23:10:07 cmp02 kernel: [    0.000000] random: fast init done
May  9 23:10:07 cmp02 kernel: [    0.000000] SMBIOS 2.8 present.
May  9 23:10:07 cmp02 kernel: [    0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
May  9 23:10:07 cmp02 kernel: [    0.000000] Hypervisor detected: KVM
May  9 23:10:07 cmp02 kernel: [    0.000000] tsc: Fast TSC calibration failed
May  9 23:10:07 cmp02 kernel: [    0.000000] tsc: Using PIT calibration value
May  9 23:10:07 cmp02 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
May  9 23:10:07 cmp02 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
May  9 23:10:07 cmp02 kernel: [    0.000000] e820: last_pfn = 0x240000 max_arch_pfn = 0x400000000
May  9 23:10:07 cmp02 kernel: [    0.000000] MTRR default type: write-back
May  9 23:10:07 cmp02 kernel: [    0.000000] MTRR fixed ranges enabled:
May  9 23:10:07 cmp02 kernel: [    0.000000]   00000-9FFFF write-back
May  9 23:10:07 cmp02 kernel: [    0.000000]   A0000-BFFFF uncachable
May  9 23:10:07 cmp02 kernel: [    0.000000]   C0000-FFFFF write-protect
May  9 23:10:07 cmp02 kernel: [    0.000000] MTRR variable ranges enabled:
May  9 23:10:07 cmp02 kernel: [    0.000000]   0 base 00C0000000 mask FFC0000000 uncachable
May  9 23:10:07 cmp02 kernel: [    0.000000]   1 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000]   2 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000]   3 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000]   4 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000]   5 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000]   6 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000]   7 disabled
May  9 23:10:07 cmp02 kernel: [    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
May  9 23:10:07 cmp02 kernel: [    0.000000] e820: last_pfn = 0xbffdf max_arch_pfn = 0x400000000
May  9 23:10:07 cmp02 kernel: [    0.000000] found SMP MP-table at [mem 0x000f65a0-0x000f65af] mapped at [ffff9f71800f65a0]
May  9 23:10:07 cmp02 kernel: [    0.000000] Scanning 1 areas for low memory corruption
May  9 23:10:07 cmp02 kernel: [    0.000000] Base memory trampoline at [ffff9f7180099000] 99000 size 24576
May  9 23:10:07 cmp02 kernel: [    0.000000] Using GB pages for direct mapping
May  9 23:10:07 cmp02 kernel: [    0.000000] BRK [0x10452c000, 0x10452cfff] PGTABLE
May  9 23:10:07 cmp02 kernel: [    0.000000] BRK [0x10452d000, 0x10452dfff] PGTABLE
May  9 23:10:07 cmp02 kernel: [    0.000000] BRK [0x10452e000, 0x10452efff] PGTABLE
May  9 23:10:07 cmp02 kernel: [    0.000000] BRK [0x10452f000, 0x10452ffff] PGTABLE
May  9 23:10:07 cmp02 kernel: [    0.000000] BRK [0x104530000, 0x104530fff] PGTABLE
May  9 23:10:07 cmp02 kernel: [    0.000000] BRK [0x104531000, 0x104531fff] PGTABLE
May  9 23:10:07 cmp02 kernel: [    0.000000] RAMDISK: [mem 0x32298000-0x35143fff]
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: Early table checksum verification disabled
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: RSDP 0x00000000000F6550 000014 (v00 BOCHS )
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: RSDT 0x00000000BFFE14A5 000030 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: FACP 0x00000000BFFE0914 000074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: DSDT 0x00000000BFFDFD40 000BD4 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: FACS 0x00000000BFFDFD00 000040
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: SSDT 0x00000000BFFE0988 000A85 (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: APIC 0x00000000BFFE140D 000098 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
May  9 23:10:07 cmp02 kernel: [    0.000000] No NUMA configuration found
May  9 23:10:07 cmp02 kernel: [    0.000000] Faking a node at [mem 0x0000000000000000-0x000000023fffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] NODE_DATA(0) allocated [mem 0x23ffd5000-0x23fffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
May  9 23:10:07 cmp02 kernel: [    0.000000] kvm-clock: cpu 0, msr 2:3ff55001, primary cpu clock
May  9 23:10:07 cmp02 kernel: [    0.000000] kvm-clock: using sched offset of 1472688678 cycles
May  9 23:10:07 cmp02 kernel: [    0.000000] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
May  9 23:10:07 cmp02 kernel: [    0.000000] Zone ranges:
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000]   Normal   [mem 0x0000000100000000-0x000000023fffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000]   Device   empty
May  9 23:10:07 cmp02 kernel: [    0.000000] Movable zone start for each node
May  9 23:10:07 cmp02 kernel: [    0.000000] Early memory node ranges
May  9 23:10:07 cmp02 kernel: [    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009efff]
May  9 23:10:07 cmp02 kernel: [    0.000000]   node   0: [mem 0x0000000000100000-0x00000000bffdefff]
May  9 23:10:07 cmp02 kernel: [    0.000000]   node   0: [mem 0x0000000100000000-0x000000023fffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000023fffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] On node 0 totalpages: 2097021
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA zone: 21 pages reserved
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA zone: 3998 pages, LIFO batch:0
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA32 zone: 12224 pages used for memmap
May  9 23:10:07 cmp02 kernel: [    0.000000]   DMA32 zone: 782303 pages, LIFO batch:31
May  9 23:10:07 cmp02 kernel: [    0.000000]   Normal zone: 20480 pages used for memmap
May  9 23:10:07 cmp02 kernel: [    0.000000]   Normal zone: 1310720 pages, LIFO batch:31
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x608
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
May  9 23:10:07 cmp02 kernel: [    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: IRQ0 used by override.
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: IRQ5 used by override.
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: IRQ9 used by override.
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: IRQ10 used by override.
May  9 23:10:07 cmp02 kernel: [    0.000000] ACPI: IRQ11 used by override.
May  9 23:10:07 cmp02 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
May  9 23:10:07 cmp02 kernel: [    0.000000] smpboot: Allowing 5 CPUs, 0 hotplug CPUs
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xbffdf000-0xbfffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xc0000000-0xfeffbfff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfeffc000-0xfeffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xfffbffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
May  9 23:10:07 cmp02 kernel: [    0.000000] e820: [mem 0xc0000000-0xfeffbfff] available for PCI devices
May  9 23:10:07 cmp02 kernel: [    0.000000] Booting paravirtualized kernel on KVM
May  9 23:10:07 cmp02 kernel: [    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
May  9 23:10:07 cmp02 kernel: [    0.000000] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:5 nr_cpu_ids:5 nr_node_ids:1
May  9 23:10:07 cmp02 kernel: [    0.000000] percpu: Embedded 45 pages/cpu @ffff9f73b7000000 s146584 r8192 d29544 u1048576
May  9 23:10:07 cmp02 kernel: [    0.000000] pcpu-alloc: s146584 r8192 d29544 u1048576 alloc=1*2097152
May  9 23:10:07 cmp02 kernel: [    0.000000] pcpu-alloc: [0] 0 1 [0] 2 3 [0] 4 - 
May  9 23:10:07 cmp02 kernel: [    0.000000] KVM setup async PF for cpu 0
May  9 23:10:07 cmp02 kernel: [    0.000000] kvm-stealtime: cpu 0, msr 2370161c0
May  9 23:10:07 cmp02 kernel: [    0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
May  9 23:10:07 cmp02 kernel: [    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2064232
May  9 23:10:07 cmp02 kernel: [    0.000000] Policy zone: Normal
May  9 23:10:07 cmp02 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=dfb884db-c6ad-4c7a-8075-98cf640a2892 ro console=tty1 console=ttyS0
May  9 23:10:07 cmp02 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
May  9 23:10:07 cmp02 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
May  9 23:10:07 cmp02 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
May  9 23:10:07 cmp02 kernel: [    0.000000] Memory: 8115668K/8388084K available (12300K kernel code, 2481K rwdata, 4008K rodata, 2368K init, 2372K bss, 272416K reserved, 0K cma-reserved)
May  9 23:10:07 cmp02 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=5, Nodes=1
May  9 23:10:07 cmp02 kernel: [    0.000000] Kernel/User page tables isolation: enabled
May  9 23:10:07 cmp02 kernel: [    0.000000] ftrace: allocating 37858 entries in 148 pages
May  9 23:10:07 cmp02 kernel: [    0.004000] Hierarchical RCU implementation.
May  9 23:10:07 cmp02 kernel: [    0.004000] 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=5.
May  9 23:10:07 cmp02 kernel: [    0.004000] 	Tasks RCU enabled.
May  9 23:10:07 cmp02 kernel: [    0.004000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=5
May  9 23:10:07 cmp02 kernel: [    0.004000] NR_IRQS: 524544, nr_irqs: 464, preallocated irqs: 16
May  9 23:10:07 cmp02 kernel: [    0.004000] Console: colour VGA+ 80x25
May  9 23:10:07 cmp02 kernel: [    0.004000] console [tty1] enabled
May  9 23:10:07 cmp02 kernel: [    0.004000] console [ttyS0] enabled
May  9 23:10:07 cmp02 kernel: [    0.004007] tsc: Detected 2799.994 MHz processor
May  9 23:10:07 cmp02 kernel: [    0.005081] Calibrating delay loop (skipped) preset value.. 5599.98 BogoMIPS (lpj=11199976)
May  9 23:10:07 cmp02 kernel: [    0.005902] pid_max: default: 32768 minimum: 301
May  9 23:10:07 cmp02 kernel: [    0.008013] ACPI: Core revision 20170531
May  9 23:10:07 cmp02 kernel: [    0.009781] ACPI: 2 ACPI AML tables successfully acquired and loaded
May  9 23:10:07 cmp02 kernel: [    0.011187] Security Framework initialized
May  9 23:10:07 cmp02 kernel: [    0.012004] Yama: becoming mindful.
May  9 23:10:07 cmp02 kernel: [    0.012893] AppArmor: AppArmor initialized
May  9 23:10:07 cmp02 kernel: [    0.016825] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
May  9 23:10:07 cmp02 kernel: [    0.019944] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
May  9 23:10:07 cmp02 kernel: [    0.021524] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
May  9 23:10:07 cmp02 kernel: [    0.023001] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
May  9 23:10:07 cmp02 kernel: [    0.024227] FEATURE SPEC_CTRL Not Present
May  9 23:10:07 cmp02 kernel: [    0.025206] mce: CPU supports 10 MCE banks
May  9 23:10:07 cmp02 kernel: [    0.026238] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
May  9 23:10:07 cmp02 kernel: [    0.028004] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
May  9 23:10:07 cmp02 kernel: [    0.029315] Spectre V2 mitigation: Mitigation: Full generic retpoline
May  9 23:10:07 cmp02 kernel: [    0.030706] Spectre V2 mitigation: Speculation control IBPB not-supported IBRS not-supported
May  9 23:10:07 cmp02 kernel: [    0.030870] Freeing SMP alternatives memory: 36K
May  9 23:10:07 cmp02 kernel: [    0.034644] smpboot: Max logical packages: 5
May  9 23:10:07 cmp02 kernel: [    0.036214] x2apic enabled
May  9 23:10:07 cmp02 kernel: [    0.037539] Switched APIC routing to physical x2apic.
May  9 23:10:07 cmp02 kernel: [    0.040604] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
May  9 23:10:07 cmp02 kernel: [    0.041949] TSC deadline timer enabled
May  9 23:10:07 cmp02 kernel: [    0.041953] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (family: 0x6, model: 0x3e, stepping: 0x4)
May  9 23:10:07 cmp02 kernel: [    0.044000] Performance Events: IvyBridge events, Intel PMU driver.
May  9 23:10:07 cmp02 kernel: [    0.044000] ... version:                2
May  9 23:10:07 cmp02 kernel: [    0.044004] ... bit width:              48
May  9 23:10:07 cmp02 kernel: [    0.044981] ... generic registers:      4
May  9 23:10:07 cmp02 kernel: [    0.045948] ... value mask:             0000ffffffffffff
May  9 23:10:07 cmp02 kernel: [    0.047437] ... max period:             000000007fffffff
May  9 23:10:07 cmp02 kernel: [    0.048004] ... fixed-purpose events:   3
May  9 23:10:07 cmp02 kernel: [    0.048978] ... event mask:             000000070000000f
May  9 23:10:07 cmp02 kernel: [    0.050197] Hierarchical SRCU implementation.
May  9 23:10:07 cmp02 kernel: [    0.051880] smp: Bringing up secondary CPUs ...
May  9 23:10:07 cmp02 kernel: [    0.052090] x86: Booting SMP configuration:
May  9 23:10:07 cmp02 kernel: [    0.053076] .... node  #0, CPUs:      #1
May  9 23:10:07 cmp02 kernel: [    0.004000] kvm-clock: cpu 1, msr 2:3ff55041, secondary cpu clock
May  9 23:10:07 cmp02 kernel: [    0.056018] KVM setup async PF for cpu 1
May  9 23:10:07 cmp02 kernel: [    0.056966] kvm-stealtime: cpu 1, msr 2371161c0
May  9 23:10:07 cmp02 kernel: [    0.058031]  #2
May  9 23:10:07 cmp02 kernel: [    0.004000] kvm-clock: cpu 2, msr 2:3ff55081, secondary cpu clock
May  9 23:10:07 cmp02 kernel: [    0.064024] KVM setup async PF for cpu 2
May  9 23:10:07 cmp02 kernel: [    0.065296] kvm-stealtime: cpu 2, msr 2372161c0
May  9 23:10:07 cmp02 kernel: [    0.067059]  #3
May  9 23:10:07 cmp02 kernel: [    0.004000] kvm-clock: cpu 3, msr 2:3ff550c1, secondary cpu clock
May  9 23:10:07 cmp02 kernel: [    0.072027] KVM setup async PF for cpu 3
May  9 23:10:07 cmp02 kernel: [    0.072944] kvm-stealtime: cpu 3, msr 2373161c0
May  9 23:10:07 cmp02 kernel: [    0.074308]  #4
May  9 23:10:07 cmp02 kernel: [    0.004000] kvm-clock: cpu 4, msr 2:3ff55101, secondary cpu clock
May  9 23:10:07 cmp02 kernel: [    0.080023] KVM setup async PF for cpu 4
May  9 23:10:07 cmp02 kernel: [    0.081869] kvm-stealtime: cpu 4, msr 2374161c0
May  9 23:10:07 cmp02 kernel: [    0.083813] smp: Brought up 1 node, 5 CPUs
May  9 23:10:07 cmp02 kernel: [    0.084009] smpboot: Total of 5 processors activated (27999.94 BogoMIPS)
May  9 23:10:07 cmp02 kernel: [    0.088446] devtmpfs: initialized
May  9 23:10:07 cmp02 kernel: [    0.089958] x86/mm: Memory block size: 128MB
May  9 23:10:07 cmp02 kernel: [    0.093392] evm: security.selinux
May  9 23:10:07 cmp02 kernel: [    0.094289] evm: security.SMACK64
May  9 23:10:07 cmp02 kernel: [    0.095796] evm: security.SMACK64EXEC
May  9 23:10:07 cmp02 kernel: [    0.096007] evm: security.SMACK64TRANSMUTE
May  9 23:10:07 cmp02 kernel: [    0.100005] evm: security.SMACK64MMAP
May  9 23:10:07 cmp02 kernel: [    0.100927] evm: security.ima
May  9 23:10:07 cmp02 kernel: [    0.101710] evm: security.capability
May  9 23:10:07 cmp02 kernel: [    0.102630] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
May  9 23:10:07 cmp02 kernel: [    0.104020] futex hash table entries: 2048 (order: 5, 131072 bytes)
May  9 23:10:07 cmp02 kernel: [    0.106161] pinctrl core: initialized pinctrl subsystem
May  9 23:10:07 cmp02 kernel: [    0.107865] RTC time: 23:09:56, date: 05/09/18
May  9 23:10:07 cmp02 kernel: [    0.110005] NET: Registered protocol family 16
May  9 23:10:07 cmp02 kernel: [    0.111274] cpuidle: using governor ladder
May  9 23:10:07 cmp02 kernel: [    0.112010] cpuidle: using governor menu
May  9 23:10:07 cmp02 kernel: [    0.112978] PCCT header not found.
May  9 23:10:07 cmp02 kernel: [    0.113975] ACPI: bus type PCI registered
May  9 23:10:07 cmp02 kernel: [    0.114952] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
May  9 23:10:07 cmp02 kernel: [    0.116139] PCI: Using configuration type 1 for base access
May  9 23:10:07 cmp02 kernel: [    0.118384] core: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
May  9 23:10:07 cmp02 kernel: [    0.121149] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
May  9 23:10:07 cmp02 kernel: [    0.121451] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
May  9 23:10:07 cmp02 kernel: [    0.124383] ACPI: Added _OSI(Module Device)
May  9 23:10:07 cmp02 kernel: [    0.125379] ACPI: Added _OSI(Processor Device)
May  9 23:10:07 cmp02 kernel: [    0.126439] ACPI: Added _OSI(3.0 _SCP Extensions)
May  9 23:10:07 cmp02 kernel: [    0.127530] ACPI: Added _OSI(Processor Aggregator Device)
May  9 23:10:07 cmp02 kernel: [    0.129545] ACPI: Interpreter enabled
May  9 23:10:07 cmp02 kernel: [    0.130819] ACPI: (supports S0 S5)
May  9 23:10:07 cmp02 kernel: [    0.131685] ACPI: Using IOAPIC for interrupt routing
May  9 23:10:07 cmp02 kernel: [    0.132017] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
May  9 23:10:07 cmp02 kernel: [    0.134876] ACPI: Enabled 16 GPEs in block 00 to 0F
May  9 23:10:07 cmp02 kernel: [    0.138952] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
May  9 23:10:07 cmp02 kernel: [    0.140010] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
May  9 23:10:07 cmp02 kernel: [    0.142121] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
May  9 23:10:07 cmp02 kernel: [    0.143893] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
May  9 23:10:07 cmp02 kernel: [    0.144278] acpiphp: Slot [3] registered
May  9 23:10:07 cmp02 kernel: [    0.145246] acpiphp: Slot [4] registered
May  9 23:10:07 cmp02 kernel: [    0.146223] acpiphp: Slot [5] registered
May  9 23:10:07 cmp02 kernel: [    0.147207] acpiphp: Slot [6] registered
May  9 23:10:07 cmp02 kernel: [    0.148027] acpiphp: Slot [7] registered
May  9 23:10:07 cmp02 kernel: [    0.149024] acpiphp: Slot [9] registered
May  9 23:10:07 cmp02 kernel: [    0.150003] acpiphp: Slot [10] registered
May  9 23:10:07 cmp02 kernel: [    0.151003] acpiphp: Slot [11] registered
May  9 23:10:07 cmp02 kernel: [    0.152026] acpiphp: Slot [12] registered
May  9 23:10:07 cmp02 kernel: [    0.153018] acpiphp: Slot [13] registered
May  9 23:10:07 cmp02 kernel: [    0.154031] acpiphp: Slot [14] registered
May  9 23:10:07 cmp02 kernel: [    0.155019] acpiphp: Slot [15] registered
May  9 23:10:07 cmp02 kernel: [    0.156026] acpiphp: Slot [16] registered
May  9 23:10:07 cmp02 kernel: [    0.157017] acpiphp: Slot [17] registered
May  9 23:10:07 cmp02 kernel: [    0.158368] acpiphp: Slot [18] registered
May  9 23:10:07 cmp02 kernel: [    0.159356] acpiphp: Slot [19] registered
May  9 23:10:07 cmp02 kernel: [    0.160028] acpiphp: Slot [20] registered
May  9 23:10:07 cmp02 kernel: [    0.163274] acpiphp: Slot [21] registered
May  9 23:10:07 cmp02 kernel: [    0.164027] acpiphp: Slot [22] registered
May  9 23:10:07 cmp02 kernel: [    0.165035] acpiphp: Slot [23] registered
May  9 23:10:07 cmp02 kernel: [    0.166026] acpiphp: Slot [24] registered
May  9 23:10:07 cmp02 kernel: [    0.167634] acpiphp: Slot [25] registered
May  9 23:10:07 cmp02 kernel: [    0.168027] acpiphp: Slot [26] registered
May  9 23:10:07 cmp02 kernel: [    0.169014] acpiphp: Slot [27] registered
May  9 23:10:07 cmp02 kernel: [    0.170008] acpiphp: Slot [28] registered
May  9 23:10:07 cmp02 kernel: [    0.171004] acpiphp: Slot [29] registered
May  9 23:10:07 cmp02 kernel: [    0.172000] acpiphp: Slot [30] registered
May  9 23:10:07 cmp02 kernel: [    0.172027] acpiphp: Slot [31] registered
May  9 23:10:07 cmp02 kernel: [    0.173014] PCI host bridge to bus 0000:00
May  9 23:10:07 cmp02 kernel: [    0.174357] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
May  9 23:10:07 cmp02 kernel: [    0.175810] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
May  9 23:10:07 cmp02 kernel: [    0.176006] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
May  9 23:10:07 cmp02 kernel: [    0.178382] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
May  9 23:10:07 cmp02 kernel: [    0.180006] pci_bus 0000:00: root bus resource [bus 00-ff]
May  9 23:10:07 cmp02 kernel: [    0.181283] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
May  9 23:10:07 cmp02 kernel: [    0.181800] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
May  9 23:10:07 cmp02 kernel: [    0.182441] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
May  9 23:10:07 cmp02 kernel: [    0.192007] pci 0000:00:01.1: reg 0x20: [io  0xc180-0xc18f]
May  9 23:10:07 cmp02 kernel: [    0.198702] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
May  9 23:10:07 cmp02 kernel: [    0.200006] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
May  9 23:10:07 cmp02 kernel: [    0.201414] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
May  9 23:10:07 cmp02 kernel: [    0.203203] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
May  9 23:10:07 cmp02 kernel: [    0.205526] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
May  9 23:10:07 cmp02 kernel: [    0.206083] pci 0000:00:01.3: quirk: [io  0x0600-0x063f] claimed by PIIX4 ACPI
May  9 23:10:07 cmp02 kernel: [    0.207998] pci 0000:00:01.3: quirk: [io  0x0700-0x070f] claimed by PIIX4 SMB
May  9 23:10:07 cmp02 kernel: [    0.208305] pci 0000:00:02.0: [1013:00b8] type 00 class 0x030000
May  9 23:10:07 cmp02 kernel: [    0.212008] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref]
May  9 23:10:07 cmp02 kernel: [    0.216007] pci 0000:00:02.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff]
May  9 23:10:07 cmp02 kernel: [    0.232007] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref]
May  9 23:10:07 cmp02 kernel: [    0.234476] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000
May  9 23:10:07 cmp02 kernel: [    0.238224] pci 0000:00:03.0: reg 0x10: [io  0xc080-0xc09f]
May  9 23:10:07 cmp02 kernel: [    0.241693] pci 0000:00:03.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff]
May  9 23:10:07 cmp02 kernel: [    0.258010] pci 0000:00:03.0: reg 0x30: [mem 0xfeac0000-0xfeafffff pref]
May  9 23:10:07 cmp02 kernel: [    0.260454] pci 0000:00:04.0: [1af4:1000] type 00 class 0x020000
May  9 23:10:07 cmp02 kernel: [    0.263086] pci 0000:00:04.0: reg 0x10: [io  0xc0a0-0xc0bf]
May  9 23:10:07 cmp02 kernel: [    0.265317] pci 0000:00:04.0: reg 0x14: [mem 0xfebd2000-0xfebd2fff]
May  9 23:10:07 cmp02 kernel: [    0.284008] pci 0000:00:04.0: reg 0x30: [mem 0xfeb00000-0xfeb3ffff pref]
May  9 23:10:07 cmp02 kernel: [    0.284412] pci 0000:00:05.0: [1af4:1000] type 00 class 0x020000
May  9 23:10:07 cmp02 kernel: [    0.288007] pci 0000:00:05.0: reg 0x10: [io  0xc0c0-0xc0df]
May  9 23:10:07 cmp02 kernel: [    0.291803] pci 0000:00:05.0: reg 0x14: [mem 0xfebd3000-0xfebd3fff]
May  9 23:10:07 cmp02 kernel: [    0.308008] pci 0000:00:05.0: reg 0x30: [mem 0xfeb40000-0xfeb7ffff pref]
May  9 23:10:07 cmp02 kernel: [    0.308412] pci 0000:00:06.0: [1af4:1000] type 00 class 0x020000
May  9 23:10:07 cmp02 kernel: [    0.311516] pci 0000:00:06.0: reg 0x10: [io  0xc0e0-0xc0ff]
May  9 23:10:07 cmp02 kernel: [    0.313343] pci 0000:00:06.0: reg 0x14: [mem 0xfebd4000-0xfebd4fff]
May  9 23:10:07 cmp02 kernel: [    0.329668] pci 0000:00:06.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref]
May  9 23:10:07 cmp02 kernel: [    0.330077] pci 0000:00:07.0: [1af4:1001] type 00 class 0x010000
May  9 23:10:07 cmp02 kernel: [    0.332007] pci 0000:00:07.0: reg 0x10: [io  0xc000-0xc03f]
May  9 23:10:07 cmp02 kernel: [    0.336007] pci 0000:00:07.0: reg 0x14: [mem 0xfebd5000-0xfebd5fff]
May  9 23:10:07 cmp02 kernel: [    0.353674] pci 0000:00:08.0: [8086:2934] type 00 class 0x0c0300
May  9 23:10:07 cmp02 kernel: [    0.362754] pci 0000:00:08.0: reg 0x20: [io  0xc100-0xc11f]
May  9 23:10:07 cmp02 kernel: [    0.365925] pci 0000:00:08.1: [8086:2935] type 00 class 0x0c0300
May  9 23:10:07 cmp02 kernel: [    0.376008] pci 0000:00:08.1: reg 0x20: [io  0xc120-0xc13f]
May  9 23:10:07 cmp02 kernel: [    0.380090] pci 0000:00:08.2: [8086:2936] type 00 class 0x0c0300
May  9 23:10:07 cmp02 kernel: [    0.390093] pci 0000:00:08.2: reg 0x20: [io  0xc140-0xc15f]
May  9 23:10:07 cmp02 kernel: [    0.396050] pci 0000:00:08.7: [8086:293a] type 00 class 0x0c0320
May  9 23:10:07 cmp02 kernel: [    0.397771] pci 0000:00:08.7: reg 0x10: [mem 0xfebd6000-0xfebd6fff]
May  9 23:10:07 cmp02 kernel: [    0.410476] pci 0000:00:09.0: [1af4:1001] type 00 class 0x010000
May  9 23:10:07 cmp02 kernel: [    0.413287] pci 0000:00:09.0: reg 0x10: [io  0xc040-0xc07f]
May  9 23:10:07 cmp02 kernel: [    0.416007] pci 0000:00:09.0: reg 0x14: [mem 0xfebd7000-0xfebd7fff]
May  9 23:10:07 cmp02 kernel: [    0.434957] pci 0000:00:0a.0: [1af4:1002] type 00 class 0x00ff00
May  9 23:10:07 cmp02 kernel: [    0.436007] pci 0000:00:0a.0: reg 0x10: [io  0xc160-0xc17f]
May  9 23:10:07 cmp02 kernel: [    0.447161] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
May  9 23:10:07 cmp02 kernel: [    0.448153] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
May  9 23:10:07 cmp02 kernel: [    0.451022] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
May  9 23:10:07 cmp02 kernel: [    0.452454] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
May  9 23:10:07 cmp02 kernel: [    0.453811] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
May  9 23:10:07 cmp02 kernel: [    0.456461] SCSI subsystem initialized
May  9 23:10:07 cmp02 kernel: [    0.457773] libata version 3.00 loaded.
May  9 23:10:07 cmp02 kernel: [    0.457773] pci 0000:00:02.0: vgaarb: setting as boot VGA device
May  9 23:10:07 cmp02 kernel: [    0.457773] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
May  9 23:10:07 cmp02 kernel: [    0.460008] pci 0000:00:02.0: vgaarb: bridge control possible
May  9 23:10:07 cmp02 kernel: [    0.461308] vgaarb: loaded
May  9 23:10:07 cmp02 kernel: [    0.462099] ACPI: bus type USB registered
May  9 23:10:07 cmp02 kernel: [    0.463428] usbcore: registered new interface driver usbfs
May  9 23:10:07 cmp02 kernel: [    0.464014] usbcore: registered new interface driver hub
May  9 23:10:07 cmp02 kernel: [    0.466084] usbcore: registered new device driver usb
May  9 23:10:07 cmp02 kernel: [    0.467296] EDAC MC: Ver: 3.0.0
May  9 23:10:07 cmp02 kernel: [    0.468351] PCI: Using ACPI for IRQ routing
May  9 23:10:07 cmp02 kernel: [    0.469330] PCI: pci_cache_line_size set to 64 bytes
May  9 23:10:07 cmp02 kernel: [    0.469622] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
May  9 23:10:07 cmp02 kernel: [    0.469623] e820: reserve RAM buffer [mem 0xbffdf000-0xbfffffff]
May  9 23:10:07 cmp02 kernel: [    0.469720] NetLabel: Initializing
May  9 23:10:07 cmp02 kernel: [    0.470874] NetLabel:  domain hash size = 128
May  9 23:10:07 cmp02 kernel: [    0.472005] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
May  9 23:10:07 cmp02 kernel: [    0.473574] NetLabel:  unlabeled traffic allowed by default
May  9 23:10:07 cmp02 kernel: [    0.474820] clocksource: Switched to clocksource kvm-clock
May  9 23:10:07 cmp02 kernel: [    0.485228] VFS: Disk quotas dquot_6.6.0
May  9 23:10:07 cmp02 kernel: [    0.486238] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
May  9 23:10:07 cmp02 kernel: [    0.488703] AppArmor: AppArmor Filesystem Enabled
May  9 23:10:07 cmp02 kernel: [    0.489847] pnp: PnP ACPI init
May  9 23:10:07 cmp02 kernel: [    0.490694] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
May  9 23:10:07 cmp02 kernel: [    0.490723] pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
May  9 23:10:07 cmp02 kernel: [    0.490751] pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
May  9 23:10:07 cmp02 kernel: [    0.490773] pnp 00:03: [dma 2]
May  9 23:10:07 cmp02 kernel: [    0.490788] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
May  9 23:10:07 cmp02 kernel: [    0.490862] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
May  9 23:10:07 cmp02 kernel: [    0.491068] pnp: PnP ACPI: found 5 devices
May  9 23:10:07 cmp02 kernel: [    0.499990] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
May  9 23:10:07 cmp02 kernel: [    0.501991] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
May  9 23:10:07 cmp02 kernel: [    0.501992] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
May  9 23:10:07 cmp02 kernel: [    0.501994] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
May  9 23:10:07 cmp02 kernel: [    0.501995] pci_bus 0000:00: resource 7 [mem 0xc0000000-0xfebfffff window]
May  9 23:10:07 cmp02 kernel: [    0.502048] NET: Registered protocol family 2
May  9 23:10:07 cmp02 kernel: [    0.503252] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
May  9 23:10:07 cmp02 kernel: [    0.505048] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
May  9 23:10:07 cmp02 kernel: [    0.507133] TCP: Hash tables configured (established 65536 bind 65536)
May  9 23:10:07 cmp02 kernel: [    0.508861] UDP hash table entries: 4096 (order: 5, 131072 bytes)
May  9 23:10:07 cmp02 kernel: [    0.510650] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
May  9 23:10:07 cmp02 kernel: [    0.512107] NET: Registered protocol family 1
May  9 23:10:07 cmp02 kernel: [    0.513143] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
May  9 23:10:07 cmp02 kernel: [    0.514462] pci 0000:00:01.0: PIIX3: Enabling Passive Release
May  9 23:10:07 cmp02 kernel: [    0.515743] pci 0000:00:01.0: Activating ISA DMA hang workarounds
May  9 23:10:07 cmp02 kernel: [    0.517122] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
May  9 23:10:07 cmp02 kernel: [    0.545503] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
May  9 23:10:07 cmp02 kernel: [    0.602523] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
May  9 23:10:07 cmp02 kernel: [    0.658230] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
May  9 23:10:07 cmp02 kernel: [    0.716860] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
May  9 23:10:07 cmp02 kernel: [    0.748686] PCI: CLS 0 bytes, default 64
May  9 23:10:07 cmp02 kernel: [    0.748724] Unpacking initramfs...
May  9 23:10:07 cmp02 kernel: [    1.558055] Freeing initrd memory: 47792K
May  9 23:10:07 cmp02 kernel: [    1.559195] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
May  9 23:10:07 cmp02 kernel: [    1.560599] software IO TLB [mem 0xbbfdf000-0xbffdf000] (64MB) mapped at [ffff9f723bfdf000-ffff9f723ffdefff]
May  9 23:10:07 cmp02 kernel: [    1.563191] Scanning for low memory corruption every 60 seconds
May  9 23:10:07 cmp02 kernel: [    1.565331] audit: initializing netlink subsys (disabled)
May  9 23:10:07 cmp02 kernel: [    1.567220] audit: type=2000 audit(1525907397.443:1): state=initialized audit_enabled=0 res=1
May  9 23:10:07 cmp02 kernel: [    1.567510] Initialise system trusted keyrings
May  9 23:10:07 cmp02 kernel: [    1.567520] Key type blacklist registered
May  9 23:10:07 cmp02 kernel: [    1.567622] workingset: timestamp_bits=36 max_order=21 bucket_order=0
May  9 23:10:07 cmp02 kernel: [    1.568808] zbud: loaded
May  9 23:10:07 cmp02 kernel: [    1.569578] squashfs: version 4.0 (2009/01/31) Phillip Lougher
May  9 23:10:07 cmp02 kernel: [    1.569732] fuse init (API version 7.26)
May  9 23:10:07 cmp02 kernel: [    1.571722] Key type asymmetric registered
May  9 23:10:07 cmp02 kernel: [    1.571723] Asymmetric key parser 'x509' registered
May  9 23:10:07 cmp02 kernel: [    1.571750] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
May  9 23:10:07 cmp02 kernel: [    1.571793] io scheduler noop registered
May  9 23:10:07 cmp02 kernel: [    1.571794] io scheduler deadline registered
May  9 23:10:07 cmp02 kernel: [    1.571816] io scheduler cfq registered (default)
May  9 23:10:07 cmp02 kernel: [    1.590034] intel_idle: does not run on family 6 model 62
May  9 23:10:07 cmp02 kernel: [    1.590158] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
May  9 23:10:07 cmp02 kernel: [    1.594324] ACPI: Power Button [PWRF]
May  9 23:10:07 cmp02 kernel: [    1.598173] GHES: HEST is not enabled!
May  9 23:10:07 cmp02 kernel: [    1.633516] virtio-pci 0000:00:03.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.668871] virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.701646] virtio-pci 0000:00:05.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.735981] virtio-pci 0000:00:06.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.769884] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.804751] virtio-pci 0000:00:09.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.844361] virtio-pci 0000:00:0a.0: virtio_pci: leaving for legacy driver
May  9 23:10:07 cmp02 kernel: [    1.848229] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
May  9 23:10:07 cmp02 kernel: [    1.879054] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
May  9 23:10:07 cmp02 kernel: [    1.883253] Linux agpgart interface v0.103
May  9 23:10:07 cmp02 kernel: [    1.887275] loop: module loaded
May  9 23:10:07 cmp02 kernel: [    1.888482] ata_piix 0000:00:01.1: version 2.13
May  9 23:10:07 cmp02 kernel: [    1.893230] scsi host0: ata_piix
May  9 23:10:07 cmp02 systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
May  9 23:10:07 cmp02 kernel: [    1.895470] scsi host1: ata_piix
May  9 23:10:07 cmp02 kernel: [    1.896577] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc180 irq 14
May  9 23:10:07 cmp02 kernel: [    1.899093] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc188 irq 15
May  9 23:10:07 cmp02 kernel: [    1.901930] libphy: Fixed MDIO Bus: probed
May  9 23:10:07 cmp02 kernel: [    1.903299] tun: Universal TUN/TAP device driver, 1.6
May  9 23:10:07 cmp02 kernel: [    1.904763] PPP generic driver version 2.4.2
May  9 23:10:07 cmp02 systemd[1]: Reached target Network.
May  9 23:10:07 cmp02 cloud-init[1038]: Cloud-init v. 18.2 running 'init' at Wed, 09 May 2018 23:10:05 +0000. Up 9.29 seconds.
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: +--------+-------+----------------------------+---------------+-------+-------------------+
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: | Device |   Up  |          Address           |      Mask     | Scope |     Hw-Address    |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: +--------+-------+----------------------------+---------------+-------+-------------------+
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |  ens3  |  True |       192.168.11.50        | 255.255.255.0 |   .   | 52:54:00:90:6f:f7 |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |  ens3  |  True | fe80::5054:ff:fe90:6ff7/64 |       .       |  link | 52:54:00:90:6f:f7 |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |  ens4  | False |             .              |       .       |   .   | 52:54:00:f6:39:39 |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |  ens5  | False |             .              |       .       |   .   | 52:54:00:53:d1:ac |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |  ens6  | False |             .              |       .       |   .   | 52:54:00:a3:a9:4f |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |   lo   |  True |         127.0.0.1          |   255.0.0.0   |   .   |         .         |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |   lo   |  True |          ::1/128           |       .       |  host |         .         |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: +--------+-------+----------------------------+---------------+-------+-------------------+
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info++++++++++++++++++++++++++++++
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: | Route | Destination  |   Gateway    |    Genmask    | Interface | Flags |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |   0   |   0.0.0.0    | 192.168.11.1 |    0.0.0.0    |    ens3   |   UG  |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: |   1   | 192.168.11.0 |   0.0.0.0    | 255.255.255.0 |    ens3   |   U   |
May  9 23:10:07 cmp02 cloud-init[1038]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
May  9 23:10:07 cmp02 cloud-init[1038]: Generating public/private rsa key pair.
May  9 23:10:07 cmp02 cloud-init[1038]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
May  9 23:10:07 cmp02 cloud-init[1038]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
May  9 23:10:07 cmp02 cloud-init[1038]: The key fingerprint is:
May  9 23:10:07 cmp02 cloud-init[1038]: SHA256:Q/daQb5f/FlcwmvICizOwvz7beTcMc8TejGIs2a+UJ4 root@cmp02
May  9 23:10:07 cmp02 cloud-init[1038]: The key's randomart image is:
May  9 23:10:07 cmp02 cloud-init[1038]: +---[RSA 2048]----+
May  9 23:10:07 cmp02 cloud-init[1038]: |            .    |
May  9 23:10:07 cmp02 cloud-init[1038]: |           o .   |
May  9 23:10:07 cmp02 cloud-init[1038]: |        . . o o .|
May  9 23:10:07 cmp02 cloud-init[1038]: |       o . o + =.|
May  9 23:10:07 cmp02 cloud-init[1038]: |      . S ..*.o =|
May  9 23:10:07 cmp02 cloud-init[1038]: |   o o . =+=+o+.+|
May  9 23:10:07 cmp02 cloud-init[1038]: |    + o .+E+ *.=.|
May  9 23:10:07 cmp02 cloud-init[1038]: |     o   oB o =  |
May  9 23:10:07 cmp02 cloud-init[1038]: |      oo.=+. . . |
May  9 23:10:07 cmp02 cloud-init[1038]: +----[SHA256]-----+
May  9 23:10:07 cmp02 cloud-init[1038]: Generating public/private dsa key pair.
May  9 23:10:07 cmp02 kernel: [    1.906113] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
May  9 23:10:07 cmp02 cloud-init[1038]: Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
May  9 23:10:07 cmp02 kernel: [    1.907794] ehci-pci: EHCI PCI platform driver
May  9 23:10:07 cmp02 kernel: [    1.944211] ehci-pci 0000:00:08.7: EHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    1.945418] ehci-pci 0000:00:08.7: new USB bus registered, assigned bus number 1
May  9 23:10:07 cmp02 kernel: [    1.948195] ehci-pci 0000:00:08.7: irq 11, io mem 0xfebd6000
May  9 23:10:07 cmp02 kernel: [    1.964332] ehci-pci 0000:00:08.7: USB 2.0 started, EHCI 1.00
May  9 23:10:07 cmp02 kernel: [    1.966623] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May  9 23:10:07 cmp02 kernel: [    1.968438] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:10:07 cmp02 kernel: [    1.970207] usb usb1: Product: EHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    1.971355] usb usb1: Manufacturer: Linux 4.13.0-41-generic ehci_hcd
May  9 23:10:07 cmp02 kernel: [    1.973244] usb usb1: SerialNumber: 0000:00:08.7
May  9 23:10:07 cmp02 kernel: [    1.994552] hub 1-0:1.0: USB hub found
May  9 23:10:07 cmp02 kernel: [    1.996050] hub 1-0:1.0: 6 ports detected
May  9 23:10:07 cmp02 kernel: [    1.997222] ehci-platform: EHCI generic platform driver
May  9 23:10:07 cmp02 kernel: [    1.999272] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
May  9 23:10:07 cmp02 kernel: [    2.001177] ohci-pci: OHCI PCI platform driver
May  9 23:10:07 cmp02 kernel: [    2.002521] ohci-platform: OHCI generic platform driver
May  9 23:10:07 cmp02 kernel: [    2.003977] uhci_hcd: USB Universal Host Controller Interface driver
May  9 23:10:07 cmp02 kernel: [    2.040527] uhci_hcd 0000:00:08.0: UHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    2.042267] uhci_hcd 0000:00:08.0: new USB bus registered, assigned bus number 2
May  9 23:10:07 cmp02 kernel: [    2.044017] uhci_hcd 0000:00:08.0: detected 2 ports
May  9 23:10:07 cmp02 kernel: [    2.045199] uhci_hcd 0000:00:08.0: irq 11, io base 0x0000c100
May  9 23:10:07 cmp02 kernel: [    2.047117] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May  9 23:10:07 cmp02 kernel: [    2.049904] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:10:07 cmp02 kernel: [    2.052444] usb usb2: Product: UHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    2.054143] usb usb2: Manufacturer: Linux 4.13.0-41-generic uhci_hcd
May  9 23:10:07 cmp02 kernel: [    2.056094] usb usb2: SerialNumber: 0000:00:08.0
May  9 23:10:07 cmp02 kernel: [    2.057248] hub 2-0:1.0: USB hub found
May  9 23:10:07 cmp02 kernel: [    2.059161] hub 2-0:1.0: 2 ports detected
May  9 23:10:07 cmp02 kernel: [    2.061633] ata1.01: NODEV after polling detection
May  9 23:10:07 cmp02 kernel: [    2.061926] ata1.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
May  9 23:10:07 cmp02 kernel: [    2.064521] ata1.00: configured for MWDMA2
May  9 23:10:07 cmp02 kernel: [    2.066186] scsi 0:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     2.5+ PQ: 0 ANSI: 5
May  9 23:10:07 cmp02 kernel: [    2.072775] sr 0:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
May  9 23:10:07 cmp02 kernel: [    2.074686] cdrom: Uniform CD-ROM driver Revision: 3.20
May  9 23:10:07 cmp02 kernel: [    2.076205] sr 0:0:0:0: Attached scsi CD-ROM sr0
May  9 23:10:07 cmp02 kernel: [    2.076245] sr 0:0:0:0: Attached scsi generic sg0 type 5
May  9 23:10:07 cmp02 kernel: [    2.102323] uhci_hcd 0000:00:08.1: UHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    2.106085] uhci_hcd 0000:00:08.1: new USB bus registered, assigned bus number 3
May  9 23:10:07 cmp02 kernel: [    2.108375] uhci_hcd 0000:00:08.1: detected 2 ports
May  9 23:10:07 cmp02 kernel: [    2.109855] uhci_hcd 0000:00:08.1: irq 10, io base 0x0000c120
May  9 23:10:07 cmp02 kernel: [    2.111761] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May  9 23:10:07 cmp02 kernel: [    2.113226] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:10:07 cmp02 kernel: [    2.117170] usb usb3: Product: UHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    2.118848] usb usb3: Manufacturer: Linux 4.13.0-41-generic uhci_hcd
May  9 23:10:07 cmp02 kernel: [    2.120762] usb usb3: SerialNumber: 0000:00:08.1
May  9 23:10:07 cmp02 kernel: [    2.121936] hub 3-0:1.0: USB hub found
May  9 23:10:07 cmp02 kernel: [    2.122876] hub 3-0:1.0: 2 ports detected
May  9 23:10:07 cmp02 kernel: [    2.159082] uhci_hcd 0000:00:08.2: UHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    2.161479] uhci_hcd 0000:00:08.2: new USB bus registered, assigned bus number 4
May  9 23:10:07 cmp02 kernel: [    2.163220] uhci_hcd 0000:00:08.2: detected 2 ports
May  9 23:10:07 cmp02 kernel: [    2.165219] uhci_hcd 0000:00:08.2: irq 10, io base 0x0000c140
May  9 23:10:07 cmp02 kernel: [    2.169452] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May  9 23:10:07 cmp02 kernel: [    2.173904] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:10:07 cmp02 kernel: [    2.176053] usb usb4: Product: UHCI Host Controller
May  9 23:10:07 cmp02 kernel: [    2.177267] usb usb4: Manufacturer: Linux 4.13.0-41-generic uhci_hcd
May  9 23:10:07 cmp02 kernel: [    2.180711] usb usb4: SerialNumber: 0000:00:08.2
May  9 23:10:07 cmp02 kernel: [    2.182227] hub 4-0:1.0: USB hub found
May  9 23:10:07 cmp02 kernel: [    2.183182] hub 4-0:1.0: 2 ports detected
May  9 23:10:07 cmp02 kernel: [    2.185505] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
May  9 23:10:07 cmp02 kernel: [    2.191776] serio: i8042 KBD port at 0x60,0x64 irq 1
May  9 23:10:07 cmp02 kernel: [    2.194502] serio: i8042 AUX port at 0x60,0x64 irq 12
May  9 23:10:07 cmp02 kernel: [    2.196842] mousedev: PS/2 mouse device common for all mice
May  9 23:10:07 cmp02 kernel: [    2.200243] rtc_cmos 00:00: RTC can wake from S4
May  9 23:10:07 cmp02 kernel: [    2.202346] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
May  9 23:10:07 cmp02 kernel: [    2.204980] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
May  9 23:10:07 cmp02 kernel: [    2.207042] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram
May  9 23:10:07 cmp02 kernel: [    2.209045] i2c /dev entries driver
May  9 23:10:07 cmp02 kernel: [    2.210522] device-mapper: uevent: version 1.0.3
May  9 23:10:07 cmp02 kernel: [    2.211937] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
May  9 23:10:07 cmp02 kernel: [    2.215840] ledtrig-cpu: registered to indicate activity on CPUs
May  9 23:10:07 cmp02 kernel: [    2.218928] NET: Registered protocol family 10
May  9 23:10:07 cmp02 kernel: [    2.225910] Segment Routing with IPv6
May  9 23:10:07 cmp02 kernel: [    2.226863] NET: Registered protocol family 17
May  9 23:10:07 cmp02 kernel: [    2.229783] Key type dns_resolver registered
May  9 23:10:07 cmp02 kernel: [    2.231985] RAS: Correctable Errors collector initialized.
May  9 23:10:07 cmp02 kernel: [    2.234066] sched_clock: Marking stable (2233888829, 0)->(2697445831, -463557002)
May  9 23:10:07 cmp02 kernel: [    2.237792] registered taskstats version 1
May  9 23:10:07 cmp02 kernel: [    2.239859] Loading compiled-in X.509 certificates
May  9 23:10:07 cmp02 kernel: [    2.245155] Loaded X.509 cert 'Build time autogenerated kernel key: 455b6c2f89645ccacce587853289bc763cf1d7aa'
May  9 23:10:07 cmp02 kernel: [    2.248558] zswap: loaded using pool lzo/zbud
May  9 23:10:07 cmp02 kernel: [    2.257368] Key type big_key registered
May  9 23:10:07 cmp02 kernel: [    2.258798] Key type trusted registered
May  9 23:10:07 cmp02 kernel: [    2.264546] Key type encrypted registered
May  9 23:10:07 cmp02 kernel: [    2.266884] AppArmor: AppArmor sha1 policy hashing enabled
May  9 23:10:07 cmp02 kernel: [    2.269190] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
May  9 23:10:07 cmp02 kernel: [    2.271813] evm: HMAC attrs: 0x1
May  9 23:10:07 cmp02 kernel: [    2.274568]   Magic number: 2:726:200
May  9 23:10:07 cmp02 kernel: [    2.276940] rtc_cmos 00:00: setting system clock to 2018-05-09 23:09:58 UTC (1525907398)
May  9 23:10:07 cmp02 kernel: [    2.280479] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
May  9 23:10:07 cmp02 kernel: [    2.282941] EDD information not available.
May  9 23:10:07 cmp02 kernel: [    2.285373] PM: Hibernation image not present or could not be loaded.
May  9 23:10:07 cmp02 kernel: [    2.292685] Freeing unused kernel memory: 2368K
May  9 23:10:07 cmp02 kernel: [    2.293759] Write protecting the kernel read-only data: 18432k
May  9 23:10:07 cmp02 kernel: [    2.295760] Freeing unused kernel memory: 2024K
May  9 23:10:07 cmp02 kernel: [    2.297872] Freeing unused kernel memory: 88K
May  9 23:10:07 cmp02 kernel: [    2.302718] x86/mm: Checked W+X mappings: passed, no W+X pages found.
May  9 23:10:07 cmp02 kernel: [    2.304389] x86/mm: Checking user space page tables
May  9 23:10:07 cmp02 kernel: [    2.307137] x86/mm: Checked W+X mappings: passed, no W+X pages found.
May  9 23:10:07 cmp02 kernel: [    2.397068]  vda: vda1
May  9 23:10:07 cmp02 kernel: [    2.401122] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input4
May  9 23:10:07 cmp02 kernel: [    2.406636] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input3
May  9 23:10:07 cmp02 kernel: [    2.407314] FDC 0 is a S82078B
May  9 23:10:07 cmp02 kernel: [    2.438604] AVX version of gcm_enc/dec engaged.
May  9 23:10:07 cmp02 kernel: [    2.440077] AES CTR mode by8 optimization enabled
May  9 23:10:07 cmp02 kernel: [    2.443393] virtio_net virtio2 ens5: renamed from eth2
May  9 23:10:07 cmp02 kernel: [    2.450379] [TTM] Zone  kernel: Available graphics memory: 4083988 kiB
May  9 23:10:07 cmp02 kernel: [    2.453447] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
May  9 23:10:07 cmp02 kernel: [    2.457640] [TTM] Initializing pool allocator
May  9 23:10:07 cmp02 kernel: [    2.459290] [TTM] Initializing DMA pool allocator
May  9 23:10:07 cmp02 kernel: [    2.463754] [drm] fb mappable at 0xFC000000
May  9 23:10:07 cmp02 kernel: [    2.464942] [drm] vram aper at 0xFC000000
May  9 23:10:07 cmp02 kernel: [    2.467150] [drm] size 33554432
May  9 23:10:07 cmp02 kernel: [    2.469169] [drm] fb depth is 24
May  9 23:10:07 cmp02 kernel: [    2.470382] [drm]    pitch is 3072
May  9 23:10:07 cmp02 kernel: [    2.473025] fbcon: cirrusdrmfb (fb0) is primary device
May  9 23:10:07 cmp02 kernel: [    2.473943] virtio_net virtio0 ens3: renamed from eth0
May  9 23:10:07 cmp02 kernel: [    2.521304] Console: switching to colour frame buffer device 128x48
May  9 23:10:07 cmp02 kernel: [    2.543609] cirrus 0000:00:02.0: fb0: cirrusdrmfb frame buffer device
May  9 23:10:07 cmp02 kernel: [    2.560317] virtio_net virtio3 ens6: renamed from eth3
May  9 23:10:07 cmp02 kernel: [    2.568600] [drm] Initialized cirrus 1.0.0 20110418 for 0000:00:02.0 on minor 0
May  9 23:10:07 cmp02 kernel: [    2.589499] tsc: Refined TSC clocksource calibration: 2800.048 MHz
May  9 23:10:07 cmp02 kernel: [    2.589821] virtio_net virtio1 ens4: renamed from eth1
May  9 23:10:07 cmp02 kernel: [    2.593938] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x285c6e38acc, max_idle_ns: 440795291487 ns
May  9 23:10:07 cmp02 kernel: [    2.792285] raid6: sse2x1   gen()  4431 MB/s
May  9 23:10:07 cmp02 kernel: [    2.840321] raid6: sse2x1   xor()  3924 MB/s
May  9 23:10:07 cmp02 kernel: [    2.888014] raid6: sse2x2   gen()  6630 MB/s
May  9 23:10:07 cmp02 kernel: [    2.936009] raid6: sse2x2   xor()  4632 MB/s
May  9 23:10:07 cmp02 kernel: [    2.984013] raid6: sse2x4   gen()  7577 MB/s
May  9 23:10:07 cmp02 kernel: [    3.032008] raid6: sse2x4   xor()  5599 MB/s
May  9 23:10:07 cmp02 kernel: [    3.034317] raid6: using algorithm sse2x4 gen() 7577 MB/s
May  9 23:10:07 cmp02 kernel: [    3.035163] raid6: .... xor() 5599 MB/s, rmw enabled
May  9 23:10:07 cmp02 kernel: [    3.036766] raid6: using ssse3x2 recovery algorithm
May  9 23:10:07 cmp02 kernel: [    3.039963] xor: automatically using best checksumming function   avx       
May  9 23:10:07 cmp02 kernel: [    3.042511] async_tx: api initialized (async)
May  9 23:10:07 cmp02 kernel: [    3.112996] Btrfs loaded, crc32c=crc32c-intel
May  9 23:10:07 cmp02 kernel: [    3.165534] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
May  9 23:10:07 cmp02 kernel: [    3.963608] EXT4-fs (vda1): re-mounted. Opts: (null)
May  9 23:10:07 cmp02 kernel: [    4.024999] Loading iSCSI transport class v2.0-870.
May  9 23:10:07 cmp02 kernel: [    4.045615] iscsi: registered transport (tcp)
May  9 23:10:07 cmp02 kernel: [    4.144891] iscsi: registered transport (iser)
May  9 23:10:07 cmp02 kernel: [    4.627097] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0x700, revision 0
May  9 23:10:07 cmp02 kernel: [    4.845954] audit: type=1400 audit(1525907401.068:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=581 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    4.957764] EDAC sbridge: Seeking for: PCI ID 8086:0ea0
May  9 23:10:07 cmp02 kernel: [    4.957770] EDAC sbridge:  Ver: 1.1.2 
May  9 23:10:07 cmp02 kernel: [    5.081392] audit: type=1400 audit(1525907401.304:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lxd/lxd-bridge-proxy" pid=582 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.128380] audit: type=1400 audit(1525907401.351:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=655 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.170681] audit: type=1400 audit(1525907401.393:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=649 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.174435] audit: type=1400 audit(1525907401.397:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=649 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.272948] audit: type=1400 audit(1525907401.496:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=583 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.273354] audit: type=1400 audit(1525907401.496:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=583 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.274570] audit: type=1400 audit(1525907401.497:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=583 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.274916] audit: type=1400 audit(1525907401.498:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=583 comm="apparmor_parser"
May  9 23:10:07 cmp02 kernel: [    5.297049] ppdev: user-space parallel port driver
May  9 23:10:07 cmp02 kernel: [    5.930987] ISO 9660 Extensions: Microsoft Joliet Level 3
May  9 23:10:07 cmp02 kernel: [    5.936662] ISO 9660 Extensions: RRIP_1991A
May  9 23:10:07 cmp02 kernel: [    9.869318] EXT4-fs (vda1): resizing filesystem from 786171 to 26214139 blocks
May  9 23:10:07 cmp02 kernel: [    9.972378] EXT4-fs (vda1): resized filesystem to 26214139
May  9 23:10:07 cmp02 kernel: [   10.846388] new mount options do not match the existing superblock, will be ignored
May  9 23:10:07 cmp02 cloud-init[1038]: Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
May  9 23:10:07 cmp02 cloud-init[1038]: The key fingerprint is:
May  9 23:10:07 cmp02 cloud-init[1038]: SHA256:hlkMnx/4s2oFODTWT2ajcKf5cBF+KPu2Me1Epa371BA root@cmp02
May  9 23:10:07 cmp02 cloud-init[1038]: The key's randomart image is:
May  9 23:10:07 cmp02 cloud-init[1038]: +---[DSA 1024]----+
May  9 23:10:07 cmp02 cloud-init[1038]: |      ..  ..     |
May  9 23:10:07 cmp02 cloud-init[1038]: |      =+o+B.     |
May  9 23:10:07 cmp02 cloud-init[1038]: |     o =BX+o. E  |
May  9 23:10:07 cmp02 cloud-init[1038]: |      o+*=oo + . |
May  9 23:10:07 cmp02 cloud-init[1038]: |      o.S=+ o o  |
May  9 23:10:07 cmp02 cloud-init[1038]: |       . .o= . o |
May  9 23:10:07 cmp02 cloud-init[1038]: |         .* + . .|
May  9 23:10:07 cmp02 cloud-init[1038]: |        .o * o   |
May  9 23:10:07 cmp02 cloud-init[1038]: |       .. . o..  |
May  9 23:10:07 cmp02 cloud-init[1038]: +----[SHA256]-----+
May  9 23:10:07 cmp02 cloud-init[1038]: Generating public/private ecdsa key pair.
May  9 23:10:07 cmp02 cloud-init[1038]: Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
May  9 23:10:07 cmp02 cloud-init[1038]: Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
May  9 23:10:07 cmp02 cloud-init[1038]: The key fingerprint is:
May  9 23:10:07 cmp02 cloud-init[1038]: SHA256:YR6yXNRbX67OPPw0J2/v1H9ZRUyfIxyZ/0bPby9D0bM root@cmp02
May  9 23:10:07 cmp02 cloud-init[1038]: The key's randomart image is:
May  9 23:10:07 cmp02 cloud-init[1038]: +---[ECDSA 256]---+
May  9 23:10:07 cmp02 cloud-init[1038]: |        ..   .oo.|
May  9 23:10:07 cmp02 cloud-init[1038]: |       .  . oo. *|
May  9 23:10:07 cmp02 cloud-init[1038]: |      . =  o +.B.|
May  9 23:10:07 cmp02 cloud-init[1038]: |     . * o.   +o*|
May  9 23:10:07 cmp02 cloud-init[1038]: |      o S      =*|
May  9 23:10:07 cmp02 cloud-init[1038]: |              oEB|
May  9 23:10:07 cmp02 cloud-init[1038]: |             *.oO|
May  9 23:10:07 cmp02 cloud-init[1038]: |              O*O|
May  9 23:10:07 cmp02 cloud-init[1038]: |               O@|
May  9 23:10:07 cmp02 cloud-init[1038]: +----[SHA256]-----+
May  9 23:10:07 cmp02 cloud-init[1038]: Generating public/private ed25519 key pair.
May  9 23:10:07 cmp02 cloud-init[1038]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
May  9 23:10:07 cmp02 cloud-init[1038]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
May  9 23:10:07 cmp02 cloud-init[1038]: The key fingerprint is:
May  9 23:10:07 cmp02 cloud-init[1038]: SHA256:49Twb2xrWhchfuJRhCj4oo/Wbt0+v1BeXe3fszby0N8 root@cmp02
May  9 23:10:07 cmp02 cloud-init[1038]: The key's randomart image is:
May  9 23:10:07 cmp02 cloud-init[1038]: +--[ED25519 256]--+
May  9 23:10:07 cmp02 cloud-init[1038]: |       .   . ..  |
May  9 23:10:07 cmp02 cloud-init[1038]: |      . . . ..  .|
May  9 23:10:07 cmp02 cloud-init[1038]: |       ...  . o o|
May  9 23:10:07 cmp02 cloud-init[1038]: |      . .+ . o +.|
May  9 23:10:07 cmp02 cloud-init[1038]: |     . .S o = + o|
May  9 23:10:07 cmp02 cloud-init[1038]: |    .  o . * =..o|
May  9 23:10:07 cmp02 cloud-init[1038]: |     + .... O..oo|
May  9 23:10:07 cmp02 cloud-init[1038]: |    o + . o=.+.o=|
May  9 23:10:07 cmp02 cloud-init[1038]: |   . o.  .o=+.+oE|
May  9 23:10:07 cmp02 cloud-init[1038]: +----[SHA256]-----+
May  9 23:10:07 cmp02 systemd[1]: Started Initial cloud-init job (metadata service crawler).
May  9 23:10:07 cmp02 systemd[1]: Reached target System Initialization.
May  9 23:10:07 cmp02 systemd[1]: Listening on ACPID Listen Socket.
May  9 23:10:07 cmp02 systemd[1]: Listening on D-Bus System Message Bus Socket.
May  9 23:10:07 cmp02 systemd[1]: Started Daily Cleanup of Temporary Directories.
May  9 23:10:07 cmp02 systemd[1]: Started Daily apt download activities.
May  9 23:10:07 cmp02 systemd[1]: Starting Socket activation for snappy daemon.
May  9 23:10:07 cmp02 systemd[1]: Starting LXD - unix socket.
May  9 23:10:07 cmp02 systemd[1]: Listening on UUID daemon activation socket.
May  9 23:10:07 cmp02 systemd[1]: Started Daily apt upgrade and clean activities.
May  9 23:10:07 cmp02 systemd[1]: Reached target Timers.
May  9 23:10:07 cmp02 systemd[1]: Started ACPI Events Check.
May  9 23:10:07 cmp02 systemd[1]: Reached target Paths.
May  9 23:10:07 cmp02 systemd[1]: Reached target Network is Online.
May  9 23:10:07 cmp02 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
May  9 23:10:07 cmp02 systemd[1]: Reached target Cloud-config availability.
May  9 23:10:07 cmp02 systemd[1]: Listening on Socket activation for snappy daemon.
May  9 23:10:07 cmp02 systemd[1]: Listening on LXD - unix socket.
May  9 23:10:07 cmp02 systemd[1]: Reached target Sockets.
May  9 23:10:07 cmp02 systemd[1]: Reached target Basic System.
May  9 23:10:07 cmp02 systemd[1]: Starting Apply the settings specified in cloud-config...
May  9 23:10:07 cmp02 systemd[1]: Starting Login Service...
May  9 23:10:07 cmp02 systemd[1]: Starting System Logging Service...
May  9 23:10:07 cmp02 systemd[1]: Started Unattended Upgrades Shutdown.
May  9 23:10:07 cmp02 systemd[1]: Starting LXD - container startup/shutdown...
May  9 23:10:07 cmp02 systemd[1]: Starting /etc/rc.local Compatibility...
May  9 23:10:07 cmp02 systemd[1]: Started FUSE filesystem for LXC.
May  9 23:10:07 cmp02 systemd[1]: Starting The Salt Minion...
May  9 23:10:07 cmp02 systemd[1]: Started Deferred execution scheduler.
May  9 23:10:07 cmp02 systemd[1]: Starting LSB: MD monitoring daemon...
May  9 23:10:07 cmp02 systemd[1]: Starting Pollinate to seed the pseudo random number generator...
May  9 23:10:07 cmp02 systemd[1]: Starting LSB: Record successful boot for GRUB...
May  9 23:10:07 cmp02 systemd[1]: Started D-Bus System Message Bus.
May  9 23:10:07 cmp02 lxcfs[1190]: hierarchies:
May  9 23:10:07 cmp02 lxcfs[1190]:   0: fd:   5: hugetlb
May  9 23:10:07 cmp02 lxcfs[1190]:   1: fd:   6: cpuset
May  9 23:10:07 cmp02 lxcfs[1190]:   2: fd:   7: blkio
May  9 23:10:07 cmp02 lxcfs[1190]:   3: fd:   8: rdma
May  9 23:10:07 cmp02 lxcfs[1190]:   4: fd:   9: devices
May  9 23:10:07 cmp02 lxcfs[1190]:   5: fd:  10: freezer
May  9 23:10:07 cmp02 lxcfs[1190]:   6: fd:  11: cpu,cpuacct
May  9 23:10:07 cmp02 lxcfs[1190]:   7: fd:  12: pids
May  9 23:10:07 cmp02 lxcfs[1190]:   8: fd:  13: perf_event
May  9 23:10:07 cmp02 lxcfs[1190]:   9: fd:  14: net_cls,net_prio
May  9 23:10:07 cmp02 lxcfs[1190]:  10: fd:  15: memory
May  9 23:10:07 cmp02 lxcfs[1190]:  11: fd:  16: name=systemd
May  9 23:10:07 cmp02 pollinate[1216]: client sent challenge to [https://entropy.ubuntu.com/]
May  9 23:10:07 cmp02 dbus[1236]: [system] AppArmor D-Bus mediation is enabled
May  9 23:10:07 cmp02 dbus[1236]: [system] Successfully activated service 'org.freedesktop.systemd1'
May  9 23:10:07 cmp02 systemd[1]: Started Regular background program processing daemon.
May  9 23:10:07 cmp02 systemd[1]: Starting Accounts Service...
May  9 23:10:07 cmp02 systemd[1]: Starting Thermal Daemon Service...
May  9 23:10:07 cmp02 cron[1297]: (CRON) INFO (pidfile fd = 3)
May  9 23:10:07 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:10:07 cmp02 systemd[1]: Starting Snappy daemon...
May  9 23:10:07 cmp02 systemd[1]: Started System Logging Service.
May  9 23:10:07 cmp02 cron[1297]: (CRON) INFO (Running @reboot jobs)
May  9 23:10:07 cmp02 systemd[1]: Started /etc/rc.local Compatibility.
May  9 23:10:07 cmp02 mdadm[1200]:  * Starting MD monitoring service mdadm --monitor
May  9 23:10:07 cmp02 systemd[1]: Started Login Service.
May  9 23:10:07 cmp02 iscsid: iSCSI logger with pid=1358 started!
May  9 23:10:07 cmp02 systemd[1]: iscsid.service: Failed to read PID from file /run/iscsid.pid: Invalid argument
May  9 23:10:07 cmp02 systemd[1]: Started iSCSI initiator daemon (iscsid).
May  9 23:10:07 cmp02 systemd[1]: Starting Login to default iSCSI targets...
May  9 23:10:07 cmp02 acpid: starting up with netlink and the input layer
May  9 23:10:07 cmp02 acpid: 1 rule loaded
May  9 23:10:07 cmp02 acpid: waiting for events: event logging is off
May  9 23:10:07 cmp02 mdadm[1200]:    ...done.
May  9 23:10:07 cmp02 systemd[1]: Started LSB: MD monitoring daemon.
May  9 23:10:07 cmp02 iscsiadm[1381]: iscsiadm: No records found
May  9 23:10:08 cmp02 systemd[1]: Started Login to default iSCSI targets.
May  9 23:10:08 cmp02 systemd[1]: Reached target Remote File Systems (Pre).
May  9 23:10:08 cmp02 systemd[1]: Reached target Remote File Systems.
May  9 23:10:08 cmp02 systemd[1]: Starting Permit User Sessions...
May  9 23:10:08 cmp02 systemd[1]: Starting LSB: daemon to balance interrupts for SMP systems...
May  9 23:10:08 cmp02 systemd[1]: Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
May  9 23:10:08 cmp02 systemd[1]: Starting LSB: automatic crash report generation...
May  9 23:10:08 cmp02 systemd[1]: Started LSB: Record successful boot for GRUB.
May  9 23:10:08 cmp02 systemd[1]: Started Permit User Sessions.
May  9 23:10:08 cmp02 systemd[1]: Starting Terminate Plymouth Boot Screen...
May  9 23:10:08 cmp02 systemd[1]: Starting Hold until boot process finishes up...
May  9 23:10:08 cmp02 systemd[1]: Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
May  9 23:10:08 cmp02 irqbalance[1415]:  * Starting SMP IRQ Balancer: irqbalance
May  9 23:10:08 cmp02 systemd[1]: Started Terminate Plymouth Boot Screen.
May  9 23:10:08 cmp02 systemd[1]: Started Hold until boot process finishes up.
May  9 23:10:08 cmp02 systemd[1]: Started Getty on tty1.
May  9 23:10:08 cmp02 systemd[1]: Starting Set console scheme...
May  9 23:10:08 cmp02 apport[1432]:  * Starting automatic crash report generation: apport
May  9 23:10:08 cmp02 systemd[1]: Started Serial Getty on ttyS0.
May  9 23:10:08 cmp02 systemd[1]: Reached target Login Prompts.
May  9 23:10:08 cmp02 irqbalance[1415]:    ...done.
May  9 23:10:08 cmp02 systemd[1]: Started LSB: daemon to balance interrupts for SMP systems.
May  9 23:10:08 cmp02 apport[1432]:    ...done.
May  9 23:10:08 cmp02 thermald[1316]: NO RAPL sysfs present
May  9 23:10:08 cmp02 thermald[1316]: 13 CPUID levels; family:model:stepping 0x6:3e:4 (6:62:4)
May  9 23:10:08 cmp02 thermald[1316]:  Need Linux PowerCap sysfs
May  9 23:10:08 cmp02 systemd[1]: Started LSB: automatic crash report generation.
May  9 23:10:08 cmp02 systemd[1]: Started Set console scheme.
May  9 23:10:08 cmp02 systemd[1]: Started Thermal Daemon Service.
May  9 23:10:08 cmp02 dbus[1236]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
May  9 23:10:08 cmp02 systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
May  9 23:10:08 cmp02 thermald[1316]: Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check
May  9 23:10:08 cmp02 thermald[1316]: THD engine start failed
May  9 23:10:08 cmp02 cloud-init[1155]: Generating locales (this might take a while)...
May  9 23:10:08 cmp02 iscsid: iSCSI daemon with pid=1361 started!
May  9 23:10:08 cmp02 polkitd[1538]: started daemon version 0.105 using authority implementation `local' version `0.105'
May  9 23:10:08 cmp02 dbus[1236]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May  9 23:10:08 cmp02 systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks.
May  9 23:10:08 cmp02 accounts-daemon[1306]: started daemon version 0.6.40
May  9 23:10:08 cmp02 systemd[1]: Started Accounts Service.
May  9 23:10:08 cmp02 systemd[1]: Started LXD - container startup/shutdown.
May  9 23:10:08 cmp02 snapd[1329]: AppArmor status: apparmor is enabled and all features are available
May  9 23:10:08 cmp02 snapd[1329]: 2018/05/09 23:10:08.563505 helpers.go:115: error trying to compare the snap system key: system-key missing on disk
May  9 23:10:08 cmp02 snapd[1329]: 2018/05/09 23:10:08.568380 daemon.go:323: started snapd/2.32.3.2 (series 16; classic) ubuntu/16.04 (amd64) linux/4.13.0-41-generic.
May  9 23:10:08 cmp02 systemd[1]: Started Snappy daemon.
May  9 23:10:08 cmp02 pollinate[1216]: client verified challenge/response with [https://entropy.ubuntu.com/]
May  9 23:10:08 cmp02 pollinate[1216]: client hashed response from [https://entropy.ubuntu.com/]
May  9 23:10:08 cmp02 pollinate[1216]: client successfully seeded [/dev/urandom]
May  9 23:10:08 cmp02 systemd[1]: Started Pollinate to seed the pseudo random number generator.
May  9 23:10:08 cmp02 systemd[1]: Starting OpenBSD Secure Shell server...
May  9 23:10:08 cmp02 systemd[1]: Started OpenBSD Secure Shell server.
May  9 23:10:08 cmp02 systemd[1]: Started The Salt Minion.
May  9 23:10:08 cmp02 systemd[1]: Reached target Multi-User System.
May  9 23:10:08 cmp02 systemd[1]: Reached target Graphical Interface.
May  9 23:10:08 cmp02 systemd[1]: Starting Update UTMP about System Runlevel Changes...
May  9 23:10:08 cmp02 systemd[1]: Started Update UTMP about System Runlevel Changes.
May  9 23:10:09 cmp02 cloud-init[1155]:   en_US.UTF-8... done
May  9 23:10:09 cmp02 cloud-init[1155]: Generation complete.
May  9 23:10:09 cmp02 cloud-init[1155]: Cloud-init v. 18.2 running 'modules:config' at Wed, 09 May 2018 23:10:07 +0000. Up 11.14 seconds.
May  9 23:10:09 cmp02 systemd[1]: Started Apply the settings specified in cloud-config.
May  9 23:10:09 cmp02 systemd[1]: Starting Execute cloud user/final scripts...
May  9 23:10:09 cmp02 salt-minion[1196]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
May  9 23:10:09 cmp02 salt-minion[1196]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds
May  9 23:10:10 cmp02 systemd[1]: Stopping The Salt Minion...
May  9 23:10:10 cmp02 salt-minion[1196]: [WARNING ] Minion received a SIGTERM. Exiting.
May  9 23:10:10 cmp02 salt-minion[1196]: The Salt Minion is shutdown. Minion received a SIGTERM. Exited.
May  9 23:10:10 cmp02 systemd[1]: Stopped The Salt Minion.
May  9 23:10:10 cmp02 systemd[1]: Starting The Salt Minion...
May  9 23:10:11 cmp02 systemd[1]: Started The Salt Minion.
May  9 23:10:11 cmp02 ec2: 
May  9 23:10:11 cmp02 ec2: #############################################################
May  9 23:10:11 cmp02 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
May  9 23:10:11 cmp02 ec2: 1024 SHA256:hlkMnx/4s2oFODTWT2ajcKf5cBF+KPu2Me1Epa371BA root@cmp02 (DSA)
May  9 23:10:11 cmp02 ec2: 256 SHA256:YR6yXNRbX67OPPw0J2/v1H9ZRUyfIxyZ/0bPby9D0bM root@cmp02 (ECDSA)
May  9 23:10:11 cmp02 ec2: 256 SHA256:49Twb2xrWhchfuJRhCj4oo/Wbt0+v1BeXe3fszby0N8 root@cmp02 (ED25519)
May  9 23:10:11 cmp02 ec2: 2048 SHA256:Q/daQb5f/FlcwmvICizOwvz7beTcMc8TejGIs2a+UJ4 root@cmp02 (RSA)
May  9 23:10:11 cmp02 ec2: -----END SSH HOST KEY FINGERPRINTS-----
May  9 23:10:11 cmp02 ec2: #############################################################
May  9 23:10:11 cmp02 cloud-init[1725]: Cloud-init v. 18.2 running 'modules:final' at Wed, 09 May 2018 23:10:10 +0000. Up 13.99 seconds.
May  9 23:10:11 cmp02 cloud-init[1725]: Cloud-init v. 18.2 finished at Wed, 09 May 2018 23:10:11 +0000. Datasource DataSourceNoCloud [seed=/dev/sr0][dsmode=net].  Up 14.91 seconds
May  9 23:10:11 cmp02 systemd[1]: Started Execute cloud user/final scripts.
May  9 23:10:11 cmp02 systemd[1]: Reached target Cloud-init target.
May  9 23:10:11 cmp02 systemd[1]: Startup finished in 3.461s (kernel) + 11.506s (userspace) = 14.967s.
May  9 23:10:30 cmp02 systemd-timesyncd[523]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
May  9 23:10:45 cmp02 kernel: [   49.477193] random: crng init done
May  9 23:10:52 cmp02 salt-minion[1766]: [ERROR   ] Error while bringing up minion for multi-master. Is master at 192.168.11.2 responding?
May  9 23:13:22 cmp02 salt-minion[1766]: message repeated 3 times: [ [ERROR   ] Error while bringing up minion for multi-master. Is master at 192.168.11.2 responding?]
May  9 23:14:44 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install python-oauth python-psutil python-m2crypto.
May  9 23:14:48 cmp02 salt-minion[1766]: [ERROR   ] Command 'while true; do salt-call saltutil.running|grep fun: && continue; salt-call --local service.restart salt-minion; break; done' failed with return code: None
May  9 23:14:50 cmp02 salt-minion[1766]: [INFO    ] Executing command ['systemctl', 'status', 'salt-minion.service', '-n', '0'] in directory '/root'
May  9 23:14:51 cmp02 salt-minion[1766]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'salt-minion.service'] in directory '/root'
May  9 23:14:51 cmp02 salt-minion[1766]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'salt-minion.service'] in directory '/root'
May  9 23:14:51 cmp02 systemd[1]: Started /bin/systemctl restart salt-minion.service.
May  9 23:14:51 cmp02 systemd[1]: Stopping The Salt Minion...
May  9 23:14:51 cmp02 salt-minion[1766]: [WARNING ] Minion received a SIGTERM. Exiting.
May  9 23:14:51 cmp02 salt-minion[1766]: The Salt Minion is shutdown. Minion received a SIGTERM. Exited.
May  9 23:14:51 cmp02 systemd[1]: Stopped The Salt Minion.
May  9 23:14:51 cmp02 systemd[1]: Starting The Salt Minion...
May  9 23:14:51 cmp02 systemd[1]: Started The Salt Minion.
May  9 23:14:51 cmp02 salt-minion[2964]: [INFO    ] Setting up the Salt Minion "cmp02.mcp-pike-ovn-noha.local"
May  9 23:14:51 cmp02 salt-minion[2964]: [INFO    ] Starting up the Salt Minion
May  9 23:14:51 cmp02 salt-minion[2964]: [INFO    ] Starting pull socket on /var/run/salt/minion/minion_event_e795df387e_pull.ipc
May  9 23:14:52 cmp02 salt-minion[2964]: [INFO    ] Creating minion process manager
May  9 23:14:53 cmp02 salt-minion[2964]: [INFO    ] Executing command ['date', '+%z'] in directory '/root'
May  9 23:14:53 cmp02 salt-minion[2964]: [INFO    ] Updating job settings for scheduled job: __mine_interval
May  9 23:14:53 cmp02 salt-minion[2964]: [INFO    ] Added mine.update to scheduler
May  9 23:14:53 cmp02 salt-minion[2964]: [INFO    ] Minion is starting as user 'root'
May  9 23:14:53 cmp02 salt-minion[2964]: [INFO    ] Minion is ready to receive requests!
May  9 23:14:54 cmp02 salt-minion[2964]: [INFO    ] Running scheduled job: __mine_interval
May  9 23:15:19 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509231519791381
May  9 23:15:19 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 3085
May  9 23:15:22 cmp02 salt-minion[2964]: [INFO    ] Loading fresh modules for state activity
May  9 23:15:22 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/init.sls'
May  9 23:15:22 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/env.sls'
May  9 23:15:22 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/profile.sls'
May  9 23:15:22 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/repo.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/package.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/timezone.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/kernel.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/cpu.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/sysfs.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/locale.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/user.sls'
May  9 23:15:23 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/group.sls'
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/limit.sls'
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/systemd.sls'
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/system/apt.sls'
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/storage/init.sls'
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/storage/lvm.sls'
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/environment] at time 23:15:24.733576
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Executing state file.blockreplace for /etc/environment
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:24 cmp02 salt-minion[2964]: ---
May  9 23:15:24 cmp02 salt-minion[2964]: +++
May  9 23:15:24 cmp02 salt-minion[2964]: @@ -1 +1,4 @@
May  9 23:15:24 cmp02 salt-minion[2964]:  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
May  9 23:15:24 cmp02 salt-minion[2964]: +# SALT MANAGED VARIABLES - DO NOT EDIT - START
May  9 23:15:24 cmp02 salt-minion[2964]: +# +# SALT MANAGED VARIABLES - END
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/environment] at time 23:15:24.746362 duration_in_ms=12.787
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/profile.d] at time 23:15:24.746883
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Executing state file.directory for /etc/profile.d
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Directory /etc/profile.d is in the correct state
May  9 23:15:24 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/profile.d] at time 23:15:24.749395 duration_in_ms=2.512
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/apt.conf.d/99prefer_ipv4-salt] at time 23:15:25.268285
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/apt/apt.conf.d/99prefer_ipv4-salt
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/apt.conf'
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:25 cmp02 salt-minion[2964]: New file
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/apt.conf.d/99prefer_ipv4-salt] at time 23:15:25.317944 duration_in_ms=49.66
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Running state [linux_repo_prereq_pkgs] at time 23:15:25.318486
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Executing state pkg.installed for linux_repo_prereq_pkgs
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] All specified packages are already installed
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Completed state [linux_repo_prereq_pkgs] at time 23:15:25.703814 duration_in_ms=385.328
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/apt.conf.d/99proxies-salt-mk_openstack] at time 23:15:25.705551
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/apt.conf.d/99proxies-salt-mk_openstack
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/apt.conf.d/99proxies-salt-mk_openstack is not present
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/apt.conf.d/99proxies-salt-mk_openstack] at time 23:15:25.706552 duration_in_ms=1.002
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/preferences.d/mk_openstack] at time 23:15:25.707380
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/apt/preferences.d/mk_openstack
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/preferences_repo'
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:25 cmp02 salt-minion[2964]: New file
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/preferences.d/mk_openstack] at time 23:15:25.827019 duration_in_ms=119.637
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Running state [deb [arch=amd64] http://apt.mirantis.com/xenial/ nightly pike] at time 23:15:25.831625
May  9 23:15:25 cmp02 salt-minion[2964]: [INFO    ] Executing state pkgrepo.managed for deb [arch=amd64] http://apt.mirantis.com/xenial/ nightly pike
May  9 23:15:26 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-key', 'add', '/var/cache/salt/minion/extrn_files/base/apt.mirantis.com/public.gpg'] in directory '/root'
May  9 23:15:26 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:15:29 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231529831468
May  9 23:15:29 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 3562
May  9 23:15:29 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231529831468
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] {'repo': 'deb [arch=amd64] http://apt.mirantis.com/xenial nightly pike'}
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Completed state [deb [arch=amd64] http://apt.mirantis.com/xenial/ nightly pike] at time 23:15:30.910147 duration_in_ms=5078.521
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/apt.conf.d/99proxies-salt-uca-staging] at time 23:15:30.910706
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/apt.conf.d/99proxies-salt-uca-staging
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/apt.conf.d/99proxies-salt-uca-staging is not present
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/apt.conf.d/99proxies-salt-uca-staging] at time 23:15:30.912261 duration_in_ms=1.555
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/preferences.d/uca-staging] at time 23:15:30.912690
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/preferences.d/uca-staging
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/preferences.d/uca-staging is not present
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/preferences.d/uca-staging] at time 23:15:30.913990 duration_in_ms=1.3
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Running state [deb http://ppa.launchpad.net/ubuntu-cloud-archive/pike-staging/ubuntu xenial main] at time 23:15:30.915204
May  9 23:15:30 cmp02 salt-minion[2964]: [INFO    ] Executing state pkgrepo.managed for deb http://ppa.launchpad.net/ubuntu-cloud-archive/pike-staging/ubuntu xenial main
May  9 23:15:31 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-key', 'export', '9F68104E'] in directory '/root'
May  9 23:15:31 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-key', 'adv', '--keyserver', 'keyserver.ubuntu.com', '--logger-fd', '1', '--recv-keys', '9F68104E'] in directory '/root'
May  9 23:15:31 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] {'repo': 'deb http://ppa.launchpad.net/ubuntu-cloud-archive/pike-staging/ubuntu xenial main'}
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] Completed state [deb http://ppa.launchpad.net/ubuntu-cloud-archive/pike-staging/ubuntu xenial main] at time 23:15:35.908420 duration_in_ms=4993.215
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/apt.conf.d/99proxies-salt-mirantis_openstack] at time 23:15:35.908946
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/apt.conf.d/99proxies-salt-mirantis_openstack
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/apt.conf.d/99proxies-salt-mirantis_openstack is not present
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/apt.conf.d/99proxies-salt-mirantis_openstack] at time 23:15:35.910440 duration_in_ms=1.493
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/preferences.d/mirantis_openstack] at time 23:15:35.910885
May  9 23:15:35 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/apt/preferences.d/mirantis_openstack
May  9 23:15:36 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:36 cmp02 salt-minion[2964]: New file
May  9 23:15:36 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/preferences.d/mirantis_openstack] at time 23:15:36.029695 duration_in_ms=118.81
May  9 23:15:36 cmp02 salt-minion[2964]: [INFO    ] Running state [deb http://mirror.fuel-infra.org/mcp-repos/pike/xenial pike main] at time 23:15:36.030581
May  9 23:15:36 cmp02 salt-minion[2964]: [INFO    ] Executing state pkgrepo.managed for deb http://mirror.fuel-infra.org/mcp-repos/pike/xenial pike main
May  9 23:15:36 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-key', 'add', '/var/cache/salt/minion/extrn_files/base/mirror.fuel-infra.org/mcp-repos/pike/xenial/archive-mcppike.key'] in directory '/root'
May  9 23:15:36 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:15:39 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231539867254
May  9 23:15:39 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 4615
May  9 23:15:39 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231539867254
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] {'repo': 'deb http://mirror.fuel-infra.org/mcp-repos/pike/xenial pike main'}
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Completed state [deb http://mirror.fuel-infra.org/mcp-repos/pike/xenial pike main] at time 23:15:41.068959 duration_in_ms=5038.376
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/apt.conf.d/99proxies-salt-uca] at time 23:15:41.069489
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/apt.conf.d/99proxies-salt-uca
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/apt.conf.d/99proxies-salt-uca is not present
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/apt.conf.d/99proxies-salt-uca] at time 23:15:41.071018 duration_in_ms=1.529
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/preferences.d/uca] at time 23:15:41.071479
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/preferences.d/uca
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/preferences.d/uca is not present
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/preferences.d/uca] at time 23:15:41.072774 duration_in_ms=1.295
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Running state [deb http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike main] at time 23:15:41.073930
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Executing state pkgrepo.managed for deb http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike main
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-key', 'export', 'EC4926EA'] in directory '/root'
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-key', 'adv', '--keyserver', 'keyserver.ubuntu.com', '--logger-fd', '1', '--recv-keys', 'EC4926EA'] in directory '/root'
May  9 23:15:41 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'repo': 'deb http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike main'}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [deb http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/pike main] at time 23:15:46.124968 duration_in_ms=5051.038
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [UTC] at time 23:15:46.126426
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state timezone.system for UTC
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command ['timedatectl'] in directory '/root'
May  9 23:15:46 cmp02 dbus[1236]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service'
May  9 23:15:46 cmp02 systemd[1]: Starting Time & Date Service...
May  9 23:15:46 cmp02 dbus[1236]: [system] Successfully activated service 'org.freedesktop.timedate1'
May  9 23:15:46 cmp02 systemd[1]: Started Time & Date Service.
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command ['timedatectl'] in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'timedatectl set-timezone UTC' in directory '/root'
May  9 23:15:46 cmp02 systemd-timedated[5240]: Changed time zone to 'UTC'.
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'timezone': 'UTC'}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [UTC] at time 23:15:46.202108 duration_in_ms=75.681
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [nf_conntrack] at time 23:15:46.203967
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state kmod.present for nf_conntrack
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'lsmod' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'lsmod' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'modprobe nf_conntrack' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'lsmod' in directory '/root'
May  9 23:15:46 cmp02 kernel: [  350.456976] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'nf_conntrack': 'loaded'}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [nf_conntrack] at time 23:15:46.757856 duration_in_ms=553.889
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_keepalive_probes] at time 23:15:46.759295
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_keepalive_probes
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:46 cmp02 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 5263 (sysctl)
May  9 23:15:46 cmp02 systemd[1]: Mounting Arbitrary Executable File Formats File System...
May  9 23:15:46 cmp02 systemd[1]: Mounted Arbitrary Executable File Formats File System.
May  9 23:15:46 cmp02 kernel: [  350.589928] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.589929] use_ibrs = 0, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.589930] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589931] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589931] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589932] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589932] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589934] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.589935] use_ibrs = 0, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.589935] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589936] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589937] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589937] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.589938] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.612942] nr_pdflush_threads exported in /proc is scheduled for removal
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_keepalive_probes="8"' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_keepalive_probes': 8}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_keepalive_probes] at time 23:15:46.836425 duration_in_ms=77.129
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [fs.file-max] at time 23:15:46.836753
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for fs.file-max
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:46 cmp02 kernel: [  350.642545] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.642547] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.642548] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642549] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642549] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642550] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642550] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642552] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.642553] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.642554] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642554] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642555] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642556] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.642556] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w fs.file-max="124165"' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'fs.file-max': 124165}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [fs.file-max] at time 23:15:46.884030 duration_in_ms=47.277
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [net.core.somaxconn] at time 23:15:46.884346
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.core.somaxconn
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:46 cmp02 kernel: [  350.689177] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.689178] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.689179] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689180] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689180] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689181] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689181] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689183] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.689184] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.689184] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689185] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689185] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689186] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.689187] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.core.somaxconn="4096"' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'net.core.somaxconn': 4096}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.core.somaxconn] at time 23:15:46.926922 duration_in_ms=42.576
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_max_syn_backlog] at time 23:15:46.927223
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_max_syn_backlog
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:46 cmp02 kernel: [  350.730524] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.730526] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.730526] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730527] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730528] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730528] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730529] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730530] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.730531] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.730532] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730532] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730533] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730533] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.730534] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_max_syn_backlog="8192"' in directory '/root'
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_max_syn_backlog': 8192}
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_max_syn_backlog] at time 23:15:46.970019 duration_in_ms=42.796
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Running state [vm.dirty_background_ratio] at time 23:15:46.970318
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for vm.dirty_background_ratio
May  9 23:15:46 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:46 cmp02 kernel: [  350.775129] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.775130] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.775131] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775132] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775132] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775133] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775134] read cpu 4 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775135] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:46 cmp02 kernel: [  350.775136] use_ibrs = 4, use_ibpb = 4
May  9 23:15:46 cmp02 kernel: [  350.775137] read cpu 0 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775137] read cpu 1 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775138] read cpu 2 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775138] read cpu 3 ibrs val 0
May  9 23:15:46 cmp02 kernel: [  350.775139] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w vm.dirty_background_ratio="5"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'vm.dirty_background_ratio': 5}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [vm.dirty_background_ratio] at time 23:15:47.017324 duration_in_ms=47.005
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_congestion_control] at time 23:15:47.017809
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_congestion_control
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  350.824746] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.824748] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.824748] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824749] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824750] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824750] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824751] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824753] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.824753] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.824754] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824754] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824755] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824756] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.824756] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_congestion_control="yeah"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_congestion_control': 'yeah'}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_congestion_control] at time 23:15:47.072401 duration_in_ms=54.592
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [vm.dirty_ratio] at time 23:15:47.072713
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for vm.dirty_ratio
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  350.878936] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.878938] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.878938] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878939] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878939] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878940] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878941] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878942] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.878943] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.878943] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878944] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878945] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878945] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.878946] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w vm.dirty_ratio="10"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'vm.dirty_ratio': 10}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [vm.dirty_ratio] at time 23:15:47.125227 duration_in_ms=52.513
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.nf_conntrack_max] at time 23:15:47.125555
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.nf_conntrack_max
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  350.931278] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.931279] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.931280] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931281] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931281] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931282] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931282] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931284] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.931285] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.931285] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931286] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931287] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931287] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.931288] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.nf_conntrack_max="1048576"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.nf_conntrack_max': 1048576}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.nf_conntrack_max] at time 23:15:47.174851 duration_in_ms=49.296
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_tw_reuse] at time 23:15:47.175181
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_tw_reuse
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  350.980367] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.980369] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.980369] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980370] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980370] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980371] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980372] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980373] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  350.980374] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  350.980374] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980375] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980376] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980376] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  350.980377] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_tw_reuse="1"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_tw_reuse': 1}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_tw_reuse] at time 23:15:47.223040 duration_in_ms=47.859
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_retries2] at time 23:15:47.223357
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_retries2
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.027745] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.027747] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.027747] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027748] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027748] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027749] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027750] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027751] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.027752] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.027753] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027753] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027754] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027754] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.027755] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_retries2="5"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_retries2': 5}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_retries2] at time 23:15:47.266656 duration_in_ms=43.298
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.core.netdev_max_backlog] at time 23:15:47.268373
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.core.netdev_max_backlog
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.073688] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.073690] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.073691] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073692] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073692] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073693] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073694] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073696] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.073697] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.073698] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073699] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073699] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073700] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.073701] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.core.netdev_max_backlog="261144"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.core.netdev_max_backlog': 261144}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.core.netdev_max_backlog] at time 23:15:47.317805 duration_in_ms=49.432
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_slow_start_after_idle] at time 23:15:47.318098
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_slow_start_after_idle
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.122347] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.122349] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.122349] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122350] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122351] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122351] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122352] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122353] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.122354] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.122355] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122355] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122356] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122356] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.122357] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_slow_start_after_idle="0"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_slow_start_after_idle': 0}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_slow_start_after_idle] at time 23:15:47.368756 duration_in_ms=50.657
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [vm.swappiness] at time 23:15:47.369070
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for vm.swappiness
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.175364] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.175366] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.175367] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175368] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175368] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175369] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175370] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175372] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.175373] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.175373] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175374] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175375] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175375] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.175376] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w vm.swappiness="10"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'vm.swappiness': 10}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [vm.swappiness] at time 23:15:47.424519 duration_in_ms=55.448
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_keepalive_intvl] at time 23:15:47.424943
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_keepalive_intvl
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.229589] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.229590] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.229591] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229591] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229592] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229592] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229593] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229595] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.229595] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.229596] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229597] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229597] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229598] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.229599] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_keepalive_intvl="3"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_keepalive_intvl': 3}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_keepalive_intvl] at time 23:15:47.470350 duration_in_ms=45.407
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.neigh.default.gc_thresh1] at time 23:15:47.470649
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.neigh.default.gc_thresh1
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.279593] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.279594] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.279595] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279596] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279597] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279597] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279598] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279600] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.279601] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.279602] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279602] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279603] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279604] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.279604] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.neigh.default.gc_thresh1="4096"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.neigh.default.gc_thresh1': 4096}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.neigh.default.gc_thresh1] at time 23:15:47.528576 duration_in_ms=57.926
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.neigh.default.gc_thresh2] at time 23:15:47.528945
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.neigh.default.gc_thresh2
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.334402] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.334403] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.334404] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334405] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334405] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334406] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334406] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334408] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.334409] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.334409] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334410] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334410] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334411] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.334412] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.neigh.default.gc_thresh2="8192"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.neigh.default.gc_thresh2': 8192}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.neigh.default.gc_thresh2] at time 23:15:47.574058 duration_in_ms=45.113
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.neigh.default.gc_thresh3] at time 23:15:47.574373
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.neigh.default.gc_thresh3
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.384084] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.384086] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.384087] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384087] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384088] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384088] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384089] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384091] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.384091] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.384092] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384092] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384093] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384094] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.384094] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.neigh.default.gc_thresh3="16384"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.neigh.default.gc_thresh3': 16384}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.neigh.default.gc_thresh3] at time 23:15:47.624375 duration_in_ms=50.002
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_fin_timeout] at time 23:15:47.624685
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_fin_timeout
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.429049] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.429051] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.429051] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429052] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429053] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429053] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429054] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429056] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.429056] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.429057] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429057] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429058] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429058] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.429059] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_fin_timeout="30"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_fin_timeout': 30}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_fin_timeout] at time 23:15:47.672439 duration_in_ms=47.753
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [net.ipv4.tcp_keepalive_time] at time 23:15:47.672756
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for net.ipv4.tcp_keepalive_time
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.476515] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.476516] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.476517] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476518] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476518] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476519] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476520] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476521] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.476522] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.476523] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476523] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476524] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476524] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.476525] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w net.ipv4.tcp_keepalive_time="30"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'net.ipv4.tcp_keepalive_time': 30}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [net.ipv4.tcp_keepalive_time] at time 23:15:47.718318 duration_in_ms=45.562
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [kernel.panic] at time 23:15:47.720048
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state sysctl.present for kernel.panic
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -a' in directory '/root'
May  9 23:15:47 cmp02 kernel: [  351.525721] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.525723] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.525724] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525724] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525725] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525725] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525726] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525728] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
May  9 23:15:47 cmp02 kernel: [  351.525728] use_ibrs = 4, use_ibpb = 4
May  9 23:15:47 cmp02 kernel: [  351.525729] read cpu 0 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525729] read cpu 1 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525730] read cpu 2 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525731] read cpu 3 ibrs val 0
May  9 23:15:47 cmp02 kernel: [  351.525731] read cpu 4 ibrs val 0
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command 'sysctl -w kernel.panic="60"' in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] {'kernel.panic': 60}
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Completed state [kernel.panic] at time 23:15:47.770316 duration_in_ms=50.268
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Running state [linux_sysfs_package] at time 23:15:47.770635
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing state pkg.installed for linux_sysfs_package
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'sysfsutils'] in directory '/root'
May  9 23:15:47 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:15:49 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231549950592
May  9 23:15:49 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 5740
May  9 23:15:49 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231549950592
May  9 23:15:50 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:15:50 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'sysfsutils'] in directory '/root'
May  9 23:15:50 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install sysfsutils.
May  9 23:15:51 cmp02 systemd[1]: Reloading.
May  9 23:15:52 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:53 cmp02 systemd[1]: Reloading.
May  9 23:15:53 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:53 cmp02 systemd[1]: Reloading.
May  9 23:15:53 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:53 cmp02 systemd[1]: Starting LSB: Set sysfs variables from /etc/sysfs.conf...
May  9 23:15:53 cmp02 sysfsutils[6078]:  * Setting sysfs variables...
May  9 23:15:53 cmp02 sysfsutils[6078]:    ...done.
May  9 23:15:53 cmp02 systemd[1]: Started LSB: Set sysfs variables from /etc/sysfs.conf.
May  9 23:15:53 cmp02 systemd[1]: Reloading.
May  9 23:15:54 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Made the following changes:
May  9 23:15:55 cmp02 salt-minion[2964]: 'libsysfs2' changed from 'absent' to '2.1.0+repack-4'
May  9 23:15:55 cmp02 salt-minion[2964]: 'sysfsutils' changed from 'absent' to '2.1.0+repack-4'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Loading fresh modules for state activity
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Completed state [linux_sysfs_package] at time 23:15:55.380234 duration_in_ms=7609.599
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/sysfs.d] at time 23:15:55.385034
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing state file.directory for /etc/sysfs.d
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Directory /etc/sysfs.d is in the correct state
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/sysfs.d] at time 23:15:55.390264 duration_in_ms=5.23
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Running state [ondemand] at time 23:15:55.766015
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing state service.dead for ondemand
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'status', 'ondemand.service', '-n', '0'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'ondemand.service'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ondemand.service'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'stop', 'ondemand.service'] in directory '/root'
May  9 23:15:55 cmp02 systemd[1]: Started /bin/systemctl stop ondemand.service.
May  9 23:15:55 cmp02 systemd[1]: Stopping LSB: Set the CPU Frequency Scaling governor to "ondemand"...
May  9 23:15:55 cmp02 systemd[1]: Stopped LSB: Set the CPU Frequency Scaling governor to "ondemand".
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'ondemand.service'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ondemand.service'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ondemand.service'] in directory '/root'
May  9 23:15:55 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', '/usr/sbin/update-rc.d', '-f', 'ondemand', 'remove'] in directory '/root'
May  9 23:15:55 cmp02 systemd[1]: Started /usr/sbin/update-rc.d -f ondemand remove.
May  9 23:15:56 cmp02 systemd[1]: Reloading.
May  9 23:15:56 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ondemand.service'] in directory '/root'
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing command 'runlevel' in directory '/root'
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] {'ondemand': True}
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Completed state [ondemand] at time 23:15:56.137325 duration_in_ms=371.31
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Running state [cs_CZ.UTF-8] at time 23:15:56.139882
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing state locale.present for cs_CZ.UTF-8
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing command 'locale -a' in directory '/root'
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing command ['locale-gen', 'cs_CZ.utf8'] in directory '/root'
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] {'locale': 'cs_CZ.UTF-8'}
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Completed state [cs_CZ.UTF-8] at time 23:15:56.981352 duration_in_ms=841.469
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Running state [en_US.UTF-8] at time 23:15:56.982505
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing state locale.present for en_US.UTF-8
May  9 23:15:56 cmp02 salt-minion[2964]: [INFO    ] Executing command 'locale -a' in directory '/root'
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Locale en_US.UTF-8 is already present
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [en_US.UTF-8] at time 23:15:57.004652 duration_in_ms=22.148
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [en_US.UTF-8] at time 23:15:57.006878
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state locale.system for en_US.UTF-8
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing command 'localectl' in directory '/root'
May  9 23:15:57 cmp02 dbus[1236]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
May  9 23:15:57 cmp02 systemd[1]: Starting Locale Service...
May  9 23:15:57 cmp02 dbus[1236]: [system] Successfully activated service 'org.freedesktop.locale1'
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] System locale en_US.UTF-8 already set
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [en_US.UTF-8] at time 23:15:57.062046 duration_in_ms=55.168
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [root] at time 23:15:57.064063
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state group.present for root
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Group root is present and up to date
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [root] at time 23:15:57.065000 duration_in_ms=0.937
May  9 23:15:57 cmp02 systemd[1]: Started Locale Service.
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [root] at time 23:15:57.067926
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state user.present for root
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] User root is present and up to date
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [root] at time 23:15:57.070214 duration_in_ms=2.289
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [/root] at time 23:15:57.073736
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state file.directory for /root
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Directory /root is in the correct state
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [/root] at time 23:15:57.075806 duration_in_ms=2.07
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/sudoers.d/90-salt-user-root] at time 23:15:57.076176
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/sudoers.d/90-salt-user-root
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] File /etc/sudoers.d/90-salt-user-root is not present
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/sudoers.d/90-salt-user-root] at time 23:15:57.077339 duration_in_ms=1.164
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/security/limits.d/90-salt-default.conf] at time 23:15:57.077707
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/security/limits.d/90-salt-default.conf
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/limits.conf'
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:57 cmp02 salt-minion[2964]: New file
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/security/limits.d/90-salt-default.conf] at time 23:15:57.206099 duration_in_ms=128.391
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/systemd/system.conf.d/90-salt.conf] at time 23:15:57.206326
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/systemd/system.conf.d/90-salt.conf
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/systemd.conf'
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:57 cmp02 salt-minion[2964]: New file
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/systemd/system.conf.d/90-salt.conf] at time 23:15:57.328401 duration_in_ms=122.075
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [service.systemctl_reload] at time 23:15:57.330747
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state module.wait for service.systemctl_reload
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] No changes made for service.systemctl_reload
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [service.systemctl_reload] at time 23:15:57.332599 duration_in_ms=1.852
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [service.systemctl_reload] at time 23:15:57.333007
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state module.mod_watch for service.systemctl_reload
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', '--system', 'daemon-reload'] in directory '/root'
May  9 23:15:57 cmp02 systemd[1]: Reloading.
May  9 23:15:57 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] {'ret': True}
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [service.systemctl_reload] at time 23:15:57.441638 duration_in_ms=108.631
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [linux_lvm_pkgs] at time 23:15:57.446447
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state pkg.installed for linux_lvm_pkgs
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] All specified packages are already installed
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Completed state [linux_lvm_pkgs] at time 23:15:57.504833 duration_in_ms=58.386
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/lvm/lvm.conf] at time 23:15:57.505674
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/lvm/lvm.conf
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/lvm.conf'
May  9 23:15:57 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:15:57 cmp02 salt-minion[2964]: ---
May  9 23:15:57 cmp02 salt-minion[2964]: +++
May  9 23:15:57 cmp02 salt-minion[2964]: @@ -1,3 +1,4 @@
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]:  # This is an example configuration file for the LVM2 system.
May  9 23:15:57 cmp02 salt-minion[2964]:  # It contains the default settings that would be used if there was no
May  9 23:15:57 cmp02 salt-minion[2964]:  # /etc/lvm/lvm.conf file.
May  9 23:15:57 cmp02 salt-minion[2964]: @@ -26,506 +27,509 @@
May  9 23:15:57 cmp02 salt-minion[2964]:  # How LVM configuration settings are handled.
May  9 23:15:57 cmp02 salt-minion[2964]:  config {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option config/checks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If enabled, any LVM configuration mismatch is reported.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This implies checking that the configuration key is understood by
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM and that the value of the key is the proper type. If disabled,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# any configuration mismatch is ignored and the default value is used
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# without any warning (a message about the configuration key not being
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# found is issued in verbose mode only).
May  9 23:15:57 cmp02 salt-minion[2964]: -#011checks = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option config/abort_on_errors.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Abort the LVM process if a configuration mismatch is found.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011abort_on_errors = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option config/profile_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Directory where LVM looks for configuration profiles.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011profile_dir = "/etc/lvm/profile"
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option config/checks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If enabled, any LVM configuration mismatch is reported.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This implies checking that the configuration key is understood by
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVM and that the value of the key is the proper type. If disabled,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # any configuration mismatch is ignored and the default value is used
May  9 23:15:57 cmp02 salt-minion[2964]: +        # without any warning (a message about the configuration key not being
May  9 23:15:57 cmp02 salt-minion[2964]: +        # found is issued in verbose mode only).
May  9 23:15:57 cmp02 salt-minion[2964]: +        checks = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option config/abort_on_errors.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Abort the LVM process if a configuration mismatch is found.
May  9 23:15:57 cmp02 salt-minion[2964]: +        abort_on_errors = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option config/profile_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Directory where LVM looks for configuration profiles.
May  9 23:15:57 cmp02 salt-minion[2964]: +        profile_dir = "/etc/lvm/profile"
May  9 23:15:57 cmp02 salt-minion[2964]:  }
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]:  # Configuration section devices.
May  9 23:15:57 cmp02 salt-minion[2964]:  # How LVM uses block devices.
May  9 23:15:57 cmp02 salt-minion[2964]:  devices {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Directory in which to create volume group device nodes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Commands also accept this as a prefix on volume group names.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011dir = "/dev"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/scan.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Directories containing device nodes to use with LVM.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011scan = [ "/dev" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/obtain_device_list_from_udev.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Obtain the list of available devices from udev.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This avoids opening or using any inapplicable non-block devices or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# subdirectories found in the udev directory. Any device node or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# symlink not managed by udev in the udev directory is ignored. This
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# setting applies only to the udev-managed device directory; other
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# directories will be scanned fully. LVM needs to be compiled with
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# udev support for this setting to apply.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011obtain_device_list_from_udev = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/external_device_info_source.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Select an external device information source.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Some information may already be available in the system and LVM can
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# use this information to determine the exact type or use of devices it
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# processes. Using an existing external device information source can
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# speed up device processing as LVM does not need to run its own native
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# routines to acquire this information. For example, this information
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is used to drive LVM filtering like MD component detection, multipath
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# component detection, partition detection and others.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   none
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     No external device information source is used.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   udev
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Reuse existing udev database records. Applicable only if LVM is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     compiled with udev support.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011external_device_info_source = "none"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/preferred_names.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Select which path name to display for a block device.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If multiple path names exist for a block device, and LVM needs to
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# display a name for the device, the path names are matched against
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# each item in this list of regular expressions. The first match is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# used. Try to avoid using undescriptive /dev/dm-N names, if present.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If no preferred name matches, or if preferred_names are not defined,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the following built-in preferences are applied in order until one
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# produces a preferred name:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Prefer names with path prefixes in the order of:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# /dev/mapper, /dev/disk, /dev/dm-*, /dev/block.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Prefer the name with the least number of slashes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Prefer a name that is a symlink.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Prefer the path with least value in lexicographical order.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/filter.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Limit the block devices that are used by LVM commands.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This is a list of regular expressions used to accept or reject block
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# device path names. Each regex is delimited by a vertical bar '|'
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (or any character) and is preceded by 'a' to accept the path, or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# by 'r' to reject the path. The first regex in the list to match the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# path is used, producing the 'a' or 'r' result for the device.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When multiple path names exist for a block device, if any path name
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# matches an 'a' pattern before an 'r' pattern, then the device is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# accepted. If all the path names match an 'r' pattern first, then the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# device is rejected. Unmatching path names do not affect the accept
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# or reject decision. If no path names for a device match a pattern,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# then the device is accepted. Be careful mixing 'a' and 'r' patterns,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# as the combination might produce unexpected results (test changes.)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Run vgscan after changing the filter to regenerate the cache.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# See the use_lvmetad comment for a special case regarding filters.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accept every block device:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filter = [ "a|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Reject the cdrom drive:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filter = [ "r|/dev/cdrom|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Work with just loopback devices, e.g. for testing:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filter = [ "a|loop|", "r|.*|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accept all loop devices and ide drives except hdc:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use anchors to be very specific:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filter = [ "a|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/global_filter.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Limit the block devices that are used by LVM system components.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Because devices/filter may be overridden from the command line, it is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# not suitable for system-wide device filtering, e.g. udev and lvmetad.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use global_filter to hide devices from these LVM system components.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The syntax is the same as devices/filter. Devices rejected by
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# global_filter are not opened by LVM.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# global_filter = [ "a|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/cache_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Directory in which to store the device cache file.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The results of filtering are cached on disk to avoid rescanning dud
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# devices (which can take a very long time). By default this cache is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# stored in a file named .cache. It is safe to delete this file; the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# tools regenerate it. If obtain_device_list_from_udev is enabled, the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# list of devices is obtained from udev and any existing .cache file
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is removed.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011cache_dir = "/run/lvm"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/cache_file_prefix.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# A prefix used before the .cache file name. See devices/cache_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011cache_file_prefix = ""
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/write_cache_state.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Enable/disable writing the cache file. See devices/cache_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011write_cache_state = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/types.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# List of additional acceptable block device types.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# These are of device type names from /proc/devices, followed by the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# maximum number of partitions.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# types = [ "fd", 16 ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/sysfs_scan.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Restrict device scanning to block devices appearing in sysfs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This is a quick way of filtering out block devices that are not
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# present on the system. sysfs must be part of the kernel and mounted.)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011sysfs_scan = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/multipath_component_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Ignore devices that are components of DM multipath devices.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011multipath_component_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/md_component_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Ignore devices that are components of software RAID (md) devices.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011md_component_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/fw_raid_component_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Ignore devices that are components of firmware RAID devices.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM must use an external_device_info_source other than none for this
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# detection to execute.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011fw_raid_component_detection = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/md_chunk_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Align PV data blocks with md device's stripe-width.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This applies if a PV is placed directly on an md device.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011md_chunk_alignment = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/default_data_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Default alignment of the start of a PV data area in MB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If set to 0, a value of 64KiB will be used.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Set to 1 for 1MiB, 2 for 2MiB, etc.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# default_data_alignment = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/data_alignment_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Detect PV data alignment based on sysfs device information.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The start of a PV data area will be a multiple of minimum_io_size or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# optimal_io_size exposed in sysfs. minimum_io_size is the smallest
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# request the device can perform without incurring a read-modify-write
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# penalty, e.g. MD chunk size. optimal_io_size is the device's
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# preferred unit of receiving I/O, e.g. MD stripe width.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# minimum_io_size is used if optimal_io_size is undefined (0).
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If md_chunk_alignment is enabled, that detects the optimal_io_size.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This setting takes precedence over md_chunk_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011data_alignment_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/data_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Alignment of the start of a PV data area in KiB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If a PV is placed directly on an md device and md_chunk_alignment or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# data_alignment_detection are enabled, then this setting is ignored.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Otherwise, md_chunk_alignment and data_alignment_detection are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# disabled if this is set. Set to 0 to use the default alignment or the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# page size, if larger.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011data_alignment = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/data_alignment_offset_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Detect PV data alignment offset based on sysfs device information.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The start of a PV aligned data area will be shifted by the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# alignment_offset exposed in sysfs. This offset is often 0, but may
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# be non-zero. Certain 4KiB sector drives that compensate for windows
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# partitioning will have an alignment_offset of 3584 bytes (sector 7
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is the lowest aligned logical block, the 4KiB sectors start at
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LBA -1, and consequently sector 63 is aligned on a 4KiB boundary).
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# pvcreate --dataalignmentoffset will skip this detection.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011data_alignment_offset_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/ignore_suspended_devices.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Ignore DM devices that have I/O suspended while scanning devices.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Otherwise, LVM waits for a suspended device to become accessible.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This should only be needed in recovery situations.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011ignore_suspended_devices = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/ignore_lvm_mirrors.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Do not scan 'mirror' LVs to avoid possible deadlocks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This avoids possible deadlocks when using the 'mirror' segment type.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This setting determines whether LVs using the 'mirror' segment type
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# are scanned for LVM labels. This affects the ability of mirrors to
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# be used as physical volumes. If this setting is enabled, it is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# impossible to create VGs on top of mirror LVs, i.e. to stack VGs on
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# mirror LVs. If this setting is disabled, allowing mirror LVs to be
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# scanned, it may cause LVM processes and I/O to the mirror to become
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# blocked. This is due to the way that the mirror segment type handles
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# failures. In order for the hang to occur, an LVM command must be run
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# just after a failure and before the automatic LVM repair process
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# takes place, or there must be failures in multiple mirrors in the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# same VG at the same time with write failures occurring moments before
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# a scan of the mirror's labels. The 'mirror' scanning problems do not
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# apply to LVM RAID types like 'raid1' which handle failures in a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# different way, making them a better choice for VG stacking.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011ignore_lvm_mirrors = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/disable_after_error_count.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Number of I/O errors after which a device is skipped.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# During each LVM operation, errors received from each device are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# counted. If the counter of a device exceeds the limit set here,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# no further I/O is sent to that device for the remainder of the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# operation. Setting this to 0 disables the counters altogether.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011disable_after_error_count = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/require_restorefile_with_uuid.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Allow use of pvcreate --uuid without requiring --restorefile.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011require_restorefile_with_uuid = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/pv_min_size.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Minimum size in KiB of block devices which can be used as PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# In a clustered environment all nodes must use the same value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Any value smaller than 512KiB is ignored. The previous built-in
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# value was 512.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011pv_min_size = 2048
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option devices/issue_discards.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Issue discards to PVs that are no longer used by an LV.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Discards are sent to an LV's underlying physical volumes when the LV
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is no longer using the physical volumes' space, e.g. lvremove,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# lvreduce. Discards inform the storage that a region is no longer
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# used. Storage that supports discards advertise the protocol-specific
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# way discards should be issued by the kernel (TRIM, UNMAP, or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# WRITE SAME with UNMAP bit set). Not all storage will support or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# benefit from discards, but SSDs and thinly provisioned LUNs
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# generally do. If enabled, discards will only be issued if both the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# storage and kernel provide support.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011issue_discards = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Directory in which to create volume group device nodes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Commands also accept this as a prefix on volume group names.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: +        dir = "/dev"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/scan.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Directories containing device nodes to use with LVM.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: +        scan = [ "/dev" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/obtain_device_list_from_udev.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Obtain the list of available devices from udev.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This avoids opening or using any inapplicable non-block devices or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # subdirectories found in the udev directory. Any device node or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # symlink not managed by udev in the udev directory is ignored. This
May  9 23:15:57 cmp02 salt-minion[2964]: +        # setting applies only to the udev-managed device directory; other
May  9 23:15:57 cmp02 salt-minion[2964]: +        # directories will be scanned fully. LVM needs to be compiled with
May  9 23:15:57 cmp02 salt-minion[2964]: +        # udev support for this setting to apply.
May  9 23:15:57 cmp02 salt-minion[2964]: +        obtain_device_list_from_udev = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/external_device_info_source.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Select an external device information source.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Some information may already be available in the system and LVM can
May  9 23:15:57 cmp02 salt-minion[2964]: +        # use this information to determine the exact type or use of devices it
May  9 23:15:57 cmp02 salt-minion[2964]: +        # processes. Using an existing external device information source can
May  9 23:15:57 cmp02 salt-minion[2964]: +        # speed up device processing as LVM does not need to run its own native
May  9 23:15:57 cmp02 salt-minion[2964]: +        # routines to acquire this information. For example, this information
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is used to drive LVM filtering like MD component detection, multipath
May  9 23:15:57 cmp02 salt-minion[2964]: +        # component detection, partition detection and others.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   none
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     No external device information source is used.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   udev
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     Reuse existing udev database records. Applicable only if LVM is
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     compiled with udev support.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        external_device_info_source = "none"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/preferred_names.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Select which path name to display for a block device.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If multiple path names exist for a block device, and LVM needs to
May  9 23:15:57 cmp02 salt-minion[2964]: +        # display a name for the device, the path names are matched against
May  9 23:15:57 cmp02 salt-minion[2964]: +        # each item in this list of regular expressions. The first match is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # used. Try to avoid using undescriptive /dev/dm-N names, if present.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If no preferred name matches, or if preferred_names are not defined,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # the following built-in preferences are applied in order until one
May  9 23:15:57 cmp02 salt-minion[2964]: +        # produces a preferred name:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Prefer names with path prefixes in the order of:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # /dev/mapper, /dev/disk, /dev/dm-*, /dev/block.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Prefer the name with the least number of slashes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Prefer a name that is a symlink.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Prefer the path with least value in lexicographical order.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:57 cmp02 salt-minion[2964]: +        # preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/filter.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Limit the block devices that are used by LVM commands.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This is a list of regular expressions used to accept or reject block
May  9 23:15:57 cmp02 salt-minion[2964]: +        # device path names. Each regex is delimited by a vertical bar '|'
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (or any character) and is preceded by 'a' to accept the path, or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # by 'r' to reject the path. The first regex in the list to match the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # path is used, producing the 'a' or 'r' result for the device.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When multiple path names exist for a block device, if any path name
May  9 23:15:57 cmp02 salt-minion[2964]: +        # matches an 'a' pattern before an 'r' pattern, then the device is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # accepted. If all the path names match an 'r' pattern first, then the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # device is rejected. Unmatching path names do not affect the accept
May  9 23:15:57 cmp02 salt-minion[2964]: +        # or reject decision. If no path names for a device match a pattern,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # then the device is accepted. Be careful mixing 'a' and 'r' patterns,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # as the combination might produce unexpected results (test changes.)
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Run vgscan after changing the filter to regenerate the cache.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # See the use_lvmetad comment for a special case regarding filters.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accept every block device:
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        filter = ["a|/dev/vdb*|", "r|.*|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filter = [ "a|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Reject the cdrom drive:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filter = [ "r|/dev/cdrom|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Work with just loopback devices, e.g. for testing:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filter = [ "a|loop|", "r|.*|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accept all loop devices and ide drives except hdc:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use anchors to be very specific:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filter = [ "a|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/global_filter.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Limit the block devices that are used by LVM system components.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Because devices/filter may be overridden from the command line, it is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # not suitable for system-wide device filtering, e.g. udev and lvmetad.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use global_filter to hide devices from these LVM system components.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The syntax is the same as devices/filter. Devices rejected by
May  9 23:15:57 cmp02 salt-minion[2964]: +        # global_filter are not opened by LVM.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # global_filter = [ "a|.*/|" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/cache_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Directory in which to store the device cache file.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The results of filtering are cached on disk to avoid rescanning dud
May  9 23:15:57 cmp02 salt-minion[2964]: +        # devices (which can take a very long time). By default this cache is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # stored in a file named .cache. It is safe to delete this file; the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # tools regenerate it. If obtain_device_list_from_udev is enabled, the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # list of devices is obtained from udev and any existing .cache file
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is removed.
May  9 23:15:57 cmp02 salt-minion[2964]: +        cache_dir = "/run/lvm"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/cache_file_prefix.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # A prefix used before the .cache file name. See devices/cache_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        cache_file_prefix = ""
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/write_cache_state.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Enable/disable writing the cache file. See devices/cache_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        write_cache_state = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/types.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # List of additional acceptable block device types.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # These are of device type names from /proc/devices, followed by the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # maximum number of partitions.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:57 cmp02 salt-minion[2964]: +        # types = [ "fd", 16 ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/sysfs_scan.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Restrict device scanning to block devices appearing in sysfs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This is a quick way of filtering out block devices that are not
May  9 23:15:57 cmp02 salt-minion[2964]: +        # present on the system. sysfs must be part of the kernel and mounted.)
May  9 23:15:57 cmp02 salt-minion[2964]: +        sysfs_scan = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/multipath_component_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Ignore devices that are components of DM multipath devices.
May  9 23:15:57 cmp02 salt-minion[2964]: +        multipath_component_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/md_component_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Ignore devices that are components of software RAID (md) devices.
May  9 23:15:57 cmp02 salt-minion[2964]: +        md_component_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/fw_raid_component_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Ignore devices that are components of firmware RAID devices.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVM must use an external_device_info_source other than none for this
May  9 23:15:57 cmp02 salt-minion[2964]: +        # detection to execute.
May  9 23:15:57 cmp02 salt-minion[2964]: +        fw_raid_component_detection = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/md_chunk_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Align PV data blocks with md device's stripe-width.
May  9 23:15:57 cmp02 systemd[1]: Started /bin/systemctl enable lvm2-lvmetad.service.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This applies if a PV is placed directly on an md device.
May  9 23:15:57 cmp02 salt-minion[2964]: +        md_chunk_alignment = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/default_data_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Default alignment of the start of a PV data area in MB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If set to 0, a value of 64KiB will be used.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Set to 1 for 1MiB, 2 for 2MiB, etc.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # default_data_alignment = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/data_alignment_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Detect PV data alignment based on sysfs device information.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The start of a PV data area will be a multiple of minimum_io_size or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # optimal_io_size exposed in sysfs. minimum_io_size is the smallest
May  9 23:15:57 cmp02 salt-minion[2964]: +        # request the device can perform without incurring a read-modify-write
May  9 23:15:57 cmp02 salt-minion[2964]: +        # penalty, e.g. MD chunk size. optimal_io_size is the device's
May  9 23:15:57 cmp02 salt-minion[2964]: +        # preferred unit of receiving I/O, e.g. MD stripe width.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # minimum_io_size is used if optimal_io_size is undefined (0).
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If md_chunk_alignment is enabled, that detects the optimal_io_size.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This setting takes precedence over md_chunk_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: +        data_alignment_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/data_alignment.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Alignment of the start of a PV data area in KiB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If a PV is placed directly on an md device and md_chunk_alignment or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # data_alignment_detection are enabled, then this setting is ignored.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Otherwise, md_chunk_alignment and data_alignment_detection are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # disabled if this is set. Set to 0 to use the default alignment or the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # page size, if larger.
May  9 23:15:57 cmp02 salt-minion[2964]: +        data_alignment = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/data_alignment_offset_detection.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Detect PV data alignment offset based on sysfs device information.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The start of a PV aligned data area will be shifted by the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # alignment_offset exposed in sysfs. This offset is often 0, but may
May  9 23:15:57 cmp02 salt-minion[2964]: +        # be non-zero. Certain 4KiB sector drives that compensate for windows
May  9 23:15:57 cmp02 salt-minion[2964]: +        # partitioning will have an alignment_offset of 3584 bytes (sector 7
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is the lowest aligned logical block, the 4KiB sectors start at
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LBA -1, and consequently sector 63 is aligned on a 4KiB boundary).
May  9 23:15:57 cmp02 salt-minion[2964]: +        # pvcreate --dataalignmentoffset will skip this detection.
May  9 23:15:57 cmp02 salt-minion[2964]: +        data_alignment_offset_detection = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/ignore_suspended_devices.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Ignore DM devices that have I/O suspended while scanning devices.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Otherwise, LVM waits for a suspended device to become accessible.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This should only be needed in recovery situations.
May  9 23:15:57 cmp02 salt-minion[2964]: +        ignore_suspended_devices = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/ignore_lvm_mirrors.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Do not scan 'mirror' LVs to avoid possible deadlocks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This avoids possible deadlocks when using the 'mirror' segment type.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This setting determines whether LVs using the 'mirror' segment type
May  9 23:15:57 cmp02 salt-minion[2964]: +        # are scanned for LVM labels. This affects the ability of mirrors to
May  9 23:15:57 cmp02 salt-minion[2964]: +        # be used as physical volumes. If this setting is enabled, it is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # impossible to create VGs on top of mirror LVs, i.e. to stack VGs on
May  9 23:15:57 cmp02 salt-minion[2964]: +        # mirror LVs. If this setting is disabled, allowing mirror LVs to be
May  9 23:15:57 cmp02 salt-minion[2964]: +        # scanned, it may cause LVM processes and I/O to the mirror to become
May  9 23:15:57 cmp02 salt-minion[2964]: +        # blocked. This is due to the way that the mirror segment type handles
May  9 23:15:57 cmp02 salt-minion[2964]: +        # failures. In order for the hang to occur, an LVM command must be run
May  9 23:15:57 cmp02 salt-minion[2964]: +        # just after a failure and before the automatic LVM repair process
May  9 23:15:57 cmp02 salt-minion[2964]: +        # takes place, or there must be failures in multiple mirrors in the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # same VG at the same time with write failures occurring moments before
May  9 23:15:57 cmp02 salt-minion[2964]: +        # a scan of the mirror's labels. The 'mirror' scanning problems do not
May  9 23:15:57 cmp02 salt-minion[2964]: +        # apply to LVM RAID types like 'raid1' which handle failures in a
May  9 23:15:57 cmp02 salt-minion[2964]: +        # different way, making them a better choice for VG stacking.
May  9 23:15:57 cmp02 salt-minion[2964]: +        ignore_lvm_mirrors = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/disable_after_error_count.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Number of I/O errors after which a device is skipped.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # During each LVM operation, errors received from each device are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # counted. If the counter of a device exceeds the limit set here,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # no further I/O is sent to that device for the remainder of the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # operation. Setting this to 0 disables the counters altogether.
May  9 23:15:57 cmp02 salt-minion[2964]: +        disable_after_error_count = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/require_restorefile_with_uuid.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Allow use of pvcreate --uuid without requiring --restorefile.
May  9 23:15:57 cmp02 salt-minion[2964]: +        require_restorefile_with_uuid = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/pv_min_size.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Minimum size in KiB of block devices which can be used as PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # In a clustered environment all nodes must use the same value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Any value smaller than 512KiB is ignored. The previous built-in
May  9 23:15:57 cmp02 salt-minion[2964]: +        # value was 512.
May  9 23:15:57 cmp02 salt-minion[2964]: +        pv_min_size = 2048
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option devices/issue_discards.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Issue discards to PVs that are no longer used by an LV.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Discards are sent to an LV's underlying physical volumes when the LV
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is no longer using the physical volumes' space, e.g. lvremove,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # lvreduce. Discards inform the storage that a region is no longer
May  9 23:15:57 cmp02 salt-minion[2964]: +        # used. Storage that supports discards advertise the protocol-specific
May  9 23:15:57 cmp02 salt-minion[2964]: +        # way discards should be issued by the kernel (TRIM, UNMAP, or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # WRITE SAME with UNMAP bit set). Not all storage will support or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # benefit from discards, but SSDs and thinly provisioned LUNs
May  9 23:15:57 cmp02 salt-minion[2964]: +        # generally do. If enabled, discards will only be issued if both the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # storage and kernel provide support.
May  9 23:15:57 cmp02 salt-minion[2964]: +        issue_discards = 1
May  9 23:15:57 cmp02 salt-minion[2964]:  }
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]:  # Configuration section allocation.
May  9 23:15:57 cmp02 salt-minion[2964]:  # How LVM selects space and applies properties to LVs.
May  9 23:15:57 cmp02 salt-minion[2964]:  allocation {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/cling_tag_list.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Advise LVM which PVs to use when searching for new space.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When searching for free space to extend an LV, the 'cling' allocation
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# policy will choose space on the same PVs as the last segment of the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# existing LV. If there is insufficient space and a list of tags is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# defined here, it will check whether any of them are attached to the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# PVs concerned and then seek to match those PV tags between existing
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# extents and new extents.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use the special tag "@*" as a wildcard to match any PV tag:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cling_tag_list = [ "@*" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVs are mirrored between two sites within a single VG, and
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# PVs are tagged with either @site1 or @site2 to indicate where
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# they are situated:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cling_tag_list = [ "@site1", "@site2" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/maximise_cling.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use a previous allocation algorithm.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Changes made in version 2.02.85 extended the reach of the 'cling'
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# policies to detect more situations where data can be grouped onto
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the same disks. This setting can be used to disable the changes
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# and revert to the previous algorithm.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011maximise_cling = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/use_blkid_wiping.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use blkid to detect existing signatures on new PVs and LVs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The blkid library can detect more signatures than the native LVM
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# detection code, but may take longer. LVM needs to be compiled with
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# blkid wiping support for this setting to apply. LVM native detection
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# code is currently able to recognize: MD device signatures,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# swap signature, and LUKS signatures. To see the list of signatures
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# recognized by blkid, check the output of the 'blkid -k' command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011use_blkid_wiping = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/wipe_signatures_when_zeroing_new_lvs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Look for and erase any signatures while zeroing a new LV.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The --wipesignatures option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Zeroing is controlled by the -Z/--zero option, and if not specified,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# zeroing is used by default if possible. Zeroing simply overwrites the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# first 4KiB of a new LV with zeroes and does no signature detection or
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# wiping. Signature wiping goes beyond zeroing and detects exact types
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# and positions of signatures within the whole LV. It provides a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cleaner LV after creation as all known signatures are wiped. The LV
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is not claimed incorrectly by other tools because of old signatures
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# from previous use. The number of signatures that LVM can detect
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# depends on the detection code that is selected (see
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# use_blkid_wiping.) Wiping each detected signature must be confirmed.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When this setting is disabled, signatures on new LVs are not detected
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# or erased unless the --wipesignatures option is used directly.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011wipe_signatures_when_zeroing_new_lvs = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/mirror_logs_require_separate_pvs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Mirror logs and images will always use different PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The default setting changed in version 2.02.85.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011mirror_logs_require_separate_pvs = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/cache_pool_metadata_require_separate_pvs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Cache pool metadata and data will always use different PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011cache_pool_metadata_require_separate_pvs = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/cache_mode.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The default cache mode used for new cache.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   writethrough
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Data blocks are immediately written from the cache to disk.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   writeback
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Data blocks are written from the cache back to disk after some
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     delay to improve performance.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This setting replaces allocation/cache_pool_cachemode.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_mode = "writethrough"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/cache_policy.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The default cache policy used for new cache volume.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Since kernel 4.2 the default policy is smq (Stochastic multique),
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# otherwise the older mq (Multiqueue) policy is selected.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration section allocation/cache_settings.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Settings for the cache policy.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# See documentation for individual cache policies for more info.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration section has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_settings {
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# }
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/cache_pool_chunk_size.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The minimal chunk size in KiB for cache pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Using a chunk_size that is too large can result in wasteful use of
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the cache, where small reads and writes can cause large sections of
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# an LV to be mapped into the cache. However, choosing a chunk_size
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# that is too small can result in more overhead trying to manage the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# numerous chunks that become mapped into the cache. The former is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# more of a problem than the latter in most cases, so the default is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# on the smaller end of the spectrum. Supported values range from
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# 32KiB to 1GiB in multiples of 32.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/thin_pool_metadata_require_separate_pvs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Thin pool metdata and data will always use different PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011thin_pool_metadata_require_separate_pvs = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/thin_pool_zero.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Thin pool data chunks are zeroed before they are first used.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Zeroing with a larger thin pool chunk size reduces performance.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_pool_zero = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/thin_pool_discards.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The discards behaviour of thin pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   ignore
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   nopassdown
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   passdown
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_pool_discards = "passdown"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/thin_pool_chunk_size_policy.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The chunk size calculation policy for thin pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   generic
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     If thin_pool_chunk_size is defined, use it. Otherwise, calculate
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     the chunk size based on estimation and device hints exposed in
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     sysfs - the minimum_io_size. The chunk size is always at least
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     64KiB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   performance
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     If thin_pool_chunk_size is defined, use it. Otherwise, calculate
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     the chunk size for performance based on device hints exposed in
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     sysfs - the optimal_io_size. The chunk size is always at least
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     512KiB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_pool_chunk_size_policy = "generic"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/thin_pool_chunk_size.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The minimal chunk size in KiB for thin pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Larger chunk sizes may improve performance for plain thin volumes,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# however using them for snapshot volumes is less efficient, as it
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# consumes more space and takes extra time for copying. When unset,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# lvm tries to estimate chunk size starting from 64KiB. Supported
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# values are in the range 64KiB to 1GiB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option allocation/physical_extent_size.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Default physical extent size in KiB to use for new VGs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# physical_extent_size = 4096
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/cling_tag_list.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Advise LVM which PVs to use when searching for new space.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When searching for free space to extend an LV, the 'cling' allocation
May  9 23:15:57 cmp02 salt-minion[2964]: +        # policy will choose space on the same PVs as the last segment of the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # existing LV. If there is insufficient space and a list of tags is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # defined here, it will check whether any of them are attached to the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # PVs concerned and then seek to match those PV tags between existing
May  9 23:15:57 cmp02 salt-minion[2964]: +        # extents and new extents.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use the special tag "@*" as a wildcard to match any PV tag:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cling_tag_list = [ "@*" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVs are mirrored between two sites within a single VG, and
May  9 23:15:57 cmp02 salt-minion[2964]: +        # PVs are tagged with either @site1 or @site2 to indicate where
May  9 23:15:57 cmp02 salt-minion[2964]: +        # they are situated:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cling_tag_list = [ "@site1", "@site2" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/maximise_cling.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use a previous allocation algorithm.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Changes made in version 2.02.85 extended the reach of the 'cling'
May  9 23:15:57 cmp02 salt-minion[2964]: +        # policies to detect more situations where data can be grouped onto
May  9 23:15:57 cmp02 salt-minion[2964]: +        # the same disks. This setting can be used to disable the changes
May  9 23:15:57 cmp02 salt-minion[2964]: +        # and revert to the previous algorithm.
May  9 23:15:57 cmp02 salt-minion[2964]: +        maximise_cling = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/use_blkid_wiping.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use blkid to detect existing signatures on new PVs and LVs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The blkid library can detect more signatures than the native LVM
May  9 23:15:57 cmp02 salt-minion[2964]: +        # detection code, but may take longer. LVM needs to be compiled with
May  9 23:15:57 cmp02 salt-minion[2964]: +        # blkid wiping support for this setting to apply. LVM native detection
May  9 23:15:57 cmp02 salt-minion[2964]: +        # code is currently able to recognize: MD device signatures,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # swap signature, and LUKS signatures. To see the list of signatures
May  9 23:15:57 cmp02 salt-minion[2964]: +        # recognized by blkid, check the output of the 'blkid -k' command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        use_blkid_wiping = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/wipe_signatures_when_zeroing_new_lvs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Look for and erase any signatures while zeroing a new LV.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The --wipesignatures option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Zeroing is controlled by the -Z/--zero option, and if not specified,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # zeroing is used by default if possible. Zeroing simply overwrites the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # first 4KiB of a new LV with zeroes and does no signature detection or
May  9 23:15:57 cmp02 salt-minion[2964]: +        # wiping. Signature wiping goes beyond zeroing and detects exact types
May  9 23:15:57 cmp02 salt-minion[2964]: +        # and positions of signatures within the whole LV. It provides a
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cleaner LV after creation as all known signatures are wiped. The LV
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is not claimed incorrectly by other tools because of old signatures
May  9 23:15:57 cmp02 salt-minion[2964]: +        # from previous use. The number of signatures that LVM can detect
May  9 23:15:57 cmp02 salt-minion[2964]: +        # depends on the detection code that is selected (see
May  9 23:15:57 cmp02 salt-minion[2964]: +        # use_blkid_wiping.) Wiping each detected signature must be confirmed.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When this setting is disabled, signatures on new LVs are not detected
May  9 23:15:57 cmp02 salt-minion[2964]: +        # or erased unless the --wipesignatures option is used directly.
May  9 23:15:57 cmp02 salt-minion[2964]: +        wipe_signatures_when_zeroing_new_lvs = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/mirror_logs_require_separate_pvs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Mirror logs and images will always use different PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The default setting changed in version 2.02.85.
May  9 23:15:57 cmp02 salt-minion[2964]: +        mirror_logs_require_separate_pvs = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/cache_pool_metadata_require_separate_pvs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Cache pool metadata and data will always use different PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        cache_pool_metadata_require_separate_pvs = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/cache_mode.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The default cache mode used for new cache.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   writethrough
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     Data blocks are immediately written from the cache to disk.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   writeback
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     Data blocks are written from the cache back to disk after some
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     delay to improve performance.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This setting replaces allocation/cache_pool_cachemode.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cache_mode = "writethrough"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/cache_policy.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The default cache policy used for new cache volume.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Since kernel 4.2 the default policy is smq (Stochastic multique),
May  9 23:15:57 cmp02 salt-minion[2964]: +        # otherwise the older mq (Multiqueue) policy is selected.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration section allocation/cache_settings.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Settings for the cache policy.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # See documentation for individual cache policies for more info.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration section has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cache_settings {
May  9 23:15:57 cmp02 salt-minion[2964]: +        # }
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/cache_pool_chunk_size.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The minimal chunk size in KiB for cache pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Using a chunk_size that is too large can result in wasteful use of
May  9 23:15:57 cmp02 salt-minion[2964]: +        # the cache, where small reads and writes can cause large sections of
May  9 23:15:57 cmp02 salt-minion[2964]: +        # an LV to be mapped into the cache. However, choosing a chunk_size
May  9 23:15:57 cmp02 salt-minion[2964]: +        # that is too small can result in more overhead trying to manage the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # numerous chunks that become mapped into the cache. The former is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # more of a problem than the latter in most cases, so the default is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # on the smaller end of the spectrum. Supported values range from
May  9 23:15:57 cmp02 salt-minion[2964]: +        # 32KiB to 1GiB in multiples of 32.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/thin_pool_metadata_require_separate_pvs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Thin pool metdata and data will always use different PVs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        thin_pool_metadata_require_separate_pvs = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/thin_pool_zero.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Thin pool data chunks are zeroed before they are first used.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Zeroing with a larger thin pool chunk size reduces performance.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_pool_zero = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/thin_pool_discards.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The discards behaviour of thin pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   ignore
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   nopassdown
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   passdown
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_pool_discards = "passdown"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/thin_pool_chunk_size_policy.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The chunk size calculation policy for thin pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   generic
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     If thin_pool_chunk_size is defined, use it. Otherwise, calculate
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     the chunk size based on estimation and device hints exposed in
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     sysfs - the minimum_io_size. The chunk size is always at least
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     64KiB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   performance
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     If thin_pool_chunk_size is defined, use it. Otherwise, calculate
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     the chunk size for performance based on device hints exposed in
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     sysfs - the optimal_io_size. The chunk size is always at least
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     512KiB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_pool_chunk_size_policy = "generic"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/thin_pool_chunk_size.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The minimal chunk size in KiB for thin pool volumes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Larger chunk sizes may improve performance for plain thin volumes,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # however using them for snapshot volumes is less efficient, as it
May  9 23:15:57 cmp02 salt-minion[2964]: +        # consumes more space and takes extra time for copying. When unset,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # lvm tries to estimate chunk size starting from 64KiB. Supported
May  9 23:15:57 cmp02 salt-minion[2964]: +        # values are in the range 64KiB to 1GiB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option allocation/physical_extent_size.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Default physical extent size in KiB to use for new VGs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # physical_extent_size = 4096
May  9 23:15:57 cmp02 salt-minion[2964]:  }
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]:  # Configuration section log.
May  9 23:15:57 cmp02 salt-minion[2964]:  # How LVM log information is reported.
May  9 23:15:57 cmp02 salt-minion[2964]:  log {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/verbose.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Controls the messages sent to stdout or stderr.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011verbose = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/silent.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Suppress all non-essential messages from stdout.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This has the same effect as -qq. When enabled, the following commands
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# still produce output: dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# pvdisplay, pvs, version, vgcfgrestore -l, vgdisplay, vgs.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Non-essential messages are shifted from log level 4 to log level 5
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# for syslog and lvm2_log_fn purposes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Any 'yes' or 'no' questions not overridden by other arguments are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# suppressed and default to 'no'.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011silent = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/syslog.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Send log messages through syslog.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011syslog = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/file.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Write error and debug log messages to a file specified here.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/overwrite.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Overwrite the log file each time the program is run.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011overwrite = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/level.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The level of log messages that are sent to the log file or syslog.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# There are 6 syslog-like log levels currently in use: 2 to 7 inclusive.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# 7 is the most verbose (LOG_DEBUG).
May  9 23:15:57 cmp02 salt-minion[2964]: -#011level = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/indent.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Indent messages according to their severity.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011indent = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/command_names.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Display the command name on each line of output.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011command_names = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/prefix.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# A prefix to use before the log message text.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (After the command name, if selected).
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Two spaces allows you to see/grep the severity of each message.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# To make the messages look similar to the original LVM tools use:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# indent = 0, command_names = 1, prefix = " -- "
May  9 23:15:57 cmp02 salt-minion[2964]: -#011prefix = "  "
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/activation.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Log messages during activation.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Don't use this in low memory situations (can deadlock).
May  9 23:15:57 cmp02 salt-minion[2964]: -#011activation = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option log/debug_classes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Select log messages by class.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Some debugging messages are assigned to a class and only appear in
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# debug output if the class is listed here. Classes currently
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# available: memory, devices, activation, allocation, lvmetad,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# metadata, cache, locking, lvmpolld. Use "all" to see everything.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011debug_classes = [ "memory", "devices", "activation", "allocation", "lvmetad", "metadata", "cache", "locking", "lvmpolld" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/verbose.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Controls the messages sent to stdout or stderr.
May  9 23:15:57 cmp02 salt-minion[2964]: +        verbose = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/silent.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Suppress all non-essential messages from stdout.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This has the same effect as -qq. When enabled, the following commands
May  9 23:15:57 cmp02 salt-minion[2964]: +        # still produce output: dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # pvdisplay, pvs, version, vgcfgrestore -l, vgdisplay, vgs.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Non-essential messages are shifted from log level 4 to log level 5
May  9 23:15:57 cmp02 salt-minion[2964]: +        # for syslog and lvm2_log_fn purposes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Any 'yes' or 'no' questions not overridden by other arguments are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # suppressed and default to 'no'.
May  9 23:15:57 cmp02 salt-minion[2964]: +        silent = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/syslog.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Send log messages through syslog.
May  9 23:15:57 cmp02 salt-minion[2964]: +        syslog = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/file.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Write error and debug log messages to a file specified here.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/overwrite.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Overwrite the log file each time the program is run.
May  9 23:15:57 cmp02 salt-minion[2964]: +        overwrite = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/level.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The level of log messages that are sent to the log file or syslog.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # There are 6 syslog-like log levels currently in use: 2 to 7 inclusive.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # 7 is the most verbose (LOG_DEBUG).
May  9 23:15:57 cmp02 salt-minion[2964]: +        level = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/indent.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Indent messages according to their severity.
May  9 23:15:57 cmp02 salt-minion[2964]: +        indent = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/command_names.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Display the command name on each line of output.
May  9 23:15:57 cmp02 salt-minion[2964]: +        command_names = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/prefix.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # A prefix to use before the log message text.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (After the command name, if selected).
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Two spaces allows you to see/grep the severity of each message.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # To make the messages look similar to the original LVM tools use:
May  9 23:15:57 cmp02 salt-minion[2964]: +        # indent = 0, command_names = 1, prefix = " -- "
May  9 23:15:57 cmp02 salt-minion[2964]: +        prefix = "  "
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/activation.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Log messages during activation.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Don't use this in low memory situations (can deadlock).
May  9 23:15:57 cmp02 salt-minion[2964]: +        activation = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 systemd[1]: Reloading.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option log/debug_classes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Select log messages by class.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Some debugging messages are assigned to a class and only appear in
May  9 23:15:57 cmp02 salt-minion[2964]: +        # debug output if the class is listed here. Classes currently
May  9 23:15:57 cmp02 salt-minion[2964]: +        # available: memory, devices, activation, allocation, lvmetad,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # metadata, cache, locking, lvmpolld. Use "all" to see everything.
May  9 23:15:57 cmp02 salt-minion[2964]: +        debug_classes = [ "memory", "devices", "activation", "allocation", "lvmetad", "metadata", "cache", "locking", "lvmpolld" ]
May  9 23:15:57 cmp02 salt-minion[2964]:  }
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]:  # Configuration section backup.
May  9 23:15:57 cmp02 salt-minion[2964]: @@ -535,957 +539,957 @@
May  9 23:15:57 cmp02 salt-minion[2964]:  # stored in a human readable text format.
May  9 23:15:57 cmp02 salt-minion[2964]:  backup {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option backup/backup.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Maintain a backup of the current metadata configuration.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Think very hard before turning this off!
May  9 23:15:57 cmp02 salt-minion[2964]: -#011backup = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option backup/backup_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Location of the metadata backup files.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Remember to back up this directory regularly!
May  9 23:15:57 cmp02 salt-minion[2964]: -#011backup_dir = "/etc/lvm/backup"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option backup/archive.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Maintain an archive of old metadata configurations.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Think very hard before turning this off.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011archive = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option backup/archive_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Location of the metdata archive files.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Remember to back up this directory regularly!
May  9 23:15:57 cmp02 salt-minion[2964]: -#011archive_dir = "/etc/lvm/archive"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option backup/retain_min.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Minimum number of archives to keep.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011retain_min = 10
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option backup/retain_days.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Minimum number of days to keep archive files.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011retain_days = 30
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option backup/backup.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Maintain a backup of the current metadata configuration.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Think very hard before turning this off!
May  9 23:15:57 cmp02 salt-minion[2964]: +        backup = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option backup/backup_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Location of the metadata backup files.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Remember to back up this directory regularly!
May  9 23:15:57 cmp02 salt-minion[2964]: +        backup_dir = "/etc/lvm/backup"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option backup/archive.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Maintain an archive of old metadata configurations.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Think very hard before turning this off.
May  9 23:15:57 cmp02 salt-minion[2964]: +        archive = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option backup/archive_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Location of the metdata archive files.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Remember to back up this directory regularly!
May  9 23:15:57 cmp02 salt-minion[2964]: +        archive_dir = "/etc/lvm/archive"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option backup/retain_min.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Minimum number of archives to keep.
May  9 23:15:57 cmp02 salt-minion[2964]: +        retain_min = 10
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option backup/retain_days.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Minimum number of days to keep archive files.
May  9 23:15:57 cmp02 salt-minion[2964]: +        retain_days = 30
May  9 23:15:57 cmp02 salt-minion[2964]:  }
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]:  # Configuration section shell.
May  9 23:15:57 cmp02 salt-minion[2964]:  # Settings for running LVM in shell (readline) mode.
May  9 23:15:57 cmp02 salt-minion[2964]:  shell {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option shell/history_size.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Number of lines of history to store in ~/.lvm_history.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011history_size = 100
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option shell/history_size.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Number of lines of history to store in ~/.lvm_history.
May  9 23:15:57 cmp02 salt-minion[2964]: +        history_size = 100
May  9 23:15:57 cmp02 salt-minion[2964]:  }
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]:  # Configuration section global.
May  9 23:15:57 cmp02 salt-minion[2964]:  # Miscellaneous global LVM settings.
May  9 23:15:57 cmp02 salt-minion[2964]:  global {
May  9 23:15:57 cmp02 salt-minion[2964]:  
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/umask.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The file creation mask for any files and directories created.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Interpreted as octal if the first digit is zero.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011umask = 077
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/test.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# No on-disk metadata changes will be made in test mode.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Equivalent to having the -t option on every command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011test = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/units.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Default value for --units argument.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011units = "h"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/si_unit_consistency.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Distinguish between powers of 1024 and 1000 bytes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The LVM commands distinguish between powers of 1024 bytes,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# e.g. KiB, MiB, GiB, and powers of 1000 bytes, e.g. KB, MB, GB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If scripts depend on the old behaviour, disable this setting
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# temporarily until they are updated.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011si_unit_consistency = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/suffix.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Display unit suffix for sizes.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This setting has no effect if the units are in human-readable form
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (global/units = "h") in which case the suffix is always displayed.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011suffix = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/activation.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Enable/disable communication with the kernel device-mapper.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Disable to use the tools to manipulate LVM metadata without
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# activating any logical volumes. If the device-mapper driver
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is not present in the kernel, disabling this should suppress
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the error messages.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011activation = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/fallback_to_lvm1.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Try running LVM1 tools if LVM cannot communicate with DM.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This option only applies to 2.4 kernels and is provided to help
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# switch between device-mapper kernels and LVM1 kernels. The LVM1
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# tools need to be installed with .lvm1 suffices, e.g. vgscan.lvm1.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# They will stop working once the lvm2 on-disk metadata format is used.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# fallback_to_lvm1 = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/format.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The default metadata format that commands should use.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The -M 1|2 option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   lvm1
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   lvm2
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# format = "lvm2"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/format_libraries.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Shared libraries that process different metadata formats.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If support for LVM1 metadata was compiled as a shared library use
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# format_libraries = "liblvm2format1.so"
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/segment_libraries.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/proc.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Location of proc filesystem.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011proc = "/proc"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/etc.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Location of /etc system configuration directory.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011etc = "/etc"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/locking_type.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Type of locking to use.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   0
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Turns off locking. Warning: this risks metadata corruption if
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     commands run concurrently.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   1
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM uses local file-based locking, the standard mode.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   2
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM uses the external shared library locking_library.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   3
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM uses built-in clustered locking with clvmd.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     This is incompatible with lvmetad. If use_lvmetad is enabled,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM prints a warning and disables lvmetad use.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   4
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM uses read-only locking which forbids any operations that
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     might change metadata.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   5
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Offers dummy locking for tools that do not need any locks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     You should not need to set this directly; the tools will select
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     when to use it instead of the configured locking_type.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Do not use lvmetad or the kernel device-mapper driver with this
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     locking type. It is used by the --readonly option that offers
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     read-only access to Volume Group metadata that cannot be locked
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     safely because it belongs to an inaccessible domain and might be
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     in use, for example a virtual machine image or a disk that is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     shared by a clustered machine.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011locking_type = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/wait_for_locks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When disabled, fail if a lock request would block.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011wait_for_locks = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/fallback_to_clustered_locking.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Attempt to use built-in cluster locking if locking_type 2 fails.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If using external locking (type 2) and initialisation fails, with
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# this enabled, an attempt will be made to use the built-in clustered
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# locking. Disable this if using a customised locking_library.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011fallback_to_clustered_locking = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/fallback_to_local_locking.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use locking_type 1 (local) if locking_type 2 or 3 fail.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# If an attempt to initialise type 2 or type 3 locking failed, perhaps
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# because cluster components such as clvmd are not running, with this
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# enabled, an attempt will be made to use local file-based locking
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (type 1). If this succeeds, only commands against local VGs will
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# proceed. VGs marked as clustered will be ignored.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011fallback_to_local_locking = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/locking_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Directory to use for LVM command file locks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Local non-LV directory that holds file-based locks while commands are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# in progress. A directory like /tmp that may get wiped on reboot is OK.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011locking_dir = "/run/lock/lvm"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/prioritise_write_locks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Allow quicker VG write access during high volume read access.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When there are competing read-only and read-write access requests for
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# a volume group's metadata, instead of always granting the read-only
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# requests immediately, delay them to allow the read-write requests to
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# be serviced. Without this setting, write access may be stalled by a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# high volume of read-only requests. This option only affects
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# locking_type 1 viz. local file-based locking.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011prioritise_write_locks = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/library_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Search this directory first for shared libraries.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/locking_library.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The external locking library to use for locking_type 2.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# locking_library = "liblvm2clusterlock.so"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/abort_on_internal_errors.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Abort a command that encounters an internal error.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Treat any internal errors as fatal errors, aborting the process that
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# encountered the internal error. Please only enable for debugging.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011abort_on_internal_errors = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/detect_internal_vg_cache_corruption.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Internal verification of VG structures.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Check if CRC matches when a parsed VG is used multiple times. This
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# is useful to catch unexpected changes to cached VG structures.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Please only enable for debugging.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011detect_internal_vg_cache_corruption = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/metadata_read_only.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# No operations that change on-disk metadata are permitted.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Additionally, read-only commands that encounter metadata in need of
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# repair will still be allowed to proceed exactly as if the repair had
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# been performed (except for the unchanged vg_seqno). Inappropriate
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# use could mess up your system, so seek advice first!
May  9 23:15:57 cmp02 salt-minion[2964]: -#011metadata_read_only = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/mirror_segtype_default.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The segment type used by the short mirroring option -m.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The --type mirror|raid1 option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   mirror
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     The original RAID1 implementation from LVM/DM. It is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     characterized by a flexible log solution (core, disk, mirrored),
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     and by the necessity to block I/O while handling a failure.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     There is an inherent race in the dmeventd failure handling logic
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     with snapshots of devices using this type of RAID1 that in the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     worst case could cause a deadlock. (Also see
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     devices/ignore_lvm_mirrors.)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   raid1
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     This is a newer RAID1 implementation using the MD RAID1
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     personality through device-mapper. It is characterized by a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     lack of log options. (A log is always allocated for every
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     device and they are placed on the same device as the image,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     so no separate devices are required.) This mirror
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     implementation does not require I/O to be blocked while
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     handling a failure. This mirror implementation is not
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     cluster-aware and cannot be used in a shared (active/active)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     fashion in a cluster.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011mirror_segtype_default = "raid1"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/raid10_segtype_default.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The segment type used by the -i -m combination.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The --type raid10|mirror option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The --stripes/-i and --mirrors/-m options can both be specified
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# during the creation of a logical volume to use both striping and
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# mirroring for the LV. There are two different implementations.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   raid10
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM uses MD's RAID10 personality through DM. This is the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     preferred option.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   mirror
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     LVM layers the 'mirror' and 'stripe' segment types. The layering
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     is done by creating a mirror LV on top of striped sub-LVs,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     effectively creating a RAID 0+1 array. The layering is suboptimal
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     in terms of providing redundancy and performance.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011raid10_segtype_default = "raid10"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/sparse_segtype_default.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The segment type used by the -V -L combination.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The --type snapshot|thin option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The combination of -V and -L options creates a sparse LV. There are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# two different implementations.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   snapshot
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     The original snapshot implementation from LVM/DM. It uses an old
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     snapshot that mixes data and metadata within a single COW
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     storage volume and performs poorly when the size of stored data
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     passes hundreds of MB.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   thin
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     A newer implementation that uses thin provisioning. It has a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     bigger minimal chunk size (64KiB) and uses a separate volume for
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     metadata. It has better performance, especially when more data
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     is used. It also supports full snapshots.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011sparse_segtype_default = "thin"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/lvdisplay_shows_full_device_path.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Enable this to reinstate the previous lvdisplay name format.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The default format for displaying LV names in lvdisplay was changed
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# in version 2.02.89 to show the LV name and path separately.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Previously this was always shown as /dev/vgname/lvname even when that
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# was never a valid path in the /dev filesystem.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# lvdisplay_shows_full_device_path = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/use_lvmetad.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use lvmetad to cache metadata and reduce disk scanning.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When enabled (and running), lvmetad provides LVM commands with VG
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# metadata and PV state. LVM commands then avoid reading this
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# information from disks which can be slow. When disabled (or not
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# running), LVM commands fall back to scanning disks to obtain VG
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# metadata. lvmetad is kept updated via udev rules which must be set
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# up for LVM to work correctly. (The udev rules should be installed
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# by default.) Without a proper udev setup, changes in the system's
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# block device configuration will be unknown to LVM, and ignored
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# until a manual 'pvscan --cache' is run. If lvmetad was running
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# while use_lvmetad was disabled, it must be stopped, use_lvmetad
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# enabled, and then started. When using lvmetad, LV activation is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# switched to an automatic, event-based mode. In this mode, LVs are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# activated based on incoming udev events that inform lvmetad when
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# PVs appear on the system. When a VG is complete (all PVs present),
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# it is auto-activated. The auto_activation_volume_list setting
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# controls which LVs are auto-activated (all by default.)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When lvmetad is updated (automatically by udev events, or directly
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# by pvscan --cache), devices/filter is ignored and all devices are
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# scanned by default. lvmetad always keeps unfiltered information
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# which is provided to LVM commands. Each LVM command then filters
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# based on devices/filter. This does not apply to other, non-regexp,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# filtering settings: component filters such as multipath and MD
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# are checked during pvscan --cache. To filter a device and prevent
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# scanning from the LVM system entirely, including lvmetad, use
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# devices/global_filter.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011use_lvmetad = 1
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/use_lvmlockd.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use lvmlockd for locking among hosts using LVM on shared storage.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# See lvmlockd(8) for more information.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011use_lvmlockd = 0
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/lvmlockd_lock_retries.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Retry lvmlockd lock requests this many times.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# lvmlockd_lock_retries = 3
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/sanlock_lv_extend.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Size in MiB to extend the internal LV holding sanlock locks.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The internal LV holds locks for each LV in the VG, and after enough
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVs have been created, the internal LV needs to be extended. lvcreate
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# will automatically extend the internal LV when needed by the amount
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# specified here. Setting this to 0 disables the automatic extension
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# and can cause lvcreate to fail.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# sanlock_lv_extend = 256
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/thin_check_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the thin_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM uses this command to check that a thin metadata device is in a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# usable state. When a thin pool is activated and after it is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# deactivated, this command is run. Activation will only proceed if
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the command has an exit status of 0. Set to "" to skip this check.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (Not recommended.) Also see thin_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_check_executable = "/usr/sbin/thin_check"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/thin_dump_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the thin_dump command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM uses this command to dump thin pool metadata.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_dump_executable = "/usr/sbin/thin_dump"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/thin_repair_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the thin_repair command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM uses this command to repair a thin metadata device if it is in
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# an unusable state. Also see thin_repair_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_repair_executable = "/usr/sbin/thin_repair"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/thin_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# List of options passed to the thin_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# With thin_check version 2.1 or newer you can add the option
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# --ignore-non-fatal-errors to let it pass through ignorable errors
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# and fix them later. With thin_check version 3.2 or newer you should
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# include the option --clear-needs-check-flag.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_check_options = [ "-q", "--clear-needs-check-flag" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/thin_repair_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# List of options passed to the thin_repair command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_repair_options = [ "" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/thin_disabled_features.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Features to not use in the thin driver.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This can be helpful for testing, or to avoid using a feature that is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# causing problems. Features include: block_size, discards,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# discards_non_power_2, external_origin, metadata_resize,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# external_origin_extend, error_if_no_space.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# thin_disabled_features = [ "discards", "block_size" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/cache_disabled_features.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Features to not use in the cache driver.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This can be helpful for testing, or to avoid using a feature that is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# causing problems. Features include: policy_mq, policy_smq.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_disabled_features = [ "policy_smq" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/cache_check_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the cache_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM uses this command to check that a cache metadata device is in a
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# usable state. When a cached LV is activated and after it is
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# deactivated, this command is run. Activation will only proceed if the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# command has an exit status of 0. Set to "" to skip this check.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (Not recommended.) Also see cache_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_check_executable = "/usr/sbin/cache_check"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/cache_dump_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the cache_dump command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM uses this command to dump cache pool metadata.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_dump_executable = "/usr/sbin/cache_dump"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/cache_repair_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the cache_repair command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# LVM uses this command to repair a cache metadata device if it is in
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# an unusable state. Also see cache_repair_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_repair_executable = "/usr/sbin/cache_repair"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/cache_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# List of options passed to the cache_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# With cache_check version 5.0 or newer you should include the option
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# --clear-needs-check-flag.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_check_options = [ "-q", "--clear-needs-check-flag" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/cache_repair_options.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# List of options passed to the cache_repair command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# cache_repair_options = [ "" ]
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/system_id_source.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The method LVM uses to set the local system ID.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Volume Groups can also be given a system ID (by vgcreate, vgchange,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# or vgimport.) A VG on shared storage devices is accessible only to
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the host with a matching system ID. See 'man lvmsystemid' for
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# information on limitations and correct usage.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   none
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     The host has no system ID.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   lvmlocal
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Obtain the system ID from the system_id setting in the 'local'
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     section of an lvm configuration file, e.g. lvmlocal.conf.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   uname
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Set the system ID from the hostname (uname) of the system.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     System IDs beginning localhost are not permitted.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   machineid
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Use the contents of the machine-id file to set the system ID.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Some systems create this file at installation time.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     See 'man machine-id' and global/etc.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#   file
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     Use the contents of another file (system_id_file) to set the
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#     system ID.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011#
May  9 23:15:57 cmp02 salt-minion[2964]: -#011system_id_source = "none"
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/system_id_file.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# The full path to the file containing a system ID.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This is used when system_id_source is set to 'file'.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Comments starting with the character # are ignored.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: -
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Configuration option global/use_lvmpolld.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# Use lvmpolld to supervise long running LVM commands.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# When enabled, control of long running LVM commands is transferred
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# from the original LVM command to the lvmpolld daemon. This allows
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# the operation to continue independent of the original LVM command.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# After lvmpolld takes over, the LVM command displays the progress
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# of the ongoing operation. lvmpolld itself runs LVM commands to
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# manage the progress of ongoing operations. lvmpolld can be used as
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# a native systemd service, which allows it to be started on demand,
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# and to use its own control group. When this option is disabled, LVM
May  9 23:15:57 cmp02 salt-minion[2964]: -#011# commands will supervise long running operations by forking themselves.
May  9 23:15:57 cmp02 salt-minion[2964]: -#011use_lvmpolld = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/umask.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The file creation mask for any files and directories created.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Interpreted as octal if the first digit is zero.
May  9 23:15:57 cmp02 salt-minion[2964]: +        umask = 077
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/test.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # No on-disk metadata changes will be made in test mode.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Equivalent to having the -t option on every command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        test = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/units.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Default value for --units argument.
May  9 23:15:57 cmp02 salt-minion[2964]: +        units = "h"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/si_unit_consistency.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Distinguish between powers of 1024 and 1000 bytes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The LVM commands distinguish between powers of 1024 bytes,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # e.g. KiB, MiB, GiB, and powers of 1000 bytes, e.g. KB, MB, GB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If scripts depend on the old behaviour, disable this setting
May  9 23:15:57 cmp02 salt-minion[2964]: +        # temporarily until they are updated.
May  9 23:15:57 cmp02 salt-minion[2964]: +        si_unit_consistency = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/suffix.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Display unit suffix for sizes.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This setting has no effect if the units are in human-readable form
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (global/units = "h") in which case the suffix is always displayed.
May  9 23:15:57 cmp02 salt-minion[2964]: +        suffix = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/activation.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Enable/disable communication with the kernel device-mapper.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Disable to use the tools to manipulate LVM metadata without
May  9 23:15:57 cmp02 salt-minion[2964]: +        # activating any logical volumes. If the device-mapper driver
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is not present in the kernel, disabling this should suppress
May  9 23:15:57 cmp02 salt-minion[2964]: +        # the error messages.
May  9 23:15:57 cmp02 salt-minion[2964]: +        activation = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/fallback_to_lvm1.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Try running LVM1 tools if LVM cannot communicate with DM.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This option only applies to 2.4 kernels and is provided to help
May  9 23:15:57 cmp02 salt-minion[2964]: +        # switch between device-mapper kernels and LVM1 kernels. The LVM1
May  9 23:15:57 cmp02 salt-minion[2964]: +        # tools need to be installed with .lvm1 suffices, e.g. vgscan.lvm1.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # They will stop working once the lvm2 on-disk metadata format is used.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # fallback_to_lvm1 = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/format.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The default metadata format that commands should use.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The -M 1|2 option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   lvm1
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   lvm2
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # format = "lvm2"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/format_libraries.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Shared libraries that process different metadata formats.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If support for LVM1 metadata was compiled as a shared library use
May  9 23:15:57 cmp02 salt-minion[2964]: +        # format_libraries = "liblvm2format1.so"
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/segment_libraries.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/proc.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Location of proc filesystem.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:57 cmp02 salt-minion[2964]: +        proc = "/proc"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/etc.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Location of /etc system configuration directory.
May  9 23:15:57 cmp02 salt-minion[2964]: +        etc = "/etc"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/locking_type.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Type of locking to use.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   0
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     Turns off locking. Warning: this risks metadata corruption if
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     commands run concurrently.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   1
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM uses local file-based locking, the standard mode.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   2
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM uses the external shared library locking_library.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   3
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM uses built-in clustered locking with clvmd.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     This is incompatible with lvmetad. If use_lvmetad is enabled,
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM prints a warning and disables lvmetad use.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   4
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM uses read-only locking which forbids any operations that
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     might change metadata.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   5
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     Offers dummy locking for tools that do not need any locks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     You should not need to set this directly; the tools will select
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     when to use it instead of the configured locking_type.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     Do not use lvmetad or the kernel device-mapper driver with this
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     locking type. It is used by the --readonly option that offers
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     read-only access to Volume Group metadata that cannot be locked
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     safely because it belongs to an inaccessible domain and might be
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     in use, for example a virtual machine image or a disk that is
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     shared by a clustered machine.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        locking_type = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/wait_for_locks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When disabled, fail if a lock request would block.
May  9 23:15:57 cmp02 salt-minion[2964]: +        wait_for_locks = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/fallback_to_clustered_locking.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Attempt to use built-in cluster locking if locking_type 2 fails.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If using external locking (type 2) and initialisation fails, with
May  9 23:15:57 cmp02 salt-minion[2964]: +        # this enabled, an attempt will be made to use the built-in clustered
May  9 23:15:57 cmp02 salt-minion[2964]: +        # locking. Disable this if using a customised locking_library.
May  9 23:15:57 cmp02 salt-minion[2964]: +        fallback_to_clustered_locking = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/fallback_to_local_locking.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use locking_type 1 (local) if locking_type 2 or 3 fail.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # If an attempt to initialise type 2 or type 3 locking failed, perhaps
May  9 23:15:57 cmp02 salt-minion[2964]: +        # because cluster components such as clvmd are not running, with this
May  9 23:15:57 cmp02 salt-minion[2964]: +        # enabled, an attempt will be made to use local file-based locking
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (type 1). If this succeeds, only commands against local VGs will
May  9 23:15:57 cmp02 salt-minion[2964]: +        # proceed. VGs marked as clustered will be ignored.
May  9 23:15:57 cmp02 salt-minion[2964]: +        fallback_to_local_locking = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/locking_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Directory to use for LVM command file locks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Local non-LV directory that holds file-based locks while commands are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # in progress. A directory like /tmp that may get wiped on reboot is OK.
May  9 23:15:57 cmp02 salt-minion[2964]: +        locking_dir = "/run/lock/lvm"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/prioritise_write_locks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Allow quicker VG write access during high volume read access.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When there are competing read-only and read-write access requests for
May  9 23:15:57 cmp02 salt-minion[2964]: +        # a volume group's metadata, instead of always granting the read-only
May  9 23:15:57 cmp02 salt-minion[2964]: +        # requests immediately, delay them to allow the read-write requests to
May  9 23:15:57 cmp02 salt-minion[2964]: +        # be serviced. Without this setting, write access may be stalled by a
May  9 23:15:57 cmp02 salt-minion[2964]: +        # high volume of read-only requests. This option only affects
May  9 23:15:57 cmp02 salt-minion[2964]: +        # locking_type 1 viz. local file-based locking.
May  9 23:15:57 cmp02 salt-minion[2964]: +        prioritise_write_locks = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/library_dir.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Search this directory first for shared libraries.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/locking_library.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The external locking library to use for locking_type 2.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # locking_library = "liblvm2clusterlock.so"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/abort_on_internal_errors.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Abort a command that encounters an internal error.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Treat any internal errors as fatal errors, aborting the process that
May  9 23:15:57 cmp02 salt-minion[2964]: +        # encountered the internal error. Please only enable for debugging.
May  9 23:15:57 cmp02 salt-minion[2964]: +        abort_on_internal_errors = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/detect_internal_vg_cache_corruption.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Internal verification of VG structures.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Check if CRC matches when a parsed VG is used multiple times. This
May  9 23:15:57 cmp02 salt-minion[2964]: +        # is useful to catch unexpected changes to cached VG structures.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Please only enable for debugging.
May  9 23:15:57 cmp02 salt-minion[2964]: +        detect_internal_vg_cache_corruption = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/metadata_read_only.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # No operations that change on-disk metadata are permitted.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Additionally, read-only commands that encounter metadata in need of
May  9 23:15:57 cmp02 salt-minion[2964]: +        # repair will still be allowed to proceed exactly as if the repair had
May  9 23:15:57 cmp02 salt-minion[2964]: +        # been performed (except for the unchanged vg_seqno). Inappropriate
May  9 23:15:57 cmp02 salt-minion[2964]: +        # use could mess up your system, so seek advice first!
May  9 23:15:57 cmp02 salt-minion[2964]: +        metadata_read_only = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/mirror_segtype_default.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The segment type used by the short mirroring option -m.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The --type mirror|raid1 option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   mirror
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     The original RAID1 implementation from LVM/DM. It is
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     characterized by a flexible log solution (core, disk, mirrored),
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     and by the necessity to block I/O while handling a failure.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     There is an inherent race in the dmeventd failure handling logic
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     with snapshots of devices using this type of RAID1 that in the
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     worst case could cause a deadlock. (Also see
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     devices/ignore_lvm_mirrors.)
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   raid1
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     This is a newer RAID1 implementation using the MD RAID1
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     personality through device-mapper. It is characterized by a
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     lack of log options. (A log is always allocated for every
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     device and they are placed on the same device as the image,
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     so no separate devices are required.) This mirror
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     implementation does not require I/O to be blocked while
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     handling a failure. This mirror implementation is not
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     cluster-aware and cannot be used in a shared (active/active)
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     fashion in a cluster.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        mirror_segtype_default = "raid1"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/raid10_segtype_default.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The segment type used by the -i -m combination.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The --type raid10|mirror option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The --stripes/-i and --mirrors/-m options can both be specified
May  9 23:15:57 cmp02 salt-minion[2964]: +        # during the creation of a logical volume to use both striping and
May  9 23:15:57 cmp02 salt-minion[2964]: +        # mirroring for the LV. There are two different implementations.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   raid10
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM uses MD's RAID10 personality through DM. This is the
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     preferred option.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   mirror
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     LVM layers the 'mirror' and 'stripe' segment types. The layering
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     is done by creating a mirror LV on top of striped sub-LVs,
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     effectively creating a RAID 0+1 array. The layering is suboptimal
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     in terms of providing redundancy and performance.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        raid10_segtype_default = "raid10"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/sparse_segtype_default.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The segment type used by the -V -L combination.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The --type snapshot|thin option overrides this setting.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The combination of -V and -L options creates a sparse LV. There are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # two different implementations.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   snapshot
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     The original snapshot implementation from LVM/DM. It uses an old
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     snapshot that mixes data and metadata within a single COW
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     storage volume and performs poorly when the size of stored data
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     passes hundreds of MB.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #   thin
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     A newer implementation that uses thin provisioning. It has a
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     bigger minimal chunk size (64KiB) and uses a separate volume for
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     metadata. It has better performance, especially when more data
May  9 23:15:57 cmp02 salt-minion[2964]: +        #     is used. It also supports full snapshots.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        sparse_segtype_default = "thin"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/lvdisplay_shows_full_device_path.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Enable this to reinstate the previous lvdisplay name format.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The default format for displaying LV names in lvdisplay was changed
May  9 23:15:57 cmp02 salt-minion[2964]: +        # in version 2.02.89 to show the LV name and path separately.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Previously this was always shown as /dev/vgname/lvname even when that
May  9 23:15:57 cmp02 salt-minion[2964]: +        # was never a valid path in the /dev filesystem.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # lvdisplay_shows_full_device_path = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/use_lvmetad.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use lvmetad to cache metadata and reduce disk scanning.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When enabled (and running), lvmetad provides LVM commands with VG
May  9 23:15:57 cmp02 salt-minion[2964]: +        # metadata and PV state. LVM commands then avoid reading this
May  9 23:15:57 cmp02 salt-minion[2964]: +        # information from disks which can be slow. When disabled (or not
May  9 23:15:57 cmp02 salt-minion[2964]: +        # running), LVM commands fall back to scanning disks to obtain VG
May  9 23:15:57 cmp02 salt-minion[2964]: +        # metadata. lvmetad is kept updated via udev rules which must be set
May  9 23:15:57 cmp02 salt-minion[2964]: +        # up for LVM to work correctly. (The udev rules should be installed
May  9 23:15:57 cmp02 salt-minion[2964]: +        # by default.) Without a proper udev setup, changes in the system's
May  9 23:15:57 cmp02 salt-minion[2964]: +        # block device configuration will be unknown to LVM, and ignored
May  9 23:15:57 cmp02 salt-minion[2964]: +        # until a manual 'pvscan --cache' is run. If lvmetad was running
May  9 23:15:57 cmp02 salt-minion[2964]: +        # while use_lvmetad was disabled, it must be stopped, use_lvmetad
May  9 23:15:57 cmp02 salt-minion[2964]: +        # enabled, and then started. When using lvmetad, LV activation is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # switched to an automatic, event-based mode. In this mode, LVs are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # activated based on incoming udev events that inform lvmetad when
May  9 23:15:57 cmp02 salt-minion[2964]: +        # PVs appear on the system. When a VG is complete (all PVs present),
May  9 23:15:57 cmp02 salt-minion[2964]: +        # it is auto-activated. The auto_activation_volume_list setting
May  9 23:15:57 cmp02 salt-minion[2964]: +        # controls which LVs are auto-activated (all by default.)
May  9 23:15:57 cmp02 salt-minion[2964]: +        # When lvmetad is updated (automatically by udev events, or directly
May  9 23:15:57 cmp02 salt-minion[2964]: +        # by pvscan --cache), devices/filter is ignored and all devices are
May  9 23:15:57 cmp02 salt-minion[2964]: +        # scanned by default. lvmetad always keeps unfiltered information
May  9 23:15:57 cmp02 salt-minion[2964]: +        # which is provided to LVM commands. Each LVM command then filters
May  9 23:15:57 cmp02 salt-minion[2964]: +        # based on devices/filter. This does not apply to other, non-regexp,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # filtering settings: component filters such as multipath and MD
May  9 23:15:57 cmp02 salt-minion[2964]: +        # are checked during pvscan --cache. To filter a device and prevent
May  9 23:15:57 cmp02 salt-minion[2964]: +        # scanning from the LVM system entirely, including lvmetad, use
May  9 23:15:57 cmp02 salt-minion[2964]: +        # devices/global_filter.
May  9 23:15:57 cmp02 salt-minion[2964]: +        use_lvmetad = 1
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/use_lvmlockd.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Use lvmlockd for locking among hosts using LVM on shared storage.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # See lvmlockd(8) for more information.
May  9 23:15:57 cmp02 salt-minion[2964]: +        use_lvmlockd = 0
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/lvmlockd_lock_retries.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Retry lvmlockd lock requests this many times.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # lvmlockd_lock_retries = 3
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/sanlock_lv_extend.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Size in MiB to extend the internal LV holding sanlock locks.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The internal LV holds locks for each LV in the VG, and after enough
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVs have been created, the internal LV needs to be extended. lvcreate
May  9 23:15:57 cmp02 salt-minion[2964]: +        # will automatically extend the internal LV when needed by the amount
May  9 23:15:57 cmp02 salt-minion[2964]: +        # specified here. Setting this to 0 disables the automatic extension
May  9 23:15:57 cmp02 salt-minion[2964]: +        # and can cause lvcreate to fail.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # sanlock_lv_extend = 256
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/thin_check_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The full path to the thin_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVM uses this command to check that a thin metadata device is in a
May  9 23:15:57 cmp02 salt-minion[2964]: +        # usable state. When a thin pool is activated and after it is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # deactivated, this command is run. Activation will only proceed if
May  9 23:15:57 cmp02 salt-minion[2964]: +        # the command has an exit status of 0. Set to "" to skip this check.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (Not recommended.) Also see thin_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_check_executable = "/usr/sbin/thin_check"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/thin_dump_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The full path to the thin_dump command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVM uses this command to dump thin pool metadata.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_dump_executable = "/usr/sbin/thin_dump"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/thin_repair_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The full path to the thin_repair command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVM uses this command to repair a thin metadata device if it is in
May  9 23:15:57 cmp02 salt-minion[2964]: +        # an unusable state. Also see thin_repair_options.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_repair_executable = "/usr/sbin/thin_repair"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/thin_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # List of options passed to the thin_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # With thin_check version 2.1 or newer you can add the option
May  9 23:15:57 cmp02 salt-minion[2964]: +        # --ignore-non-fatal-errors to let it pass through ignorable errors
May  9 23:15:57 cmp02 salt-minion[2964]: +        # and fix them later. With thin_check version 3.2 or newer you should
May  9 23:15:57 cmp02 salt-minion[2964]: +        # include the option --clear-needs-check-flag.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_check_options = [ "-q", "--clear-needs-check-flag" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/thin_repair_options.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # List of options passed to the thin_repair command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_repair_options = [ "" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/thin_disabled_features.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Features to not use in the thin driver.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This can be helpful for testing, or to avoid using a feature that is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # causing problems. Features include: block_size, discards,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # discards_non_power_2, external_origin, metadata_resize,
May  9 23:15:57 cmp02 salt-minion[2964]: +        # external_origin_extend, error_if_no_space.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:57 cmp02 salt-minion[2964]: +        # thin_disabled_features = [ "discards", "block_size" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/cache_disabled_features.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Features to not use in the cache driver.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This can be helpful for testing, or to avoid using a feature that is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # causing problems. Features include: policy_mq, policy_smq.
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cache_disabled_features = [ "policy_smq" ]
May  9 23:15:57 cmp02 salt-minion[2964]: +        #
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:57 cmp02 salt-minion[2964]: +        # Configuration option global/cache_check_executable.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # The full path to the cache_check command.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # LVM uses this command to check that a cache metadata device is in a
May  9 23:15:57 cmp02 salt-minion[2964]: +        # usable state. When a cached LV is activated and after it is
May  9 23:15:57 cmp02 salt-minion[2964]: +        # deactivated, this command is run. Activation will only proceed if the
May  9 23:15:57 cmp02 salt-minion[2964]: +        # command has an exit status of 0. Set to "" to skip this check.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (Not recommended.) Also see cache_check_options.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:57 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:57 cmp02 salt-minion[2964]: +        # cache_check_executable = "/usr/sbin/cache_check"
May  9 23:15:57 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/cache_dump_executable.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The full path to the cache_dump command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # LVM uses this command to dump cache pool metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # cache_dump_executable = "/usr/sbin/cache_dump"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/cache_repair_executable.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The full path to the cache_repair command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # LVM uses this command to repair a cache metadata device if it is in
May  9 23:15:58 cmp02 salt-minion[2964]: +        # an unusable state. Also see cache_repair_options.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # (See package device-mapper-persistent-data or thin-provisioning-tools)
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # cache_repair_executable = "/usr/sbin/cache_repair"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/cache_check_options.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of options passed to the cache_check command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # With cache_check version 5.0 or newer you should include the option
May  9 23:15:58 cmp02 salt-minion[2964]: +        # --clear-needs-check-flag.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # cache_check_options = [ "-q", "--clear-needs-check-flag" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/cache_repair_options.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of options passed to the cache_repair command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # cache_repair_options = [ "" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/system_id_source.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The method LVM uses to set the local system ID.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Volume Groups can also be given a system ID (by vgcreate, vgchange,
May  9 23:15:58 cmp02 salt-minion[2964]: +        # or vgimport.) A VG on shared storage devices is accessible only to
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the host with a matching system ID. See 'man lvmsystemid' for
May  9 23:15:58 cmp02 salt-minion[2964]: +        # information on limitations and correct usage.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   none
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The host has no system ID.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   lvmlocal
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Obtain the system ID from the system_id setting in the 'local'
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     section of an lvm configuration file, e.g. lvmlocal.conf.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   uname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Set the system ID from the hostname (uname) of the system.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     System IDs beginning localhost are not permitted.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   machineid
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Use the contents of the machine-id file to set the system ID.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Some systems create this file at installation time.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     See 'man machine-id' and global/etc.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   file
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Use the contents of another file (system_id_file) to set the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     system ID.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        system_id_source = "none"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/system_id_file.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The full path to the file containing a system ID.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This is used when system_id_source is set to 'file'.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Comments starting with the character # are ignored.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option global/use_lvmpolld.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use lvmpolld to supervise long running LVM commands.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When enabled, control of long running LVM commands is transferred
May  9 23:15:58 cmp02 salt-minion[2964]: +        # from the original LVM command to the lvmpolld daemon. This allows
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the operation to continue independent of the original LVM command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # After lvmpolld takes over, the LVM command displays the progress
May  9 23:15:58 cmp02 salt-minion[2964]: +        # of the ongoing operation. lvmpolld itself runs LVM commands to
May  9 23:15:58 cmp02 salt-minion[2964]: +        # manage the progress of ongoing operations. lvmpolld can be used as
May  9 23:15:58 cmp02 salt-minion[2964]: +        # a native systemd service, which allows it to be started on demand,
May  9 23:15:58 cmp02 salt-minion[2964]: +        # and to use its own control group. When this option is disabled, LVM
May  9 23:15:58 cmp02 salt-minion[2964]: +        # commands will supervise long running operations by forking themselves.
May  9 23:15:58 cmp02 salt-minion[2964]: +        use_lvmpolld = 1
May  9 23:15:58 cmp02 salt-minion[2964]:  }
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]:  # Configuration section activation.
May  9 23:15:58 cmp02 salt-minion[2964]:  activation {
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/checks.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Perform internal checks of libdevmapper operations.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Useful for debugging problems with activation. Some of the checks may
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# be expensive, so it's best to use this only when there seems to be a
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# problem.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011checks = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/udev_sync.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use udev notifications to synchronize udev and LVM.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --nodevsync option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When disabled, LVM commands will not wait for notifications from
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# udev, but continue irrespective of any possible udev processing in
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# the background. Only use this if udev is not running or has rules
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# that ignore the devices LVM creates. If enabled when udev is not
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# running, and LVM processes are waiting for udev, run the command
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# 'dmsetup udevcomplete_all' to wake them up.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011udev_sync = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/udev_rules.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use udev rules to manage LV device nodes and symlinks.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When disabled, LVM will manage the device nodes and symlinks for
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# active LVs itself. Manual intervention may be required if this
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# setting is changed while LVs are active.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011udev_rules = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/verify_udev_operations.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use extra checks in LVM to verify udev operations.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This enables additional checks (and if necessary, repairs) on entries
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# in the device directory after udev has completed processing its
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# events. Useful for diagnosing problems with LVM/udev interactions.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011verify_udev_operations = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/retry_deactivation.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Retry failed LV deactivation.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If LV deactivation fails, LVM will retry for a few seconds before
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# failing. This may happen because a process run from a quick udev rule
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# temporarily opened the device.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011retry_deactivation = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/missing_stripe_filler.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Method to fill missing stripes when activating an incomplete LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Using 'error' will make inaccessible parts of the device return I/O
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# errors on access. You can instead use a device path, in which case,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# that device will be used in place of missing stripes. Using anything
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# other than 'error' with mirrored or snapshotted volumes is likely to
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# result in data corruption.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011missing_stripe_filler = "error"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/use_linear_target.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use the linear target to optimize single stripe LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When disabled, the striped target is used. The linear target is an
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# optimised version of the striped target that only handles a single
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# stripe.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011use_linear_target = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/reserved_stack.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Stack size in KiB to reserve for use while devices are suspended.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Insufficent reserve risks I/O deadlock during device suspension.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011reserved_stack = 64
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/reserved_memory.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Memory size in KiB to reserve for use while devices are suspended.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Insufficent reserve risks I/O deadlock during device suspension.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011reserved_memory = 8192
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/process_priority.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Nice value used while devices are suspended.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use a high priority so that LVs are suspended
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# for the shortest possible time.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011process_priority = -18
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Only LVs selected by this list are activated.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If this list is defined, an LV is only activated if it matches an
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# entry in this list. If this list is undefined, it imposes no limits
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# on LV activation (all are allowed).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   vgname
May  9 23:15:58 cmp02 systemd[1]: Reloading.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The VG name is matched exactly and selects all LVs in the VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   vgname/lvname
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The VG name and LV name are matched exactly and selects the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   @tag
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Selects an LV if the specified tag matches a tag set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   @*
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Selects an LV if a tag defined on the host is also set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or VG. See tags/hosttags. If any host tags exist but volume_list
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     is not defined, a default single-entry list containing '@*' is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     assumed.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/auto_activation_volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Only LVs selected by this list are auto-activated.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This list works like volume_list, but it is used only by
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# auto-activation commands. It does not apply to direct activation
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# commands. If this list is defined, an LV is only auto-activated
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# if it matches an entry in this list. If this list is undefined, it
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# imposes no limits on LV auto-activation (all are allowed.) If this
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# list is defined and empty, i.e. "[]", then no LVs are selected for
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# auto-activation. An LV that is selected by this list for
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# auto-activation, must also be selected by volume_list (if defined)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# before it is activated. Auto-activation is an activation command that
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# includes the 'a' argument: --activate ay or -a ay. The 'a' (auto)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# argument for auto-activation is meant to be used by activation
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# commands that are run automatically by the system, as opposed to LVM
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# commands run directly by a user. A user may also use the 'a' flag
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# directly to perform auto-activation. Also see pvscan(8) for more
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# information about auto-activation.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   vgname
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The VG name is matched exactly and selects all LVs in the VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   vgname/lvname
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The VG name and LV name are matched exactly and selects the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   @tag
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Selects an LV if the specified tag matches a tag set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   @*
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Selects an LV if a tag defined on the host is also set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or VG. See tags/hosttags. If any host tags exist but volume_list
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     is not defined, a default single-entry list containing '@*' is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     assumed.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/read_only_volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# LVs in this list are activated in read-only mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If this list is defined, each LV that is to be activated is checked
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# against this list, and if it matches, it is activated in read-only
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# mode. This overrides the permission setting stored in the metadata,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# e.g. from --permission rw.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   vgname
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The VG name is matched exactly and selects all LVs in the VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   vgname/lvname
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The VG name and LV name are matched exactly and selects the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   @tag
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Selects an LV if the specified tag matches a tag set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   @*
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Selects an LV if a tag defined on the host is also set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or VG. See tags/hosttags. If any host tags exist but volume_list
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     is not defined, a default single-entry list containing '@*' is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     assumed.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/raid_region_size.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Size in KiB of each raid or mirror synchronization region.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# For raid or mirror segment types, this is the amount of data that is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# copied at once when initializing, or moved at once by pvmove.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011raid_region_size = 512
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/error_when_full.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Return errors if a thin pool runs out of space.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --errorwhenfull option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When enabled, writes to thin LVs immediately return an error if the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# thin pool is out of data space. When disabled, writes to thin LVs
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# are queued if the thin pool is out of space, and processed when the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# thin pool data space is extended. New thin pools are assigned the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# behavior defined here.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# error_when_full = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/readahead.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Setting to use when there is no readahead setting in metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   none
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Disable readahead.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   auto
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Use default value chosen by kernel.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011readahead = "auto"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/raid_fault_policy.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Defines how a device failure in a RAID LV is handled.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This includes LVs that have the following segment types:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# raid1, raid4, raid5*, and raid6*.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If a device in the LV fails, the policy determines the steps
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# performed by dmeventd automatically, and the steps perfomed by the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# manual command lvconvert --repair --use-policies.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Automatic handling requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   warn
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Use the system log to warn the user that a device in the RAID LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     has failed. It is left to the user to run lvconvert --repair
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     manually to remove or replace the failed device. As long as the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     number of failed devices does not exceed the redundancy of the LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     (1 device for raid4/5, 2 for raid6), the LV will remain usable.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   allocate
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Attempt to use any extra physical volumes in the VG as spares and
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     replace faulty devices.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011raid_fault_policy = "warn"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/mirror_image_fault_policy.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Defines how a device failure in a 'mirror' LV is handled.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# An LV with the 'mirror' segment type is composed of mirror images
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# (copies) and a mirror log. A disk log ensures that a mirror LV does
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# not need to be re-synced (all copies made the same) every time a
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# machine reboots or crashes. If a device in the LV fails, this policy
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# determines the steps perfomed by dmeventd automatically, and the steps
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# performed by the manual command lvconvert --repair --use-policies.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Automatic handling requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   remove
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Simply remove the faulty device and run without it. If the log
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     device fails, the mirror would convert to using an in-memory log.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     This means the mirror will not remember its sync status across
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     crashes/reboots and the entire mirror will be re-synced. If a
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     mirror image fails, the mirror will convert to a non-mirrored
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     device if there is only one remaining good copy.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   allocate
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Remove the faulty device and try to allocate space on a new
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     device to be a replacement for the failed device. Using this
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     policy for the log is fast and maintains the ability to remember
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     sync state through crashes/reboots. Using this policy for a
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     mirror device is slow, as it requires the mirror to resynchronize
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     the devices, but it will preserve the mirror characteristic of
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     the device. This policy acts like 'remove' if no suitable device
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     and space can be allocated for the replacement.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   allocate_anywhere
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Not yet implemented. Useful to place the log device temporarily
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     on the same physical volume as one of the mirror images. This
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     policy is not recommended for mirror devices since it would break
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     the redundant nature of the mirror. This policy acts like
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     'remove' if no suitable device and space can be allocated for the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     replacement.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011mirror_image_fault_policy = "remove"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/mirror_log_fault_policy.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Defines how a device failure in a 'mirror' log LV is handled.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The mirror_image_fault_policy description for mirrored LVs also
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# applies to mirrored log LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011mirror_log_fault_policy = "allocate"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/snapshot_autoextend_threshold.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Auto-extend a snapshot when its usage exceeds this percent.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Setting this to 100 disables automatic extension.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The minimum value is 50 (a smaller value is treated as 50.)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Also see snapshot_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Automatic extension requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# snapshot_autoextend_threshold = 70
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011snapshot_autoextend_threshold = 100
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/snapshot_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Auto-extending a snapshot adds this percent extra space.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The amount of additional space added to a snapshot is this
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# percent of its current size.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# snapshot_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011snapshot_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/thin_pool_autoextend_threshold.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Auto-extend a thin pool when its usage exceeds this percent.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Setting this to 100 disables automatic extension.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The minimum value is 50 (a smaller value is treated as 50.)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Also see thin_pool_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Automatic extension requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# thin_pool_autoextend_threshold = 70
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011thin_pool_autoextend_threshold = 100
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/thin_pool_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Auto-extending a thin pool adds this percent extra space.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The amount of additional space added to a thin pool is this
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# percent of its current size.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# thin_pool_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011thin_pool_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/mlock_filter.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Do not mlock these memory areas.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# While activating devices, I/O to devices being (re)configured is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# suspended. As a precaution against deadlocks, LVM pins memory it is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# using so it is not paged out, and will not require I/O to reread.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Groups of pages that are known not to be accessed during activation
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# do not need to be pinned into memory. Each string listed in this
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# setting is compared against each line in /proc/self/maps, and the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pages corresponding to lines that match are not pinned. On some
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# systems, locale-archive was found to make up over 80% of the memory
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# used by the process.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/use_mlockall.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use the old behavior of mlockall to pin all memory.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Prior to version 2.02.62, LVM used mlockall() to pin the whole
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# process's memory while activating devices.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011use_mlockall = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/monitoring.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Monitor LVs that are activated.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --ignoremonitoring option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When enabled, LVM will ask dmeventd to monitor activated LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011monitoring = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/polling_interval.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Check pvmove or lvconvert progress at this interval (seconds).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When pvmove or lvconvert must wait for the kernel to finish
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# synchronising or merging data, they check and report progress at
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# intervals of this number of seconds. If this is set to 0 and there
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# is only one thing to wait for, there are no progress reports, but
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# the process is awoken immediately once the operation is complete.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011polling_interval = 15
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/auto_set_activation_skip.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Set the activation skip flag on new thin snapshot LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --setactivationskip option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# An LV can have a persistent 'activation skip' flag. The flag causes
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# the LV to be skipped during normal activation. The lvchange/vgchange
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# -K option is required to activate LVs that have the activation skip
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# flag set. When this setting is enabled, the activation skip flag is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# set on new thin snapshot LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# auto_set_activation_skip = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/activation_mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# How LVs with missing devices are activated.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --activationmode option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   complete
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Only allow activation of an LV if all of the Physical Volumes it
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     uses are present. Other PVs in the Volume Group may be missing.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   degraded
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Like complete, but additionally RAID LVs of segment type raid1,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     raid4, raid5, radid6 and raid10 will be activated if there is no
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     data loss, i.e. they have sufficient redundancy to present the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     entire addressable range of the Logical Volume.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   partial
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Allows the activation of any LV even if a missing or failed PV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     could cause data loss with a portion of the LV inaccessible.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     This setting should not normally be used, but may sometimes
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     assist with data recovery.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011activation_mode = "degraded"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/lock_start_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Locking is started only for VGs selected by this list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The rules are the same as those for volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option activation/auto_lock_start_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Locking is auto-started only for VGs selected by this list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The rules are the same as those for auto_activation_volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/checks.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Perform internal checks of libdevmapper operations.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Useful for debugging problems with activation. Some of the checks may
May  9 23:15:58 cmp02 salt-minion[2964]: +        # be expensive, so it's best to use this only when there seems to be a
May  9 23:15:58 cmp02 salt-minion[2964]: +        # problem.
May  9 23:15:58 cmp02 salt-minion[2964]: +        checks = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/udev_sync.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use udev notifications to synchronize udev and LVM.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --nodevsync option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When disabled, LVM commands will not wait for notifications from
May  9 23:15:58 cmp02 salt-minion[2964]: +        # udev, but continue irrespective of any possible udev processing in
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the background. Only use this if udev is not running or has rules
May  9 23:15:58 cmp02 salt-minion[2964]: +        # that ignore the devices LVM creates. If enabled when udev is not
May  9 23:15:58 cmp02 salt-minion[2964]: +        # running, and LVM processes are waiting for udev, run the command
May  9 23:15:58 cmp02 salt-minion[2964]: +        # 'dmsetup udevcomplete_all' to wake them up.
May  9 23:15:58 cmp02 salt-minion[2964]: +        udev_sync = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/udev_rules.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use udev rules to manage LV device nodes and symlinks.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When disabled, LVM will manage the device nodes and symlinks for
May  9 23:15:58 cmp02 salt-minion[2964]: +        # active LVs itself. Manual intervention may be required if this
May  9 23:15:58 cmp02 salt-minion[2964]: +        # setting is changed while LVs are active.
May  9 23:15:58 cmp02 salt-minion[2964]: +        udev_rules = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/verify_udev_operations.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use extra checks in LVM to verify udev operations.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This enables additional checks (and if necessary, repairs) on entries
May  9 23:15:58 cmp02 salt-minion[2964]: +        # in the device directory after udev has completed processing its
May  9 23:15:58 cmp02 salt-minion[2964]: +        # events. Useful for diagnosing problems with LVM/udev interactions.
May  9 23:15:58 cmp02 salt-minion[2964]: +        verify_udev_operations = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/retry_deactivation.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Retry failed LV deactivation.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If LV deactivation fails, LVM will retry for a few seconds before
May  9 23:15:58 cmp02 salt-minion[2964]: +        # failing. This may happen because a process run from a quick udev rule
May  9 23:15:58 cmp02 salt-minion[2964]: +        # temporarily opened the device.
May  9 23:15:58 cmp02 salt-minion[2964]: +        retry_deactivation = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/missing_stripe_filler.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Method to fill missing stripes when activating an incomplete LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Using 'error' will make inaccessible parts of the device return I/O
May  9 23:15:58 cmp02 salt-minion[2964]: +        # errors on access. You can instead use a device path, in which case,
May  9 23:15:58 cmp02 salt-minion[2964]: +        # that device will be used in place of missing stripes. Using anything
May  9 23:15:58 cmp02 salt-minion[2964]: +        # other than 'error' with mirrored or snapshotted volumes is likely to
May  9 23:15:58 cmp02 salt-minion[2964]: +        # result in data corruption.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: +        missing_stripe_filler = "error"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/use_linear_target.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use the linear target to optimize single stripe LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When disabled, the striped target is used. The linear target is an
May  9 23:15:58 cmp02 salt-minion[2964]: +        # optimised version of the striped target that only handles a single
May  9 23:15:58 cmp02 salt-minion[2964]: +        # stripe.
May  9 23:15:58 cmp02 salt-minion[2964]: +        use_linear_target = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/reserved_stack.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Stack size in KiB to reserve for use while devices are suspended.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Insufficent reserve risks I/O deadlock during device suspension.
May  9 23:15:58 cmp02 salt-minion[2964]: +        reserved_stack = 64
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/reserved_memory.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Memory size in KiB to reserve for use while devices are suspended.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Insufficent reserve risks I/O deadlock during device suspension.
May  9 23:15:58 cmp02 salt-minion[2964]: +        reserved_memory = 8192
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/process_priority.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Nice value used while devices are suspended.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use a high priority so that LVs are suspended
May  9 23:15:58 cmp02 salt-minion[2964]: +        # for the shortest possible time.
May  9 23:15:58 cmp02 salt-minion[2964]: +        process_priority = -18
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Only LVs selected by this list are activated.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If this list is defined, an LV is only activated if it matches an
May  9 23:15:58 cmp02 salt-minion[2964]: +        # entry in this list. If this list is undefined, it imposes no limits
May  9 23:15:58 cmp02 salt-minion[2964]: +        # on LV activation (all are allowed).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   vgname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The VG name is matched exactly and selects all LVs in the VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   vgname/lvname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The VG name and LV name are matched exactly and selects the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   @tag
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Selects an LV if the specified tag matches a tag set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   @*
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Selects an LV if a tag defined on the host is also set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or VG. See tags/hosttags. If any host tags exist but volume_list
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     is not defined, a default single-entry list containing '@*' is
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     assumed.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/auto_activation_volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Only LVs selected by this list are auto-activated.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This list works like volume_list, but it is used only by
May  9 23:15:58 cmp02 salt-minion[2964]: +        # auto-activation commands. It does not apply to direct activation
May  9 23:15:58 cmp02 salt-minion[2964]: +        # commands. If this list is defined, an LV is only auto-activated
May  9 23:15:58 cmp02 salt-minion[2964]: +        # if it matches an entry in this list. If this list is undefined, it
May  9 23:15:58 cmp02 salt-minion[2964]: +        # imposes no limits on LV auto-activation (all are allowed.) If this
May  9 23:15:58 cmp02 salt-minion[2964]: +        # list is defined and empty, i.e. "[]", then no LVs are selected for
May  9 23:15:58 cmp02 salt-minion[2964]: +        # auto-activation. An LV that is selected by this list for
May  9 23:15:58 cmp02 salt-minion[2964]: +        # auto-activation, must also be selected by volume_list (if defined)
May  9 23:15:58 cmp02 salt-minion[2964]: +        # before it is activated. Auto-activation is an activation command that
May  9 23:15:58 cmp02 salt-minion[2964]: +        # includes the 'a' argument: --activate ay or -a ay. The 'a' (auto)
May  9 23:15:58 cmp02 salt-minion[2964]: +        # argument for auto-activation is meant to be used by activation
May  9 23:15:58 cmp02 salt-minion[2964]: +        # commands that are run automatically by the system, as opposed to LVM
May  9 23:15:58 cmp02 salt-minion[2964]: +        # commands run directly by a user. A user may also use the 'a' flag
May  9 23:15:58 cmp02 salt-minion[2964]: +        # directly to perform auto-activation. Also see pvscan(8) for more
May  9 23:15:58 cmp02 salt-minion[2964]: +        # information about auto-activation.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   vgname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The VG name is matched exactly and selects all LVs in the VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   vgname/lvname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The VG name and LV name are matched exactly and selects the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   @tag
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Selects an LV if the specified tag matches a tag set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   @*
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Selects an LV if a tag defined on the host is also set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or VG. See tags/hosttags. If any host tags exist but volume_list
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     is not defined, a default single-entry list containing '@*' is
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     assumed.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/read_only_volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # LVs in this list are activated in read-only mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If this list is defined, each LV that is to be activated is checked
May  9 23:15:58 cmp02 salt-minion[2964]: +        # against this list, and if it matches, it is activated in read-only
May  9 23:15:58 cmp02 salt-minion[2964]: +        # mode. This overrides the permission setting stored in the metadata,
May  9 23:15:58 cmp02 salt-minion[2964]: +        # e.g. from --permission rw.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   vgname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The VG name is matched exactly and selects all LVs in the VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   vgname/lvname
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The VG name and LV name are matched exactly and selects the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   @tag
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Selects an LV if the specified tag matches a tag set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   @*
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Selects an LV if a tag defined on the host is also set on the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or VG. See tags/hosttags. If any host tags exist but volume_list
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     is not defined, a default single-entry list containing '@*' is
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     assumed.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/raid_region_size.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Size in KiB of each raid or mirror synchronization region.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # For raid or mirror segment types, this is the amount of data that is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # copied at once when initializing, or moved at once by pvmove.
May  9 23:15:58 cmp02 salt-minion[2964]: +        raid_region_size = 512
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/error_when_full.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Return errors if a thin pool runs out of space.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --errorwhenfull option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When enabled, writes to thin LVs immediately return an error if the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # thin pool is out of data space. When disabled, writes to thin LVs
May  9 23:15:58 cmp02 salt-minion[2964]: +        # are queued if the thin pool is out of space, and processed when the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # thin pool data space is extended. New thin pools are assigned the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # behavior defined here.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # error_when_full = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/readahead.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Setting to use when there is no readahead setting in metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   none
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Disable readahead.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   auto
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Use default value chosen by kernel.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        readahead = "auto"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/raid_fault_policy.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Defines how a device failure in a RAID LV is handled.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This includes LVs that have the following segment types:
May  9 23:15:58 cmp02 salt-minion[2964]: +        # raid1, raid4, raid5*, and raid6*.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If a device in the LV fails, the policy determines the steps
May  9 23:15:58 cmp02 salt-minion[2964]: +        # performed by dmeventd automatically, and the steps perfomed by the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # manual command lvconvert --repair --use-policies.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Automatic handling requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   warn
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Use the system log to warn the user that a device in the RAID LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     has failed. It is left to the user to run lvconvert --repair
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     manually to remove or replace the failed device. As long as the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     number of failed devices does not exceed the redundancy of the LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     (1 device for raid4/5, 2 for raid6), the LV will remain usable.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   allocate
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Attempt to use any extra physical volumes in the VG as spares and
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     replace faulty devices.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        raid_fault_policy = "warn"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/mirror_image_fault_policy.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Defines how a device failure in a 'mirror' LV is handled.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # An LV with the 'mirror' segment type is composed of mirror images
May  9 23:15:58 cmp02 salt-minion[2964]: +        # (copies) and a mirror log. A disk log ensures that a mirror LV does
May  9 23:15:58 cmp02 salt-minion[2964]: +        # not need to be re-synced (all copies made the same) every time a
May  9 23:15:58 cmp02 salt-minion[2964]: +        # machine reboots or crashes. If a device in the LV fails, this policy
May  9 23:15:58 cmp02 salt-minion[2964]: +        # determines the steps perfomed by dmeventd automatically, and the steps
May  9 23:15:58 cmp02 salt-minion[2964]: +        # performed by the manual command lvconvert --repair --use-policies.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Automatic handling requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   remove
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Simply remove the faulty device and run without it. If the log
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     device fails, the mirror would convert to using an in-memory log.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     This means the mirror will not remember its sync status across
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     crashes/reboots and the entire mirror will be re-synced. If a
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     mirror image fails, the mirror will convert to a non-mirrored
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     device if there is only one remaining good copy.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   allocate
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Remove the faulty device and try to allocate space on a new
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     device to be a replacement for the failed device. Using this
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     policy for the log is fast and maintains the ability to remember
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     sync state through crashes/reboots. Using this policy for a
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     mirror device is slow, as it requires the mirror to resynchronize
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     the devices, but it will preserve the mirror characteristic of
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     the device. This policy acts like 'remove' if no suitable device
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     and space can be allocated for the replacement.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   allocate_anywhere
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Not yet implemented. Useful to place the log device temporarily
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     on the same physical volume as one of the mirror images. This
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     policy is not recommended for mirror devices since it would break
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     the redundant nature of the mirror. This policy acts like
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     'remove' if no suitable device and space can be allocated for the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     replacement.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        mirror_image_fault_policy = "remove"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/mirror_log_fault_policy.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Defines how a device failure in a 'mirror' log LV is handled.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The mirror_image_fault_policy description for mirrored LVs also
May  9 23:15:58 cmp02 salt-minion[2964]: +        # applies to mirrored log LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        mirror_log_fault_policy = "allocate"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/snapshot_autoextend_threshold.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Auto-extend a snapshot when its usage exceeds this percent.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Setting this to 100 disables automatic extension.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The minimum value is 50 (a smaller value is treated as 50.)
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Also see snapshot_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Automatic extension requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: +        # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: +        # 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: +        # snapshot_autoextend_threshold = 70
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        snapshot_autoextend_threshold = 100
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/snapshot_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Auto-extending a snapshot adds this percent extra space.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The amount of additional space added to a snapshot is this
May  9 23:15:58 cmp02 salt-minion[2964]: +        # percent of its current size.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: +        # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: +        # 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: +        # snapshot_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        snapshot_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/thin_pool_autoextend_threshold.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Auto-extend a thin pool when its usage exceeds this percent.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Setting this to 100 disables automatic extension.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The minimum value is 50 (a smaller value is treated as 50.)
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Also see thin_pool_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Automatic extension requires dmeventd to be monitoring the LV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: +        # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: +        # 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: +        # thin_pool_autoextend_threshold = 70
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        thin_pool_autoextend_threshold = 100
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/thin_pool_autoextend_percent.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Auto-extending a thin pool adds this percent extra space.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The amount of additional space added to a thin pool is this
May  9 23:15:58 cmp02 salt-minion[2964]: +        # percent of its current size.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Using 70% autoextend threshold and 20% autoextend size, when a 1G
May  9 23:15:58 cmp02 salt-minion[2964]: +        # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
May  9 23:15:58 cmp02 salt-minion[2964]: +        # 840M, it is extended to 1.44G:
May  9 23:15:58 cmp02 salt-minion[2964]: +        # thin_pool_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        thin_pool_autoextend_percent = 20
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/mlock_filter.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Do not mlock these memory areas.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # While activating devices, I/O to devices being (re)configured is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # suspended. As a precaution against deadlocks, LVM pins memory it is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # using so it is not paged out, and will not require I/O to reread.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Groups of pages that are known not to be accessed during activation
May  9 23:15:58 cmp02 salt-minion[2964]: +        # do not need to be pinned into memory. Each string listed in this
May  9 23:15:58 cmp02 salt-minion[2964]: +        # setting is compared against each line in /proc/self/maps, and the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pages corresponding to lines that match are not pinned. On some
May  9 23:15:58 cmp02 salt-minion[2964]: +        # systems, locale-archive was found to make up over 80% of the memory
May  9 23:15:58 cmp02 salt-minion[2964]: +        # used by the process.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/use_mlockall.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use the old behavior of mlockall to pin all memory.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Prior to version 2.02.62, LVM used mlockall() to pin the whole
May  9 23:15:58 cmp02 salt-minion[2964]: +        # process's memory while activating devices.
May  9 23:15:58 cmp02 salt-minion[2964]: +        use_mlockall = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/monitoring.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Monitor LVs that are activated.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --ignoremonitoring option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When enabled, LVM will ask dmeventd to monitor activated LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        monitoring = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/polling_interval.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Check pvmove or lvconvert progress at this interval (seconds).
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When pvmove or lvconvert must wait for the kernel to finish
May  9 23:15:58 cmp02 salt-minion[2964]: +        # synchronising or merging data, they check and report progress at
May  9 23:15:58 cmp02 salt-minion[2964]: +        # intervals of this number of seconds. If this is set to 0 and there
May  9 23:15:58 cmp02 salt-minion[2964]: +        # is only one thing to wait for, there are no progress reports, but
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the process is awoken immediately once the operation is complete.
May  9 23:15:58 cmp02 salt-minion[2964]: +        polling_interval = 15
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/auto_set_activation_skip.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Set the activation skip flag on new thin snapshot LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --setactivationskip option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # An LV can have a persistent 'activation skip' flag. The flag causes
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the LV to be skipped during normal activation. The lvchange/vgchange
May  9 23:15:58 cmp02 salt-minion[2964]: +        # -K option is required to activate LVs that have the activation skip
May  9 23:15:58 cmp02 salt-minion[2964]: +        # flag set. When this setting is enabled, the activation skip flag is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # set on new thin snapshot LVs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # auto_set_activation_skip = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/activation_mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # How LVs with missing devices are activated.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --activationmode option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   complete
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Only allow activation of an LV if all of the Physical Volumes it
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     uses are present. Other PVs in the Volume Group may be missing.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   degraded
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Like complete, but additionally RAID LVs of segment type raid1,
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     raid4, raid5, radid6 and raid10 will be activated if there is no
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     data loss, i.e. they have sufficient redundancy to present the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     entire addressable range of the Logical Volume.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   partial
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Allows the activation of any LV even if a missing or failed PV
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     could cause data loss with a portion of the LV inaccessible.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     This setting should not normally be used, but may sometimes
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     assist with data recovery.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        activation_mode = "degraded"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/lock_start_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Locking is started only for VGs selected by this list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The rules are the same as those for volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option activation/auto_lock_start_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Locking is auto-started only for VGs selected by this list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The rules are the same as those for auto_activation_volume_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]:  }
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]:  # Configuration section metadata.
May  9 23:15:58 cmp02 salt-minion[2964]:  # This configuration section has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]:  # metadata {
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option metadata/pvmetadatacopies.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Number of copies of metadata to store on each PV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --pvmetadatacopies option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   2
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Two copies of the VG metadata are stored on the PV, one at the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     front of the PV, and one at the end.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   1
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     One copy of VG metadata is stored at the front of the PV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   0
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     No copies of VG metadata are stored on the PV. This may be
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     useful for VGs containing large numbers of PVs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvmetadatacopies = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option metadata/vgmetadatacopies.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Number of copies of metadata to maintain for each VG.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --vgmetadatacopies option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If set to a non-zero value, LVM automatically chooses which of the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# available metadata areas to use to achieve the requested number of
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# copies of the VG metadata. If you set a value larger than the the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# total number of metadata areas available, then metadata is stored in
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# them all. The value 0 (unmanaged) disables this automatic management
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# and allows you to control which metadata areas are used at the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# individual PV level using pvchange --metadataignore y|n.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# vgmetadatacopies = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option metadata/pvmetadatasize.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Approximate number of sectors to use for each metadata copy.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# VGs with large numbers of PVs or LVs, or VGs containing complex LV
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# structures, may need additional space for VG metadata. The metadata
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# areas are treated as circular buffers, so unused space becomes filled
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# with an archive of the most recent previous versions of the metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvmetadatasize = 255
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option metadata/pvmetadataignore.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Ignore metadata areas on a new PV.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The --metadataignore option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If metadata areas on a PV are ignored, LVM will not store metadata
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# in them.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvmetadataignore = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option metadata/stripesize.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# stripesize = 64
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option metadata/dirs.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Directories holding live copies of text format metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# These directories must not be on logical volumes!
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# It's possible to use LVM with a couple of directories here,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# preferably on different (non-LV) filesystems, and with no other
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# on-disk metadata (pvmetadatacopies = 0). Or this can be in addition
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# to on-disk metadata areas. The feature was originally added to
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# simplify testing and is not supported under low memory situations -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# the machine could lock up. Never edit any files in these directories
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# by hand unless you are absolutely sure you know what you are doing!
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use the supplied toolset to make changes (e.g. vgcfgrestore).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option metadata/pvmetadatacopies.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Number of copies of metadata to store on each PV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --pvmetadatacopies option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   2
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Two copies of the VG metadata are stored on the PV, one at the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     front of the PV, and one at the end.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   1
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     One copy of VG metadata is stored at the front of the PV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   0
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     No copies of VG metadata are stored on the PV. This may be
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     useful for VGs containing large numbers of PVs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvmetadatacopies = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option metadata/vgmetadatacopies.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Number of copies of metadata to maintain for each VG.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --vgmetadatacopies option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If set to a non-zero value, LVM automatically chooses which of the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # available metadata areas to use to achieve the requested number of
May  9 23:15:58 cmp02 salt-minion[2964]: +        # copies of the VG metadata. If you set a value larger than the the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # total number of metadata areas available, then metadata is stored in
May  9 23:15:58 cmp02 salt-minion[2964]: +        # them all. The value 0 (unmanaged) disables this automatic management
May  9 23:15:58 cmp02 salt-minion[2964]: +        # and allows you to control which metadata areas are used at the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # individual PV level using pvchange --metadataignore y|n.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # vgmetadatacopies = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option metadata/pvmetadatasize.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Approximate number of sectors to use for each metadata copy.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # VGs with large numbers of PVs or LVs, or VGs containing complex LV
May  9 23:15:58 cmp02 salt-minion[2964]: +        # structures, may need additional space for VG metadata. The metadata
May  9 23:15:58 cmp02 salt-minion[2964]: +        # areas are treated as circular buffers, so unused space becomes filled
May  9 23:15:58 cmp02 salt-minion[2964]: +        # with an archive of the most recent previous versions of the metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvmetadatasize = 255
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option metadata/pvmetadataignore.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Ignore metadata areas on a new PV.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The --metadataignore option overrides this setting.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If metadata areas on a PV are ignored, LVM will not store metadata
May  9 23:15:58 cmp02 salt-minion[2964]: +        # in them.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvmetadataignore = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option metadata/stripesize.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # stripesize = 64
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option metadata/dirs.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Directories holding live copies of text format metadata.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # These directories must not be on logical volumes!
May  9 23:15:58 cmp02 salt-minion[2964]: +        # It's possible to use LVM with a couple of directories here,
May  9 23:15:58 cmp02 salt-minion[2964]: +        # preferably on different (non-LV) filesystems, and with no other
May  9 23:15:58 cmp02 salt-minion[2964]: +        # on-disk metadata (pvmetadatacopies = 0). Or this can be in addition
May  9 23:15:58 cmp02 salt-minion[2964]: +        # to on-disk metadata areas. The feature was originally added to
May  9 23:15:58 cmp02 salt-minion[2964]: +        # simplify testing and is not supported under low memory situations -
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the machine could lock up. Never edit any files in these directories
May  9 23:15:58 cmp02 salt-minion[2964]: +        # by hand unless you are absolutely sure you know what you are doing!
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use the supplied toolset to make changes (e.g. vgcfgrestore).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option is advanced.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]:  # }
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]:  # Configuration section report.
May  9 23:15:58 cmp02 salt-minion[2964]: @@ -1493,357 +1497,357 @@
May  9 23:15:58 cmp02 salt-minion[2964]:  # This configuration section has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]:  # report {
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/compact_output.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Do not print empty values for all report fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If enabled, all fields that don't have a value set for any of the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# rows reported are skipped and not printed. Compact output is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# applicable only if report/buffered is enabled. If you need to
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# compact only specified fields, use compact_output=0 and define
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# report/compact_output_cols configuration setting instead.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# compact_output = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/compact_output_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Do not print empty values for specified report fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If defined, specified fields that don't have a value set for any
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# of the rows reported are skipped and not printed. Compact output
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# is applicable only if report/buffered is enabled. If you need to
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# compact all fields, use compact_output=1 instead in which case
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# the compact_output_cols setting is then ignored.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# compact_output_cols = ""
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/aligned.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Align columns in report output.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# aligned = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/buffered.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Buffer report output.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# When buffered reporting is used, the report's content is appended
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# incrementally to include each object being reported until the report
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# is flushed to output which normally happens at the end of command
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# execution. Otherwise, if buffering is not used, each object is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# reported as soon as its processing is finished.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# buffered = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/headings.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Show headings for columns on report.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# headings = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/separator.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# A separator to use on report after each field.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# separator = " "
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/list_item_separator.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# A separator to use for list items when reported.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# list_item_separator = ","
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/prefixes.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use a field name prefix for each field reported.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# prefixes = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/quoted.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Quote field values when using field name prefixes.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# quoted = 1
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/colums_as_rows.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Output each column as a row.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# If set, this also implies report/prefixes=1.
May  9 23:15:58 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# colums_as_rows = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/binary_values_as_numeric.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Use binary values 0 or 1 instead of descriptive literal values.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# For columns that have exactly two valid values to report
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# (not counting the 'unknown' value which denotes that the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# value could not be determined).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# binary_values_as_numeric = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/time_format.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Set time format for fields reporting time values.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Format specification is a string which may contain special character
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# sequences and ordinary character sequences. Ordinary character
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# sequences are copied verbatim. Each special character sequence is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# introduced by the '%' character and such sequence is then
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# substituted with a value as described below.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %a
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The abbreviated name of the day of the week according to the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %A
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The full name of the day of the week according to the current
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     locale.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %b
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The abbreviated month name according to the current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %B
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The full month name according to the current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %c
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The preferred date and time representation for the current
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     locale (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %C
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The century number (year/100) as a 2-digit integer. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %d
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The day of the month as a decimal number (range 01 to 31).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %D
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Equivalent to %m/%d/%y. (For Americans only. Americans should
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     note that in other countries%d/%m/%y is rather common. This
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     means that in international context this format is ambiguous and
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     should not be used.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %e
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Like %d, the day of the month as a decimal number, but a leading
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     zero is replaced by a space. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %E
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Modifier: use alternative local-dependent representation if
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     available.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %F
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Equivalent to %Y-%m-%d (the ISO 8601 date format).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %G
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The ISO 8601 week-based year with century as adecimal number.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The 4-digit year corresponding to the ISO week number (see %V).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     This has the same format and value as %Y, except that if the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     ISO week number belongs to the previous or next year, that year
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     is used instead.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %g
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Like %G, but without century, that is, with a 2-digit year
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     (00-99).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %h
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Equivalent to %b.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %H
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The hour as a decimal number using a 24-hour clock
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     (range 00 to 23). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %I
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The hour as a decimal number using a 12-hour clock
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     (range 01 to 12). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %j
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The day of the year as a decimal number (range 001 to 366).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %k
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The hour (24-hour clock) as a decimal number (range 0 to 23);
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     single digits are preceded by a blank. (See also %H.)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %l
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The hour (12-hour clock) as a decimal number (range 1 to 12);
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     single digits are preceded by a blank. (See also %I.)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %m
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The month as a decimal number (range 01 to 12). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %M
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The minute as a decimal number (range 00 to 59). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %O
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Modifier: use alternative numeric symbols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %p
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Either "AM" or "PM" according to the given time value,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     or the corresponding strings for the current locale. Noon is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     treated as "PM" and midnight as "AM".
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %P
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     Like %p but in lowercase: "am" or "pm" or a corresponding
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     string for the current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %r
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The time in a.m. or p.m. notation. In the POSIX locale this is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     equivalent to %I:%M:%S %p.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %R
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The time in 24-hour notation (%H:%M). For a version including
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     the seconds, see %T below.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %s
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The number of seconds since the Epoch,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     1970-01-01 00:00:00 +0000 (UTC)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %S
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The second as a decimal number (range 00 to 60). (The range is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     up to 60 to allow for occasional leap seconds.) (alt O)
May  9 23:15:58 cmp02 systemd[1]: Reloading.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %t
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     A tab character.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %T
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The time in 24-hour notation (%H:%M:%S).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %u
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The day of the week as a decimal, range 1 to 7, Monday being 1.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     See also %w. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %U
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The week number of the current year as a decimal number,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     range 00 to 53, starting with the first Sunday as the first
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     day of week 01. See also %V and %W. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %V
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The ISO 8601 week number of the current year as a decimal number,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     range 01 to 53, where week 1 is the first week that has at least
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     4 days in the new year. See also %U and %W. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %w
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The day of the week as a decimal, range 0 to 6, Sunday being 0.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     See also %u. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %W
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The week number of the current year as a decimal number,
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     range 00 to 53, starting with the first Monday as the first day
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     of week 01. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %x
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The preferred date representation for the current locale without
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     the time. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %X
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The preferred time representation for the current locale without
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     the date. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %y
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The year as a decimal number without a century (range 00 to 99).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     (alt E, alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %Y
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The year as a decimal number including the century. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %z
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The +hhmm or -hhmm numeric timezone (that is, the hour and minute
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     offset from UTC).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %Z
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     The timezone name or abbreviation.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#   %%
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#     A literal '%' character.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# time_format = "%Y-%m-%d %T %z"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/devtypes_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'lvm devtypes' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvm devtypes -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# devtypes_sort = "devtype_name"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/devtypes_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'lvm devtypes' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvm devtypes -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# devtypes_cols = "devtype_name,devtype_max_partitions,devtype_description"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/devtypes_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'lvm devtypes' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvm devtypes -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# devtypes_cols_verbose = "devtype_name,devtype_max_partitions,devtype_description"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/lvs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'lvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# lvs_sort = "vg_name,lv_name"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/lvs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'lvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# lvs_cols = "lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,metadata_percent,move_pv,mirror_log,copy_percent,convert_lv"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/lvs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'lvs' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# lvs_cols_verbose = "lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert_lv,lv_uuid,lv_profile"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/vgs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'vgs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'vgs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# vgs_sort = "vg_name"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/vgs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'vgs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'vgs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# vgs_cols = "vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/vgs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'vgs' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'vgs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# vgs_cols_verbose = "vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/pvs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'pvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'pvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvs_sort = "pv_name"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/pvs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'pvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'pvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/pvs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'pvs' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'pvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/segs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'lvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# segs_sort = "vg_name,lv_name,seg_start"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/segs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'lvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# segs_cols = "lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/segs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to report for 'lvs --segments' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'lvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# segs_cols_verbose = "lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/pvsegs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'pvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'pvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvsegs_sort = "pv_name,pvseg_start"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/pvsegs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'pvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'pvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvsegs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option report/pvsegs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# List of columns to sort by when reporting 'pvs --segments' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# See 'pvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# pvsegs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/compact_output.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Do not print empty values for all report fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If enabled, all fields that don't have a value set for any of the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # rows reported are skipped and not printed. Compact output is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # applicable only if report/buffered is enabled. If you need to
May  9 23:15:58 cmp02 salt-minion[2964]: +        # compact only specified fields, use compact_output=0 and define
May  9 23:15:58 cmp02 salt-minion[2964]: +        # report/compact_output_cols configuration setting instead.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # compact_output = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/compact_output_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Do not print empty values for specified report fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If defined, specified fields that don't have a value set for any
May  9 23:15:58 cmp02 salt-minion[2964]: +        # of the rows reported are skipped and not printed. Compact output
May  9 23:15:58 cmp02 salt-minion[2964]: +        # is applicable only if report/buffered is enabled. If you need to
May  9 23:15:58 cmp02 salt-minion[2964]: +        # compact all fields, use compact_output=1 instead in which case
May  9 23:15:58 cmp02 salt-minion[2964]: +        # the compact_output_cols setting is then ignored.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # compact_output_cols = ""
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/aligned.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Align columns in report output.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # aligned = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/buffered.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Buffer report output.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # When buffered reporting is used, the report's content is appended
May  9 23:15:58 cmp02 salt-minion[2964]: +        # incrementally to include each object being reported until the report
May  9 23:15:58 cmp02 salt-minion[2964]: +        # is flushed to output which normally happens at the end of command
May  9 23:15:58 cmp02 salt-minion[2964]: +        # execution. Otherwise, if buffering is not used, each object is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # reported as soon as its processing is finished.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # buffered = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/headings.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Show headings for columns on report.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # headings = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/separator.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # A separator to use on report after each field.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # separator = " "
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/list_item_separator.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # A separator to use for list items when reported.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # list_item_separator = ","
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/prefixes.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use a field name prefix for each field reported.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # prefixes = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/quoted.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Quote field values when using field name prefixes.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # quoted = 1
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/colums_as_rows.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Output each column as a row.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # If set, this also implies report/prefixes=1.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # colums_as_rows = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/binary_values_as_numeric.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Use binary values 0 or 1 instead of descriptive literal values.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # For columns that have exactly two valid values to report
May  9 23:15:58 cmp02 salt-minion[2964]: +        # (not counting the 'unknown' value which denotes that the
May  9 23:15:58 cmp02 salt-minion[2964]: +        # value could not be determined).
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # binary_values_as_numeric = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/time_format.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Set time format for fields reporting time values.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Format specification is a string which may contain special character
May  9 23:15:58 cmp02 salt-minion[2964]: +        # sequences and ordinary character sequences. Ordinary character
May  9 23:15:58 cmp02 salt-minion[2964]: +        # sequences are copied verbatim. Each special character sequence is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # introduced by the '%' character and such sequence is then
May  9 23:15:58 cmp02 salt-minion[2964]: +        # substituted with a value as described below.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Accepted values:
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %a
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The abbreviated name of the day of the week according to the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %A
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The full name of the day of the week according to the current
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     locale.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %b
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The abbreviated month name according to the current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %B
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The full month name according to the current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %c
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The preferred date and time representation for the current
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     locale (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %C
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The century number (year/100) as a 2-digit integer. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %d
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The day of the month as a decimal number (range 01 to 31).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %D
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Equivalent to %m/%d/%y. (For Americans only. Americans should
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     note that in other countries%d/%m/%y is rather common. This
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     means that in international context this format is ambiguous and
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     should not be used.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %e
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Like %d, the day of the month as a decimal number, but a leading
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     zero is replaced by a space. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %E
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Modifier: use alternative local-dependent representation if
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     available.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %F
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Equivalent to %Y-%m-%d (the ISO 8601 date format).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %G
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The ISO 8601 week-based year with century as adecimal number.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The 4-digit year corresponding to the ISO week number (see %V).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     This has the same format and value as %Y, except that if the
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     ISO week number belongs to the previous or next year, that year
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     is used instead.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %g
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Like %G, but without century, that is, with a 2-digit year
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     (00-99).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %h
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Equivalent to %b.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %H
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The hour as a decimal number using a 24-hour clock
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     (range 00 to 23). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %I
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The hour as a decimal number using a 12-hour clock
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     (range 01 to 12). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %j
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The day of the year as a decimal number (range 001 to 366).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %k
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The hour (24-hour clock) as a decimal number (range 0 to 23);
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     single digits are preceded by a blank. (See also %H.)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %l
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The hour (12-hour clock) as a decimal number (range 1 to 12);
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     single digits are preceded by a blank. (See also %I.)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %m
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The month as a decimal number (range 01 to 12). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %M
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The minute as a decimal number (range 00 to 59). (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %O
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Modifier: use alternative numeric symbols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %p
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Either "AM" or "PM" according to the given time value,
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     or the corresponding strings for the current locale. Noon is
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     treated as "PM" and midnight as "AM".
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %P
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     Like %p but in lowercase: "am" or "pm" or a corresponding
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     string for the current locale.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %r
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The time in a.m. or p.m. notation. In the POSIX locale this is
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     equivalent to %I:%M:%S %p.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %R
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The time in 24-hour notation (%H:%M). For a version including
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     the seconds, see %T below.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %s
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The number of seconds since the Epoch,
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     1970-01-01 00:00:00 +0000 (UTC)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %S
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The second as a decimal number (range 00 to 60). (The range is
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     up to 60 to allow for occasional leap seconds.) (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %t
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     A tab character.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %T
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The time in 24-hour notation (%H:%M:%S).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %u
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The day of the week as a decimal, range 1 to 7, Monday being 1.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     See also %w. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %U
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The week number of the current year as a decimal number,
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     range 00 to 53, starting with the first Sunday as the first
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     day of week 01. See also %V and %W. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %V
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The ISO 8601 week number of the current year as a decimal number,
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     range 01 to 53, where week 1 is the first week that has at least
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     4 days in the new year. See also %U and %W. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %w
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The day of the week as a decimal, range 0 to 6, Sunday being 0.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     See also %u. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %W
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The week number of the current year as a decimal number,
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     range 00 to 53, starting with the first Monday as the first day
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     of week 01. (alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %x
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The preferred date representation for the current locale without
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     the time. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %X
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The preferred time representation for the current locale without
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     the date. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %y
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The year as a decimal number without a century (range 00 to 99).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     (alt E, alt O)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %Y
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The year as a decimal number including the century. (alt E)
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %z
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The +hhmm or -hhmm numeric timezone (that is, the hour and minute
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     offset from UTC).
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %Z
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     The timezone name or abbreviation.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #   %%
May  9 23:15:58 cmp02 salt-minion[2964]: +        #     A literal '%' character.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # time_format = "%Y-%m-%d %T %z"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/devtypes_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'lvm devtypes' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvm devtypes -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # devtypes_sort = "devtype_name"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/devtypes_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'lvm devtypes' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvm devtypes -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # devtypes_cols = "devtype_name,devtype_max_partitions,devtype_description"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/devtypes_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'lvm devtypes' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvm devtypes -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # devtypes_cols_verbose = "devtype_name,devtype_max_partitions,devtype_description"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/lvs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'lvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # lvs_sort = "vg_name,lv_name"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/lvs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'lvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # lvs_cols = "lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,metadata_percent,move_pv,mirror_log,copy_percent,convert_lv"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/lvs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'lvs' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # lvs_cols_verbose = "lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert_lv,lv_uuid,lv_profile"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/vgs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'vgs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'vgs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # vgs_sort = "vg_name"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/vgs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'vgs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'vgs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # vgs_cols = "vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/vgs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'vgs' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'vgs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # vgs_cols_verbose = "vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/pvs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'pvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'pvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvs_sort = "pv_name"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/pvs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'pvs' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'pvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/pvs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'pvs' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'pvs -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/segs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'lvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # segs_sort = "vg_name,lv_name,seg_start"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/segs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'lvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # segs_cols = "lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/segs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to report for 'lvs --segments' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'lvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # segs_cols_verbose = "lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/pvsegs_sort.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'pvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'pvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvsegs_sort = "pv_name,pvseg_start"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/pvsegs_cols.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'pvs --segments' command.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'pvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvsegs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option report/pvsegs_cols_verbose.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # List of columns to sort by when reporting 'pvs --segments' command in verbose mode.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # See 'pvs --segments -o help' for the list of possible fields.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # pvsegs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
May  9 23:15:58 cmp02 salt-minion[2964]:  # }
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]:  # Configuration section dmeventd.
May  9 23:15:58 cmp02 salt-minion[2964]:  # Settings for the LVM event daemon.
May  9 23:15:58 cmp02 salt-minion[2964]:  dmeventd {
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option dmeventd/mirror_library.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The library dmeventd uses when monitoring a mirror device.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# libdevmapper-event-lvm2mirror.so attempts to recover from
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# failures. It removes failed devices from a volume group and
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# reconfigures a mirror as necessary. If no mirror library is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# provided, mirrors are not monitored through dmeventd.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011mirror_library = "libdevmapper-event-lvm2mirror.so"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option dmeventd/raid_library.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# raid_library = "libdevmapper-event-lvm2raid.so"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option dmeventd/snapshot_library.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The library dmeventd uses when monitoring a snapshot device.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# libdevmapper-event-lvm2snapshot.so monitors the filling of snapshots
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# and emits a warning through syslog when the usage exceeds 80%. The
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# warning is repeated when 85%, 90% and 95% of the snapshot is filled.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011snapshot_library = "libdevmapper-event-lvm2snapshot.so"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option dmeventd/thin_library.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The library dmeventd uses when monitoring a thin device.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# libdevmapper-event-lvm2thin.so monitors the filling of a pool
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# and emits a warning through syslog when the usage exceeds 80%. The
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# warning is repeated when 85%, 90% and 95% of the pool is filled.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011thin_library = "libdevmapper-event-lvm2thin.so"
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option dmeventd/executable.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The full path to the dmeventd binary.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# executable = "/sbin/dmeventd"
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option dmeventd/mirror_library.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The library dmeventd uses when monitoring a mirror device.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # libdevmapper-event-lvm2mirror.so attempts to recover from
May  9 23:15:58 cmp02 salt-minion[2964]: +        # failures. It removes failed devices from a volume group and
May  9 23:15:58 cmp02 salt-minion[2964]: +        # reconfigures a mirror as necessary. If no mirror library is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # provided, mirrors are not monitored through dmeventd.
May  9 23:15:58 cmp02 salt-minion[2964]: +        mirror_library = "libdevmapper-event-lvm2mirror.so"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option dmeventd/raid_library.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # raid_library = "libdevmapper-event-lvm2raid.so"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option dmeventd/snapshot_library.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The library dmeventd uses when monitoring a snapshot device.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # libdevmapper-event-lvm2snapshot.so monitors the filling of snapshots
May  9 23:15:58 cmp02 salt-minion[2964]: +        # and emits a warning through syslog when the usage exceeds 80%. The
May  9 23:15:58 cmp02 salt-minion[2964]: +        # warning is repeated when 85%, 90% and 95% of the snapshot is filled.
May  9 23:15:58 cmp02 salt-minion[2964]: +        snapshot_library = "libdevmapper-event-lvm2snapshot.so"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option dmeventd/thin_library.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The library dmeventd uses when monitoring a thin device.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # libdevmapper-event-lvm2thin.so monitors the filling of a pool
May  9 23:15:58 cmp02 salt-minion[2964]: +        # and emits a warning through syslog when the usage exceeds 80%. The
May  9 23:15:58 cmp02 salt-minion[2964]: +        # warning is repeated when 85%, 90% and 95% of the pool is filled.
May  9 23:15:58 cmp02 salt-minion[2964]: +        thin_library = "libdevmapper-event-lvm2thin.so"
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option dmeventd/executable.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The full path to the dmeventd binary.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # executable = "/sbin/dmeventd"
May  9 23:15:58 cmp02 salt-minion[2964]:  }
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]:  # Configuration section tags.
May  9 23:15:58 cmp02 salt-minion[2964]: @@ -1851,37 +1855,37 @@
May  9 23:15:58 cmp02 salt-minion[2964]:  # This configuration section has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]:  # tags {
May  9 23:15:58 cmp02 salt-minion[2964]:  
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration option tags/hosttags.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Create a host tag using the machine name.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The machine name is nodename returned by uname(2).
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# hosttags = 0
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Configuration section tags/<tag>.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Replace this subsection name with a custom tag name.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Multiple subsections like this can be created. The '@' prefix for
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# tags is optional. This subsection can contain host_list, which is a
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# list of machine names. If the name of the local machine is found in
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# host_list, then the name of this subsection is used as a tag and is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# applied to the local machine as a 'host tag'. If this subsection is
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# empty (has no host_list), then the subsection name is always applied
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# as a 'host tag'.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# Example
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# The host tag foo is given to all hosts, and the host tag
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# bar is given to the hosts named machine1 and machine2.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# tags { foo { } bar { host_list = [ "machine1", "machine2" ] } }
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration section has variable name.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# This configuration section has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# tag {
May  9 23:15:58 cmp02 salt-minion[2964]: -
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# Configuration option tags/<tag>/host_list.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# A list of machine names.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# These machine names are compared to the nodename returned
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# by uname(2). If the local machine name matches an entry in
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# this list, the name of the subsection is applied to the
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# machine as a 'host tag'.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011#011# This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: -#011# }
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration option tags/hosttags.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Create a host tag using the machine name.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The machine name is nodename returned by uname(2).
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration option has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # hosttags = 0
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Configuration section tags/<tag>.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Replace this subsection name with a custom tag name.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Multiple subsections like this can be created. The '@' prefix for
May  9 23:15:58 cmp02 salt-minion[2964]: +        # tags is optional. This subsection can contain host_list, which is a
May  9 23:15:58 cmp02 salt-minion[2964]: +        # list of machine names. If the name of the local machine is found in
May  9 23:15:58 cmp02 salt-minion[2964]: +        # host_list, then the name of this subsection is used as a tag and is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # applied to the local machine as a 'host tag'. If this subsection is
May  9 23:15:58 cmp02 salt-minion[2964]: +        # empty (has no host_list), then the subsection name is always applied
May  9 23:15:58 cmp02 salt-minion[2964]: +        # as a 'host tag'.
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # Example
May  9 23:15:58 cmp02 salt-minion[2964]: +        # The host tag foo is given to all hosts, and the host tag
May  9 23:15:58 cmp02 salt-minion[2964]: +        # bar is given to the hosts named machine1 and machine2.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # tags { foo { } bar { host_list = [ "machine1", "machine2" ] } }
May  9 23:15:58 cmp02 salt-minion[2964]: +        #
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration section has variable name.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # This configuration section has an automatic default value.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # tag {
May  9 23:15:58 cmp02 salt-minion[2964]: +
May  9 23:15:58 cmp02 salt-minion[2964]: +                # Configuration option tags/<tag>/host_list.
May  9 23:15:58 cmp02 salt-minion[2964]: +                # A list of machine names.
May  9 23:15:58 cmp02 salt-minion[2964]: +                # These machine names are compared to the nodename returned
May  9 23:15:58 cmp02 salt-minion[2964]: +                # by uname(2). If the local machine name matches an entry in
May  9 23:15:58 cmp02 salt-minion[2964]: +                # this list, the name of the subsection is applied to the
May  9 23:15:58 cmp02 salt-minion[2964]: +                # machine as a 'host tag'.
May  9 23:15:58 cmp02 salt-minion[2964]: +                # This configuration option does not have a default value defined.
May  9 23:15:58 cmp02 salt-minion[2964]: +        # }
May  9 23:15:58 cmp02 salt-minion[2964]:  # }
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/lvm/lvm.conf] at time 23:15:57.684892 duration_in_ms=179.215
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Running state [lvm2-lvmetad] at time 23:15:57.688421
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing state service.running for lvm2-lvmetad
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'status', 'lvm2-lvmetad.service', '-n', '0'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'lvm2-lvmetad.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmetad.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: message repeated 2 times: [ [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmetad.service'] in directory '/root']
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'enable', 'lvm2-lvmetad.service'] in directory '/root'
May  9 23:15:58 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmetad.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] {'lvm2-lvmetad': True}
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Completed state [lvm2-lvmetad] at time 23:15:58.240047 duration_in_ms=551.626
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Running state [lvm2-lvmpolld] at time 23:15:58.241731
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing state service.running for lvm2-lvmpolld
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'status', 'lvm2-lvmpolld.service', '-n', '0'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'start', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 systemd[1]: Started /bin/systemctl start lvm2-lvmpolld.service.
May  9 23:15:58 cmp02 systemd[1]: Started LVM2 poll daemon.
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: message repeated 2 times: [ [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmpolld.service'] in directory '/root']
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'enable', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 systemd[1]: Started /bin/systemctl enable lvm2-lvmpolld.service.
May  9 23:15:58 cmp02 systemd[1]: Reloading.
May  9 23:15:58 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:58 cmp02 systemd[1]: Reloading.
May  9 23:15:58 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:58 cmp02 systemd[1]: Reloading.
May  9 23:15:58 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-lvmpolld.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] {'lvm2-lvmpolld': True}
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Completed state [lvm2-lvmpolld] at time 23:15:58.909076 duration_in_ms=667.345
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Running state [lvm2-monitor] at time 23:15:58.910484
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing state service.running for lvm2-monitor
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'status', 'lvm2-monitor.service', '-n', '0'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'lvm2-monitor.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-monitor.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] The service lvm2-monitor is already running
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Completed state [lvm2-monitor] at time 23:15:58.954307 duration_in_ms=43.822
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Running state [lvm2-monitor] at time 23:15:58.954686
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing state service.mod_watch for lvm2-monitor
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-active', 'lvm2-monitor.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'lvm2-monitor.service'] in directory '/root'
May  9 23:15:58 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'lvm2-monitor.service'] in directory '/root'
May  9 23:15:59 cmp02 systemd[1]: Started /bin/systemctl restart lvm2-monitor.service.
May  9 23:15:59 cmp02 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
May  9 23:15:59 cmp02 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May  9 23:15:59 cmp02 systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
May  9 23:15:59 cmp02 systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] {'lvm2-monitor': True}
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Completed state [lvm2-monitor] at time 23:15:59.054072 duration_in_ms=99.386
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Running state [/dev/vdb] at time 23:15:59.057386
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing state lvm.pv_present for /dev/vdb
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['pvdisplay', '-c', '/dev/vdb'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] Command '['pvdisplay', '-c', '/dev/vdb']' failed with return code: 5
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] stderr:   Failed to find physical volume "/dev/vdb".
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] retcode: 5
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['pvdisplay', '-c', '/dev/vdb'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] Command '['pvdisplay', '-c', '/dev/vdb']' failed with return code: 5
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] stderr:   Failed to find physical volume "/dev/vdb".
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] retcode: 5
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['pvcreate', '-y', '/dev/vdb'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['pvdisplay', '-c', '/dev/vdb'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['pvdisplay', '-c', '/dev/vdb'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] {'created': True}
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Completed state [/dev/vdb] at time 23:15:59.172854 duration_in_ms=115.468
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Running state [cinder-volume] at time 23:15:59.173881
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing state lvm.vg_present for cinder-volume
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['vgdisplay', '-c', 'cinder-volume'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] Command '['vgdisplay', '-c', 'cinder-volume']' failed with return code: 5
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] stderr:   Volume group "cinder-volume" not found
May  9 23:15:59 cmp02 salt-minion[2964]:   Cannot process volume group cinder-volume
May  9 23:15:59 cmp02 salt-minion[2964]: [ERROR   ] retcode: 5
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['vgcreate', 'cinder-volume', '/dev/vdb'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['vgdisplay', '-c', 'cinder-volume'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Executing command ['vgdisplay', '-c', 'cinder-volume'] in directory '/root'
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] {'created': {'Output from vgcreate': 'Volume group "cinder-volume" successfully created', 'cinder-volume': {'Total Physical Extents': '25599', 'Volume Group Name': 'cinder-volume', 'Actual Physical Volumes': '1', 'Maximum Physical Volumes': '0', 'Physical Extent Size (kB)': '4096', 'Volume Group Access': 'r/w', 'Free Physical Extents': '25599', 'UUID': 'ibJb9Q-w008-xeGp-jR5X-ux8i-OpfU-eqPRhH', 'Internal Volume Group Number': '-1', 'Open Logical Volumes': '0', 'Maximum Logical Volume Size': '-1', 'Current Logical Volumes': '0', 'Volume Group Size (kB)': '104853504', 'Current Physical Volumes': '1', 'Volume Group Status': '772', 'Maximum Logical Volumes': '0', 'Allocated Physical Extents': '0'}}}
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Completed state [cinder-volume] at time 23:15:59.240151 duration_in_ms=66.27
May  9 23:15:59 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231519791381
May  9 23:16:00 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509231600061479
May  9 23:16:00 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 6642
May  9 23:16:02 cmp02 salt-minion[2964]: [INFO    ] Loading fresh modules for state activity
May  9 23:16:02 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/network/init.sls'
May  9 23:16:02 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/network/hostname.sls'
May  9 23:16:02 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/network/host.sls'
May  9 23:16:02 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/network/interface.sls'
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/network/proxy.sls'
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/hostname] at time 23:16:03.351442
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/hostname
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/hostname'
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] File /etc/hostname is in the correct state
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/hostname] at time 23:16:03.381590 duration_in_ms=30.149
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [hostname cmp02] at time 23:16:03.382608
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state cmd.wait for hostname cmp02
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] No changes made for hostname cmp02
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [hostname cmp02] at time 23:16:03.383331 duration_in_ms=0.723
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cfg] at time 23:16:03.384797
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cfg
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cfg'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cfg] at time 23:16:03.386113 duration_in_ms=1.315
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cfg.mcp-pike-ovn-noha.local] at time 23:16:03.386351
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cfg.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cfg.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cfg.mcp-pike-ovn-noha.local] at time 23:16:03.387550 duration_in_ms=1.199
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [gtw01] at time 23:16:03.387781
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for gtw01
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'gtw01'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [gtw01] at time 23:16:03.388921 duration_in_ms=1.14
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [gtw01.mcp-pike-ovn-noha.local] at time 23:16:03.389149
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for gtw01.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'gtw01.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [gtw01.mcp-pike-ovn-noha.local] at time 23:16:03.390592 duration_in_ms=1.442
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cmp01] at time 23:16:03.391418
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cmp01
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cmp01'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cmp01] at time 23:16:03.392597 duration_in_ms=1.178
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cmp01.mcp-pike-ovn-noha.local] at time 23:16:03.392828
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cmp01.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cmp01.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cmp01.mcp-pike-ovn-noha.local] at time 23:16:03.395320 duration_in_ms=2.492
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [ctl01] at time 23:16:03.395823
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for ctl01
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'ctl01'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [ctl01] at time 23:16:03.396998 duration_in_ms=1.175
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [ctl01.mcp-pike-ovn-noha.local] at time 23:16:03.397783
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for ctl01.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'ctl01.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [ctl01.mcp-pike-ovn-noha.local] at time 23:16:03.398971 duration_in_ms=1.187
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [ctl] at time 23:16:03.399218
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for ctl
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'ctl'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [ctl] at time 23:16:03.400386 duration_in_ms=1.169
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [ctl.mcp-pike-ovn-noha.local] at time 23:16:03.400612
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for ctl.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'ctl.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [ctl.mcp-pike-ovn-noha.local] at time 23:16:03.401777 duration_in_ms=1.165
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cmp02] at time 23:16:03.402004
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cmp02
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cmp02'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cmp02] at time 23:16:03.403780 duration_in_ms=1.776
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cmp02.mcp-pike-ovn-noha.local] at time 23:16:03.404003
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cmp02.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cmp02.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cmp02.mcp-pike-ovn-noha.local] at time 23:16:03.406115 duration_in_ms=2.112
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cfg01] at time 23:16:03.406339
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cfg01
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cfg01'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cfg01] at time 23:16:03.408195 duration_in_ms=1.855
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [cfg01.mcp-pike-ovn-noha.local] at time 23:16:03.408424
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state host.present for cfg01.mcp-pike-ovn-noha.local
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] {'host': 'cfg01.mcp-pike-ovn-noha.local'}
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Completed state [cfg01.mcp-pike-ovn-noha.local] at time 23:16:03.409672 duration_in_ms=1.248
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Running state [linux_network_bridge_pkgs] at time 23:16:03.910790
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing state pkg.installed for linux_network_bridge_pkgs
May  9 23:16:03 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:16:04 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'openvswitch-switch'] in directory '/root'
May  9 23:16:04 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'bridge-utils'] in directory '/root'
May  9 23:16:04 cmp02 salt-minion[2964]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:16:07 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:16:07 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'openvswitch-switch', 'bridge-utils'] in directory '/root'
May  9 23:16:07 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install openvswitch-switch bridge-utils.
May  9 23:16:09 cmp02 systemd[1]: Reloading.
May  9 23:16:09 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:09 cmp02 systemd[1]: Reloading.
May  9 23:16:10 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:10 cmp02 systemd[1]: Reloading.
May  9 23:16:10 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231610102407
May  9 23:16:10 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 7745
May  9 23:16:10 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231610102407
May  9 23:16:10 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:10 cmp02 systemd[1]: Reloading.
May  9 23:16:10 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:10 cmp02 systemd[1]: Starting Open vSwitch Internal Unit...
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * /etc/openvswitch/conf.db does not exist
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * Creating empty database /etc/openvswitch/conf.db
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * Starting ovsdb-server
May  9 23:16:10 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait -- init -- set Open_vSwitch . db-version=7.15.0
May  9 23:16:10 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait set Open_vSwitch . ovs-version=2.8.0 "external-ids:system-id=\"a765059e-e69c-4ec4-81ac-f541e3b69dfe\"" "external-ids:hostname=\"cmp02\"" "external-ids:rundir=\"/var/run/openvswitch\"" "system-type=\"ubuntu\"" "system-version=\"16.04\""
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * Configuring Open vSwitch system IDs
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * Inserting openvswitch module
May  9 23:16:10 cmp02 kernel: [  374.281151] openvswitch: Open vSwitch switching datapath
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * Starting ovs-vswitchd
May  9 23:16:10 cmp02 ovs-ctl[7809]:  * Enabling remote OVSDB managers
May  9 23:16:10 cmp02 systemd[1]: Started Open vSwitch Internal Unit.
May  9 23:16:10 cmp02 systemd[1]: Starting Open vSwitch...
May  9 23:16:10 cmp02 systemd[1]: Started Open vSwitch.
May  9 23:16:10 cmp02 systemd[1]: Reloading.
May  9 23:16:10 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:10 cmp02 systemd[1]: Reloading.
May  9 23:16:10 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Made the following changes:
May  9 23:16:12 cmp02 salt-minion[2964]: 'openvswitch-switch' changed from 'absent' to '2.8.0-1~u16.04+mcp2'
May  9 23:16:12 cmp02 salt-minion[2964]: 'bridge-utils' changed from 'absent' to '1.5-9ubuntu1'
May  9 23:16:12 cmp02 salt-minion[2964]: 'openvswitch-common' changed from 'absent' to '2.8.0-1~u16.04+mcp2'
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Loading fresh modules for state activity
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Completed state [linux_network_bridge_pkgs] at time 23:16:12.331569 duration_in_ms=8420.779
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces.d/50-cloud-init.cfg] at time 23:16:12.336705
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/network/interfaces.d/50-cloud-init.cfg
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] {'removed': '/etc/network/interfaces.d/50-cloud-init.cfg'}
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces.d/50-cloud-init.cfg] at time 23:16:12.342582 duration_in_ms=5.876
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Running state [ens5] at time 23:16:12.357807
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for ens5
May  9 23:16:12 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'ens5'] in directory '/root'
May  9 23:16:12 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:12 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface ens5 is up'}
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] Completed state [ens5] at time 23:16:13.156819 duration_in_ms=799.012
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] Running state [br-mesh] at time 23:16:13.158369
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for br-mesh
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'bridge-utils'] in directory '/root'
May  9 23:16:13 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install bridge-utils.
May  9 23:16:13 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'br-mesh'] in directory '/root'
May  9 23:16:14 cmp02 kernel: [  377.863401] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
May  9 23:16:14 cmp02 systemd-udevd[8146]: Could not generate persistent MAC address for br-mesh: No such file or directory
May  9 23:16:14 cmp02 kernel: [  377.874412] br-mesh: port 1(ens5) entered blocking state
May  9 23:16:14 cmp02 kernel: [  377.874416] br-mesh: port 1(ens5) entered disabled state
May  9 23:16:14 cmp02 kernel: [  377.874652] device ens5 entered promiscuous mode
May  9 23:16:14 cmp02 kernel: [  377.877154] br-mesh: port 1(ens5) entered blocking state
May  9 23:16:14 cmp02 kernel: [  377.877157] br-mesh: port 1(ens5) entered forwarding state
May  9 23:16:14 cmp02 systemd[1]: Started ifup for br-mesh.
May  9 23:16:14 cmp02 sh[8201]: ifup: waiting for lock on /run/network/ifstate.br-mesh
May  9 23:16:14 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/br-mesh.
May  9 23:16:14 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:14 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:14 cmp02 sh[8201]: ifup: interface br-mesh already configured
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface br-mesh is up'}
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Completed state [br-mesh] at time 23:16:14.920058 duration_in_ms=1761.691
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:14.920587
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing state file.prepend for /etc/network/interfaces
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:16:14 cmp02 salt-minion[2964]: ---
May  9 23:16:14 cmp02 salt-minion[2964]: +++
May  9 23:16:14 cmp02 salt-minion[2964]: @@ -1,3 +1,6 @@
May  9 23:16:14 cmp02 salt-minion[2964]: +source /etc/network/interfaces.d/*
May  9 23:16:14 cmp02 salt-minion[2964]: +# Workaround for Upstream-Bug: https://github.com/saltstack/salt/issues/40262
May  9 23:16:14 cmp02 salt-minion[2964]: +source /etc/network/interfaces.u/*
May  9 23:16:14 cmp02 salt-minion[2964]:  auto lo
May  9 23:16:14 cmp02 salt-minion[2964]:  iface lo inet loopback
May  9 23:16:14 cmp02 salt-minion[2964]:  auto ens5
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:14.927322 duration_in_ms=6.735
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces.u/ifcfg-float-to-ex] at time 23:16:14.927661
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /etc/network/interfaces.u/ifcfg-float-to-ex
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'linux/files/ovs_port'
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:16:14 cmp02 salt-minion[2964]: New file
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces.u/ifcfg-float-to-ex] at time 23:16:14.963956 duration_in_ms=36.295
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:14.964302
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing state file.replace for /etc/network/interfaces
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] No changes needed to be made
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:14.966858 duration_in_ms=2.556
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:14.967212
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing state file.replace for /etc/network/interfaces
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] No changes needed to be made
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:14.969154 duration_in_ms=1.942
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Running state [br-floating] at time 23:16:14.974095
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing state openvswitch_bridge.present for br-floating
May  9 23:16:14 cmp02 salt-minion[2964]: [INFO    ] Executing command 'ovs-vsctl br-exists br-floating' in directory '/root'
May  9 23:16:15 cmp02 salt-minion[2964]: [ERROR   ] Command 'ovs-vsctl br-exists br-floating' failed with return code: 2
May  9 23:16:15 cmp02 salt-minion[2964]: [ERROR   ] retcode: 2
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing command 'ovs-vsctl --may-exist add-br br-floating' in directory '/root'
May  9 23:16:15 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --may-exist add-br br-floating
May  9 23:16:15 cmp02 systemd-udevd[8311]: Could not generate persistent MAC address for ovs-system: No such file or directory
May  9 23:16:15 cmp02 kernel: [  378.819464] device ovs-system entered promiscuous mode
May  9 23:16:15 cmp02 kernel: [  378.847435] device br-floating entered promiscuous mode
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Made the following changes:
May  9 23:16:15 cmp02 salt-minion[2964]: 'br-floating' changed from 'Bridge br-floating does not exist.' to 'Bridge br-floating created'
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Completed state [br-floating] at time 23:16:15.061343 duration_in_ms=87.247
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:15.061688
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing state file.prepend for /etc/network/interfaces
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] File /etc/network/interfaces is in correct state
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:15.064120 duration_in_ms=2.432
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Running state [ifup float-to-ex] at time 23:16:15.065690
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing state cmd.run for ifup float-to-ex
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing command 'ip link show float-to-ex | grep -q '\<UP\>'' in directory '/root'
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing command 'ifup float-to-ex' in directory '/root'
May  9 23:16:15 cmp02 systemd[1]: Started Open vSwitch.
May  9 23:16:15 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --may-exist add-port br-floating float-to-ex -- set Interface float-to-ex type=internal --
May  9 23:16:15 cmp02 systemd-udevd[8501]: Could not generate persistent MAC address for float-to-ex: No such file or directory
May  9 23:16:15 cmp02 kernel: [  379.137906] device float-to-ex entered promiscuous mode
May  9 23:16:15 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:15 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:15 cmp02 systemd[1]: Started ifup for float-to-ex.
May  9 23:16:15 cmp02 sh[8593]: ifup: waiting for lock on /run/network/ifstate.float-to-ex
May  9 23:16:15 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/float-to-ex.
May  9 23:16:15 cmp02 sh[8593]: ifup: interface float-to-ex already configured
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] {'pid': 8422, 'retcode': 0, 'stderr': '', 'stdout': ''}
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Completed state [ifup float-to-ex] at time 23:16:15.408396 duration_in_ms=342.705
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Running state [ens3] at time 23:16:15.410991
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for ens3
May  9 23:16:15 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifdown', 'ens3'] in directory '/root'
May  9 23:16:15 cmp02 dhclient[8632]: Killed old client process
May  9 23:16:16 cmp02 dhclient[8632]: Internet Systems Consortium DHCP Client 4.3.3
May  9 23:16:16 cmp02 dhclient[8632]: Copyright 2004-2015 Internet Systems Consortium.
May  9 23:16:16 cmp02 dhclient[8632]: All rights reserved.
May  9 23:16:16 cmp02 dhclient[8632]: For info, please visit https://www.isc.org/software/dhcp/
May  9 23:16:16 cmp02 dhclient[8632]: 
May  9 23:16:16 cmp02 dhclient[8632]: Listening on LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:16 cmp02 dhclient[8632]: Sending on   LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:16 cmp02 dhclient[8632]: Sending on   Socket/fallback
May  9 23:16:16 cmp02 dhclient[8632]: DHCPRELEASE on ens3 to 192.168.11.1 port 67 (xid=0x60dbc55a)
May  9 23:16:16 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'ens3'] in directory '/root'
May  9 23:16:16 cmp02 dhclient[8683]: Internet Systems Consortium DHCP Client 4.3.3
May  9 23:16:16 cmp02 dhclient[8683]: Copyright 2004-2015 Internet Systems Consortium.
May  9 23:16:16 cmp02 dhclient[8683]: All rights reserved.
May  9 23:16:16 cmp02 dhclient[8683]: For info, please visit https://www.isc.org/software/dhcp/
May  9 23:16:16 cmp02 dhclient[8683]: 
May  9 23:16:16 cmp02 dhclient[8683]: Listening on LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:16 cmp02 dhclient[8683]: Sending on   LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:16 cmp02 dhclient[8683]: Sending on   Socket/fallback
May  9 23:16:16 cmp02 dhclient[8683]: DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0xd951aa44)
May  9 23:16:16 cmp02 dhclient[8683]: DHCPREQUEST of 192.168.11.50 on ens3 to 255.255.255.255 port 67 (xid=0x44aa51d9)
May  9 23:16:16 cmp02 dhclient[8683]: DHCPOFFER of 192.168.11.50 from 192.168.11.1
May  9 23:16:16 cmp02 dhclient[8683]: DHCPACK of 192.168.11.50 from 192.168.11.1
May  9 23:16:16 cmp02 dhclient[8683]: bound to 192.168.11.50 -- renewal in 1644 seconds.
May  9 23:16:16 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:16 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:16 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface ens3 restart to validate'}
May  9 23:16:16 cmp02 salt-minion[2964]: [INFO    ] Completed state [ens3] at time 23:16:16.670476 duration_in_ms=1259.484
May  9 23:16:16 cmp02 salt-minion[2964]: [INFO    ] Running state [ens4] at time 23:16:16.670907
May  9 23:16:16 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for ens4
May  9 23:16:16 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'ens4'] in directory '/root'
May  9 23:16:16 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:16 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface ens4 is up'}
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Completed state [ens4] at time 23:16:17.348796 duration_in_ms=677.889
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Running state [ens6] at time 23:16:17.349222
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for ens6
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'ens6'] in directory '/root'
May  9 23:16:17 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:17 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface ens6 is up'}
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Completed state [ens6] at time 23:16:17.993189 duration_in_ms=643.966
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Running state [br-mgmt] at time 23:16:17.994355
May  9 23:16:17 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for br-mgmt
May  9 23:16:18 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:16:18 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'bridge-utils'] in directory '/root'
May  9 23:16:18 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install bridge-utils.
May  9 23:16:18 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:16:18 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'br-mgmt'] in directory '/root'
May  9 23:16:18 cmp02 systemd-udevd[9013]: Could not generate persistent MAC address for br-mgmt: No such file or directory
May  9 23:16:18 cmp02 kernel: [  382.323845] br-mgmt: port 1(ens4) entered blocking state
May  9 23:16:18 cmp02 kernel: [  382.323849] br-mgmt: port 1(ens4) entered disabled state
May  9 23:16:18 cmp02 kernel: [  382.324317] device ens4 entered promiscuous mode
May  9 23:16:18 cmp02 kernel: [  382.326881] br-mgmt: port 1(ens4) entered blocking state
May  9 23:16:18 cmp02 kernel: [  382.326883] br-mgmt: port 1(ens4) entered forwarding state
May  9 23:16:18 cmp02 systemd[1]: Started ifup for br-mgmt.
May  9 23:16:18 cmp02 sh[9105]: ifup: waiting for lock on /run/network/ifstate.br-mgmt
May  9 23:16:18 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/br-mgmt.
May  9 23:16:18 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:18 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:18 cmp02 sh[9105]: ifup: interface br-mgmt already configured
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface br-mgmt is up'}
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Completed state [br-mgmt] at time 23:16:19.421395 duration_in_ms=1427.038
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Running state [br-ex] at time 23:16:19.424200
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Executing state network.managed for br-ex
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'bridge-utils'] in directory '/root'
May  9 23:16:19 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install bridge-utils.
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:16:19 cmp02 salt-minion[2964]: [INFO    ] Executing command ['ifup', 'br-ex'] in directory '/root'
May  9 23:16:19 cmp02 systemd-udevd[9269]: Could not generate persistent MAC address for br-ex: No such file or directory
May  9 23:16:19 cmp02 kernel: [  383.742742] br-ex: port 1(ens6) entered blocking state
May  9 23:16:19 cmp02 kernel: [  383.742745] br-ex: port 1(ens6) entered disabled state
May  9 23:16:19 cmp02 kernel: [  383.742830] device ens6 entered promiscuous mode
May  9 23:16:19 cmp02 kernel: [  383.745644] br-ex: port 2(float-to-ex) entered blocking state
May  9 23:16:19 cmp02 kernel: [  383.745646] br-ex: port 2(float-to-ex) entered disabled state
May  9 23:16:19 cmp02 kernel: [  383.749635] br-ex: port 2(float-to-ex) entered blocking state
May  9 23:16:19 cmp02 kernel: [  383.749639] br-ex: port 2(float-to-ex) entered forwarding state
May  9 23:16:19 cmp02 kernel: [  383.749692] br-ex: port 1(ens6) entered blocking state
May  9 23:16:19 cmp02 kernel: [  383.749696] br-ex: port 1(ens6) entered forwarding state
May  9 23:16:20 cmp02 systemd[1]: Started ifup for br-ex.
May  9 23:16:20 cmp02 sh[9377]: ifup: waiting for lock on /run/network/ifstate.br-ex
May  9 23:16:20 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/br-ex.
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231620121407
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 9391
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231620121407
May  9 23:16:20 cmp02 systemd[1]: Reloading OpenBSD Secure Shell server.
May  9 23:16:20 cmp02 systemd[1]: Reloaded OpenBSD Secure Shell server.
May  9 23:16:20 cmp02 sh[9377]: ifup: interface br-ex already configured
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] {'interface': 'Added network interface.', 'status': 'Interface br-ex is up'}
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Completed state [br-ex] at time 23:16:20.857848 duration_in_ms=1433.647
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:20.858134
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Executing state file.replace for /etc/network/interfaces
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] No changes needed to be made
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:20.860912 duration_in_ms=2.778
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:20.861141
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Executing state file.replace for /etc/network/interfaces
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] No changes needed to be made
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:20.863463 duration_in_ms=2.322
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/network/interfaces] at time 23:16:20.863703
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Executing state file.prepend for /etc/network/interfaces
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:16:20 cmp02 salt-minion[2964]: ---
May  9 23:16:20 cmp02 salt-minion[2964]: +++
May  9 23:16:20 cmp02 salt-minion[2964]: @@ -1,3 +1,6 @@
May  9 23:16:20 cmp02 salt-minion[2964]: +source /etc/network/interfaces.d/*
May  9 23:16:20 cmp02 salt-minion[2964]: +# Workaround for Upstream-Bug: https://github.com/saltstack/salt/issues/40262
May  9 23:16:20 cmp02 salt-minion[2964]: +source /etc/network/interfaces.u/*
May  9 23:16:20 cmp02 salt-minion[2964]:  auto lo
May  9 23:16:20 cmp02 salt-minion[2964]:  iface lo inet loopback
May  9 23:16:20 cmp02 salt-minion[2964]:  auto ens5
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/network/interfaces] at time 23:16:20.865710 duration_in_ms=2.007
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/profile.d/proxy.sh] at time 23:16:20.865935
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/profile.d/proxy.sh
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] File /etc/profile.d/proxy.sh is not present
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/profile.d/proxy.sh] at time 23:16:20.866636 duration_in_ms=0.7
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Running state [/etc/apt/apt.conf.d/95proxies] at time 23:16:20.866863
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Executing state file.absent for /etc/apt/apt.conf.d/95proxies
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] File /etc/apt/apt.conf.d/95proxies is not present
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Completed state [/etc/apt/apt.conf.d/95proxies] at time 23:16:20.867909 duration_in_ms=1.046
May  9 23:16:20 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231600061479
May  9 23:16:24 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509231624627153
May  9 23:16:24 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 9517
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] Loading fresh modules for state activity
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'opnfv/route_wrapper.sls'
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] Running state [/usr/local/sbin/route] at time 23:16:27.348168
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] Executing state file.managed for /usr/local/sbin/route
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] File changed:
May  9 23:16:27 cmp02 salt-minion[2964]: New file
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] Completed state [/usr/local/sbin/route] at time 23:16:27.360204 duration_in_ms=12.036
May  9 23:16:27 cmp02 salt-minion[2964]: [INFO    ] Returning information for job: 20180509231624627153
May  9 23:16:28 cmp02 salt-minion[2964]: [INFO    ] User sudo_ubuntu Executing command system.reboot with jid 20180509231628032781
May  9 23:16:28 cmp02 salt-minion[2964]: [INFO    ] Starting a new job with PID 9534
May  9 23:16:28 cmp02 salt-minion[2964]: [INFO    ] Executing command ['shutdown', '-r', 'now'] in directory '/root'
May  9 23:16:28 cmp02 systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks...
May  9 23:16:28 cmp02 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1164" x-info="http://www.rsyslog.com"] exiting on signal 15.
May  9 23:16:39 cmp02 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="2688" x-info="http://www.rsyslog.com"] start
May  9 23:16:39 cmp02 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
May  9 23:16:39 cmp02 rsyslogd: rsyslogd's groupid changed to 108
May  9 23:16:39 cmp02 rsyslogd: rsyslogd's userid changed to 104
May  9 23:16:39 cmp02 kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x42/0x507 with crng_init=0
May  9 23:16:39 cmp02 kernel: [    0.000000] Linux version 4.13.0-41-generic (buildd@lgw01-amd64-028) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #46~16.04.1-Ubuntu SMP Thu May 3 10:06:43 UTC 2018 (Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16)
May  9 23:16:39 cmp02 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=dfb884db-c6ad-4c7a-8075-98cf640a2892 ro console=tty1 console=ttyS0
May  9 23:16:39 cmp02 kernel: [    0.000000] KERNEL supported cpus:
May  9 23:16:39 cmp02 kernel: [    0.000000]   Intel GenuineIntel
May  9 23:16:39 cmp02 kernel: [    0.000000]   AMD AuthenticAMD
May  9 23:16:39 cmp02 kernel: [    0.000000]   Centaur CentaurHauls
May  9 23:16:39 cmp02 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May  9 23:16:39 cmp02 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May  9 23:16:39 cmp02 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May  9 23:16:39 cmp02 kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May  9 23:16:39 cmp02 kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
May  9 23:16:39 cmp02 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffdefff] usable
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000bffdf000-0x00000000bfffffff] reserved
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
May  9 23:16:39 cmp02 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000023fffffff] usable
May  9 23:16:39 cmp02 kernel: [    0.000000] NX (Execute Disable) protection: active
May  9 23:16:39 cmp02 kernel: [    0.000000] random: fast init done
May  9 23:16:39 cmp02 kernel: [    0.000000] SMBIOS 2.8 present.
May  9 23:16:39 cmp02 kernel: [    0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
May  9 23:16:39 cmp02 kernel: [    0.000000] Hypervisor detected: KVM
May  9 23:16:39 cmp02 kernel: [    0.000000] tsc: Fast TSC calibration failed
May  9 23:16:39 cmp02 kernel: [    0.000000] tsc: Unable to calibrate against PIT
May  9 23:16:39 cmp02 kernel: [    0.000000] tsc: No reference (HPET/PMTIMER) available
May  9 23:16:39 cmp02 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
May  9 23:16:39 cmp02 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
May  9 23:16:39 cmp02 kernel: [    0.000000] e820: last_pfn = 0x240000 max_arch_pfn = 0x400000000
May  9 23:16:39 cmp02 kernel: [    0.000000] MTRR default type: write-back
May  9 23:16:39 cmp02 kernel: [    0.000000] MTRR fixed ranges enabled:
May  9 23:16:39 cmp02 kernel: [    0.000000]   00000-9FFFF write-back
May  9 23:16:39 cmp02 kernel: [    0.000000]   A0000-BFFFF uncachable
May  9 23:16:39 cmp02 kernel: [    0.000000]   C0000-FFFFF write-protect
May  9 23:16:39 cmp02 kernel: [    0.000000] MTRR variable ranges enabled:
May  9 23:16:39 cmp02 kernel: [    0.000000]   0 base 00C0000000 mask FFC0000000 uncachable
May  9 23:16:39 cmp02 kernel: [    0.000000]   1 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000]   2 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000]   3 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000]   4 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000]   5 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000]   6 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000]   7 disabled
May  9 23:16:39 cmp02 kernel: [    0.000000] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
May  9 23:16:39 cmp02 kernel: [    0.000000] e820: last_pfn = 0xbffdf max_arch_pfn = 0x400000000
May  9 23:16:39 cmp02 kernel: [    0.000000] found SMP MP-table at [mem 0x000f65a0-0x000f65af] mapped at [ffff92cd000f65a0]
May  9 23:16:39 cmp02 kernel: [    0.000000] Scanning 1 areas for low memory corruption
May  9 23:16:39 cmp02 kernel: [    0.000000] Base memory trampoline at [ffff92cd00099000] 99000 size 24576
May  9 23:16:39 cmp02 kernel: [    0.000000] Using GB pages for direct mapping
May  9 23:16:39 cmp02 kernel: [    0.000000] BRK [0x19572c000, 0x19572cfff] PGTABLE
May  9 23:16:39 cmp02 kernel: [    0.000000] BRK [0x19572d000, 0x19572dfff] PGTABLE
May  9 23:16:39 cmp02 kernel: [    0.000000] BRK [0x19572e000, 0x19572efff] PGTABLE
May  9 23:16:39 cmp02 kernel: [    0.000000] BRK [0x19572f000, 0x19572ffff] PGTABLE
May  9 23:16:39 cmp02 kernel: [    0.000000] BRK [0x195730000, 0x195730fff] PGTABLE
May  9 23:16:39 cmp02 kernel: [    0.000000] BRK [0x195731000, 0x195731fff] PGTABLE
May  9 23:16:39 cmp02 kernel: [    0.000000] RAMDISK: [mem 0x32298000-0x35143fff]
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: Early table checksum verification disabled
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: RSDP 0x00000000000F6550 000014 (v00 BOCHS )
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: RSDT 0x00000000BFFE14A5 000030 (v01 BOCHS  BXPCRSDT 00000001 BXPC 00000001)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: FACP 0x00000000BFFE0914 000074 (v01 BOCHS  BXPCFACP 00000001 BXPC 00000001)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: DSDT 0x00000000BFFDFD40 000BD4 (v01 BOCHS  BXPCDSDT 00000001 BXPC 00000001)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: FACS 0x00000000BFFDFD00 000040
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: SSDT 0x00000000BFFE0988 000A85 (v01 BOCHS  BXPCSSDT 00000001 BXPC 00000001)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: APIC 0x00000000BFFE140D 000098 (v01 BOCHS  BXPCAPIC 00000001 BXPC 00000001)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
May  9 23:16:39 cmp02 kernel: [    0.000000] No NUMA configuration found
May  9 23:16:39 cmp02 kernel: [    0.000000] Faking a node at [mem 0x0000000000000000-0x000000023fffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] NODE_DATA(0) allocated [mem 0x23ffd5000-0x23fffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
May  9 23:16:39 cmp02 kernel: [    0.000000] kvm-clock: cpu 0, msr 2:3ff55001, primary cpu clock
May  9 23:16:39 cmp02 kernel: [    0.000000] kvm-clock: using sched offset of 397460170122 cycles
May  9 23:16:39 cmp02 kernel: [    0.000000] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
May  9 23:16:39 cmp02 kernel: [    0.000000] Zone ranges:
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000]   Normal   [mem 0x0000000100000000-0x000000023fffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000]   Device   empty
May  9 23:16:39 cmp02 kernel: [    0.000000] Movable zone start for each node
May  9 23:16:39 cmp02 kernel: [    0.000000] Early memory node ranges
May  9 23:16:39 cmp02 kernel: [    0.000000]   node   0: [mem 0x0000000000001000-0x000000000009efff]
May  9 23:16:39 cmp02 kernel: [    0.000000]   node   0: [mem 0x0000000000100000-0x00000000bffdefff]
May  9 23:16:39 cmp02 kernel: [    0.000000]   node   0: [mem 0x0000000100000000-0x000000023fffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000023fffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] On node 0 totalpages: 2097021
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA zone: 21 pages reserved
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA zone: 3998 pages, LIFO batch:0
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA32 zone: 12224 pages used for memmap
May  9 23:16:39 cmp02 kernel: [    0.000000]   DMA32 zone: 782303 pages, LIFO batch:31
May  9 23:16:39 cmp02 kernel: [    0.000000]   Normal zone: 20480 pages used for memmap
May  9 23:16:39 cmp02 kernel: [    0.000000]   Normal zone: 1310720 pages, LIFO batch:31
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x608
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
May  9 23:16:39 cmp02 kernel: [    0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: IRQ0 used by override.
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: IRQ5 used by override.
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: IRQ9 used by override.
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: IRQ10 used by override.
May  9 23:16:39 cmp02 kernel: [    0.000000] ACPI: IRQ11 used by override.
May  9 23:16:39 cmp02 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
May  9 23:16:39 cmp02 kernel: [    0.000000] smpboot: Allowing 5 CPUs, 0 hotplug CPUs
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xbffdf000-0xbfffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xc0000000-0xfeffbfff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfeffc000-0xfeffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xfffbffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfffc0000-0xffffffff]
May  9 23:16:39 cmp02 kernel: [    0.000000] e820: [mem 0xc0000000-0xfeffbfff] available for PCI devices
May  9 23:16:39 cmp02 kernel: [    0.000000] Booting paravirtualized kernel on KVM
May  9 23:16:39 cmp02 systemd-modules-load[421]: Inserted module 'iscsi_tcp'
May  9 23:16:39 cmp02 loadkeys[423]: Loading /etc/console-setup/cached.kmap.gz
May  9 23:16:39 cmp02 systemd[1]: Started Set console keymap.
May  9 23:16:39 cmp02 systemd[1]: Started Load/Save Random Seed.
May  9 23:16:39 cmp02 systemd[1]: Starting Flush Journal to Persistent Storage...
May  9 23:16:39 cmp02 systemd-modules-load[421]: Inserted module 'ib_iser'
May  9 23:16:39 cmp02 systemd[1]: Started Flush Journal to Persistent Storage.
May  9 23:16:39 cmp02 systemd[1]: Started udev Coldplug all Devices.
May  9 23:16:39 cmp02 systemd-modules-load[421]: Inserted module 'nf_conntrack'
May  9 23:16:39 cmp02 systemd[1]: Started Load Kernel Modules.
May  9 23:16:39 cmp02 systemd[1]: Mounting Configuration File System...
May  9 23:16:39 cmp02 systemd[1]: Starting Apply Kernel Variables...
May  9 23:16:39 cmp02 systemd[1]: Mounting FUSE Control File System...
May  9 23:16:39 cmp02 systemd[1]: Mounted Configuration File System.
May  9 23:16:39 cmp02 systemd[1]: Mounted FUSE Control File System.
May  9 23:16:39 cmp02 systemd[1]: Started Create Static Device Nodes in /dev.
May  9 23:16:39 cmp02 systemd[1]: Starting udev Kernel Device Manager...
May  9 23:16:39 cmp02 kernel: [    0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
May  9 23:16:39 cmp02 systemd[1]: Started Apply Kernel Variables.
May  9 23:16:39 cmp02 kernel: [    0.000000] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:5 nr_cpu_ids:5 nr_node_ids:1
May  9 23:16:39 cmp02 kernel: [    0.000000] percpu: Embedded 45 pages/cpu @ffff92cf37000000 s146584 r8192 d29544 u1048576
May  9 23:16:39 cmp02 kernel: [    0.000000] pcpu-alloc: s146584 r8192 d29544 u1048576 alloc=1*2097152
May  9 23:16:39 cmp02 kernel: [    0.000000] pcpu-alloc: [0] 0 1 [0] 2 3 [0] 4 - 
May  9 23:16:39 cmp02 systemd[1]: Started udev Kernel Device Manager.
May  9 23:16:39 cmp02 kernel: [    0.000000] KVM setup async PF for cpu 0
May  9 23:16:39 cmp02 kernel: [    0.000000] kvm-stealtime: cpu 0, msr 2370161c0
May  9 23:16:39 cmp02 kernel: [    0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
May  9 23:16:39 cmp02 kernel: [    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 2064232
May  9 23:16:39 cmp02 kernel: [    0.000000] Policy zone: Normal
May  9 23:16:39 cmp02 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
May  9 23:16:39 cmp02 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=dfb884db-c6ad-4c7a-8075-98cf640a2892 ro console=tty1 console=ttyS0
May  9 23:16:39 cmp02 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
May  9 23:16:39 cmp02 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
May  9 23:16:39 cmp02 systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May  9 23:16:39 cmp02 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
May  9 23:16:39 cmp02 kernel: [    0.000000] Memory: 8115668K/8388084K available (12300K kernel code, 2481K rwdata, 4008K rodata, 2368K init, 2372K bss, 272416K reserved, 0K cma-reserved)
May  9 23:16:39 cmp02 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=5, Nodes=1
May  9 23:16:39 cmp02 systemd[1]: Reached target Local File Systems (Pre).
May  9 23:16:39 cmp02 kernel: [    0.000000] Kernel/User page tables isolation: enabled
May  9 23:16:39 cmp02 kernel: [    0.000000] ftrace: allocating 37858 entries in 148 pages
May  9 23:16:39 cmp02 kernel: [    0.004000] Hierarchical RCU implementation.
May  9 23:16:39 cmp02 kernel: [    0.004000] 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=5.
May  9 23:16:39 cmp02 kernel: [    0.004000] 	Tasks RCU enabled.
May  9 23:16:39 cmp02 systemd[1]: Reached target Local File Systems.
May  9 23:16:39 cmp02 kernel: [    0.004000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=5
May  9 23:16:39 cmp02 kernel: [    0.004000] NR_IRQS: 524544, nr_irqs: 464, preallocated irqs: 16
May  9 23:16:39 cmp02 kernel: [    0.004000] Console: colour VGA+ 80x25
May  9 23:16:39 cmp02 systemd[1]: Starting LSB: AppArmor initialization...
May  9 23:16:39 cmp02 kernel: [    0.004000] console [tty1] enabled
May  9 23:16:39 cmp02 kernel: [    0.004000] console [ttyS0] enabled
May  9 23:16:39 cmp02 kernel: [    0.004006] tsc: Detected 2799.994 MHz processor
May  9 23:16:39 cmp02 kernel: [    0.005079] Calibrating delay loop (skipped) preset value.. 5599.98 BogoMIPS (lpj=11199976)
May  9 23:16:39 cmp02 systemd[1]: Starting Set console font and keymap...
May  9 23:16:39 cmp02 kernel: [    0.006480] pid_max: default: 32768 minimum: 301
May  9 23:16:39 cmp02 kernel: [    0.008013] ACPI: Core revision 20170531
May  9 23:16:39 cmp02 kernel: [    0.009829] ACPI: 2 ACPI AML tables successfully acquired and loaded
May  9 23:16:39 cmp02 kernel: [    0.011229] Security Framework initialized
May  9 23:16:39 cmp02 kernel: [    0.012004] Yama: becoming mindful.
May  9 23:16:39 cmp02 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
May  9 23:16:39 cmp02 kernel: [    0.012907] AppArmor: AppArmor initialized
May  9 23:16:39 cmp02 kernel: [    0.016306] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
May  9 23:16:39 cmp02 kernel: [    0.018762] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
May  9 23:16:39 cmp02 systemd[1]: Starting Create Volatile Files and Directories...
May  9 23:16:39 cmp02 kernel: [    0.020032] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
May  9 23:16:39 cmp02 kernel: [    0.021511] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
May  9 23:16:39 cmp02 kernel: [    0.023457] FEATURE SPEC_CTRL Not Present
May  9 23:16:39 cmp02 kernel: [    0.024017] mce: CPU supports 10 MCE banks
May  9 23:16:39 cmp02 systemd-tmpfiles[513]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
May  9 23:16:39 cmp02 kernel: [    0.025051] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
May  9 23:16:39 cmp02 kernel: [    0.026235] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
May  9 23:16:39 cmp02 kernel: [    0.028004] Spectre V2 mitigation: Mitigation: Full generic retpoline
May  9 23:16:39 cmp02 kernel: [    0.029666] Spectre V2 mitigation: Speculation control IBPB not-supported IBRS not-supported
May  9 23:16:39 cmp02 systemd[1]: Found device /dev/ttyS0.
May  9 23:16:39 cmp02 kernel: [    0.030018] Freeing SMP alternatives memory: 36K
May  9 23:16:39 cmp02 kernel: [    0.034198] smpboot: Max logical packages: 5
May  9 23:16:39 cmp02 systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
May  9 23:16:39 cmp02 kernel: [    0.035411] x2apic enabled
May  9 23:16:39 cmp02 kernel: [    0.036006] Switched APIC routing to physical x2apic.
May  9 23:16:39 cmp02 systemd[1]: Started Create Volatile Files and Directories.
May  9 23:16:39 cmp02 kernel: [    0.038149] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
May  9 23:16:39 cmp02 kernel: [    0.039473] TSC deadline timer enabled
May  9 23:16:39 cmp02 systemd[1]: Starting Network Time Synchronization...
May  9 23:16:39 cmp02 kernel: [    0.039477] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (family: 0x6, model: 0x3e, stepping: 0x4)
May  9 23:16:39 cmp02 systemd[1]: Starting Update UTMP about System Boot/Shutdown...
May  9 23:16:39 cmp02 kernel: [    0.040000] Performance Events: IvyBridge events, Intel PMU driver.
May  9 23:16:39 cmp02 kernel: [    0.040000] ... version:                2
May  9 23:16:39 cmp02 kernel: [    0.040004] ... bit width:              48
May  9 23:16:39 cmp02 kernel: [    0.040993] ... generic registers:      4
May  9 23:16:39 cmp02 kernel: [    0.041946] ... value mask:             0000ffffffffffff
May  9 23:16:39 cmp02 systemd[1]: Started Network Time Synchronization.
May  9 23:16:39 cmp02 kernel: [    0.043112] ... max period:             000000007fffffff
May  9 23:16:39 cmp02 kernel: [    0.044004] ... fixed-purpose events:   3
May  9 23:16:39 cmp02 kernel: [    0.044973] ... event mask:             000000070000000f
May  9 23:16:39 cmp02 kernel: [    0.046194] Hierarchical SRCU implementation.
May  9 23:16:39 cmp02 kernel: [    0.047903] smp: Bringing up secondary CPUs ...
May  9 23:16:39 cmp02 kernel: [    0.048105] x86: Booting SMP configuration:
May  9 23:16:39 cmp02 systemd[1]: Reached target System Time Synchronized.
May  9 23:16:39 cmp02 kernel: [    0.049086] .... node  #0, CPUs:      #1
May  9 23:16:39 cmp02 kernel: [    0.004000] kvm-clock: cpu 1, msr 2:3ff55041, secondary cpu clock
May  9 23:16:39 cmp02 kernel: [    0.052018] KVM setup async PF for cpu 1
May  9 23:16:39 cmp02 systemd[1]: Started Update UTMP about System Boot/Shutdown.
May  9 23:16:39 cmp02 kernel: [    0.053495] kvm-stealtime: cpu 1, msr 2371161c0
May  9 23:16:39 cmp02 kernel: [    0.054538]  #2
May  9 23:16:39 cmp02 kernel: [    0.004000] kvm-clock: cpu 2, msr 2:3ff55081, secondary cpu clock
May  9 23:16:39 cmp02 kernel: [    0.060025] KVM setup async PF for cpu 2
May  9 23:16:39 cmp02 apparmor[509]:  * Starting AppArmor profiles
May  9 23:16:39 cmp02 systemd[1]: Started Set console font and keymap.
May  9 23:16:39 cmp02 kernel: [    0.061756] kvm-stealtime: cpu 2, msr 2372161c0
May  9 23:16:39 cmp02 kernel: [    0.062799]  #3
May  9 23:16:39 cmp02 kernel: [    0.004000] kvm-clock: cpu 3, msr 2:3ff550c1, secondary cpu clock
May  9 23:16:39 cmp02 kernel: [    0.068021] KVM setup async PF for cpu 3
May  9 23:16:39 cmp02 systemd[1]: Created slice system-getty.slice.
May  9 23:16:39 cmp02 kernel: [    0.068951] kvm-stealtime: cpu 3, msr 2373161c0
May  9 23:16:39 cmp02 systemd[1]: Found device Virtio network device.
May  9 23:16:39 cmp02 kernel: [    0.070287]  #4
May  9 23:16:39 cmp02 kernel: [    0.004000] kvm-clock: cpu 4, msr 2:3ff55101, secondary cpu clock
May  9 23:16:39 cmp02 kernel: [    0.076024] KVM setup async PF for cpu 4
May  9 23:16:39 cmp02 kernel: [    0.076944] kvm-stealtime: cpu 4, msr 2374161c0
May  9 23:16:39 cmp02 kernel: [    0.077997] smp: Brought up 1 node, 5 CPUs
May  9 23:16:39 cmp02 kernel: [    0.080006] smpboot: Total of 5 processors activated (27999.94 BogoMIPS)
May  9 23:16:39 cmp02 kernel: [    0.082384] devtmpfs: initialized
May  9 23:16:39 cmp02 kernel: [    0.082384] x86/mm: Memory block size: 128MB
May  9 23:16:39 cmp02 kernel: [    0.084734] evm: security.selinux
May  9 23:16:39 cmp02 kernel: [    0.086181] evm: security.SMACK64
May  9 23:16:39 cmp02 kernel: [    0.087049] evm: security.SMACK64EXEC
May  9 23:16:39 cmp02 kernel: [    0.088005] evm: security.SMACK64TRANSMUTE
May  9 23:16:39 cmp02 kernel: [    0.089528] evm: security.SMACK64MMAP
May  9 23:16:39 cmp02 kernel: [    0.090426] evm: security.ima
May  9 23:16:39 cmp02 kernel: [    0.091205] evm: security.capability
May  9 23:16:39 cmp02 kernel: [    0.092098] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
May  9 23:16:39 cmp02 kernel: [    0.095102] futex hash table entries: 2048 (order: 5, 131072 bytes)
May  9 23:16:39 cmp02 kernel: [    0.096411] pinctrl core: initialized pinctrl subsystem
May  9 23:16:39 cmp02 kernel: [    0.097737] RTC time: 23:16:32, date: 05/09/18
May  9 23:16:39 cmp02 kernel: [    0.099909] NET: Registered protocol family 16
May  9 23:16:39 cmp02 kernel: [    0.100209] cpuidle: using governor ladder
May  9 23:16:39 cmp02 kernel: [    0.101540] cpuidle: using governor menu
May  9 23:16:39 cmp02 kernel: [    0.102772] PCCT header not found.
May  9 23:16:39 cmp02 kernel: [    0.104011] ACPI: bus type PCI registered
May  9 23:16:39 cmp02 kernel: [    0.105266] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
May  9 23:16:39 cmp02 kernel: [    0.107082] PCI: Using configuration type 1 for base access
May  9 23:16:39 cmp02 kernel: [    0.108040] core: PMU erratum BJ122, BV98, HSD29 workaround disabled, HT off
May  9 23:16:39 cmp02 kernel: [    0.111223] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
May  9 23:16:39 cmp02 kernel: [    0.112012] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
May  9 23:16:39 cmp02 kernel: [    0.114046] ACPI: Added _OSI(Module Device)
May  9 23:16:39 cmp02 kernel: [    0.114046] ACPI: Added _OSI(Processor Device)
May  9 23:16:39 cmp02 kernel: [    0.116006] ACPI: Added _OSI(3.0 _SCP Extensions)
May  9 23:16:39 cmp02 kernel: [    0.117657] ACPI: Added _OSI(Processor Aggregator Device)
May  9 23:16:39 cmp02 kernel: [    0.121067] ACPI: Interpreter enabled
May  9 23:16:39 cmp02 kernel: [    0.121982] ACPI: (supports S0 S5)
May  9 23:16:39 cmp02 kernel: [    0.122832] ACPI: Using IOAPIC for interrupt routing
May  9 23:16:39 cmp02 kernel: [    0.123954] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
May  9 23:16:39 cmp02 kernel: [    0.124487] ACPI: Enabled 16 GPEs in block 00 to 0F
May  9 23:16:39 cmp02 kernel: [    0.129370] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
May  9 23:16:39 cmp02 kernel: [    0.131557] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
May  9 23:16:39 cmp02 kernel: [    0.132010] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
May  9 23:16:39 cmp02 kernel: [    0.133423] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
May  9 23:16:39 cmp02 kernel: [    0.136117] acpiphp: Slot [3] registered
May  9 23:16:39 cmp02 kernel: [    0.137097] acpiphp: Slot [4] registered
May  9 23:16:39 cmp02 kernel: [    0.138067] acpiphp: Slot [5] registered
May  9 23:16:39 cmp02 kernel: [    0.139025] acpiphp: Slot [6] registered
May  9 23:16:39 cmp02 kernel: [    0.140027] acpiphp: Slot [7] registered
May  9 23:16:39 cmp02 kernel: [    0.141294] acpiphp: Slot [9] registered
May  9 23:16:39 cmp02 kernel: [    0.142257] acpiphp: Slot [10] registered
May  9 23:16:39 cmp02 kernel: [    0.143230] acpiphp: Slot [11] registered
May  9 23:16:39 cmp02 kernel: [    0.144026] acpiphp: Slot [12] registered
May  9 23:16:39 cmp02 kernel: [    0.145848] acpiphp: Slot [13] registered
May  9 23:16:39 cmp02 kernel: [    0.146827] acpiphp: Slot [14] registered
May  9 23:16:39 cmp02 kernel: [    0.147798] acpiphp: Slot [15] registered
May  9 23:16:39 cmp02 kernel: [    0.148026] acpiphp: Slot [16] registered
May  9 23:16:39 cmp02 kernel: [    0.149000] acpiphp: Slot [17] registered
May  9 23:16:39 cmp02 kernel: [    0.149975] acpiphp: Slot [18] registered
May  9 23:16:39 cmp02 kernel: [    0.151234] acpiphp: Slot [19] registered
May  9 23:16:39 cmp02 kernel: [    0.152032] acpiphp: Slot [20] registered
May  9 23:16:39 cmp02 kernel: [    0.153004] acpiphp: Slot [21] registered
May  9 23:16:39 cmp02 kernel: [    0.153972] acpiphp: Slot [22] registered
May  9 23:16:39 cmp02 kernel: [    0.154939] acpiphp: Slot [23] registered
May  9 23:16:39 cmp02 kernel: [    0.156027] acpiphp: Slot [24] registered
May  9 23:16:39 cmp02 kernel: [    0.157003] acpiphp: Slot [25] registered
May  9 23:16:39 cmp02 kernel: [    0.157996] acpiphp: Slot [26] registered
May  9 23:16:39 cmp02 kernel: [    0.158979] acpiphp: Slot [27] registered
May  9 23:16:39 cmp02 kernel: [    0.160026] acpiphp: Slot [28] registered
May  9 23:16:39 cmp02 kernel: [    0.161001] acpiphp: Slot [29] registered
May  9 23:16:39 cmp02 kernel: [    0.162259] acpiphp: Slot [30] registered
May  9 23:16:39 cmp02 kernel: [    0.163233] acpiphp: Slot [31] registered
May  9 23:16:39 cmp02 kernel: [    0.164018] PCI host bridge to bus 0000:00
May  9 23:16:39 cmp02 kernel: [    0.164980] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
May  9 23:16:39 cmp02 kernel: [    0.168006] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
May  9 23:16:39 cmp02 kernel: [    0.169424] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
May  9 23:16:39 cmp02 kernel: [    0.171171] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
May  9 23:16:39 cmp02 kernel: [    0.172006] pci_bus 0000:00: root bus resource [bus 00-ff]
May  9 23:16:39 cmp02 kernel: [    0.173545] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
May  9 23:16:39 cmp02 kernel: [    0.174022] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
May  9 23:16:39 cmp02 kernel: [    0.174650] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
May  9 23:16:39 cmp02 kernel: [    0.183442] pci 0000:00:01.1: reg 0x20: [io  0xc180-0xc18f]
May  9 23:16:39 cmp02 kernel: [    0.186788] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
May  9 23:16:39 cmp02 kernel: [    0.188006] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
May  9 23:16:39 cmp02 kernel: [    0.190004] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
May  9 23:16:39 cmp02 kernel: [    0.192005] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
May  9 23:16:39 cmp02 kernel: [    0.194701] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
May  9 23:16:39 cmp02 kernel: [    0.195196] pci 0000:00:01.3: quirk: [io  0x0600-0x063f] claimed by PIIX4 ACPI
May  9 23:16:39 cmp02 kernel: [    0.196017] pci 0000:00:01.3: quirk: [io  0x0700-0x070f] claimed by PIIX4 SMB
May  9 23:16:39 cmp02 kernel: [    0.197826] pci 0000:00:02.0: [1013:00b8] type 00 class 0x030000
May  9 23:16:39 cmp02 kernel: [    0.201538] pci 0000:00:02.0: reg 0x10: [mem 0xfc000000-0xfdffffff pref]
May  9 23:16:39 cmp02 kernel: [    0.205449] pci 0000:00:02.0: reg 0x14: [mem 0xfebd0000-0xfebd0fff]
May  9 23:16:39 cmp02 kernel: [    0.226206] pci 0000:00:02.0: reg 0x30: [mem 0xfebc0000-0xfebcffff pref]
May  9 23:16:39 cmp02 kernel: [    0.226454] pci 0000:00:03.0: [1af4:1000] type 00 class 0x020000
May  9 23:16:39 cmp02 kernel: [    0.230998] pci 0000:00:03.0: reg 0x10: [io  0xc080-0xc09f]
May  9 23:16:39 cmp02 kernel: [    0.233280] pci 0000:00:03.0: reg 0x14: [mem 0xfebd1000-0xfebd1fff]
May  9 23:16:39 cmp02 kernel: [    0.251250] pci 0000:00:03.0: reg 0x30: [mem 0xfeac0000-0xfeafffff pref]
May  9 23:16:39 cmp02 kernel: [    0.251667] pci 0000:00:04.0: [1af4:1000] type 00 class 0x020000
May  9 23:16:39 cmp02 kernel: [    0.253319] pci 0000:00:04.0: reg 0x10: [io  0xc0a0-0xc0bf]
May  9 23:16:39 cmp02 kernel: [    0.258950] pci 0000:00:04.0: reg 0x14: [mem 0xfebd2000-0xfebd2fff]
May  9 23:16:39 cmp02 kernel: [    0.273875] pci 0000:00:04.0: reg 0x30: [mem 0xfeb00000-0xfeb3ffff pref]
May  9 23:16:39 cmp02 kernel: [    0.274838] pci 0000:00:05.0: [1af4:1000] type 00 class 0x020000
May  9 23:16:39 cmp02 kernel: [    0.278198] pci 0000:00:05.0: reg 0x10: [io  0xc0c0-0xc0df]
May  9 23:16:39 cmp02 kernel: [    0.283494] pci 0000:00:05.0: reg 0x14: [mem 0xfebd3000-0xfebd3fff]
May  9 23:16:39 cmp02 kernel: [    0.299282] pci 0000:00:05.0: reg 0x30: [mem 0xfeb40000-0xfeb7ffff pref]
May  9 23:16:39 cmp02 kernel: [    0.299658] pci 0000:00:06.0: [1af4:1000] type 00 class 0x020000
May  9 23:16:39 cmp02 kernel: [    0.303770] pci 0000:00:06.0: reg 0x10: [io  0xc0e0-0xc0ff]
May  9 23:16:39 cmp02 kernel: [    0.307321] pci 0000:00:06.0: reg 0x14: [mem 0xfebd4000-0xfebd4fff]
May  9 23:16:39 cmp02 kernel: [    0.322442] pci 0000:00:06.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref]
May  9 23:16:39 cmp02 kernel: [    0.322834] pci 0000:00:07.0: [1af4:1001] type 00 class 0x010000
May  9 23:16:39 cmp02 kernel: [    0.326679] pci 0000:00:07.0: reg 0x10: [io  0xc000-0xc03f]
May  9 23:16:39 cmp02 kernel: [    0.331050] pci 0000:00:07.0: reg 0x14: [mem 0xfebd5000-0xfebd5fff]
May  9 23:16:39 cmp02 kernel: [    0.346264] pci 0000:00:08.0: [8086:2934] type 00 class 0x0c0300
May  9 23:16:39 cmp02 kernel: [    0.355048] pci 0000:00:08.0: reg 0x20: [io  0xc100-0xc11f]
May  9 23:16:39 cmp02 kernel: [    0.357449] pci 0000:00:08.1: [8086:2935] type 00 class 0x0c0300
May  9 23:16:39 cmp02 kernel: [    0.368007] pci 0000:00:08.1: reg 0x20: [io  0xc120-0xc13f]
May  9 23:16:39 cmp02 kernel: [    0.372496] pci 0000:00:08.2: [8086:2936] type 00 class 0x0c0300
May  9 23:16:39 cmp02 kernel: [    0.380007] pci 0000:00:08.2: reg 0x20: [io  0xc140-0xc15f]
May  9 23:16:39 cmp02 kernel: [    0.386737] pci 0000:00:08.7: [8086:293a] type 00 class 0x0c0320
May  9 23:16:39 cmp02 kernel: [    0.388007] pci 0000:00:08.7: reg 0x10: [mem 0xfebd6000-0xfebd6fff]
May  9 23:16:39 cmp02 kernel: [    0.399987] pci 0000:00:09.0: [1af4:1001] type 00 class 0x010000
May  9 23:16:39 cmp02 kernel: [    0.404007] pci 0000:00:09.0: reg 0x10: [io  0xc040-0xc07f]
May  9 23:16:39 cmp02 kernel: [    0.409400] pci 0000:00:09.0: reg 0x14: [mem 0xfebd7000-0xfebd7fff]
May  9 23:16:39 cmp02 kernel: [    0.424648] pci 0000:00:0a.0: [1af4:1002] type 00 class 0x00ff00
May  9 23:16:39 cmp02 kernel: [    0.426985] pci 0000:00:0a.0: reg 0x10: [io  0xc160-0xc17f]
May  9 23:16:39 cmp02 kernel: [    0.437798] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
May  9 23:16:39 cmp02 kernel: [    0.440125] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
May  9 23:16:39 cmp02 kernel: [    0.442297] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
May  9 23:16:39 cmp02 kernel: [    0.444120] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
May  9 23:16:39 cmp02 kernel: [    0.445970] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
May  9 23:16:39 cmp02 kernel: [    0.448939] SCSI subsystem initialized
May  9 23:16:39 cmp02 kernel: [    0.450036] libata version 3.00 loaded.
May  9 23:16:39 cmp02 kernel: [    0.450036] pci 0000:00:02.0: vgaarb: setting as boot VGA device
May  9 23:16:39 cmp02 kernel: [    0.450036] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
May  9 23:16:39 cmp02 kernel: [    0.452009] pci 0000:00:02.0: vgaarb: bridge control possible
May  9 23:16:39 cmp02 kernel: [    0.453743] vgaarb: loaded
May  9 23:16:39 cmp02 kernel: [    0.454604] ACPI: bus type USB registered
May  9 23:16:39 cmp02 kernel: [    0.456014] usbcore: registered new interface driver usbfs
May  9 23:16:39 cmp02 kernel: [    0.458737] usbcore: registered new interface driver hub
May  9 23:16:39 cmp02 kernel: [    0.460036] usbcore: registered new device driver usb
May  9 23:16:39 cmp02 kernel: [    0.461243] EDAC MC: Ver: 3.0.0
May  9 23:16:39 cmp02 kernel: [    0.461462] PCI: Using ACPI for IRQ routing
May  9 23:16:39 cmp02 kernel: [    0.464006] PCI: pci_cache_line_size set to 64 bytes
May  9 23:16:39 cmp02 kernel: [    0.464294] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
May  9 23:16:39 cmp02 kernel: [    0.464296] e820: reserve RAM buffer [mem 0xbffdf000-0xbfffffff]
May  9 23:16:39 cmp02 kernel: [    0.464392] NetLabel: Initializing
May  9 23:16:39 cmp02 kernel: [    0.465257] NetLabel:  domain hash size = 128
May  9 23:16:39 cmp02 kernel: [    0.466574] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
May  9 23:16:39 cmp02 kernel: [    0.468021] NetLabel:  unlabeled traffic allowed by default
May  9 23:16:39 cmp02 kernel: [    0.470957] clocksource: Switched to clocksource kvm-clock
May  9 23:16:39 cmp02 kernel: [    0.484314] VFS: Disk quotas dquot_6.6.0
May  9 23:16:39 cmp02 kernel: [    0.485293] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
May  9 23:16:39 cmp02 kernel: [    0.487137] AppArmor: AppArmor Filesystem Enabled
May  9 23:16:39 cmp02 kernel: [    0.488811] pnp: PnP ACPI init
May  9 23:16:39 cmp02 kernel: [    0.489654] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
May  9 23:16:39 cmp02 kernel: [    0.489684] pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
May  9 23:16:39 cmp02 kernel: [    0.489714] pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
May  9 23:16:39 cmp02 kernel: [    0.489737] pnp 00:03: [dma 2]
May  9 23:16:39 cmp02 kernel: [    0.489752] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
May  9 23:16:39 cmp02 kernel: [    0.489824] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
May  9 23:16:39 cmp02 kernel: [    0.490031] pnp: PnP ACPI: found 5 devices
May  9 23:16:39 cmp02 kernel: [    0.499813] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
May  9 23:16:39 cmp02 kernel: [    0.502056] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
May  9 23:16:39 cmp02 kernel: [    0.502058] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
May  9 23:16:39 cmp02 kernel: [    0.502059] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
May  9 23:16:39 cmp02 kernel: [    0.502061] pci_bus 0000:00: resource 7 [mem 0xc0000000-0xfebfffff window]
May  9 23:16:39 cmp02 kernel: [    0.502113] NET: Registered protocol family 2
May  9 23:16:39 cmp02 kernel: [    0.503603] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
May  9 23:16:39 cmp02 kernel: [    0.507025] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
May  9 23:16:39 cmp02 kernel: [    0.511468] TCP: Hash tables configured (established 65536 bind 65536)
May  9 23:16:39 cmp02 kernel: [    0.512936] UDP hash table entries: 4096 (order: 5, 131072 bytes)
May  9 23:16:39 cmp02 kernel: [    0.514278] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
May  9 23:16:39 cmp02 kernel: [    0.516032] NET: Registered protocol family 1
May  9 23:16:39 cmp02 kernel: [    0.517637] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
May  9 23:16:39 cmp02 kernel: [    0.519477] pci 0000:00:01.0: PIIX3: Enabling Passive Release
May  9 23:16:39 cmp02 kernel: [    0.521045] pci 0000:00:01.0: Activating ISA DMA hang workarounds
May  9 23:16:39 cmp02 kernel: [    0.522691] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
May  9 23:16:39 cmp02 kernel: [    0.551333] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
May  9 23:16:39 cmp02 kernel: [    0.607176] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
May  9 23:16:39 cmp02 kernel: [    0.663315] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
May  9 23:16:39 cmp02 systemd[1]: message repeated 2 times: [ Found device Virtio network device.]
May  9 23:16:39 cmp02 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
May  9 23:16:39 cmp02 systemd[1]: Found device Virtio network device.
May  9 23:16:39 cmp02 apparmor[509]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
May  9 23:16:39 cmp02 apparmor[509]:    ...done.
May  9 23:16:39 cmp02 kernel: [    0.721900] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
May  9 23:16:39 cmp02 kernel: [    0.748810] PCI: CLS 0 bytes, default 64
May  9 23:16:39 cmp02 systemd[1]: Started LSB: AppArmor initialization.
May  9 23:16:39 cmp02 kernel: [    0.748871] Unpacking initramfs...
May  9 23:16:39 cmp02 kernel: [    1.501761] Freeing initrd memory: 47792K
May  9 23:16:39 cmp02 kernel: [    1.503465] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
May  9 23:16:39 cmp02 kernel: [    1.504861] software IO TLB [mem 0xbbfdf000-0xbffdf000] (64MB) mapped at [ffff92cdbbfdf000-ffff92cdbffdefff]
May  9 23:16:39 cmp02 systemd[1]: Starting Open vSwitch Internal Unit...
May  9 23:16:39 cmp02 kernel: [    1.507124] Scanning for low memory corruption every 60 seconds
May  9 23:16:39 cmp02 kernel: [    1.509169] audit: initializing netlink subsys (disabled)
May  9 23:16:39 cmp02 systemd-udevd[503]: Could not generate persistent MAC address for br-mesh: No such file or directory
May  9 23:16:39 cmp02 kernel: [    1.511063] audit: type=2000 audit(1525907793.375:1): state=initialized audit_enabled=0 res=1
May  9 23:16:39 cmp02 kernel: [    1.511353] Initialise system trusted keyrings
May  9 23:16:39 cmp02 kernel: [    1.511363] Key type blacklist registered
May  9 23:16:39 cmp02 kernel: [    1.511449] workingset: timestamp_bits=36 max_order=21 bucket_order=0
May  9 23:16:39 cmp02 kernel: [    1.512911] zbud: loaded
May  9 23:16:39 cmp02 systemd-udevd[500]: Could not generate persistent MAC address for br-mgmt: No such file or directory
May  9 23:16:39 cmp02 kernel: [    1.513388] squashfs: version 4.0 (2009/01/31) Phillip Lougher
May  9 23:16:39 cmp02 systemd-udevd[496]: Could not generate persistent MAC address for br-ex: No such file or directory
May  9 23:16:39 cmp02 kernel: [    1.513530] fuse init (API version 7.26)
May  9 23:16:39 cmp02 kernel: [    1.516068] Key type asymmetric registered
May  9 23:16:39 cmp02 kernel: [    1.516069] Asymmetric key parser 'x509' registered
May  9 23:16:39 cmp02 kernel: [    1.516099] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
May  9 23:16:39 cmp02 ovs-ctl[1245]:  * Starting ovsdb-server
May  9 23:16:39 cmp02 kernel: [    1.516143] io scheduler noop registered
May  9 23:16:39 cmp02 kernel: [    1.516144] io scheduler deadline registered
May  9 23:16:39 cmp02 kernel: [    1.516168] io scheduler cfq registered (default)
May  9 23:16:39 cmp02 kernel: [    1.530356] intel_idle: does not run on family 6 model 62
May  9 23:16:39 cmp02 kernel: [    1.530423] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
May  9 23:16:39 cmp02 kernel: [    1.532574] ACPI: Power Button [PWRF]
May  9 23:16:39 cmp02 kernel: [    1.533754] GHES: HEST is not enabled!
May  9 23:16:39 cmp02 kernel: [    1.567076] virtio-pci 0000:00:03.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.598575] virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.631189] virtio-pci 0000:00:05.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.665132] virtio-pci 0000:00:06.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.699085] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.732655] virtio-pci 0000:00:09.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.764529] virtio-pci 0000:00:0a.0: virtio_pci: leaving for legacy driver
May  9 23:16:39 cmp02 kernel: [    1.767528] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
May  9 23:16:39 cmp02 kernel: [    1.795352] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
May  9 23:16:39 cmp02 kernel: [    1.798709] Linux agpgart interface v0.103
May  9 23:16:39 cmp02 kernel: [    1.802207] loop: module loaded
May  9 23:16:39 cmp02 kernel: [    1.803120] ata_piix 0000:00:01.1: version 2.13
May  9 23:16:39 cmp02 kernel: [    1.804933] scsi host0: ata_piix
May  9 23:16:39 cmp02 kernel: [    1.806709] scsi host1: ata_piix
May  9 23:16:39 cmp02 kernel: [    1.807583] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc180 irq 14
May  9 23:16:39 cmp02 kernel: [    1.809308] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc188 irq 15
May  9 23:16:39 cmp02 kernel: [    1.811098] libphy: Fixed MDIO Bus: probed
May  9 23:16:39 cmp02 kernel: [    1.812486] tun: Universal TUN/TAP device driver, 1.6
May  9 23:16:39 cmp02 kernel: [    1.814229] PPP generic driver version 2.4.2
May  9 23:16:39 cmp02 kernel: [    1.815279] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
May  9 23:16:39 cmp02 kernel: [    1.817819] ehci-pci: EHCI PCI platform driver
May  9 23:16:39 cmp02 kernel: [    1.847857] ehci-pci 0000:00:08.7: EHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    1.849869] ehci-pci 0000:00:08.7: new USB bus registered, assigned bus number 1
May  9 23:16:39 cmp02 kernel: [    1.851785] ehci-pci 0000:00:08.7: irq 11, io mem 0xfebd6000
May  9 23:16:39 cmp02 kernel: [    1.868347] ehci-pci 0000:00:08.7: USB 2.0 started, EHCI 1.00
May  9 23:16:39 cmp02 kernel: [    1.870613] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
May  9 23:16:39 cmp02 kernel: [    1.872991] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:16:39 cmp02 kernel: [    1.876059] usb usb1: Product: EHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    1.877794] usb usb1: Manufacturer: Linux 4.13.0-41-generic ehci_hcd
May  9 23:16:39 cmp02 kernel: [    1.900979] usb usb1: SerialNumber: 0000:00:08.7
May  9 23:16:39 cmp02 kernel: [    1.902484] hub 1-0:1.0: USB hub found
May  9 23:16:39 cmp02 kernel: [    1.904083] hub 1-0:1.0: 6 ports detected
May  9 23:16:39 cmp02 kernel: [    1.905576] ehci-platform: EHCI generic platform driver
May  9 23:16:39 cmp02 kernel: [    1.907386] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
May  9 23:16:39 cmp02 kernel: [    1.909406] ohci-pci: OHCI PCI platform driver
May  9 23:16:39 cmp02 kernel: [    1.910638] ohci-platform: OHCI generic platform driver
May  9 23:16:39 cmp02 kernel: [    1.912278] uhci_hcd: USB Universal Host Controller Interface driver
May  9 23:16:39 cmp02 kernel: [    1.941757] uhci_hcd 0000:00:08.0: UHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    1.943225] uhci_hcd 0000:00:08.0: new USB bus registered, assigned bus number 2
May  9 23:16:39 cmp02 kernel: [    1.946027] uhci_hcd 0000:00:08.0: detected 2 ports
May  9 23:16:39 cmp02 kernel: [    1.947185] uhci_hcd 0000:00:08.0: irq 11, io base 0x0000c100
May  9 23:16:39 cmp02 kernel: [    1.948522] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
May  9 23:16:39 cmp02 kernel: [    1.949985] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:16:39 cmp02 kernel: [    1.953629] usb usb2: Product: UHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    1.956461] usb usb2: Manufacturer: Linux 4.13.0-41-generic uhci_hcd
May  9 23:16:39 cmp02 kernel: [    1.959233] usb usb2: SerialNumber: 0000:00:08.0
May  9 23:16:39 cmp02 kernel: [    1.961825] hub 2-0:1.0: USB hub found
May  9 23:16:39 cmp02 kernel: [    1.963666] hub 2-0:1.0: 2 ports detected
May  9 23:16:39 cmp02 kernel: [    1.968777] ata1.01: NODEV after polling detection
May  9 23:16:39 cmp02 kernel: [    1.969439] ata1.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
May  9 23:16:39 cmp02 kernel: [    1.971465] ata1.00: configured for MWDMA2
May  9 23:16:39 cmp02 kernel: [    1.973474] scsi 0:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     2.5+ PQ: 0 ANSI: 5
May  9 23:16:39 cmp02 kernel: [    1.977454] sr 0:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
May  9 23:16:39 cmp02 kernel: [    1.980592] cdrom: Uniform CD-ROM driver Revision: 3.20
May  9 23:16:39 cmp02 kernel: [    1.982202] sr 0:0:0:0: Attached scsi CD-ROM sr0
May  9 23:16:39 cmp02 kernel: [    1.982239] sr 0:0:0:0: Attached scsi generic sg0 type 5
May  9 23:16:39 cmp02 kernel: [    1.999633] uhci_hcd 0000:00:08.1: UHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    2.001944] uhci_hcd 0000:00:08.1: new USB bus registered, assigned bus number 3
May  9 23:16:39 cmp02 kernel: [    2.004536] uhci_hcd 0000:00:08.1: detected 2 ports
May  9 23:16:39 cmp02 kernel: [    2.005718] uhci_hcd 0000:00:08.1: irq 10, io base 0x0000c120
May  9 23:16:39 cmp02 kernel: [    2.007619] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
May  9 23:16:39 cmp02 kernel: [    2.009215] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:16:39 cmp02 kernel: [    2.011007] usb usb3: Product: UHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    2.013734] usb usb3: Manufacturer: Linux 4.13.0-41-generic uhci_hcd
May  9 23:16:39 cmp02 kernel: [    2.017016] usb usb3: SerialNumber: 0000:00:08.1
May  9 23:16:39 cmp02 kernel: [    2.019169] hub 3-0:1.0: USB hub found
May  9 23:16:39 cmp02 kernel: [    2.020866] hub 3-0:1.0: 2 ports detected
May  9 23:16:39 cmp02 kernel: [    2.056502] uhci_hcd 0000:00:08.2: UHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    2.058547] uhci_hcd 0000:00:08.2: new USB bus registered, assigned bus number 4
May  9 23:16:39 cmp02 kernel: [    2.060443] uhci_hcd 0000:00:08.2: detected 2 ports
May  9 23:16:39 cmp02 kernel: [    2.061964] uhci_hcd 0000:00:08.2: irq 10, io base 0x0000c140
May  9 23:16:39 cmp02 kernel: [    2.063592] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
May  9 23:16:39 cmp02 kernel: [    2.065506] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
May  9 23:16:39 cmp02 kernel: [    2.068661] usb usb4: Product: UHCI Host Controller
May  9 23:16:39 cmp02 kernel: [    2.070229] usb usb4: Manufacturer: Linux 4.13.0-41-generic uhci_hcd
May  9 23:16:39 cmp02 kernel: [    2.072265] usb usb4: SerialNumber: 0000:00:08.2
May  9 23:16:39 cmp02 kernel: [    2.073433] hub 4-0:1.0: USB hub found
May  9 23:16:39 cmp02 kernel: [    2.074380] hub 4-0:1.0: 2 ports detected
May  9 23:16:39 cmp02 kernel: [    2.076091] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
May  9 23:16:39 cmp02 kernel: [    2.079535] serio: i8042 KBD port at 0x60,0x64 irq 1
May  9 23:16:39 cmp02 kernel: [    2.080686] serio: i8042 AUX port at 0x60,0x64 irq 12
May  9 23:16:39 cmp02 kernel: [    2.082237] mousedev: PS/2 mouse device common for all mice
May  9 23:16:39 cmp02 kernel: [    2.084643] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
May  9 23:16:39 cmp02 kernel: [    2.087137] rtc_cmos 00:00: RTC can wake from S4
May  9 23:16:39 cmp02 kernel: [    2.088536] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
May  9 23:16:39 cmp02 kernel: [    2.090266] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram
May  9 23:16:39 cmp02 kernel: [    2.091608] i2c /dev entries driver
May  9 23:16:39 cmp02 kernel: [    2.092830] device-mapper: uevent: version 1.0.3
May  9 23:16:39 cmp02 kernel: [    2.094249] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
May  9 23:16:39 cmp02 kernel: [    2.096657] ledtrig-cpu: registered to indicate activity on CPUs
May  9 23:16:39 cmp02 kernel: [    2.099089] NET: Registered protocol family 10
May  9 23:16:39 cmp02 kernel: [    2.107346] Segment Routing with IPv6
May  9 23:16:39 cmp02 kernel: [    2.109318] NET: Registered protocol family 17
May  9 23:16:39 cmp02 kernel: [    2.111650] Key type dns_resolver registered
May  9 23:16:39 cmp02 kernel: [    2.113686] RAS: Correctable Errors collector initialized.
May  9 23:16:39 cmp02 kernel: [    2.115822] sched_clock: Marking stable (2113541167, 0)->(2583394899, -469853732)
May  9 23:16:39 cmp02 kernel: [    2.121782] registered taskstats version 1
May  9 23:16:39 cmp02 kernel: [    2.123650] Loading compiled-in X.509 certificates
May  9 23:16:39 cmp02 kernel: [    2.128973] Loaded X.509 cert 'Build time autogenerated kernel key: 455b6c2f89645ccacce587853289bc763cf1d7aa'
May  9 23:16:39 cmp02 kernel: [    2.136093] zswap: loaded using pool lzo/zbud
May  9 23:16:39 cmp02 kernel: [    2.145222] Key type big_key registered
May  9 23:16:39 cmp02 kernel: [    2.147229] Key type trusted registered
May  9 23:16:39 cmp02 kernel: [    2.151973] Key type encrypted registered
May  9 23:16:39 cmp02 kernel: [    2.153791] AppArmor: AppArmor sha1 policy hashing enabled
May  9 23:16:39 cmp02 kernel: [    2.158843] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
May  9 23:16:39 cmp02 kernel: [    2.161186] evm: HMAC attrs: 0x1
May  9 23:16:39 cmp02 kernel: [    2.162859]   Magic number: 2:829:301
May  9 23:16:39 cmp02 kernel: [    2.164822] tty tty30: hash matches
May  9 23:16:39 cmp02 kernel: [    2.167515] rtc_cmos 00:00: setting system clock to 2018-05-09 23:16:34 UTC (1525907794)
May  9 23:16:39 cmp02 kernel: [    2.169771] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
May  9 23:16:39 cmp02 kernel: [    2.172855] EDD information not available.
May  9 23:16:39 cmp02 kernel: [    2.173864] PM: Hibernation image not present or could not be loaded.
May  9 23:16:39 cmp02 kernel: [    2.178741] Freeing unused kernel memory: 2368K
May  9 23:16:39 cmp02 kernel: [    2.180139] Write protecting the kernel read-only data: 18432k
May  9 23:16:39 cmp02 kernel: [    2.182995] Freeing unused kernel memory: 2024K
May  9 23:16:39 cmp02 kernel: [    2.185145] Freeing unused kernel memory: 88K
May  9 23:16:39 cmp02 kernel: [    2.189230] x86/mm: Checked W+X mappings: passed, no W+X pages found.
May  9 23:16:39 cmp02 kernel: [    2.191178] x86/mm: Checking user space page tables
May  9 23:16:39 cmp02 kernel: [    2.195133] x86/mm: Checked W+X mappings: passed, no W+X pages found.
May  9 23:16:39 cmp02 kernel: [    2.297075]  vda: vda1
May  9 23:16:39 cmp02 kernel: [    2.301405] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input4
May  9 23:16:39 cmp02 kernel: [    2.305076] input: VirtualPS/2 VMware VMMouse as /devices/platform/i8042/serio1/input/input3
May  9 23:16:39 cmp02 kernel: [    2.319492] [TTM] Zone  kernel: Available graphics memory: 4083988 kiB
May  9 23:16:39 cmp02 kernel: [    2.322258] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
May  9 23:16:39 cmp02 kernel: [    2.325277] [TTM] Initializing pool allocator
May  9 23:16:39 cmp02 kernel: [    2.326936] [TTM] Initializing DMA pool allocator
May  9 23:16:39 cmp02 kernel: [    2.329031] [drm] fb mappable at 0xFC000000
May  9 23:16:39 cmp02 kernel: [    2.330571] [drm] vram aper at 0xFC000000
May  9 23:16:39 cmp02 kernel: [    2.332352] [drm] size 33554432
May  9 23:16:39 cmp02 kernel: [    2.333160] [drm] fb depth is 24
May  9 23:16:39 cmp02 kernel: [    2.334258] [drm]    pitch is 3072
May  9 23:16:39 cmp02 kernel: [    2.336023] FDC 0 is a S82078B
May  9 23:16:39 cmp02 kernel: [    2.341207] fbcon: cirrusdrmfb (fb0) is primary device
May  9 23:16:39 cmp02 kernel: [    2.343200] AVX version of gcm_enc/dec engaged.
May  9 23:16:39 cmp02 kernel: [    2.343200] AES CTR mode by8 optimization enabled
May  9 23:16:39 cmp02 kernel: [    2.350762] virtio_net virtio0 ens3: renamed from eth0
May  9 23:16:39 cmp02 kernel: [    2.377811] virtio_net virtio2 ens5: renamed from eth2
May  9 23:16:39 cmp02 kernel: [    2.387258] Console: switching to colour frame buffer device 128x48
May  9 23:16:39 cmp02 kernel: [    2.393040] virtio_net virtio3 ens6: renamed from eth3
May  9 23:16:39 cmp02 kernel: [    2.413681] cirrus 0000:00:02.0: fb0: cirrusdrmfb frame buffer device
May  9 23:16:39 cmp02 kernel: [    2.428099] [drm] Initialized cirrus 1.0.0 20110418 for 0000:00:02.0 on minor 0
May  9 23:16:39 cmp02 kernel: [    2.432783] virtio_net virtio1 ens4: renamed from eth1
May  9 23:16:39 cmp02 kernel: [    2.532510] tsc: Refined TSC clocksource calibration: 2800.046 MHz
May  9 23:16:39 cmp02 kernel: [    2.534372] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x285c6c3b9bb, max_idle_ns: 440795208083 ns
May  9 23:16:39 cmp02 kernel: [    2.632028] raid6: sse2x1   gen()  5232 MB/s
May  9 23:16:39 cmp02 kernel: [    2.680054] raid6: sse2x1   xor()  4409 MB/s
May  9 23:16:39 cmp02 kernel: [    2.728018] raid6: sse2x2   gen()  6906 MB/s
May  9 23:16:39 cmp02 kernel: [    2.776025] raid6: sse2x2   xor()  5430 MB/s
May  9 23:16:39 cmp02 kernel: [    2.824022] raid6: sse2x4   gen()  8795 MB/s
May  9 23:16:39 cmp02 kernel: [    2.872023] raid6: sse2x4   xor()  5987 MB/s
May  9 23:16:39 cmp02 kernel: [    2.872714] raid6: using algorithm sse2x4 gen() 8795 MB/s
May  9 23:16:39 cmp02 kernel: [    2.874379] raid6: .... xor() 5987 MB/s, rmw enabled
May  9 23:16:39 cmp02 kernel: [    2.875457] raid6: using ssse3x2 recovery algorithm
May  9 23:16:39 cmp02 kernel: [    2.878832] xor: automatically using best checksumming function   avx       
May  9 23:16:39 cmp02 kernel: [    2.881631] async_tx: api initialized (async)
May  9 23:16:39 cmp02 kernel: [    2.945728] Btrfs loaded, crc32c=crc32c-intel
May  9 23:16:39 cmp02 kernel: [    2.999108] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
May  9 23:16:39 cmp02 kernel: [    3.750907] EXT4-fs (vda1): re-mounted. Opts: (null)
May  9 23:16:39 cmp02 kernel: [    3.814291] Loading iSCSI transport class v2.0-870.
May  9 23:16:39 cmp02 kernel: [    3.831518] iscsi: registered transport (tcp)
May  9 23:16:39 cmp02 kernel: [    3.918574] iscsi: registered transport (iser)
May  9 23:16:39 cmp02 kernel: [    4.000622] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
May  9 23:16:39 cmp02 kernel: [    4.325935] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0x700, revision 0
May  9 23:16:39 cmp02 kernel: [    4.635127] EDAC sbridge: Seeking for: PCI ID 8086:0ea0
May  9 23:16:39 cmp02 kernel: [    4.635132] EDAC sbridge:  Ver: 1.1.2 
May  9 23:16:39 cmp02 kernel: [    4.666133] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
May  9 23:16:39 cmp02 kernel: [    4.667366] br-mesh: port 1(ens5) entered blocking state
May  9 23:16:39 cmp02 kernel: [    4.667369] br-mesh: port 1(ens5) entered disabled state
May  9 23:16:39 cmp02 kernel: [    4.667415] device ens5 entered promiscuous mode
May  9 23:16:39 cmp02 kernel: [    4.668905] br-ex: port 1(ens6) entered blocking state
May  9 23:16:39 cmp02 kernel: [    4.668907] br-ex: port 1(ens6) entered disabled state
May  9 23:16:39 cmp02 kernel: [    4.668941] device ens6 entered promiscuous mode
May  9 23:16:39 cmp02 kernel: [    4.669396] br-mgmt: port 1(ens4) entered blocking state
May  9 23:16:39 cmp02 kernel: [    4.669398] br-mgmt: port 1(ens4) entered disabled state
May  9 23:16:39 cmp02 kernel: [    4.669435] device ens4 entered promiscuous mode
May  9 23:16:39 cmp02 kernel: [    4.973887] audit: type=1400 audit(1525907797.306:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=1149 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.005231] audit: type=1400 audit(1525907797.337:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=1151 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.005235] audit: type=1400 audit(1525907797.337:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1151 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.005314] audit: type=1400 audit(1525907797.337:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default" pid=1147 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.005316] audit: type=1400 audit(1525907797.337:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-cgns" pid=1147 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.005318] audit: type=1400 audit(1525907797.337:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-with-mounting" pid=1147 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.005321] audit: type=1400 audit(1525907797.337:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-with-nesting" pid=1147 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.012942] audit: type=1400 audit(1525907797.345:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lxd/lxd-bridge-proxy" pid=1150 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.020255] audit: type=1400 audit(1525907797.351:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=1196 comm="apparmor_parser"
May  9 23:16:39 cmp02 kernel: [    5.069365] ppdev: user-space parallel port driver
May  9 23:16:39 cmp02 kernel: [    5.265043] openvswitch: Open vSwitch switching datapath
May  9 23:16:39 cmp02 kernel: [    5.307277] device ovs-system entered promiscuous mode
May  9 23:16:39 cmp02 kernel: [    5.338892] device br-floating entered promiscuous mode
May  9 23:16:39 cmp02 kernel: [    5.767021] ISO 9660 Extensions: Microsoft Joliet Level 3
May  9 23:16:39 cmp02 kernel: [    5.772494] ISO 9660 Extensions: RRIP_1991A
May  9 23:16:39 cmp02 kernel: [    5.994477] br-mgmt: port 1(ens4) entered blocking state
May  9 23:16:39 cmp02 kernel: [    5.994480] br-mgmt: port 1(ens4) entered forwarding state
May  9 23:16:39 cmp02 kernel: [    6.007990] br-mesh: port 1(ens5) entered blocking state
May  9 23:16:39 cmp02 kernel: [    6.007992] br-mesh: port 1(ens5) entered forwarding state
May  9 23:16:39 cmp02 kernel: [    6.016607] br-ex: port 1(ens6) entered blocking state
May  9 23:16:39 cmp02 kernel: [    6.016609] br-ex: port 1(ens6) entered forwarding state
May  9 23:16:39 cmp02 kernel: [    6.115562] device float-to-ex entered promiscuous mode
May  9 23:16:39 cmp02 kernel: [    6.153194] br-ex: port 2(float-to-ex) entered blocking state
May  9 23:16:39 cmp02 kernel: [    6.153197] br-ex: port 2(float-to-ex) entered disabled state
May  9 23:16:39 cmp02 kernel: [    6.154252] br-ex: port 2(float-to-ex) entered blocking state
May  9 23:16:39 cmp02 kernel: [    6.154254] br-ex: port 2(float-to-ex) entered forwarding state
May  9 23:16:39 cmp02 kernel: [    7.501106] new mount options do not match the existing superblock, will be ignored
May  9 23:16:39 cmp02 rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
May  9 23:16:39 cmp02 rsyslogd-2007: action 'action 11' suspended, next retry is Wed May  9 23:17:09 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
May  9 23:16:39 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait -- init -- set Open_vSwitch . db-version=7.15.0
May  9 23:16:39 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait set Open_vSwitch . ovs-version=2.8.0 "external-ids:system-id=\"a765059e-e69c-4ec4-81ac-f541e3b69dfe\"" "external-ids:hostname=\"cmp02\"" "external-ids:rundir=\"/var/run/openvswitch\"" "system-type=\"ubuntu\"" "system-version=\"16.04\""
May  9 23:16:39 cmp02 ovs-ctl[1245]:  * Configuring Open vSwitch system IDs
May  9 23:16:39 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/br-mesh.
May  9 23:16:39 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/br-ex.
May  9 23:16:39 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/br-mgmt.
May  9 23:16:39 cmp02 ovs-ctl[1245]:  * Inserting openvswitch module
May  9 23:16:39 cmp02 systemd-udevd[1600]: Could not generate persistent MAC address for ovs-system: No such file or directory
May  9 23:16:39 cmp02 ovs-ctl[1245]:  * Starting ovs-vswitchd
May  9 23:16:39 cmp02 ovs-ctl[1245]:  * Enabling remote OVSDB managers
May  9 23:16:39 cmp02 systemd[1]: Started Open vSwitch Internal Unit.
May  9 23:16:39 cmp02 cloud-init[455]: Cloud-init v. 18.2 running 'init-local' at Wed, 09 May 2018 23:16:37 +0000. Up 5.61 seconds.
May  9 23:16:39 cmp02 systemd[1]: Started Initial cloud-init job (pre-networking).
May  9 23:16:39 cmp02 systemd[1]: Reached target Network (Pre).
May  9 23:16:39 cmp02 systemd[1]: Started ifup for br-mgmt.
May  9 23:16:39 cmp02 systemd[1]: Started ifup for br-ex.
May  9 23:16:39 cmp02 systemd[1]: Started ifup for ens5.
May  9 23:16:39 cmp02 systemd[1]: Starting Raise network interfaces...
May  9 23:16:39 cmp02 systemd[1]: Started ifup for br-mesh.
May  9 23:16:39 cmp02 systemd[1]: Started ifup for ens4.
May  9 23:16:39 cmp02 systemd[1]: Started ifup for ens3.
May  9 23:16:39 cmp02 systemd[1]: Started ifup for ens6.
May  9 23:16:39 cmp02 sh[1854]: Waiting for br-mgmt to get ready (MAXWAIT is 32 seconds).
May  9 23:16:39 cmp02 sh[1881]: Waiting for br-mesh to get ready (MAXWAIT is 32 seconds).
May  9 23:16:39 cmp02 sh[1856]: interface float-to-ex does not exist!
May  9 23:16:39 cmp02 sh[1856]: Waiting for br-ex to get ready (MAXWAIT is 32 seconds).
May  9 23:16:39 cmp02 dhclient[1962]: Internet Systems Consortium DHCP Client 4.3.3
May  9 23:16:39 cmp02 dhclient[1962]: Copyright 2004-2015 Internet Systems Consortium.
May  9 23:16:39 cmp02 sh[1894]: Internet Systems Consortium DHCP Client 4.3.3
May  9 23:16:39 cmp02 sh[1894]: Copyright 2004-2015 Internet Systems Consortium.
May  9 23:16:39 cmp02 sh[1894]: All rights reserved.
May  9 23:16:39 cmp02 sh[1894]: For info, please visit https://www.isc.org/software/dhcp/
May  9 23:16:39 cmp02 dhclient[1962]: All rights reserved.
May  9 23:16:39 cmp02 dhclient[1962]: For info, please visit https://www.isc.org/software/dhcp/
May  9 23:16:39 cmp02 dhclient[1962]: 
May  9 23:16:39 cmp02 dhclient[1962]: Listening on LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:39 cmp02 sh[1894]: Listening on LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:39 cmp02 sh[1894]: Sending on   LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:39 cmp02 sh[1894]: Sending on   Socket/fallback
May  9 23:16:39 cmp02 sh[1894]: DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x96db705f)
May  9 23:16:39 cmp02 dhclient[1962]: Sending on   LPF/ens3/52:54:00:90:6f:f7
May  9 23:16:39 cmp02 sh[1894]: DHCPREQUEST of 192.168.11.50 on ens3 to 255.255.255.255 port 67 (xid=0x5f70db96)
May  9 23:16:39 cmp02 sh[1894]: DHCPOFFER of 192.168.11.50 from 192.168.11.1
May  9 23:16:39 cmp02 sh[1894]: DHCPACK of 192.168.11.50 from 192.168.11.1
May  9 23:16:39 cmp02 dhclient[1962]: Sending on   Socket/fallback
May  9 23:16:39 cmp02 dhclient[1962]: DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x96db705f)
May  9 23:16:39 cmp02 dhclient[1962]: DHCPREQUEST of 192.168.11.50 on ens3 to 255.255.255.255 port 67 (xid=0x5f70db96)
May  9 23:16:39 cmp02 dhclient[1962]: DHCPOFFER of 192.168.11.50 from 192.168.11.1
May  9 23:16:39 cmp02 dhclient[1962]: DHCPACK of 192.168.11.50 from 192.168.11.1
May  9 23:16:39 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --may-exist add-port br-floating float-to-ex -- set Interface float-to-ex type=internal --
May  9 23:16:39 cmp02 systemd-udevd[2183]: Could not generate persistent MAC address for float-to-ex: No such file or directory
May  9 23:16:39 cmp02 dhclient[1962]: bound to 192.168.11.50 -- renewal in 1451 seconds.
May  9 23:16:39 cmp02 sh[1894]: bound to 192.168.11.50 -- renewal in 1451 seconds.
May  9 23:16:39 cmp02 ifup[2012]: /sbin/ifup: waiting for lock on /run/network/ifstate.br-mesh
May  9 23:16:39 cmp02 systemd[1]: Started ifup for float-to-ex.
May  9 23:16:39 cmp02 sh[2383]: ifup: interface float-to-ex already configured
May  9 23:16:39 cmp02 systemd[1]: Found device /sys/subsystem/net/devices/float-to-ex.
May  9 23:16:39 cmp02 ifup[2012]: /sbin/ifup: waiting for lock on /run/network/ifstate.br-mgmt
May  9 23:16:39 cmp02 systemd[1]: Started Raise network interfaces.
May  9 23:16:39 cmp02 systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
May  9 23:16:39 cmp02 systemd[1]: Reached target Network.
May  9 23:16:39 cmp02 cloud-init[2564]: Cloud-init v. 18.2 running 'init' at Wed, 09 May 2018 23:16:39 +0000. Up 6.69 seconds.
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +++++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++++++
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +-------------+-------+------------------------------+---------------+-------+-------------------+
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |    Device   |   Up  |           Address            |      Mask     | Scope |     Hw-Address    |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +-------------+-------+------------------------------+---------------+-------+-------------------+
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |    br-ex    |  True |         10.16.0.111          | 255.255.255.0 |   .   | 52:54:00:a3:a9:4f |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |    br-ex    |  True |  fe80::5054:ff:fea3:a94f/64  |       .       |  link | 52:54:00:a3:a9:4f |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: | br-floating | False |              .               |       .       |   .   | 5e:cf:9e:10:a5:45 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   br-mesh   |  True |           10.1.0.6           | 255.255.255.0 |   .   | 52:54:00:53:d1:ac |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   br-mesh   |  True |  fe80::5054:ff:fe53:d1ac/64  |       .       |  link | 52:54:00:53:d1:ac |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   br-mgmt   |  True |         172.16.10.53         | 255.255.255.0 |   .   | 52:54:00:f6:39:39 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   br-mgmt   |  True |  fe80::5054:ff:fef6:3939/64  |       .       |  link | 52:54:00:f6:39:39 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens3    |  True |        192.168.11.50         | 255.255.255.0 |   .   | 52:54:00:90:6f:f7 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens3    |  True |  fe80::5054:ff:fe90:6ff7/64  |       .       |  link | 52:54:00:90:6f:f7 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens4    |  True |              .               |       .       |   .   | 52:54:00:f6:39:39 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens4    |  True |  fe80::5054:ff:fef6:3939/64  |       .       |  link | 52:54:00:f6:39:39 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens5    |  True |              .               |       .       |   .   | 52:54:00:53:d1:ac |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens5    |  True |  fe80::5054:ff:fe53:d1ac/64  |       .       |  link | 52:54:00:53:d1:ac |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens6    |  True |              .               |       .       |   .   | 52:54:00:a3:a9:4f |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |     ens6    |  True |  fe80::5054:ff:fea3:a94f/64  |       .       |  link | 52:54:00:a3:a9:4f |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: | float-to-ex |  True |              .               |       .       |   .   | ee:65:21:6b:4c:06 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: | float-to-ex |  True | fe80::ec65:21ff:fe6b:4c06/64 |       .       |  link | ee:65:21:6b:4c:06 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |      lo     |  True |          127.0.0.1           |   255.0.0.0   |   .   |         .         |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |      lo     |  True |           ::1/128            |       .       |  host |         .         |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |  ovs-system | False |              .               |       .       |   .   | 3a:bf:60:42:3a:f1 |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +-------------+-------+------------------------------+---------------+-------+-------------------+
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info++++++++++++++++++++++++++++++
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: | Route | Destination  |   Gateway    |    Genmask    | Interface | Flags |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   0   |   0.0.0.0    | 192.168.11.1 |    0.0.0.0    |    ens3   |   UG  |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   1   |   10.1.0.0   |   0.0.0.0    | 255.255.255.0 |  br-mesh  |   U   |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   2   |  10.16.0.0   |   0.0.0.0    | 255.255.255.0 |   br-ex   |   U   |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   3   | 172.16.10.0  |   0.0.0.0    | 255.255.255.0 |  br-mgmt  |   U   |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: |   4   | 192.168.11.0 |   0.0.0.0    | 255.255.255.0 |    ens3   |   U   |
May  9 23:16:39 cmp02 cloud-init[2564]: ci-info: +-------+--------------+--------------+---------------+-----------+-------+
May  9 23:16:39 cmp02 systemd[1]: Started Initial cloud-init job (metadata service crawler).
May  9 23:16:39 cmp02 systemd[1]: Reached target Network is Online.
May  9 23:16:39 cmp02 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
May  9 23:16:39 cmp02 systemd[1]: Reached target Cloud-config availability.
May  9 23:16:39 cmp02 systemd[1]: Reached target System Initialization.
May  9 23:16:39 cmp02 systemd[1]: Starting LXD - unix socket.
May  9 23:16:39 cmp02 systemd[1]: Started ACPI Events Check.
May  9 23:16:39 cmp02 systemd[1]: Reached target Paths.
May  9 23:16:39 cmp02 systemd[1]: Started Daily apt download activities.
May  9 23:16:39 cmp02 systemd[1]: Started Daily apt upgrade and clean activities.
May  9 23:16:39 cmp02 systemd[1]: Started Daily Cleanup of Temporary Directories.
May  9 23:16:39 cmp02 systemd[1]: Reached target Timers.
May  9 23:16:39 cmp02 systemd[1]: Listening on ACPID Listen Socket.
May  9 23:16:39 cmp02 systemd[1]: Listening on D-Bus System Message Bus Socket.
May  9 23:16:39 cmp02 systemd[1]: Starting Socket activation for snappy daemon.
May  9 23:16:39 cmp02 systemd[1]: Listening on UUID daemon activation socket.
May  9 23:16:39 cmp02 systemd[1]: Listening on LXD - unix socket.
May  9 23:16:39 cmp02 systemd[1]: Listening on Socket activation for snappy daemon.
May  9 23:16:39 cmp02 systemd[1]: Reached target Sockets.
May  9 23:16:39 cmp02 systemd[1]: Reached target Basic System.
May  9 23:16:39 cmp02 systemd[1]: Starting Accounts Service...
May  9 23:16:39 cmp02 systemd[1]: Started FUSE filesystem for LXC.
May  9 23:16:39 cmp02 iscsid: iSCSI logger with pid=2671 started!
May  9 23:16:39 cmp02 systemd[1]: Started Unattended Upgrades Shutdown.
May  9 23:16:39 cmp02 iscsid: iSCSI daemon with pid=2673 started!
May  9 23:16:39 cmp02 systemd[1]: Starting /etc/rc.local Compatibility...
May  9 23:16:39 cmp02 systemd[1]: Starting System Logging Service...
May  9 23:16:39 cmp02 systemd[1]: Starting Thermal Daemon Service...
May  9 23:16:39 cmp02 systemd[1]: Starting Apply the settings specified in cloud-config...
May  9 23:16:39 cmp02 systemd[1]: Started Deferred execution scheduler.
May  9 23:16:39 cmp02 systemd[1]: Started D-Bus System Message Bus.
May  9 23:16:39 cmp02 lxcfs[2670]: hierarchies:
May  9 23:16:39 cmp02 lxcfs[2670]:   0: fd:   5: devices
May  9 23:16:39 cmp02 lxcfs[2670]:   1: fd:   6: freezer
May  9 23:16:39 cmp02 lxcfs[2670]:   2: fd:   7: pids
May  9 23:16:39 cmp02 lxcfs[2670]:   3: fd:   8: blkio
May  9 23:16:39 cmp02 lxcfs[2670]:   4: fd:   9: cpu,cpuacct
May  9 23:16:39 cmp02 lxcfs[2670]:   5: fd:  10: memory
May  9 23:16:39 cmp02 lxcfs[2670]:   6: fd:  11: hugetlb
May  9 23:16:39 cmp02 lxcfs[2670]:   7: fd:  12: rdma
May  9 23:16:39 cmp02 lxcfs[2670]:   8: fd:  13: net_cls,net_prio
May  9 23:16:39 cmp02 lxcfs[2670]:   9: fd:  14: perf_event
May  9 23:16:39 cmp02 lxcfs[2670]:  10: fd:  15: cpuset
May  9 23:16:39 cmp02 lxcfs[2670]:  11: fd:  16: name=systemd
May  9 23:16:40 cmp02 dbus[2710]: [system] AppArmor D-Bus mediation is enabled
May  9 23:16:40 cmp02 systemd[1]: Starting LSB: Record successful boot for GRUB...
May  9 23:16:40 cmp02 systemd[1]: Starting LSB: MD monitoring daemon...
May  9 23:16:40 cmp02 thermald[2690]: NO RAPL sysfs present
May  9 23:16:40 cmp02 thermald[2690]: 13 CPUID levels; family:model:stepping 0x6:3e:4 (6:62:4)
May  9 23:16:40 cmp02 thermald[2690]:  Need Linux PowerCap sysfs
May  9 23:16:40 cmp02 systemd[1]: Started Regular background program processing daemon.
May  9 23:16:40 cmp02 cron[2769]: (CRON) INFO (pidfile fd = 3)
May  9 23:16:40 cmp02 systemd[1]: Starting Snappy daemon...
May  9 23:16:40 cmp02 systemd[1]: Starting LSB: Set sysfs variables from /etc/sysfs.conf...
May  9 23:16:40 cmp02 systemd[1]: Starting Open vSwitch...
May  9 23:16:40 cmp02 thermald[2690]: Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check
May  9 23:16:40 cmp02 thermald[2690]: THD engine start failed
May  9 23:16:40 cmp02 dbus[2710]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
May  9 23:16:40 cmp02 systemd[1]: Starting Login Service...
May  9 23:16:40 cmp02 cron[2769]: (CRON) INFO (Running @reboot jobs)
May  9 23:16:40 cmp02 systemd[1]: Starting OpenBSD Secure Shell server...
May  9 23:16:40 cmp02 systemd[1]: Starting The Salt Minion...
May  9 23:16:40 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:16:40 cmp02 systemd[1]: Starting LXD - container startup/shutdown...
May  9 23:16:40 cmp02 systemd[1]: Started System Logging Service.
May  9 23:16:40 cmp02 systemd[1]: Started iSCSI initiator daemon (iscsid).
May  9 23:16:40 cmp02 systemd[1]: Started /etc/rc.local Compatibility.
May  9 23:16:40 cmp02 systemd[1]: Started Thermal Daemon Service.
May  9 23:16:40 cmp02 systemd[1]: Started Open vSwitch.
May  9 23:16:40 cmp02 sysfsutils[2796]:  * Setting sysfs variables...
May  9 23:16:40 cmp02 mdadm[2756]:  * Starting MD monitoring service mdadm --monitor
May  9 23:16:40 cmp02 systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks...
May  9 23:16:40 cmp02 systemd[1]: Starting Login to default iSCSI targets...
May  9 23:16:40 cmp02 systemd[1]: Started Login Service.
May  9 23:16:40 cmp02 acpid: starting up with netlink and the input layer
May  9 23:16:40 cmp02 sysfsutils[2796]:    ...done.
May  9 23:16:40 cmp02 systemd[1]: Started LSB: Set sysfs variables from /etc/sysfs.conf.
May  9 23:16:40 cmp02 acpid: 1 rule loaded
May  9 23:16:40 cmp02 acpid: waiting for events: event logging is off
May  9 23:16:40 cmp02 iscsiadm[2881]: iscsiadm: No records found
May  9 23:16:40 cmp02 mdadm[2756]:    ...done.
May  9 23:16:40 cmp02 systemd[1]: Started LSB: MD monitoring daemon.
May  9 23:16:40 cmp02 systemd[1]: Started Login to default iSCSI targets.
May  9 23:16:40 cmp02 systemd[1]: Reached target Remote File Systems (Pre).
May  9 23:16:40 cmp02 systemd[1]: Reached target Remote File Systems.
May  9 23:16:40 cmp02 systemd[1]: Starting Permit User Sessions...
May  9 23:16:40 cmp02 systemd[1]: Starting LSB: automatic crash report generation...
May  9 23:16:40 cmp02 systemd[1]: Starting LSB: daemon to balance interrupts for SMP systems...
May  9 23:16:40 cmp02 systemd[1]: Started Permit User Sessions.
May  9 23:16:40 cmp02 systemd[1]: Starting Hold until boot process finishes up...
May  9 23:16:40 cmp02 systemd[1]: Starting Terminate Plymouth Boot Screen...
May  9 23:16:40 cmp02 irqbalance[2929]:  * Starting SMP IRQ Balancer: irqbalance
May  9 23:16:40 cmp02 systemd[1]: Started Hold until boot process finishes up.
May  9 23:16:40 cmp02 systemd[1]: Started LSB: Record successful boot for GRUB.
May  9 23:16:40 cmp02 systemd[1]: Started Terminate Plymouth Boot Screen.
May  9 23:16:40 cmp02 systemd[1]: Started Serial Getty on ttyS0.
May  9 23:16:40 cmp02 apport[2925]:  * Starting automatic crash report generation: apport
May  9 23:16:40 cmp02 systemd[1]: Starting Set console scheme...
May  9 23:16:40 cmp02 systemd[1]: Started Getty on tty1.
May  9 23:16:40 cmp02 systemd[1]: Reached target Login Prompts.
May  9 23:16:40 cmp02 polkitd[2857]: started daemon version 0.105 using authority implementation `local' version `0.105'
May  9 23:16:40 cmp02 dbus[2710]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
May  9 23:16:40 cmp02 systemd[1]: Started Authenticate and Authorize Users to Run Privileged Tasks.
May  9 23:16:40 cmp02 accounts-daemon[2665]: started daemon version 0.6.40
May  9 23:16:40 cmp02 systemd[1]: Started Accounts Service.
May  9 23:16:40 cmp02 irqbalance[2929]:    ...done.
May  9 23:16:40 cmp02 systemd[1]: Started LSB: daemon to balance interrupts for SMP systems.
May  9 23:16:40 cmp02 systemd[1]: Started Set console scheme.
May  9 23:16:40 cmp02 apport[2925]:    ...done.
May  9 23:16:40 cmp02 systemd[1]: Started LSB: automatic crash report generation.
May  9 23:16:40 cmp02 systemd[1]: Started OpenBSD Secure Shell server.
May  9 23:16:40 cmp02 cloud-init[2691]: Cloud-init v. 18.2 running 'modules:config' at Wed, 09 May 2018 23:16:40 +0000. Up 7.90 seconds.
May  9 23:16:40 cmp02 systemd[1]: Started Apply the settings specified in cloud-config.
May  9 23:16:41 cmp02 snapd[2790]: AppArmor status: apparmor is enabled and all features are available
May  9 23:16:41 cmp02 systemd[1]: Started LXD - container startup/shutdown.
May  9 23:16:41 cmp02 snapd[2790]: 2018/05/09 23:16:41.076474 daemon.go:323: started snapd/2.32.3.2 (series 16; classic) ubuntu/16.04 (amd64) linux/4.13.0-41-generic.
May  9 23:16:41 cmp02 systemd[1]: Started Snappy daemon.
May  9 23:16:41 cmp02 systemd[1]: Started The Salt Minion.
May  9 23:16:41 cmp02 systemd[1]: Reached target Multi-User System.
May  9 23:16:41 cmp02 systemd[1]: Reached target Graphical Interface.
May  9 23:16:41 cmp02 systemd[1]: Starting Execute cloud user/final scripts...
May  9 23:16:41 cmp02 systemd[1]: Starting Update UTMP about System Runlevel Changes...
May  9 23:16:41 cmp02 systemd[1]: Started Update UTMP about System Runlevel Changes.
May  9 23:16:41 cmp02 salt-minion[2824]: [INFO    ] Setting up the Salt Minion "cmp02.mcp-pike-ovn-noha.local"
May  9 23:16:41 cmp02 cloud-init[3063]: Cloud-init v. 18.2 running 'modules:final' at Wed, 09 May 2018 23:16:41 +0000. Up 9.47 seconds.
May  9 23:16:41 cmp02 cloud-init[3063]: Cloud-init v. 18.2 finished at Wed, 09 May 2018 23:16:41 +0000. Datasource DataSourceNoCloud [seed=/dev/sr0][dsmode=net].  Up 9.65 seconds
May  9 23:16:42 cmp02 systemd[1]: Started Execute cloud user/final scripts.
May  9 23:16:42 cmp02 systemd[1]: Reached target Cloud-init target.
May  9 23:16:42 cmp02 systemd[1]: Startup finished in 3.225s (kernel) + 6.484s (userspace) = 9.709s.
May  9 23:16:42 cmp02 salt-minion[2824]: [INFO    ] Starting up the Salt Minion
May  9 23:16:42 cmp02 salt-minion[2824]: [INFO    ] Starting pull socket on /var/run/salt/minion/minion_event_e795df387e_pull.ipc
May  9 23:16:42 cmp02 salt-minion[2824]: [INFO    ] Creating minion process manager
May  9 23:16:44 cmp02 salt-minion[2824]: [INFO    ] Executing command ['date', '+%z'] in directory '/root'
May  9 23:16:44 cmp02 salt-minion[2824]: [INFO    ] Updating job settings for scheduled job: __mine_interval
May  9 23:16:44 cmp02 salt-minion[2824]: [INFO    ] Added mine.update to scheduler
May  9 23:16:44 cmp02 salt-minion[2824]: [INFO    ] Minion is starting as user 'root'
May  9 23:16:44 cmp02 salt-minion[2824]: [INFO    ] Minion is ready to receive requests!
May  9 23:16:45 cmp02 salt-minion[2824]: [INFO    ] Running scheduled job: __mine_interval
May  9 23:16:48 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command test.ping with jid 20180509231648704984
May  9 23:16:48 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 3223
May  9 23:16:48 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231648704984
May  9 23:16:49 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command pkg.upgrade with jid 20180509231649521010
May  9 23:16:49 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 3228
May  9 23:16:49 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:16:50 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'dist-upgrade'] in directory '/root'
May  9 23:16:50 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef dist-upgrade.
May  9 23:16:59 cmp02 dbus[2710]: [system] Reloaded configuration
May  9 23:16:59 cmp02 kernel: [   27.325250] random: crng init done
May  9 23:16:59 cmp02 dbus[2710]: [system] Reloaded configuration
May  9 23:16:59 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231659540238
May  9 23:16:59 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 3336
May  9 23:16:59 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231659540238
May  9 23:17:01 cmp02 CRON[3491]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  9 23:17:04 cmp02 dbus[2710]: [system] Reloaded configuration
May  9 23:17:05 cmp02 dbus[2710]: [system] Reloaded configuration
May  9 23:17:09 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231709709607
May  9 23:17:09 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 4415
May  9 23:17:09 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231709709607
May  9 23:17:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:17:12 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231649521010
May  9 23:17:17 cmp02 systemd-timesyncd[537]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
May  9 23:17:17 cmp02 systemd-timesyncd[537]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
May  9 23:17:29 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509231729702807
May  9 23:17:29 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 4514
May  9 23:17:31 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:17:32 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ntp/init.sls'
May  9 23:17:32 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ntp/client.sls'
May  9 23:17:32 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ntp/server.sls'
May  9 23:17:33 cmp02 salt-minion[2824]: [INFO    ] Running state [ntp] at time 23:17:33.190398
May  9 23:17:33 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for ntp
May  9 23:17:33 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:17:33 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'ntp'] in directory '/root'
May  9 23:17:33 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:17:36 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:17:36 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'ntp'] in directory '/root'
May  9 23:17:36 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install ntp.
May  9 23:17:37 cmp02 systemd[1]: Reloading.
May  9 23:17:37 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:17:39 cmp02 systemd[1]: Reloading.
May  9 23:17:39 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:17:39 cmp02 systemd[1]: Reloading.
May  9 23:17:39 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:17:39 cmp02 systemd[1]: Starting LSB: Start NTP daemon...
May  9 23:17:39 cmp02 ntp[5652]:  * Starting NTP server ntpd
May  9 23:17:39 cmp02 ntpd[5673]: ntpd 4.2.8p4@1.3265-o Wed Feb 14 14:56:29 UTC 2018 (1): Starting
May  9 23:17:39 cmp02 ntpd[5673]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:116
May  9 23:17:39 cmp02 ntp[5652]:    ...done.
May  9 23:17:39 cmp02 systemd[1]: Started LSB: Start NTP daemon.
May  9 23:17:39 cmp02 ntpd[5677]: proto: precision = 0.062 usec (-24)
May  9 23:17:39 cmp02 ntpd[5677]: Listen and drop on 0 v6wildcard [::]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen and drop on 1 v4wildcard 0.0.0.0:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 2 lo 127.0.0.1:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 3 ens3 192.168.11.50:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 4 br-mesh 10.1.0.6:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 5 br-mgmt 172.16.10.53:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 6 br-ex 10.16.0.111:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 7 lo [::1]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 8 ens3 [fe80::5054:ff:fe90:6ff7%2]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 9 ens4 [fe80::5054:ff:fef6:3939%3]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 10 ens5 [fe80::5054:ff:fe53:d1ac%4]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 11 ens6 [fe80::5054:ff:fea3:a94f%5]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 12 br-mesh [fe80::5054:ff:fe53:d1ac%6]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 13 br-mgmt [fe80::5054:ff:fef6:3939%7]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 14 br-ex [fe80::5054:ff:fea3:a94f%8]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listen normally on 15 float-to-ex [fe80::ec65:21ff:fe6b:4c06%11]:123
May  9 23:17:39 cmp02 ntpd[5677]: Listening on routing socket on fd #32 for interface updates
May  9 23:17:39 cmp02 kernel: [   67.465309] kauditd_printk_skb: 4 callbacks suppressed
May  9 23:17:39 cmp02 kernel: [   67.465310] audit: type=1400 audit(1525907859.675:15): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=5686 comm="apparmor_parser"
May  9 23:17:39 cmp02 systemd[1]: Reloading.
May  9 23:17:39 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:17:39 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231739814313
May  9 23:17:39 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 5721
May  9 23:17:39 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231739814313
May  9 23:17:40 cmp02 ntpd[5677]: Soliciting pool server 193.228.143.12
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:17:41 cmp02 salt-minion[2824]: 'ntp' changed from 'absent' to '1:4.2.8p4+dfsg-3ubuntu5.8'
May  9 23:17:41 cmp02 salt-minion[2824]: 'libopts25' changed from 'absent' to '1:5.18.7-3'
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Completed state [ntp] at time 23:17:41.425517 duration_in_ms=8235.12
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/ntp.conf] at time 23:17:41.431077
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/ntp.conf
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ntp/files/ntp.conf'
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:17:41 cmp02 salt-minion[2824]: ---
May  9 23:17:41 cmp02 salt-minion[2824]: +++
May  9 23:17:41 cmp02 salt-minion[2824]: @@ -1,66 +1,26 @@
May  9 23:17:41 cmp02 salt-minion[2824]: -# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -driftfile /var/lib/ntp/ntp.drift
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -# Enable this if you want statistics to be logged.
May  9 23:17:41 cmp02 salt-minion[2824]: -#statsdir /var/log/ntpstats/
May  9 23:17:41 cmp02 salt-minion[2824]: +# ntpd will only synchronize your clock.
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -statistics loopstats peerstats clockstats
May  9 23:17:41 cmp02 salt-minion[2824]: -filegen loopstats file loopstats type day enable
May  9 23:17:41 cmp02 salt-minion[2824]: -filegen peerstats file peerstats type day enable
May  9 23:17:41 cmp02 salt-minion[2824]: -filegen clockstats file clockstats type day enable
May  9 23:17:41 cmp02 salt-minion[2824]: +# For details, see:
May  9 23:17:41 cmp02 salt-minion[2824]: +# - the ntp.conf man page
May  9 23:17:41 cmp02 salt-minion[2824]: +# - http://support.ntp.org/bin/view/Support/GettingStarted
May  9 23:17:41 cmp02 salt-minion[2824]: +# - https://wiki.archlinux.org/index.php/Network_Time_Protocol_daemon
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -# Specify one or more NTP servers.
May  9 23:17:41 cmp02 salt-minion[2824]: +# Associate to cloud NTP pool servers
May  9 23:17:41 cmp02 salt-minion[2824]: +server 1.se.pool.ntp.org iburst
May  9 23:17:41 cmp02 salt-minion[2824]: +server 0.se.pool.ntp.org
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -# Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
May  9 23:17:41 cmp02 salt-minion[2824]: -# on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
May  9 23:17:41 cmp02 salt-minion[2824]: -# more information.
May  9 23:17:41 cmp02 salt-minion[2824]: -pool 0.ubuntu.pool.ntp.org iburst
May  9 23:17:41 cmp02 salt-minion[2824]: -pool 1.ubuntu.pool.ntp.org iburst
May  9 23:17:41 cmp02 salt-minion[2824]: -pool 2.ubuntu.pool.ntp.org iburst
May  9 23:17:41 cmp02 salt-minion[2824]: -pool 3.ubuntu.pool.ntp.org iburst
May  9 23:17:41 cmp02 salt-minion[2824]: +# Exchange time with everybody, but don't allow configuration.
May  9 23:17:41 cmp02 salt-minion[2824]: +restrict -4 default kod notrap nomodify nopeer noquery
May  9 23:17:41 cmp02 salt-minion[2824]: +restrict -6 default kod notrap nomodify nopeer noquery
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -# Use Ubuntu's ntp server as a fallback.
May  9 23:17:41 cmp02 salt-minion[2824]: -pool ntp.ubuntu.com
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
May  9 23:17:41 cmp02 salt-minion[2824]: -# details.  The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
May  9 23:17:41 cmp02 salt-minion[2824]: -# might also be helpful.
May  9 23:17:41 cmp02 salt-minion[2824]: -#
May  9 23:17:41 cmp02 salt-minion[2824]: -# Note that "restrict" applies to both servers and clients, so a configuration
May  9 23:17:41 cmp02 salt-minion[2824]: -# that might be intended to block requests from certain clients could also end
May  9 23:17:41 cmp02 salt-minion[2824]: -# up blocking replies from your own upstream servers.
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -# By default, exchange time with everybody, but don't allow configuration.
May  9 23:17:41 cmp02 salt-minion[2824]: -restrict -4 default kod notrap nomodify nopeer noquery limited
May  9 23:17:41 cmp02 salt-minion[2824]: -restrict -6 default kod notrap nomodify nopeer noquery limited
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -# Local users may interrogate the ntp server more closely.
May  9 23:17:41 cmp02 salt-minion[2824]: +# Only allow read-only access from localhost
May  9 23:17:41 cmp02 salt-minion[2824]:  restrict 127.0.0.1
May  9 23:17:41 cmp02 salt-minion[2824]:  restrict ::1
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -# Needed for adding pool entries
May  9 23:17:41 cmp02 salt-minion[2824]: -restrict source notrap nomodify noquery
May  9 23:17:41 cmp02 salt-minion[2824]: +# mode7 is required for collectd monitoring
May  9 23:17:41 cmp02 salt-minion[2824]:  
May  9 23:17:41 cmp02 salt-minion[2824]: -# Clients from this (example!) subnet have unlimited access, but only if
May  9 23:17:41 cmp02 salt-minion[2824]: -# cryptographically authenticated.
May  9 23:17:41 cmp02 salt-minion[2824]: -#restrict 192.168.123.0 mask 255.255.255.0 notrust
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -# If you want to provide time to your local subnet, change the next line.
May  9 23:17:41 cmp02 salt-minion[2824]: -# (Again, the address is an example only.)
May  9 23:17:41 cmp02 salt-minion[2824]: -#broadcast 192.168.123.255
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -# If you want to listen to time broadcasts on your local subnet, de-comment the
May  9 23:17:41 cmp02 salt-minion[2824]: -# next lines.  Please do this only if you trust everybody on the network!
May  9 23:17:41 cmp02 salt-minion[2824]: -#disable auth
May  9 23:17:41 cmp02 salt-minion[2824]: -#broadcastclient
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -#Changes recquired to use pps synchonisation as explained in documentation:
May  9 23:17:41 cmp02 salt-minion[2824]: -#http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm#AEN3918
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -#server 127.127.8.1 mode 135 prefer    # Meinberg GPS167 with PPS
May  9 23:17:41 cmp02 salt-minion[2824]: -#fudge 127.127.8.1 time1 0.0042        # relative to PPS for my hardware
May  9 23:17:41 cmp02 salt-minion[2824]: -
May  9 23:17:41 cmp02 salt-minion[2824]: -#server 127.127.22.1                   # ATOM(PPS)
May  9 23:17:41 cmp02 salt-minion[2824]: -#fudge 127.127.22.1 flag3 1            # enable PPS API
May  9 23:17:41 cmp02 salt-minion[2824]: +# Location of drift file
May  9 23:17:41 cmp02 salt-minion[2824]: +driftfile /var/lib/ntp/ntp.drift
May  9 23:17:41 cmp02 salt-minion[2824]: +logfile /var/log/ntp.log
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/ntp.conf] at time 23:17:41.601814 duration_in_ms=170.736
May  9 23:17:41 cmp02 ntpd[5677]: Soliciting pool server 193.228.143.14
May  9 23:17:41 cmp02 ntpd[5677]: Soliciting pool server 2.248.181.59
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Running state [ntp] at time 23:17:41.991542
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Executing state service.running for ntp
May  9 23:17:41 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'status', 'ntp.service', '-n', '0'] in directory '/root'
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'ntp.service'] in directory '/root'
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ntp.service'] in directory '/root'
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] The service ntp is already running
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Completed state [ntp] at time 23:17:42.040436 duration_in_ms=48.894
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Running state [ntp] at time 23:17:42.041209
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Executing state service.mod_watch for ntp
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'ntp.service'] in directory '/root'
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ntp.service'] in directory '/root'
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'ntp.service'] in directory '/root'
May  9 23:17:42 cmp02 systemd[1]: Started /bin/systemctl restart ntp.service.
May  9 23:17:42 cmp02 systemd[1]: Stopping LSB: Start NTP daemon...
May  9 23:17:42 cmp02 ntp[5818]:  * Stopping NTP server ntpd
May  9 23:17:42 cmp02 ntpd[5677]: ntpd exiting on signal 15 (Terminated)
May  9 23:17:42 cmp02 ntp[5818]:    ...done.
May  9 23:17:42 cmp02 ntpd[5677]: 193.228.143.12 local addr 192.168.11.50 -> <null>
May  9 23:17:42 cmp02 ntpd[5677]: 2.248.181.59 local addr 192.168.11.50 -> <null>
May  9 23:17:42 cmp02 systemd[1]: Stopped LSB: Start NTP daemon.
May  9 23:17:42 cmp02 systemd[1]: Starting LSB: Start NTP daemon...
May  9 23:17:42 cmp02 ntp[5830]:  * Starting NTP server ntpd
May  9 23:17:42 cmp02 ntpd[5850]: ntpd 4.2.8p4@1.3265-o Wed Feb 14 14:56:29 UTC 2018 (1): Starting
May  9 23:17:42 cmp02 ntpd[5850]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:116
May  9 23:17:42 cmp02 ntp[5830]:    ...done.
May  9 23:17:42 cmp02 systemd[1]: Started LSB: Start NTP daemon.
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] {'ntp': True}
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Completed state [ntp] at time 23:17:42.162570 duration_in_ms=121.36
May  9 23:17:42 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231729702807
May  9 23:17:42 cmp02 ntpd[5853]: proto: precision = 0.062 usec (-24)
May  9 23:17:42 cmp02 ntpd[5853]: restrict 0.0.0.0: KOD does nothing without LIMITED.
May  9 23:17:42 cmp02 ntpd[5853]: restrict ::: KOD does nothing without LIMITED.
May  9 23:17:42 cmp02 ntpd[5853]: switching logging to file /var/log/ntp.log
May  9 23:17:58 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509231758051843
May  9 23:17:58 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 5877
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nfs/init.sls'
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nfs/client.sls'
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nfs/map.jinja'
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Running state [rpcbind] at time 23:18:00.876397
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for rpcbind
May  9 23:18:00 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:18:01 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'rpcbind'] in directory '/root'
May  9 23:18:01 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:18:03 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:18:03 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'rpcbind'] in directory '/root'
May  9 23:18:03 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install rpcbind.
May  9 23:18:05 cmp02 systemd[1]: Reloading.
May  9 23:18:05 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:05 cmp02 systemd[1]: Reloading.
May  9 23:18:05 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:06 cmp02 systemd[1]: Reloading.
May  9 23:18:06 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:06 cmp02 systemd[1]: Reloading.
May  9 23:18:06 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:06 cmp02 systemd[1]: Reloading.
May  9 23:18:06 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:06 cmp02 systemd[1]: Listening on RPCbind Server Activation Socket.
May  9 23:18:06 cmp02 systemd[1]: Starting RPC bind portmap service...
May  9 23:18:06 cmp02 rpcbind[6893]: rpcbind: xdr_/run/rpcbind/rpcbind.xdr: failed
May  9 23:18:06 cmp02 rpcbind[6893]: rpcbind: xdr_/run/rpcbind/portmap.xdr: failed
May  9 23:18:06 cmp02 systemd[1]: Started RPC bind portmap service.
May  9 23:18:06 cmp02 systemd[1]: Reached target RPC Port Mapper.
May  9 23:18:06 cmp02 systemd[1]: Reloading.
May  9 23:18:06 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509231808170572
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:18:08 cmp02 salt-minion[2824]: 'rpcbind' changed from 'absent' to '0.2.3-0.2'
May  9 23:18:08 cmp02 salt-minion[2824]: 'libtirpc1' changed from 'absent' to '0.2.5-1'
May  9 23:18:08 cmp02 salt-minion[2824]: 'portmap' changed from 'absent' to '1'
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 6963
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231808170572
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Completed state [rpcbind] at time 23:18:08.224878 duration_in_ms=7348.482
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Running state [nfs-common] at time 23:18:08.237449
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for nfs-common
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:18:08 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'nfs-common'] in directory '/root'
May  9 23:18:08 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install nfs-common.
May  9 23:18:10 cmp02 systemd[1]: Reloading.
May  9 23:18:10 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:11 cmp02 systemd[1]: Reloading.
May  9 23:18:12 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:12 cmp02 systemd[1]: Reloading.
May  9 23:18:12 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:18:13 cmp02 salt-minion[2824]: 'keyutils' changed from 'absent' to '1.5.9-8ubuntu1'
May  9 23:18:13 cmp02 salt-minion[2824]: 'nfs-common' changed from 'absent' to '1:1.2.8-9ubuntu12.1'
May  9 23:18:13 cmp02 salt-minion[2824]: 'libnfsidmap2' changed from 'absent' to '0.25-5'
May  9 23:18:13 cmp02 salt-minion[2824]: 'nfs-client' changed from 'absent' to '1'
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Completed state [nfs-common] at time 23:18:13.469404 duration_in_ms=5231.955
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Running state [/var/lib/nova/instances] at time 23:18:13.472701
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing state file.directory for /var/lib/nova/instances
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] {'/var/lib/nova/instances': 'New Dir'}
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Completed state [/var/lib/nova/instances] at time 23:18:13.477221 duration_in_ms=4.52
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Running state [/var/lib/nova/instances] at time 23:18:13.479554
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing state mount.mounted for /var/lib/nova/instances
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing command 'mount -l' in directory '/root'
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing command 'blkid' in directory '/root'
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing command 'mount -o defaults -t nfs 172.16.10.36:/srv/nova/instances /var/lib/nova/instances ' in directory '/root'
May  9 23:18:13 cmp02 kernel: [  101.404010] FS-Cache: Loaded
May  9 23:18:13 cmp02 kernel: [  101.417968] RPC: Registered named UNIX socket transport module.
May  9 23:18:13 cmp02 kernel: [  101.417969] RPC: Registered udp transport module.
May  9 23:18:13 cmp02 kernel: [  101.417970] RPC: Registered tcp transport module.
May  9 23:18:13 cmp02 kernel: [  101.417971] RPC: Registered tcp NFSv4.1 backchannel transport module.
May  9 23:18:13 cmp02 kernel: [  101.432595] FS-Cache: Netfs 'nfs' registered for caching
May  9 23:18:13 cmp02 kernel: [  101.450757] NFS: Registering the id_resolver key type
May  9 23:18:13 cmp02 kernel: [  101.450764] Key type id_resolver registered
May  9 23:18:13 cmp02 kernel: [  101.450765] Key type id_legacy registered
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing command 'mount -l' in directory '/root'
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Executing command 'blkid' in directory '/root'
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] {'mount': True, 'persist': 'new'}
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Completed state [/var/lib/nova/instances] at time 23:18:13.775360 duration_in_ms=295.806
May  9 23:18:13 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509231758051843
May  9 23:29:46 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509232946930880
May  9 23:29:46 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 8093
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/init.sls'
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/volume.sls'
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/user.sls'
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Running state [cinder] at time 23:29:49.781432
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Executing state group.present for cinder
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Executing command ['groupadd', '-g 304', '-r', 'cinder'] in directory '/root'
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] {'passwd': 'x', 'gid': 304, 'name': 'cinder', 'members': []}
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Completed state [cinder] at time 23:29:49.864742 duration_in_ms=83.311
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Running state [cinder] at time 23:29:49.865127
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Executing state user.present for cinder
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Executing command ['useradd', '-s', '/bin/false', '-u', '304', '-g', '304', '-m', '-d', '/var/lib/cinder', '-r', 'cinder'] in directory '/root'
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] {'shell': '/bin/false', 'workphone': '', 'uid': 304, 'passwd': 'x', 'roomnumber': '', 'groups': ['cinder'], 'home': '/var/lib/cinder', 'name': 'cinder', 'gid': 304, 'fullname': '', 'homephone': ''}
May  9 23:29:49 cmp02 salt-minion[2824]: [INFO    ] Completed state [cinder] at time 23:29:49.898846 duration_in_ms=33.718
May  9 23:29:50 cmp02 salt-minion[2824]: [INFO    ] Running state [cinder-volume] at time 23:29:50.390788
May  9 23:29:50 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for cinder-volume
May  9 23:29:50 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:29:50 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'cinder-volume'] in directory '/root'
May  9 23:29:50 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:29:53 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:29:53 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'cinder-volume'] in directory '/root'
May  9 23:29:53 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install cinder-volume.
May  9 23:29:57 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509232957050666
May  9 23:29:57 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 8563
May  9 23:29:57 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509232957050666
May  9 23:30:07 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233007088972
May  9 23:30:07 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 8568
May  9 23:30:07 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233007088972
May  9 23:30:17 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233017104476
May  9 23:30:17 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 8573
May  9 23:30:17 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233017104476
May  9 23:30:27 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233027137633
May  9 23:30:27 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 9302
May  9 23:30:27 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233027137633
May  9 23:30:37 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233037170589
May  9 23:30:37 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 10930
May  9 23:30:37 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233037170589
May  9 23:30:37 cmp02 systemd[1]: Reloading.
May  9 23:30:37 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:30:41 cmp02 systemd[1]: Reloading.
May  9 23:30:41 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:30:41 cmp02 systemd[1]: Reloading.
May  9 23:30:41 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:30:41 cmp02 systemd[1]: Reloading.
May  9 23:30:41 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:30:41 cmp02 systemd[1]: Starting LSB: Apache2 web server...
May  9 23:30:41 cmp02 apache2[11823]:  * Starting Apache httpd web server apache2
May  9 23:30:42 cmp02 apache2[11823]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.10.53. Set the 'ServerName' directive globally to suppress this message
May  9 23:30:43 cmp02 apache2[11823]:  *
May  9 23:30:43 cmp02 systemd[1]: Started LSB: Apache2 web server.
May  9 23:30:46 cmp02 libapache2-mod-wsgi: apache2_invoke: Enable module wsgi
May  9 23:30:46 cmp02 systemd[1]: Reloading.
May  9 23:30:46 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:30:46 cmp02 systemd[1]: Stopping LSB: Apache2 web server...
May  9 23:30:46 cmp02 apache2[12132]:  * Stopping Apache httpd web server apache2
May  9 23:30:47 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233047191791
May  9 23:30:47 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 12156
May  9 23:30:47 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233047191791
May  9 23:30:47 cmp02 apache2[12132]:  *
May  9 23:30:47 cmp02 systemd[1]: Stopped LSB: Apache2 web server.
May  9 23:30:47 cmp02 systemd[1]: Starting LSB: Apache2 web server...
May  9 23:30:47 cmp02 apache2[12161]:  * Starting Apache httpd web server apache2
May  9 23:30:47 cmp02 apache2[12161]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.16.10.53. Set the 'ServerName' directive globally to suppress this message
May  9 23:30:48 cmp02 apache2[12161]:  *
May  9 23:30:48 cmp02 systemd[1]: Started LSB: Apache2 web server.
May  9 23:30:57 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233057214918
May  9 23:30:57 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 12809
May  9 23:30:57 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233057214918
May  9 23:31:02 cmp02 systemd[1]: Reloading.
May  9 23:31:02 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:02 cmp02 systemd[1]: Reloading.
May  9 23:31:02 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:02 cmp02 systemd[1]: Starting LSB: Start LIO targets...
May  9 23:31:07 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233107434482
May  9 23:31:07 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 13074
May  9 23:31:07 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233107434482
May  9 23:31:12 cmp02 rtslib-fb-targetctl[13052]:  * Loading rstlib-fb targetctl targetctl
May  9 23:31:12 cmp02 kernel: [  880.434183] Rounding down aligned max_sectors from 4294967295 to 4294967288
May  9 23:31:12 cmp02 rtslib-fb-targetctl[13052]:    ...done.
May  9 23:31:12 cmp02 systemd[1]: Started LSB: Start LIO targets.
May  9 23:31:14 cmp02 systemd[1]: Reloading.
May  9 23:31:14 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:14 cmp02 systemd[1]: Reloading.
May  9 23:31:14 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:14 cmp02 systemd[1]: Reloading.
May  9 23:31:14 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:14 cmp02 systemd[1]: Starting (i)SCSI target daemon...
May  9 23:31:14 cmp02 tgtd[13270]: tgtd: iser_ib_init(3434) Failed to initialize RDMA; load kernel modules?
May  9 23:31:14 cmp02 tgtd[13270]: tgtd: work_timer_start(150) use signal based scheduler
May  9 23:31:14 cmp02 tgtd[13270]: tgtd: bs_init(387) use signalfd notification
May  9 23:31:14 cmp02 systemd[1]: Started (i)SCSI target daemon.
May  9 23:31:17 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233117491364
May  9 23:31:17 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 13442
May  9 23:31:17 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233117491364
May  9 23:31:21 cmp02 systemd[1]: Reloading.
May  9 23:31:21 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:21 cmp02 systemd[1]: Reloading.
May  9 23:31:21 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:21 cmp02 systemd[1]: Reloading.
May  9 23:31:21 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:21 cmp02 systemd[1]: Starting OpenStack Cinder Volume...
May  9 23:31:21 cmp02 systemd[1]: Started OpenStack Cinder Volume.
May  9 23:31:21 cmp02 systemd[1]: Reloading.
May  9 23:31:22 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:31:23 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:31:23 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-routes' changed from 'absent' to '2.4.1-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-retrying' changed from 'absent' to '1.3.3-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libiscsi2' changed from 'absent' to '1.12.0-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-kombu' changed from 'absent' to '4.1.0-1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.concurrency' changed from 'absent' to '3.21.0-1~u16.04+mcp3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-sqlparse' changed from 'absent' to '0.2.2-1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-monotonic' changed from 'absent' to '0.6-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'liblapack3' changed from 'absent' to '3.6.0-2ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-psycopg2' changed from 'absent' to '2.6.1-1build2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-secretstorage' changed from 'absent' to '2.1.3-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-numpy' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-glanceclient' changed from 'absent' to '1:2.8.0-1~u16.04+mcp12'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-formencode' changed from 'absent' to '1.3.0-0ubuntu5'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-functools32' changed from 'absent' to '3.2.3.2-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libaprutil1-ldap' changed from 'absent' to '1.5.4-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-migrate' changed from 'absent' to '0.11.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-cachetools' changed from 'absent' to '1.1.6-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.serialization' changed from 'absent' to '2.20.2-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'apache2' changed from 'absent' to '2.4.18-2ubuntu3.8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libquadmath0' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-egenix-mxtools' changed from 'absent' to '3.2.9-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-blinker' changed from 'absent' to '1.3.dfsg2-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-roman' changed from 'absent' to '2.0.0-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'apache2-bin' changed from 'absent' to '2.4.18-2ubuntu3.8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'sg3-utils' changed from 'absent' to '1.40-0ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-tenacity' changed from 'absent' to '3.3.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.versionedobjects' changed from 'absent' to '1.26.1-1~u16.04+mcp7'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-setuptools' changed from 'absent' to '36.2.7-2~cloud0'
May  9 23:31:23 cmp02 salt-minion[2824]: 'docutils-doc' changed from 'absent' to '0.12+dfsg-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-dbus' changed from 'absent' to '1.2.0-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'librados2' changed from 'absent' to '12.2.4-0ubuntu0.17.10.1~cloud0'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-fixtures' changed from 'absent' to '3.0.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pycadf' changed from 'absent' to '2.6.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-httplib2' changed from 'absent' to '0.9.1+dfsg-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-testtools' changed from 'absent' to '1.8.1-0ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-egenix-mxdatetime' changed from 'absent' to '3.2.9-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-anyjson' changed from 'absent' to '0.3.3-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libnss3-nssdb' changed from 'absent' to '2:3.28.4-0ubuntu0.16.04.3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-jwt' changed from 'absent' to '1.3.0-1ubuntu0.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-prettytable' changed from 'absent' to '0.7.2-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pymemcache' changed from 'absent' to '1.3.2-2ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libblas3' changed from 'absent' to '3.6.0-2ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-netaddr' changed from 'absent' to '0.7.18-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-dnspython' changed from 'absent' to '1.14.0-3.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-babel' changed from 'absent' to '2.3.4+dfsg.1-2.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-paramiko' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-jsonschema' changed from 'absent' to '2.5.1-4'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pil' changed from 'absent' to '3.1.2-0ubuntu1.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.privsep' changed from 'absent' to '1.22.1-1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-lxml' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-suds' changed from 'absent' to '0.7~git20150727.94664dd-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.db' changed from 'absent' to '4.25.1-2~u16.04+mcp4'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-sqlalchemy-ext' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libnspr4' changed from 'absent' to '2:4.13.1-0ubuntu0.16.04.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-os-win' changed from 'absent' to '2.2.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libpaper-utils' changed from 'absent' to '1.1.24+nmu4ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-tz' changed from 'absent' to '2014.10~dfsg1-0ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-simplejson' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libtiff5' changed from 'absent' to '4.0.6-1ubuntu0.4'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-funcsigs' changed from 'absent' to '1.0.2-3~cloud0'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-scgi' changed from 'absent' to '1.13-1.1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-pil' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-rtslib-fb' changed from 'absent' to '2.1.57+debian-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-zake' changed from 'absent' to '0.1.6-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-repoze.lru' changed from 'absent' to '0.6-6'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-posix-ipc' changed from 'absent' to '0.9.8-2build2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'formencode-i18n' changed from 'absent' to '1.3.0-0ubuntu5'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo-context' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-testtools' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-alembic' changed from 'absent' to '0.8.10-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'docutils' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'ieee-data' changed from 'absent' to '20150531.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-dbus' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.middleware' changed from 'absent' to '3.30.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pygments' changed from 'absent' to '2.2.0+dfsg-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pillow' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libpaperg' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'liblapack.so.3' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-netifaces' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-numpy-dev' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'liblcms2-2' changed from 'absent' to '2.6-3ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'docutils-common' changed from 'absent' to '0.12+dfsg-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.context' changed from 'absent' to '1:2.17.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-f2py' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'librdmacm1' changed from 'absent' to '1.0.21-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'qemu-block-extra' changed from 'absent' to '1:2.11+dfsg-1.1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'sharutils' changed from 'absent' to '1:4.15.2-1ubuntu0.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pyasn1-modules' changed from 'absent' to '0.0.7-0.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'qemu-utils' changed from 'absent' to '1:2.11+dfsg-1.1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libaprutil1-dbd-sqlite3' changed from 'absent' to '1.5.4-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-pyinotify' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-webob' changed from 'absent' to '1:1.7.2-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pyparsing' changed from 'absent' to '2.1.10+dfsg1-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-babel-localedata' changed from 'absent' to '2.3.4+dfsg.1-2.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-positional' changed from 'absent' to '1.1.1-3.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-barbicanclient' changed from 'absent' to '4.5.2-1.1~u16.04+mcp8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-castellan' changed from 'absent' to '0.12.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-cmd2' changed from 'absent' to '0.6.8-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.vmware' changed from 'absent' to '2.17.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-distribute' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-linecache2' changed from 'absent' to '1.0.0-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libconfig-general-perl' changed from 'absent' to '2.60-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'httpd-cgi' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libsgutils2-2' changed from 'absent' to '1.40-0ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-iso8601' changed from 'absent' to '0.1.11-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-jsonpatch' changed from 'absent' to '1.19-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'alembic' changed from 'absent' to '0.8.10-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libwebpmux1' changed from 'absent' to '0.4.4-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libapr1' changed from 'absent' to '1.5.2-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-googleapi' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'tgt' changed from 'absent' to '1:1.0.63-1ubuntu1.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.policy' changed from 'absent' to '1.25.1-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-stevedore' changed from 'absent' to '1:1.25.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-paste' changed from 'absent' to '1.7.5.1-6ubuntu3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-googleapi' changed from 'absent' to '1.4.2-1ubuntu1.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-lxml' changed from 'absent' to '3.5.0-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.config' changed from 'absent' to '1:4.11.1-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libnss3' changed from 'absent' to '2:3.28.4-0ubuntu0.16.04.3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-paramiko' changed from 'absent' to '2.0.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'apache2-utils' changed from 'absent' to '2.4.18-2ubuntu3.8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-futurist' changed from 'absent' to '0.13.0-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'httpd' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libpaper1' changed from 'absent' to '1.1.24+nmu4ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-fasteners' changed from 'absent' to '0.12.0-2ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-gi' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oauth2client' changed from 'absent' to '2.0.1-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-mimeparse' changed from 'absent' to '0.1.4-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pastedeploy-tpl' changed from 'absent' to '1.5.2-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oauthlib' changed from 'absent' to '1.0.3-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo-db' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libblas-common' changed from 'absent' to '3.6.0-2ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libgfortran3' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-gi' changed from 'absent' to '3.20.0-0ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libpq5' changed from 'absent' to '9.5.12-0ubuntu0.16.04'
May  9 23:31:23 cmp02 salt-minion[2824]: 'pycadf-common' changed from 'absent' to '2.6.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-contextlib2' changed from 'absent' to '0.5.1-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libjpeg8' changed from 'absent' to '8c-2ubuntu8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-novaclient' changed from 'absent' to '2:9.1.1-1~u16.04+mcp10'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.utils' changed from 'absent' to '3.28.2-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-taskflow' changed from 'absent' to '2.9.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libaio1' changed from 'absent' to '0.3.110-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pika-pool' changed from 'absent' to '0.1.3-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-automaton' changed from 'absent' to '1.2.0-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-warlock' changed from 'absent' to '1.1.0-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.rootwrap' changed from 'absent' to '5.9.2-1~u16.04+mcp4'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-iso8601' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-numpy' changed from 'absent' to '1:1.11.0-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-simplejson' changed from 'absent' to '3.8.1-1ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-wrapt' changed from 'absent' to '1.8.0-5build2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-tooz' changed from 'absent' to '1.47.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-docutils' changed from 'absent' to '0.12+dfsg-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-openid' changed from 'absent' to '2.2.5-6'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pastedeploy' changed from 'absent' to '1.5.2-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-cmd2' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pastescript' changed from 'absent' to '1.7.5-3build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-zope.interface' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-cliff' changed from 'absent' to '2.8.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.i18n' changed from 'absent' to '3.17.0-1~u16.04+mcp3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-bs4' changed from 'absent' to '4.6.0-1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'cinder-volume' changed from 'absent' to '2:11.1.0-1~u16.04+mcp88'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.reports' changed from 'absent' to '1.17.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-networkx' changed from 'absent' to '1.11-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-statsd' changed from 'absent' to '3.2.1-2~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libxslt1.1' changed from 'absent' to '1.1.28-2.1ubuntu0.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-keyring' changed from 'absent' to '8.5.1-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-redis' changed from 'absent' to '2.10.5-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo-utils' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libblas.so.3' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'apache2-data' changed from 'absent' to '2.4.18-2ubuntu3.8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libapache2-mod-wsgi' changed from 'absent' to '4.4.15-0.1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-unicodecsv' changed from 'absent' to '0.14.1-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-extras' changed from 'absent' to '0.0.3-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-mock' changed from 'absent' to '2.0.0-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-rfc3986' changed from 'absent' to '0.3.1-2.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-eventlet' changed from 'absent' to '0.20.0-4~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'thin-provisioning-tools' changed from 'absent' to '0.5.6-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-unittest2' changed from 'absent' to '1.1.0-6.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-pyparsing' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-uritemplate' changed from 'absent' to '0.6-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.log' changed from 'absent' to '3.30.2-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pyinotify' changed from 'absent' to '0.9.6-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libjpeg-turbo8' changed from 'absent' to '1.4.2-0ubuntu3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-amqp' changed from 'absent' to '2.2.1-1~exp1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-cinder' changed from 'absent' to '2:11.1.0-1~u16.04+mcp88'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libwebp5' changed from 'absent' to '0.4.4-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-zope.interface' changed from 'absent' to '4.1.3-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libaprutil1' changed from 'absent' to '1.5.4-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-numpy-abi9' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-vine' changed from 'absent' to '1.1.3+dfsg-2~u16.04+mcp3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libpython2.7' changed from 'absent' to '2.7.12-1ubuntu0~16.04.3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-defusedxml' changed from 'absent' to '0.5.0-1~u16.04+mcp1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-kazoo' changed from 'absent' to '2.2.1-1ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-decorator' changed from 'absent' to '4.0.6-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-osprofiler' changed from 'absent' to '1.11.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'httpd-wsgi' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.messaging' changed from 'absent' to '5.30.2-1~u16.04+mcp8'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-os-brick' changed from 'absent' to '1.15.2-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-debtcollector' changed from 'absent' to '1.3.0-2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-keyrings.alt' changed from 'absent' to '1.1.1-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo-log' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-json-pointer' changed from 'absent' to '1.9-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pbr' changed from 'absent' to '2.0.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-html5lib' changed from 'absent' to '0.999-4'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-swiftclient' changed from 'absent' to '1:3.4.0-1~u16.04+mcp3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-pika' changed from 'absent' to '0.10.0-1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-keystoneclient' changed from 'absent' to '1:3.13.0-1~u16.04+mcp6'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-greenlet' changed from 'absent' to '0.4.9-2fakesync1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-sqlalchemy-ext' changed from 'absent' to '1.0.13+ds1-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo.service' changed from 'absent' to '1.25.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'librbd1' changed from 'absent' to '12.2.4-0ubuntu0.17.10.1~cloud0'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libibverbs1' changed from 'absent' to '1.1.8-1.1ubuntu2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'apache2-api-20120211' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-ceilometerclient' changed from 'absent' to '2.9.0-2~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'liblua5.1-0' changed from 'absent' to '5.1.5-8ubuntu1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'os-brick-common' changed from 'absent' to '1.15.2-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-zopeinterface' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-traceback2' changed from 'absent' to '1.4.0-3'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-numpy-api10' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-keystoneauth1' changed from 'absent' to '3.1.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-tempita' changed from 'absent' to '0.5.2-1build1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-sqlalchemy' changed from 'absent' to '1.0.13+ds1-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-keystonemiddleware' changed from 'absent' to '4.17.0-1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-zope' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-voluptuous' changed from 'absent' to '0.9.3-1.1~u16.04+mcp2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'ssl-cert' changed from 'absent' to '1.0.37'
May  9 23:31:23 cmp02 salt-minion[2824]: 'cinder-common' changed from 'absent' to '2:11.1.0-1~u16.04+mcp88'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-oslo-rootwrap' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-netifaces' changed from 'absent' to '0.10.4-0.1build2'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python-rsa' changed from 'absent' to '3.2.3-1.1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'python2.7-rtslib-fb' changed from 'absent' to '1'
May  9 23:31:23 cmp02 salt-minion[2824]: 'libjbig0' changed from 'absent' to '2.1-3.1'
May  9 23:31:23 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:31:23 cmp02 salt-minion[2824]: [INFO    ] Completed state [cinder-volume] at time 23:31:23.557296 duration_in_ms=93166.509
May  9 23:31:23 cmp02 salt-minion[2824]: [INFO    ] Running state [lvm2] at time 23:31:23.567902
May  9 23:31:23 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for lvm2
May  9 23:31:24 cmp02 systemd[1]: cinder-volume.service: Main process exited, code=exited, status=1/FAILURE
May  9 23:31:24 cmp02 systemd[1]: cinder-volume.service: Unit entered failed state.
May  9 23:31:24 cmp02 systemd[1]: cinder-volume.service: Failed with result 'exit-code'.
May  9 23:31:24 cmp02 systemd[1]: cinder-volume.service: Service hold-off time over, scheduling restart.
May  9 23:31:24 cmp02 systemd[1]: Stopped OpenStack Cinder Volume.
May  9 23:31:24 cmp02 systemd[1]: Starting OpenStack Cinder Volume...
May  9 23:31:24 cmp02 systemd[1]: Started OpenStack Cinder Volume.
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [lvm2] at time 23:31:24.841531 duration_in_ms=1273.63
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Running state [sysfsutils] at time 23:31:24.841907
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for sysfsutils
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [sysfsutils] at time 23:31:24.852100 duration_in_ms=10.192
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Running state [sg3-utils] at time 23:31:24.852408
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for sg3-utils
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [sg3-utils] at time 23:31:24.861240 duration_in_ms=8.832
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Running state [python-cinder] at time 23:31:24.861544
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-cinder
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-cinder] at time 23:31:24.869238 duration_in_ms=7.694
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Running state [python-mysqldb] at time 23:31:24.869541
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-mysqldb
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:31:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'python-mysqldb'] in directory '/root'
May  9 23:31:24 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install python-mysqldb.
May  9 23:31:26 cmp02 systemd[1]: cinder-volume.service: Main process exited, code=exited, status=1/FAILURE
May  9 23:31:26 cmp02 systemd[1]: cinder-volume.service: Unit entered failed state.
May  9 23:31:26 cmp02 systemd[1]: cinder-volume.service: Failed with result 'exit-code'.
May  9 23:31:27 cmp02 systemd[1]: cinder-volume.service: Service hold-off time over, scheduling restart.
May  9 23:31:27 cmp02 systemd[1]: Stopped OpenStack Cinder Volume.
May  9 23:31:27 cmp02 systemd[1]: Starting OpenStack Cinder Volume...
May  9 23:31:27 cmp02 systemd[1]: Started OpenStack Cinder Volume.
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:31:27 cmp02 salt-minion[2824]: 'python2.7-mysqldb' changed from 'absent' to '1'
May  9 23:31:27 cmp02 salt-minion[2824]: 'mysql-common' changed from 'absent' to '5.7.22-0ubuntu0.16.04.1'
May  9 23:31:27 cmp02 salt-minion[2824]: 'mysql-common-5.6' changed from 'absent' to '1'
May  9 23:31:27 cmp02 salt-minion[2824]: 'libmysqlclient20' changed from 'absent' to '5.7.22-0ubuntu0.16.04.1'
May  9 23:31:27 cmp02 salt-minion[2824]: 'python-mysqldb' changed from 'absent' to '1.3.7-1build2'
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-mysqldb] at time 23:31:27.527324 duration_in_ms=2657.783
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Running state [p7zip] at time 23:31:27.538924
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for p7zip
May  9 23:31:27 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:31:28 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'p7zip'] in directory '/root'
May  9 23:31:28 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233127710052
May  9 23:31:28 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install p7zip.
May  9 23:31:28 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 13989
May  9 23:31:28 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233127710052
May  9 23:31:29 cmp02 systemd[1]: cinder-volume.service: Main process exited, code=exited, status=1/FAILURE
May  9 23:31:29 cmp02 systemd[1]: cinder-volume.service: Unit entered failed state.
May  9 23:31:29 cmp02 systemd[1]: cinder-volume.service: Failed with result 'exit-code'.
May  9 23:31:29 cmp02 systemd[1]: cinder-volume.service: Service hold-off time over, scheduling restart.
May  9 23:31:29 cmp02 systemd[1]: Stopped OpenStack Cinder Volume.
May  9 23:31:29 cmp02 systemd[1]: Starting OpenStack Cinder Volume...
May  9 23:31:29 cmp02 systemd[1]: Started OpenStack Cinder Volume.
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:31:30 cmp02 salt-minion[2824]: 'p7zip' changed from 'absent' to '9.20.1~dfsg.1-4.2'
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Completed state [p7zip] at time 23:31:30.333241 duration_in_ms=2794.316
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Running state [gettext-base] at time 23:31:30.346231
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for gettext-base
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Completed state [gettext-base] at time 23:31:30.784633 duration_in_ms=438.401
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Running state [python-memcache] at time 23:31:30.785305
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-memcache
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:31:30 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'python-memcache'] in directory '/root'
May  9 23:31:30 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install python-memcache.
May  9 23:31:31 cmp02 systemd[1]: cinder-volume.service: Main process exited, code=exited, status=1/FAILURE
May  9 23:31:31 cmp02 systemd[1]: cinder-volume.service: Unit entered failed state.
May  9 23:31:31 cmp02 systemd[1]: cinder-volume.service: Failed with result 'exit-code'.
May  9 23:31:32 cmp02 systemd[1]: cinder-volume.service: Service hold-off time over, scheduling restart.
May  9 23:31:32 cmp02 systemd[1]: Stopped OpenStack Cinder Volume.
May  9 23:31:32 cmp02 systemd[1]: Starting OpenStack Cinder Volume...
May  9 23:31:32 cmp02 systemd[1]: Started OpenStack Cinder Volume.
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:31:33 cmp02 systemd[1]: Starting Cleanup of Temporary Directories...
May  9 23:31:33 cmp02 systemd-tmpfiles[14438]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
May  9 23:31:33 cmp02 systemd[1]: Started Cleanup of Temporary Directories.
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:31:33 cmp02 salt-minion[2824]: 'python-memcache' changed from 'absent' to '1.57-2~u16.04+mcp1'
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-memcache] at time 23:31:33.322227 duration_in_ms=2536.922
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Running state [python-pycadf] at time 23:31:33.334443
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-pycadf
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-pycadf] at time 23:31:33.855511 duration_in_ms=521.067
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Running state [/var/lock/cinder] at time 23:31:33.857826
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Executing state file.directory for /var/lock/cinder
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Directory /var/lock/cinder is in the correct state
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Completed state [/var/lock/cinder] at time 23:31:33.860135 duration_in_ms=2.309
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/cinder/cinder.conf] at time 23:31:33.861055
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/cinder/cinder.conf
May  9 23:31:33 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/files/pike/cinder.conf.volume.Debian'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/files/backend/_lvm.conf'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:31:34 cmp02 salt-minion[2824]: ---
May  9 23:31:34 cmp02 salt-minion[2824]: +++
May  9 23:31:34 cmp02 salt-minion[2824]: @@ -1,15 +1,122 @@
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]:  [DEFAULT]
May  9 23:31:34 cmp02 salt-minion[2824]:  rootwrap_config = /etc/cinder/rootwrap.conf
May  9 23:31:34 cmp02 salt-minion[2824]:  api_paste_confg = /etc/cinder/api-paste.ini
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]:  iscsi_helper = tgtadm
May  9 23:31:34 cmp02 salt-minion[2824]:  volume_name_template = volume-%s
May  9 23:31:34 cmp02 salt-minion[2824]: -volume_group = cinder-volumes
May  9 23:31:34 cmp02 salt-minion[2824]: +#volume_group = cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]:  verbose = True
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +osapi_volume_workers = 4
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]:  auth_strategy = keystone
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]:  state_path = /var/lib/cinder
May  9 23:31:34 cmp02 salt-minion[2824]: -lock_path = /var/lock/cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +use_syslog=False
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +glance_num_retries=0
May  9 23:31:34 cmp02 salt-minion[2824]: +debug=False
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +os_region_name=RegionOne
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +#glance_api_ssl_compression=False
May  9 23:31:34 cmp02 salt-minion[2824]: +#glance_api_insecure=False
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +osapi_volume_listen=172.16.10.36
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +glance_api_servers = http://172.16.10.36:9292
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +glance_host=172.16.10.36
May  9 23:31:34 cmp02 salt-minion[2824]: +glance_port=9292
May  9 23:31:34 cmp02 salt-minion[2824]: +glance_api_version=2
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +os_privileged_user_name=cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +os_privileged_user_password=opnfv_secret
May  9 23:31:34 cmp02 salt-minion[2824]: +os_privileged_user_tenant=service
May  9 23:31:34 cmp02 salt-minion[2824]: +os_privileged_user_auth_url=http://172.16.10.36:5000/v3/
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +volume_backend_name=DEFAULT
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +default_volume_type=lvm-driver
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +enabled_backends=lvm-driver
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +# Enables the Force option on upload_to_image. This enables running
May  9 23:31:34 cmp02 salt-minion[2824]: +# upload_volume on in-use volumes for backends that support it. (boolean value)
May  9 23:31:34 cmp02 salt-minion[2824]: +#enable_force_upload = false
May  9 23:31:34 cmp02 salt-minion[2824]: +enable_force_upload = false
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +#RPC response timeout recommended by Hitachi
May  9 23:31:34 cmp02 salt-minion[2824]: +rpc_response_timeout=3600
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +#Rabbit
May  9 23:31:34 cmp02 salt-minion[2824]: +control_exchange=cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +volume_clear=none
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +volume_name_template = volume-%s
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +#volume_group = vg_cinder_volume
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]:  volumes_dir = /var/lib/cinder/volumes
May  9 23:31:34 cmp02 salt-minion[2824]: -enabled_backends = lvm
May  9 23:31:34 cmp02 salt-minion[2824]: +log_dir=/var/log/cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +# Use syslog for logging. (boolean value)
May  9 23:31:34 cmp02 salt-minion[2824]: +#use_syslog=false
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +use_syslog=false
May  9 23:31:34 cmp02 salt-minion[2824]: +verbose=True
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +nova_catalog_admin_info = compute:nova:adminURL
May  9 23:31:34 cmp02 salt-minion[2824]: +nova_catalog_info = compute:nova:internalURL
May  9 23:31:34 cmp02 salt-minion[2824]: +transport_url = rabbit://openstack:opnfv_secret@172.16.10.36:5672//openstack
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +[oslo_messaging_notifications]
May  9 23:31:34 cmp02 salt-minion[2824]: +driver = messagingv2
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +[oslo_concurrency]
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +lock_path=/var/lock/cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +[oslo_middleware]
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +enable_proxy_headers_parsing = True
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +[keystone_authtoken]
May  9 23:31:34 cmp02 salt-minion[2824]: +signing_dir=/tmp/keystone-signing-cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +revocation_cache_time = 10
May  9 23:31:34 cmp02 salt-minion[2824]: +auth_type = password
May  9 23:31:34 cmp02 salt-minion[2824]: +user_domain_name = Default
May  9 23:31:34 cmp02 salt-minion[2824]: +project_domain_name = Default
May  9 23:31:34 cmp02 salt-minion[2824]: +project_name = service
May  9 23:31:34 cmp02 salt-minion[2824]: +username = cinder
May  9 23:31:34 cmp02 salt-minion[2824]: +password = opnfv_secret
May  9 23:31:34 cmp02 salt-minion[2824]: +auth_uri=http://172.16.10.36:5000
May  9 23:31:34 cmp02 salt-minion[2824]: +auth_url=http://172.16.10.36:35357
May  9 23:31:34 cmp02 salt-minion[2824]: +
May  9 23:31:34 cmp02 salt-minion[2824]: +# Temporary disabled for backward compataiblity
May  9 23:31:34 cmp02 salt-minion[2824]: +#auth_uri=http://172.16.10.36/identity
May  9 23:31:34 cmp02 salt-minion[2824]: +#auth_url=http://172.16.10.36/identity_v2_admin
May  9 23:31:34 cmp02 salt-minion[2824]: +memcached_servers=172.16.10.36:11211,172.16.10.37:11211,172.16.10.38:11211
May  9 23:31:34 cmp02 salt-minion[2824]: +auth_version = v3
May  9 23:31:34 cmp02 salt-minion[2824]:  
May  9 23:31:34 cmp02 salt-minion[2824]:  [database]
May  9 23:31:34 cmp02 salt-minion[2824]: -connection = sqlite:////var/lib/cinder/cinder.sqlite
May  9 23:31:34 cmp02 salt-minion[2824]: +idle_timeout=3600
May  9 23:31:34 cmp02 salt-minion[2824]: +max_pool_size=30
May  9 23:31:34 cmp02 salt-minion[2824]: +max_retries=-1
May  9 23:31:34 cmp02 salt-minion[2824]: +max_overflow=40
May  9 23:31:34 cmp02 salt-minion[2824]: +connection = mysql+pymysql://cinder:opnfv_secret@172.16.10.36/cinder?charset=utf8
May  9 23:31:34 cmp02 salt-minion[2824]: +[lvm-driver]
May  9 23:31:34 cmp02 salt-minion[2824]: +host=cmp02
May  9 23:31:34 cmp02 salt-minion[2824]: +volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
May  9 23:31:34 cmp02 salt-minion[2824]: +volume_backend_name=lvm-driver
May  9 23:31:34 cmp02 salt-minion[2824]: +lvm_type = default
May  9 23:31:34 cmp02 salt-minion[2824]: +iscsi_helper = tgtadm
May  9 23:31:34 cmp02 salt-minion[2824]: +volume_group = cinder-volume
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/cinder/cinder.conf] at time 23:31:34.036951 duration_in_ms=175.894
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/cinder/api-paste.ini] at time 23:31:34.037380
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/cinder/api-paste.ini
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/files/pike/api-paste.ini.volume.Debian'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:31:34 cmp02 salt-minion[2824]: ---
May  9 23:31:34 cmp02 salt-minion[2824]: +++
May  9 23:31:34 cmp02 salt-minion[2824]: @@ -12,8 +12,8 @@
May  9 23:31:34 cmp02 salt-minion[2824]:  [composite:openstack_volume_api_v1]
May  9 23:31:34 cmp02 salt-minion[2824]:  use = call:cinder.api.middleware.auth:pipeline_factory
May  9 23:31:34 cmp02 salt-minion[2824]:  noauth = cors http_proxy_to_wsgi request_id faultwrap sizelimit osprofiler noauth apiv1
May  9 23:31:34 cmp02 salt-minion[2824]: -keystone = cors http_proxy_to_wsgi request_id faultwrap sizelimit osprofiler authtoken keystonecontext apiv1
May  9 23:31:34 cmp02 salt-minion[2824]: -keystone_nolimit = cors http_proxy_to_wsgi request_id faultwrap sizelimit osprofiler authtoken keystonecontext apiv1
May  9 23:31:34 cmp02 salt-minion[2824]: +keystone = cors http_proxy_to_wsgi request_id faultwrap sizelimit osprofiler authtoken keystonecontext  apiv1
May  9 23:31:34 cmp02 salt-minion[2824]: +keystone_nolimit = cors http_proxy_to_wsgi request_id faultwrap sizelimit osprofiler authtoken keystonecontext  apiv1
May  9 23:31:34 cmp02 salt-minion[2824]:  
May  9 23:31:34 cmp02 salt-minion[2824]:  [composite:openstack_volume_api_v2]
May  9 23:31:34 cmp02 salt-minion[2824]:  use = call:cinder.api.middleware.auth:pipeline_factory
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/cinder/api-paste.ini] at time 23:31:34.122693 duration_in_ms=85.313
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/default/cinder-volume] at time 23:31:34.123083
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/default/cinder-volume
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'cinder/files/default'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:31:34 cmp02 salt-minion[2824]: New file
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/default/cinder-volume] at time 23:31:34.152448 duration_in_ms=29.365
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Running state [cinder-volume] at time 23:31:34.154623
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing state service.running for cinder-volume
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'status', 'cinder-volume.service', '-n', '0'] in directory '/root'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'cinder-volume.service'] in directory '/root'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'cinder-volume.service'] in directory '/root'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] The service cinder-volume is already running
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Completed state [cinder-volume] at time 23:31:34.217666 duration_in_ms=63.044
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Running state [cinder-volume] at time 23:31:34.218010
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing state service.mod_watch for cinder-volume
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'cinder-volume.service'] in directory '/root'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'cinder-volume.service'] in directory '/root'
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'cinder-volume.service'] in directory '/root'
May  9 23:31:34 cmp02 systemd[1]: Started /bin/systemctl restart cinder-volume.service.
May  9 23:31:34 cmp02 systemd[1]: Stopping OpenStack Cinder Volume...
May  9 23:31:34 cmp02 systemd[1]: cinder-volume.service: Main process exited, code=exited, status=1/FAILURE
May  9 23:31:34 cmp02 systemd[1]: Stopped OpenStack Cinder Volume.
May  9 23:31:34 cmp02 systemd[1]: cinder-volume.service: Unit entered failed state.
May  9 23:31:34 cmp02 systemd[1]: cinder-volume.service: Failed with result 'exit-code'.
May  9 23:31:34 cmp02 systemd[1]: Starting OpenStack Cinder Volume...
May  9 23:31:34 cmp02 systemd[1]: Started OpenStack Cinder Volume.
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] {'cinder-volume': True}
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Completed state [cinder-volume] at time 23:31:34.474952 duration_in_ms=256.941
May  9 23:31:34 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509232946930880
May  9 23:32:37 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509233237859766
May  9 23:32:37 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 14605
May  9 23:32:40 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:32:40 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'neutron/init.sls'
May  9 23:32:40 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'neutron/compute.sls'
May  9 23:32:40 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'neutron/map.jinja'
May  9 23:32:41 cmp02 salt-minion[2824]: [INFO    ] Running state [ovn-common] at time 23:32:41.786717
May  9 23:32:41 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for ovn-common
May  9 23:32:41 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:32:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'ovn-common'] in directory '/root'
May  9 23:32:42 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:32:45 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:32:45 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'ovn-common'] in directory '/root'
May  9 23:32:45 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install ovn-common.
May  9 23:32:47 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:32:47 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:32:47 cmp02 salt-minion[2824]: 'ovn-common' changed from 'absent' to '2.8.0-1~u16.04+mcp2'
May  9 23:32:47 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:32:47 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovn-common] at time 23:32:47.823412 duration_in_ms=6036.695
May  9 23:32:47 cmp02 salt-minion[2824]: [INFO    ] Running state [ovn-host] at time 23:32:47.837453
May  9 23:32:47 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for ovn-host
May  9 23:32:48 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:32:48 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'ovn-host'] in directory '/root'
May  9 23:32:48 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install ovn-host.
May  9 23:32:48 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233247987850
May  9 23:32:48 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 15501
May  9 23:32:48 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233247987850
May  9 23:32:49 cmp02 systemd[1]: Reloading.
May  9 23:32:49 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:32:50 cmp02 systemd[1]: Reloading.
May  9 23:32:50 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:32:50 cmp02 systemd[1]: Reloading.
May  9 23:32:50 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:32:50 cmp02 systemd[1]: Starting LSB: OVN host components...
May  9 23:32:50 cmp02 ovn-host[15862]:  * Starting ovn-controller
May  9 23:32:50 cmp02 systemd[1]: Started LSB: OVN host components.
May  9 23:32:50 cmp02 systemd[1]: Reloading.
May  9 23:32:50 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:32:51 cmp02 salt-minion[2824]: 'ovn-host' changed from 'absent' to '2.8.0-1~u16.04+mcp2'
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovn-host] at time 23:32:51.977249 duration_in_ms=4139.795
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Running state [ovs-vsctl set open . external-ids:ovn-remote=tcp:172.16.10.36:6642] at time 23:32:51.981770
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Executing state cmd.run for ovs-vsctl set open . external-ids:ovn-remote=tcp:172.16.10.36:6642
May  9 23:32:51 cmp02 salt-minion[2824]: [INFO    ] Executing command 'ovs-vsctl set open . external-ids:ovn-remote=tcp:172.16.10.36:6642' in directory '/root'
May  9 23:32:51 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl set open . external-ids:ovn-remote=tcp:172.16.10.36:6642
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] {'pid': 15946, 'retcode': 0, 'stderr': '', 'stdout': ''}
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovs-vsctl set open . external-ids:ovn-remote=tcp:172.16.10.36:6642] at time 23:32:52.007546 duration_in_ms=25.775
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Running state [ovs-vsctl set open . external-ids:ovn-encap-type=geneve,vxlan] at time 23:32:52.008904
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing state cmd.run for ovs-vsctl set open . external-ids:ovn-encap-type=geneve,vxlan
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command 'ovs-vsctl set open . external-ids:ovn-encap-type=geneve,vxlan' in directory '/root'
May  9 23:32:52 cmp02 kernel: [  979.831254] device br-int entered promiscuous mode
May  9 23:32:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl set open . external-ids:ovn-encap-type=geneve,vxlan
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] {'pid': 15957, 'retcode': 0, 'stderr': '', 'stdout': ''}
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovs-vsctl set open . external-ids:ovn-encap-type=geneve,vxlan] at time 23:32:52.037736 duration_in_ms=28.832
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Running state [ovs-vsctl set open . external-ids:ovn-encap-ip=10.1.0.6] at time 23:32:52.038316
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing state cmd.run for ovs-vsctl set open . external-ids:ovn-encap-ip=10.1.0.6
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command 'ovs-vsctl set open . external-ids:ovn-encap-ip=10.1.0.6' in directory '/root'
May  9 23:32:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl set open . external-ids:ovn-encap-ip=10.1.0.6
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] {'pid': 15986, 'retcode': 0, 'stderr': '', 'stdout': ''}
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovs-vsctl set open . external-ids:ovn-encap-ip=10.1.0.6] at time 23:32:52.066575 duration_in_ms=28.258
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Running state [ovs-vsctl --no-wait br-set-external-id br-floating bridge-id br-floating] at time 23:32:52.067438
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing state cmd.run for ovs-vsctl --no-wait br-set-external-id br-floating bridge-id br-floating
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command 'ovs-vsctl --no-wait br-set-external-id br-floating bridge-id br-floating' in directory '/root'
May  9 23:32:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait br-set-external-id br-floating bridge-id br-floating
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] {'pid': 16015, 'retcode': 0, 'stderr': '', 'stdout': ''}
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovs-vsctl --no-wait br-set-external-id br-floating bridge-id br-floating] at time 23:32:52.091036 duration_in_ms=23.598
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Running state [ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-floating] at time 23:32:52.091653
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing state cmd.run for ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-floating
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command 'ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-floating' in directory '/root'
May  9 23:32:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-floating
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] {'pid': 16042, 'retcode': 0, 'stderr': '', 'stdout': ''}
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-floating] at time 23:32:52.113837 duration_in_ms=22.185
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Running state [ovn-host] at time 23:32:52.599028
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing state service.running for ovn-host
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'status', 'ovn-host.service', '-n', '0'] in directory '/root'
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'ovn-host.service'] in directory '/root'
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ovn-host.service'] in directory '/root'
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] The service ovn-host is already running
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Completed state [ovn-host] at time 23:32:52.663640 duration_in_ms=64.612
May  9 23:32:52 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233237859766
May  9 23:32:54 cmp02 systemd-udevd[16105]: Could not generate persistent MAC address for genev_sys_6081: No such file or directory
May  9 23:32:54 cmp02 kernel: [  982.738094] device genev_sys_6081 entered promiscuous mode
May  9 23:32:56 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509233256310298
May  9 23:32:56 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 16207
May  9 23:32:56 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:32:56 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/init.sls'
May  9 23:32:56 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/compute.sls'
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Running state [nova] at time 23:32:58.671674
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing state group.present for nova
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing command ['groupadd', '-g 303', '-r', 'nova'] in directory '/root'
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] {'passwd': 'x', 'gid': 303, 'name': 'nova', 'members': []}
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova] at time 23:32:58.705886 duration_in_ms=34.212
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Running state [libvirtd] at time 23:32:58.706936
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing state group.present for libvirtd
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing command ['groupadd', '-r', 'libvirtd'] in directory '/root'
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] {'passwd': 'x', 'gid': 999, 'name': 'libvirtd', 'members': []}
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Completed state [libvirtd] at time 23:32:58.759457 duration_in_ms=52.519
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Running state [nova] at time 23:32:58.762865
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing state user.present for nova
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing command ['useradd', '-s', '/bin/bash', '-u', '303', '-g', '303', '-m', '-d', '/var/lib/nova', '-r', 'nova'] in directory '/root'
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] {'shell': '/bin/bash', 'workphone': '', 'uid': 303, 'passwd': 'x', 'roomnumber': '', 'groups': ['nova'], 'home': '/var/lib/nova', 'name': 'nova', 'gid': 303, 'fullname': '', 'homephone': ''}
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova] at time 23:32:58.792871 duration_in_ms=30.006
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Running state [nova-common] at time 23:32:58.793574
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for nova-common
May  9 23:32:58 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:32:59 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'nova-common'] in directory '/root'
May  9 23:32:59 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:33:02 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:33:02 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'nova-common'] in directory '/root'
May  9 23:33:02 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install nova-common.
May  9 23:33:06 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233306352096
May  9 23:33:06 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 16685
May  9 23:33:06 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233306352096
May  9 23:33:16 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233316391822
May  9 23:33:16 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 16690
May  9 23:33:16 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233316391822
May  9 23:33:26 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233326445788
May  9 23:33:26 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 17183
May  9 23:33:26 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233326445788
May  9 23:33:36 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233336492016
May  9 23:33:36 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 18284
May  9 23:33:36 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233336492016
May  9 23:33:43 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:33:43 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-pypowervm' changed from 'absent' to '1.1.6-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxrender1' changed from 'absent' to '1:0.9.9-0ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libavahi-common3' changed from 'absent' to '0.6.32~rc+dfsg-1ubuntu2.2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'nova-common' changed from 'absent' to '2:16.1.1-1~u16.04+mcp78'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libthai-data' changed from 'absent' to '0.1.24-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-gobject-2' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'fonts-dejavu-core' changed from 'absent' to '2.35-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-pymongo' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-cairo' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-microversion-parse' changed from 'absent' to '0.1.3-2.1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-bson' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgtk2.0-bin' changed from 'absent' to '2.24.30-1ubuntu1.16.04.2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'websockify-common' changed from 'absent' to '0.8.0+dfsg1-7~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxdamage1' changed from 'absent' to '1:1.1.4-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxinerama1' changed from 'absent' to '2:1.1.3-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libcairo2' changed from 'absent' to '1.14.6-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-nova' changed from 'absent' to '2:16.1.1-1~u16.04+mcp78'
May  9 23:33:43 cmp02 salt-minion[2824]: 'fontconfig' changed from 'absent' to '2.11.94-0ubuntu1.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libpixman-1-0' changed from 'absent' to '0.33.6-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxi6' changed from 'absent' to '2:1.7.6-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-mimeparse' changed from 'absent' to '0.1.4-1build1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libsubunit-diff-perl' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-gobject-2' changed from 'absent' to '2.28.6-12ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-pymongo-ext' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'websockify' changed from 'absent' to '0.8.0+dfsg1-7~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-junitxml' changed from 'absent' to '0.6-1.1ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxfixes3' changed from 'absent' to '1:5.0.1-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-gridfs' changed from 'absent' to '3.2-1build1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-extras' changed from 'absent' to '0.0.3-3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libpangocairo-1.0-0' changed from 'absent' to '1.38.1-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-bson-ext' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-cairo' changed from 'absent' to '1.8.8-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgtk2.0-0' changed from 'absent' to '2.24.30-1ubuntu1.16.04.2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libpango-1.0-0' changed from 'absent' to '1.38.1-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-dogpile.cache' changed from 'absent' to '0.6.2-1.1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-subunit' changed from 'absent' to '1.1.0-3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-linecache2' changed from 'absent' to '1.0.0-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgraphite2-3' changed from 'absent' to '1.3.10-0ubuntu0.16.04.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-appdirs' changed from 'absent' to '1.4.0-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libsubunit-perl' changed from 'absent' to '1.1.0-3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxcursor1' changed from 'absent' to '1:1.1.14-1ubuntu0.16.04.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libpangoft2-1.0-0' changed from 'absent' to '1.38.1-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libcups2' changed from 'absent' to '2.1.3-4ubuntu0.4'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libatk1.0-data' changed from 'absent' to '2.18.0-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libfontconfig1' changed from 'absent' to '2.11.94-0ubuntu1.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'hicolor-icon-theme' changed from 'absent' to '0.15-0ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libatk1.0-0' changed from 'absent' to '2.18.0-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgraphite2-2.0.0' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-os-vif' changed from 'absent' to '1.7.0-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libavahi-client3' changed from 'absent' to '0.6.32~rc+dfsg-1ubuntu2.2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-osc-lib' changed from 'absent' to '1.7.0-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-unittest2' changed from 'absent' to '1.1.0-6.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-pbr' changed from 'absent' to '2.0.0-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxcb-shm0' changed from 'absent' to '1.11.1-1ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-os-xenapi' changed from 'absent' to '0.2.0-1~u16.04+mcp3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-gridfs' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-bson-ext' changed from 'absent' to '3.2-1build1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-os-client-config' changed from 'absent' to '1.28.0-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-testtools' changed from 'absent' to '1.8.1-0ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-subunit' changed from 'absent' to '1.1.0-3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxrandr2' changed from 'absent' to '2:1.5.0-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgdk-pixbuf2.0-0' changed from 'absent' to '2.32.2-1ubuntu1.4'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libthai0' changed from 'absent' to '0.1.24-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-gobject' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'sqlite3' changed from 'absent' to '3.11.0-1ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgtk2.0-common' changed from 'absent' to '2.24.30-1ubuntu1.16.04.2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'subunit' changed from 'absent' to '1.1.0-3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-websockify' changed from 'absent' to '0.8.0+dfsg1-7~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-cinderclient' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxcb-render0' changed from 'absent' to '1.11.1-1ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-os-traits' changed from 'absent' to '0.3.3-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libxcomposite1' changed from 'absent' to '1:0.4.4-1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-neutronclient' changed from 'absent' to '1:6.5.0-1~u16.04+mcp15'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-pymongo-ext' changed from 'absent' to '3.2-1build1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libfontconfig' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-cursive' changed from 'absent' to '0.2.0-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libharfbuzz0b' changed from 'absent' to '1.0.1-1ubuntu0.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-oslo.cache' changed from 'absent' to '1.25.1-1~u16.04+mcp3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python2.7-nova' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-pymongo' changed from 'absent' to '3.2-1build1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-gtk2' changed from 'absent' to '2.24.0-4ubuntu1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libdatrie1' changed from 'absent' to '0.2.10-2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-bson' changed from 'absent' to '3.2-1build1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python3-traceback2' changed from 'absent' to '1.4.0-3'
May  9 23:33:43 cmp02 salt-minion[2824]: 'fontconfig-config' changed from 'absent' to '2.11.94-0ubuntu1.1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libgdk-pixbuf2.0-common' changed from 'absent' to '2.32.2-1ubuntu1.4'
May  9 23:33:43 cmp02 salt-minion[2824]: 'libavahi-common-data' changed from 'absent' to '0.6.32~rc+dfsg-1ubuntu2.2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-requestsexceptions' changed from 'absent' to '1.3.0-3~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: 'gtk2.0-binver-2.10.0' changed from 'absent' to '1'
May  9 23:33:43 cmp02 salt-minion[2824]: 'python-cinderclient' changed from 'absent' to '1:3.1.0-1~u16.04+mcp2'
May  9 23:33:43 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:33:43 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova-common] at time 23:33:43.743164 duration_in_ms=44949.589
May  9 23:33:43 cmp02 salt-minion[2824]: [INFO    ] Running state [nova-compute-kvm] at time 23:33:43.756101
May  9 23:33:43 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for nova-compute-kvm
May  9 23:33:44 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:33:44 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'nova-compute-kvm'] in directory '/root'
May  9 23:33:44 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install nova-compute-kvm.
May  9 23:33:46 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233346575006
May  9 23:33:46 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 18496
May  9 23:33:46 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233346575006
May  9 23:33:56 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233356614473
May  9 23:33:56 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 18501
May  9 23:33:56 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233356614473
May  9 23:34:06 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233406660630
May  9 23:34:06 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 18577
May  9 23:34:06 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233406660630
May  9 23:34:16 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233416743049
May  9 23:34:16 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 19152
May  9 23:34:16 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233416743049
May  9 23:34:26 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233426778543
May  9 23:34:26 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 23356
May  9 23:34:26 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233426778543
May  9 23:34:29 cmp02 systemd[1]: Reloading.
May  9 23:34:29 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:31 cmp02 kernel: [ 1079.305475] audit: type=1400 audit(1525908871.485:16): apparmor="STATUS" operation="profile_load" profile="unconfined" name="virt-aa-helper" pid=27162 comm="apparmor_parser"
May  9 23:34:31 cmp02 kernel: [ 1079.464940] audit: type=1400 audit(1525908871.644:17): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/libvirtd" pid=27171 comm="apparmor_parser"
May  9 23:34:31 cmp02 kernel: [ 1079.465364] audit: type=1400 audit(1525908871.645:18): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/libvirtd//qemu_bridge_helper" pid=27171 comm="apparmor_parser"
May  9 23:34:31 cmp02 systemd[1]: Reloading.
May  9 23:34:31 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:32 cmp02 systemd[1]: Reloading.
May  9 23:34:32 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:33 cmp02 systemd[1]: Reloading.
May  9 23:34:33 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:33 cmp02 systemd[1]: Reloading.
May  9 23:34:33 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:33 cmp02 systemd[1]: Listening on Virtual machine log manager socket.
May  9 23:34:33 cmp02 systemd[1]: Started Virtual machine log manager.
May  9 23:34:33 cmp02 systemd[1]: Reloading.
May  9 23:34:33 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:33 cmp02 systemd[1]: Reloading.
May  9 23:34:33 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:33 cmp02 systemd[1]: Listening on Virtual machine lock manager socket.
May  9 23:34:33 cmp02 systemd[1]: Starting Virtualization daemon...
May  9 23:34:33 cmp02 systemd[1]: Started Virtualization daemon.
May  9 23:34:34 cmp02 kernel: [ 1081.867992] ip_tables: (C) 2000-2006 Netfilter Core Team
May  9 23:34:34 cmp02 systemd[1]: Reloading.
May  9 23:34:34 cmp02 kernel: [ 1081.896475] ip6_tables: (C) 2000-2006 Netfilter Core Team
May  9 23:34:34 cmp02 kernel: [ 1081.917396] Ebtables v2.0 registered
May  9 23:34:34 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:34 cmp02 systemd[1]: Reloading.
May  9 23:34:34 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:34 cmp02 systemd[1]: Reached target Libvirt guests shutdown.
May  9 23:34:34 cmp02 systemd[1]: Starting Suspend/Resume Running libvirt Guests...
May  9 23:34:34 cmp02 systemd[1]: Started Suspend/Resume Running libvirt Guests.
May  9 23:34:34 cmp02 systemd[1]: Reloading.
May  9 23:34:34 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:34 cmp02 systemd[1]: Listening on Virtual machine lock manager socket.
May  9 23:34:34 cmp02 systemd[1]: Reloading.
May  9 23:34:34 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:34 cmp02 systemd[1]: Listening on Virtual machine lock manager socket.
May  9 23:34:34 cmp02 systemd-udevd[27664]: Could not generate persistent MAC address for virbr0: No such file or directory
May  9 23:34:34 cmp02 kernel: [ 1082.732742] virbr0: port 1(virbr0-nic) entered blocking state
May  9 23:34:34 cmp02 kernel: [ 1082.732744] virbr0: port 1(virbr0-nic) entered disabled state
May  9 23:34:34 cmp02 kernel: [ 1082.733162] device virbr0-nic entered promiscuous mode
May  9 23:34:34 cmp02 systemd[1]: Reloading.
May  9 23:34:35 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:35 cmp02 systemd[1]: Reloading.
May  9 23:34:35 cmp02 kernel: [ 1082.956029] virbr0: port 1(virbr0-nic) entered blocking state
May  9 23:34:35 cmp02 kernel: [ 1082.956032] virbr0: port 1(virbr0-nic) entered listening state
May  9 23:34:35 cmp02 dnsmasq[27939]: started, version 2.78 cachesize 150
May  9 23:34:35 cmp02 dnsmasq[27939]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
May  9 23:34:35 cmp02 dnsmasq-dhcp[27939]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
May  9 23:34:35 cmp02 dnsmasq-dhcp[27939]: DHCP, sockets bound exclusively to interface virbr0
May  9 23:34:35 cmp02 dnsmasq[27939]: reading /etc/resolv.conf
May  9 23:34:35 cmp02 dnsmasq[27939]: using nameserver 192.168.11.1#53
May  9 23:34:35 cmp02 dnsmasq[27939]: read /etc/hosts - 12 addresses
May  9 23:34:35 cmp02 dnsmasq[27939]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
May  9 23:34:35 cmp02 dnsmasq-dhcp[27939]: read /var/lib/libvirt/dnsmasq/default.hostsfile
May  9 23:34:35 cmp02 kernel: [ 1083.001677] virbr0: port 1(virbr0-nic) entered disabled state
May  9 23:34:35 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:35 cmp02 systemd[1]: Starting QEMU KVM preparation - module, ksm, hugepages...
May  9 23:34:35 cmp02 systemd[1]: Started QEMU KVM preparation - module, ksm, hugepages.
May  9 23:34:35 cmp02 systemd[1]: Reloading.
May  9 23:34:35 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:35 cmp02 systemd[1]: Reloading.
May  9 23:34:35 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:35 cmp02 systemd[1]: Starting LSB: ebtables ruleset management...
May  9 23:34:36 cmp02 systemd[1]: Started LSB: ebtables ruleset management.
May  9 23:34:36 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233436820497
May  9 23:34:36 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 28140
May  9 23:34:36 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233436820497
May  9 23:34:37 cmp02 systemd[1]: Reloading.
May  9 23:34:37 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:37 cmp02 systemd[1]: Reloading.
May  9 23:34:37 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:37 cmp02 systemd[1]: Reloading.
May  9 23:34:37 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:37 cmp02 systemd[1]: Starting OpenStack Compute...
May  9 23:34:37 cmp02 systemd[1]: Started OpenStack Compute.
May  9 23:34:37 cmp02 systemd[1]: Reloading.
May  9 23:34:37 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:34:42 cmp02 systemd[1]: nova-compute.service: Main process exited, code=exited, status=1/FAILURE
May  9 23:34:42 cmp02 systemd[1]: nova-compute.service: Unit entered failed state.
May  9 23:34:42 cmp02 systemd[1]: nova-compute.service: Failed with result 'exit-code'.
May  9 23:34:42 cmp02 systemd[1]: nova-compute.service: Service hold-off time over, scheduling restart.
May  9 23:34:42 cmp02 systemd[1]: Stopped OpenStack Compute.
May  9 23:34:42 cmp02 systemd[1]: Starting OpenStack Compute...
May  9 23:34:42 cmp02 systemd[1]: Started OpenStack Compute.
May  9 23:34:46 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233446964520
May  9 23:34:46 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 2376
May  9 23:34:46 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233446964520
May  9 23:34:57 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233457179412
May  9 23:34:57 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 3300
May  9 23:34:57 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233457179412
May  9 23:34:57 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:34:57 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:34:57 cmp02 salt-minion[2824]: 'libnet-ssleay-perl' changed from 'absent' to '1.72-1build1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'c++-compiler' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libguestfs-hfsplus' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-keymaps' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libmailtools-perl' changed from 'absent' to '2.13-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libyajl2' changed from 'absent' to '2.1.0-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'elf-binutils' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libubsan0' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libasyncns0' changed from 'absent' to '0.8-5build1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'c-compiler' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'augeas-lenses' changed from 'absent' to '1.4.0-0ubuntu1.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libmpc3' changed from 'absent' to '1.0.3-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libvirt-daemon-system' changed from 'absent' to '4.0.0-1.7~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libvirt-clients' changed from 'absent' to '4.0.0-1.7~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'ipxe-qemu' changed from 'absent' to '1.0.0+git-20150424.a25a16d-1ubuntu1.2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'liblwp-mediatypes-perl' changed from 'absent' to '6.02-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libsndfile1' changed from 'absent' to '1.0.25-10ubuntu0.16.04.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libxml2-utils' changed from 'absent' to '2.9.3+dfsg1-1ubuntu0.5'
May  9 23:34:57 cmp02 salt-minion[2824]: 'mkisofs' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'liburi-perl' changed from 'absent' to '1.71-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'lzop' changed from 'absent' to '1.03-3.2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libspice-server1' changed from 'absent' to '0.12.6-4ubuntu0.3'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libtimedate-perl' changed from 'absent' to '2.3000-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhfsp0' changed from 'absent' to '1.0.4-13'
May  9 23:34:57 cmp02 salt-minion[2824]: 'genisoimage' changed from 'absent' to '9:1.1.11-3ubuntu1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libcaca0' changed from 'absent' to '0.99.beta19-2build2~gcc5.2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libfile-listing-perl' changed from 'absent' to '6.04-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'reiserfsprogs' changed from 'absent' to '1:3.6.24-3.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libalgorithm-merge-perl' changed from 'absent' to '0.08-3'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-system-common' changed from 'absent' to '1:2.11+dfsg-1.1~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-system-i386' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'c++abi2-dev' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-system-x86-64' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'msr-tools' changed from 'absent' to '1.3-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libusbredirparser1' changed from 'absent' to '0.7.1-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'supermin' changed from 'absent' to '5.1.14-2ubuntu1.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'mtools' changed from 'absent' to '4.0.18-2ubuntu0.16.04'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libcc1-0' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libgomp1' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libio-socket-ssl-perl' changed from 'absent' to '2.024-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'syslinux-common' changed from 'absent' to '3:6.03+dfsg-11ubuntu1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libfont-afm-perl' changed from 'absent' to '1.20-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libwww-robotrules-perl' changed from 'absent' to '6.01-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'linux-libc-dev' changed from 'absent' to '4.4.0-124.148'
May  9 23:34:57 cmp02 salt-minion[2824]: 'gcc-5' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libxen-4.6' changed from 'absent' to '4.6.5-0ubuntu1.4'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libxenstore3.0' changed from 'absent' to '4.6.5-0ubuntu1.4'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libwww-perl' changed from 'absent' to '6.15-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libasan2' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libatomic1' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libcacard0' changed from 'absent' to '1:2.5.0-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libitm1' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libvorbisenc2' changed from 'absent' to '1.3.5-3ubuntu0.2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'g++' changed from 'absent' to '4:5.3.1-1ubuntu1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libwin-hivex-perl' changed from 'absent' to '1.3.13-1build3'
May  9 23:34:57 cmp02 salt-minion[2824]: 'cpp:any' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'kpartx' changed from 'absent' to '0.5.0+git1.656f8865-5ubuntu2.5'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libmpx0' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libstdc++-5-dev' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhtml-format-perl' changed from 'absent' to '2.11-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'nova-compute-kvm' changed from 'absent' to '2:16.1.1-1~u16.04+mcp78'
May  9 23:34:57 cmp02 salt-minion[2824]: 'hfsplus' changed from 'absent' to '1.0.4-13'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhtml-parser-perl' changed from 'absent' to '3.72-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhttp-message-perl' changed from 'absent' to '6.11-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libtsan0' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'g++-5' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libstdc++-dev' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libaugeas0' changed from 'absent' to '1.4.0-0ubuntu1.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libintl-perl' changed from 'absent' to '1.24-1build1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhtml-form-perl' changed from 'absent' to '6.03-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libxml-parser-perl' changed from 'absent' to '2.44-1build1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libsys-virt-perl' changed from 'absent' to '1.2.16-1ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libbrlapi0.6' changed from 'absent' to '5.3.1-2ubuntu2.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'manpages-dev' changed from 'absent' to '4.04-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'cpp-5' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'linux-kernel-headers' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libguestfs-reiserfs' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhtml-tagset-perl' changed from 'absent' to '3.20-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libflac8' changed from 'absent' to '1.3.1-4'
May  9 23:34:57 cmp02 salt-minion[2824]: 'binutils' changed from 'absent' to '2.26.1-1ubuntu1~16.04.6'
May  9 23:34:57 cmp02 salt-minion[2824]: 'build-essential' changed from 'absent' to '12.1ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libbluetooth3' changed from 'absent' to '5.37-0ubuntu5.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libencode-locale-perl' changed from 'absent' to '1.05-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libconfig9' changed from 'absent' to '1.5-0.2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-kvm-spice' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libstring-shellquote-perl' changed from 'absent' to '1.03-1.2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libguestfs-tools' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libalgorithm-diff-xs-perl' changed from 'absent' to '0.04-4build1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'syslinux' changed from 'absent' to '3:6.03+dfsg-11ubuntu1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'timedate' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libpciaccess0' changed from 'absent' to '0.13.4-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libfdt1' changed from 'absent' to '1.4.2-1.2~u16.04+mcp2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libfile-fcntllock-perl' changed from 'absent' to '0.22-3'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhttp-daemon-perl' changed from 'absent' to '6.01-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libguestfs-perl' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-kvm' changed from 'absent' to '1:2.11+dfsg-1.1~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'make:any' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libguestfs0' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'mailtools' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhttp-cookies-perl' changed from 'absent' to '6.01-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'qemu-system-x86' changed from 'absent' to '1:2.11+dfsg-1.1~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libauthen-sasl-perl' changed from 'absent' to '2.1600-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libnet-smtp-ssl-perl' changed from 'absent' to '1.03-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libvirt0' changed from 'absent' to '4.0.0-1.7~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libnl-route-3-200' changed from 'absent' to '3.2.27-1ubuntu0.16.04.1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'attr' changed from 'absent' to '1:2.4.47-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libguestfs-xfs' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libisl15' changed from 'absent' to '0.16.1-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libopus0' changed from 'absent' to '1.1.2-1ubuntu1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libvirt-daemon-driver-storage-rbd' changed from 'absent' to '4.0.0-1.7~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'liblsan0' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'ipxe-qemu-256k-compat-efi-roms' changed from 'absent' to '1.0.0+git-20150424.a25a16d-0.2~u16.04+mcp1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libgcc-5-dev' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libalgorithm-diff-perl' changed from 'absent' to '1.19.03-1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libhttp-negotiate-perl' changed from 'absent' to '6.00-2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'seabios' changed from 'absent' to '1.10.2-1.1~u16.04+mcp2'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libmail-perl' changed from 'absent' to '1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'libfakeroot' changed from 'absent' to '1.20.2-1ubuntu1'
May  9 23:34:57 cmp02 salt-minion[2824]: 'conntrack' changed from 'absent' to '1:1.4.3-3'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libasound2' changed from 'absent' to '1.1.0-0ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libxml-xpath-perl' changed from 'absent' to '1.30-1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'lsscsi' changed from 'absent' to '0.27-3'
May  9 23:34:58 cmp02 salt-minion[2824]: 'gcc' changed from 'absent' to '4:5.3.1-1ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libsdl1.2debian' changed from 'absent' to '1.2.15+dfsg1-3'
May  9 23:34:58 cmp02 salt-minion[2824]: 'make' changed from 'absent' to '4.1-6'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libvirt-daemon' changed from 'absent' to '4.0.0-1.7~u16.04+mcp1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'nova-compute-hypervisor' changed from 'absent' to '1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'dpkg-dev' changed from 'absent' to '1.18.4ubuntu1.4'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libnet-http-perl' changed from 'absent' to '6.09-1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libio-html-perl' changed from 'absent' to '1.001-1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libvorbis0a' changed from 'absent' to '1.3.5-3ubuntu0.2'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libogg0' changed from 'absent' to '1.3.2-1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'ebtables' changed from 'absent' to '2.0.10.4-3.4ubuntu2'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libasound2-data' changed from 'absent' to '1.1.0-0ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'scrub' changed from 'absent' to '2.6.1-1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libc-dev' changed from 'absent' to '1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libdpkg-perl' changed from 'absent' to '1.18.4ubuntu1.4'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libhivex0' changed from 'absent' to '1.3.13-1build3'
May  9 23:34:58 cmp02 salt-minion[2824]: 'kvm' changed from 'absent' to '1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libc6-dev' changed from 'absent' to '2.23-0ubuntu10'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libcilkrts5' changed from 'absent' to '5.4.0-6ubuntu1~16.04.9'
May  9 23:34:58 cmp02 salt-minion[2824]: 'liblwp-protocol-https-perl' changed from 'absent' to '6.06-2'
May  9 23:34:58 cmp02 salt-minion[2824]: 'python-libvirt' changed from 'absent' to '3.5.0-1.1~u16.04+mcp3'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libpulse0' changed from 'absent' to '1:8.0-0ubuntu3.10'
May  9 23:34:58 cmp02 salt-minion[2824]: 'nova-compute' changed from 'absent' to '2:16.1.1-1~u16.04+mcp78'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libnetcf1' changed from 'absent' to '1:0.2.8-1ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libhtml-tree-perl' changed from 'absent' to '5.03-2'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libhttp-date-perl' changed from 'absent' to '6.02-1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'fakeroot' changed from 'absent' to '1.20.2-1ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'libc-dev-bin' changed from 'absent' to '2.23-0ubuntu10'
May  9 23:34:58 cmp02 salt-minion[2824]: 'cpp' changed from 'absent' to '4:5.3.1-1ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'extlinux' changed from 'absent' to '3:6.03+dfsg-11ubuntu1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'binutils-gold' changed from 'absent' to '1'
May  9 23:34:58 cmp02 salt-minion[2824]: 'cpu-checker' changed from 'absent' to '0.7-0ubuntu7'
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova-compute-kvm] at time 23:34:58.208118 duration_in_ms=74452.016
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Running state [python-novaclient] at time 23:34:58.221066
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-novaclient
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-novaclient] at time 23:34:58.725112 duration_in_ms=504.046
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Running state [pm-utils] at time 23:34:58.725537
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for pm-utils
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:34:58 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'pm-utils'] in directory '/root'
May  9 23:34:58 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install pm-utils.
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:35:02 cmp02 salt-minion[2824]: 'pm-utils' changed from 'absent' to '1.4.1-16'
May  9 23:35:02 cmp02 salt-minion[2824]: 'libx86-1' changed from 'absent' to '1.1+ds1-10'
May  9 23:35:02 cmp02 salt-minion[2824]: 'vbetool' changed from 'absent' to '1.1-3'
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Completed state [pm-utils] at time 23:35:02.205697 duration_in_ms=3480.159
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Running state [sysfsutils] at time 23:35:02.219292
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for sysfsutils
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Completed state [sysfsutils] at time 23:35:02.705070 duration_in_ms=485.778
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Running state [sg3-utils] at time 23:35:02.705530
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for sg3-utils
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Completed state [sg3-utils] at time 23:35:02.718852 duration_in_ms=13.322
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Running state [libvirt-bin] at time 23:35:02.719415
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for libvirt-bin
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:35:02 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'libvirt-bin'] in directory '/root'
May  9 23:35:02 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install libvirt-bin.
May  9 23:35:05 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:35:05 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:35:05 cmp02 salt-minion[2824]: 'libvirt-bin' changed from 'absent' to '4.0.0-1.7~u16.04+mcp1'
May  9 23:35:05 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:35:05 cmp02 salt-minion[2824]: [INFO    ] Completed state [libvirt-bin] at time 23:35:05.914282 duration_in_ms=3194.867
May  9 23:35:05 cmp02 salt-minion[2824]: [INFO    ] Running state [python-memcache] at time 23:35:05.928675
May  9 23:35:05 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-memcache
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-memcache] at time 23:35:06.495203 duration_in_ms=566.528
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Running state [qemu-kvm] at time 23:35:06.495638
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for qemu-kvm
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Completed state [qemu-kvm] at time 23:35:06.505817 duration_in_ms=10.179
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Running state [python-guestfs] at time 23:35:06.506167
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for python-guestfs
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:35:06 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'python-guestfs'] in directory '/root'
May  9 23:35:06 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install python-guestfs.
May  9 23:35:07 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233507206385
May  9 23:35:07 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 4146
May  9 23:35:07 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233507206385
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:35:10 cmp02 salt-minion[2824]: 'python-guestfs' changed from 'absent' to '1:1.32.2-4ubuntu2'
May  9 23:35:10 cmp02 salt-minion[2824]: 'python-libguestfs' changed from 'absent' to '1'
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Completed state [python-guestfs] at time 23:35:10.443043 duration_in_ms=3936.876
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Running state [gettext-base] at time 23:35:10.457052
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for gettext-base
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] All specified packages are already installed
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Completed state [gettext-base] at time 23:35:10.966695 duration_in_ms=509.642
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Running state [/var/log/nova] at time 23:35:10.969261
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Executing state file.directory for /var/log/nova
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] {'group': 'nova'}
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Completed state [/var/log/nova] at time 23:35:10.972222 duration_in_ms=2.961
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Running state [ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCltIn93BcTMzNK/n2eBze6PyTkmIgdDkeXNR9X4DqE48Va80ojv2pq8xuaBxiNITJzyl+4p4UvTTXo+HmuX8qbHvqgMGXvuPUCpndEfb2r67f6vpMqPwMgBrUg2ZKgN4OsSDHU+H0dia0cEaTjz5pvbUy9lIsSyhrqOUVF9reJq+boAvVEedm8fUqiZuiejAw2D27+rRtdEPgsKMnh3626YEsr963q4rjU/JssV/iKMNu7mk2a+koOrJ+aHvcVU8zJjfA0YghoeVT/I3GLU/MB/4tD/RyR8GM+UYbI4sgAC7ZOCdQyHdJgnEzx3SJIwcS65U0T2XYvn2qXHXqJ9iGZ root@mirantis.com] at time 23:35:10.974375
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Executing state ssh_auth.present for ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCltIn93BcTMzNK/n2eBze6PyTkmIgdDkeXNR9X4DqE48Va80ojv2pq8xuaBxiNITJzyl+4p4UvTTXo+HmuX8qbHvqgMGXvuPUCpndEfb2r67f6vpMqPwMgBrUg2ZKgN4OsSDHU+H0dia0cEaTjz5pvbUy9lIsSyhrqOUVF9reJq+boAvVEedm8fUqiZuiejAw2D27+rRtdEPgsKMnh3626YEsr963q4rjU/JssV/iKMNu7mk2a+koOrJ+aHvcVU8zJjfA0YghoeVT/I3GLU/MB/4tD/RyR8GM+UYbI4sgAC7ZOCdQyHdJgnEzx3SJIwcS65U0T2XYvn2qXHXqJ9iGZ root@mirantis.com
May  9 23:35:10 cmp02 salt-minion[2824]: [WARNING ] Public Key hashing currently defaults to "md5". This will change to "sha256" in the Nitrogen release.
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] {'AAAAB3NzaC1yc2EAAAADAQABAAABAQCltIn93BcTMzNK/n2eBze6PyTkmIgdDkeXNR9X4DqE48Va80ojv2pq8xuaBxiNITJzyl+4p4UvTTXo+HmuX8qbHvqgMGXvuPUCpndEfb2r67f6vpMqPwMgBrUg2ZKgN4OsSDHU+H0dia0cEaTjz5pvbUy9lIsSyhrqOUVF9reJq+boAvVEedm8fUqiZuiejAw2D27+rRtdEPgsKMnh3626YEsr963q4rjU/JssV/iKMNu7mk2a+koOrJ+aHvcVU8zJjfA0YghoeVT/I3GLU/MB/4tD/RyR8GM+UYbI4sgAC7ZOCdQyHdJgnEzx3SJIwcS65U0T2XYvn2qXHXqJ9iGZ': 'New'}
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Completed state [ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCltIn93BcTMzNK/n2eBze6PyTkmIgdDkeXNR9X4DqE48Va80ojv2pq8xuaBxiNITJzyl+4p4UvTTXo+HmuX8qbHvqgMGXvuPUCpndEfb2r67f6vpMqPwMgBrUg2ZKgN4OsSDHU+H0dia0cEaTjz5pvbUy9lIsSyhrqOUVF9reJq+boAvVEedm8fUqiZuiejAw2D27+rRtdEPgsKMnh3626YEsr963q4rjU/JssV/iKMNu7mk2a+koOrJ+aHvcVU8zJjfA0YghoeVT/I3GLU/MB/4tD/RyR8GM+UYbI4sgAC7ZOCdQyHdJgnEzx3SJIwcS65U0T2XYvn2qXHXqJ9iGZ root@mirantis.com] at time 23:35:10.978392 duration_in_ms=4.017
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Running state [nova] at time 23:35:10.979037
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Executing state user.present for nova
May  9 23:35:10 cmp02 salt-minion[2824]: [INFO    ] Executing command ['usermod', '-s', '/bin/bash', 'nova'] in directory '/root'
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Executing command ['usermod', '-G', 'libvirtd', 'nova'] in directory '/root'
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] {'shell': '/bin/bash', 'groups': ['libvirtd', 'nova']}
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova] at time 23:35:11.054645 duration_in_ms=75.608
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Running state [/var/lib/nova/.ssh/id_rsa] at time 23:35:11.055409
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /var/lib/nova/.ssh/id_rsa
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:11 cmp02 salt-minion[2824]: New file
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Completed state [/var/lib/nova/.ssh/id_rsa] at time 23:35:11.061202 duration_in_ms=5.793
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Running state [/var/lib/nova/.ssh/config] at time 23:35:11.061671
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /var/lib/nova/.ssh/config
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:11 cmp02 salt-minion[2824]: New file
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Completed state [/var/lib/nova/.ssh/config] at time 23:35:11.065048 duration_in_ms=3.377
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/nova/nova.conf] at time 23:35:11.065778
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/nova/nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/files/pike/nova-compute.conf.Debian'
May  9 23:35:11 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:11 cmp02 salt-minion[2824]: ---
May  9 23:35:11 cmp02 salt-minion[2824]: +++
May  9 23:35:11 cmp02 salt-minion[2824]: @@ -1,4 +1,2782 @@
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]:  [DEFAULT]
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +compute_manager=nova.compute.manager.ComputeManager
May  9 23:35:11 cmp02 salt-minion[2824]: +network_device_mtu=65000
May  9 23:35:11 cmp02 salt-minion[2824]: +use_neutron = True
May  9 23:35:11 cmp02 salt-minion[2824]: +security_group_api=neutron
May  9 23:35:11 cmp02 salt-minion[2824]: +image_service=nova.image.glance.GlanceImageService
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# When returning instance metadata, this is the class that is used
May  9 23:35:11 cmp02 salt-minion[2824]: +# for getting vendor metadata when that class isn't specified in the individual
May  9 23:35:11 cmp02 salt-minion[2824]: +# request. The value should be the full dot-separated path to the class to use.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid dot-separated class path that can be imported.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 13.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +#vendordata_driver=nova.api.metadata.vendordata_json.JsonFileVendorData
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is used to enable or disable quota checking for tenant networks.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * quota_networks
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# CRUD operations on tenant networks are only available when using nova-network
May  9 23:35:11 cmp02 salt-minion[2824]: +# and nova-network is itself deprecated.
May  9 23:35:11 cmp02 salt-minion[2824]: +#enable_network_quota=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option controls the number of private networks that can be created per
May  9 23:35:11 cmp02 salt-minion[2824]: +# project (or per tenant).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * enable_network_quota
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# CRUD operations on tenant networks are only available when using nova-network
May  9 23:35:11 cmp02 salt-minion[2824]: +# and nova-network is itself deprecated.
May  9 23:35:11 cmp02 salt-minion[2824]: +#quota_networks=3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies the name of the availability zone for the
May  9 23:35:11 cmp02 salt-minion[2824]: +# internal services. Services like nova-scheduler, nova-network,
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-conductor are internal services. These services will appear in
May  9 23:35:11 cmp02 salt-minion[2824]: +# their own internal availability_zone.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string representing an availability zone name
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 'internal' is the default value
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#internal_service_availability_zone=internal
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Default compute node availability_zone.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the availability zone to be used when it is not
May  9 23:35:11 cmp02 salt-minion[2824]: +# specified in the VM creation request. If this option is not set,
May  9 23:35:11 cmp02 salt-minion[2824]: +# the default availability zone 'nova' is used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string representing an availability zone name
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 'nova' is the default value
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_availability_zone=nova
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Length of generated instance admin passwords. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#password_length=12
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time period to generate instance usages for. It is possible to define optional
May  9 23:35:11 cmp02 salt-minion[2824]: +# offset to given period by appending @ character followed by a number defining
May  9 23:35:11 cmp02 salt-minion[2824]: +# offset.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# *  period, example: ``hour``, ``day``, ``month` or ``year``
May  9 23:35:11 cmp02 salt-minion[2824]: +# *  period with offset, example: ``month@15`` will result in monthly audits
May  9 23:35:11 cmp02 salt-minion[2824]: +#    starting on 15th day of month.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_usage_audit_period=month
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +instance_usage_audit = True
May  9 23:35:11 cmp02 salt-minion[2824]: +instance_usage_audit_period = hour
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Start and use a daemon that can run the commands that need to be run with
May  9 23:35:11 cmp02 salt-minion[2824]: +# root privileges. This option is usually enabled on nodes that run nova compute
May  9 23:35:11 cmp02 salt-minion[2824]: +# processes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_rootwrap_daemon=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Path to the rootwrap configuration file.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Goal of the root wrapper is to allow a service-specific unprivileged user to
May  9 23:35:11 cmp02 salt-minion[2824]: +# run a number of actions as the root user in the safest manner possible.
May  9 23:35:11 cmp02 salt-minion[2824]: +# The configuration file used here must match the one defined in the sudoers
May  9 23:35:11 cmp02 salt-minion[2824]: +# entry.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#rootwrap_config=/etc/nova/rootwrap.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +rootwrap_config=/etc/nova/rootwrap.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Explicitly specify the temporary working directory. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#tempdir=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Determine if monkey patching should be applied.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``monkey_patch_modules``: This must have values set for this option to
May  9 23:35:11 cmp02 salt-minion[2824]: +#   have any effect
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#monkey_patch=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# List of modules/decorators to monkey patch.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option allows you to patch a decorator for all functions in specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# modules.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * nova.compute.api:nova.notifications.notify_decorator
May  9 23:35:11 cmp02 salt-minion[2824]: +# * nova.api.ec2.cloud:nova.notifications.notify_decorator
May  9 23:35:11 cmp02 salt-minion[2824]: +# * [...]
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``monkey_patch``: This must be set to ``True`` for this option to
May  9 23:35:11 cmp02 salt-minion[2824]: +#   have any effect
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#monkey_patch_modules=nova.compute.api:nova.notifications.notify_decorator
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Defines which driver to use for controlling virtualization.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``libvirt.LibvirtDriver``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``xenapi.XenAPIDriver``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``fake.FakeDriver``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``ironic.IronicDriver``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``vmwareapi.VMwareVCDriver``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``hyperv.HyperVDriver``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#compute_driver=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +compute_driver = libvirt.LibvirtDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allow destination machine to match source for resize. Useful when
May  9 23:35:11 cmp02 salt-minion[2824]: +# testing in single-host environments. By default it is not allowed
May  9 23:35:11 cmp02 salt-minion[2824]: +# to resize to the same host. Setting this option to true will add
May  9 23:35:11 cmp02 salt-minion[2824]: +# the same host to the destination options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#allow_resize_to_same_host=false
May  9 23:35:11 cmp02 salt-minion[2824]: +allow_resize_to_same_host=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Availability zone to use when user doesn't specify one.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is used by the scheduler to determine which availability
May  9 23:35:11 cmp02 salt-minion[2824]: +# zone to place a new VM instance into if the user did not specify one
May  9 23:35:11 cmp02 salt-minion[2824]: +# at the time of VM boot request.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string representing an availability zone name
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Default value is None.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_schedule_zone=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Image properties that should not be inherited from the instance
May  9 23:35:11 cmp02 salt-minion[2824]: +# when taking a snapshot.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option gives an opportunity to select which image-properties
May  9 23:35:11 cmp02 salt-minion[2824]: +# should not be inherited by newly created snapshots.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A list whose item is an image property. Usually only the image
May  9 23:35:11 cmp02 salt-minion[2824]: +#   properties that are only needed by base images can be included
May  9 23:35:11 cmp02 salt-minion[2824]: +#   here, since the snapshots that are created from the base images
May  9 23:35:11 cmp02 salt-minion[2824]: +#   doesn't need them.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Default list: ['cache_in_nova', 'bittorrent']
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#non_inheritable_image_properties=cache_in_nova,bittorrent
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is used to decide when an image should have no external
May  9 23:35:11 cmp02 salt-minion[2824]: +# ramdisk or kernel. By default this is set to 'nokernel', so when an
May  9 23:35:11 cmp02 salt-minion[2824]: +# image is booted with the property 'kernel_id' with the value
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nokernel', Nova assumes the image doesn't require an external kernel
May  9 23:35:11 cmp02 salt-minion[2824]: +# and ramdisk.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# When an image is booted with the property 'kernel_id' with the value
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nokernel', Nova assumes the image doesn't require an external kernel and
May  9 23:35:11 cmp02 salt-minion[2824]: +# ramdisk. This option allows user to change the API behaviour which should not
May  9 23:35:11 cmp02 salt-minion[2824]: +# be allowed and this value "nokernel" should be hard coded.
May  9 23:35:11 cmp02 salt-minion[2824]: +#null_kernel=nokernel
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# When creating multiple instances with a single request using the
May  9 23:35:11 cmp02 salt-minion[2824]: +# os-multiple-create API extension, this template will be used to build
May  9 23:35:11 cmp02 salt-minion[2824]: +# the display name for each instance. The benefit is that the instances
May  9 23:35:11 cmp02 salt-minion[2824]: +# end up with different hostnames. Example display names when creating
May  9 23:35:11 cmp02 salt-minion[2824]: +# two VM's: name-1, name-2.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Valid keys for the template are: name, uuid, count.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This config changes API behaviour. All changes in API behaviour should be
May  9 23:35:11 cmp02 salt-minion[2824]: +# discoverable.
May  9 23:35:11 cmp02 salt-minion[2824]: +#multi_instance_display_name_template=%(name)s-%(count)d
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum number of devices that will result in a local image being
May  9 23:35:11 cmp02 salt-minion[2824]: +# created on the hypervisor node.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# A negative number means unlimited. Setting max_local_block_devices
May  9 23:35:11 cmp02 salt-minion[2824]: +# to 0 means that any request that attempts to create a local disk
May  9 23:35:11 cmp02 salt-minion[2824]: +# will fail. This option is meant to limit the number of local discs
May  9 23:35:11 cmp02 salt-minion[2824]: +# (so root local disc that is the result of --image being used, and
May  9 23:35:11 cmp02 salt-minion[2824]: +# any other ephemeral and swap disks). 0 does not mean that images
May  9 23:35:11 cmp02 salt-minion[2824]: +# will be automatically converted to volumes and boot instances from
May  9 23:35:11 cmp02 salt-minion[2824]: +# volumes - it just means that all requests that attempt to create a
May  9 23:35:11 cmp02 salt-minion[2824]: +# local disk will fail.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Creating a local disk is not allowed.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Negative number: Allows unlimited number of local discs.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Positive number: Allows only these many number of local discs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#                        (Default value is 3).
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_local_block_devices=3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# A list of monitors that can be used for getting compute metrics.
May  9 23:35:11 cmp02 salt-minion[2824]: +# You can use the alias/name from the setuptools entry points for
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova.compute.monitors.* namespaces. If no namespace is supplied,
May  9 23:35:11 cmp02 salt-minion[2824]: +# the "cpu." namespace is assumed for backwards-compatibility.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An empty list will disable the feature(Default).
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An example value that would enable both the CPU and NUMA memory
May  9 23:35:11 cmp02 salt-minion[2824]: +#   bandwidth monitors that used the virt driver variant:
May  9 23:35:11 cmp02 salt-minion[2824]: +#   ["cpu.virt_driver", "numa_mem_bw.virt_driver"]
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#compute_monitors =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The default format an ephemeral_volume will be formatted with on creation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``ext2``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``ext3``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``ext4``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``xfs``
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``ntfs`` (only for Windows guests)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_ephemeral_format=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Determine if instance should boot or fail on VIF plugging timeout.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Nova sends a port update to Neutron after an instance has been scheduled,
May  9 23:35:11 cmp02 salt-minion[2824]: +# providing Neutron with the necessary information to finish setup of the port.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Once completed, Neutron notifies Nova that it has finished setting up the
May  9 23:35:11 cmp02 salt-minion[2824]: +# port, at which point Nova resumes the boot of the instance since network
May  9 23:35:11 cmp02 salt-minion[2824]: +# connectivity is now supposed to be present. A timeout will occur if the reply
May  9 23:35:11 cmp02 salt-minion[2824]: +# is not received after a given interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines what Nova does when the VIF plugging timeout event
May  9 23:35:11 cmp02 salt-minion[2824]: +# happens. When enabled, the instance will error out. When disabled, the
May  9 23:35:11 cmp02 salt-minion[2824]: +# instance will continue to boot on the assumption that the port is ready.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * True: Instances should fail after VIF plugging timeout
May  9 23:35:11 cmp02 salt-minion[2824]: +# * False: Instances should continue booting after VIF plugging timeout
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#vif_plugging_is_fatal=true
May  9 23:35:11 cmp02 salt-minion[2824]: +vif_plugging_is_fatal=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Timeout for Neutron VIF plugging event message arrival.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds to wait for Neutron vif plugging events to
May  9 23:35:11 cmp02 salt-minion[2824]: +# arrive before continuing or failing (see 'vif_plugging_is_fatal').
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * vif_plugging_is_fatal - If ``vif_plugging_timeout`` is set to zero and
May  9 23:35:11 cmp02 salt-minion[2824]: +#   ``vif_plugging_is_fatal`` is False, events should not be expected to
May  9 23:35:11 cmp02 salt-minion[2824]: +#   arrive at all.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#vif_plugging_timeout=300
May  9 23:35:11 cmp02 salt-minion[2824]: +vif_plugging_timeout=300
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Path to '/etc/network/interfaces' template.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The path to a template file for the '/etc/network/interfaces'-style file,
May  9 23:35:11 cmp02 salt-minion[2824]: +# which
May  9 23:35:11 cmp02 salt-minion[2824]: +# will be populated by nova and subsequently used by cloudinit. This provides a
May  9 23:35:11 cmp02 salt-minion[2824]: +# method to configure network connectivity in environments without a DHCP
May  9 23:35:11 cmp02 salt-minion[2824]: +# server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The template will be rendered using Jinja2 template engine, and receive a
May  9 23:35:11 cmp02 salt-minion[2824]: +# top-level key called ``interfaces``. This key will contain a list of
May  9 23:35:11 cmp02 salt-minion[2824]: +# dictionaries, one for each interface.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Refer to the cloudinit documentaion for more information:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#   https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A path to a Jinja2-formatted template for a Debian '/etc/network/interfaces'
May  9 23:35:11 cmp02 salt-minion[2824]: +#   file. This applies even if using a non Debian-derived guest.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``flat_inject``: This must be set to ``True`` to ensure nova embeds network
May  9 23:35:11 cmp02 salt-minion[2824]: +#   configuration information in the metadata provided through the config drive.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#injected_network_template=$pybasedir/nova/virt/interfaces.template
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The image preallocation mode to use.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Image preallocation allows storage for instance images to be allocated up
May  9 23:35:11 cmp02 salt-minion[2824]: +# front
May  9 23:35:11 cmp02 salt-minion[2824]: +# when the instance is initially provisioned. This ensures immediate feedback is
May  9 23:35:11 cmp02 salt-minion[2824]: +# given if enough space isn't available. In addition, it should significantly
May  9 23:35:11 cmp02 salt-minion[2824]: +# improve performance on writes to new blocks and may even improve I/O
May  9 23:35:11 cmp02 salt-minion[2824]: +# performance to prewritten blocks due to reduced fragmentation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * "none"  => no storage provisioning is done up front
May  9 23:35:11 cmp02 salt-minion[2824]: +# * "space" => storage is fully allocated at instance start
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: none, space
May  9 23:35:11 cmp02 salt-minion[2824]: +#preallocate_images=none
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Enable use of copy-on-write (cow) images.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# QEMU/KVM allow the use of qcow2 as backing files. By disabling this,
May  9 23:35:11 cmp02 salt-minion[2824]: +# backing files will not be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_cow_images=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Force conversion of backing images to raw format.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * True: Backing image files will be converted to raw image format
May  9 23:35:11 cmp02 salt-minion[2824]: +# * False: Backing image files will not be converted
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``compute_driver``: Only the libvirt driver uses this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#force_raw_images=true
May  9 23:35:11 cmp02 salt-minion[2824]: +force_raw_images=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Name of the mkfs commands for ephemeral device.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The format is <os_type>=<mkfs command>
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +#virt_mkfs =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Enable resizing of filesystems via a block device.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If enabled, attempt to resize the filesystem by accessing the image over a
May  9 23:35:11 cmp02 salt-minion[2824]: +# block device. This is done by the host and may not be necessary if the image
May  9 23:35:11 cmp02 salt-minion[2824]: +# contains a recent version of cloud-init. Possible mechanisms require the nbd
May  9 23:35:11 cmp02 salt-minion[2824]: +# driver (for qcow and raw), or loop (for raw).
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#resize_fs_using_block_device=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Amount of time, in seconds, to wait for NBD device start up. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#timeout_nbd=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Location of cached images.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is NOT the full path - just a folder name relative to '$instances_path'.
May  9 23:35:11 cmp02 salt-minion[2824]: +# For per-compute-host cached images, set to '_base_$my_ip'
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#image_cache_subdirectory_name=_base
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Should unused base images be removed? (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#remove_unused_base_images=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Unused unresized base images younger than this will not be removed.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#remove_unused_original_minimum_age_seconds=86400
May  9 23:35:11 cmp02 salt-minion[2824]: +remove_unused_original_minimum_age_seconds=86400
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Generic property to specify the pointer type.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Input devices allow interaction with a graphical framebuffer. For
May  9 23:35:11 cmp02 salt-minion[2824]: +# example to provide a graphic tablet for absolute cursor movement.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If set, the 'hw_pointer_model' image property takes precedence over
May  9 23:35:11 cmp02 salt-minion[2824]: +# this configuration option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * None: Uses default behavior provided by drivers (mouse on PS2 for
May  9 23:35:11 cmp02 salt-minion[2824]: +#         libvirt x86)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ps2mouse: Uses relative movement. Mouse connected by PS2
May  9 23:35:11 cmp02 salt-minion[2824]: +# * usbtablet: Uses absolute movement. Tablet connect by USB
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * usbtablet must be configured with VNC enabled or SPICE enabled and SPICE
May  9 23:35:11 cmp02 salt-minion[2824]: +#   agent disabled. When used with libvirt the instance mode should be
May  9 23:35:11 cmp02 salt-minion[2824]: +#   configured as HVM.
May  9 23:35:11 cmp02 salt-minion[2824]: +#   (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: <None>, ps2mouse, usbtablet
May  9 23:35:11 cmp02 salt-minion[2824]: +#pointer_model=usbtablet
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Defines which physical CPUs (pCPUs) can be used by instance
May  9 23:35:11 cmp02 salt-minion[2824]: +# virtual CPUs (vCPUs).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A comma-separated list of physical CPU numbers that virtual CPUs can be
May  9 23:35:11 cmp02 salt-minion[2824]: +#   allocated to by default. Each element should be either a single CPU number,
May  9 23:35:11 cmp02 salt-minion[2824]: +#   a range of CPU numbers, or a caret followed by a CPU number to be
May  9 23:35:11 cmp02 salt-minion[2824]: +#   excluded from a previous range. For example:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     vcpu_pin_set = "4-12,^8,15"
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#vcpu_pin_set=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of huge/large memory pages to reserved per NUMA host cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A list of valid key=value which reflect NUMA node ID, page size
May  9 23:35:11 cmp02 salt-minion[2824]: +#   (Default unit is KiB) and number of pages to be reserved.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     reserved_huge_pages = node:0,size:2048,count:64
May  9 23:35:11 cmp02 salt-minion[2824]: +#     reserved_huge_pages = node:1,size:1GB,count:1
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#   In this example we are reserving on NUMA node 0 64 pages of 2MiB
May  9 23:35:11 cmp02 salt-minion[2824]: +#   and on NUMA node 1 1 page of 1GiB.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (dict value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#reserved_huge_pages=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Amount of disk resources in MB to make them always available to host. The
May  9 23:35:11 cmp02 salt-minion[2824]: +# disk usage gets reported back to the scheduler from nova-compute running
May  9 23:35:11 cmp02 salt-minion[2824]: +# on the compute nodes. To prevent the disk resources from being considered
May  9 23:35:11 cmp02 salt-minion[2824]: +# as available, this option can be used to reserve disk space for that host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing amount of disk in MB to reserve
May  9 23:35:11 cmp02 salt-minion[2824]: +#   for the host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#reserved_host_disk_mb=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Amount of memory in MB to reserve for the host so that it is always available
May  9 23:35:11 cmp02 salt-minion[2824]: +# to host processes. The host resources usage is reported back to the scheduler
May  9 23:35:11 cmp02 salt-minion[2824]: +# continuously from nova-compute running on the compute node. To prevent the
May  9 23:35:11 cmp02 salt-minion[2824]: +# host
May  9 23:35:11 cmp02 salt-minion[2824]: +# memory from being considered as available, this option is used to reserve
May  9 23:35:11 cmp02 salt-minion[2824]: +# memory for the host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing amount of memory in MB to reserve
May  9 23:35:11 cmp02 salt-minion[2824]: +#   for the host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#reserved_host_memory_mb=512
May  9 23:35:11 cmp02 salt-minion[2824]: +reserved_host_memory_mb = 512
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option helps you specify virtual CPU to physical CPU allocation ratio.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From Ocata (15.0.0) this is used to influence the hosts selected by
May  9 23:35:11 cmp02 salt-minion[2824]: +# the Placement API. Note that when Placement is used, the CoreFilter
May  9 23:35:11 cmp02 salt-minion[2824]: +# is redundant, because the Placement API will have already filtered
May  9 23:35:11 cmp02 salt-minion[2824]: +# out hosts that would have failed the CoreFilter.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This configuration specifies ratio for CoreFilter which can be set
May  9 23:35:11 cmp02 salt-minion[2824]: +# per compute node. For AggregateCoreFilter, it will fall back to this
May  9 23:35:11 cmp02 salt-minion[2824]: +# configuration value if no per-aggregate setting is found.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# NOTE: This can be set per-compute, or if set to 0.0, the value
May  9 23:35:11 cmp02 salt-minion[2824]: +# set on the scheduler node(s) or compute node(s) will be used
May  9 23:35:11 cmp02 salt-minion[2824]: +# and defaulted to 16.0'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid positive integer or float value
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#cpu_allocation_ratio=0.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option helps you specify virtual RAM to physical RAM
May  9 23:35:11 cmp02 salt-minion[2824]: +# allocation ratio.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From Ocata (15.0.0) this is used to influence the hosts selected by
May  9 23:35:11 cmp02 salt-minion[2824]: +# the Placement API. Note that when Placement is used, the RamFilter
May  9 23:35:11 cmp02 salt-minion[2824]: +# is redundant, because the Placement API will have already filtered
May  9 23:35:11 cmp02 salt-minion[2824]: +# out hosts that would have failed the RamFilter.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This configuration specifies ratio for RamFilter which can be set
May  9 23:35:11 cmp02 salt-minion[2824]: +# per compute node. For AggregateRamFilter, it will fall back to this
May  9 23:35:11 cmp02 salt-minion[2824]: +# configuration value if no per-aggregate setting found.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# NOTE: This can be set per-compute, or if set to 0.0, the value
May  9 23:35:11 cmp02 salt-minion[2824]: +# set on the scheduler node(s) or compute node(s) will be used and
May  9 23:35:11 cmp02 salt-minion[2824]: +# defaulted to 1.5.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid positive integer or float value
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#ram_allocation_ratio=0.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Defines which physical CPUs (pCPUs) can be used by instance
May  9 23:35:11 cmp02 salt-minion[2824]: +# virtual CPUs (vCPUs).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A comma-separated list of physical CPU numbers that virtual CPUs can be
May  9 23:35:11 cmp02 salt-minion[2824]: +#   allocated to by default. Each element should be either a single CPU number,
May  9 23:35:11 cmp02 salt-minion[2824]: +#   a range of CPU numbers, or a caret followed by a CPU number to be
May  9 23:35:11 cmp02 salt-minion[2824]: +#   excluded from a previous range. For example:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     vcpu_pin_set = "4-12,^8,15"
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#vcpu_pin_set=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option helps you specify virtual disk to physical disk
May  9 23:35:11 cmp02 salt-minion[2824]: +# allocation ratio.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From Ocata (15.0.0) this is used to influence the hosts selected by
May  9 23:35:11 cmp02 salt-minion[2824]: +# the Placement API. Note that when Placement is used, the DiskFilter
May  9 23:35:11 cmp02 salt-minion[2824]: +# is redundant, because the Placement API will have already filtered
May  9 23:35:11 cmp02 salt-minion[2824]: +# out hosts that would have failed the DiskFilter.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# A ratio greater than 1.0 will result in over-subscription of the
May  9 23:35:11 cmp02 salt-minion[2824]: +# available physical disk, which can be useful for more
May  9 23:35:11 cmp02 salt-minion[2824]: +# efficiently packing instances created with images that do not
May  9 23:35:11 cmp02 salt-minion[2824]: +# use the entire virtual disk, such as sparse or compressed
May  9 23:35:11 cmp02 salt-minion[2824]: +# images. It can be set to a value between 0.0 and 1.0 in order
May  9 23:35:11 cmp02 salt-minion[2824]: +# to preserve a percentage of the disk for uses other than
May  9 23:35:11 cmp02 salt-minion[2824]: +# instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# NOTE: This can be set per-compute, or if set to 0.0, the value
May  9 23:35:11 cmp02 salt-minion[2824]: +# set on the scheduler node(s) or compute node(s) will be used and
May  9 23:35:11 cmp02 salt-minion[2824]: +# defaulted to 1.0'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid positive integer or float value
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#disk_allocation_ratio=0.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Console proxy host to be used to connect to instances on this host. It is the
May  9 23:35:11 cmp02 salt-minion[2824]: +# publicly visible name for the console host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Current hostname (default) or any string representing hostname.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#console_host=socket.gethostname()
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Name of the network to be used to set access IPs for instances. If there are
May  9 23:35:11 cmp02 salt-minion[2824]: +# multiple IPs to choose from, an arbitrary one will be chosen.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * None (default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string representing network name.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_access_ip_network_name=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Whether to batch up the application of IPTables rules during a host restart
May  9 23:35:11 cmp02 salt-minion[2824]: +# and apply all at the end of the init phase.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#defer_iptables_apply=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Specifies where instances are stored on the hypervisor's disk.
May  9 23:35:11 cmp02 salt-minion[2824]: +# It can point to locally attached storage or a directory on NFS.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * $state_path/instances where state_path is a config option that specifies
May  9 23:35:11 cmp02 salt-minion[2824]: +#   the top-level directory for maintaining nova's state. (default) or
May  9 23:35:11 cmp02 salt-minion[2824]: +#   Any string representing directory path.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instances_path=$state_path/instances
May  9 23:35:11 cmp02 salt-minion[2824]: +instances_path = $state_path/instances
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option enables periodic compute.instance.exists notifications. Each
May  9 23:35:11 cmp02 salt-minion[2824]: +# compute node must be configured to generate system usage data. These
May  9 23:35:11 cmp02 salt-minion[2824]: +# notifications are consumed by OpenStack Telemetry service.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_usage_audit=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum number of 1 second retries in live_migration. It specifies number
May  9 23:35:11 cmp02 salt-minion[2824]: +# of retries to iptables when it complains. It happens when an user continuously
May  9 23:35:11 cmp02 salt-minion[2824]: +# sends live-migration request to same host leading to concurrent request
May  9 23:35:11 cmp02 salt-minion[2824]: +# to iptables.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing retry count.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#live_migration_retry_count=30
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies whether to start guests that were running before the
May  9 23:35:11 cmp02 salt-minion[2824]: +# host rebooted. It ensures that all of the instances on a Nova compute node
May  9 23:35:11 cmp02 salt-minion[2824]: +# resume their state each time the compute node boots or restarts.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#resume_guests_state_on_host_boot=false
May  9 23:35:11 cmp02 salt-minion[2824]: +resume_guests_state_on_host_boot=True
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of times to retry network allocation. It is required to attempt network
May  9 23:35:11 cmp02 salt-minion[2824]: +# allocation retries if the virtual interface plug fails.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing retry count.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#network_allocate_retries=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Limits the maximum number of instance builds to run concurrently by
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-compute. Compute service can attempt to build an infinite number of
May  9 23:35:11 cmp02 salt-minion[2824]: +# instances, if asked to do so. This limit is enforced to avoid building
May  9 23:35:11 cmp02 salt-minion[2824]: +# unlimited instance concurrently on a compute node. This value can be set
May  9 23:35:11 cmp02 salt-minion[2824]: +# per compute node.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0 : treated as unlimited.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing maximum concurrent builds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_concurrent_builds=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum number of live migrations to run concurrently. This limit is enforced
May  9 23:35:11 cmp02 salt-minion[2824]: +# to avoid outbound live migrations overwhelming the host/network and causing
May  9 23:35:11 cmp02 salt-minion[2824]: +# failures. It is not recommended that you change this unless you are very sure
May  9 23:35:11 cmp02 salt-minion[2824]: +# that doing so is safe and stable in your environment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0 : treated as unlimited.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Negative value defaults to 0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing maximum number of live migrations
May  9 23:35:11 cmp02 salt-minion[2824]: +#   to run concurrently.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_concurrent_live_migrations=1
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of times to retry block device allocation on failures. Starting with
May  9 23:35:11 cmp02 salt-minion[2824]: +# Liberty, Cinder can use image volume cache. This may help with block device
May  9 23:35:11 cmp02 salt-minion[2824]: +# allocation performance. Look at the cinder image_volume_cache_enabled
May  9 23:35:11 cmp02 salt-minion[2824]: +# configuration option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 60 (default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * If value is 0, then one attempt is made.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any negative value is treated as 0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * For any value > 0, total attempts are (value + 1)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#block_device_allocate_retries=60
May  9 23:35:11 cmp02 salt-minion[2824]: +block_device_allocate_retries=600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of greenthreads available for use to sync power states.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option can be used to reduce the number of concurrent requests
May  9 23:35:11 cmp02 salt-minion[2824]: +# made to the hypervisor or system with real instance power states
May  9 23:35:11 cmp02 salt-minion[2824]: +# for performance reasons, for example, with Ironic.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer representing greenthreads count.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#sync_power_state_pool_size=1000
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds to wait between runs of the image cache manager.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: run at the default rate.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * -1: disable
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any other value
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#image_cache_manager_interval=2400
May  9 23:35:11 cmp02 salt-minion[2824]: +image_cache_manager_interval=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval to pull network bandwidth usage info.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Not supported on all hypervisors. If a hypervisor doesn't support bandwidth
May  9 23:35:11 cmp02 salt-minion[2824]: +# usage, it will not get the info in the usage events.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Will run at the default periodic interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value < 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#bandwidth_poll_interval=600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval to sync power states between the database and the hypervisor.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The interval that Nova checks the actual virtual machine power state
May  9 23:35:11 cmp02 salt-minion[2824]: +# and the power state that Nova has in its database. If a user powers
May  9 23:35:11 cmp02 salt-minion[2824]: +# down their VM, Nova updates the API to report the VM has been
May  9 23:35:11 cmp02 salt-minion[2824]: +# powered down. Should something turn on the VM unexpectedly,
May  9 23:35:11 cmp02 salt-minion[2824]: +# Nova will turn the VM back off to keep the system in the expected
May  9 23:35:11 cmp02 salt-minion[2824]: +# state.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Will run at the default periodic interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value < 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * If ``handle_virt_lifecycle_events`` in workarounds_group is
May  9 23:35:11 cmp02 salt-minion[2824]: +#   false and this option is negative, then instances that get out
May  9 23:35:11 cmp02 salt-minion[2824]: +#   of sync between the hypervisor and the Nova database will have
May  9 23:35:11 cmp02 salt-minion[2824]: +#   to be synchronized manually.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#sync_power_state_interval=600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval between instance network information cache updates.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds after which each compute node runs the task of
May  9 23:35:11 cmp02 salt-minion[2824]: +# querying Neutron for all of its instances networking information,
May  9 23:35:11 cmp02 salt-minion[2824]: +# then updates the Nova db with that information. Nova will never
May  9 23:35:11 cmp02 salt-minion[2824]: +# update it's cache if this option is set to 0. If we don't update the
May  9 23:35:11 cmp02 salt-minion[2824]: +# cache, the metadata service and nova-api endpoints will be proxying
May  9 23:35:11 cmp02 salt-minion[2824]: +# incorrect network data about the instance. So, it is not recommended
May  9 23:35:11 cmp02 salt-minion[2824]: +# to set this option to 0.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value <=0 will disable the sync. This is not recommended.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#heal_instance_info_cache_interval=60
May  9 23:35:11 cmp02 salt-minion[2824]: +heal_instance_info_cache_interval = 60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval for reclaiming deleted instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# A value greater than 0 will enable SOFT_DELETE of instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option decides whether the server to be deleted will be put into
May  9 23:35:11 cmp02 salt-minion[2824]: +# the SOFT_DELETED state. If this value is greater than 0, the deleted
May  9 23:35:11 cmp02 salt-minion[2824]: +# server will not be deleted immediately, instead it will be put into
May  9 23:35:11 cmp02 salt-minion[2824]: +# a queue until it's too old (deleted time greater than the value of
May  9 23:35:11 cmp02 salt-minion[2824]: +# reclaim_instance_interval). The server can be recovered from the
May  9 23:35:11 cmp02 salt-minion[2824]: +# delete queue by using the restore action. If the deleted server remains
May  9 23:35:11 cmp02 salt-minion[2824]: +# longer than the value of reclaim_instance_interval, it will be
May  9 23:35:11 cmp02 salt-minion[2824]: +# deleted by a periodic task in the compute service automatically.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note that this option is read from both the API and compute nodes, and
May  9 23:35:11 cmp02 salt-minion[2824]: +# must be set globally otherwise servers could be put into a soft deleted
May  9 23:35:11 cmp02 salt-minion[2824]: +# state in the API and never actually reclaimed (deleted) on the compute
May  9 23:35:11 cmp02 salt-minion[2824]: +# node.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer(in seconds) greater than 0 will enable
May  9 23:35:11 cmp02 salt-minion[2824]: +#   this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value <=0 will disable the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#reclaim_instance_interval=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval for gathering volume usages.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option updates the volume usage cache for every
May  9 23:35:11 cmp02 salt-minion[2824]: +# volume_usage_poll_interval number of seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer(in seconds) greater than 0 will enable
May  9 23:35:11 cmp02 salt-minion[2824]: +#   this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value <=0 will disable the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#volume_usage_poll_interval=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval for polling shelved instances to offload.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The periodic task runs for every shelved_poll_interval number
May  9 23:35:11 cmp02 salt-minion[2824]: +# of seconds and checks if there are any shelved instances. If it
May  9 23:35:11 cmp02 salt-minion[2824]: +# finds a shelved instance, based on the 'shelved_offload_time' config
May  9 23:35:11 cmp02 salt-minion[2824]: +# value it offloads the shelved instances. Check 'shelved_offload_time'
May  9 23:35:11 cmp02 salt-minion[2824]: +# config option description for details.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value <= 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``shelved_offload_time``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#shelved_poll_interval=3600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time before a shelved instance is eligible for removal from a host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# By default this option is set to 0 and the shelved instance will be
May  9 23:35:11 cmp02 salt-minion[2824]: +# removed from the hypervisor immediately after shelve operation.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Otherwise, the instance will be kept for the value of
May  9 23:35:11 cmp02 salt-minion[2824]: +# shelved_offload_time(in seconds) so that during the time period the
May  9 23:35:11 cmp02 salt-minion[2824]: +# unshelve action will be faster, then the periodic task will remove
May  9 23:35:11 cmp02 salt-minion[2824]: +# the instance from hypervisor after shelved_offload_time passes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Instance will be immediately offloaded after being
May  9 23:35:11 cmp02 salt-minion[2824]: +#      shelved.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value < 0: An instance will never offload.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds: The instance will exist for
May  9 23:35:11 cmp02 salt-minion[2824]: +#   the specified number of seconds before being offloaded.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#shelved_offload_time=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval for retrying failed instance file deletes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option depends on 'maximum_instance_delete_attempts'.
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies how often to retry deletes whereas
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'maximum_instance_delete_attempts' specifies the maximum number
May  9 23:35:11 cmp02 salt-minion[2824]: +# of retry attempts that can be made.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Will run at the default periodic interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value < 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``maximum_instance_delete_attempts`` from instance_cleaning_opts
May  9 23:35:11 cmp02 salt-minion[2824]: +#   group.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_delete_interval=300
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval (in seconds) between block device allocation retries on failures.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option allows the user to specify the time interval between
May  9 23:35:11 cmp02 salt-minion[2824]: +# consecutive retries. 'block_device_allocate_retries' option specifies
May  9 23:35:11 cmp02 salt-minion[2824]: +# the maximum number of retries.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds enables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``block_device_allocate_retries`` in compute_manager_opts group.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#block_device_allocate_retries_interval=3
May  9 23:35:11 cmp02 salt-minion[2824]: +block_device_allocate_retries_interval=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval between sending the scheduler a list of current instance UUIDs to
May  9 23:35:11 cmp02 salt-minion[2824]: +# verify that its view of instances is in sync with nova.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If the CONF option 'scheduler_tracks_instance_changes' is
May  9 23:35:11 cmp02 salt-minion[2824]: +# False, the sync calls will not be made. So, changing this option will
May  9 23:35:11 cmp02 salt-minion[2824]: +# have no effect.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If the out of sync situations are not very common, this interval
May  9 23:35:11 cmp02 salt-minion[2824]: +# can be increased to lower the number of RPC messages being sent.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Likewise, if sync issues turn out to be a problem, the interval
May  9 23:35:11 cmp02 salt-minion[2824]: +# can be lowered to check more frequently.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Will run at the default periodic interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value < 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This option has no impact if ``scheduler_tracks_instance_changes``
May  9 23:35:11 cmp02 salt-minion[2824]: +#   is set to False.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#scheduler_instance_sync_interval=120
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval for updating compute resources.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies how often the update_available_resources
May  9 23:35:11 cmp02 salt-minion[2824]: +# periodic task should run. A number less than 0 means to disable the
May  9 23:35:11 cmp02 salt-minion[2824]: +# task completely. Leaving this at the default of 0 will cause this to
May  9 23:35:11 cmp02 salt-minion[2824]: +# run at the default periodic interval. Setting it to any positive
May  9 23:35:11 cmp02 salt-minion[2824]: +# value will cause it to run at approximately that number of seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Will run at the default periodic interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value < 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#update_resources_interval=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time interval after which an instance is hard rebooted automatically.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When doing a soft reboot, it is possible that a guest kernel is
May  9 23:35:11 cmp02 salt-minion[2824]: +# completely hung in a way that causes the soft reboot task
May  9 23:35:11 cmp02 salt-minion[2824]: +# to not ever finish. Setting this option to a time period in seconds
May  9 23:35:11 cmp02 salt-minion[2824]: +# will automatically hard reboot an instance if it has been stuck
May  9 23:35:11 cmp02 salt-minion[2824]: +# in a rebooting state longer than N seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Disables the option (default).
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds: Enables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#reboot_timeout=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum time in seconds that an instance can take to build.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If this timer expires, instance status will be changed to ERROR.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Enabling this option will make sure an instance will not be stuck
May  9 23:35:11 cmp02 salt-minion[2824]: +# in BUILD state for a longer period.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Disables the option (default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds: Enables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_build_timeout=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval to wait before un-rescuing an instance stuck in RESCUE.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Disables the option (default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds: Enables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#rescue_timeout=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 systemd[1]: Started /bin/systemctl restart nova-compute.service.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Automatically confirm resizes after N seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Resize functionality will save the existing server before resizing.
May  9 23:35:11 cmp02 salt-minion[2824]: +# After the resize completes, user is requested to confirm the resize.
May  9 23:35:11 cmp02 salt-minion[2824]: +# The user has the opportunity to either confirm or revert all
May  9 23:35:11 cmp02 salt-minion[2824]: +# changes. Confirm resize removes the original server and changes
May  9 23:35:11 cmp02 salt-minion[2824]: +# server status from resized to active. Setting this option to a time
May  9 23:35:11 cmp02 salt-minion[2824]: +# period (in seconds) will automatically confirm the resize if the
May  9 23:35:11 cmp02 salt-minion[2824]: +# server is in resized state longer than that time.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Disables the option (default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds: Enables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#resize_confirm_window=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Total time to wait in seconds for an instance toperform a clean
May  9 23:35:11 cmp02 salt-minion[2824]: +# shutdown.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# It determines the overall period (in seconds) a VM is allowed to
May  9 23:35:11 cmp02 salt-minion[2824]: +# perform a clean shutdown. While performing stop, rescue and shelve,
May  9 23:35:11 cmp02 salt-minion[2824]: +# rebuild operations, configuring this option gives the VM a chance
May  9 23:35:11 cmp02 salt-minion[2824]: +# to perform a controlled shutdown before the instance is powered off.
May  9 23:35:11 cmp02 salt-minion[2824]: +# The default timeout is 60 seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The timeout value can be overridden on a per image basis by means
May  9 23:35:11 cmp02 salt-minion[2824]: +# of os_shutdown_timeout that is an image metadata setting allowing
May  9 23:35:11 cmp02 salt-minion[2824]: +# different types of operating systems to specify how much time they
May  9 23:35:11 cmp02 salt-minion[2824]: +# need to shut down cleanly.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds (default value is 60).
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +#shutdown_timeout=60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The compute service periodically checks for instances that have been
May  9 23:35:11 cmp02 salt-minion[2824]: +# deleted in the database but remain running on the compute node. The
May  9 23:35:11 cmp02 salt-minion[2824]: +# above option enables action to be taken when such instances are
May  9 23:35:11 cmp02 salt-minion[2824]: +# identified.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * reap: Powers down the instances and deletes them(default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * log: Logs warning message about deletion of the resource
May  9 23:35:11 cmp02 salt-minion[2824]: +# * shutdown: Powers down instances and marks them as non-
May  9 23:35:11 cmp02 salt-minion[2824]: +#   bootable which can be later used for debugging/analysis
May  9 23:35:11 cmp02 salt-minion[2824]: +# * noop: Takes no action
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 systemd[1]: Stopping OpenStack Compute...
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * running_deleted_instance_poll
May  9 23:35:11 cmp02 salt-minion[2824]: +# * running_deleted_instance_timeout
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: noop, log, shutdown, reap
May  9 23:35:11 cmp02 salt-minion[2824]: +#running_deleted_instance_action=reap
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time interval in seconds to wait between runs for the clean up action.
May  9 23:35:11 cmp02 salt-minion[2824]: +# If set to 0, above check will be disabled. If "running_deleted_instance
May  9 23:35:11 cmp02 salt-minion[2824]: +# _action" is set to "log" or "reap", a value greater than 0 must be set.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds enables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0: Disables the option.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 1800: Default value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * running_deleted_instance_action
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#running_deleted_instance_poll_interval=1800
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time interval in seconds to wait for the instances that have
May  9 23:35:11 cmp02 salt-minion[2824]: +# been marked as deleted in database to be eligible for cleanup.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer in seconds(default is 0).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * "running_deleted_instance_action"
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#running_deleted_instance_timeout=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The number of times to attempt to reap an instance's files.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies the maximum number of retry attempts
May  9 23:35:11 cmp02 salt-minion[2824]: +# that can be made.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer defines how many attempts are made.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any value <=0 means no delete attempts occur, but you should use
May  9 23:35:11 cmp02 salt-minion[2824]: +#   ``instance_delete_interval`` to disable the delete attempts.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``instance_delete_interval`` in interval_opts group can be used to disable
May  9 23:35:11 cmp02 salt-minion[2824]: +#   this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#maximum_instance_delete_attempts=5
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the message queue topic that the compute service 'listens' on. It is
May  9 23:35:11 cmp02 salt-minion[2824]: +# used when the compute service is started up to configure the queue, and
May  9 23:35:11 cmp02 salt-minion[2824]: +# whenever an RPC call to the compute service is made.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string, but there is almost never any reason to ever change this value
May  9 23:35:11 cmp02 salt-minion[2824]: +#   from its default of 'compute'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 systemd[1]: Stopped OpenStack Compute.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# There is no need to let users choose the RPC topic for all services - there
May  9 23:35:11 cmp02 salt-minion[2824]: +# is little gain from this. Furthermore, it makes it really easy to break Nova
May  9 23:35:11 cmp02 salt-minion[2824]: +# by using this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#compute_topic=compute
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Sets the scope of the check for unique instance names.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The default doesn't check for unique names. If a scope for the name check is
May  9 23:35:11 cmp02 salt-minion[2824]: +# set, a launch of a new instance or an update of an existing instance with a
May  9 23:35:11 cmp02 salt-minion[2824]: +# duplicate name will result in an ''InstanceExists'' error. The uniqueness is
May  9 23:35:11 cmp02 salt-minion[2824]: +# case-insensitive. Setting this option can increase the usability for end
May  9 23:35:11 cmp02 salt-minion[2824]: +# users as they don't have to distinguish among instances with the same name
May  9 23:35:11 cmp02 salt-minion[2824]: +# by their IDs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * '': An empty value means that no uniqueness check is done and duplicate
May  9 23:35:11 cmp02 salt-minion[2824]: +#   names are possible.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * "project": The instance name check is done only for instances within the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   same project.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * "global": The instance name check is done for all instances regardless of
May  9 23:35:11 cmp02 salt-minion[2824]: +#   the project.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: '', project, global
May  9 23:35:11 cmp02 salt-minion[2824]: +#osapi_compute_unique_server_name_scope =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Enable new services on this host automatically.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When a new service (for example "nova-compute") starts up, it gets
May  9 23:35:11 cmp02 salt-minion[2824]: +# registered in the database as an enabled service. Sometimes it can be useful
May  9 23:35:11 cmp02 salt-minion[2824]: +# to register new services in disabled state and then enabled them at a later
May  9 23:35:11 cmp02 salt-minion[2824]: +# point in time. This option can set this behavior for all services per host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``True``: Each new service is enabled as soon as it registers itself.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``False``: Services must be enabled via a REST API call or with the CLI
May  9 23:35:11 cmp02 salt-minion[2824]: +#   with ``nova service-enable <hostname> <binary>``, otherwise they are not
May  9 23:35:11 cmp02 salt-minion[2824]: +#   ready to use.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#enable_new_services=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Template string to be used to generate instance names.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This template controls the creation of the database name of an instance. This
May  9 23:35:11 cmp02 systemd[1]: Starting OpenStack Compute...
May  9 23:35:11 cmp02 salt-minion[2824]: +# is *not* the display name you enter when creating an instance (via Horizon
May  9 23:35:11 cmp02 salt-minion[2824]: +# or CLI). For a new deployment it is advisable to change the default value
May  9 23:35:11 cmp02 salt-minion[2824]: +# (which uses the database autoincrement) to another value which makes use
May  9 23:35:11 cmp02 salt-minion[2824]: +# of the attributes of an instance, like ``instance-%(uuid)s``. If you
May  9 23:35:11 cmp02 salt-minion[2824]: +# already have instances in your deployment when you change this, your
May  9 23:35:11 cmp02 salt-minion[2824]: +# deployment will break.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A string which either uses the instance database ID (like the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A string with a list of named database columns, for example ``%(id)d``
May  9 23:35:11 cmp02 salt-minion[2824]: +#   or ``%(uuid)s`` or ``%(hostname)s``.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * not to be confused with: ``multi_instance_display_name_template``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_name_template=instance-%08x
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of times to retry live-migration before failing.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * If == -1, try until out of hosts (default)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * If == 0, only try once, no retries
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Integer greater than 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#migrate_max_retries=-1
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Configuration drive format
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Configuration drive format that will contain metadata attached to the
May  9 23:35:11 cmp02 salt-minion[2824]: +# instance when it boots.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * iso9660: A file system image standard that is widely supported across
May  9 23:35:11 cmp02 salt-minion[2824]: +#   operating systems. NOTE: Mind the libvirt bug
May  9 23:35:11 cmp02 salt-minion[2824]: +#   (https://bugs.launchpad.net/nova/+bug/1246201) - If your hypervisor
May  9 23:35:11 cmp02 salt-minion[2824]: +#   driver is libvirt, and you want live migrate to work without shared storage,
May  9 23:35:11 cmp02 salt-minion[2824]: +#   then use VFAT.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * vfat: For legacy reasons, you can configure the configuration drive to
May  9 23:35:11 cmp02 salt-minion[2824]: +#   use VFAT format instead of ISO 9660.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This option is meaningful when one of the following alternatives occur:
May  9 23:35:11 cmp02 salt-minion[2824]: +#   1. force_config_drive option set to 'true'
May  9 23:35:11 cmp02 salt-minion[2824]: +#   2. the REST API call to create the instance contains an enable flag for
May  9 23:35:11 cmp02 salt-minion[2824]: +#      config drive option
May  9 23:35:11 cmp02 salt-minion[2824]: +#   3. the image used to create the instance requires a config drive,
May  9 23:35:11 cmp02 salt-minion[2824]: +#      this is defined by img_config_drive property for that image.
May  9 23:35:11 cmp02 systemd[1]: Started OpenStack Compute.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A compute node running Hyper-V hypervisor can be configured to attach
May  9 23:35:11 cmp02 salt-minion[2824]: +#   configuration drive as a CD drive. To attach the configuration drive as a CD
May  9 23:35:11 cmp02 salt-minion[2824]: +#   drive, set config_drive_cdrom option at hyperv section, to true.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: iso9660, vfat
May  9 23:35:11 cmp02 salt-minion[2824]: +#config_drive_format=iso9660
May  9 23:35:11 cmp02 salt-minion[2824]: +config_drive_format=vfat
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Force injection to take place on a config drive
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When this option is set to true configuration drive functionality will be
May  9 23:35:11 cmp02 salt-minion[2824]: +# forced enabled by default, otherwise user can still enable configuration
May  9 23:35:11 cmp02 salt-minion[2824]: +# drives via the REST API or image metadata properties.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * True: Force to use of configuration drive regardless the user's input in the
May  9 23:35:11 cmp02 salt-minion[2824]: +#         REST API call.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * False: Do not force use of configuration drive. Config drives can still be
May  9 23:35:11 cmp02 salt-minion[2824]: +#          enabled via the REST API or image metadata properties.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Use the 'mkisofs_cmd' flag to set the path where you install the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   genisoimage program. If genisoimage is in same path as the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   nova-compute service, you do not need to set this flag.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * To use configuration drive with Hyper-V, you must set the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   'mkisofs_cmd' value to the full path to an mkisofs.exe installation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#   Additionally, you must set the qemu_img_cmd value in the hyperv
May  9 23:35:11 cmp02 salt-minion[2824]: +#   configuration section to the full path to an qemu-img command
May  9 23:35:11 cmp02 salt-minion[2824]: +#   installation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#force_config_drive=false
May  9 23:35:11 cmp02 salt-minion[2824]: +force_config_drive=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Name or path of the tool used for ISO image creation
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Use the mkisofs_cmd flag to set the path where you install the genisoimage
May  9 23:35:11 cmp02 salt-minion[2824]: +# program. If genisoimage is on the system path, you do not need to change
May  9 23:35:11 cmp02 salt-minion[2824]: +# the default value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# To use configuration drive with Hyper-V, you must set the mkisofs_cmd value
May  9 23:35:11 cmp02 salt-minion[2824]: +# to the full path to an mkisofs.exe installation. Additionally, you must set
May  9 23:35:11 cmp02 salt-minion[2824]: +# the qemu_img_cmd value in the hyperv configuration section to the full path
May  9 23:35:11 cmp02 salt-minion[2824]: +# to an qemu-img command installation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Name of the ISO image creator program, in case it is in the same directory
May  9 23:35:11 cmp02 salt-minion[2824]: +#   as the nova-compute service
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Path to ISO image creator program
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This option is meaningful when config drives are enabled.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * To use configuration drive with Hyper-V, you must set the qemu_img_cmd
May  9 23:35:11 cmp02 salt-minion[2824]: +#   value in the hyperv configuration section to the full path to an qemu-img
May  9 23:35:11 cmp02 salt-minion[2824]: +#   command installation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#mkisofs_cmd=genisoimage
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-console-proxy is used to set up multi-tenant VM console access.
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option allows pluggable driver program for the console session
May  9 23:35:11 cmp02 salt-minion[2824]: +# and represents driver to use for the console proxy.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A string representing fully classified class name of console driver.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option no longer does anything. Previously this option had only two
May  9 23:35:11 cmp02 salt-minion[2824]: +# valid,
May  9 23:35:11 cmp02 salt-minion[2824]: +# in-tree values: nova.console.xvp.XVPConsoleProxy and
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova.console.fake.FakeConsoleProxy. The latter of these was only used in tests
May  9 23:35:11 cmp02 salt-minion[2824]: +# and has since been replaced.
May  9 23:35:11 cmp02 salt-minion[2824]: +#console_driver=nova.console.xvp.XVPConsoleProxy
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Represents the message queue topic name used by nova-console
May  9 23:35:11 cmp02 salt-minion[2824]: +# service when communicating via the AMQP server. The Nova API uses a message
May  9 23:35:11 cmp02 salt-minion[2824]: +# queue to communicate with nova-console to retrieve a console URL for that
May  9 23:35:11 cmp02 salt-minion[2824]: +# host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A string representing topic exchange name
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# There is no need to let users choose the RPC topic for all services - there
May  9 23:35:11 cmp02 salt-minion[2824]: +# is little gain from this. Furthermore, it makes it really easy to break Nova
May  9 23:35:11 cmp02 salt-minion[2824]: +# by using this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#console_topic=console
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option allows you to change the message topic used by nova-consoleauth
May  9 23:35:11 cmp02 salt-minion[2824]: +# service when communicating via the AMQP server. Nova Console Authentication
May  9 23:35:11 cmp02 salt-minion[2824]: +# server authenticates nova consoles. Users can then access their instances
May  9 23:35:11 cmp02 salt-minion[2824]: +# through VNC clients. The Nova API service uses a message queue to
May  9 23:35:11 cmp02 salt-minion[2824]: +# communicate with nova-consoleauth to get a VNC console.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 'consoleauth' (default) or Any string representing topic exchange name.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# There is no need to let users choose the RPC topic for all services - there
May  9 23:35:11 cmp02 salt-minion[2824]: +# is little gain from this. Furthermore, it makes it really easy to break Nova
May  9 23:35:11 cmp02 salt-minion[2824]: +# by using this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#consoleauth_topic=consoleauth
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED: The driver to use for database access (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 13.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +#db_driver=nova.db
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Default flavor to use for the EC2 API only.
May  9 23:35:11 cmp02 salt-minion[2824]: +# The Nova API does not support a default flavor.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason: The EC2 API is deprecated.
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_flavor=m1.small
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Default pool for floating IPs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies the default floating IP pool for allocating floating
May  9 23:35:11 cmp02 salt-minion[2824]: +# IPs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# While allocating a floating ip, users can optionally pass in the name of the
May  9 23:35:11 cmp02 salt-minion[2824]: +# pool they want to allocate from, otherwise it will be pulled from the
May  9 23:35:11 cmp02 salt-minion[2824]: +# default pool.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If this option is not set, then 'nova' is used as default floating pool.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string representing a floating IP pool name
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_floating_pool=nova
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Autoassigning floating IP to VM
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When set to True, floating IP is auto allocated and associated
May  9 23:35:11 cmp02 salt-minion[2824]: +# to the VM upon creation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron: this options only works with nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#auto_assign_floating_ip=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Full class name for the DNS Manager for floating IPs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies the class of the driver that provides functionality
May  9 23:35:11 cmp02 salt-minion[2824]: +# to manage DNS entries associated with floating IPs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When a user adds a DNS entry for a specified domain to a floating IP,
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova will add a DNS entry using the specified floating DNS driver.
May  9 23:35:11 cmp02 salt-minion[2824]: +# When a floating IP is deallocated, its DNS entry will automatically be
May  9 23:35:11 cmp02 salt-minion[2824]: +# deleted.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Full Python path to the class to be used
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron: this options only works with nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#floating_ip_dns_manager=nova.network.noop_dns_driver.NoopDNSDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Full class name for the DNS Manager for instance IPs.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies the class of the driver that provides functionality
May  9 23:35:11 cmp02 salt-minion[2824]: +# to manage DNS entries for instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# On instance creation, nova will add DNS entries for the instance name and
May  9 23:35:11 cmp02 salt-minion[2824]: +# id, using the specified instance DNS driver and domain. On instance deletion,
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova will remove the DNS entries.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Full Python path to the class to be used
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron: this options only works with nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_dns_manager=nova.network.noop_dns_driver.NoopDNSDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# If specified, Nova checks if the availability_zone of every instance matches
May  9 23:35:11 cmp02 salt-minion[2824]: +# what the database says the availability_zone should be for the specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# dns_domain.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron: this options only works with nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_dns_domain =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Abstracts out IPv6 address generation to pluggable backends.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network can be put into dual-stack mode, so that it uses
May  9 23:35:11 cmp02 salt-minion[2824]: +# both IPv4 and IPv6 addresses. In dual-stack mode, by default, instances
May  9 23:35:11 cmp02 salt-minion[2824]: +# acquire IPv6 global unicast addresses with the help of stateless address
May  9 23:35:11 cmp02 salt-minion[2824]: +# auto-configuration mechanism.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron: this option only works with nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_ipv6: this option only works if ipv6 is enabled for nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: rfc2462, account_identifier
May  9 23:35:11 cmp02 salt-minion[2824]: +#ipv6_backend=rfc2462
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The IP address which the host is using to connect to the management network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * String with valid IP address. Default is IPv4 address of this host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * metadata_host
May  9 23:35:11 cmp02 salt-minion[2824]: +# * my_block_storage_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +# * routing_source_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +# * vpn_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#my_ip=10.89.104.70
May  9 23:35:11 cmp02 salt-minion[2824]: +my_ip=172.16.10.53
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The IP address which is used to connect to the block storage network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * String with valid IP address. Default is IP address of this host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * my_ip - if my_block_storage_ip is not set, then my_ip value is used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#my_block_storage_ip=$my_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Hostname, FQDN or IP address of this host. Must be valid within AMQP key.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * String with hostname, FQDN or IP address. Default is hostname of this host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#host=lcy01-22
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Assign IPv6 and IPv4 addresses when creating instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron: this only works with nova-network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_ipv6=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is a list of full paths to one or more configuration files for
May  9 23:35:11 cmp02 salt-minion[2824]: +# dhcpbridge. In most cases the default path of '/etc/nova/nova-dhcpbridge.conf'
May  9 23:35:11 cmp02 salt-minion[2824]: +# should be sufficient, but if you have special needs for configuring
May  9 23:35:11 cmp02 salt-minion[2824]: +# dhcpbridge,
May  9 23:35:11 cmp02 salt-minion[2824]: +# you can change or add to this list.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     A list of strings, where each string is the full path to a dhcpbridge
May  9 23:35:11 cmp02 salt-minion[2824]: +#     configuration file.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +dhcpbridge_flagfile=/etc/nova/nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The location where the network configuration files will be kept. The default
May  9 23:35:11 cmp02 salt-minion[2824]: +# is
May  9 23:35:11 cmp02 salt-minion[2824]: +# the 'networks' directory off of the location where nova's Python module is
May  9 23:35:11 cmp02 salt-minion[2824]: +# installed.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     A string containing the full path to the desired configuration directory
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#networks_path=$state_path/networks
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the name of the network interface for public IP addresses. The default
May  9 23:35:11 cmp02 salt-minion[2824]: +# is 'eth0'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any string representing a network interface name
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#public_interface=eth0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The location of the binary nova-dhcpbridge. By default it is the binary named
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nova-dhcpbridge' that is installed with all the other nova binaries.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any string representing the full path to the binary for dhcpbridge
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +dhcpbridge=/usr/bin/nova-dhcpbridge
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the public IP address of the network host. It is used when creating a
May  9 23:35:11 cmp02 salt-minion[2824]: +# SNAT rule.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid IP address
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     force_snat_range
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#routing_source_ip=$my_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The lifetime of a DHCP lease, in seconds. The default is 86400 (one day).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any positive integer value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +#dhcp_lease_time=86400
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Despite the singular form of the name of this option, it is actually a list of
May  9 23:35:11 cmp02 salt-minion[2824]: +# zero or more server addresses that dnsmasq will use for DNS nameservers. If
May  9 23:35:11 cmp02 systemd[1]: Reloading.
May  9 23:35:11 cmp02 salt-minion[2824]: +# this is not empty, dnsmasq will not read /etc/resolv.conf, but will only use
May  9 23:35:11 cmp02 salt-minion[2824]: +# the servers specified in this option. If the option use_network_dns_servers is
May  9 23:35:11 cmp02 salt-minion[2824]: +# True, the dns1 and dns2 servers from the network will be appended to this
May  9 23:35:11 cmp02 salt-minion[2824]: +# list,
May  9 23:35:11 cmp02 salt-minion[2824]: +# and will be used as DNS servers, too.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     A list of strings, where each string is either an IP address or a FQDN.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     use_network_dns_servers
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +#dns_server =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When this option is set to True, the dns1 and dns2 servers for the network
May  9 23:35:11 cmp02 salt-minion[2824]: +# specified by the user on boot will be used for DNS, as well as any specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# in
May  9 23:35:11 cmp02 salt-minion[2824]: +# the `dns_server` option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     dns_server
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_network_dns_servers=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is a list of zero or more IP address ranges in your network's DMZ
May  9 23:35:11 cmp02 salt-minion[2824]: +# that should be accepted.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     A list of strings, each of which should be a valid CIDR.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#dmz_cidr =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is a list of zero or more IP ranges that traffic from the
May  9 23:35:11 cmp02 salt-minion[2824]: +# `routing_source_ip` will be SNATted to. If the list is empty, then no SNAT
May  9 23:35:11 cmp02 salt-minion[2824]: +# rules are created.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     A list of strings, each of which should be a valid CIDR.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     routing_source_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +#force_snat_range =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The path to the custom dnsmasq configuration file, if any.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     The full path to the configuration file, or an empty string if there is no
May  9 23:35:11 cmp02 salt-minion[2824]: +#     custom dnsmasq configuration file.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#dnsmasq_config_file =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the class used as the ethernet device driver for linuxnet bridge
May  9 23:35:11 cmp02 salt-minion[2824]: +# operations. The default value should be all you need for most cases, but if
May  9 23:35:11 cmp02 salt-minion[2824]: +# you
May  9 23:35:11 cmp02 salt-minion[2824]: +# wish to use a customized class, set this option to the full dot-separated
May  9 23:35:11 cmp02 salt-minion[2824]: +# import path for that class.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any string representing a dot-separated class path that Nova can import.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#linuxnet_interface_driver=nova.network.linux_net.LinuxBridgeInterfaceDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The name of the Open vSwitch bridge that is used with linuxnet when connecting
May  9 23:35:11 cmp02 salt-minion[2824]: +# with Open vSwitch."
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any string representing a valid bridge name.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#linuxnet_ovs_integration_bridge=br-int
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When True, when a device starts up, and upon binding floating IP addresses,
May  9 23:35:11 cmp02 salt-minion[2824]: +# arp
May  9 23:35:11 cmp02 salt-minion[2824]: +# messages will be sent to ensure that the arp caches on the compute hosts are
May  9 23:35:11 cmp02 salt-minion[2824]: +# up-to-date.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     send_arp_for_ha_count
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#send_arp_for_ha=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When arp messages are configured to be sent, they will be sent with the count
May  9 23:35:11 cmp02 salt-minion[2824]: +# set to the value of this option. Of course, if this is set to zero, no arp
May  9 23:35:11 cmp02 salt-minion[2824]: +# messages will be sent.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any integer greater than or equal to 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     send_arp_for_ha
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#send_arp_for_ha_count=3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When set to True, only the firt nic of a VM will get its default gateway from
May  9 23:35:11 cmp02 salt-minion[2824]: +# the DHCP server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_single_default_gateway=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# One or more interfaces that bridges can forward traffic to. If any of the
May  9 23:35:11 cmp02 salt-minion[2824]: +# items
May  9 23:35:11 cmp02 salt-minion[2824]: +# in this list is the special keyword 'all', then all traffic will be forwarded.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     A list of zero or more interface names, or the word 'all'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +#forward_bridge_interface=all
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the IP address for the network metadata API server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#    * Any valid IP address. The default is the address of the Nova API server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * metadata_port
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#metadata_host=$my_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the port used for the metadata API server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * metadata_host
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:11 cmp02 salt-minion[2824]: +#metadata_port=8775
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This expression, if defined, will select any matching iptables rules and place
May  9 23:35:11 cmp02 salt-minion[2824]: +# them at the top when applying metadata changes to the rules.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * Any string representing a valid regular expression, or an empty string
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * iptables_bottom_regex
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#iptables_top_regex =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This expression, if defined, will select any matching iptables rules and place
May  9 23:35:11 cmp02 salt-minion[2824]: +# them at the bottom when applying metadata changes to the rules.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * Any string representing a valid regular expression, or an empty string
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * iptables_top_regex
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#iptables_bottom_regex =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# By default, packets that do not pass the firewall are DROPped. In many cases,
May  9 23:35:11 cmp02 salt-minion[2824]: +# though, an operator may find it more useful to change this from DROP to
May  9 23:35:11 cmp02 salt-minion[2824]: +# REJECT,
May  9 23:35:11 cmp02 salt-minion[2824]: +# so that the user issuing those packets may have a better idea as to what's
May  9 23:35:11 cmp02 salt-minion[2824]: +# going on, or LOGDROP in order to record the blocked traffic before DROPping.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * A string representing an iptables chain. The default is DROP.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#iptables_drop_action=DROP
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option represents the period of time, in seconds, that the ovs_vsctl
May  9 23:35:11 cmp02 salt-minion[2824]: +# calls
May  9 23:35:11 cmp02 salt-minion[2824]: +# will wait for a response from the database before timing out. A setting of 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# means that the utility should wait forever for a response.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * Any positive integer if a limited timeout is desired, or zero if the
May  9 23:35:11 cmp02 salt-minion[2824]: +#     calls should wait forever for a response.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#ovs_vsctl_timeout=120
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is used mainly in testing to avoid calls to the underlying network
May  9 23:35:11 cmp02 salt-minion[2824]: +# utilities.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#fake_network=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the number of times to retry ebtables commands before
May  9 23:35:11 cmp02 salt-minion[2824]: +# giving up. The minimum number of retries is 1.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * Any positive integer
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * ebtables_retry_interval
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +#ebtables_exec_attempts=3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the time, in seconds, that the system will sleep in
May  9 23:35:11 cmp02 salt-minion[2824]: +# between ebtables retries. Note that each successive retry waits a multiple of
May  9 23:35:11 cmp02 salt-minion[2824]: +# this value, so for example, if this is set to the default of 1.0 seconds, and
May  9 23:35:11 cmp02 salt-minion[2824]: +# ebtables_exec_attempts is 4, after the first failure, the system will sleep
May  9 23:35:11 cmp02 salt-minion[2824]: +# for
May  9 23:35:11 cmp02 salt-minion[2824]: +# 1 * 1.0 seconds, after the second failure it will sleep 2 * 1.0 seconds, and
May  9 23:35:11 cmp02 salt-minion[2824]: +# after the third failure it will sleep 3 * 1.0 seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * Any non-negative float or integer. Setting this to zero will result in
May  9 23:35:11 cmp02 salt-minion[2824]: +# no
May  9 23:35:11 cmp02 salt-minion[2824]: +#     waiting between attempts.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * ebtables_exec_attempts
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ebtables_retry_interval=1.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines whether the network setup information is injected into
May  9 23:35:11 cmp02 salt-minion[2824]: +# the VM before it is booted. While it was originally designed to be used only
May  9 23:35:11 cmp02 salt-minion[2824]: +# by
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network, it is also used by the vmware and xenapi virt drivers to control
May  9 23:35:11 cmp02 salt-minion[2824]: +# whether network information is injected into a VM.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#flat_injected=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the bridge used for simple network interfaces when no
May  9 23:35:11 cmp02 salt-minion[2824]: +# bridge is specified in the VM creation request.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any string representing a valid network bridge, such as 'br100'
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#flat_network_bridge=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the address of the DNS server for a simple network. If this option is
May  9 23:35:11 cmp02 salt-minion[2824]: +# not specified, the default of '8.8.4.4' is used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid IP address.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#flat_network_dns=8.8.4.4
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is the name of the virtual interface of the VM on which the bridge
May  9 23:35:11 cmp02 salt-minion[2824]: +# will be built. While it was originally designed to be used only by
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network, it is also used by libvirt for the bridge interface name.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid virtual interface name, such as 'eth0'
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#flat_interface=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the VLAN number used for private networks. Note that the when creating
May  9 23:35:11 cmp02 salt-minion[2824]: +# the networks, if the specified number has already been assigned, nova-network
May  9 23:35:11 cmp02 salt-minion[2824]: +# will increment this number until it finds an available VLAN.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment. It also will be ignored if the configuration
May  9 23:35:11 cmp02 salt-minion[2824]: +# option
May  9 23:35:11 cmp02 salt-minion[2824]: +# for `network_manager` is not set to the default of
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nova.network.manager.VlanManager'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any integer between 1 and 4094. Values outside of that range will raise a
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ValueError exception. Default = 100.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``network_manager``, ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum value: 4094
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#vlan_start=100
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is the name of the virtual interface of the VM on which the VLAN
May  9 23:35:11 cmp02 salt-minion[2824]: +# bridge will be built. While it was originally designed to be used only by
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network, it is also used by libvirt and xenapi for the bridge interface
May  9 23:35:11 cmp02 salt-minion[2824]: +# name.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this setting will be ignored in nova-network if the
May  9 23:35:11 cmp02 salt-minion[2824]: +# configuration option for `network_manager` is not set to the default of
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nova.network.manager.VlanManager'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid virtual interface name, such as 'eth0'
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options. While
May  9 23:35:11 cmp02 salt-minion[2824]: +# this option has an effect when using neutron, it incorrectly override the
May  9 23:35:11 cmp02 salt-minion[2824]: +# value
May  9 23:35:11 cmp02 salt-minion[2824]: +# provided by neutron and should therefore not be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#vlan_interface=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option represents the number of networks to create if not explicitly
May  9 23:35:11 cmp02 salt-minion[2824]: +# specified when the network is created. The only time this is used is if a CIDR
May  9 23:35:11 cmp02 salt-minion[2824]: +# is specified, but an explicit network_size is not. In that case, the subnets
May  9 23:35:11 cmp02 salt-minion[2824]: +# are created by diving the IP address space of the CIDR by num_networks. The
May  9 23:35:11 cmp02 salt-minion[2824]: +# resulting subnet sizes cannot be larger than the configuration option
May  9 23:35:11 cmp02 salt-minion[2824]: +# `network_size`; in that event, they are reduced to `network_size`, and a
May  9 23:35:11 cmp02 salt-minion[2824]: +# warning is logged.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any positive integer is technically valid, although there are practical
May  9 23:35:11 cmp02 salt-minion[2824]: +#     limits based upon available IP address space and virtual interfaces. The
May  9 23:35:11 cmp02 salt-minion[2824]: +#     default is 1.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``network_size``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#num_networks=1
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the public IP address for the cloudpipe VPN servers. It defaults to
May  9 23:35:11 cmp02 salt-minion[2824]: +# the
May  9 23:35:11 cmp02 salt-minion[2824]: +# IP address of the host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment. It also will be ignored if the configuration
May  9 23:35:11 cmp02 salt-minion[2824]: +# option
May  9 23:35:11 cmp02 salt-minion[2824]: +# for `network_manager` is not set to the default of
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nova.network.manager.VlanManager'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid IP address. The default is $my_ip, the IP address of the VM.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``network_manager``, ``use_neutron``, ``vpn_start``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#vpn_ip=$my_ip
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the port number to use as the first VPN port for private networks.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment. It also will be ignored if the configuration
May  9 23:35:11 cmp02 salt-minion[2824]: +# option
May  9 23:35:11 cmp02 salt-minion[2824]: +# for `network_manager` is not set to the default of
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nova.network.manager.VlanManager', or if you specify a value the 'vpn_start'
May  9 23:35:11 cmp02 salt-minion[2824]: +# parameter when creating a network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any integer representing a valid port number. The default is 1000.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``vpn_ip``, ``network_manager``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#vpn_start=1000
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the number of addresses in each private subnet.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any positive integer that is less than or equal to the available network
May  9 23:35:11 cmp02 salt-minion[2824]: +#     size. Note that if you are creating multiple networks, they must all fit
May  9 23:35:11 cmp02 salt-minion[2824]: +# in
May  9 23:35:11 cmp02 salt-minion[2824]: +#     the available IP address space. The default is 256.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``num_networks``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#network_size=256
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the fixed IPv6 address block when creating a network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid IPv6 CIDR. The default value is "fd00::/48".
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#fixed_range_v6=fd00::/48
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the default IPv4 gateway. It is used only in the testing suite.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid IP address.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``gateway_v6``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#gateway=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the default IPv6 gateway. It is used only in the testing suite.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Please note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any valid IP address.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``gateway``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#gateway_v6=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option represents the number of IP addresses to reserve at the top of the
May  9 23:35:11 cmp02 salt-minion[2824]: +# address range for VPN clients. It also will be ignored if the configuration
May  9 23:35:11 cmp02 salt-minion[2824]: +# option for `network_manager` is not set to the default of
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'nova.network.manager.VlanManager'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any integer, 0 or greater. The default is 0.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``network_manager``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#cnt_vpn_clients=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the number of seconds to wait before disassociating a deallocated
May  9 23:35:11 cmp02 salt-minion[2824]: +# fixed
May  9 23:35:11 cmp02 salt-minion[2824]: +# IP address. This is only used with the nova-network service, and has no effect
May  9 23:35:11 cmp02 salt-minion[2824]: +# when using neutron for networking.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any integer, zero or greater. The default is 600 (10 minutes).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#fixed_ip_disassociate_timeout=600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines how many times nova-network will attempt to create a
May  9 23:35:11 cmp02 salt-minion[2824]: +# unique MAC address before giving up and raising a
May  9 23:35:11 cmp02 salt-minion[2824]: +# `VirtualInterfaceMacAddressException` error.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any positive integer. The default is 5.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#create_unique_mac_address_attempts=5
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Determines whether unused gateway devices, both VLAN and bridge, are deleted
May  9 23:35:11 cmp02 salt-minion[2824]: +# if
May  9 23:35:11 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:35:11 cmp02 salt-minion[2824]: +# the network is in nova-network VLAN mode and is multi-hosted.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``, ``vpn_ip``, ``fake_network``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#teardown_unused_network_gateway=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# When this option is True, a call is made to release the DHCP for the instance
May  9 23:35:11 cmp02 salt-minion[2824]: +# when that instance is terminated.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +force_dhcp_release=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# When this option is True, whenever a DNS entry must be updated, a fanout cast
May  9 23:35:11 cmp02 salt-minion[2824]: +# message is sent to all network hosts to update their DNS entries in multi-host
May  9 23:35:11 cmp02 salt-minion[2824]: +# mode.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#update_dns_entries=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option determines the time, in seconds, to wait between refreshing DNS
May  9 23:35:11 cmp02 salt-minion[2824]: +# entries for the network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Either -1 (default), or any positive integer. A negative value will
May  9 23:35:11 cmp02 salt-minion[2824]: +# disable
May  9 23:35:11 cmp02 salt-minion[2824]: +#     the updates.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#dns_update_periodic_interval=-1
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option allows you to specify the domain for the DHCP server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any string that is a valid domain name.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#dhcp_domain=novalocal
May  9 23:35:11 cmp02 salt-minion[2824]: +dhcp_domain=novalocal
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option allows you to specify the L3 management library to be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     Any dot-separated string that represents the import path to an L3
May  9 23:35:11 cmp02 salt-minion[2824]: +#     networking library.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     ``use_neutron``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#l3_lib=nova.network.l3.LinuxNetL3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# THIS VALUE SHOULD BE SET WHEN CREATING THE NETWORK.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If True in multi_host mode, all compute hosts share the same dhcp address. The
May  9 23:35:11 cmp02 salt-minion[2824]: +# same IP address used for DHCP will be added on each nova-network node which is
May  9 23:35:11 cmp02 salt-minion[2824]: +# only visible to the VMs on the same host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The use of this configuration has been deprecated and may be removed in any
May  9 23:35:11 cmp02 salt-minion[2824]: +# release after Mitaka. It is recommended that instead of relying on this
May  9 23:35:11 cmp02 salt-minion[2824]: +# option,
May  9 23:35:11 cmp02 salt-minion[2824]: +# an explicit value should be passed to 'create_networks()' as a keyword
May  9 23:35:11 cmp02 salt-minion[2824]: +# argument
May  9 23:35:11 cmp02 salt-minion[2824]: +# with the name 'share_address'.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 2014.2.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +#share_dhcp_address=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED: Whether to use Neutron or Nova Network as the back end for
May  9 23:35:11 cmp02 salt-minion[2824]: +# networking. Defaults to False (indicating Nova network).Set to True to use
May  9 23:35:11 cmp02 salt-minion[2824]: +# neutron. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_neutron=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# URL for LDAP server which will store DNS entries
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A valid LDAP URL representing the server
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (uri value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_url=ldap://ldap.example.com:389
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Bind user for LDAP server (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_user=uid=admin,ou=people,dc=example,dc=org
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Bind user's password for LDAP server (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_password=password
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Hostmaster for LDAP DNS driver Statement of Authority
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid string representing LDAP DNS hostmaster.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_soa_hostmaster=hostmaster@example.org
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# DNS Servers for LDAP DNS driver
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * A valid URL representing a DNS server
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_servers=dns.example.org
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Base distinguished name for the LDAP search query
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option helps to decide where to look up the host in LDAP.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_base_dn=ou=hosts,dc=example,dc=org
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Refresh interval (in seconds) for LDAP DNS driver Start of Authority
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time interval, a secondary/slave DNS server waits before requesting for
May  9 23:35:11 cmp02 salt-minion[2824]: +# primary DNS server's current SOA record. If the records are different,
May  9 23:35:11 cmp02 salt-minion[2824]: +# secondary DNS server will request a zone transfer from primary.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# NOTE: Lower values would cause more traffic.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_soa_refresh=1800
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Retry interval (in seconds) for LDAP DNS driver Start of Authority
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time interval, a secondary/slave DNS server should wait, if an
May  9 23:35:11 cmp02 salt-minion[2824]: +# attempt to transfer zone failed during the previous refresh interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_soa_retry=3600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Expiry interval (in seconds) for LDAP DNS driver Start of Authority
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Time interval, a secondary/slave DNS server holds the information
May  9 23:35:11 cmp02 salt-minion[2824]: +# before it is no longer considered authoritative.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_soa_expiry=86400
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum interval (in seconds) for LDAP DNS driver Start of Authority
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# It is Minimum time-to-live applies for all resource records in the
May  9 23:35:11 cmp02 salt-minion[2824]: +# zone file. This value is supplied to other servers how long they
May  9 23:35:11 cmp02 salt-minion[2824]: +# should keep the data in cache.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ldap_dns_soa_minimum=7200
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED: The topic network nodes listen on (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# There is no need to let users choose the RPC topic for all services - there
May  9 23:35:11 cmp02 salt-minion[2824]: +# is little gain from this. Furthermore, it makes it really easy to break Nova
May  9 23:35:11 cmp02 salt-minion[2824]: +# by using this option.
May  9 23:35:11 cmp02 salt-minion[2824]: +#network_topic=network
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Default value for multi_host in networks.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network service can operate in a multi-host or single-host mode.
May  9 23:35:11 cmp02 salt-minion[2824]: +# In multi-host mode each compute node runs a copy of nova-network and the
May  9 23:35:11 cmp02 salt-minion[2824]: +# instances on that compute node use the compute node as a gateway to the
May  9 23:35:11 cmp02 salt-minion[2824]: +# Internet. Where as in single-host mode, a central server runs the nova-network
May  9 23:35:11 cmp02 salt-minion[2824]: +# service. All compute nodes forward traffic from the instances to the
May  9 23:35:11 cmp02 salt-minion[2824]: +# cloud controller which then forwards traffic to the Internet.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If this options is set to true, some rpc network calls will be sent directly
May  9 23:35:11 cmp02 salt-minion[2824]: +# to host.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note that this option is only used when using nova-network instead of
May  9 23:35:11 cmp02 salt-minion[2824]: +# Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#multi_host=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Driver to use for network creation.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Network driver initializes (creates bridges and so on) only when the
May  9 23:35:11 cmp02 salt-minion[2824]: +# first VM lands on a host node. All network managers configure the
May  9 23:35:11 cmp02 salt-minion[2824]: +# network using network drivers. The driver is not tied to any particular
May  9 23:35:11 cmp02 salt-minion[2824]: +# network manager.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The default Linux driver implements vlans, bridges, and iptables rules
May  9 23:35:11 cmp02 salt-minion[2824]: +# using linux utilities.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note that this option is only used when using nova-network instead
May  9 23:35:11 cmp02 salt-minion[2824]: +# of Neutron in your deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * use_neutron
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:11 cmp02 salt-minion[2824]: +#network_driver=nova.network.linux_net
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Firewall driver to use with ``nova-network`` service.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option only applies when using the ``nova-network`` service. When using
May  9 23:35:11 cmp02 salt-minion[2824]: +# another networking services, such as Neutron, this should be to set to the
May  9 23:35:11 cmp02 salt-minion[2824]: +# ``nova.virt.firewall.NoopFirewallDriver``.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If unset (the default), this will default to the hypervisor-specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# default driver.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * nova.virt.firewall.IptablesFirewallDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +# * nova.virt.firewall.NoopFirewallDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +# * nova.virt.libvirt.firewall.IptablesFirewallDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +# * [...]
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``use_neutron``: This must be set to ``False`` to enable ``nova-network``
May  9 23:35:11 cmp02 salt-minion[2824]: +#   networking
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#firewall_driver=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +firewall_driver = nova.virt.firewall.NoopFirewallDriver
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Determine whether to allow network traffic from same network.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When set to true, hosts on the same subnet are not filtered and are allowed
May  9 23:35:11 cmp02 salt-minion[2824]: +# to pass all types of traffic between them. On a flat network, this allows
May  9 23:35:11 cmp02 salt-minion[2824]: +# all instances from all projects unfiltered communication. With VLAN
May  9 23:35:11 cmp02 salt-minion[2824]: +# networking, this allows access between instances within the same project.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option only applies when using the ``nova-network`` service. When using
May  9 23:35:11 cmp02 salt-minion[2824]: +# another networking services, such as Neutron, security groups or other
May  9 23:35:11 cmp02 salt-minion[2824]: +# approaches should be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * True: Network traffic should be allowed pass between all instances on the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   same network, regardless of their tenant and security policies
May  9 23:35:11 cmp02 salt-minion[2824]: +# * False: Network traffic should not be allowed pass between instances unless
May  9 23:35:11 cmp02 salt-minion[2824]: +#   it is unblocked in a security group
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``use_neutron``: This must be set to ``False`` to enable ``nova-network``
May  9 23:35:11 cmp02 salt-minion[2824]: +#   networking
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``firewall_driver``: This must be set to
May  9 23:35:11 cmp02 salt-minion[2824]: +#   ``nova.virt.libvirt.firewall.IptablesFirewallDriver`` to ensure the
May  9 23:35:11 cmp02 salt-minion[2824]: +#   libvirt firewall driver is enabled.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#allow_same_net_traffic=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Filename that will be used for storing websocket frames received
May  9 23:35:11 cmp02 salt-minion[2824]: +# and sent by a proxy service (like VNC, spice, serial) running on this host.
May  9 23:35:11 cmp02 salt-minion[2824]: +# If this is not set, no recording will be done.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#record=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Run as a background process. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#daemon=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Disallow non-encrypted connections. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ssl_only=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Set to True if source host is addressed with IPv6. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#source_is_ipv6=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Path to SSL certificate file. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#cert=self.pem
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# SSL key file (if separate from cert). (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#key=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Path to directory with content which will be served by a web server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#web=/usr/share/spice-html5
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The directory where the Nova python modules are installed.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This directory is used to store template files for networking and remote
May  9 23:35:11 cmp02 salt-minion[2824]: +# console access. It is also the default path for other config options which
May  9 23:35:11 cmp02 salt-minion[2824]: +# need to persist Nova internal data. It is very unlikely that you need to
May  9 23:35:11 cmp02 salt-minion[2824]: +# change this option from its default value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * The full path to a directory.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * ``state_path``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#pybasedir=/build/nova-elxmSs/nova-15.0.2
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The directory where the Nova binaries are installed.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is only relevant if the networking capabilities from Nova are
May  9 23:35:11 cmp02 salt-minion[2824]: +# used (see services below). Nova's networking capabilities are targeted to
May  9 23:35:11 cmp02 salt-minion[2824]: +# be fully replaced by Neutron in the future. It is very unlikely that you need
May  9 23:35:11 cmp02 salt-minion[2824]: +# to change this option from its default value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * The full path to a directory.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#bindir=/usr/local/bin
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The top-level directory for maintaining Nova's state.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This directory is used to store Nova's internal state. It is used by a
May  9 23:35:11 cmp02 salt-minion[2824]: +# variety of other config options which derive from this. In some scenarios
May  9 23:35:11 cmp02 salt-minion[2824]: +# (for example migrations) it makes sense to use a storage location which is
May  9 23:35:11 cmp02 salt-minion[2824]: +# shared between multiple compute hosts (for example via NFS). Unless the
May  9 23:35:11 cmp02 salt-minion[2824]: +# option ``instances_path`` gets overwritten, this directory can grow very
May  9 23:35:11 cmp02 salt-minion[2824]: +# large.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * The full path to a directory. Defaults to value provided in ``pybasedir``.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +state_path=/var/lib/nova
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds indicating how frequently the state of services on a
May  9 23:35:11 cmp02 salt-minion[2824]: +# given hypervisor is reported. Nova needs to know this to determine the
May  9 23:35:11 cmp02 salt-minion[2824]: +# overall health of the deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related Options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * service_down_time
May  9 23:35:11 cmp02 salt-minion[2824]: +#   report_interval should be less than service_down_time. If service_down_time
May  9 23:35:11 cmp02 salt-minion[2824]: +#   is less than report_interval, services will routinely be considered down,
May  9 23:35:11 cmp02 salt-minion[2824]: +#   because they report in too rarely.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#report_interval=10
May  9 23:35:11 cmp02 salt-minion[2824]: +report_interval = 60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum time in seconds since last check-in for up service
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Each compute node periodically updates their database status based on the
May  9 23:35:11 cmp02 salt-minion[2824]: +# specified report interval. If the compute node hasn't updated the status
May  9 23:35:11 cmp02 salt-minion[2824]: +# for more than service_down_time, then the compute node is considered down.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related Options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * report_interval (service_down_time should not be less than report_interval)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#service_down_time=60
May  9 23:35:11 cmp02 salt-minion[2824]: +service_down_time=90
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Enable periodic tasks.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If set to true, this option allows services to periodically run tasks
May  9 23:35:11 cmp02 salt-minion[2824]: +# on the manager.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# In case of running multiple schedulers or conductors you may want to run
May  9 23:35:11 cmp02 salt-minion[2824]: +# periodic tasks on only one host - in this case disable this option for all
May  9 23:35:11 cmp02 salt-minion[2824]: +# hosts but one.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#periodic_enable=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds to randomly delay when starting the periodic task
May  9 23:35:11 cmp02 salt-minion[2824]: +# scheduler to reduce stampeding.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When compute workers are restarted in unison across a cluster,
May  9 23:35:11 cmp02 salt-minion[2824]: +# they all end up running the periodic tasks at the same time
May  9 23:35:11 cmp02 salt-minion[2824]: +# causing problems for the external services. To mitigate this
May  9 23:35:11 cmp02 salt-minion[2824]: +# behavior, periodic_fuzzy_delay option allows you to introduce a
May  9 23:35:11 cmp02 salt-minion[2824]: +# random initial delay when starting the periodic task scheduler.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer (in seconds)
May  9 23:35:11 cmp02 salt-minion[2824]: +# * 0 : disable the random delay
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#periodic_fuzzy_delay=60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# List of APIs to be enabled by default. (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +enabled_apis=osapi_compute,metadata
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# List of APIs with enabled SSL.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Nova provides SSL support for the API servers. enabled_ssl_apis option
May  9 23:35:11 cmp02 salt-minion[2824]: +# allows configuring the SSL support.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#enabled_ssl_apis =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# IP address on which the OpenStack API will listen.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The OpenStack API service listens on this IP address for incoming
May  9 23:35:11 cmp02 salt-minion[2824]: +# requests.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#osapi_compute_listen=0.0.0.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Port on which the OpenStack API will listen.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The OpenStack API service listens on this port number for incoming
May  9 23:35:11 cmp02 salt-minion[2824]: +# requests.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:11 cmp02 salt-minion[2824]: +#osapi_compute_listen_port=8774
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of workers for OpenStack API service. The default will be the number
May  9 23:35:11 cmp02 salt-minion[2824]: +# of CPUs available.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# OpenStack API services can be configured to run as multi-process (workers).
May  9 23:35:11 cmp02 salt-minion[2824]: +# This overcomes the problem of reduction in throughput when API request
May  9 23:35:11 cmp02 salt-minion[2824]: +# concurrency increases. OpenStack API service will run in the specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# number of processes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer
May  9 23:35:11 cmp02 salt-minion[2824]: +# * None (default value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +#osapi_compute_workers=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# IP address on which the metadata API will listen.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The metadata API service listens on this IP address for incoming
May  9 23:35:11 cmp02 salt-minion[2824]: +# requests.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#metadata_listen=0.0.0.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Port on which the metadata API will listen.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The metadata API service listens on this port number for incoming
May  9 23:35:11 cmp02 salt-minion[2824]: +# requests.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:11 cmp02 salt-minion[2824]: +#metadata_listen_port=8775
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of workers for metadata service. If not specified the number of
May  9 23:35:11 cmp02 salt-minion[2824]: +# available CPUs will be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The metadata service can be configured to run as multi-process (workers).
May  9 23:35:11 cmp02 salt-minion[2824]: +# This overcomes the problem of reduction in throughput when API request
May  9 23:35:11 cmp02 salt-minion[2824]: +# concurrency increases. The metadata service will run in the specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# number of processes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any positive integer
May  9 23:35:11 cmp02 salt-minion[2824]: +# * None (default value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]: +#metadata_workers=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Full class name for the Manager for network (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: nova.network.manager.FlatManager, nova.network.manager.FlatDHCPManager, nova.network.manager.VlanManager
May  9 23:35:11 cmp02 salt-minion[2824]: +#network_manager=nova.network.manager.VlanManager
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option specifies the driver to be used for the servicegroup service.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# ServiceGroup API in nova enables checking status of a compute node. When a
May  9 23:35:11 cmp02 salt-minion[2824]: +# compute worker running the nova-compute daemon starts, it calls the join API
May  9 23:35:11 cmp02 salt-minion[2824]: +# to join the compute group. Services like nova scheduler can query the
May  9 23:35:11 cmp02 salt-minion[2824]: +# ServiceGroup API to check if a node is alive. Internally, the ServiceGroup
May  9 23:35:11 cmp02 salt-minion[2824]: +# client driver automatically updates the compute worker status. There are
May  9 23:35:11 cmp02 salt-minion[2824]: +# multiple backend implementations for this service: Database ServiceGroup
May  9 23:35:11 cmp02 salt-minion[2824]: +# driver
May  9 23:35:11 cmp02 salt-minion[2824]: +# and Memcache ServiceGroup driver.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * db : Database ServiceGroup driver
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * mc : Memcache ServiceGroup driver
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related Options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     * service_down_time (maximum time since last check-in for up service)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: db, mc
May  9 23:35:11 cmp02 salt-minion[2824]: +#servicegroup_driver=db
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  #
May  9 23:35:11 cmp02 salt-minion[2824]:  # From oslo.log
May  9 23:35:11 cmp02 salt-minion[2824]: @@ -7,7 +2785,15 @@
May  9 23:35:11 cmp02 salt-minion[2824]:  # If set to true, the logging level will be set to DEBUG instead of the default
May  9 23:35:11 cmp02 salt-minion[2824]:  # INFO level. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Note: This option can be changed without restarting.
May  9 23:35:11 cmp02 salt-minion[2824]: -#debug = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#debug=false
May  9 23:35:11 cmp02 salt-minion[2824]: +debug=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED: If set to false, the logging level will be set to WARNING instead
May  9 23:35:11 cmp02 salt-minion[2824]: +# of the default INFO level. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +#verbose=true
May  9 23:35:11 cmp02 salt-minion[2824]: +verbose=true
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The name of a logging configuration file. This file is appended to any
May  9 23:35:11 cmp02 salt-minion[2824]:  # existing logging configuration files. For details about logging configuration
May  9 23:35:11 cmp02 salt-minion[2824]: @@ -17,131 +2803,132 @@
May  9 23:35:11 cmp02 salt-minion[2824]:  # example, logging_context_format_string). (string value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Note: This option can be changed without restarting.
May  9 23:35:11 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/log_config
May  9 23:35:11 cmp02 salt-minion[2824]: -#log_config_append = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +#log_config_append=<None>
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Defines the format string for %%(asctime)s in log records. Default:
May  9 23:35:11 cmp02 salt-minion[2824]:  # %(default)s . This option is ignored if log_config_append is set. (string
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#log_date_format = %Y-%m-%d %H:%M:%S
May  9 23:35:11 cmp02 salt-minion[2824]: +#log_date_format=%Y-%m-%d %H:%M:%S
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # (Optional) Name of log file to send logging output to. If no default is set,
May  9 23:35:11 cmp02 salt-minion[2824]:  # logging will go to stderr as defined by use_stderr. This option is ignored if
May  9 23:35:11 cmp02 salt-minion[2824]:  # log_config_append is set. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/logfile
May  9 23:35:11 cmp02 salt-minion[2824]: -#log_file = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +#log_file=<None>
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # (Optional) The base directory used for relative log_file  paths. This option
May  9 23:35:11 cmp02 salt-minion[2824]:  # is ignored if log_config_append is set. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/logdir
May  9 23:35:11 cmp02 salt-minion[2824]: -#log_dir = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +log_dir=/var/log/nova
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Uses logging handler designed to watch file system. When log file is moved or
May  9 23:35:11 cmp02 salt-minion[2824]:  # removed this handler will open a new log file with specified path
May  9 23:35:11 cmp02 salt-minion[2824]:  # instantaneously. It makes sense only if log_file option is specified and Linux
May  9 23:35:11 cmp02 salt-minion[2824]:  # platform is used. This option is ignored if log_config_append is set. (boolean
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#watch_log_file = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#watch_log_file=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Use syslog for logging. Existing syslog format is DEPRECATED and will be
May  9 23:35:11 cmp02 salt-minion[2824]:  # changed later to honor RFC5424. This option is ignored if log_config_append is
May  9 23:35:11 cmp02 salt-minion[2824]:  # set. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#use_syslog = false
May  9 23:35:11 cmp02 salt-minion[2824]: -
May  9 23:35:11 cmp02 salt-minion[2824]: -# Enable journald for logging. If running in a systemd environment you may wish
May  9 23:35:11 cmp02 salt-minion[2824]: -# to enable journal support. Doing so will use the journal native protocol which
May  9 23:35:11 cmp02 salt-minion[2824]: -# includes structured metadata in addition to log messages.This option is
May  9 23:35:11 cmp02 salt-minion[2824]: -# ignored if log_config_append is set. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#use_journal = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_syslog=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Syslog facility to receive log lines. This option is ignored if
May  9 23:35:11 cmp02 salt-minion[2824]:  # log_config_append is set. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#syslog_log_facility = LOG_USER
May  9 23:35:11 cmp02 salt-minion[2824]: +#syslog_log_facility=LOG_USER
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Log output to standard error. This option is ignored if log_config_append is
May  9 23:35:11 cmp02 salt-minion[2824]:  # set. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#use_stderr = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_stderr=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Format string to use for log messages with context. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s
May  9 23:35:11 cmp02 salt-minion[2824]: +#logging_context_format_string=%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Format string to use for log messages when context is undefined. (string
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s
May  9 23:35:11 cmp02 salt-minion[2824]: +#logging_default_format_string=%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Additional data to append to log message when logging level for the message is
May  9 23:35:11 cmp02 salt-minion[2824]:  # DEBUG. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d
May  9 23:35:11 cmp02 salt-minion[2824]: +#logging_debug_format_suffix=%(funcName)s %(pathname)s:%(lineno)d
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Prefix each line of exception output with this format. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s
May  9 23:35:11 cmp02 salt-minion[2824]: +#logging_exception_prefix=%(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Defines the format string for %(user_identity)s that is used in
May  9 23:35:11 cmp02 salt-minion[2824]:  # logging_context_format_string. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#logging_user_identity_format = %(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)s
May  9 23:35:11 cmp02 salt-minion[2824]: +#logging_user_identity_format=%(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)s
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # List of package logging levels in logger=LEVEL pairs. This option is ignored
May  9 23:35:11 cmp02 salt-minion[2824]:  # if log_config_append is set. (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#default_log_levels = amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=INFO,oslo.messaging=INFO,oslo_messaging=INFO,iso8601=WARN,requests.packages.urllib3.connectionpool=WARN,urllib3.connectionpool=WARN,websocket=WARN,requests.packages.urllib3.util.retry=WARN,urllib3.util.retry=WARN,keystonemiddleware=WARN,routes.middleware=WARN,stevedore=WARN,taskflow=WARN,keystoneauth=WARN,oslo.cache=INFO,dogpile.core.dogpile=INFO
May  9 23:35:11 cmp02 salt-minion[2824]: +#default_log_levels=amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=INFO,oslo.messaging=INFO,iso8601=WARN,requests.packages.urllib3.connectionpool=WARN,urllib3.connectionpool=WARN,websocket=WARN,requests.packages.urllib3.util.retry=WARN,urllib3.util.retry=WARN,keystonemiddleware=WARN,routes.middleware=WARN,stevedore=WARN,taskflow=WARN,keystoneauth=WARN,oslo.cache=INFO,dogpile.core.dogpile=INFO
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Enables or disables publication of error events. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#publish_errors = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#publish_errors=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The format for an instance that is passed with the log message. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#instance_format = "[instance: %(uuid)s] "
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_format="[instance: %(uuid)s] "
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The format for an instance UUID that is passed with the log message. (string
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#instance_uuid_format = "[instance: %(uuid)s] "
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_uuid_format="[instance: %(uuid)s] "
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Interval, number of seconds, of log rate limiting. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rate_limit_interval = 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#rate_limit_interval=0
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Maximum number of logged messages per rate_limit_interval. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rate_limit_burst = 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#rate_limit_burst=0
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG or
May  9 23:35:11 cmp02 salt-minion[2824]:  # empty string. Logs with level greater or equal to rate_limit_except_level are
May  9 23:35:11 cmp02 salt-minion[2824]:  # not filtered. An empty string means that all levels are filtered. (string
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rate_limit_except_level = CRITICAL
May  9 23:35:11 cmp02 salt-minion[2824]: +#rate_limit_except_level=CRITICAL
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Enables or disables fatal status of deprecations. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#fatal_deprecations = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#fatal_deprecations=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  #
May  9 23:35:11 cmp02 salt-minion[2824]:  # From oslo.messaging
May  9 23:35:11 cmp02 salt-minion[2824]:  #
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Size of RPC connection pool. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_conn_pool_size = 30
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_conn_pool_size
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_conn_pool_size=30
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The pool size limit for connections expiration policy (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#conn_pool_min_size = 2
May  9 23:35:11 cmp02 salt-minion[2824]: +#conn_pool_min_size=2
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The time-to-live in sec of idle connections in the pool (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#conn_pool_ttl = 1200
May  9 23:35:11 cmp02 salt-minion[2824]: +#conn_pool_ttl=1200
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP.
May  9 23:35:11 cmp02 salt-minion[2824]:  # The "host" option should point or resolve to this address. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_bind_address = *
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_bind_address
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_bind_address=*
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # MatchMaker driver. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Allowed values: redis, sentinel, dummy
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_matchmaker = redis
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_matchmaker
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_matchmaker=redis
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Number of ZeroMQ contexts, defaults to 1. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_contexts = 1
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_contexts
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_contexts=1
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Maximum number of ingress messages to locally buffer per topic. Default is
May  9 23:35:11 cmp02 salt-minion[2824]:  # unlimited. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_topic_backlog = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_topic_backlog
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_topic_backlog=<None>
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Directory for holding IPC sockets. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_ipc_dir = /var/run/openstack
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_ipc_dir
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_ipc_dir=/var/run/openstack
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Name of this node. Must be a valid hostname, FQDN, or IP address. Must match
May  9 23:35:11 cmp02 salt-minion[2824]:  # "host" option, if running Nova. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_host = localhost
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_host
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_host=localhost
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Number of seconds to wait before all pending messages will be sent after
May  9 23:35:11 cmp02 salt-minion[2824]:  # closing a socket. The default value of -1 specifies an infinite linger period.
May  9 23:35:11 cmp02 salt-minion[2824]: @@ -149,138 +2936,146 @@
May  9 23:35:11 cmp02 salt-minion[2824]:  # immediately when the socket is closed. Positive values specify an upper bound
May  9 23:35:11 cmp02 salt-minion[2824]:  # for the linger period. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/rpc_cast_timeout
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_linger = -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_linger=-1
May  9 23:35:11 cmp02 salt-minion[2824]: +zmq_linger=30
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The default number of seconds that poll should wait. Poll raises timeout
May  9 23:35:11 cmp02 salt-minion[2824]:  # exception when timeout expired. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_poll_timeout = 1
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_poll_timeout
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_poll_timeout=1
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Expiration timeout in seconds of a name service record about existing target (
May  9 23:35:11 cmp02 salt-minion[2824]:  # < 0 means no timeout). (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_target_expire = 300
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/zmq_target_expire
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_target_expire=300
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Update period in seconds of a name service record about existing target.
May  9 23:35:11 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_target_update = 180
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/zmq_target_update
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_target_update=180
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. (boolean
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#use_pub_sub = false
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/use_pub_sub
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_pub_sub=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Use ROUTER remote proxy. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#use_router_proxy = false
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/use_router_proxy
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_router_proxy=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # This option makes direct connections dynamic or static. It makes sense only
May  9 23:35:11 cmp02 salt-minion[2824]:  # with use_router_proxy=False which means to use direct connections for direct
May  9 23:35:11 cmp02 salt-minion[2824]:  # message types (ignored otherwise). (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#use_dynamic_connections = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#use_dynamic_connections=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # How many additional connections to a host will be made for failover reasons.
May  9 23:35:11 cmp02 salt-minion[2824]:  # This option is actual only in dynamic connections mode. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_failover_connections = 2
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_failover_connections=2
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Minimal port number for random ports range. (port value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]:  # Maximum value: 65535
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_min_port = 49153
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_min_port
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_min_port=49153
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Maximal port number for random ports range. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:11 cmp02 salt-minion[2824]:  # Maximum value: 65536
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_max_port = 65536
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_max_port
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_max_port=65536
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Number of retries to find free port number before fail with ZMQBindError.
May  9 23:35:11 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_bind_port_retries = 100
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_bind_port_retries
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_bind_port_retries=100
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Default serialization mechanism for serializing/deserializing
May  9 23:35:11 cmp02 salt-minion[2824]:  # outgoing/incoming messages (string value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Allowed values: json, msgpack
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_zmq_serialization = json
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_serialization
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_zmq_serialization=json
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # This option configures round-robin mode in zmq socket. True means not keeping
May  9 23:35:11 cmp02 salt-minion[2824]:  # a queue when server side disconnects. False means to keep queue and messages
May  9 23:35:11 cmp02 salt-minion[2824]:  # even if server is disconnected, when the server appears we send all
May  9 23:35:11 cmp02 salt-minion[2824]:  # accumulated messages to it. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_immediate = true
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_immediate=true
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any
May  9 23:35:11 cmp02 salt-minion[2824]:  # other negative value) means to skip any overrides and leave it to OS default;
May  9 23:35:11 cmp02 salt-minion[2824]:  # 0 and 1 (or any other positive value) mean to disable and enable the option
May  9 23:35:11 cmp02 salt-minion[2824]:  # respectively. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive = -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive=-1
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The duration between two keepalive transmissions in idle condition. The unit
May  9 23:35:11 cmp02 salt-minion[2824]:  # is platform dependent, for example, seconds in Linux, milliseconds in Windows
May  9 23:35:11 cmp02 salt-minion[2824]:  # etc. The default value of -1 (or any other negative value and 0) means to skip
May  9 23:35:11 cmp02 salt-minion[2824]:  # any overrides and leave it to OS default. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_idle = -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive_idle=-1
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The number of retransmissions to be carried out before declaring that remote
May  9 23:35:11 cmp02 salt-minion[2824]:  # end is not available. The default value of -1 (or any other negative value and
May  9 23:35:11 cmp02 salt-minion[2824]:  # 0) means to skip any overrides and leave it to OS default. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_cnt = -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive_cnt=-1
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The duration between two successive keepalive retransmissions, if
May  9 23:35:11 cmp02 salt-minion[2824]:  # acknowledgement to the previous keepalive transmission is not received. The
May  9 23:35:11 cmp02 salt-minion[2824]:  # unit is platform dependent, for example, seconds in Linux, milliseconds in
May  9 23:35:11 cmp02 salt-minion[2824]:  # Windows etc. The default value of -1 (or any other negative value and 0) means
May  9 23:35:11 cmp02 salt-minion[2824]:  # to skip any overrides and leave it to OS default. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_intvl = -1
May  9 23:35:11 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive_intvl=-1
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Maximum number of (green) threads to work concurrently. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_thread_pool_size = 100
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_thread_pool_size=100
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Expiration timeout in seconds of a sent/received message after which it is not
May  9 23:35:11 cmp02 salt-minion[2824]:  # tracked anymore by a client/server. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_message_ttl = 300
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_message_ttl=300
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Wait for message acknowledgements from receivers. This mechanism works only
May  9 23:35:11 cmp02 salt-minion[2824]:  # via proxy without PUB/SUB. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_use_acks = false
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_use_acks=false
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Number of seconds to wait for an ack from a cast/call. After each retry
May  9 23:35:11 cmp02 salt-minion[2824]:  # attempt this timeout is multiplied by some specified multiplier. (integer
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_ack_timeout_base = 15
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_ack_timeout_base=15
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Number to multiply base ack timeout by after each retry attempt. (integer
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_ack_timeout_multiplier = 2
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_ack_timeout_multiplier=2
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Default number of message sending attempts in case of any problems occurred:
May  9 23:35:11 cmp02 salt-minion[2824]:  # positive value N means at most N retries, 0 means no retries, None or -1 (or
May  9 23:35:11 cmp02 salt-minion[2824]:  # any other negative values) mean to retry forever. This option is used only if
May  9 23:35:11 cmp02 salt-minion[2824]:  # acknowledgments are enabled. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_retry_attempts = 3
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_retry_attempts=3
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # List of publisher hosts SubConsumer can subscribe on. This option has higher
May  9 23:35:11 cmp02 salt-minion[2824]:  # priority then the default publishers list taken from the matchmaker. (list
May  9 23:35:11 cmp02 salt-minion[2824]:  # value)
May  9 23:35:11 cmp02 salt-minion[2824]:  #subscribe_on =
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]: -# Size of executor thread pool when executor is threading or eventlet. (integer
May  9 23:35:11 cmp02 salt-minion[2824]: -# value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Size of executor thread pool. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/rpc_thread_pool_size
May  9 23:35:11 cmp02 salt-minion[2824]: -#executor_thread_pool_size = 64
May  9 23:35:11 cmp02 salt-minion[2824]: +#executor_thread_pool_size=64
May  9 23:35:11 cmp02 salt-minion[2824]: +executor_thread_pool_size=70
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Seconds to wait for a response from a call. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_response_timeout = 60
May  9 23:35:11 cmp02 salt-minion[2824]: -
May  9 23:35:11 cmp02 salt-minion[2824]: -# A URL representing the messaging driver to use and its full configuration.
May  9 23:35:11 cmp02 salt-minion[2824]: -# (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#transport_url = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_response_timeout=60
May  9 23:35:11 cmp02 salt-minion[2824]: +rpc_response_timeout = 3600
May  9 23:35:11 cmp02 salt-minion[2824]: +transport_url = rabbit://openstack:opnfv_secret@172.16.10.36:5672//openstack
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # DEPRECATED: The messaging driver to use, defaults to rabbit. Other drivers
May  9 23:35:11 cmp02 salt-minion[2824]:  # include amqp and zmq. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:11 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:11 cmp02 salt-minion[2824]: -#rpc_backend = rabbit
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_backend=rabbit
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # The default exchange under which topics are scoped. May be overridden by an
May  9 23:35:11 cmp02 salt-minion[2824]:  # exchange name specified in the transport_url option. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#control_exchange = openstack
May  9 23:35:11 cmp02 salt-minion[2824]: +#control_exchange=openstack
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  #
May  9 23:35:11 cmp02 salt-minion[2824]:  # From oslo.service.periodic_task
May  9 23:35:11 cmp02 salt-minion[2824]: @@ -288,7 +3083,7 @@
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Some periodic tasks can be run in a separate process. Should we run them here?
May  9 23:35:11 cmp02 salt-minion[2824]:  # (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#run_external_periodic_tasks = true
May  9 23:35:11 cmp02 salt-minion[2824]: +#run_external_periodic_tasks=true
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  #
May  9 23:35:11 cmp02 salt-minion[2824]:  # From oslo.service.service
May  9 23:35:11 cmp02 salt-minion[2824]: @@ -300,21 +3095,1160 @@
May  9 23:35:11 cmp02 salt-minion[2824]:  # is in use); and <start>:<end> results in listening on the smallest unused port
May  9 23:35:11 cmp02 salt-minion[2824]:  # number within the specified range of port numbers.  The chosen port is
May  9 23:35:11 cmp02 salt-minion[2824]:  # displayed in the service's log file. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#backdoor_port = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +#backdoor_port=<None>
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Enable eventlet backdoor, using the provided path as a unix socket that can
May  9 23:35:11 cmp02 salt-minion[2824]:  # receive connections. This option is mutually exclusive with 'backdoor_port' in
May  9 23:35:11 cmp02 salt-minion[2824]:  # that only one should be provided. If both are provided then the existence of
May  9 23:35:11 cmp02 salt-minion[2824]:  # this option overrides the usage of that option. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#backdoor_socket = <None>
May  9 23:35:11 cmp02 salt-minion[2824]: +#backdoor_socket=<None>
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Enables or disables logging values of all registered options when starting a
May  9 23:35:11 cmp02 salt-minion[2824]:  # service (at DEBUG level). (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: -#log_options = true
May  9 23:35:11 cmp02 salt-minion[2824]: +#log_options=true
May  9 23:35:11 cmp02 salt-minion[2824]:  
May  9 23:35:11 cmp02 salt-minion[2824]:  # Specify a timeout after which a gracefully shutdown server will exit. Zero
May  9 23:35:11 cmp02 salt-minion[2824]: +# such as create, rebuild, evacuate, or rescue. If the hypervisor does not
May  9 23:35:11 cmp02 salt-minion[2824]: +# support password injection, then the password returned will not be correct,
May  9 23:35:11 cmp02 salt-minion[2824]: +# so if your hypervisor does not support password injection, set this to False.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/enable_instance_password
May  9 23:35:11 cmp02 salt-minion[2824]: +#enable_instance_password=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +[api_database]
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The *Nova API Database* is a separate database which is used for information
May  9 23:35:11 cmp02 salt-minion[2824]: +# which is used across *cells*. This database is mandatory since the Mitaka
May  9 23:35:11 cmp02 salt-minion[2824]: +# release (13.0.0).
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# The SQLAlchemy connection string to use to connect to the database. (string
May  9 23:35:11 cmp02 salt-minion[2824]: +# value)
May  9 23:35:11 cmp02 salt-minion[2824]: +connection=sqlite:////var/lib/nova/nova.sqlite
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# If True, SQLite uses synchronous mode. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#sqlite_synchronous=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# The SQLAlchemy connection string to use to connect to the slave database.
May  9 23:35:11 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#slave_connection=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# The SQL mode to be used for MySQL sessions. This option, including the
May  9 23:35:11 cmp02 salt-minion[2824]: +# default, overrides any server-set SQL mode. To use whatever SQL mode is set by
May  9 23:35:11 cmp02 salt-minion[2824]: +# the server configuration, set this to no value. Example: mysql_sql_mode=
May  9 23:35:11 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#mysql_sql_mode=TRADITIONAL
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Timeout before idle SQL connections are reaped. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#idle_timeout=3600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum number of SQL connections to keep open in a pool. Setting a value of 0
May  9 23:35:11 cmp02 salt-minion[2824]: +# indicates no limit. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_pool_size=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum number of database connection retries during startup. Set to -1 to
May  9 23:35:11 cmp02 salt-minion[2824]: +# specify an infinite retry count. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_retries=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Interval between retries of opening a SQL connection. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#retry_interval=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# If set, use this value for max_overflow with SQLAlchemy. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_overflow=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Verbosity of SQL debugging information: 0=None, 100=Everything. (integer
May  9 23:35:11 cmp02 salt-minion[2824]: +# value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#connection_debug=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Add Python stack traces to SQL as comment strings. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#connection_trace=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# If set, use this value for pool_timeout with SQLAlchemy. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#pool_timeout=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +[cache]
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +backend = oslo_cache.memcache_pool
May  9 23:35:11 cmp02 salt-minion[2824]: +enabled = true
May  9 23:35:11 cmp02 salt-minion[2824]: +memcache_servers=172.16.10.36:11211,172.16.10.37:11211,172.16.10.38:11211,127.0.0.1:11211
May  9 23:35:11 cmp02 salt-minion[2824]: +# Prefix for building the configuration dictionary for the cache region. This
May  9 23:35:11 cmp02 salt-minion[2824]: +# should not need to be changed unless there is another dogpile.cache region
May  9 23:35:11 cmp02 salt-minion[2824]: +# with the same configuration name. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#config_prefix=cache.oslo
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Default TTL, in seconds, for any cached item in the dogpile.cache region. This
May  9 23:35:11 cmp02 salt-minion[2824]: +# applies to any cached method that doesn't have an explicit cache expiration
May  9 23:35:11 cmp02 salt-minion[2824]: +# time defined for it. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#expiration_time=600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Dogpile.cache backend module. It is recommended that Memcache or Redis
May  9 23:35:11 cmp02 salt-minion[2824]: +# (dogpile.cache.redis) be used in production deployments. For eventlet-based or
May  9 23:35:11 cmp02 salt-minion[2824]: +# highly threaded servers, Memcache with pooling (oslo_cache.memcache_pool) is
May  9 23:35:11 cmp02 salt-minion[2824]: +# recommended. For low thread servers, dogpile.cache.memcached is recommended.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Test environments with a single instance of the server can use the
May  9 23:35:11 cmp02 salt-minion[2824]: +# dogpile.cache.memory backend. (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#backend=dogpile.cache.null
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Arguments supplied to the backend module. Specify this option once per
May  9 23:35:11 cmp02 salt-minion[2824]: +# argument to be passed to the dogpile.cache backend. Example format:
May  9 23:35:11 cmp02 salt-minion[2824]: +# "<argname>:<value>". (multi valued)
May  9 23:35:11 cmp02 salt-minion[2824]: +#backend_argument =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Proxy classes to import that will affect the way the dogpile.cache backend
May  9 23:35:11 cmp02 salt-minion[2824]: +# functions. See the dogpile.cache documentation on changing-backend-behavior.
May  9 23:35:11 cmp02 salt-minion[2824]: +# (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#proxies =
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Global toggle for caching. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#enabled=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Extra debugging from the cache backend (cache keys, get/set/delete/etc calls).
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is only really useful if you need to see the specific cache-backend
May  9 23:35:11 cmp02 salt-minion[2824]: +# get/set/delete calls with the keys/values.  Typically this should be left set
May  9 23:35:11 cmp02 salt-minion[2824]: +# to false. (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#debug_cache_backend=false
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Memcache servers in the format of "host:port". (dogpile.cache.memcache and
May  9 23:35:11 cmp02 salt-minion[2824]: +# oslo_cache.memcache_pool backends only). (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#memcache_servers=localhost:11211
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds memcached server is considered dead before it is tried
May  9 23:35:11 cmp02 salt-minion[2824]: +# again. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).
May  9 23:35:11 cmp02 salt-minion[2824]: +# (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#memcache_dead_retry=300
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Timeout in seconds for every call to a server. (dogpile.cache.memcache and
May  9 23:35:11 cmp02 salt-minion[2824]: +# oslo_cache.memcache_pool backends only). (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#memcache_socket_timeout=3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Max total number of open connections to every memcached server.
May  9 23:35:11 cmp02 salt-minion[2824]: +# (oslo_cache.memcache_pool backend only). (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#memcache_pool_maxsize=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds a connection to memcached is held unused in the pool before
May  9 23:35:11 cmp02 salt-minion[2824]: +# it is closed. (oslo_cache.memcache_pool backend only). (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#memcache_pool_unused_timeout=60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds that an operation will wait to get a memcache client
May  9 23:35:11 cmp02 salt-minion[2824]: +# connection. (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#memcache_pool_connection_get_timeout=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +[cells]
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cells options allow you to use cells functionality in openstack
May  9 23:35:11 cmp02 salt-minion[2824]: +# deployment.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note that the options in this group are only for cells v1 functionality, which
May  9 23:35:11 cmp02 salt-minion[2824]: +# is considered experimental and not recommended for new deployments. Cells v1
May  9 23:35:11 cmp02 salt-minion[2824]: +# is being replaced with cells v2, which starting in the 15.0.0 Ocata release is
May  9 23:35:11 cmp02 salt-minion[2824]: +# required and all Nova deployments will be at least a cells v2 cell of one.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Topic.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This is the message queue topic that cells nodes listen on. It is
May  9 23:35:11 cmp02 salt-minion[2824]: +# used when the cells service is started up to configure the queue,
May  9 23:35:11 cmp02 salt-minion[2824]: +# and whenever an RPC call to the scheduler is made.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * cells: This is the recommended and the default value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:11 cmp02 salt-minion[2824]: +# Configurable RPC topics provide little value and can result in a wide variety
May  9 23:35:11 cmp02 salt-minion[2824]: +# of errors. They should not be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#topic=cells
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Enable cell v1 functionality.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note that cells v1 is considered experimental and not recommended for new
May  9 23:35:11 cmp02 salt-minion[2824]: +# Nova deployments. Cells v1 is being replaced by cells v2 which starting in
May  9 23:35:11 cmp02 salt-minion[2824]: +# the 15.0.0 Ocata release, all Nova deployments are at least a cells v2 cell
May  9 23:35:11 cmp02 salt-minion[2824]: +# of one. Setting this option, or any other options in the [cells] group, is
May  9 23:35:11 cmp02 salt-minion[2824]: +# not required for cells v2.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When this functionality is enabled, it lets you to scale an OpenStack
May  9 23:35:11 cmp02 salt-minion[2824]: +# Compute cloud in a more distributed fashion without having to use
May  9 23:35:11 cmp02 salt-minion[2824]: +# complicated technologies like database and message queue clustering.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cells are configured as a tree. The top-level cell should have a host
May  9 23:35:11 cmp02 salt-minion[2824]: +# that runs a nova-api service, but no nova-compute services. Each
May  9 23:35:11 cmp02 salt-minion[2824]: +# child cell should run all of the typical nova-* services in a regular
May  9 23:35:11 cmp02 salt-minion[2824]: +# Compute cloud except for nova-api. You can think of cells as a normal
May  9 23:35:11 cmp02 salt-minion[2824]: +# Compute deployment in that each cell has its own database server and
May  9 23:35:11 cmp02 salt-minion[2824]: +# message queue broker.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * name: A unique cell name must be given when this functionality
May  9 23:35:11 cmp02 salt-minion[2824]: +#   is enabled.
May  9 23:35:11 cmp02 salt-minion[2824]: +# * cell_type: Cell type should be defined for all cells.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +enable=False
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Name of the current cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This value must be unique for each cell. Name of a cell is used as
May  9 23:35:11 cmp02 salt-minion[2824]: +# its id, leaving this option unset or setting the same name for
May  9 23:35:11 cmp02 salt-minion[2824]: +# two or more cells may cause unexpected behaviour.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * enabled: This option is meaningful only when cells service
May  9 23:35:11 cmp02 salt-minion[2824]: +#   is enabled
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#name=nova
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cell capabilities.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# List of arbitrary key=value pairs defining capabilities of the
May  9 23:35:11 cmp02 salt-minion[2824]: +# current cell to be sent to the parent cells. These capabilities
May  9 23:35:11 cmp02 salt-minion[2824]: +# are intended to be used in cells scheduler filters/weighers.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * key=value pairs list for example;
May  9 23:35:11 cmp02 salt-minion[2824]: +#   ``hypervisor=xenserver;kvm,os=linux;windows``
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#capabilities=hypervisor=xenserver;kvm,os=linux;windows
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Call timeout.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cell messaging module waits for response(s) to be put into the
May  9 23:35:11 cmp02 salt-minion[2824]: +# eventlet queue. This option defines the seconds waited for
May  9 23:35:11 cmp02 salt-minion[2824]: +# response from a call to a cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An integer, corresponding to the interval time in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#call_timeout=60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Reserve percentage
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Percentage of cell capacity to hold in reserve, so the minimum
May  9 23:35:11 cmp02 salt-minion[2824]: +# amount of free resource is considered to be;
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     min_free = total * (reserve_percent / 100.0)
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option affects both memory and disk utilization.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The primary purpose of this reserve is to ensure some space is
May  9 23:35:11 cmp02 salt-minion[2824]: +# available for users who want to resize their instance to be larger.
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note that currently once the capacity expands into this reserve
May  9 23:35:11 cmp02 salt-minion[2824]: +# space this option is ignored.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An integer or float, corresponding to the percentage of cell capacity to
May  9 23:35:11 cmp02 salt-minion[2824]: +#   be held in reserve.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#reserve_percent=10.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Type of cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When cells feature is enabled the hosts in the OpenStack Compute
May  9 23:35:11 cmp02 salt-minion[2824]: +# cloud are partitioned into groups. Cells are configured as a tree.
May  9 23:35:11 cmp02 salt-minion[2824]: +# The top-level cell's cell_type must be set to ``api``. All other
May  9 23:35:11 cmp02 salt-minion[2824]: +# cells are defined as a ``compute cell`` by default.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related option:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * quota_driver: Disable quota checking for the child cells.
May  9 23:35:11 cmp02 salt-minion[2824]: +#   (nova.quota.NoopQuotaDriver)
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allowed values: api, compute
May  9 23:35:11 cmp02 salt-minion[2824]: +#cell_type=compute
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Mute child interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds after which a lack of capability and capacity
May  9 23:35:11 cmp02 salt-minion[2824]: +# update the child cell is to be treated as a mute cell. Then the
May  9 23:35:11 cmp02 salt-minion[2824]: +# child cell will be weighed as recommend highly that it be skipped.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An integer, corresponding to the interval time in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#mute_child_interval=300
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Bandwidth update interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Seconds between bandwidth usage cache updates for cells.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An integer, corresponding to the interval time in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#bandwidth_update_interval=600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Instance update sync database limit.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of instances to pull from the database at one time for
May  9 23:35:11 cmp02 salt-minion[2824]: +# a sync. If there are more instances to update the results will
May  9 23:35:11 cmp02 salt-minion[2824]: +# be paged through.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * An integer, corresponding to a number of instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_update_sync_database_limit=100
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Mute weight multiplier.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Multiplier used to weigh mute children. Mute children cells are
May  9 23:35:11 cmp02 salt-minion[2824]: +# recommended to be skipped so their weight is multiplied by this
May  9 23:35:11 cmp02 salt-minion[2824]: +# negative value.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Negative numeric number
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#mute_weight_multiplier=-10000.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Ram weight multiplier.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Multiplier used for weighing ram. Negative numbers indicate that
May  9 23:35:11 cmp02 salt-minion[2824]: +# Compute should stack VMs on one host instead of spreading out new
May  9 23:35:11 cmp02 salt-minion[2824]: +# VMs to more hosts in the cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Numeric multiplier
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#ram_weight_multiplier=10.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Offset weight multiplier
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Multiplier used to weigh offset weigher. Cells with higher
May  9 23:35:11 cmp02 salt-minion[2824]: +# weight_offsets in the DB will be preferred. The weight_offset
May  9 23:35:11 cmp02 salt-minion[2824]: +# is a property of a cell stored in the database. It can be used
May  9 23:35:11 cmp02 salt-minion[2824]: +# by a deployer to have scheduling decisions favor or disfavor
May  9 23:35:11 cmp02 salt-minion[2824]: +# cells based on the setting.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Numeric multiplier
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#offset_weight_multiplier=1.0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Instance updated at threshold
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of seconds after an instance was updated or deleted to
May  9 23:35:11 cmp02 salt-minion[2824]: +# continue to update cells. This option lets cells manager to only
May  9 23:35:11 cmp02 salt-minion[2824]: +# attempt to sync instances that have been updated recently.
May  9 23:35:11 cmp02 salt-minion[2824]: +# i.e., a threshold of 3600 means to only update instances that
May  9 23:35:11 cmp02 salt-minion[2824]: +# have modified in the last hour.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Threshold in seconds
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This value is used with the ``instance_update_num_instances``
May  9 23:35:11 cmp02 salt-minion[2824]: +#   value in a periodic task run.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_updated_at_threshold=3600
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Instance update num instances
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# On every run of the periodic task, nova cells manager will attempt to
May  9 23:35:11 cmp02 salt-minion[2824]: +# sync instance_updated_at_threshold number of instances. When the
May  9 23:35:11 cmp02 salt-minion[2824]: +# manager gets the list of instances, it shuffles them so that multiple
May  9 23:35:11 cmp02 salt-minion[2824]: +# nova-cells services do not attempt to sync the same instances in
May  9 23:35:11 cmp02 salt-minion[2824]: +# lockstep.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Positive integer number
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This value is used with the ``instance_updated_at_threshold``
May  9 23:35:11 cmp02 salt-minion[2824]: +#   value in a periodic task run.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#instance_update_num_instances=1
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Maximum hop count
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When processing a targeted message, if the local cell is not the
May  9 23:35:11 cmp02 salt-minion[2824]: +# target, a route is defined between neighbouring cells. And the
May  9 23:35:11 cmp02 salt-minion[2824]: +# message is processed across the whole routing path. This option
May  9 23:35:11 cmp02 salt-minion[2824]: +# defines the maximum hop counts until reaching the target.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Positive integer value
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#max_hop_count=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cells scheduler.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The class of the driver used by the cells scheduler. This should be
May  9 23:35:11 cmp02 salt-minion[2824]: +# the full Python path to the class to be used. If nothing is specified
May  9 23:35:11 cmp02 salt-minion[2824]: +# in this option, the CellsScheduler is used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#scheduler=nova.cells.scheduler.CellsScheduler
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# RPC driver queue base.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# When sending a message to another cell by JSON-ifying the message
May  9 23:35:11 cmp02 salt-minion[2824]: +# and making an RPC cast to 'process_message', a base queue is used.
May  9 23:35:11 cmp02 salt-minion[2824]: +# This option defines the base queue name to be used when communicating
May  9 23:35:11 cmp02 salt-minion[2824]: +# between cells. Various topics by message type will be appended to this.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * The base queue name to be used when communicating between cells.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#rpc_driver_queue_base=cells.intercell
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Scheduler filter classes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Filter classes the cells scheduler should use. An entry of
May  9 23:35:11 cmp02 salt-minion[2824]: +# "nova.cells.filters.all_filters" maps to all cells filters
May  9 23:35:11 cmp02 salt-minion[2824]: +# included with nova. As of the Mitaka release the following
May  9 23:35:11 cmp02 salt-minion[2824]: +# filter classes are available:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Different cell filter: A scheduler hint of 'different_cell'
May  9 23:35:11 cmp02 salt-minion[2824]: +# with a value of a full cell name may be specified to route
May  9 23:35:11 cmp02 salt-minion[2824]: +# a build away from a particular cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Image properties filter: Image metadata named
May  9 23:35:11 cmp02 salt-minion[2824]: +# 'hypervisor_version_requires' with a version specification
May  9 23:35:11 cmp02 salt-minion[2824]: +# may be specified to ensure the build goes to a cell which
May  9 23:35:11 cmp02 salt-minion[2824]: +# has hypervisors of the required version. If either the version
May  9 23:35:11 cmp02 salt-minion[2824]: +# requirement on the image or the hypervisor capability of the
May  9 23:35:11 cmp02 salt-minion[2824]: +# cell is not present, this filter returns without filtering out
May  9 23:35:11 cmp02 salt-minion[2824]: +# the cells.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Target cell filter: A scheduler hint of 'target_cell' with a
May  9 23:35:11 cmp02 salt-minion[2824]: +# value of a full cell name may be specified to route a build to
May  9 23:35:11 cmp02 salt-minion[2824]: +# a particular cell. No error handling is done as there's no way
May  9 23:35:11 cmp02 salt-minion[2824]: +# to know whether the full path is a valid.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# As an admin user, you can also add a filter that directs builds
May  9 23:35:11 cmp02 salt-minion[2824]: +# to a particular cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#scheduler_filter_classes=nova.cells.filters.all_filters
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Scheduler weight classes.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Weigher classes the cells scheduler should use. An entry of
May  9 23:35:11 cmp02 salt-minion[2824]: +# "nova.cells.weights.all_weighers" maps to all cell weighers
May  9 23:35:11 cmp02 salt-minion[2824]: +# included with nova. As of the Mitaka release the following
May  9 23:35:11 cmp02 salt-minion[2824]: +# weight classes are available:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# mute_child: Downgrades the likelihood of child cells being
May  9 23:35:11 cmp02 salt-minion[2824]: +# chosen for scheduling requests, which haven't sent capacity
May  9 23:35:11 cmp02 salt-minion[2824]: +# or capability updates in a while. Options include
May  9 23:35:11 cmp02 salt-minion[2824]: +# mute_weight_multiplier (multiplier for mute children; value
May  9 23:35:11 cmp02 salt-minion[2824]: +# should be negative).
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# ram_by_instance_type: Select cells with the most RAM capacity
May  9 23:35:11 cmp02 salt-minion[2824]: +# for the instance type being requested. Because higher weights
May  9 23:35:11 cmp02 salt-minion[2824]: +# win, Compute returns the number of available units for the
May  9 23:35:11 cmp02 salt-minion[2824]: +# instance type requested. The ram_weight_multiplier option defaults
May  9 23:35:11 cmp02 salt-minion[2824]: +# to 10.0 that adds to the weight by a factor of 10. Use a negative
May  9 23:35:11 cmp02 salt-minion[2824]: +# number to stack VMs on one host instead of spreading out new VMs
May  9 23:35:11 cmp02 salt-minion[2824]: +# to more hosts in the cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# weight_offset: Allows modifying the database to weight a particular
May  9 23:35:11 cmp02 salt-minion[2824]: +# cell. The highest weight will be the first cell to be scheduled for
May  9 23:35:11 cmp02 salt-minion[2824]: +# launching an instance. When the weight_offset of a cell is set to 0,
May  9 23:35:11 cmp02 salt-minion[2824]: +# it is unlikely to be picked but it could be picked if other cells
May  9 23:35:11 cmp02 salt-minion[2824]: +# have a lower weight, like if they're full. And when the weight_offset
May  9 23:35:11 cmp02 salt-minion[2824]: +# is set to a very high value (for example, '999999999999999'), it is
May  9 23:35:11 cmp02 salt-minion[2824]: +# likely to be picked if another cell do not have a higher weight.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#scheduler_weight_classes=nova.cells.weights.all_weighers
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Scheduler retries.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# How many retries when no cells are available. Specifies how many
May  9 23:35:11 cmp02 salt-minion[2824]: +# times the scheduler tries to launch a new instance when no cells
May  9 23:35:11 cmp02 salt-minion[2824]: +# are available.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Positive integer value
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This value is used with the ``scheduler_retry_delay`` value
May  9 23:35:11 cmp02 salt-minion[2824]: +#   while retrying to find a suitable cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#scheduler_retries=10
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Scheduler retry delay.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Specifies the delay (in seconds) between scheduling retries when no
May  9 23:35:11 cmp02 salt-minion[2824]: +# cell can be found to place the new instance on. When the instance
May  9 23:35:11 cmp02 salt-minion[2824]: +# could not be scheduled to a cell after ``scheduler_retries`` in
May  9 23:35:11 cmp02 salt-minion[2824]: +# combination with ``scheduler_retry_delay``, then the scheduling
May  9 23:35:11 cmp02 salt-minion[2824]: +# of the instance failed.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Time in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * This value is used with the ``scheduler_retries`` value
May  9 23:35:11 cmp02 salt-minion[2824]: +#   while retrying to find a suitable cell.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#scheduler_retry_delay=2
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# DB check interval.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cell state manager updates cell status for all cells from the DB
May  9 23:35:11 cmp02 salt-minion[2824]: +# only after this particular interval time is passed. Otherwise cached
May  9 23:35:11 cmp02 salt-minion[2824]: +# status are used. If this value is 0 or negative all cell status are
May  9 23:35:11 cmp02 salt-minion[2824]: +# updated from the DB whenever a state is needed.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Interval time, in seconds.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#db_check_interval=60
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Optional cells configuration.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Configuration file from which to read cells configuration. If given,
May  9 23:35:11 cmp02 salt-minion[2824]: +# overrides reading cells from the database.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Cells store all inter-cell communication data, including user names
May  9 23:35:11 cmp02 salt-minion[2824]: +# and passwords, in the database. Because the cells data is not updated
May  9 23:35:11 cmp02 salt-minion[2824]: +# very frequently, use this option to specify a JSON file to store
May  9 23:35:11 cmp02 salt-minion[2824]: +# cells data. With this configuration, the database is no longer
May  9 23:35:11 cmp02 salt-minion[2824]: +# consulted when reloading the cells data. The file must have columns
May  9 23:35:11 cmp02 salt-minion[2824]: +# present in the Cell model (excluding common database fields and the
May  9 23:35:11 cmp02 salt-minion[2824]: +# id column). You must specify the queue connection information through
May  9 23:35:11 cmp02 salt-minion[2824]: +# a transport_url field, instead of username, password, and so on.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The transport_url has the following form:
May  9 23:35:11 cmp02 salt-minion[2824]: +# rabbit://USERNAME:PASSWORD@HOSTNAME:PORT/VIRTUAL_HOST
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The scheme can be either qpid or rabbit, the following sample shows
May  9 23:35:11 cmp02 salt-minion[2824]: +# this optional configuration:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#     {
May  9 23:35:11 cmp02 salt-minion[2824]: +#         "parent": {
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "name": "parent",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "api_url": "http://api.example.com:8774",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "transport_url": "rabbit://rabbit.example.com",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "weight_offset": 0.0,
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "weight_scale": 1.0,
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "is_parent": true
May  9 23:35:11 cmp02 salt-minion[2824]: +#         },
May  9 23:35:11 cmp02 salt-minion[2824]: +#         "cell1": {
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "name": "cell1",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "api_url": "http://api.example.com:8774",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "transport_url": "rabbit://rabbit1.example.com",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "weight_offset": 0.0,
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "weight_scale": 1.0,
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "is_parent": false
May  9 23:35:11 cmp02 salt-minion[2824]: +#         },
May  9 23:35:11 cmp02 salt-minion[2824]: +#         "cell2": {
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "name": "cell2",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "api_url": "http://api.example.com:8774",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "transport_url": "rabbit://rabbit2.example.com",
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "weight_offset": 0.0,
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "weight_scale": 1.0,
May  9 23:35:11 cmp02 salt-minion[2824]: +#             "is_parent": false
May  9 23:35:11 cmp02 salt-minion[2824]: +#         }
May  9 23:35:11 cmp02 salt-minion[2824]: +#     }
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#cells_config=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +[cinder]
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +os_region_name = RegionOne
May  9 23:35:11 cmp02 salt-minion[2824]: +catalog_info=volumev2:cinderv2:internalURL
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Info to match when looking for cinder in the service catalog.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Format is separated values of the form:
May  9 23:35:11 cmp02 salt-minion[2824]: +#   <service_type>:<service_name>:<endpoint_type>
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note: Nova does not support the Cinder v1 API since the Nova 15.0.0 Ocata
May  9 23:35:11 cmp02 salt-minion[2824]: +# release.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * endpoint_template - Setting this option will override catalog_info
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#catalog_info=volumev2:cinderv2:publicURL
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If this option is set then it will override service catalog lookup with
May  9 23:35:11 cmp02 salt-minion[2824]: +# this template for cinder endpoint
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * URL for cinder endpoint API
May  9 23:35:11 cmp02 salt-minion[2824]: +#   e.g. http://localhost:8776/v2/%(project_id)s
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note: Nova does not support the Cinder v1 API since the Nova 15.0.0 Ocata
May  9 23:35:11 cmp02 salt-minion[2824]: +# release.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * catalog_info - If endpoint_template is not set, catalog_info will be used.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#endpoint_template=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Region name of this node. This is used when picking the URL in the service
May  9 23:35:11 cmp02 salt-minion[2824]: +# catalog.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any string representing region name
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#os_region_name=<None>
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Number of times cinderclient should retry on any failed http call.
May  9 23:35:11 cmp02 salt-minion[2824]: +# 0 means connection is attempted only once. Setting it to any positive integer
May  9 23:35:11 cmp02 salt-minion[2824]: +# means that on failure connection is retried that many times e.g. setting it
May  9 23:35:11 cmp02 salt-minion[2824]: +# to 3 means total attempts to connect will be 4.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any integer value. 0 means connection is attempted only once
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:11 cmp02 salt-minion[2824]: +#http_retries=3
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Allow attach between instance and volume in different availability zones.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# If False, volumes attached to an instance must be in the same availability
May  9 23:35:11 cmp02 salt-minion[2824]: +# zone in Cinder as the instance availability zone in Nova.
May  9 23:35:11 cmp02 salt-minion[2824]: +# This also means care should be taken when booting an instance from a volume
May  9 23:35:11 cmp02 salt-minion[2824]: +# where source is not "volume" because Nova will attempt to create a volume
May  9 23:35:11 cmp02 salt-minion[2824]: +# using
May  9 23:35:11 cmp02 salt-minion[2824]: +# the same availability zone as what is assigned to the instance.
May  9 23:35:11 cmp02 salt-minion[2824]: +# If that AZ is not in Cinder (or allow_availability_zone_fallback=False in
May  9 23:35:11 cmp02 salt-minion[2824]: +# cinder.conf), the volume create request will fail and the instance will fail
May  9 23:35:11 cmp02 salt-minion[2824]: +# the build request.
May  9 23:35:11 cmp02 salt-minion[2824]: +# By default there is no availability zone restriction on volume attach.
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:11 cmp02 salt-minion[2824]: +#cross_az_attach=true
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +[cloudpipe]
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Image ID used when starting up a cloudpipe VPN client.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# An empty instance is created and configured with OpenVPN using
May  9 23:35:11 cmp02 salt-minion[2824]: +# boot_script_template. This instance would be snapshotted and stored
May  9 23:35:11 cmp02 salt-minion[2824]: +# in glance. ID of the stored image is used in 'vpn_image_id' to
May  9 23:35:11 cmp02 salt-minion[2824]: +# create cloudpipe VPN client.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid ID of a VPN image
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vpn_image_id
May  9 23:35:11 cmp02 salt-minion[2824]: +#vpn_image_id=0
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Flavor for VPN instances.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid flavor name
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vpn_flavor
May  9 23:35:11 cmp02 salt-minion[2824]: +#vpn_flavor=m1.tiny
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Template for cloudpipe instance boot script.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid path to a cloudpipe instance boot script template
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# The following options are required to configure cloudpipe-managed
May  9 23:35:11 cmp02 salt-minion[2824]: +# OpenVPN server.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * dmz_net
May  9 23:35:11 cmp02 salt-minion[2824]: +# * dmz_mask
May  9 23:35:11 cmp02 salt-minion[2824]: +# * cnt_vpn_clients
May  9 23:35:11 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:11 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/boot_script_template
May  9 23:35:11 cmp02 salt-minion[2824]: +#boot_script_template=$pybasedir/nova/cloudpipe/bootscript.template
May  9 23:35:11 cmp02 salt-minion[2824]: +
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Network to push into OpenVPN config.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Note: Above mentioned OpenVPN config can be found at
May  9 23:35:11 cmp02 salt-minion[2824]: +# /etc/openvpn/server.conf.
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:11 cmp02 salt-minion[2824]: +#
May  9 23:35:11 cmp02 salt-minion[2824]: +# * Any valid IPv4/IPV6 address
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * boot_script_template - dmz_net is pushed into bootscript.template
May  9 23:35:12 cmp02 salt-minion[2824]: +#   to configure cloudpipe-managed OpenVPN server
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (IP address value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/dmz_net
May  9 23:35:12 cmp02 salt-minion[2824]: +#dmz_net=10.0.0.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Netmask to push into OpenVPN config.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid IPv4/IPV6 netmask
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * dmz_net - dmz_net and dmz_mask is pushed into bootscript.template
May  9 23:35:12 cmp02 salt-minion[2824]: +#   to configure cloudpipe-managed OpenVPN server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * boot_script_template
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (IP address value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/dmz_mask
May  9 23:35:12 cmp02 salt-minion[2824]: +#dmz_mask=255.255.255.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Suffix to add to project name for VPN key and secgroups
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string value representing the VPN key suffix
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vpn_key_suffix
May  9 23:35:12 cmp02 salt-minion[2824]: +#vpn_key_suffix=-vpn
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[conductor]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Options under this group are used to define Conductor's communication,
May  9 23:35:12 cmp02 salt-minion[2824]: +# which manager should be act as a proxy between computes and database,
May  9 23:35:12 cmp02 salt-minion[2824]: +# and finally, how many worker processes will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Topic exchange name on which conductor nodes listen.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# There is no need to let users choose the RPC topic for all services - there
May  9 23:35:12 cmp02 salt-minion[2824]: +# is little gain from this. Furthermore, it makes it really easy to break Nova
May  9 23:35:12 cmp02 salt-minion[2824]: +# by using this option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#topic=conductor
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of workers for OpenStack Conductor service. The default will be the
May  9 23:35:12 cmp02 salt-minion[2824]: +# number of CPUs available.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#workers=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[console]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Options under this group allow to tune the configuration of the console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +# service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: in configuration of every compute is a ``console_host`` option,
May  9 23:35:12 cmp02 salt-minion[2824]: +# which allows to select the console proxy service to connect to.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Adds list of allowed origins to the console websocket proxy to allow
May  9 23:35:12 cmp02 salt-minion[2824]: +# connections from other origin hostnames.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Websocket proxy matches the host header with the origin header to
May  9 23:35:12 cmp02 salt-minion[2824]: +# prevent cross-site requests. This list specifies if any there are
May  9 23:35:12 cmp02 salt-minion[2824]: +# values other than host are allowed in the origin header.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list where each element is an allowed origin hostnames, else an empty list
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_allowed_origins
May  9 23:35:12 cmp02 salt-minion[2824]: +#allowed_origins =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[consoleauth]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The lifetime of a console auth token.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# A console auth token is used in authorizing console access for a user.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Once the auth token time to live count has elapsed, the token is
May  9 23:35:12 cmp02 salt-minion[2824]: +# considered expired.  Expired tokens are then deleted.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_token_ttl
May  9 23:35:12 cmp02 salt-minion[2824]: +#token_ttl=600
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [cors]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -326,24 +4260,135 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # Indicate whether this resource may be shared with the domain received in the
May  9 23:35:12 cmp02 salt-minion[2824]:  # requests "origin" header. Format: "<protocol>://<host>[:<port>]", no trailing
May  9 23:35:12 cmp02 salt-minion[2824]:  # slash. Example: https://horizon.example.com (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#allowed_origin = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#allowed_origin=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Indicate that the actual request can include user credentials (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#allow_credentials = true
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_credentials=true
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Indicate which headers are safe to expose to the API. Defaults to HTTP Simple
May  9 23:35:12 cmp02 salt-minion[2824]:  # Headers. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#expose_headers =
May  9 23:35:12 cmp02 salt-minion[2824]: +#expose_headers=X-Auth-Token,X-Openstack-Request-Id,X-Subject-Token,X-Service-Token
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum cache age of CORS preflight requests. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_age = 3600
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_age=3600
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Indicate which methods can be used during the actual request. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#allow_methods = OPTIONS,GET,HEAD,POST,PUT,DELETE,TRACE,PATCH
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_methods=GET,PUT,POST,DELETE,PATCH
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Indicate which header field names may be used during the actual request. (list
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#allow_headers =
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_headers=X-Auth-Token,X-Openstack-Request-Id,X-Identity-Status,X-Roles,X-Service-Catalog,X-User-Id,X-Tenant-Id
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[cors.subdomain]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From oslo.middleware
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Indicate whether this resource may be shared with the domain received in the
May  9 23:35:12 cmp02 salt-minion[2824]: +# requests "origin" header. Format: "<protocol>://<host>[:<port>]", no trailing
May  9 23:35:12 cmp02 salt-minion[2824]: +# slash. Example: https://horizon.example.com (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#allowed_origin=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Indicate that the actual request can include user credentials (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_credentials=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Indicate which headers are safe to expose to the API. Defaults to HTTP Simple
May  9 23:35:12 cmp02 salt-minion[2824]: +# Headers. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#expose_headers=X-Auth-Token,X-Openstack-Request-Id,X-Subject-Token,X-Service-Token
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum cache age of CORS preflight requests. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_age=3600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Indicate which methods can be used during the actual request. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_methods=GET,PUT,POST,DELETE,PATCH
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Indicate which header field names may be used during the actual request. (list
May  9 23:35:12 cmp02 salt-minion[2824]: +# value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_headers=X-Auth-Token,X-Openstack-Request-Id,X-Identity-Status,X-Roles,X-Service-Catalog,X-User-Id,X-Tenant-Id
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[crypto]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filename of root CA (Certificate Authority). This is a container format
May  9 23:35:12 cmp02 salt-minion[2824]: +# and includes root certificates.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any file name containing root CA, cacert.pem is default
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ca_path
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#ca_file=cacert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filename of a private key.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * keys_path
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/key_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#key_file=private/cakey.pem
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filename of root Certificate Revocation List (CRL). This is a list of
May  9 23:35:12 cmp02 salt-minion[2824]: +# certificates that have been revoked, and therefore, entities presenting
May  9 23:35:12 cmp02 salt-minion[2824]: +# those (revoked) certificates should no longer be trusted.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ca_path
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/crl_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#crl_file=crl.pem
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Directory path where keys are located.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * key_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/keys_path
May  9 23:35:12 cmp02 salt-minion[2824]: +#keys_path=$state_path/keys
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Directory path where root CA is located.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ca_path
May  9 23:35:12 cmp02 salt-minion[2824]: +#ca_path=$state_path/CA
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Option to enable/disable use of CA for each project. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/use_project_ca
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_project_ca=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Subject for certificate for users, %s for
May  9 23:35:12 cmp02 salt-minion[2824]: +# project, user, timestamp
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/user_cert_subject
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_cert_subject=/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Subject for certificate for projects, %s for
May  9 23:35:12 cmp02 salt-minion[2824]: +# project, timestamp
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/project_cert_subject
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_cert_subject=/C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [database]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -352,100 +4397,105 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # From oslo.db
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: The file name to use with SQLite. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/sqlite_db
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: Should use config option connection or slave_connection to connect the
May  9 23:35:12 cmp02 salt-minion[2824]: +# database.
May  9 23:35:12 cmp02 salt-minion[2824]: +#sqlite_db=oslo.sqlite
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  # If True, SQLite uses synchronous mode. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#sqlite_synchronous = true
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/sqlite_synchronous
May  9 23:35:12 cmp02 salt-minion[2824]: +#sqlite_synchronous=true
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The back end to use for the database. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/db_backend
May  9 23:35:12 cmp02 salt-minion[2824]: -#backend = sqlalchemy
May  9 23:35:12 cmp02 salt-minion[2824]: +#backend=sqlalchemy
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The SQLAlchemy connection string to use to connect to the database. (string
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_connection
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sql_connection
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [sql]/connection
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The SQLAlchemy connection string to use to connect to the slave database.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#slave_connection = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#slave_connection=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The SQL mode to be used for MySQL sessions. This option, including the
May  9 23:35:12 cmp02 salt-minion[2824]:  # default, overrides any server-set SQL mode. To use whatever SQL mode is set by
May  9 23:35:12 cmp02 salt-minion[2824]:  # the server configuration, set this to no value. Example: mysql_sql_mode=
May  9 23:35:12 cmp02 salt-minion[2824]:  # (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#mysql_sql_mode = TRADITIONAL
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# If True, transparently enables support for handling MySQL Cluster (NDB).
May  9 23:35:12 cmp02 salt-minion[2824]: -# (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#mysql_enable_ndb = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#mysql_sql_mode=TRADITIONAL
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Timeout before idle SQL connections are reaped. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_idle_timeout
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sql_idle_timeout
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [sql]/idle_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: -#idle_timeout = 3600
May  9 23:35:12 cmp02 salt-minion[2824]: +#idle_timeout=3600
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum number of SQL connections to keep open in a pool. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_min_pool_size
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sql_min_pool_size
May  9 23:35:12 cmp02 salt-minion[2824]: -#min_pool_size = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#min_pool_size=1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of SQL connections to keep open in a pool. Setting a value of 0
May  9 23:35:12 cmp02 salt-minion[2824]:  # indicates no limit. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_max_pool_size
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sql_max_pool_size
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_pool_size = 5
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_pool_size=5
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of database connection retries during startup. Set to -1 to
May  9 23:35:12 cmp02 salt-minion[2824]:  # specify an infinite retry count. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_max_retries
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sql_max_retries
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_retries = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_retries=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Interval between retries of opening a SQL connection. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_retry_interval
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/reconnect_interval
May  9 23:35:12 cmp02 salt-minion[2824]: -#retry_interval = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#retry_interval=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # If set, use this value for max_overflow with SQLAlchemy. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_max_overflow
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sqlalchemy_max_overflow
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_overflow = 50
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_overflow=50
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Verbosity of SQL debugging information: 0=None, 100=Everything. (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum value: 100
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_connection_debug
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection_debug = 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_debug=0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Add Python stack traces to SQL as comment strings. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/sql_connection_trace
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection_trace = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_trace=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # If set, use this value for pool_timeout with SQLAlchemy. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DATABASE]/sqlalchemy_pool_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_timeout = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_timeout=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Enable the experimental use of database reconnect on connection lost. (boolean
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#use_db_reconnect = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_db_reconnect=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Seconds between retries of a database transaction. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#db_retry_interval = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#db_retry_interval=1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # If True, increases the interval between retries of a database operation up to
May  9 23:35:12 cmp02 salt-minion[2824]:  # db_max_retry_interval. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#db_inc_retry_interval = true
May  9 23:35:12 cmp02 salt-minion[2824]: +#db_inc_retry_interval=true
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # If db_inc_retry_interval is set, the maximum seconds between retries of a
May  9 23:35:12 cmp02 salt-minion[2824]:  # database operation. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#db_max_retry_interval = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#db_max_retry_interval=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum retries in case of connection error or deadlock error before error is
May  9 23:35:12 cmp02 salt-minion[2824]:  # raised. Set to -1 to specify an infinite retry count. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#db_max_retries = 20
May  9 23:35:12 cmp02 salt-minion[2824]: +#db_max_retries=20
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # From oslo.db.concurrency
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -454,7 +4504,562 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # Enable the experimental use of thread pooling for all DB API calls (boolean
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/dbapi_use_tpool
May  9 23:35:12 cmp02 salt-minion[2824]: -#use_tpool = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_tpool=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[ephemeral_storage_encryption]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enables/disables LVM ephemeral storage encryption.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cipher-mode string to be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The cipher and mode to be used to encrypt ephemeral storage. The set of
May  9 23:35:12 cmp02 salt-minion[2824]: +# cipher-mode combinations available depends on kernel support.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any crypto option listed in ``/proc/crypto``.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cipher=aes-xts-plain64
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Encryption key length in bits.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The bit length of the encryption key to be used to encrypt ephemeral storage.
May  9 23:35:12 cmp02 salt-minion[2824]: +# In XTS mode only half of the bits are used for encryption key.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#key_size=512
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[filter_scheduler]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Size of subset of best hosts selected by scheduler.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# New instances will be scheduled on a host chosen randomly from a subset of the
May  9 23:35:12 cmp02 salt-minion[2824]: +# N best hosts, where N is the value set by this option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Setting this to a value greater than 1 will reduce the chance that multiple
May  9 23:35:12 cmp02 salt-minion[2824]: +# scheduler processes handling similar requests will select the same host,
May  9 23:35:12 cmp02 salt-minion[2824]: +# creating a potential race condition. By selecting a host randomly from the N
May  9 23:35:12 cmp02 salt-minion[2824]: +# hosts that best fit the request, the chance of a conflict is reduced. However,
May  9 23:35:12 cmp02 salt-minion[2824]: +# the higher you set this value, the less optimal the chosen host may be for a
May  9 23:35:12 cmp02 salt-minion[2824]: +# given request.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer, where the integer corresponds to the size of a host subset. Any
May  9 23:35:12 cmp02 salt-minion[2824]: +#   integer is valid, although any value less than 1 will be treated as 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_host_subset_size
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_subset_size=1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of instances that can be actively performing IO on a host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Instances performing IO includes those in the following states: build, resize,
May  9 23:35:12 cmp02 salt-minion[2824]: +# snapshot, migrate, rescue, unshelve.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'io_ops_filter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer, where the integer corresponds to the max number of instances
May  9 23:35:12 cmp02 salt-minion[2824]: +#   that can be actively performing IO on any given host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/max_io_ops_per_host
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_io_ops_per_host=8
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum number of instances that be active on a host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If you need to limit the number of instances on any given host, set this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option
May  9 23:35:12 cmp02 salt-minion[2824]: +# to the maximum number of instances you want to allow. The num_instances_filter
May  9 23:35:12 cmp02 salt-minion[2824]: +# will reject any host that has at least as many instances as this option's
May  9 23:35:12 cmp02 salt-minion[2824]: +# value.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'num_instances_filter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer, where the integer corresponds to the max instances that can be
May  9 23:35:12 cmp02 salt-minion[2824]: +#   scheduled on a host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/max_instances_per_host
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_instances_per_host=50
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable querying of individual hosts for instance information.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The scheduler may need information about the instances on a host in order to
May  9 23:35:12 cmp02 salt-minion[2824]: +# evaluate its filters and weighers. The most common need for this information
May  9 23:35:12 cmp02 salt-minion[2824]: +# is
May  9 23:35:12 cmp02 salt-minion[2824]: +# for the (anti-)affinity filters, which need to choose a host based on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# instances already running on a host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If the configured filters and weighers do not need this information, disabling
May  9 23:35:12 cmp02 salt-minion[2824]: +# this option will improve performance. It may also be disabled when the
May  9 23:35:12 cmp02 salt-minion[2824]: +# tracking
May  9 23:35:12 cmp02 salt-minion[2824]: +# overhead proves too heavy, although this will cause classes requiring host
May  9 23:35:12 cmp02 salt-minion[2824]: +# usage data to query the database on each request instead.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_tracks_instance_changes
May  9 23:35:12 cmp02 salt-minion[2824]: +#track_instance_changes=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filters that the scheduler can use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An unordered list of the filter classes the nova scheduler may apply.  Only
May  9 23:35:12 cmp02 salt-minion[2824]: +# the
May  9 23:35:12 cmp02 salt-minion[2824]: +# filters specified in the 'scheduler_enabled_filters' option will be used, but
May  9 23:35:12 cmp02 salt-minion[2824]: +# any filter appearing in that option must also be included in this list.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By default, this is set to all filters that are included with nova.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of zero or more strings, where each string corresponds to the name of
May  9 23:35:12 cmp02 salt-minion[2824]: +#   a filter that may be used for selecting a host
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler_enabled_filters
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_available_filters
May  9 23:35:12 cmp02 salt-minion[2824]: +#available_filters=nova.scheduler.filters.all_filters
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filters that the scheduler will use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An ordered list of filter class names that will be used for filtering
May  9 23:35:12 cmp02 salt-minion[2824]: +# hosts. Ignore the word 'default' in the name of this option: these filters
May  9 23:35:12 cmp02 salt-minion[2824]: +# will
May  9 23:35:12 cmp02 salt-minion[2824]: +# *always* be applied, and they will be applied in the order they are listed so
May  9 23:35:12 cmp02 salt-minion[2824]: +# place your most restrictive filters first to make the filtering process more
May  9 23:35:12 cmp02 salt-minion[2824]: +# efficient.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of zero or more strings, where each string corresponds to the name of
May  9 23:35:12 cmp02 salt-minion[2824]: +#   a filter to be used for selecting a host
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * All of the filters in this option *must* be present in the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'scheduler_available_filters' option, or a SchedulerHostFilterNotFound
May  9 23:35:12 cmp02 salt-minion[2824]: +#   exception will be raised.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_default_filters
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled_filters=RetryFilter,AvailabilityZoneFilter,RamFilter,DiskFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filters used for filtering baremetal hosts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filters are applied in order, so place your most restrictive filters first to
May  9 23:35:12 cmp02 salt-minion[2824]: +# make the filtering process more efficient.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of zero or more strings, where each string corresponds to the name of
May  9 23:35:12 cmp02 salt-minion[2824]: +#   a filter to be used for selecting a baremetal host
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If the 'scheduler_use_baremetal_filters' option is False, this option has
May  9 23:35:12 cmp02 salt-minion[2824]: +#   no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/baremetal_scheduler_default_filters
May  9 23:35:12 cmp02 salt-minion[2824]: +#baremetal_enabled_filters=RetryFilter,AvailabilityZoneFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ExactRamFilter,ExactDiskFilter,ExactCoreFilter
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable baremetal filters.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Set this to True to tell the nova scheduler that it should use the filters
May  9 23:35:12 cmp02 salt-minion[2824]: +# specified in the 'baremetal_scheduler_enabled_filters' option. If you are not
May  9 23:35:12 cmp02 salt-minion[2824]: +# scheduling baremetal nodes, leave this at the default setting of False.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If this option is set to True, then the filters specified in the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'baremetal_scheduler_enabled_filters' are used instead of the filters
May  9 23:35:12 cmp02 salt-minion[2824]: +#   specified in 'scheduler_enabled_filters'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_use_baremetal_filters
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_baremetal_filters=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Weighers that the scheduler will use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Only hosts which pass the filters are weighed. The weight for any host starts
May  9 23:35:12 cmp02 salt-minion[2824]: +# at 0, and the weighers order these hosts by adding to or subtracting from the
May  9 23:35:12 cmp02 salt-minion[2824]: +# weight assigned by the previous weigher. Weights may become negative. An
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance will be scheduled to one of the N most-weighted hosts, where N is
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'scheduler_host_subset_size'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By default, this is set to all weighers that are included with Nova.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of zero or more strings, where each string corresponds to the name of
May  9 23:35:12 cmp02 salt-minion[2824]: +#   a weigher that will be used for selecting a host
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_weight_classes
May  9 23:35:12 cmp02 salt-minion[2824]: +#weight_classes=nova.scheduler.weights.all_weighers
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Ram weight multipler ratio.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option determines how hosts with more or less available RAM are weighed.
May  9 23:35:12 cmp02 salt-minion[2824]: +# A
May  9 23:35:12 cmp02 salt-minion[2824]: +# positive value will result in the scheduler preferring hosts with more
May  9 23:35:12 cmp02 salt-minion[2824]: +# available RAM, and a negative number will result in the scheduler preferring
May  9 23:35:12 cmp02 salt-minion[2824]: +# hosts with less available RAM. Another way to look at it is that positive
May  9 23:35:12 cmp02 salt-minion[2824]: +# values for this option will tend to spread instances across many hosts, while
May  9 23:35:12 cmp02 salt-minion[2824]: +# negative values will tend to fill up (stack) hosts as much as possible before
May  9 23:35:12 cmp02 salt-minion[2824]: +# scheduling to a less-used host. The absolute value, whether positive or
May  9 23:35:12 cmp02 salt-minion[2824]: +# negative, controls how strong the RAM weigher is relative to other weighers.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'ram' weigher is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to the multipler
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ratio for this weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ram_weight_multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#ram_weight_multiplier=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Disk weight multipler ratio.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Multiplier used for weighing free disk space. Negative numbers mean to
May  9 23:35:12 cmp02 salt-minion[2824]: +# stack vs spread.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'ram' weigher is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to the multipler
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ratio for this weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/disk_weight_multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#disk_weight_multiplier=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# IO operations weight multipler ratio.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option determines how hosts with differing workloads are weighed.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Negative
May  9 23:35:12 cmp02 salt-minion[2824]: +# values, such as the default, will result in the scheduler preferring hosts
May  9 23:35:12 cmp02 salt-minion[2824]: +# with
May  9 23:35:12 cmp02 salt-minion[2824]: +# lighter workloads whereas positive values will prefer hosts with heavier
May  9 23:35:12 cmp02 salt-minion[2824]: +# workloads. Another way to look at it is that positive values for this option
May  9 23:35:12 cmp02 salt-minion[2824]: +# will tend to schedule instances onto hosts that are already busy, while
May  9 23:35:12 cmp02 salt-minion[2824]: +# negative values will tend to distribute the workload across more hosts. The
May  9 23:35:12 cmp02 salt-minion[2824]: +# absolute value, whether positive or negative, controls how strong the io_ops
May  9 23:35:12 cmp02 salt-minion[2824]: +# weigher is relative to other weighers.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'io_ops' weigher is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to the multipler
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ratio for this weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/io_ops_weight_multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#io_ops_weight_multiplier=-1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Multiplier used for weighing hosts for group soft-affinity.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to weight multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for hosts with group soft affinity. Only a positive value are meaningful, as
May  9 23:35:12 cmp02 salt-minion[2824]: +#   negative values would make this behave as a soft anti-affinity weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/soft_affinity_weight_multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#soft_affinity_weight_multiplier=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Multiplier used for weighing hosts for group soft-anti-affinity.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to weight multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for hosts with group soft anti-affinity. Only a positive value are
May  9 23:35:12 cmp02 salt-minion[2824]: +#   meaningful, as negative values would make this behave as a soft affinity
May  9 23:35:12 cmp02 salt-minion[2824]: +#   weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/soft_anti_affinity_weight_multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#soft_anti_affinity_weight_multiplier=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of UUIDs for images that can only be run on certain hosts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If there is a need to restrict some images to only run on certain designated
May  9 23:35:12 cmp02 salt-minion[2824]: +# hosts, list those image UUIDs here.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'IsolatedHostsFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of UUID strings, where each string corresponds to the UUID of an
May  9 23:35:12 cmp02 salt-minion[2824]: +#   image
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler/isolated_hosts
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler/restrict_isolated_hosts_to_isolated_images
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/isolated_images
May  9 23:35:12 cmp02 salt-minion[2824]: +#isolated_images =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of hosts that can only run certain images.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If there is a need to restrict some images to only run on certain designated
May  9 23:35:12 cmp02 salt-minion[2824]: +# hosts, list those host names here.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'IsolatedHostsFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of strings, where each string corresponds to the name of a host
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler/isolated_images
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler/restrict_isolated_hosts_to_isolated_images
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/isolated_hosts
May  9 23:35:12 cmp02 salt-minion[2824]: +#isolated_hosts =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Prevent non-isolated images from being built on isolated hosts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'IsolatedHostsFilter' filter is enabled. Even
May  9 23:35:12 cmp02 salt-minion[2824]: +# then, this option doesn't affect the behavior of requests for isolated images,
May  9 23:35:12 cmp02 salt-minion[2824]: +# which will *always* be restricted to isolated hosts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler/isolated_images
May  9 23:35:12 cmp02 salt-minion[2824]: +# * scheduler/isolated_hosts
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/restrict_isolated_hosts_to_isolated_images
May  9 23:35:12 cmp02 salt-minion[2824]: +#restrict_isolated_hosts_to_isolated_images=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Image property namespace for use in the host aggregate.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Images and hosts can be configured so that certain images can only be
May  9 23:35:12 cmp02 salt-minion[2824]: +# scheduled
May  9 23:35:12 cmp02 salt-minion[2824]: +# to hosts in a particular aggregate. This is done with metadata values set on
May  9 23:35:12 cmp02 salt-minion[2824]: +# the host aggregate that are identified by beginning with the value of this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option. If the host is part of an aggregate with such a metadata key, the
May  9 23:35:12 cmp02 salt-minion[2824]: +# image
May  9 23:35:12 cmp02 salt-minion[2824]: +# in the request spec must have the value of that metadata in its properties in
May  9 23:35:12 cmp02 salt-minion[2824]: +# order for the scheduler to consider the host as acceptable.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'aggregate_image_properties_isolation' filter
May  9 23:35:12 cmp02 salt-minion[2824]: +# is
May  9 23:35:12 cmp02 salt-minion[2824]: +# enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string, where the string corresponds to an image property namespace
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * aggregate_image_properties_isolation_separator
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/aggregate_image_properties_isolation_namespace
May  9 23:35:12 cmp02 salt-minion[2824]: +#aggregate_image_properties_isolation_namespace=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Separator character(s) for image property namespace and name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When using the aggregate_image_properties_isolation filter, the relevant
May  9 23:35:12 cmp02 salt-minion[2824]: +# metadata keys are prefixed with the namespace defined in the
May  9 23:35:12 cmp02 salt-minion[2824]: +# aggregate_image_properties_isolation_namespace configuration option plus a
May  9 23:35:12 cmp02 salt-minion[2824]: +# separator. This option defines the separator to be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'aggregate_image_properties_isolation' filter
May  9 23:35:12 cmp02 salt-minion[2824]: +# is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string, where the string corresponds to an image property namespace
May  9 23:35:12 cmp02 salt-minion[2824]: +#   separator character
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * aggregate_image_properties_isolation_namespace
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/aggregate_image_properties_isolation_separator
May  9 23:35:12 cmp02 salt-minion[2824]: +#aggregate_image_properties_isolation_separator=.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[glance]
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration options for the Image service
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of glance api servers endpoints available to nova.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# https is used for ssl-based glance api servers.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of any fully qualified url of the form
May  9 23:35:12 cmp02 salt-minion[2824]: +# "scheme://hostname:port[/path]"
May  9 23:35:12 cmp02 salt-minion[2824]: +#   (i.e. "http://10.0.1.0:9292" or "https://my.glance.server/image").
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#api_servers=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +api_servers = http://172.16.10.36:9292
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable insecure SSL (https) requests to glance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This setting can be used to turn off verification of the glance server
May  9 23:35:12 cmp02 salt-minion[2824]: +# certificate against the certificate authorities.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#api_insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable glance operation retries.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specifies the number of retries when uploading / downloading
May  9 23:35:12 cmp02 salt-minion[2824]: +# an image to / from glance. 0 means no retries.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#num_retries=0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of url schemes that can be directly accessed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies a list of url schemes that can be downloaded
May  9 23:35:12 cmp02 salt-minion[2824]: +# directly via the direct_url. This direct_URL can be fetched from
May  9 23:35:12 cmp02 salt-minion[2824]: +# Image metadata which can be used by nova to get the
May  9 23:35:12 cmp02 salt-minion[2824]: +# image more efficiently. nova-compute could benefit from this by
May  9 23:35:12 cmp02 salt-minion[2824]: +# invoking a copy when it has access to the same file system as glance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * [file], Empty list (default)
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#allowed_direct_url_schemes =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable image signature verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova uses the image signature metadata from glance and verifies the signature
May  9 23:35:12 cmp02 salt-minion[2824]: +# of a signed image while downloading that image. If the image signature cannot
May  9 23:35:12 cmp02 salt-minion[2824]: +# be verified or if the image signature metadata is either incomplete or
May  9 23:35:12 cmp02 salt-minion[2824]: +# unavailable, then nova will not boot the image and instead will place the
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance into an error state. This provides end users with stronger assurances
May  9 23:35:12 cmp02 salt-minion[2824]: +# of the integrity of the image data they are using to create servers.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The options in the `key_manager` group, as the key_manager is used
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for the signature validation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#verify_glance_signatures=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable or disable debug logging with glanceclient. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#debug=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[guestfs]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# libguestfs is a set of tools for accessing and modifying virtual
May  9 23:35:12 cmp02 salt-minion[2824]: +# machine (VM) disk images. You can use this for viewing and editing
May  9 23:35:12 cmp02 salt-minion[2824]: +# files inside guests, scripting changes to VMs, monitoring disk
May  9 23:35:12 cmp02 salt-minion[2824]: +# used/free statistics, creating guests, P2V, V2V, performing backups,
May  9 23:35:12 cmp02 salt-minion[2824]: +# cloning VMs, building VMs, formatting disks and resizing disks.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable/disables guestfs logging.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This configures guestfs to debug messages and push them to Openstack
May  9 23:35:12 cmp02 salt-minion[2824]: +# logging system. When set to True, it traces libguestfs API calls and
May  9 23:35:12 cmp02 salt-minion[2824]: +# enable verbose debug messages. In order to use the above feature,
May  9 23:35:12 cmp02 salt-minion[2824]: +# "libguestfs" package must be installed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Since libguestfs access and modifies VM's managed by libvirt, below options
May  9 23:35:12 cmp02 salt-minion[2824]: +# should be set to give access to those VM's.
May  9 23:35:12 cmp02 salt-minion[2824]: +#     * libvirt.inject_key
May  9 23:35:12 cmp02 salt-minion[2824]: +#     * libvirt.inject_partition
May  9 23:35:12 cmp02 salt-minion[2824]: +#     * libvirt.inject_password
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#debug=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [healthcheck]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -466,10 +5071,10 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The path to respond to healtcheck requests on. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: -#path = /healthcheck
May  9 23:35:12 cmp02 salt-minion[2824]: +#path=/healthcheck
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Show more detailed information as part of the response (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#detailed = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#detailed=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Additional backends that can perform health checks and report that information
May  9 23:35:12 cmp02 salt-minion[2824]:  # back as part of a request. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -477,7 +5082,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Check the presence of a file to determine if an application is running on a
May  9 23:35:12 cmp02 salt-minion[2824]:  # port. Used by DisableByFileHealthcheck plugin. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#disable_by_file_path = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#disable_by_file_path=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Check the presence of a file based on a port to determine if an application is
May  9 23:35:12 cmp02 salt-minion[2824]:  # running on a port. Expects a "port:path" list of strings. Used by
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -485,57 +5090,490 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #disable_by_file_paths =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: +[hyperv]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The hyperv feature allows you to configure the Hyper-V hypervisor
May  9 23:35:12 cmp02 salt-minion[2824]: +# driver to be used within an OpenStack deployment.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Dynamic memory ratio
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enables dynamic memory allocation (ballooning) when set to a value
May  9 23:35:12 cmp02 salt-minion[2824]: +# greater than 1. The value expresses the ratio between the total RAM
May  9 23:35:12 cmp02 salt-minion[2824]: +# assigned to an instance and its startup RAM amount. For example a
May  9 23:35:12 cmp02 salt-minion[2824]: +# ratio of 2.0 for an instance with 1024MB of RAM implies 512MB of
May  9 23:35:12 cmp02 salt-minion[2824]: +# RAM allocated at startup.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 1.0: Disables dynamic memory allocation (Default).
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Float values greater than 1.0: Enables allocation of total implied
May  9 23:35:12 cmp02 salt-minion[2824]: +#   RAM divided by this value for startup.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#dynamic_memory_ratio=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable instance metrics collection
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enables metrics collections for an instance by using Hyper-V's
May  9 23:35:12 cmp02 salt-minion[2824]: +# metric APIs. Collected data can by retrieved by other apps and
May  9 23:35:12 cmp02 salt-minion[2824]: +# services, e.g.: Ceilometer.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enable_instance_metrics_collection=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Instances path share
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The name of a Windows share mapped to the "instances_path" dir
May  9 23:35:12 cmp02 salt-minion[2824]: +# and used by the resize feature to copy files to the target host.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If left blank, an administrative share (hidden network share) will
May  9 23:35:12 cmp02 salt-minion[2824]: +# be used, looking for the same "instances_path" used locally.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * "": An administrative share will be used (Default).
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Name of a Windows share.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * "instances_path": The directory which will be used if this option
May  9 23:35:12 cmp02 salt-minion[2824]: +#   here is left blank.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#instances_path_share =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Limit CPU features
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This flag is needed to support live migration to hosts with
May  9 23:35:12 cmp02 salt-minion[2824]: +# different CPU features and checked during instance creation
May  9 23:35:12 cmp02 salt-minion[2824]: +# in order to limit the CPU features used by the instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#limit_cpu_features=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mounted disk query retry count
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of times to retry checking for a mounted disk.
May  9 23:35:12 cmp02 salt-minion[2824]: +# The query runs until the device can be found or the retry
May  9 23:35:12 cmp02 salt-minion[2824]: +# count is reached.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Positive integer values. Values greater than 1 is recommended
May  9 23:35:12 cmp02 salt-minion[2824]: +#   (Default: 10).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Time interval between disk mount retries is declared with
May  9 23:35:12 cmp02 salt-minion[2824]: +#   "mounted_disk_query_retry_interval" option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#mounted_disk_query_retry_count=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mounted disk query retry interval
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Interval between checks for a mounted disk, in seconds.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Time in seconds (Default: 5).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option is meaningful when the mounted_disk_query_retry_count
May  9 23:35:12 cmp02 salt-minion[2824]: +#   is greater than 1.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The retry loop runs with mounted_disk_query_retry_count and
May  9 23:35:12 cmp02 salt-minion[2824]: +#   mounted_disk_query_retry_interval configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#mounted_disk_query_retry_interval=5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Power state check timeframe
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The timeframe to be checked for instance power state changes.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is used to fetch the state of the instance from Hyper-V
May  9 23:35:12 cmp02 salt-minion[2824]: +# through the WMI interface, within the specified timeframe.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Timeframe in seconds (Default: 60).
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#power_state_check_timeframe=60
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Power state event polling interval
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Instance power state change event polling frequency. Sets the
May  9 23:35:12 cmp02 salt-minion[2824]: +# listener interval for power state events to the given value.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option enhances the internal lifecycle notifications of
May  9 23:35:12 cmp02 salt-minion[2824]: +# instances that reboot themselves. It is unlikely that an operator
May  9 23:35:12 cmp02 salt-minion[2824]: +# has to change this value.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Time in seconds (Default: 2).
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#power_state_event_polling_interval=2
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# qemu-img command
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# qemu-img is required for some of the image related operations
May  9 23:35:12 cmp02 salt-minion[2824]: +# like converting between different image types. You can get it
May  9 23:35:12 cmp02 salt-minion[2824]: +# from here: (http://qemu.weilnetz.de/) or you can install the
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cloudbase OpenStack Hyper-V Compute Driver
May  9 23:35:12 cmp02 salt-minion[2824]: +# (https://cloudbase.it/openstack-hyperv-driver/) which automatically
May  9 23:35:12 cmp02 salt-minion[2824]: +# sets the proper path for this config option. You can either give the
May  9 23:35:12 cmp02 salt-minion[2824]: +# full path of qemu-img.exe or set its path in the PATH environment
May  9 23:35:12 cmp02 salt-minion[2824]: +# variable and leave this option to the default value.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Name of the qemu-img executable, in case it is in the same
May  9 23:35:12 cmp02 salt-minion[2824]: +#   directory as the nova-compute service or its path is in the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   PATH environment variable (Default).
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Path of qemu-img command (DRIVELETTER:\PATH\TO\QEMU-IMG\COMMAND).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If the config_drive_cdrom option is False, qemu-img will be used to
May  9 23:35:12 cmp02 salt-minion[2824]: +#   convert the ISO to a VHD, otherwise the configuration drive will
May  9 23:35:12 cmp02 salt-minion[2824]: +#   remain an ISO. To use configuration drive with Hyper-V, you must
May  9 23:35:12 cmp02 salt-minion[2824]: +#   set the mkisofs_cmd value to the full path to an mkisofs.exe
May  9 23:35:12 cmp02 salt-minion[2824]: +#   installation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#qemu_img_cmd=qemu-img.exe
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# External virtual switch name
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The Hyper-V Virtual Switch is a software-based layer-2 Ethernet
May  9 23:35:12 cmp02 salt-minion[2824]: +# network switch that is available with the installation of the
May  9 23:35:12 cmp02 salt-minion[2824]: +# Hyper-V server role. The switch includes programmatically managed
May  9 23:35:12 cmp02 salt-minion[2824]: +# and extensible capabilities to connect virtual machines to both
May  9 23:35:12 cmp02 salt-minion[2824]: +# virtual networks and the physical network. In addition, Hyper-V
May  9 23:35:12 cmp02 salt-minion[2824]: +# Virtual Switch provides policy enforcement for security, isolation,
May  9 23:35:12 cmp02 salt-minion[2824]: +# and service levels. The vSwitch represented by this config option
May  9 23:35:12 cmp02 salt-minion[2824]: +# must be an external one (not internal or private).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If not provided, the first of a list of available vswitches
May  9 23:35:12 cmp02 salt-minion[2824]: +#   is used. This list is queried using WQL.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Virtual switch name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vswitch_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Wait soft reboot seconds
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds to wait for instance to shut down after soft
May  9 23:35:12 cmp02 salt-minion[2824]: +# reboot request is made. We fall back to hard reboot if instance
May  9 23:35:12 cmp02 salt-minion[2824]: +# does not shutdown within this window.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Time in seconds (Default: 60).
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#wait_soft_reboot_seconds=60
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration drive cdrom
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# OpenStack can be configured to write instance metadata to
May  9 23:35:12 cmp02 salt-minion[2824]: +# a configuration drive, which is then attached to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance before it boots. The configuration drive can be
May  9 23:35:12 cmp02 salt-minion[2824]: +# attached as a disk drive (default) or as a CD drive.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * True: Attach the configuration drive image as a CD drive.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * False: Attach the configuration drive image as a disk drive (Default).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option is meaningful with force_config_drive option set to 'True'
May  9 23:35:12 cmp02 salt-minion[2824]: +#   or when the REST API call to create an instance will have
May  9 23:35:12 cmp02 salt-minion[2824]: +#   '--config-drive=True' flag.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * config_drive_format option must be set to 'iso9660' in order to use
May  9 23:35:12 cmp02 salt-minion[2824]: +#   CD drive as the configuration drive image.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * To use configuration drive with Hyper-V, you must set the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   mkisofs_cmd value to the full path to an mkisofs.exe installation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   Additionally, you must set the qemu_img_cmd value to the full path
May  9 23:35:12 cmp02 salt-minion[2824]: +#   to an qemu-img command installation.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * You can configure the Compute service to always create a configuration
May  9 23:35:12 cmp02 salt-minion[2824]: +#   drive by setting the force_config_drive option to 'True'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#config_drive_cdrom=false
May  9 23:35:12 cmp02 salt-minion[2824]: +config_drive_cdrom=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration drive inject password
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enables setting the admin password in the configuration drive image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option is meaningful when used with other options that enable
May  9 23:35:12 cmp02 salt-minion[2824]: +#   configuration drive usage with Hyper-V, such as force_config_drive.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Currently, the only accepted config_drive_format is 'iso9660'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#config_drive_inject_password=false
May  9 23:35:12 cmp02 salt-minion[2824]: +config_drive_inject_password=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Volume attach retry count
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of times to retry attaching a volume. Volume attachment
May  9 23:35:12 cmp02 salt-minion[2824]: +# is retried until success or the given retry count is reached.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Positive integer values (Default: 10).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Time interval between attachment attempts is declared with
May  9 23:35:12 cmp02 salt-minion[2824]: +#   volume_attach_retry_interval option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#volume_attach_retry_count=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Volume attach retry interval
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Interval between volume attachment attempts, in seconds.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Time in seconds (Default: 5).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This options is meaningful when volume_attach_retry_count
May  9 23:35:12 cmp02 salt-minion[2824]: +#   is greater than 1.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The retry loop runs with volume_attach_retry_count and
May  9 23:35:12 cmp02 salt-minion[2824]: +#   volume_attach_retry_interval configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#volume_attach_retry_interval=5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable RemoteFX feature
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This requires at least one DirectX 11 capable graphics adapter for
May  9 23:35:12 cmp02 salt-minion[2824]: +# Windows / Hyper-V Server 2012 R2 or newer and RDS-Virtualization
May  9 23:35:12 cmp02 salt-minion[2824]: +# feature has to be enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Instances with RemoteFX can be requested with the following flavor
May  9 23:35:12 cmp02 salt-minion[2824]: +# extra specs:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# **os:resolution**. Guest VM screen resolution size. Acceptable values::
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     1024x768, 1280x1024, 1600x1200, 1920x1200, 2560x1600, 3840x2160
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# ``3840x2160`` is only available on Windows / Hyper-V Server 2016.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# **os:monitors**. Guest VM number of monitors. Acceptable values::
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     [1, 4] - Windows / Hyper-V Server 2012 R2
May  9 23:35:12 cmp02 salt-minion[2824]: +#     [1, 8] - Windows / Hyper-V Server 2016
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# **os:vram**. Guest VM VRAM amount. Only available on
May  9 23:35:12 cmp02 salt-minion[2824]: +# Windows / Hyper-V Server 2016. Acceptable values::
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     64, 128, 256, 512, 1024
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enable_remotefx=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use multipath connections when attaching iSCSI or FC disks.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This requires the Multipath IO Windows feature to be enabled. MPIO must be
May  9 23:35:12 cmp02 salt-minion[2824]: +# configured to claim such devices.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_multipath_io=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of iSCSI initiators that will be used for estabilishing iSCSI sessions.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If none are specified, the Microsoft iSCSI initiator service will choose the
May  9 23:35:12 cmp02 salt-minion[2824]: +# initiator.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#iscsi_initiator_list =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[image_file_url]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of file systems that are configured in this file in the
May  9 23:35:12 cmp02 salt-minion[2824]: +# image_file_url:<list entry name> sections
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The feature to download images from glance via filesystem is not used and will
May  9 23:35:12 cmp02 salt-minion[2824]: +# be removed in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +#filesystems =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: message repeated 4 times: [ +]
May  9 23:35:12 cmp02 salt-minion[2824]: +[key_manager]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Fixed key returned by key manager, specified in hex.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Empty string or a key in hex value
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [keymgr]/fixed_key
May  9 23:35:12 cmp02 salt-minion[2824]: +#fixed_key=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# The full class name of the key manager API class (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# The type of authentication credential to create. Possible values are 'token',
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'password', 'keystone_token', and 'keystone_password'. Required if no context
May  9 23:35:12 cmp02 salt-minion[2824]: +# is passed to the credential factory. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Token for authentication. Required for 'token' and 'keystone_token' auth_type
May  9 23:35:12 cmp02 salt-minion[2824]: +# if no context is passed to the credential factory. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#token=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username for authentication. Required for 'password' auth_type. Optional for
May  9 23:35:12 cmp02 salt-minion[2824]: +# the 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#username=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Password for authentication. Required for 'password' and 'keystone_password'
May  9 23:35:12 cmp02 salt-minion[2824]: +# auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User ID for authentication. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain ID for authentication. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain name for authentication. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Trust ID for trust scoping. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#trust_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID for domain scoping. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name for domain scoping. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project ID for project scoping. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project name for project scoping. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project's domain ID for project. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project's domain name for project. Optional for 'keystone_token' and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_password' auth_type. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allow fetching a new token if the current one is going to expire. Optional for
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'keystone_token' and 'keystone_password' auth_type. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#reauthenticate=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  [keystone_authtoken]
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # From keystonemiddleware.auth_token
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: +signing_dirname=/tmp/keystone-signing-nova
May  9 23:35:12 cmp02 salt-minion[2824]: +revocation_cache_time = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_type = password
May  9 23:35:12 cmp02 salt-minion[2824]: +user_domain_id = default
May  9 23:35:12 cmp02 salt-minion[2824]: +project_domain_id = default
May  9 23:35:12 cmp02 salt-minion[2824]: +project_name = service
May  9 23:35:12 cmp02 salt-minion[2824]: +username = nova
May  9 23:35:12 cmp02 salt-minion[2824]: +password = opnfv_secret
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_uri=http://172.16.10.36:5000
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_url=http://172.16.10.36:35357
May  9 23:35:12 cmp02 salt-minion[2824]: +memcached_servers=172.16.10.36:11211,172.16.10.37:11211,172.16.10.38:11211,127.0.0.1:11211
May  9 23:35:12 cmp02 salt-minion[2824]:  # Complete "public" Identity API endpoint. This endpoint should not be an
May  9 23:35:12 cmp02 salt-minion[2824]:  # "admin" endpoint, as it should be accessible by all end users. Unauthenticated
May  9 23:35:12 cmp02 salt-minion[2824]:  # clients are redirected to this endpoint to authenticate. Although this
May  9 23:35:12 cmp02 salt-minion[2824]: -# endpoint should ideally be unversioned, client support in the wild varies. If
May  9 23:35:12 cmp02 salt-minion[2824]: -# you're using a versioned v2 endpoint here, then this should *not* be the same
May  9 23:35:12 cmp02 salt-minion[2824]: -# endpoint the service user utilizes for validating tokens, because normal end
May  9 23:35:12 cmp02 salt-minion[2824]: -# users may not be able to reach that endpoint. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_uri = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +# endpoint should  ideally be unversioned, client support in the wild varies.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If you're using a versioned v2 endpoint here, then this  should *not* be the
May  9 23:35:12 cmp02 salt-minion[2824]: +# same endpoint the service user utilizes  for validating tokens, because normal
May  9 23:35:12 cmp02 salt-minion[2824]: +# end users may not be  able to reach that endpoint. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_uri=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # API version of the admin Identity API endpoint. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_version = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_version=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Do not handle authorization requests within the middleware, but delegate the
May  9 23:35:12 cmp02 salt-minion[2824]:  # authorization decision to downstream WSGI components. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#delay_auth_decision = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#delay_auth_decision=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Request timeout value for communicating with Identity API server. (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#http_connect_timeout = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#http_connect_timeout=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How many times are we trying to reconnect when communicating with Identity API
May  9 23:35:12 cmp02 salt-minion[2824]:  # Server. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#http_request_max_retries = 3
May  9 23:35:12 cmp02 salt-minion[2824]: +#http_request_max_retries=3
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Request environment key where the Swift cache object is stored. When
May  9 23:35:12 cmp02 salt-minion[2824]:  # auth_token middleware is deployed with a Swift cache, use this option to have
May  9 23:35:12 cmp02 salt-minion[2824]:  # the middleware share a caching backend with swift. Otherwise, use the
May  9 23:35:12 cmp02 salt-minion[2824]:  # ``memcached_servers`` option instead. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#cache = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#cache=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Required if identity server requires client certificate (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#certfile = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#certfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Required if identity server requires client certificate (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#keyfile = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#keyfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # A PEM encoded Certificate Authority to use when verifying HTTPs connections.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Defaults to system CAs. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#cafile = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#cafile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Verify HTTPS connections. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#insecure = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The region in which the identity server can be found. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#region_name = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#region_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Directory used to cache files related to PKI tokens. This option
May  9 23:35:12 cmp02 salt-minion[2824]:  # has been deprecated in the Ocata release and will be removed in the P release.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -543,17 +5581,17 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal since Ocata.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: PKI token format is no longer supported.
May  9 23:35:12 cmp02 salt-minion[2824]: -#signing_dir = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#signing_dir=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Optionally specify a list of memcached server(s) to use for caching. If left
May  9 23:35:12 cmp02 salt-minion[2824]:  # undefined, tokens will instead be cached in-process. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [keystone_authtoken]/memcache_servers
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcached_servers = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcached_servers=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # In order to prevent excessive effort spent validating tokens, the middleware
May  9 23:35:12 cmp02 salt-minion[2824]:  # caches previously-seen tokens for a configurable duration (in seconds). Set to
May  9 23:35:12 cmp02 salt-minion[2824]:  # -1 to disable caching completely. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#token_cache_time = 300
May  9 23:35:12 cmp02 salt-minion[2824]: +#token_cache_time=300
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Determines the frequency at which the list of revoked tokens is
May  9 23:35:12 cmp02 salt-minion[2824]:  # retrieved from the Identity service (in seconds). A high number of revocation
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -563,7 +5601,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal since Ocata.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: PKI token format is no longer supported.
May  9 23:35:12 cmp02 salt-minion[2824]: -#revocation_cache_time = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#revocation_cache_time=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) If defined, indicate whether token data should be authenticated or
May  9 23:35:12 cmp02 salt-minion[2824]:  # authenticated and encrypted. If MAC, token data is authenticated (with HMAC)
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -571,40 +5609,40 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # cache. If the value is not one of these options or empty, auth_token will
May  9 23:35:12 cmp02 salt-minion[2824]:  # raise an exception on initialization. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: None, MAC, ENCRYPT
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_security_strategy = None
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_security_strategy=None
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional, mandatory if memcache_security_strategy is defined) This string is
May  9 23:35:12 cmp02 salt-minion[2824]:  # used for key derivation. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_secret_key = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_secret_key=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Number of seconds memcached server is considered dead before it is
May  9 23:35:12 cmp02 salt-minion[2824]:  # tried again. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_pool_dead_retry = 300
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_pool_dead_retry=300
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Maximum total number of open connections to every memcached server.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_pool_maxsize = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_pool_maxsize=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Socket timeout in seconds for communicating with a memcached
May  9 23:35:12 cmp02 salt-minion[2824]:  # server. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_pool_socket_timeout = 3
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_pool_socket_timeout=3
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Number of seconds a connection to memcached is held unused in the
May  9 23:35:12 cmp02 salt-minion[2824]:  # pool before it is closed. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_pool_unused_timeout = 60
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_pool_unused_timeout=60
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Number of seconds that an operation will wait to get a memcached
May  9 23:35:12 cmp02 salt-minion[2824]:  # client connection from the pool. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_pool_conn_get_timeout = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_pool_conn_get_timeout=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Use the advanced (eventlet safe) memcached client pool. The
May  9 23:35:12 cmp02 salt-minion[2824]:  # advanced pool will only work under python 2.x. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#memcache_use_advanced_pool = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#memcache_use_advanced_pool=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # (Optional) Indicate whether to set the X-Service-Catalog header. If False,
May  9 23:35:12 cmp02 salt-minion[2824]:  # middleware will not ask for service catalog on token validation and will not
May  9 23:35:12 cmp02 salt-minion[2824]:  # set the X-Service-Catalog header. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#include_service_catalog = true
May  9 23:35:12 cmp02 salt-minion[2824]: +#include_service_catalog=true
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Used to control the use and type of token binding. Can be set to: "disabled"
May  9 23:35:12 cmp02 salt-minion[2824]:  # to not check token binding. "permissive" (default) to validate binding
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -613,7 +5651,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # be rejected. "required" any form of token binding is needed to be allowed.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Finally the name of a binding method that must be present in tokens. (string
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#enforce_token_bind = permissive
May  9 23:35:12 cmp02 salt-minion[2824]: +#enforce_token_bind=permissive
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: If true, the revocation list will be checked for cached tokens.
May  9 23:35:12 cmp02 salt-minion[2824]:  # This requires that PKI tokens are configured on the identity server. (boolean
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -621,7 +5659,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal since Ocata.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: PKI token format is no longer supported.
May  9 23:35:12 cmp02 salt-minion[2824]: -#check_revocations_for_cached = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#check_revocations_for_cached=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Hash algorithms to use for hashing PKI tokens. This may be a
May  9 23:35:12 cmp02 salt-minion[2824]:  # single algorithm or multiple. The algorithms are those supported by Python
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -634,7 +5672,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal since Ocata.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: PKI token format is no longer supported.
May  9 23:35:12 cmp02 salt-minion[2824]: -#hash_algorithms = md5
May  9 23:35:12 cmp02 salt-minion[2824]: +#hash_algorithms=md5
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # A choice of roles that must be present in a service token. Service tokens are
May  9 23:35:12 cmp02 salt-minion[2824]:  # allowed to request that an expired token can be used and so this check should
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -642,13 +5680,13 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # here are applied as an ANY check so any role in this list must be present. For
May  9 23:35:12 cmp02 salt-minion[2824]:  # backwards compatibility reasons this currently only affects the allow_expired
May  9 23:35:12 cmp02 salt-minion[2824]:  # check. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#service_token_roles = service
May  9 23:35:12 cmp02 salt-minion[2824]: +#service_token_roles=service
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # For backwards compatibility reasons we must let valid service tokens pass that
May  9 23:35:12 cmp02 salt-minion[2824]:  # don't pass the service_token_roles check as valid. Setting this true will
May  9 23:35:12 cmp02 salt-minion[2824]:  # become the default in a future release and should be enabled if possible.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#service_token_roles_required = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#service_token_roles_required=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Prefix to prepend at the beginning of the path. Deprecated, use identity_uri.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -656,43 +5694,1007 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Host providing the admin Identity API endpoint. Deprecated, use identity_uri.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_host = 127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_host=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Port of the admin Identity API endpoint. Deprecated, use identity_uri.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_port = 35357
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_port=35357
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Protocol of the admin Identity API endpoint. Deprecated, use identity_uri.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: http, https
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_protocol = https
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_protocol=https
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Complete admin Identity API endpoint. This should specify the unversioned root
May  9 23:35:12 cmp02 salt-minion[2824]:  # endpoint e.g. https://localhost:35357/ (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#identity_uri = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#identity_uri=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated and may be removed in a future release. Single
May  9 23:35:12 cmp02 salt-minion[2824]:  # shared secret with the Keystone configuration used for bootstrapping a
May  9 23:35:12 cmp02 salt-minion[2824]:  # Keystone installation, or otherwise bypassing the normal authentication
May  9 23:35:12 cmp02 salt-minion[2824]:  # process. This option should not be used, use `admin_user` and `admin_password`
May  9 23:35:12 cmp02 salt-minion[2824]:  # instead. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_token = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#admin_token=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Service username. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_user = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#admin_user=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Service user password. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_password = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#admin_password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Service tenant name. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_tenant_name = admin
May  9 23:35:12 cmp02 salt-minion[2824]: +#admin_tenant_name=admin
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Authentication type to load (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [keystone_authtoken]/auth_plugin
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_type = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Config Section from which to load plugin specific options (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#auth_section = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_section=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[libvirt]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Libvirt options allows cloud administrator to configure related
May  9 23:35:12 cmp02 salt-minion[2824]: +# libvirt hypervisor driver to be used within an OpenStack deployment.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Almost all of the libvirt config options are influence by ``virt_type`` config
May  9 23:35:12 cmp02 salt-minion[2824]: +# which describes the virtualization type (or so called domain type) libvirt
May  9 23:35:12 cmp02 salt-minion[2824]: +# should use for specific features such as live migration, snapshot.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +cpu_mode = host-passthrough
May  9 23:35:12 cmp02 salt-minion[2824]: +virt_type = kvm
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +inject_partition=-2
May  9 23:35:12 cmp02 salt-minion[2824]: +inject_password=False
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +disk_cachemodes="file=directsync,block=none"
May  9 23:35:12 cmp02 salt-minion[2824]: +block_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE,VIR_MIGRATE_NON_SHARED_INC
May  9 23:35:12 cmp02 salt-minion[2824]: +live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE,VIR_MIGRATE_PERSIST_DEST
May  9 23:35:12 cmp02 salt-minion[2824]: +inject_key=True
May  9 23:35:12 cmp02 salt-minion[2824]: +vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ID of the image to boot from to rescue data from a corrupted instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If the rescue REST API operation doesn't provide an ID of an image to
May  9 23:35:12 cmp02 salt-minion[2824]: +# use, the image which is referenced by this ID is used. If this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option is not set, the image from the instance is used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An ID of an image or nothing. If it points to an *Amazon Machine
May  9 23:35:12 cmp02 salt-minion[2824]: +#   Image* (AMI), consider to set the config options ``rescue_kernel_id``
May  9 23:35:12 cmp02 salt-minion[2824]: +#   and ``rescue_ramdisk_id`` too. If nothing is set, the image of the instance
May  9 23:35:12 cmp02 salt-minion[2824]: +#   is used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``rescue_kernel_id``: If the chosen rescue image allows the separate
May  9 23:35:12 cmp02 salt-minion[2824]: +#   definition of its kernel disk, the value of this option is used,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   if specified. This is the case when *Amazon*'s AMI/AKI/ARI image
May  9 23:35:12 cmp02 salt-minion[2824]: +#   format is used for the rescue image.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``rescue_ramdisk_id``: If the chosen rescue image allows the separate
May  9 23:35:12 cmp02 salt-minion[2824]: +#   definition of its RAM disk, the value of this option is used if,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   specified. This is the case when *Amazon*'s AMI/AKI/ARI image
May  9 23:35:12 cmp02 salt-minion[2824]: +#   format is used for the rescue image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#rescue_image_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ID of the kernel (AKI) image to use with the rescue image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If the chosen rescue image allows the separate definition of its kernel
May  9 23:35:12 cmp02 salt-minion[2824]: +# disk, the value of this option is used, if specified. This is the case
May  9 23:35:12 cmp02 salt-minion[2824]: +# when *Amazon*'s AMI/AKI/ARI image format is used for the rescue image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An ID of an kernel image or nothing. If nothing is specified, the kernel
May  9 23:35:12 cmp02 salt-minion[2824]: +#   disk from the instance is used if it was launched with one.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``rescue_image_id``: If that option points to an image in *Amazon*'s
May  9 23:35:12 cmp02 salt-minion[2824]: +#   AMI/AKI/ARI image format, it's useful to use ``rescue_kernel_id`` too.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#rescue_kernel_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ID of the RAM disk (ARI) image to use with the rescue image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If the chosen rescue image allows the separate definition of its RAM
May  9 23:35:12 cmp02 salt-minion[2824]: +# disk, the value of this option is used, if specified. This is the case
May  9 23:35:12 cmp02 salt-minion[2824]: +# when *Amazon*'s AMI/AKI/ARI image format is used for the rescue image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An ID of a RAM disk image or nothing. If nothing is specified, the RAM
May  9 23:35:12 cmp02 salt-minion[2824]: +#   disk from the instance is used if it was launched with one.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``rescue_image_id``: If that option points to an image in *Amazon*'s
May  9 23:35:12 cmp02 salt-minion[2824]: +#   AMI/AKI/ARI image format, it's useful to use ``rescue_ramdisk_id`` too.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#rescue_ramdisk_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Describes the virtualization type (or so called domain type) libvirt should
May  9 23:35:12 cmp02 salt-minion[2824]: +# use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The choice of this type must match the underlying virtualization strategy
May  9 23:35:12 cmp02 salt-minion[2824]: +# you have chosen for this host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * See the predefined set of case-sensitive values.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``connection_uri``: depends on this
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``disk_prefix``: depends on this
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``cpu_mode``: depends on this
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``cpu_model``: depends on this
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: kvm, lxc, qemu, uml, xen, parallels
May  9 23:35:12 cmp02 salt-minion[2824]: +#virt_type=kvm
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Overrides the default libvirt URI of the chosen virtualization type.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set, Nova will use this URI to connect to libvirt.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An URI like ``qemu:///system`` or ``xen+ssh://oirase/`` for example.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   This is only necessary if the URI differs to the commonly known URIs
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for the chosen virtualization type.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``virt_type``: Influences what is used as default value here.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_uri =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allow the injection of an admin password for instance only at ``create`` and
May  9 23:35:12 cmp02 salt-minion[2824]: +# ``rebuild`` process.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# There is no agent needed within the image to do this. If *libguestfs* is
May  9 23:35:12 cmp02 salt-minion[2824]: +# available on the host, it will be used. Otherwise *nbd* is used. The file
May  9 23:35:12 cmp02 salt-minion[2824]: +# system of the image will be mounted and the admin password, which is provided
May  9 23:35:12 cmp02 salt-minion[2824]: +# in the REST API call will be injected as password for the root user. If no
May  9 23:35:12 cmp02 salt-minion[2824]: +# root user is available, the instance won't be launched and an error is thrown.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Be aware that the injection is *not* possible when the instance gets launched
May  9 23:35:12 cmp02 salt-minion[2824]: +# from a volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * True: Allows the injection.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * False (default): Disallows the injection. Any via the REST API provided
May  9 23:35:12 cmp02 salt-minion[2824]: +# admin password will be silently ignored.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``inject_partition``: That option will decide about the discovery and usage
May  9 23:35:12 cmp02 salt-minion[2824]: +#   of the file system. It also can disable the injection at all.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#inject_password=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allow the injection of an SSH key at boot time.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# There is no agent needed within the image to do this. If *libguestfs* is
May  9 23:35:12 cmp02 salt-minion[2824]: +# available on the host, it will be used. Otherwise *nbd* is used. The file
May  9 23:35:12 cmp02 salt-minion[2824]: +# system of the image will be mounted and the SSH key, which is provided
May  9 23:35:12 cmp02 salt-minion[2824]: +# in the REST API call will be injected as SSH key for the root user and
May  9 23:35:12 cmp02 salt-minion[2824]: +# appended to the ``authorized_keys`` of that user. The SELinux context will
May  9 23:35:12 cmp02 salt-minion[2824]: +# be set if necessary. Be aware that the injection is *not* possible when the
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance gets launched from a volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This config option will enable directly modifying the instance disk and does
May  9 23:35:12 cmp02 salt-minion[2824]: +# not affect what cloud-init may do using data from config_drive option or the
May  9 23:35:12 cmp02 salt-minion[2824]: +# metadata service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``inject_partition``: That option will decide about the discovery and usage
May  9 23:35:12 cmp02 salt-minion[2824]: +#   of the file system. It also can disable the injection at all.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#inject_key=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Determines the way how the file system is chosen to inject data into it.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# *libguestfs* will be used a first solution to inject data. If that's not
May  9 23:35:12 cmp02 salt-minion[2824]: +# available on the host, the image will be locally mounted on the host as a
May  9 23:35:12 cmp02 salt-minion[2824]: +# fallback solution. If libguestfs is not able to determine the root partition
May  9 23:35:12 cmp02 salt-minion[2824]: +# (because there are more or less than one root partition) or cannot mount the
May  9 23:35:12 cmp02 salt-minion[2824]: +# file system it will result in an error and the instance won't be boot.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -2 => disable the injection of data.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 => find the root partition with the file system to mount with libguestfs
May  9 23:35:12 cmp02 salt-minion[2824]: +# *  0 => The image is not partitioned
May  9 23:35:12 cmp02 salt-minion[2824]: +# * >0 => The number of the partition to use for the injection
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``inject_key``: If this option allows the injection of a SSH key it depends
May  9 23:35:12 cmp02 salt-minion[2824]: +#   on value greater or equal to -1 for ``inject_partition``.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``inject_password``: If this option allows the injection of an admin
May  9 23:35:12 cmp02 salt-minion[2824]: +# password
May  9 23:35:12 cmp02 salt-minion[2824]: +#   it depends on value greater or equal to -1 for ``inject_partition``.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``guestfs`` You can enable the debug log level of libguestfs with this
May  9 23:35:12 cmp02 salt-minion[2824]: +#   config option. A more verbose output will help in debugging issues.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``virt_type``: If you use ``lxc`` as virt_type it will be treated as a
May  9 23:35:12 cmp02 salt-minion[2824]: +#   single partition image
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -2
May  9 23:35:12 cmp02 salt-minion[2824]: +#inject_partition=-2
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable a mouse cursor within a graphical VNC or SPICE sessions.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This will only be taken into account if the VM is fully virtualized and VNC
May  9 23:35:12 cmp02 salt-minion[2824]: +# and/or SPICE is enabled. If the node doesn't support a graphical framebuffer,
May  9 23:35:12 cmp02 salt-minion[2824]: +# then it is valid to set this to False.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``[vnc]enabled``: If VNC is enabled, ``use_usb_tablet`` will have an effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``[spice]enabled`` + ``[spice].agent_enabled``: If SPICE is enabled and the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   spice agent is disabled, the config value of ``use_usb_tablet`` will have
May  9 23:35:12 cmp02 salt-minion[2824]: +#   an effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: This option is being replaced by the 'pointer_model' option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_usb_tablet=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The IP address or hostname to be used as the target for live migration
May  9 23:35:12 cmp02 salt-minion[2824]: +# traffic.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If this option is set to None, the hostname of the migration target compute
May  9 23:35:12 cmp02 salt-minion[2824]: +# node will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is useful in environments where the live-migration traffic can
May  9 23:35:12 cmp02 salt-minion[2824]: +# impact the network plane significantly. A separate network for live-migration
May  9 23:35:12 cmp02 salt-minion[2824]: +# traffic can then use this config option and avoids the impact on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# management network.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A valid IP address or hostname, else None.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_inbound_addr=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Live migration target URI to use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Override the default libvirt live migration target URI (which is dependent
May  9 23:35:12 cmp02 salt-minion[2824]: +# on virt_type). Any included "%s" is replaced with the migration target
May  9 23:35:12 cmp02 salt-minion[2824]: +# hostname.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If this option is set to None (which is the default), Nova will automatically
May  9 23:35:12 cmp02 salt-minion[2824]: +# generate the `live_migration_uri` value based on only 3 supported `virt_type`
May  9 23:35:12 cmp02 salt-minion[2824]: +# in following list:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 'kvm': 'qemu+tcp://%s/system'
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 'qemu': 'qemu+tcp://%s/system'
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 'xen': 'xenmigr://%s/system'
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``live_migration_inbound_addr``: If ``live_migration_inbound_addr`` value
May  9 23:35:12 cmp02 salt-minion[2824]: +#   is not None, the ip/hostname address of target compute node is used instead
May  9 23:35:12 cmp02 salt-minion[2824]: +#   of ``live_migration_uri`` as the uri for live migration.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``live_migration_scheme``: If ``live_migration_uri`` is not set, the scheme
May  9 23:35:12 cmp02 salt-minion[2824]: +#   used for live migration is taken from ``live_migration_scheme`` instead.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# live_migration_uri is deprecated for removal in favor of two other options
May  9 23:35:12 cmp02 salt-minion[2824]: +# that
May  9 23:35:12 cmp02 salt-minion[2824]: +# allow to change live migration scheme and target URI:
May  9 23:35:12 cmp02 salt-minion[2824]: +# ``live_migration_scheme``
May  9 23:35:12 cmp02 salt-minion[2824]: +# and ``live_migration_inbound_addr`` respectively.
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_uri=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Schema used for live migration.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Override the default libvirt live migration scheme (which is dependant on
May  9 23:35:12 cmp02 salt-minion[2824]: +# virt_type). If this option is set to None, nova will automatically choose a
May  9 23:35:12 cmp02 salt-minion[2824]: +# sensible default based on the hypervisor. It is not recommended that you
May  9 23:35:12 cmp02 salt-minion[2824]: +# change
May  9 23:35:12 cmp02 salt-minion[2824]: +# this unless you are very sure that hypervisor supports a particular scheme.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``virt_type``: This option is meaningful only when ``virt_type`` is set to
May  9 23:35:12 cmp02 salt-minion[2824]: +#   `kvm` or `qemu`.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``live_migration_uri``: If ``live_migration_uri`` value is not None, the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   scheme used for live migration is taken from ``live_migration_uri`` instead.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_scheme=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable tunnelled migration.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option enables the tunnelled migration feature, where migration data is
May  9 23:35:12 cmp02 salt-minion[2824]: +# transported over the libvirtd connection. If enabled, we use the
May  9 23:35:12 cmp02 salt-minion[2824]: +# VIR_MIGRATE_TUNNELLED migration flag, avoiding the need to configure
May  9 23:35:12 cmp02 salt-minion[2824]: +# the network to allow direct hypervisor to hypervisor communication.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If False, use the native transport. If not set, Nova will choose a
May  9 23:35:12 cmp02 salt-minion[2824]: +# sensible default based on, for example the availability of native
May  9 23:35:12 cmp02 salt-minion[2824]: +# encryption support in the hypervisor. Enable this option will definitely
May  9 23:35:12 cmp02 salt-minion[2824]: +# impact performance massively.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note that this option is NOT compatible with use of block migration.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Supersedes and (if set) overrides the deprecated 'live_migration_flag' and
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'block_migration_flag' to enable tunneled migration.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_tunnelled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum bandwidth(in MiB/s) to be used during migration.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set to 0, the hypervisor will choose a suitable default. Some hypervisors
May  9 23:35:12 cmp02 salt-minion[2824]: +# do not support this feature and will return an error if bandwidth is not 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Please refer to the libvirt documentation for further details.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_bandwidth=0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum permitted downtime, in milliseconds, for live migration
May  9 23:35:12 cmp02 salt-minion[2824]: +# switchover.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Will be rounded up to a minimum of 100ms. You can increase this value
May  9 23:35:12 cmp02 salt-minion[2824]: +# if you want to allow live-migrations to complete faster, or avoid
May  9 23:35:12 cmp02 salt-minion[2824]: +# live-migration timeout errors by allowing the guest to be paused for
May  9 23:35:12 cmp02 salt-minion[2824]: +# longer during the live-migration switch over.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * live_migration_completion_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_downtime=500
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of incremental steps to reach max downtime value.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Will be rounded up to a minimum of 3 steps.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_downtime_steps=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Time to wait, in seconds, between each step increase of the migration
May  9 23:35:12 cmp02 salt-minion[2824]: +# downtime.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum delay is 10 seconds. Value is per GiB of guest RAM + disk to be
May  9 23:35:12 cmp02 salt-minion[2824]: +# transferred, with lower bound of a minimum of 2 GiB per device.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_downtime_delay=75
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Time to wait, in seconds, for migration to successfully complete transferring
May  9 23:35:12 cmp02 salt-minion[2824]: +# data before aborting the operation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Value is per GiB of guest RAM + disk to be transferred, with lower bound of
May  9 23:35:12 cmp02 salt-minion[2824]: +# a minimum of 2 GiB. Should usually be larger than downtime delay * downtime
May  9 23:35:12 cmp02 salt-minion[2824]: +# steps. Set to 0 to disable timeouts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * live_migration_downtime
May  9 23:35:12 cmp02 salt-minion[2824]: +# * live_migration_downtime_steps
May  9 23:35:12 cmp02 salt-minion[2824]: +# * live_migration_downtime_delay
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: This option can be changed without restarting.
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_completion_timeout=800
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Time to wait, in seconds, for migration to make forward progress in
May  9 23:35:12 cmp02 salt-minion[2824]: +# transferring data before aborting the operation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Set to 0 to disable timeouts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is deprecated, and now disabled by default because we have found serious
May  9 23:35:12 cmp02 salt-minion[2824]: +# bugs in this feature that caused false live-migration timeout failures. This
May  9 23:35:12 cmp02 salt-minion[2824]: +# feature will be removed or replaced in a future release.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: This option can be changed without restarting.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: Serious bugs found in this feature.
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_progress_timeout=0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows nova to switch an on-going live migration to post-copy
May  9 23:35:12 cmp02 salt-minion[2824]: +# mode, i.e., switch the active VM to the one on the destination node before the
May  9 23:35:12 cmp02 salt-minion[2824]: +# migration is complete, therefore ensuring an upper bound on the memory that
May  9 23:35:12 cmp02 salt-minion[2824]: +# needs to be transferred. Post-copy requires libvirt>=1.3.3 and QEMU>=2.5.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When permitted, post-copy mode will be automatically activated if a
May  9 23:35:12 cmp02 salt-minion[2824]: +# live-migration memory copy iteration does not make percentage increase of at
May  9 23:35:12 cmp02 salt-minion[2824]: +# least 10% over the last iteration.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The live-migration force complete API also uses post-copy when permitted. If
May  9 23:35:12 cmp02 salt-minion[2824]: +# post-copy mode is not available, force complete falls back to pausing the VM
May  9 23:35:12 cmp02 salt-minion[2824]: +# to ensure the live-migration operation will complete.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When using post-copy mode, if the source and destination hosts loose network
May  9 23:35:12 cmp02 salt-minion[2824]: +# connectivity, the VM being live-migrated will need to be rebooted. For more
May  9 23:35:12 cmp02 salt-minion[2824]: +# details, please see the Administration guide.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     * live_migration_permit_auto_converge
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_permit_post_copy=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows nova to start live migration with auto converge on.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Auto converge throttles down CPU if a progress of on-going live migration
May  9 23:35:12 cmp02 salt-minion[2824]: +# is slow. Auto converge will only be used if this flag is set to True and
May  9 23:35:12 cmp02 salt-minion[2824]: +# post copy is not permitted or post copy is unavailable due to the version
May  9 23:35:12 cmp02 salt-minion[2824]: +# of libvirt and QEMU in use. Auto converge requires libvirt>=1.2.3 and
May  9 23:35:12 cmp02 salt-minion[2824]: +# QEMU>=1.6.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     * live_migration_permit_post_copy
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#live_migration_permit_auto_converge=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Determine the snapshot image format when sending to the image service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set, this decides what format is used when sending the snapshot to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# image service.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If not set, defaults to same type as source image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``raw``: RAW disk format
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``qcow2``: KVM default disk format
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``vmdk``: VMWare default disk format
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``vdi``: VirtualBox default disk format
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If not set, defaults to same type as source image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: raw, qcow2, vmdk, vdi
May  9 23:35:12 cmp02 salt-minion[2824]: +#snapshot_image_format=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Override the default disk prefix for the devices attached to an instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set, this is used to identify a free disk device name for a bus.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any prefix which will result in a valid disk device name like 'sda' or 'hda'
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for example. This is only necessary if the device names differ to the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   commonly known device name prefixes for a virtualization type such as: sd,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   xvd, uvd, vd.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``virt_type``: Influences which device type is used, which determines
May  9 23:35:12 cmp02 salt-minion[2824]: +#   the default disk prefix.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#disk_prefix=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds to wait for instance to shut down after soft reboot request
May  9 23:35:12 cmp02 salt-minion[2824]: +# is made. We fall back to hard reboot if instance does not shutdown within this
May  9 23:35:12 cmp02 salt-minion[2824]: +# window. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#wait_soft_reboot_seconds=120
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Is used to set the CPU mode an instance should have.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If virt_type="kvm|qemu", it will default to "host-model", otherwise it will
May  9 23:35:12 cmp02 salt-minion[2824]: +# default to "none".
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``host-model``: Clones the host CPU feature flags.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``host-passthrough``: Use the host CPU model exactly;
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``custom``: Use a named CPU model;
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``none``: Not set any CPU model.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``cpu_model``: If ``custom`` is used for ``cpu_mode``, set this config
May  9 23:35:12 cmp02 salt-minion[2824]: +#   option too, otherwise this would result in an error and the instance won't
May  9 23:35:12 cmp02 salt-minion[2824]: +#   be launched.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: host-model, host-passthrough, custom, none
May  9 23:35:12 cmp02 salt-minion[2824]: +#cpu_mode=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Set the name of the libvirt CPU model the instance should use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The names listed in /usr/share/libvirt/cpu_map.xml
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``cpu_mode``: Don't set this when ``cpu_mode`` is NOT set to ``custom``.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   This would result in an error and the instance won't be launched.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``virt_type``: Only the virtualization types ``kvm`` and ``qemu`` use this.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cpu_model=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Location where libvirt driver will store snapshots before uploading them to
May  9 23:35:12 cmp02 salt-minion[2824]: +# image service (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#snapshots_directory=$instances_path/snapshots
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Location where the Xen hvmloader is kept (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#xen_hvmloader_path=/usr/lib/xen/boot/hvmloader
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specific cachemodes to use for different disk types e.g:
May  9 23:35:12 cmp02 salt-minion[2824]: +# file=directsync,block=none (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#disk_cachemodes =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# A path to a device that will be used as source of entropy on the host.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Permitted options are: /dev/random or /dev/hwrng (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#rng_dev_path=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# For qemu or KVM guests, set this option to specify a default machine type per
May  9 23:35:12 cmp02 salt-minion[2824]: +# host architecture. You can find a list of supported machine types in your
May  9 23:35:12 cmp02 salt-minion[2824]: +# environment by checking the output of the "virsh capabilities"command. The
May  9 23:35:12 cmp02 salt-minion[2824]: +# format of the value for this config option is host-arch=machine-type. For
May  9 23:35:12 cmp02 salt-minion[2824]: +# example: x86_64=machinetype1,armv7l=machinetype2 (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#hw_machine_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# The data source used to the populate the host "serial" UUID exposed to guest
May  9 23:35:12 cmp02 salt-minion[2824]: +# in the virtual BIOS. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: none, os, hardware, auto
May  9 23:35:12 cmp02 salt-minion[2824]: +#sysinfo_serial=auto
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# A number of seconds to memory usage statistics period. Zero or negative value
May  9 23:35:12 cmp02 salt-minion[2824]: +# mean to disable memory usage statistics. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#mem_stats_period_seconds=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of uid targets and ranges.Syntax is guest-uid:host-uid:countMaximum of 5
May  9 23:35:12 cmp02 salt-minion[2824]: +# allowed. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#uid_maps =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# List of guid targets and ranges.Syntax is guest-gid:host-gid:countMaximum of 5
May  9 23:35:12 cmp02 salt-minion[2824]: +# allowed. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#gid_maps =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# In a realtime host context vCPUs for guest will run in that scheduling
May  9 23:35:12 cmp02 salt-minion[2824]: +# priority. Priority depends on the host kernel (usually 1-99) (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#realtime_scheduler_priority=1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is a performance event list which could be used as monitor. These events
May  9 23:35:12 cmp02 salt-minion[2824]: +# will be passed to libvirt domain xml while creating a new instances.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Then event statistics data can be collected from libvirt.  The minimum
May  9 23:35:12 cmp02 salt-minion[2824]: +# libvirt version is 2.0.0. For more information about `Performance monitoring
May  9 23:35:12 cmp02 salt-minion[2824]: +# events`, refer https://libvirt.org/formatdomain.html#elementsPerf .
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string list. For example: ``enabled_perf_events = cmt, mbml, mbmt``
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The supported events list can be found in
May  9 23:35:12 cmp02 salt-minion[2824]: +#   https://libvirt.org/html/libvirt-libvirt-domain.html ,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   which you may need to search key words ``VIR_PERF_PARAM_*``
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled_perf_events =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# VM Images format.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If default is specified, then use_cow_images flag is used instead of this
May  9 23:35:12 cmp02 salt-minion[2824]: +# one.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * virt.use_cow_images
May  9 23:35:12 cmp02 salt-minion[2824]: +# * images_volume_group
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: raw, flat, qcow2, lvm, rbd, ploop, default
May  9 23:35:12 cmp02 salt-minion[2824]: +#images_type=default
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# LVM Volume Group that is used for VM images, when you specify images_type=lvm
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * images_type
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#images_volume_group=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Create sparse logical volumes (with virtualsize) if this flag is set to True.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#sparse_logical_volumes=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# The RADOS pool in which rbd volumes are stored (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#images_rbd_pool=rbd
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Path to the ceph configuration file to use (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#images_rbd_ceph_conf =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Discard option for nova managed disks.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Requires:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Libvirt >= 1.0.6
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Qemu >= 1.5 (raw format)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Qemu >= 1.6 (qcow2 format)
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: ignore, unmap
May  9 23:35:12 cmp02 salt-minion[2824]: +#hw_disk_discard=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: Allows image information files to be stored in non-standard
May  9 23:35:12 cmp02 salt-minion[2824]: +# locations (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: Image info files are no longer used by the image cache
May  9 23:35:12 cmp02 salt-minion[2824]: +#image_info_filename_pattern=$instances_path/$image_cache_subdirectory_name/%(image)s.info
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Unused resized base images younger than this will not be removed (integer
May  9 23:35:12 cmp02 salt-minion[2824]: +# value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#remove_unused_resized_minimum_age_seconds=3600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: Write a checksum for files in _base to disk (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: The image cache no longer periodically calculates checksums of stored
May  9 23:35:12 cmp02 salt-minion[2824]: +# images. Data integrity can be checked at the block or filesystem level.
May  9 23:35:12 cmp02 salt-minion[2824]: +#checksum_base_images=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: How frequently to checksum base images (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: The image cache no longer periodically calculates checksums of stored
May  9 23:35:12 cmp02 salt-minion[2824]: +# images. Data integrity can be checked at the block or filesystem level.
May  9 23:35:12 cmp02 salt-minion[2824]: +#checksum_interval_seconds=3600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Method used to wipe ephemeral disks when they are deleted. Only takes effect
May  9 23:35:12 cmp02 salt-minion[2824]: +# if LVM is set as backing storage.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * none - do not wipe deleted volumes
May  9 23:35:12 cmp02 salt-minion[2824]: +# * zero - overwrite volumes with zeroes
May  9 23:35:12 cmp02 salt-minion[2824]: +# * shred - overwrite volume repeatedly
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * images_type - must be set to ``lvm``
May  9 23:35:12 cmp02 salt-minion[2824]: +# * volume_clear_size
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: none, zero, shred
May  9 23:35:12 cmp02 salt-minion[2824]: +#volume_clear=zero
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Size of area in MiB, counting from the beginning of the allocated volume,
May  9 23:35:12 cmp02 salt-minion[2824]: +# that will be cleared using method set in ``volume_clear`` option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 0 - clear whole volume
May  9 23:35:12 cmp02 salt-minion[2824]: +# * >0 - clear specified amount of MiB
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * images_type - must be set to ``lvm``
May  9 23:35:12 cmp02 salt-minion[2824]: +# * volume_clear - must be set and the value must be different than ``none``
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for this option to have any impact
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#volume_clear_size=0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable snapshot compression for ``qcow2`` images.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: you can set ``snapshot_image_format`` to ``qcow2`` to force all
May  9 23:35:12 cmp02 salt-minion[2824]: +# snapshots to be in ``qcow2`` format, independently from their original image
May  9 23:35:12 cmp02 salt-minion[2824]: +# type.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * snapshot_image_format
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#snapshot_compression=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use virtio for bridge interfaces with KVM/QEMU (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_virtio_for_bridges=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Protocols listed here will be accessed directly from QEMU.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If gluster is present in qemu_allowed_storage_drivers, glusterfs's backend
May  9 23:35:12 cmp02 salt-minion[2824]: +# will
May  9 23:35:12 cmp02 salt-minion[2824]: +# pass a disk configuration to QEMU. This allows QEMU to access the volume using
May  9 23:35:12 cmp02 salt-minion[2824]: +# libgfapi rather than mounting GlusterFS via fuse.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * [gluster]
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#qemu_allowed_storage_drivers =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use multipath connection of the iSCSI or FC volume
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Volumes can be connected in the LibVirt as multipath devices. This will
May  9 23:35:12 cmp02 salt-minion[2824]: +# provide high availability and fault tolerance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [libvirt]/iscsi_use_multipath
May  9 23:35:12 cmp02 salt-minion[2824]: +#volume_use_multipath=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of times to rediscover AoE target to find volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Nova provides support for block storage attaching to hosts via AOE (ATA over
May  9 23:35:12 cmp02 salt-minion[2824]: +# Ethernet). This option allows the user to specify the maximum number of retry
May  9 23:35:12 cmp02 salt-minion[2824]: +# attempts that can be made to discover the AoE device.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#num_aoe_discover_tries=3
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Absolute path to the directory where the glusterfs volume is mounted on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# compute node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#glusterfs_mount_point_base=$state_path/mnt
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of times to scan iSCSI target to find volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#num_iscsi_scan_tries=5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The iSCSI transport iface to use to connect to target in case offload support
May  9 23:35:12 cmp02 salt-minion[2824]: +# is desired.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Default format is of the form <transport_name>.<hwaddress> where
May  9 23:35:12 cmp02 salt-minion[2824]: +# <transport_name> is one of (be2iscsi, bnx2i, cxgb3i, cxgb4i, qla4xxx, ocs) and
May  9 23:35:12 cmp02 salt-minion[2824]: +# <hwaddress> is the MAC address of the interface and can be generated via the
May  9 23:35:12 cmp02 salt-minion[2824]: +# iscsiadm -m iface command. Do not confuse the iscsi_iface parameter to be
May  9 23:35:12 cmp02 salt-minion[2824]: +# provided here with the actual transport name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [libvirt]/iscsi_transport
May  9 23:35:12 cmp02 salt-minion[2824]: +#iscsi_iface=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of times to scan iSER target to find volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# iSER is a server network protocol that extends iSCSI protocol to use Remote
May  9 23:35:12 cmp02 salt-minion[2824]: +# Direct Memory Access (RDMA). This option allows the user to specify the
May  9 23:35:12 cmp02 salt-minion[2824]: +# maximum
May  9 23:35:12 cmp02 salt-minion[2824]: +# number of scan attempts that can be made to find iSER volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#num_iser_scan_tries=5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use multipath connection of the iSER volume.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# iSER volumes can be connected as multipath devices. This will provide high
May  9 23:35:12 cmp02 salt-minion[2824]: +# availability and fault tolerance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#iser_use_multipath=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The RADOS client name for accessing rbd(RADOS Block Devices) volumes.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Libvirt will refer to this user when connecting and authenticating with
May  9 23:35:12 cmp02 salt-minion[2824]: +# the Ceph RBD server.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#rbd_user=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The libvirt UUID of the secret for the rbd_user volumes.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#rbd_secret_uuid=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Directory where the NFS volume is mounted on the compute node.
May  9 23:35:12 cmp02 salt-minion[2824]: +# The default is 'mnt' directory of the location where nova's Python module
May  9 23:35:12 cmp02 salt-minion[2824]: +# is installed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# NFS provides shared storage for the OpenStack Block Storage service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing absolute path of mount point.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#nfs_mount_point_base=$state_path/mnt
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mount options passed to the NFS client. See section of the nfs man page
May  9 23:35:12 cmp02 salt-minion[2824]: +# for details.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mount options controls the way the filesystem is mounted and how the
May  9 23:35:12 cmp02 salt-minion[2824]: +# NFS client behaves when accessing files on this mount point.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string representing mount options separated by commas.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Example string: vers=3,lookupcache=pos
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#nfs_mount_options=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Directory where the Quobyte volume is mounted on the compute node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Nova supports Quobyte volume driver that enables storing Block Storage
May  9 23:35:12 cmp02 salt-minion[2824]: +# service volumes on a Quobyte storage back end. This Option sepcifies the
May  9 23:35:12 cmp02 salt-minion[2824]: +# path of the directory where Quobyte volume is mounted.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing absolute path of mount point.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#quobyte_mount_point_base=$state_path/mnt
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Path to a Quobyte Client configuration file. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#quobyte_client_cfg=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Path or URL to Scality SOFS(Scale-Out File Server) configuration file.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The Scality SOFS provides OpenStack users the option of storing their
May  9 23:35:12 cmp02 salt-minion[2824]: +# data on a high capacity, replicated, highly available Scality Ring object
May  9 23:35:12 cmp02 salt-minion[2824]: +# storage cluster.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#scality_sofs_config=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Base dir where Scality SOFS shall be mounted.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The Scality volume driver in Nova mounts SOFS and lets the hypervisor access
May  9 23:35:12 cmp02 salt-minion[2824]: +# the volumes.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * $state_path/scality where state_path is a config option that specifies
May  9 23:35:12 cmp02 salt-minion[2824]: +#   the top-level directory for maintaining nova's state or Any string
May  9 23:35:12 cmp02 salt-minion[2824]: +#   containing the full directory path.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#scality_sofs_mount_point=$state_path/scality
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Directory where the SMBFS shares are mounted on the compute node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#smbfs_mount_point_base=$state_path/mnt
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mount options passed to the SMBFS client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Provide SMBFS options as a single string containing all parameters.
May  9 23:35:12 cmp02 salt-minion[2824]: +# See mount.cifs man page for  details. Note that the libvirt-qemu ``uid``
May  9 23:35:12 cmp02 salt-minion[2824]: +# and ``gid`` must be specified.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#smbfs_mount_options =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# libvirt's transport method for remote file operations.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Because libvirt cannot use RPC to copy files over network to/from other
May  9 23:35:12 cmp02 salt-minion[2824]: +# compute nodes, other method must be used for:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * creating directory on remote host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * creating file on remote host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * removing file from remote host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * copying file to remote host
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: ssh, rsync
May  9 23:35:12 cmp02 salt-minion[2824]: +#remote_filesystem_transport=ssh
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Directory where the Virtuozzo Storage clusters are mounted on the compute
May  9 23:35:12 cmp02 salt-minion[2824]: +# node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option defines non-standard mountpoint for Vzstorage cluster.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vzstorage_mount_* group of parameters
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_mount_point_base=$state_path/mnt
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mount owner user name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option defines the owner user of Vzstorage cluster mountpoint.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vzstorage_mount_* group of parameters
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_mount_user=stack
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mount owner group name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option defines the owner group of Vzstorage cluster mountpoint.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vzstorage_mount_* group of parameters
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_mount_group=qemu
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Mount access mode.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option defines the access bits of Vzstorage cluster mountpoint,
May  9 23:35:12 cmp02 salt-minion[2824]: +# in the format similar to one of chmod(1) utility, like this: 0770.
May  9 23:35:12 cmp02 salt-minion[2824]: +# It consists of one to four digits ranging from 0 to 7, with missing
May  9 23:35:12 cmp02 salt-minion[2824]: +# lead digits assumed to be 0's.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vzstorage_mount_* group of parameters
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_mount_perms=0770
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Path to vzstorage client log.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option defines the log of cluster operations,
May  9 23:35:12 cmp02 salt-minion[2824]: +# it should include "%(cluster_name)s" template to separate
May  9 23:35:12 cmp02 salt-minion[2824]: +# logs from multiple shares.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vzstorage_mount_opts may include more detailed logging options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_log_path=/var/log/pstorage/%(cluster_name)s/nova.log.gz
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Path to the SSD cache file.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# You can attach an SSD drive to a client and configure the drive to store
May  9 23:35:12 cmp02 salt-minion[2824]: +# a local cache of frequently accessed data. By having a local cache on a
May  9 23:35:12 cmp02 salt-minion[2824]: +# client's SSD drive, you can increase the overall cluster performance by
May  9 23:35:12 cmp02 salt-minion[2824]: +# up to 10 and more times.
May  9 23:35:12 cmp02 salt-minion[2824]: +# WARNING! There is a lot of SSD models which are not server grade and
May  9 23:35:12 cmp02 salt-minion[2824]: +# may loose arbitrary set of data changes on power loss.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Such SSDs should not be used in Vstorage and are dangerous as may lead
May  9 23:35:12 cmp02 salt-minion[2824]: +# to data corruptions and inconsistencies. Please consult with the manual
May  9 23:35:12 cmp02 salt-minion[2824]: +# on which SSD models are known to be safe or verify it using
May  9 23:35:12 cmp02 salt-minion[2824]: +# vstorage-hwflush-check(1) utility.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option defines the path which should include "%(cluster_name)s"
May  9 23:35:12 cmp02 salt-minion[2824]: +# template to separate caches from multiple shares.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vzstorage_mount_opts may include more detailed cache options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_cache_path=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Extra mount options for pstorage-mount
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# For full description of them, see
May  9 23:35:12 cmp02 salt-minion[2824]: +# https://static.openvz.org/vz-man/man1/pstorage-mount.1.gz.html
May  9 23:35:12 cmp02 salt-minion[2824]: +# Format is a python string representation of arguments list, like:
May  9 23:35:12 cmp02 salt-minion[2824]: +# "['-v', '-R', '500']"
May  9 23:35:12 cmp02 salt-minion[2824]: +# Shouldn't include -c, -l, -C, -u, -g and -m as those have
May  9 23:35:12 cmp02 salt-minion[2824]: +# explicit vzstorage_* options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * All other vzstorage_* options
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vzstorage_mount_opts =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [matchmaker_redis]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -705,7 +6707,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#host = 127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +#host=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Use this port to connect to redis host. (port value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -713,7 +6715,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#port = 6379
May  9 23:35:12 cmp02 salt-minion[2824]: +#port=6379
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Password for Redis server (optional). (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -729,16 +6731,485 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #sentinel_hosts =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Redis replica set name. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#sentinel_group_name = oslo-messaging-zeromq
May  9 23:35:12 cmp02 salt-minion[2824]: +#sentinel_group_name=oslo-messaging-zeromq
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Time in ms to wait between connection attempts. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#wait_timeout = 2000
May  9 23:35:12 cmp02 salt-minion[2824]: +#wait_timeout=2000
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Time in ms to wait before the transaction is killed. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#check_timeout = 20000
May  9 23:35:12 cmp02 salt-minion[2824]: +#check_timeout=20000
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Timeout in ms on blocking socket operations. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#socket_timeout = 10000
May  9 23:35:12 cmp02 salt-minion[2824]: +#socket_timeout=10000
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[metrics]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration options for metrics
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Options under this group allow to adjust how values assigned to metrics are
May  9 23:35:12 cmp02 salt-minion[2824]: +# calculated.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When using metrics to weight the suitability of a host, you can use this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option
May  9 23:35:12 cmp02 salt-minion[2824]: +# to change how the calculated weight influences the weight assigned to a host
May  9 23:35:12 cmp02 salt-minion[2824]: +# as
May  9 23:35:12 cmp02 salt-minion[2824]: +# follows:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * >1.0: increases the effect of the metric on overall weight
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 1.0: no change to the calculated weight
May  9 23:35:12 cmp02 salt-minion[2824]: +# * >0.0,<1.0: reduces the effect of the metric on overall weight
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 0.0: the metric value is ignored, and the value of the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'weight_of_unavailable' option is returned instead
May  9 23:35:12 cmp02 salt-minion[2824]: +# * >-1.0,<0.0: the effect is reduced and reversed
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1.0: the effect is reversed
May  9 23:35:12 cmp02 salt-minion[2824]: +# * <-1.0: the effect is increased proportionally and reversed
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to the multipler
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ratio for this weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * weight_of_unavailable
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#weight_multiplier=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This setting specifies the metrics to be weighed and the relative ratios for
May  9 23:35:12 cmp02 salt-minion[2824]: +# each metric. This should be a single string value, consisting of a series of
May  9 23:35:12 cmp02 salt-minion[2824]: +# one or more 'name=ratio' pairs, separated by commas, where 'name' is the name
May  9 23:35:12 cmp02 salt-minion[2824]: +# of the metric to be weighed, and 'ratio' is the relative weight for that
May  9 23:35:12 cmp02 salt-minion[2824]: +# metric.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note that if the ratio is set to 0, the metric value is ignored, and instead
May  9 23:35:12 cmp02 salt-minion[2824]: +# the weight will be set to the value of the 'weight_of_unavailable' option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# As an example, let's consider the case where this option is set to:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     ``name1=1.0, name2=-1.3``
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The final weight will be:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     ``(name1.value * 1.0) + (name2.value * -1.3)``
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of zero or more key/value pairs separated by commas, where the key is
May  9 23:35:12 cmp02 salt-minion[2824]: +#   a string representing the name of a metric and the value is a numeric weight
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for that metric. If any value is set to 0, the value is ignored and the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   weight will be set to the value of the 'weight_of_unavailable' option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * weight_of_unavailable
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#weight_setting =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This setting determines how any unavailable metrics are treated. If this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option
May  9 23:35:12 cmp02 salt-minion[2824]: +# is set to True, any hosts for which a metric is unavailable will raise an
May  9 23:35:12 cmp02 salt-minion[2824]: +# exception, so it is recommended to also use the MetricFilter to filter out
May  9 23:35:12 cmp02 salt-minion[2824]: +# those hosts before weighing.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * True or False, where False ensures any metric being unavailable for a host
May  9 23:35:12 cmp02 salt-minion[2824]: +#   will set the host weight to 'weight_of_unavailable'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * weight_of_unavailable
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#required=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When any of the following conditions are met, this value will be used in place
May  9 23:35:12 cmp02 salt-minion[2824]: +# of any actual metric value:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * One of the metrics named in 'weight_setting' is not available for a host,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   and the value of 'required' is False
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The ratio specified for a metric in 'weight_setting' is 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The 'weight_multiplier' option is set to 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer or float value, where the value corresponds to the multipler
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ratio for this weigher.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * weight_setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# * required
May  9 23:35:12 cmp02 salt-minion[2824]: +# * weight_multiplier
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#weight_of_unavailable=-10000.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[mks]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Nova compute node uses WebMKS, a desktop sharing protocol to provide
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance console access to VM's created by VMware hypervisors.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Following options must be set to provide console access.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * mksproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * enabled
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Location of MKS web console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The URL in the response points to a WebMKS proxy which
May  9 23:35:12 cmp02 salt-minion[2824]: +# starts proxying between client and corresponding vCenter
May  9 23:35:12 cmp02 salt-minion[2824]: +# server where instance runs. In order to use the web based
May  9 23:35:12 cmp02 salt-minion[2824]: +# console access, WebMKS proxy should be installed and configured
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Must be a valid URL of the form:``http://host:port/``
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#mksproxy_base_url=http://127.0.0.1:6090/
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enables graphical console access for virtual machines.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[neutron]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration options for neutron (network connectivity as a service).
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +username=neutron
May  9 23:35:12 cmp02 salt-minion[2824]: +password=opnfv_secret
May  9 23:35:12 cmp02 salt-minion[2824]: +project_name=service
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_url = http://172.16.10.36:35357/v3
May  9 23:35:12 cmp02 salt-minion[2824]: +url=http://172.16.10.36:9696
May  9 23:35:12 cmp02 salt-minion[2824]: +region_name= RegionOne
May  9 23:35:12 cmp02 salt-minion[2824]: +extension_sync_interval=600
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_type = v3password
May  9 23:35:12 cmp02 salt-minion[2824]: +project_domain_name = Default
May  9 23:35:12 cmp02 salt-minion[2824]: +user_domain_name = Default
May  9 23:35:12 cmp02 salt-minion[2824]: +timeout=30
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the URL for connecting to Neutron.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid URL that points to the Neutron API service is appropriate here.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   This typically matches the URL returned for the 'network' service type
May  9 23:35:12 cmp02 salt-minion[2824]: +#   from the Keystone service catalog.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (uri value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#url=http://127.0.0.1:9696
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Region name for connecting to Neutron in admin context.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is used in multi-region setups. If there are two Neutron
May  9 23:35:12 cmp02 salt-minion[2824]: +# servers running in two regions in two different machines, then two
May  9 23:35:12 cmp02 salt-minion[2824]: +# services need to be created in Keystone with two different regions and
May  9 23:35:12 cmp02 salt-minion[2824]: +# associate corresponding endpoints to those services. When requests are made
May  9 23:35:12 cmp02 salt-minion[2824]: +# to Keystone, the Keystone service uses the region_name to determine the
May  9 23:35:12 cmp02 salt-minion[2824]: +# region the request is coming from.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#region_name=RegionOne
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specifies the name of an integration bridge interface used by OpenvSwitch.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is used only if Neutron does not specify the OVS bridge name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string representing OVS bridge name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ovs_bridge=br-int
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Integer value representing the number of seconds to wait before querying
May  9 23:35:12 cmp02 salt-minion[2824]: +# Neutron for extensions.  After this number of seconds the next time Nova
May  9 23:35:12 cmp02 salt-minion[2824]: +# needs to create a resource in Neutron it will requery Neutron for the
May  9 23:35:12 cmp02 salt-minion[2824]: +# extensions that it has loaded.  Setting value to 0 will refresh the
May  9 23:35:12 cmp02 salt-minion[2824]: +# extensions with no wait.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#extension_sync_interval=600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When set to True, this option indicates that Neutron will be used to proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +# metadata requests and resolve instance ids. Otherwise, the instance ID must be
May  9 23:35:12 cmp02 salt-minion[2824]: +# passed to the metadata request in the 'X-Instance-ID' header.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * metadata_proxy_shared_secret
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#service_metadata_proxy=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option holds the shared secret string used to validate proxy requests to
May  9 23:35:12 cmp02 salt-minion[2824]: +# Neutron metadata requests. In order to be used, the
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'X-Metadata-Provider-Signature' header must be supplied in the request.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * service_metadata_proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#metadata_proxy_shared_secret =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded Certificate Authority to use when verifying HTTPs connections.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cafile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate cert file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#certfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate key file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#keyfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Verify HTTPS connections. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Timeout value for http requests (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#timeout=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +timeout = 300
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication type to load (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [neutron]/auth_plugin
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Config Section from which to load plugin specific options (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_section=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication URL (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Trust ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#trust_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain ID to use with v3 and v2 parameters. It will be used for both
May  9 23:35:12 cmp02 salt-minion[2824]: +# the user and project domain in v3 and ignored in v2 authentication. (string
May  9 23:35:12 cmp02 salt-minion[2824]: +# value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain name to use with v3 API and v2 parameters. It will be used for
May  9 23:35:12 cmp02 salt-minion[2824]: +# both the user and project domain in v3 and ignored in v2 authentication.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [neutron]/user-name
May  9 23:35:12 cmp02 salt-minion[2824]: +#username=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain id (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's password (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant Name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[notifications]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Most of the actions in Nova which manipulate the system state generate
May  9 23:35:12 cmp02 salt-minion[2824]: +# notifications which are posted to the messaging component (e.g. RabbitMQ) and
May  9 23:35:12 cmp02 salt-minion[2824]: +# can be consumed by any service outside the Openstack. More technical details
May  9 23:35:12 cmp02 salt-minion[2824]: +# at http://docs.openstack.org/developer/nova/notifications.html
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set, send compute.instance.update notifications on instance state
May  9 23:35:12 cmp02 salt-minion[2824]: +# changes.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Please refer to https://wiki.openstack.org/wiki/SystemUsageData for
May  9 23:35:12 cmp02 salt-minion[2824]: +# additional information on notifications.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * None - no notifications
May  9 23:35:12 cmp02 salt-minion[2824]: +# * "vm_state" - notifications on VM state changes
May  9 23:35:12 cmp02 salt-minion[2824]: +# * "vm_and_task_state" - notifications on VM and task state changes
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: <None>, vm_state, vm_and_task_state
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/notify_on_state_change
May  9 23:35:12 cmp02 salt-minion[2824]: +#notify_on_state_change=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +notify_on_state_change = vm_and_task_state
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If enabled, send api.fault notifications on caught exceptions in the
May  9 23:35:12 cmp02 salt-minion[2824]: +# API service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/notify_api_faults
May  9 23:35:12 cmp02 salt-minion[2824]: +#notify_on_api_faults=false
May  9 23:35:12 cmp02 salt-minion[2824]: +notify_on_api_faults=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Default notification level for outgoing notifications. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: DEBUG, INFO, WARN, ERROR, CRITICAL
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/default_notification_level
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_level=INFO
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Default publisher_id for outgoing notifications. If you consider routing
May  9 23:35:12 cmp02 salt-minion[2824]: +# notifications using different publisher, change this value accordingly.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Defaults to the IPv4 address of this host, but it can be any valid
May  9 23:35:12 cmp02 salt-minion[2824]: +#   oslo.messaging publisher_id
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# *  my_ip - IP address of this host
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/default_publisher_id
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_publisher_id=$my_ip
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specifies which notification format shall be used by nova.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The default value is fine for most deployments and rarely needs to be changed.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This value can be set to 'versioned' once the infrastructure moves closer to
May  9 23:35:12 cmp02 salt-minion[2824]: +# consuming the newer format of notifications. After this occurs, this option
May  9 23:35:12 cmp02 salt-minion[2824]: +# will be removed (possibly in the "P" release).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * unversioned: Only the legacy unversioned notifications are emitted.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * versioned: Only the new versioned notifications are emitted.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * both: Both the legacy unversioned and the new versioned notifications are
May  9 23:35:12 cmp02 salt-minion[2824]: +#   emitted. (Default)
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The list of versioned notifications is visible in
May  9 23:35:12 cmp02 salt-minion[2824]: +# http://docs.openstack.org/developer/nova/notifications.html
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: unversioned, versioned, both
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/notification_format
May  9 23:35:12 cmp02 salt-minion[2824]: +#notification_format=both
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[osapi_v21]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is a list of all of the v2.1 API extensions to never load.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of strings, each being the alias of an extension that you do not
May  9 23:35:12 cmp02 salt-minion[2824]: +#   wish to load.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * enabled
May  9 23:35:12 cmp02 salt-minion[2824]: +# * extensions_whitelist
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 12.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# API extensions are now part of the standard API. API extensions should be
May  9 23:35:12 cmp02 salt-minion[2824]: +# disabled using policy, rather than via these configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#extensions_blacklist =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is a list of extensions. If it is empty, then *all* extensions except
May  9 23:35:12 cmp02 salt-minion[2824]: +# those specified in the extensions_blacklist option will be loaded. If it is
May  9 23:35:12 cmp02 salt-minion[2824]: +# not
May  9 23:35:12 cmp02 salt-minion[2824]: +# empty, then only those extensions in this list will be loaded, provided that
May  9 23:35:12 cmp02 salt-minion[2824]: +# they are also not in the extensions_blacklist option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of strings, each being the alias of an extension that you wish to
May  9 23:35:12 cmp02 salt-minion[2824]: +#   load, or an empty list, which indicates that all extensions are to be run.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * enabled
May  9 23:35:12 cmp02 salt-minion[2824]: +# * extensions_blacklist
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 12.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# API extensions are now part of the standard API. API extensions should be
May  9 23:35:12 cmp02 salt-minion[2824]: +# disabled using policy, rather than via these configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#extensions_whitelist =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is a string representing a regular expression (regex) that matches
May  9 23:35:12 cmp02 salt-minion[2824]: +# the project_id as contained in URLs. If not set, it will match normal UUIDs
May  9 23:35:12 cmp02 salt-minion[2824]: +# created by keystone.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing any legal regular expression
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 13.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Recent versions of nova constrain project IDs to hexadecimal characters and
May  9 23:35:12 cmp02 salt-minion[2824]: +# dashes. If your installation uses IDs outside of this range, you should use
May  9 23:35:12 cmp02 salt-minion[2824]: +# this option to provide your own regex and give you time to migrate offending
May  9 23:35:12 cmp02 salt-minion[2824]: +# projects to valid IDs before the next release.
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_id_regex=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_concurrency]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -748,14 +7219,16 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Enables or disables inter-process locks. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#disable_process_locking = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/disable_process_locking
May  9 23:35:12 cmp02 salt-minion[2824]: +#disable_process_locking=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Directory to use for lock files.  For security, the specified directory should
May  9 23:35:12 cmp02 salt-minion[2824]:  # only be writable by the user running the processes that need locking. Defaults
May  9 23:35:12 cmp02 salt-minion[2824]:  # to environment variable OSLO_LOCK_PATH. If OSLO_LOCK_PATH is not set in the
May  9 23:35:12 cmp02 salt-minion[2824]:  # environment, use the Python tempfile.gettempdir function to find a suitable
May  9 23:35:12 cmp02 salt-minion[2824]:  # location. If external locks are used, a lock path must be set. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#lock_path = /tmp
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/lock_path
May  9 23:35:12 cmp02 salt-minion[2824]: +lock_path = /var/lib/nova/tmp
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_messaging_amqp]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -766,112 +7239,103 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Name for the AMQP container. must be globally unique. Defaults to a generated
May  9 23:35:12 cmp02 salt-minion[2824]:  # UUID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#container_name = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/container_name
May  9 23:35:12 cmp02 salt-minion[2824]: +#container_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Timeout for inactive connections (in seconds) (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#idle_timeout = 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/idle_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +#idle_timeout=0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Debug: dump AMQP frames to stdout (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#trace = false
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Attempt to connect via SSL. If no other ssl-related parameters are given, it
May  9 23:35:12 cmp02 salt-minion[2824]: -# will use the system's CA-bundle to verify the server's certificate. (boolean
May  9 23:35:12 cmp02 salt-minion[2824]: -# value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/trace
May  9 23:35:12 cmp02 salt-minion[2824]: +#trace=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # CA certificate PEM file used to verify the server's certificate (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/ssl_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]:  #ssl_ca_file =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Self-identifying certificate PEM file for client authentication (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/ssl_cert_file
May  9 23:35:12 cmp02 salt-minion[2824]:  #ssl_cert_file =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Private key PEM file used to sign ssl_cert_file certificate (optional) (string
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/ssl_key_file
May  9 23:35:12 cmp02 salt-minion[2824]:  #ssl_key_file =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Password for decrypting ssl_key_file (if encrypted) (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_key_password = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# By default SSL checks that the name in the server's certificate matches the
May  9 23:35:12 cmp02 salt-minion[2824]: -# hostname in the transport_url. In some configurations it may be preferable to
May  9 23:35:12 cmp02 salt-minion[2824]: -# use the virtual hostname instead, for example if the server uses the Server
May  9 23:35:12 cmp02 salt-minion[2824]: -# Name Indication TLS extension (rfc6066) to provide a certificate per virtual
May  9 23:35:12 cmp02 salt-minion[2824]: -# host. Set ssl_verify_vhost to True if the server's SSL certificate uses the
May  9 23:35:12 cmp02 salt-minion[2824]: -# virtual host name instead of the DNS name. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_verify_vhost = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/ssl_key_password
May  9 23:35:12 cmp02 salt-minion[2824]: +#ssl_key_password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Accept clients using either SSL or plain TCP (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/allow_insecure_clients
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Not applicable - not a SSL server
May  9 23:35:12 cmp02 salt-minion[2824]: -#allow_insecure_clients = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#allow_insecure_clients=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Space separated list of acceptable SASL mechanisms (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/sasl_mechanisms
May  9 23:35:12 cmp02 salt-minion[2824]:  #sasl_mechanisms =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Path to directory that contains the SASL configuration (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/sasl_config_dir
May  9 23:35:12 cmp02 salt-minion[2824]:  #sasl_config_dir =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Name of configuration file (without .conf suffix) (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/sasl_config_name
May  9 23:35:12 cmp02 salt-minion[2824]:  #sasl_config_name =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# SASL realm to use if no realm present in username (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#sasl_default_realm =
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# DEPRECATED: User name for message broker authentication (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Reason: Should use configuration option transport_url to provide the username.
May  9 23:35:12 cmp02 salt-minion[2824]: +# User name for message broker authentication (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/username
May  9 23:35:12 cmp02 salt-minion[2824]:  #username =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# DEPRECATED: Password for message broker authentication (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Reason: Should use configuration option transport_url to provide the password.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Password for message broker authentication (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/password
May  9 23:35:12 cmp02 salt-minion[2824]:  #password =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Seconds to pause before attempting to re-connect. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection_retry_interval = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_retry_interval=1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Increase the connection_retry_interval by this many seconds after each
May  9 23:35:12 cmp02 salt-minion[2824]:  # unsuccessful failover attempt. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection_retry_backoff = 2
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_retry_backoff=2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum limit for connection_retry_interval + connection_retry_backoff
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection_retry_interval_max = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_retry_interval_max=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Time to pause between re-connecting an AMQP 1.0 link that failed due to a
May  9 23:35:12 cmp02 salt-minion[2824]:  # recoverable error. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#link_retry_delay = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#link_retry_delay=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The maximum number of attempts to re-send a reply message which failed due to
May  9 23:35:12 cmp02 salt-minion[2824]:  # a recoverable error. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_reply_retry = 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_reply_retry=0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The deadline for an rpc reply message delivery. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_reply_timeout = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_reply_timeout=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The deadline for an rpc cast or call message delivery. Only used when caller
May  9 23:35:12 cmp02 salt-minion[2824]:  # does not provide a timeout expiry. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_send_timeout = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_send_timeout=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The deadline for a sent notification message delivery. Only used when caller
May  9 23:35:12 cmp02 salt-minion[2824]:  # does not provide a timeout expiry. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_notify_timeout = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_notify_timeout=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The duration to schedule a purge of idle sender links. Detach link after
May  9 23:35:12 cmp02 salt-minion[2824]:  # expiry. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_sender_link_timeout = 600
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_sender_link_timeout=600
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Indicates the addressing mode used by the driver.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Permitted values:
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -879,44 +7343,39 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # 'routable' - use routable addresses
May  9 23:35:12 cmp02 salt-minion[2824]:  # 'dynamic'  - use legacy addresses if the message bus does not support routing
May  9 23:35:12 cmp02 salt-minion[2824]:  # otherwise use routable addressing (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#addressing_mode = dynamic
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enable virtual host support for those message buses that do not natively
May  9 23:35:12 cmp02 salt-minion[2824]: -# support virtual hosting (such as qpidd). When set to true the virtual host
May  9 23:35:12 cmp02 salt-minion[2824]: -# name will be added to all message bus addresses, effectively creating a
May  9 23:35:12 cmp02 salt-minion[2824]: -# private 'subnet' per virtual host. Set to False if the message bus supports
May  9 23:35:12 cmp02 salt-minion[2824]: -# virtual hosting using the 'hostname' field in the AMQP 1.0 Open performative
May  9 23:35:12 cmp02 salt-minion[2824]: -# as the name of the virtual host. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pseudo_vhost = true
May  9 23:35:12 cmp02 salt-minion[2824]: +#addressing_mode=dynamic
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # address prefix used when sending to a specific server (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#server_request_prefix = exclusive
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/server_request_prefix
May  9 23:35:12 cmp02 salt-minion[2824]: +#server_request_prefix=exclusive
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # address prefix used when broadcasting to all servers (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#broadcast_prefix = broadcast
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/broadcast_prefix
May  9 23:35:12 cmp02 salt-minion[2824]: +#broadcast_prefix=broadcast
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # address prefix when sending to any server in group (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#group_request_prefix = unicast
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [amqp1]/group_request_prefix
May  9 23:35:12 cmp02 salt-minion[2824]: +#group_request_prefix=unicast
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Address prefix for all generated RPC addresses (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_address_prefix = openstack.org/om/rpc
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_address_prefix=openstack.org/om/rpc
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Address prefix for all generated Notification addresses (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#notify_address_prefix = openstack.org/om/notify
May  9 23:35:12 cmp02 salt-minion[2824]: +#notify_address_prefix=openstack.org/om/notify
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Appended to the address prefix when sending a fanout message. Used by the
May  9 23:35:12 cmp02 salt-minion[2824]:  # message bus to identify fanout messages. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#multicast_address = multicast
May  9 23:35:12 cmp02 salt-minion[2824]: +#multicast_address=multicast
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Appended to the address prefix when sending to a particular RPC/Notification
May  9 23:35:12 cmp02 salt-minion[2824]:  # server. Used by the message bus to identify messages sent to a single
May  9 23:35:12 cmp02 salt-minion[2824]:  # destination. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#unicast_address = unicast
May  9 23:35:12 cmp02 salt-minion[2824]: +#unicast_address=unicast
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Appended to the address prefix when sending to a group of consumers. Used by
May  9 23:35:12 cmp02 salt-minion[2824]:  # the message bus to identify messages that should be delivered in a round-robin
May  9 23:35:12 cmp02 salt-minion[2824]:  # fashion across consumers. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#anycast_address = anycast
May  9 23:35:12 cmp02 salt-minion[2824]: +#anycast_address=anycast
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name used in notification addresses.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name resolution precedence:
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -924,7 +7383,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # else default_notification_exchange if set
May  9 23:35:12 cmp02 salt-minion[2824]:  # else control_exchange if set
May  9 23:35:12 cmp02 salt-minion[2824]:  # else 'notify' (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_notification_exchange = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_notification_exchange=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name used in RPC addresses.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name resolution precedence:
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -932,19 +7391,19 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # else default_rpc_exchange if set
May  9 23:35:12 cmp02 salt-minion[2824]:  # else control_exchange if set
May  9 23:35:12 cmp02 salt-minion[2824]:  # else 'rpc' (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_rpc_exchange = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_rpc_exchange=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Window size for incoming RPC Reply messages. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#reply_link_credit = 200
May  9 23:35:12 cmp02 salt-minion[2824]: +#reply_link_credit=200
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Window size for incoming RPC Request messages (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_server_credit = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_server_credit=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Window size for incoming Notification messages (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#notify_server_credit = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +#notify_server_credit=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Send messages of this type pre-settled.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Pre-settled messages will not receive acknowledgement
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -956,8 +7415,8 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # 'rpc-cast' - Send RPC Casts pre-settled
May  9 23:35:12 cmp02 salt-minion[2824]:  # 'notify'   - Send Notifications pre-settled
May  9 23:35:12 cmp02 salt-minion[2824]:  #  (multi valued)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pre_settled = rpc-cast
May  9 23:35:12 cmp02 salt-minion[2824]: -#pre_settled = rpc-reply
May  9 23:35:12 cmp02 salt-minion[2824]: +#pre_settled=rpc-cast
May  9 23:35:12 cmp02 salt-minion[2824]: +#pre_settled=rpc-reply
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_messaging_kafka]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -970,7 +7429,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#kafka_default_host = localhost
May  9 23:35:12 cmp02 salt-minion[2824]: +#kafka_default_host=localhost
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Default Kafka broker Port (port value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -978,33 +7437,33 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#kafka_default_port = 9092
May  9 23:35:12 cmp02 salt-minion[2824]: +#kafka_default_port=9092
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Max fetch bytes of Kafka consumer (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#kafka_max_fetch_bytes = 1048576
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Default timeout(s) for Kafka consumers (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#kafka_consumer_timeout = 1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +#kafka_max_fetch_bytes=1048576
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Default timeout(s) for Kafka consumers (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#kafka_consumer_timeout=1.0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Pool Size for Kafka Consumers (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_size = 10
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_size=10
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The pool size limit for connections expiration policy (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#conn_pool_min_size = 2
May  9 23:35:12 cmp02 salt-minion[2824]: +#conn_pool_min_size=2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The time-to-live in sec of idle connections in the pool (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#conn_pool_ttl = 1200
May  9 23:35:12 cmp02 salt-minion[2824]: +#conn_pool_ttl=1200
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Group id for Kafka consumer. Consumers in one group will coordinate message
May  9 23:35:12 cmp02 salt-minion[2824]:  # consumption (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#consumer_group = oslo_messaging_consumer
May  9 23:35:12 cmp02 salt-minion[2824]: +#consumer_group=oslo_messaging_consumer
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Upper bound on the delay for KafkaProducer batching in seconds (floating point
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#producer_batch_timeout = 0.0
May  9 23:35:12 cmp02 salt-minion[2824]: +#producer_batch_timeout=0.0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Size of batch for the producer async send (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#producer_batch_size = 16384
May  9 23:35:12 cmp02 salt-minion[2824]: +#producer_batch_size=16384
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_messaging_notifications]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1012,6 +7471,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # From oslo.messaging
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: +driver = messagingv2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The Drivers(s) to handle sending notifications. Possible values are messaging,
May  9 23:35:12 cmp02 salt-minion[2824]:  # messagingv2, routing, log, test, noop (multi valued)
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1021,17 +7481,12 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # A URL representing the messaging driver to use for notifications. If not set,
May  9 23:35:12 cmp02 salt-minion[2824]:  # we fall back to the same configuration used for RPC. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/notification_transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#transport_url = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#transport_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # AMQP topic used for OpenStack notifications. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [rpc_notifier2]/topics
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/notification_topics
May  9 23:35:12 cmp02 salt-minion[2824]: -#topics = notifications
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The maximum number of attempts to re-send a notification message which failed
May  9 23:35:12 cmp02 salt-minion[2824]: -# to be delivered due to a recoverable error. 0 - No retry, -1 - indefinite
May  9 23:35:12 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#retry = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#topics=notifications
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_messaging_rabbit]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1043,110 +7498,122 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # Use durable queues in AMQP. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/amqp_durable_queues
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/rabbit_durable_queues
May  9 23:35:12 cmp02 salt-minion[2824]: -#amqp_durable_queues = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#amqp_durable_queues=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Auto-delete queues in AMQP. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#amqp_auto_delete = false
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enable SSL (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/amqp_auto_delete
May  9 23:35:12 cmp02 salt-minion[2824]: +#amqp_auto_delete=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and
May  9 23:35:12 cmp02 salt-minion[2824]:  # SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some
May  9 23:35:12 cmp02 salt-minion[2824]:  # distributions. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_version
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_version =
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/kombu_ssl_version
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_ssl_version =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # SSL key file (valid only if SSL enabled). (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_keyfile
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_key_file =
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/kombu_ssl_keyfile
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_ssl_keyfile =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # SSL cert file (valid only if SSL enabled). (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_certfile
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_cert_file =
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/kombu_ssl_certfile
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_ssl_certfile =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # SSL certification authority file (valid only if SSL enabled). (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_ca_certs
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_ca_file =
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/kombu_ssl_ca_certs
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_ssl_ca_certs =
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How long to wait before reconnecting in response to an AMQP consumer cancel
May  9 23:35:12 cmp02 salt-minion[2824]:  # notification. (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#kombu_reconnect_delay = 1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/kombu_reconnect_delay
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_reconnect_delay=1.0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not
May  9 23:35:12 cmp02 salt-minion[2824]:  # be used. This option may not be available in future versions. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#kombu_compression = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_compression=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How long to wait a missing client before abandoning to send it its replies.
May  9 23:35:12 cmp02 salt-minion[2824]:  # This value should not be longer than rpc_response_timeout. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [oslo_messaging_rabbit]/kombu_reconnect_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: -#kombu_missing_consumer_retry_timeout = 60
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_missing_consumer_retry_timeout=60
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Determines how the next RabbitMQ node is chosen in case the one we are
May  9 23:35:12 cmp02 salt-minion[2824]:  # currently connected to becomes unavailable. Takes effect only if more than one
May  9 23:35:12 cmp02 salt-minion[2824]:  # RabbitMQ node is provided in config. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: round-robin, shuffle
May  9 23:35:12 cmp02 salt-minion[2824]: -#kombu_failover_strategy = round-robin
May  9 23:35:12 cmp02 salt-minion[2824]: +#kombu_failover_strategy=round-robin
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The RabbitMQ broker address where a single node is used. (string
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_host
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_host = localhost
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_host=localhost
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The RabbitMQ broker port where a single node is used. (port value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_port
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_port = 5672
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_port=5672
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: RabbitMQ HA cluster host:port pairs. (list value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_hosts
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_hosts = $rabbit_host:$rabbit_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_hosts=$rabbit_host:$rabbit_port
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Connect over SSL for RabbitMQ. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_use_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_use_ssl=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The RabbitMQ userid. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_userid
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_userid = guest
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_userid=guest
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The RabbitMQ password. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_password
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_password = guest
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_password=guest
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The RabbitMQ login method. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: PLAIN, AMQPLAIN, RABBIT-CR-DEMO
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_login_method = AMQPLAIN
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_login_method
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_login_method=AMQPLAIN
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The RabbitMQ virtual host. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_virtual_host
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reason: Replaced by [DEFAULT]/transport_url
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_virtual_host = /
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_virtual_host=/
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How frequently to retry connecting with RabbitMQ. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_retry_interval = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_retry_interval=1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How long to backoff for between retries when connecting to RabbitMQ. (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_retry_backoff = 2
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_retry_backoff
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_retry_backoff=2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum interval of RabbitMQ connection retries. Default is 30 seconds.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_interval_max = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_interval_max=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: Maximum number of RabbitMQ connection retries. Default is 0
May  9 23:35:12 cmp02 salt-minion[2824]:  # (infinite retry count). (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_max_retries
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_max_retries = 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_max_retries=0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this
May  9 23:35:12 cmp02 salt-minion[2824]:  # option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1154,131 +7621,138 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # you just want to make sure that all queues (except those with auto-generated
May  9 23:35:12 cmp02 salt-minion[2824]:  # names) are mirrored across all nodes, run: "rabbitmqctl set_policy HA
May  9 23:35:12 cmp02 salt-minion[2824]:  # '^(?!amq\.).*' '{"ha-mode": "all"}' " (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_ha_queues = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rabbit_ha_queues
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_ha_queues=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Positive integer representing duration in seconds for queue TTL (x-expires).
May  9 23:35:12 cmp02 salt-minion[2824]:  # Queues which are unused for the duration of the TTL are automatically deleted.
May  9 23:35:12 cmp02 salt-minion[2824]:  # The parameter affects only reply and fanout queues. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_transient_queues_ttl = 1800
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_transient_queues_ttl=1800
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Specifies the number of messages to prefetch. Setting to zero allows unlimited
May  9 23:35:12 cmp02 salt-minion[2824]:  # messages. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rabbit_qos_prefetch_count = 64
May  9 23:35:12 cmp02 salt-minion[2824]: +#rabbit_qos_prefetch_count=0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Number of seconds after which the Rabbit broker is considered down if
May  9 23:35:12 cmp02 salt-minion[2824]:  # heartbeat's keep-alive fails (0 disable the heartbeat). EXPERIMENTAL (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#heartbeat_timeout_threshold = 60
May  9 23:35:12 cmp02 salt-minion[2824]: +#heartbeat_timeout_threshold=60
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How often times during the heartbeat_timeout_threshold we check the heartbeat.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#heartbeat_rate = 2
May  9 23:35:12 cmp02 salt-minion[2824]: +#heartbeat_rate=2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#fake_rabbit = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/fake_rabbit
May  9 23:35:12 cmp02 salt-minion[2824]: +#fake_rabbit=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of channels to allow (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#channel_max = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#channel_max=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The maximum byte size for an AMQP frame (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#frame_max = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#frame_max=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How often to send heartbeats for consumer's connections (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#heartbeat_interval = 3
May  9 23:35:12 cmp02 salt-minion[2824]: +#heartbeat_interval=3
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable SSL (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ssl=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Arguments passed to ssl.wrap_socket (dict value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#ssl_options = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +#ssl_options=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set socket timeout in seconds for connection's socket (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#socket_timeout = 0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +#socket_timeout=0.25
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set TCP_USER_TIMEOUT in seconds for connection's socket (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#tcp_user_timeout = 0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +#tcp_user_timeout=0.25
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set delay for reconnection to some host which has connection error (floating
May  9 23:35:12 cmp02 salt-minion[2824]:  # point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#host_connection_reconnect_delay = 0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_connection_reconnect_delay=0.25
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Connection factory implementation (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: new, single, read_write
May  9 23:35:12 cmp02 salt-minion[2824]: -#connection_factory = single
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_factory=single
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of connections to keep queued. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_max_size = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_max_size=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of connections to create above `pool_max_size`. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_max_overflow = 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_max_overflow=0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Default number of seconds to wait for a connections to available (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_timeout = 30
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_timeout=30
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Lifetime of a connection (since creation) in seconds or None for no recycling.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Expired connections are closed on acquire. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_recycle = 600
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_recycle=600
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Threshold at which inactive (since release) connections are considered stale
May  9 23:35:12 cmp02 salt-minion[2824]:  # in seconds or None for no staleness. Stale connections are closed on acquire.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#pool_stale = 60
May  9 23:35:12 cmp02 salt-minion[2824]: +#pool_stale=60
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Default serialization mechanism for serializing/deserializing
May  9 23:35:12 cmp02 salt-minion[2824]:  # outgoing/incoming messages (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: json, msgpack
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_serializer_type = json
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_serializer_type=json
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Persist notification messages. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#notification_persistence = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#notification_persistence=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name for sending notifications (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_notification_exchange = ${control_exchange}_notification
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_notification_exchange=${control_exchange}_notification
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Max number of not acknowledged message which RabbitMQ can send to notification
May  9 23:35:12 cmp02 salt-minion[2824]:  # listener. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#notification_listener_prefetch_count = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +#notification_listener_prefetch_count=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reconnecting retry count in case of connectivity problem during sending
May  9 23:35:12 cmp02 salt-minion[2824]:  # notification, -1 means infinite retry. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_notification_retry_attempts = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_notification_retry_attempts=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reconnecting retry delay in case of connectivity problem during sending
May  9 23:35:12 cmp02 salt-minion[2824]:  # notification message (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#notification_retry_delay = 0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +#notification_retry_delay=0.25
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Time to live for rpc queues without consumers in seconds. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_queue_expiration = 60
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_queue_expiration=60
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name for sending RPC messages (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_rpc_exchange = ${control_exchange}_rpc
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_rpc_exchange=${control_exchange}_rpc
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Exchange name for receiving RPC replies (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_reply_exchange = ${control_exchange}_rpc_reply
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_reply_exchange=${control_exchange}_rpc_reply
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Max number of not acknowledged message which RabbitMQ can send to rpc
May  9 23:35:12 cmp02 salt-minion[2824]:  # listener. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_listener_prefetch_count = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_listener_prefetch_count=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Max number of not acknowledged message which RabbitMQ can send to rpc reply
May  9 23:35:12 cmp02 salt-minion[2824]:  # listener. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_reply_listener_prefetch_count = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_reply_listener_prefetch_count=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reconnecting retry count in case of connectivity problem during sending reply.
May  9 23:35:12 cmp02 salt-minion[2824]:  # -1 means infinite retry during rpc_timeout (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_reply_retry_attempts = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_reply_retry_attempts=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reconnecting retry delay in case of connectivity problem during sending reply.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_reply_retry_delay = 0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_reply_retry_delay=0.25
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reconnecting retry count in case of connectivity problem during sending RPC
May  9 23:35:12 cmp02 salt-minion[2824]:  # message, -1 means infinite retry. If actual retry attempts in not 0 the rpc
May  9 23:35:12 cmp02 salt-minion[2824]:  # request could be processed more than one time (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_rpc_retry_attempts = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_rpc_retry_attempts=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Reconnecting retry delay in case of connectivity problem during sending RPC
May  9 23:35:12 cmp02 salt-minion[2824]:  # message (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_retry_delay = 0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_retry_delay=0.25
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_messaging_zmq]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1289,25 +7763,31 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP.
May  9 23:35:12 cmp02 salt-minion[2824]:  # The "host" option should point or resolve to this address. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_bind_address = *
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_bind_address
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_bind_address=*
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # MatchMaker driver. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: redis, sentinel, dummy
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_matchmaker = redis
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_matchmaker
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_matchmaker=redis
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Number of ZeroMQ contexts, defaults to 1. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_contexts = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_contexts
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_contexts=1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of ingress messages to locally buffer per topic. Default is
May  9 23:35:12 cmp02 salt-minion[2824]:  # unlimited. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_topic_backlog = <None>
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_topic_backlog
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_topic_backlog=<None>
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Directory for holding IPC sockets. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_ipc_dir = /var/run/openstack
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_ipc_dir
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_ipc_dir=/var/run/openstack
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Name of this node. Must be a valid hostname, FQDN, or IP address. Must match
May  9 23:35:12 cmp02 salt-minion[2824]:  # "host" option, if running Nova. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_host = localhost
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_host
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_host=localhost
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Number of seconds to wait before all pending messages will be sent after
May  9 23:35:12 cmp02 salt-minion[2824]:  # closing a socket. The default value of -1 specifies an infinite linger period.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1315,110 +7795,119 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # immediately when the socket is closed. Positive values specify an upper bound
May  9 23:35:12 cmp02 salt-minion[2824]:  # for the linger period. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/rpc_cast_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_linger = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_linger=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The default number of seconds that poll should wait. Poll raises timeout
May  9 23:35:12 cmp02 salt-minion[2824]:  # exception when timeout expired. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_poll_timeout = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_poll_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_poll_timeout=1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Expiration timeout in seconds of a name service record about existing target (
May  9 23:35:12 cmp02 salt-minion[2824]:  # < 0 means no timeout). (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_target_expire = 300
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/zmq_target_expire
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_target_expire=300
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Update period in seconds of a name service record about existing target.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_target_update = 180
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/zmq_target_update
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_target_update=180
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. (boolean
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#use_pub_sub = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/use_pub_sub
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_pub_sub=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Use ROUTER remote proxy. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#use_router_proxy = false
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/use_router_proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_router_proxy=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option makes direct connections dynamic or static. It makes sense only
May  9 23:35:12 cmp02 salt-minion[2824]:  # with use_router_proxy=False which means to use direct connections for direct
May  9 23:35:12 cmp02 salt-minion[2824]:  # message types (ignored otherwise). (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#use_dynamic_connections = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_dynamic_connections=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # How many additional connections to a host will be made for failover reasons.
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is actual only in dynamic connections mode. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_failover_connections = 2
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_failover_connections=2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimal port number for random ports range. (port value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_min_port = 49153
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_min_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_min_port=49153
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximal port number for random ports range. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum value: 65536
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_max_port = 65536
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_max_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_max_port=65536
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Number of retries to find free port number before fail with ZMQBindError.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_bind_port_retries = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_bind_port_retries
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_bind_port_retries=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Default serialization mechanism for serializing/deserializing
May  9 23:35:12 cmp02 salt-minion[2824]:  # outgoing/incoming messages (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Allowed values: json, msgpack
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_zmq_serialization = json
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/rpc_zmq_serialization
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_zmq_serialization=json
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option configures round-robin mode in zmq socket. True means not keeping
May  9 23:35:12 cmp02 salt-minion[2824]:  # a queue when server side disconnects. False means to keep queue and messages
May  9 23:35:12 cmp02 salt-minion[2824]:  # even if server is disconnected, when the server appears we send all
May  9 23:35:12 cmp02 salt-minion[2824]:  # accumulated messages to it. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_immediate = true
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_immediate=true
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any
May  9 23:35:12 cmp02 salt-minion[2824]:  # other negative value) means to skip any overrides and leave it to OS default;
May  9 23:35:12 cmp02 salt-minion[2824]:  # 0 and 1 (or any other positive value) mean to disable and enable the option
May  9 23:35:12 cmp02 salt-minion[2824]:  # respectively. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The duration between two keepalive transmissions in idle condition. The unit
May  9 23:35:12 cmp02 salt-minion[2824]:  # is platform dependent, for example, seconds in Linux, milliseconds in Windows
May  9 23:35:12 cmp02 salt-minion[2824]:  # etc. The default value of -1 (or any other negative value and 0) means to skip
May  9 23:35:12 cmp02 salt-minion[2824]:  # any overrides and leave it to OS default. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_idle = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive_idle=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The number of retransmissions to be carried out before declaring that remote
May  9 23:35:12 cmp02 salt-minion[2824]:  # end is not available. The default value of -1 (or any other negative value and
May  9 23:35:12 cmp02 salt-minion[2824]:  # 0) means to skip any overrides and leave it to OS default. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_cnt = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive_cnt=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The duration between two successive keepalive retransmissions, if
May  9 23:35:12 cmp02 salt-minion[2824]:  # acknowledgement to the previous keepalive transmission is not received. The
May  9 23:35:12 cmp02 salt-minion[2824]:  # unit is platform dependent, for example, seconds in Linux, milliseconds in
May  9 23:35:12 cmp02 salt-minion[2824]:  # Windows etc. The default value of -1 (or any other negative value and 0) means
May  9 23:35:12 cmp02 salt-minion[2824]:  # to skip any overrides and leave it to OS default. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_intvl = -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#zmq_tcp_keepalive_intvl=-1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Maximum number of (green) threads to work concurrently. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_thread_pool_size = 100
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_thread_pool_size=100
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Expiration timeout in seconds of a sent/received message after which it is not
May  9 23:35:12 cmp02 salt-minion[2824]:  # tracked anymore by a client/server. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_message_ttl = 300
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_message_ttl=300
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Wait for message acknowledgements from receivers. This mechanism works only
May  9 23:35:12 cmp02 salt-minion[2824]:  # via proxy without PUB/SUB. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_use_acks = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_use_acks=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Number of seconds to wait for an ack from a cast/call. After each retry
May  9 23:35:12 cmp02 salt-minion[2824]:  # attempt this timeout is multiplied by some specified multiplier. (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_ack_timeout_base = 15
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_ack_timeout_base=15
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Number to multiply base ack timeout by after each retry attempt. (integer
May  9 23:35:12 cmp02 salt-minion[2824]:  # value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_ack_timeout_multiplier = 2
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_ack_timeout_multiplier=2
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Default number of message sending attempts in case of any problems occurred:
May  9 23:35:12 cmp02 salt-minion[2824]:  # positive value N means at most N retries, 0 means no retries, None or -1 (or
May  9 23:35:12 cmp02 salt-minion[2824]:  # any other negative values) mean to retry forever. This option is used only if
May  9 23:35:12 cmp02 salt-minion[2824]:  # acknowledgments are enabled. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#rpc_retry_attempts = 3
May  9 23:35:12 cmp02 salt-minion[2824]: +#rpc_retry_attempts=3
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # List of publisher hosts SubConsumer can subscribe on. This option has higher
May  9 23:35:12 cmp02 salt-minion[2824]:  # priority then the default publishers list taken from the matchmaker. (list
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1435,18 +7924,18 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # The maximum body size for each  request, in bytes. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/osapi_max_request_body_size
May  9 23:35:12 cmp02 salt-minion[2824]:  # Deprecated group/name - [DEFAULT]/max_request_body_size
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_request_body_size = 114688
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_request_body_size=114688
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # DEPRECATED: The HTTP Header that will be used to determine what the original
May  9 23:35:12 cmp02 salt-minion[2824]:  # request protocol scheme was, even if it was hidden by a SSL termination proxy.
May  9 23:35:12 cmp02 salt-minion[2824]:  # (string value)
May  9 23:35:12 cmp02 salt-minion[2824]:  # This option is deprecated for removal.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: -#secure_proxy_ssl_header = X-Forwarded-Proto
May  9 23:35:12 cmp02 salt-minion[2824]: +#secure_proxy_ssl_header=X-Forwarded-Proto
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Whether the application is behind a proxy or not. This determines if the
May  9 23:35:12 cmp02 salt-minion[2824]:  # middleware should parse the headers or not. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#enable_proxy_headers_parsing = false
May  9 23:35:12 cmp02 salt-minion[2824]: +#enable_proxy_headers_parsing=false
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  [oslo_policy]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1456,14 +7945,2772 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The file that defines policies. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#policy_file = policy.json
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/policy_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#policy_file=policy.json
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Default rule. Enforced when a requested rule is not found. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: -#policy_default_rule = default
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/policy_default_rule
May  9 23:35:12 cmp02 salt-minion[2824]: +#policy_default_rule=default
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Directories where policy configuration files are stored. They can be relative
May  9 23:35:12 cmp02 salt-minion[2824]:  # to any directory in the search path defined by the config_dir option, or
May  9 23:35:12 cmp02 salt-minion[2824]:  # absolute paths. The file defined by policy_file must exist for these
May  9 23:35:12 cmp02 salt-minion[2824]:  # directories to be searched.  Missing or empty directories are ignored. (multi
May  9 23:35:12 cmp02 salt-minion[2824]:  # valued)
May  9 23:35:12 cmp02 salt-minion[2824]: -#policy_dirs = policy.d
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/policy_dirs
May  9 23:35:12 cmp02 salt-minion[2824]: +#policy_dirs=policy.d
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[pci]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An alias for a PCI passthrough device requirement.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This allows users to specify the alias in the extra_spec for a flavor, without
May  9 23:35:12 cmp02 salt-minion[2824]: +# needing to repeat all the PCI property requirements.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A list of JSON values which describe the aliases. For example:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     alias = {
May  9 23:35:12 cmp02 salt-minion[2824]: +#       "name": "QuickAssist",
May  9 23:35:12 cmp02 salt-minion[2824]: +#       "product_id": "0443",
May  9 23:35:12 cmp02 salt-minion[2824]: +#       "vendor_id": "8086",
May  9 23:35:12 cmp02 salt-minion[2824]: +#       "device_type": "type-PCI"
May  9 23:35:12 cmp02 salt-minion[2824]: +#     }
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   defines an alias for the Intel QuickAssist card. (multi valued). Valid key
May  9 23:35:12 cmp02 salt-minion[2824]: +#   values are :
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "name": Name of the PCI alias.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "product_id": Product ID of the device in hexadecimal.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "vendor_id": Vendor ID of the device in hexadecimal.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "device_type": Type of PCI device. Valid values are: "type-PCI",
May  9 23:35:12 cmp02 salt-minion[2824]: +#     "type-PF" and "type-VF".
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/pci_alias
May  9 23:35:12 cmp02 salt-minion[2824]: +#alias =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# White list of PCI devices available to VMs.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A JSON dictionary which describe a whitelisted PCI device. It should take
May  9 23:35:12 cmp02 salt-minion[2824]: +#   the following format:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     ["vendor_id": "<id>",] ["product_id": "<id>",]
May  9 23:35:12 cmp02 salt-minion[2824]: +#     ["address": "[[[[<domain>]:]<bus>]:][<slot>][.[<function>]]" |
May  9 23:35:12 cmp02 salt-minion[2824]: +#      "devname": "<name>",]
May  9 23:35:12 cmp02 salt-minion[2824]: +#     {"<tag>": "<tag_value>",}
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   Where '[' indicates zero or one occurrences, '{' indicates zero or multiple
May  9 23:35:12 cmp02 salt-minion[2824]: +#   occurrences, and '|' mutually exclusive options. Note that any missing
May  9 23:35:12 cmp02 salt-minion[2824]: +#   fields are automatically wildcarded.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   Valid key values are :
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "vendor_id": Vendor ID of the device in hexadecimal.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "product_id": Product ID of the device in hexadecimal.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "address": PCI address of the device.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "devname": Device name of the device (for e.g. interface name). Not all
May  9 23:35:12 cmp02 salt-minion[2824]: +#     PCI devices have a name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   * "<tag>": Additional <tag> and <tag_value> used for matching PCI devices.
May  9 23:35:12 cmp02 salt-minion[2824]: +#     Supported <tag>: "physical_network".
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The address key supports traditional glob style and regular expression
May  9 23:35:12 cmp02 salt-minion[2824]: +#   syntax. Valid examples are:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"devname":"eth0",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "physical_network":"physnet"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"address":"*:0a:00.*"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"address":":0a:00.",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "physical_network":"physnet1"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"vendor_id":"1137",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "product_id":"0071"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"vendor_id":"1137",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "product_id":"0071",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "address": "0000:0a:00.1",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "physical_network":"physnet1"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"address":{"domain": ".*",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                                         "bus": "02", "slot": "01",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                                         "function": "[2-7]"},
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "physical_network":"physnet1"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"address":{"domain": ".*",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                                         "bus": "02", "slot": "0[1-2]",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                                         "function": ".*"},
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "physical_network":"physnet1"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The following are invalid, as they specify mutually exclusive options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = {"devname":"eth0",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "physical_network":"physnet",
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              "address":"*:0a:00.*"}
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A JSON list of JSON dictionaries corresponding to the above format. For
May  9 23:35:12 cmp02 salt-minion[2824]: +#   example:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     passthrough_whitelist = [{"product_id":"0001", "vendor_id":"8086"},
May  9 23:35:12 cmp02 salt-minion[2824]: +#                              {"product_id":"0002", "vendor_id":"8086"}]
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (multi valued)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/pci_passthrough_whitelist
May  9 23:35:12 cmp02 salt-minion[2824]: +#passthrough_whitelist =
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[placement]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_type = password
May  9 23:35:12 cmp02 salt-minion[2824]: +user_domain_id = default
May  9 23:35:12 cmp02 salt-minion[2824]: +project_domain_id = default
May  9 23:35:12 cmp02 salt-minion[2824]: +project_name = service
May  9 23:35:12 cmp02 salt-minion[2824]: +username = nova
May  9 23:35:12 cmp02 salt-minion[2824]: +password = opnfv_secret
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_url=http://172.16.10.36:35357/v3
May  9 23:35:12 cmp02 salt-minion[2824]: +os_interface = internal
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Region name of this node. This is used when picking the URL in the service
May  9 23:35:12 cmp02 salt-minion[2824]: +# catalog.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string representing region name
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#os_region_name = openstack
May  9 23:35:12 cmp02 salt-minion[2824]: +os_region_name = RegionOne
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Endpoint interface for this node. This is used when picking the URL in the
May  9 23:35:12 cmp02 salt-minion[2824]: +# service catalog.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#os_interface=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded Certificate Authority to use when verifying HTTPs connections.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cafile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate cert file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#certfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate key file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#keyfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Verify HTTPS connections. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Timeout value for http requests (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#timeout=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication type to load (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [placement]/auth_plugin
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Config Section from which to load plugin specific options (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_section=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication URL (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Trust ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#trust_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain ID to use with v3 and v2 parameters. It will be used for both
May  9 23:35:12 cmp02 salt-minion[2824]: +# the user and project domain in v3 and ignored in v2 authentication. (string
May  9 23:35:12 cmp02 salt-minion[2824]: +# value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain name to use with v3 API and v2 parameters. It will be used for
May  9 23:35:12 cmp02 salt-minion[2824]: +# both the user and project domain in v3 and ignored in v2 authentication.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [placement]/user-name
May  9 23:35:12 cmp02 salt-minion[2824]: +#username=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain id (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's password (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant Name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[quota]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Quota options allow to manage quotas in openstack deployment.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of instances allowed per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible Values
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_instances
May  9 23:35:12 cmp02 salt-minion[2824]: +#instances=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of instance cores or vCPUs allowed per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_cores
May  9 23:35:12 cmp02 salt-minion[2824]: +#cores=20
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of megabytes of instance RAM allowed per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_ram
May  9 23:35:12 cmp02 salt-minion[2824]: +#ram=51200
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of floating IPs allowed per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Floating IPs are not allocated to instances by default. Users need to select
May  9 23:35:12 cmp02 salt-minion[2824]: +# them from the pool configured by the OpenStack administrator to attach to
May  9 23:35:12 cmp02 salt-minion[2824]: +# their
May  9 23:35:12 cmp02 salt-minion[2824]: +# instances.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_floating_ips
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#floating_ips=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of fixed IPs allowed per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Unlike floating IPs, fixed IPs are allocated dynamically by the network
May  9 23:35:12 cmp02 salt-minion[2824]: +# component when instances boot up.  This quota value should be at least the
May  9 23:35:12 cmp02 salt-minion[2824]: +# number of instances allowed
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_fixed_ips
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#fixed_ips=-1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of metadata items allowed per instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Users can associate metadata with an instance during instance creation. This
May  9 23:35:12 cmp02 salt-minion[2824]: +# metadata takes the form of key-value pairs.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_metadata_items
May  9 23:35:12 cmp02 salt-minion[2824]: +#metadata_items=128
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of injected files allowed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# File injection allows users to customize the personality of an instance by
May  9 23:35:12 cmp02 salt-minion[2824]: +# injecting data into it upon boot. Only text file injection is permitted:
May  9 23:35:12 cmp02 salt-minion[2824]: +# binary
May  9 23:35:12 cmp02 salt-minion[2824]: +# or ZIP files are not accepted. During file injection, any existing files that
May  9 23:35:12 cmp02 salt-minion[2824]: +# match specified files are renamed to include ``.bak`` extension appended with
May  9 23:35:12 cmp02 salt-minion[2824]: +# a
May  9 23:35:12 cmp02 salt-minion[2824]: +# timestamp.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_injected_files
May  9 23:35:12 cmp02 salt-minion[2824]: +#injected_files=5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of bytes allowed per injected file.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_injected_file_content_bytes
May  9 23:35:12 cmp02 salt-minion[2824]: +#injected_file_content_bytes=10240
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The maximum allowed injected file path length.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_injected_file_path_length
May  9 23:35:12 cmp02 salt-minion[2824]: +#injected_file_path_length=255
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of security groups per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_security_groups
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#security_groups=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of security rules per security group.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The associated rules in each security group control the traffic to instances
May  9 23:35:12 cmp02 salt-minion[2824]: +# in
May  9 23:35:12 cmp02 salt-minion[2824]: +# the group.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_security_group_rules
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova-network is deprecated, as are any related configuration options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#security_group_rules=20
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The maximum number of key pairs allowed per user.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Users can create at least one key pair for each project and use the key pair
May  9 23:35:12 cmp02 salt-minion[2824]: +# for multiple instances that belong to that project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_key_pairs
May  9 23:35:12 cmp02 salt-minion[2824]: +#key_pairs=100
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The maxiumum number of server groups per project.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Server groups are used to control the affinity and anti-affinity scheduling
May  9 23:35:12 cmp02 salt-minion[2824]: +# policy for a group of servers or instances. Reducing the quota will not affect
May  9 23:35:12 cmp02 salt-minion[2824]: +# any existing group, but new servers will not be allowed into groups that have
May  9 23:35:12 cmp02 salt-minion[2824]: +# become over quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_server_groups
May  9 23:35:12 cmp02 salt-minion[2824]: +#server_groups=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The maximum number of servers per server group.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer or 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * -1 to disable the quota.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_server_group_members
May  9 23:35:12 cmp02 salt-minion[2824]: +#server_group_members=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of seconds until a reservation expires.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This quota represents the time period for invalidating quota reservations.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/reservation_expire
May  9 23:35:12 cmp02 salt-minion[2824]: +#reservation_expire=86400
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The count of reservations until usage is refreshed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This defaults to 0 (off) to avoid additional load but it is useful to turn on
May  9 23:35:12 cmp02 salt-minion[2824]: +# to help keep quota usage up-to-date and reduce the impact of out of sync usage
May  9 23:35:12 cmp02 salt-minion[2824]: +# issues.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/until_refresh
May  9 23:35:12 cmp02 salt-minion[2824]: +#until_refresh=0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The number of seconds between subsequent usage refreshes.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This defaults to 0 (off) to avoid additional load but it is useful to turn on
May  9 23:35:12 cmp02 salt-minion[2824]: +# to help keep quota usage up-to-date and reduce the impact of out of sync usage
May  9 23:35:12 cmp02 salt-minion[2824]: +# issues. Note that quotas are not updated on a periodic task, they will update
May  9 23:35:12 cmp02 salt-minion[2824]: +# on a new reservation if max_age has passed since the last reservation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/max_age
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_age=0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The quota enforcer driver.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Provides abstraction for quota checks. Users can configure a specific
May  9 23:35:12 cmp02 salt-minion[2824]: +# driver to use for quota checks.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * nova.quota.DbQuotaDriver (default) or any string representing fully
May  9 23:35:12 cmp02 salt-minion[2824]: +#   qualified class name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/quota_driver
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 14.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +#driver=nova.quota.DbQuotaDriver
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[rdp]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Options under this group enable and configure Remote Desktop Protocol (
May  9 23:35:12 cmp02 salt-minion[2824]: +# RDP) related features.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This group is only relevant to Hyper-V users.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable Remote Desktop Protocol (RDP) related features.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Hyper-V, unlike the majority of the hypervisors employed on Nova compute
May  9 23:35:12 cmp02 salt-minion[2824]: +# nodes, uses RDP instead of VNC and SPICE as a desktop sharing protocol to
May  9 23:35:12 cmp02 salt-minion[2824]: +# provide instance console access. This option enables RDP for graphical
May  9 23:35:12 cmp02 salt-minion[2824]: +# console access for virtual machines created by Hyper-V.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# **Note:** RDP should only be enabled on compute nodes that support the Hyper-V
May  9 23:35:12 cmp02 salt-minion[2824]: +# virtualization platform.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``compute_driver``: Must be hyperv.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The URL an end user would use to connect to the RDP HTML5 console proxy.
May  9 23:35:12 cmp02 salt-minion[2824]: +# The console proxy service is called with this token-embedded URL and
May  9 23:35:12 cmp02 salt-minion[2824]: +# establishes the connection to the proper instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An RDP HTML5 console proxy service will need to be configured to listen on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# address configured here. Typically the console proxy service would be run on a
May  9 23:35:12 cmp02 salt-minion[2824]: +# controller node. The localhost address used as default would only work in a
May  9 23:35:12 cmp02 salt-minion[2824]: +# single node environment i.e. devstack.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An RDP HTML5 proxy allows a user to access via the web the text or graphical
May  9 23:35:12 cmp02 salt-minion[2824]: +# console of any Windows server or workstation using RDP. RDP HTML5 console
May  9 23:35:12 cmp02 salt-minion[2824]: +# proxy services include FreeRDP, wsgate.
May  9 23:35:12 cmp02 salt-minion[2824]: +# See https://github.com/FreeRDP/FreeRDP-WebConnect
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * <scheme>://<ip-address>:<port-number>/
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The scheme must be identical to the scheme configured for the RDP HTML5
May  9 23:35:12 cmp02 salt-minion[2824]: +#   console proxy service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The IP address must be identical to the address on which the RDP HTML5
May  9 23:35:12 cmp02 salt-minion[2824]: +#   console proxy service is listening.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The port must be identical to the port on which the RDP HTML5 console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +#   service is listening.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``rdp.enabled``: Must be set to ``True`` for ``html5_proxy_base_url`` to be
May  9 23:35:12 cmp02 salt-minion[2824]: +#   effective.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#html5_proxy_base_url=http://127.0.0.1:6083/
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[remote_debug]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Debug host (IP or name) to connect to. This command line parameter is used
May  9 23:35:12 cmp02 salt-minion[2824]: +# when
May  9 23:35:12 cmp02 salt-minion[2824]: +# you want to connect to a nova service via a debugger running on a different
May  9 23:35:12 cmp02 salt-minion[2824]: +# host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note that using the remote debug option changes how Nova uses the eventlet
May  9 23:35:12 cmp02 salt-minion[2824]: +# library to support async IO. This could result in failures that do not occur
May  9 23:35:12 cmp02 salt-minion[2824]: +# under normal operation. Use at your own risk.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#    * IP address of a remote host as a command line parameter
May  9 23:35:12 cmp02 salt-minion[2824]: +#      to a nova service. For Example:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#     --remote_debug-host <IP address where the debugger is running>
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#host=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Debug port to connect to. This command line parameter allows you to specify
May  9 23:35:12 cmp02 salt-minion[2824]: +# the port you want to use to connect to a nova service via a debugger running
May  9 23:35:12 cmp02 salt-minion[2824]: +# on different host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note that using the remote debug option changes how Nova uses the eventlet
May  9 23:35:12 cmp02 salt-minion[2824]: +# library to support async IO. This could result in failures that do not occur
May  9 23:35:12 cmp02 salt-minion[2824]: +# under normal operation. Use at your own risk.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible Values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#    * Port number you want to use as a command line parameter
May  9 23:35:12 cmp02 salt-minion[2824]: +#      to a nova service. For Example:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#     /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#     --remote_debug-host <IP address where the debugger is running>
May  9 23:35:12 cmp02 salt-minion[2824]: +#     --remote_debug-port <port> it's listening on>.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#port=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[scheduler]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The scheduler host manager to use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The host manager manages the in-memory picture of the hosts that the scheduler
May  9 23:35:12 cmp02 salt-minion[2824]: +# uses. The options values are chosen from the entry points under the namespace
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'nova.scheduler.host_manager' in 'setup.cfg'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: host_manager, ironic_host_manager
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_host_manager
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_manager=host_manager
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The class of the driver used by the scheduler.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The options are chosen from the entry points under the namespace
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'nova.scheduler.driver' in 'setup.cfg'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string, where the string corresponds to the class name of a scheduler
May  9 23:35:12 cmp02 salt-minion[2824]: +#   driver. There are a number of options available:
May  9 23:35:12 cmp02 salt-minion[2824]: +# ** 'caching_scheduler', which aggressively caches the system state for better
May  9 23:35:12 cmp02 salt-minion[2824]: +#    individual scheduler performance at the risk of more retries when running
May  9 23:35:12 cmp02 salt-minion[2824]: +#    multiple schedulers
May  9 23:35:12 cmp02 salt-minion[2824]: +# ** 'chance_scheduler', which simply picks a host at random
May  9 23:35:12 cmp02 salt-minion[2824]: +# ** 'fake_scheduler', which is used for testing
May  9 23:35:12 cmp02 salt-minion[2824]: +# ** A custom scheduler driver. In this case, you will be responsible for
May  9 23:35:12 cmp02 salt-minion[2824]: +#    creating and maintaining the entry point in your 'setup.cfg' file
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: filter_scheduler, caching_scheduler, chance_scheduler, fake_scheduler
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_driver
May  9 23:35:12 cmp02 salt-minion[2824]: +#driver=filter_scheduler
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Periodic task interval.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This value controls how often (in seconds) to run periodic tasks in the
May  9 23:35:12 cmp02 salt-minion[2824]: +# scheduler. The specific tasks that are run for each period are determined by
May  9 23:35:12 cmp02 salt-minion[2824]: +# the particular scheduler being used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If this is larger than the nova-service 'service_down_time' setting, Nova may
May  9 23:35:12 cmp02 salt-minion[2824]: +# report the scheduler service as down. This is because the scheduler driver is
May  9 23:35:12 cmp02 salt-minion[2824]: +# responsible for sending a heartbeat and it will only do that as often as this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option allows. As each scheduler can work a little differently than the
May  9 23:35:12 cmp02 salt-minion[2824]: +# others,
May  9 23:35:12 cmp02 salt-minion[2824]: +# be sure to test this with your selected scheduler.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An integer, where the integer corresponds to periodic task interval in
May  9 23:35:12 cmp02 salt-minion[2824]: +#   seconds. 0 uses the default interval (60 seconds). A negative value disables
May  9 23:35:12 cmp02 salt-minion[2824]: +#   periodic tasks.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``nova-service service_down_time``
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_driver_task_period
May  9 23:35:12 cmp02 salt-minion[2824]: +#periodic_task_interval=60
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum number of schedule attempts for a chosen host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is the maximum number of attempts that will be made to schedule an
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance before it is assumed that the failures aren't due to normal
May  9 23:35:12 cmp02 salt-minion[2824]: +# occasional
May  9 23:35:12 cmp02 salt-minion[2824]: +# race conflicts, but rather some other problem. When this is reached a
May  9 23:35:12 cmp02 salt-minion[2824]: +# MaxRetriesExceeded exception is raised, and the instance is set to an error
May  9 23:35:12 cmp02 salt-minion[2824]: +# state.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A positive integer, where the integer corresponds to the max number of
May  9 23:35:12 cmp02 salt-minion[2824]: +#   attempts that can be made when scheduling an instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#          (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/scheduler_max_attempts
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_attempts=3
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Periodic task interval.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This value controls how often (in seconds) the scheduler should attempt
May  9 23:35:12 cmp02 salt-minion[2824]: +# to discover new hosts that have been added to cells. If negative (the
May  9 23:35:12 cmp02 salt-minion[2824]: +# default), no automatic discovery will occur.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Small deployments may want this periodic task enabled, as surveying the
May  9 23:35:12 cmp02 salt-minion[2824]: +# cells for new hosts is likely to be lightweight enough to not cause undue
May  9 23:35:12 cmp02 salt-minion[2824]: +# burdon to the scheduler. However, larger clouds (and those that are not
May  9 23:35:12 cmp02 salt-minion[2824]: +# adding hosts regularly) will likely want to disable this automatic
May  9 23:35:12 cmp02 salt-minion[2824]: +# behavior and instead use the `nova-manage cell_v2 discover_hosts` command
May  9 23:35:12 cmp02 salt-minion[2824]: +# when hosts have been added to a cell.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +#discover_hosts_in_cells_interval=-1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[serial_console]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The serial console feature allows you to connect to a guest in case a
May  9 23:35:12 cmp02 salt-minion[2824]: +# graphical console like VNC, RDP or SPICE is not available. This is only
May  9 23:35:12 cmp02 salt-minion[2824]: +# currently supported for the libvirt, Ironic and hyper-v drivers.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable the serial console feature.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# In order to use this feature, the service ``nova-serialproxy`` needs to run.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This service is typically executed on the controller node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# A range of TCP ports a guest can use for its backend.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Each instance which gets created will use one port out of this range. If the
May  9 23:35:12 cmp02 salt-minion[2824]: +# range is not big enough to provide another port for an new instance, this
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance won't get launched.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Each string which passes the regex ``\d+:\d+`` For example ``10000:20000``.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   Be sure that the first port number is lower than the second port number
May  9 23:35:12 cmp02 salt-minion[2824]: +#   and that both are in range from 0 to 65535.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#port_range=10000:20000
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The URL an end user would use to connect to the ``nova-serialproxy`` service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ``nova-serialproxy`` service is called with this token enriched URL
May  9 23:35:12 cmp02 salt-minion[2824]: +# and establishes the connection to the proper instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The IP address must be identical to the address to which the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ``nova-serialproxy`` service is listening (see option ``serialproxy_host``
May  9 23:35:12 cmp02 salt-minion[2824]: +#   in this section).
May  9 23:35:12 cmp02 salt-minion[2824]: +# * The port must be the same as in the option ``serialproxy_port`` of this
May  9 23:35:12 cmp02 salt-minion[2824]: +#   section.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If you choose to use a secured websocket connection, then start this option
May  9 23:35:12 cmp02 salt-minion[2824]: +#   with ``wss://`` instead of the unsecured ``ws://``. The options ``cert``
May  9 23:35:12 cmp02 salt-minion[2824]: +#   and ``key`` in the ``[DEFAULT]`` section have to be set for that.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (uri value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#base_url=ws://127.0.0.1:6083/
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The IP address to which proxy clients (like ``nova-serialproxy``) should
May  9 23:35:12 cmp02 salt-minion[2824]: +# connect to get the serial console of an instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is typically the IP address of the host of a ``nova-compute`` service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#proxyclient_address=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The IP address which is used by the ``nova-serialproxy`` service to listen
May  9 23:35:12 cmp02 salt-minion[2824]: +# for incoming requests.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ``nova-serialproxy`` service listens on this IP address for incoming
May  9 23:35:12 cmp02 salt-minion[2824]: +# connection requests to instances which expose serial console.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Ensure that this is the same IP address which is defined in the option
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ``base_url`` of this section or use ``0.0.0.0`` to listen on all addresses.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#serialproxy_host=0.0.0.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The port number which is used by the ``nova-serialproxy`` service to listen
May  9 23:35:12 cmp02 salt-minion[2824]: +# for incoming requests.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ``nova-serialproxy`` service listens on this port number for incoming
May  9 23:35:12 cmp02 salt-minion[2824]: +# connection requests to instances which expose serial console.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Ensure that this is the same port number which is defined in the option
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ``base_url`` of this section.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#serialproxy_port=6083
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[service_user]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration options for service to service authentication using a service
May  9 23:35:12 cmp02 salt-minion[2824]: +# token. These options allow to send a service token along with the
May  9 23:35:12 cmp02 salt-minion[2824]: +# user's token when contacting external REST APIs.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When True, if sending a user token to an REST API, also send a service token.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Nova often reuses the user token provided to the nova-api to talk to other
May  9 23:35:12 cmp02 salt-minion[2824]: +# REST APIs, such as Cinder and Neutron. It is possible that while the
May  9 23:35:12 cmp02 salt-minion[2824]: +# user token was valid when the request was made to Nova, the token may expire
May  9 23:35:12 cmp02 salt-minion[2824]: +# before it reaches the other service. To avoid any failures, and to
May  9 23:35:12 cmp02 salt-minion[2824]: +# make it clear it is Nova calling the service on the users behalf, we include
May  9 23:35:12 cmp02 salt-minion[2824]: +# a server token along with the user token. Should the user's token have
May  9 23:35:12 cmp02 salt-minion[2824]: +# expired, a valid service token ensures the REST API request will still be
May  9 23:35:12 cmp02 salt-minion[2824]: +# accepted by the keystone middleware.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This feature is currently experimental, and as such is turned off by default
May  9 23:35:12 cmp02 salt-minion[2824]: +# while full testing and performance tuning of this feature is completed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#send_service_user_token=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded Certificate Authority to use when verifying HTTPs connections.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cafile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate cert file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#certfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate key file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#keyfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Verify HTTPS connections. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Timeout value for http requests (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#timeout=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication type to load (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [service_user]/auth_plugin
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Config Section from which to load plugin specific options (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_section=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication URL (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Trust ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#trust_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain ID to use with v3 and v2 parameters. It will be used for both
May  9 23:35:12 cmp02 salt-minion[2824]: +# the user and project domain in v3 and ignored in v2 authentication. (string
May  9 23:35:12 cmp02 salt-minion[2824]: +# value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain name to use with v3 API and v2 parameters. It will be used for
May  9 23:35:12 cmp02 salt-minion[2824]: +# both the user and project domain in v3 and ignored in v2 authentication.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [service_user]/user-name
May  9 23:35:12 cmp02 salt-minion[2824]: +#username=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain id (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's password (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant Name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[spice]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# SPICE console feature allows you to connect to a guest virtual machine.
May  9 23:35:12 cmp02 salt-minion[2824]: +# SPICE is a replacement for fairly limited VNC protocol.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Following requirements must be met in order to use SPICE:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Virtualization driver must be libvirt
May  9 23:35:12 cmp02 salt-minion[2824]: +# * spice.enabled set to True
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vnc.enabled set to False
May  9 23:35:12 cmp02 salt-minion[2824]: +# * update html5proxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * update server_proxyclient_address
May  9 23:35:12 cmp02 salt-minion[2824]: +enabled = false
May  9 23:35:12 cmp02 salt-minion[2824]: +html5proxy_base_url = http://10.16.0.107:6080/spice_auto.html
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable SPICE related features.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * VNC must be explicitly disabled to get access to the SPICE console. Set the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   enabled option to False in the [vnc] section to disable the VNC console.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable the SPICE guest agent support on the instances.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The Spice agent works with the Spice protocol to offer a better guest console
May  9 23:35:12 cmp02 salt-minion[2824]: +# experience. However, the Spice console can still be used without the Spice
May  9 23:35:12 cmp02 salt-minion[2824]: +# Agent. With the Spice agent installed the following features are enabled:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Copy & Paste of text and images between the guest and client machine
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Automatic adjustment of resolution when the client screen changes - e.g.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   if you make the Spice console full screen the guest resolution will adjust
May  9 23:35:12 cmp02 salt-minion[2824]: +# to
May  9 23:35:12 cmp02 salt-minion[2824]: +#   match it rather than letterboxing.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Better mouse integration - The mouse can be captured and released without
May  9 23:35:12 cmp02 salt-minion[2824]: +#   needing to click inside the console or press keys to release it. The
May  9 23:35:12 cmp02 salt-minion[2824]: +#   performance of mouse movement is also improved.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#agent_enabled=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Location of the SPICE HTML5 console proxy.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# End user would use this URL to connect to the `nova-spicehtml5proxy``
May  9 23:35:12 cmp02 salt-minion[2824]: +# service. This service will forward request to the console of an instance.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# In order to use SPICE console, the service ``nova-spicehtml5proxy`` should be
May  9 23:35:12 cmp02 salt-minion[2824]: +# running. This service is typically launched on the controller node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Must be a valid URL of the form:  ``http://host:port/spice_auto.html``
May  9 23:35:12 cmp02 salt-minion[2824]: +#   where host is the node running ``nova-spicehtml5proxy`` and the port is
May  9 23:35:12 cmp02 salt-minion[2824]: +#   typically 6082. Consider not using default value as it is not well defined
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for any real deployment.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option depends on ``html5proxy_host`` and ``html5proxy_port`` options.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The access URL returned by the compute node must have the host
May  9 23:35:12 cmp02 salt-minion[2824]: +#   and port where the ``nova-spicehtml5proxy`` service is listening.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (uri value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#html5proxy_base_url=http://127.0.0.1:6082/spice_auto.html
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The  address where the SPICE server running on the instances should listen.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Typically, the ``nova-spicehtml5proxy`` proxy client runs on the controller
May  9 23:35:12 cmp02 salt-minion[2824]: +# node and connects over the private network to this address on the compute
May  9 23:35:12 cmp02 salt-minion[2824]: +# node(s).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * IP address to listen on.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#server_listen=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The address used by ``nova-spicehtml5proxy`` client to connect to instance
May  9 23:35:12 cmp02 salt-minion[2824]: +# console.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Typically, the ``nova-spicehtml5proxy`` proxy client runs on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# controller node and connects over the private network to this address on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# compute node(s).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid IP address on the compute node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option depends on the ``server_listen`` option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The proxy client must be able to access the address specified in
May  9 23:35:12 cmp02 salt-minion[2824]: +#   ``server_listen`` using the value of this option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#server_proxyclient_address=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# A keyboard layout which is supported by the underlying hypervisor on this
May  9 23:35:12 cmp02 salt-minion[2824]: +# node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This is usually an 'IETF language tag' (default is 'en-us'). If you
May  9 23:35:12 cmp02 salt-minion[2824]: +#   use QEMU as hypervisor, you should find the list of supported keyboard
May  9 23:35:12 cmp02 salt-minion[2824]: +#   layouts at /usr/share/qemu/keymaps.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#keymap=en-us
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# IP address or a hostname on which the ``nova-spicehtml5proxy`` service
May  9 23:35:12 cmp02 salt-minion[2824]: +# listens for incoming requests.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option depends on the ``html5proxy_base_url`` option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The ``nova-spicehtml5proxy`` service must be listening on a host that is
May  9 23:35:12 cmp02 salt-minion[2824]: +#   accessible from the HTML5 client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#html5proxy_host=0.0.0.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Port on which the ``nova-spicehtml5proxy`` service listens for incoming
May  9 23:35:12 cmp02 salt-minion[2824]: +# requests.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option depends on the ``html5proxy_base_url`` option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#   The ``nova-spicehtml5proxy`` service must be listening on a port that is
May  9 23:35:12 cmp02 salt-minion[2824]: +#   accessible from the HTML5 client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#html5proxy_port=6082
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[ssl]
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# CA certificate file to use to verify connecting clients. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ssl_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# Certificate file to use when starting the server securely. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ssl_cert_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#cert_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Private key file to use when starting the server securely. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ssl_key_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#key_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and
May  9 23:35:12 cmp02 salt-minion[2824]: +# SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some
May  9 23:35:12 cmp02 salt-minion[2824]: +# distributions. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#version=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Sets the list of available ciphers. value should be a string in the OpenSSL
May  9 23:35:12 cmp02 salt-minion[2824]: +# cipher list format. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ciphers=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[trusted_computing]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration options for enabling Trusted Platform Module.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The host to use as the attestation server.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cloud computing pools can involve thousands of compute nodes located at
May  9 23:35:12 cmp02 salt-minion[2824]: +# different geographical locations, making it difficult for cloud providers to
May  9 23:35:12 cmp02 salt-minion[2824]: +# identify a node's trustworthiness. When using the Trusted filter, users can
May  9 23:35:12 cmp02 salt-minion[2824]: +# request that their VMs only be placed on nodes that have been verified by the
May  9 23:35:12 cmp02 salt-minion[2824]: +# attestation server specified in this option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing the host name or IP address of the attestation server,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   or an empty string.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_api_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_blob
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_insecure_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_server=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The absolute path to the certificate to use for authentication when connecting
May  9 23:35:12 cmp02 salt-minion[2824]: +# to the attestation server. See the `attestation_server` help text for more
May  9 23:35:12 cmp02 salt-minion[2824]: +# information about host verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing the path to the authentication certificate for the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   attestation server, or an empty string.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_api_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_blob
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_insecure_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_server_ca_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The port to use when connecting to the attestation server. See the
May  9 23:35:12 cmp02 salt-minion[2824]: +# `attestation_server` help text for more information about host verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_api_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_blob
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_insecure_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_port=8443
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The URL on the attestation server to use. See the `attestation_server` help
May  9 23:35:12 cmp02 salt-minion[2824]: +# text for more information about host verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This value must be just that path portion of the full URL, as it will be
May  9 23:35:12 cmp02 salt-minion[2824]: +# joined
May  9 23:35:12 cmp02 salt-minion[2824]: +# to the host specified in the attestation_server option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A valid URL string of the attestation server, or an empty string.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_blob
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_insecure_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_api_url=/OpenAttestationWebServices/V1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Attestation servers require a specific blob that is used to authenticate. The
May  9 23:35:12 cmp02 salt-minion[2824]: +# content and format of the blob are determined by the particular attestation
May  9 23:35:12 cmp02 salt-minion[2824]: +# server being used. There is no default value; you must supply the value as
May  9 23:35:12 cmp02 salt-minion[2824]: +# specified by your attestation service. See the `attestation_server` help text
May  9 23:35:12 cmp02 salt-minion[2824]: +# for more information about host verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string containing the specific blob required by the attestation server, or
May  9 23:35:12 cmp02 salt-minion[2824]: +#   an empty string.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_api_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_insecure_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_auth_blob=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This value controls how long a successful attestation is cached. Once this
May  9 23:35:12 cmp02 salt-minion[2824]: +# period has elapsed, a new attestation request will be made. See the
May  9 23:35:12 cmp02 salt-minion[2824]: +# `attestation_server` help text for more information about host verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A integer value, corresponding to the timeout interval for attestations in
May  9 23:35:12 cmp02 salt-minion[2824]: +#   seconds. Any integer is valid, although setting this to zero or negative
May  9 23:35:12 cmp02 salt-minion[2824]: +#   values can greatly impact performance when using an attestation service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_api_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_blob
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_insecure_ssl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_auth_timeout=60
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When set to True, the SSL certificate verification is skipped for the
May  9 23:35:12 cmp02 salt-minion[2824]: +# attestation service. See the `attestation_server` help text for more
May  9 23:35:12 cmp02 salt-minion[2824]: +# information about host verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is only used by the FilterScheduler and its subclasses; if you use
May  9 23:35:12 cmp02 salt-minion[2824]: +# a different scheduler, this option has no effect. Also note that this setting
May  9 23:35:12 cmp02 salt-minion[2824]: +# only affects scheduling if the 'TrustedFilter' filter is enabled.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_server_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_api_url
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_blob
May  9 23:35:12 cmp02 salt-minion[2824]: +# * attestation_auth_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#attestation_insecure_ssl=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[upgrade_levels]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# upgrade_levels options are used to set version cap for RPC
May  9 23:35:12 cmp02 salt-minion[2824]: +# messages sent between different nova services.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By default all services send messages using the latest version
May  9 23:35:12 cmp02 salt-minion[2824]: +# they know about.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The compute upgrade level is an important part of rolling upgrades
May  9 23:35:12 cmp02 salt-minion[2824]: +# where old and new nova-compute services run side by side.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The other options can largely be ignored, and are only kept to
May  9 23:35:12 cmp02 salt-minion[2824]: +# help with a possible future backport issue.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Compute RPC API version cap.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By default, we always send messages using the most recent version
May  9 23:35:12 cmp02 salt-minion[2824]: +# the client knows about.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Where you have old and new compute services running, you should set
May  9 23:35:12 cmp02 salt-minion[2824]: +# this to the lowest deployed version. This is to guarantee that all
May  9 23:35:12 cmp02 salt-minion[2824]: +# services never send messages that one of the compute nodes can't
May  9 23:35:12 cmp02 salt-minion[2824]: +# understand. Note that we only support upgrading from release N to
May  9 23:35:12 cmp02 salt-minion[2824]: +# release N+1.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Set this option to "auto" if you want to let the compute RPC module
May  9 23:35:12 cmp02 salt-minion[2824]: +# automatically determine what version to use based on the service
May  9 23:35:12 cmp02 salt-minion[2824]: +# versions in the deployment.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * By default send the latest version the client knows about
May  9 23:35:12 cmp02 salt-minion[2824]: +# * 'auto': Automatically determines what version to use based on
May  9 23:35:12 cmp02 salt-minion[2824]: +#   the service versions in the deployment.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing a version number in the format 'N.N';
May  9 23:35:12 cmp02 salt-minion[2824]: +#   for example, possible values might be '1.12' or '2.0'.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * An OpenStack release name, in lower case, such as 'mitaka' or
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'liberty'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#compute=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cells RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cells=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Intercell RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#intercell=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cert RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cert=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Scheduler RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#scheduler=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Conductor RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#conductor=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Console RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#console=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Consoleauth RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#consoleauth=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Network RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#network=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Base API RPC API version cap (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#baseapi=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[vendordata_dynamic_auth]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Options within this group control the authentication of the vendordata
May  9 23:35:12 cmp02 salt-minion[2824]: +# subsystem of the metadata API server (and config drive) with external systems.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded Certificate Authority to use when verifying HTTPs connections.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cafile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate cert file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#certfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# PEM encoded client certificate key file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#keyfile=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Verify HTTPS connections. (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Timeout value for http requests (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#timeout=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication type to load (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [vendordata_dynamic_auth]/auth_plugin
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_type=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Config Section from which to load plugin specific options (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_section=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Authentication URL (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project ID to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Project name to scope to (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain ID containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Domain name containing project (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#project_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Trust ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#trust_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain ID to use with v3 and v2 parameters. It will be used for both
May  9 23:35:12 cmp02 salt-minion[2824]: +# the user and project domain in v3 and ignored in v2 authentication. (string
May  9 23:35:12 cmp02 salt-minion[2824]: +# value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional domain name to use with v3 API and v2 parameters. It will be used for
May  9 23:35:12 cmp02 salt-minion[2824]: +# both the user and project domain in v3 and ignored in v2 authentication.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [vendordata_dynamic_auth]/user-name
May  9 23:35:12 cmp02 salt-minion[2824]: +#username=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain id (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's domain name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#user_domain_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# User's password (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant ID (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_id=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Tenant Name (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#tenant_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[vmware]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Following options must be set in order to launch VMware-based
May  9 23:35:12 cmp02 salt-minion[2824]: +# virtual machines.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * compute_driver: Must use vmwareapi.VMwareVCDriver.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vmware.host_username
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vmware.host_password
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vmware.cluster_name
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the physical ethernet adapter name for VLAN
May  9 23:35:12 cmp02 salt-minion[2824]: +# networking.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Set the vlan_interface configuration option to match the ESX host
May  9 23:35:12 cmp02 salt-minion[2824]: +# interface that handles VLAN-tagged VM traffic.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid string representing VLAN interface name
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#vlan_interface=vmnic0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option should be configured only when using the NSX-MH Neutron
May  9 23:35:12 cmp02 salt-minion[2824]: +# plugin. This is the name of the integration bridge on the ESXi server
May  9 23:35:12 cmp02 salt-minion[2824]: +# or host. This should not be set for any other Neutron plugin. Hence
May  9 23:35:12 cmp02 salt-minion[2824]: +# the default value is not set.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid string representing the name of the integration bridge
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#integration_bridge=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Set this value if affected by an increased network latency causing
May  9 23:35:12 cmp02 salt-minion[2824]: +# repeated characters when typing in a remote console.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_delay_seconds=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Identifies the remote system where the serial port traffic will
May  9 23:35:12 cmp02 salt-minion[2824]: +# be sent.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option adds a virtual serial port which sends console output to
May  9 23:35:12 cmp02 salt-minion[2824]: +# a configurable service URI. At the service URI address there will be
May  9 23:35:12 cmp02 salt-minion[2824]: +# virtual serial port concentrator that will collect console logs.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If this is not set, no serial ports will be added to the created VMs.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid URI
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#serial_port_service_uri=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Identifies a proxy service that provides network access to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# serial_port_service_uri.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid URI
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is ignored if serial_port_service_uri is not specified.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * serial_port_service_uri
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#serial_port_proxy_uri=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Hostname or IP address for connection to VMware vCenter host. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_ip=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Port for connection to VMware vCenter host. (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_port=443
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username for connection to VMware vCenter host. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_username=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Password for connection to VMware vCenter host. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#host_password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specifies the CA bundle file to be used in verifying the vCenter
May  9 23:35:12 cmp02 salt-minion[2824]: +# server certificate.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ca_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If true, the vCenter server certificate is not verified. If false,
May  9 23:35:12 cmp02 salt-minion[2824]: +# then the default CA truststore is used for verification.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ca_file: This option is ignored if "ca_file" is set.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#insecure=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Name of a VMware Cluster ComputeResource. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cluster_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Regular expression pattern to match the name of datastore.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The datastore_regex setting specifies the datastores to use with
May  9 23:35:12 cmp02 salt-minion[2824]: +# Compute. For example, datastore_regex="nas.*" selects all the data
May  9 23:35:12 cmp02 salt-minion[2824]: +# stores that have a name starting with "nas".
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# NOTE: If no regex is given, it just picks the datastore with the
May  9 23:35:12 cmp02 salt-minion[2824]: +# most freespace.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any matching regular expression to a datastore must be given
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#datastore_regex=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Time interval in seconds to poll remote tasks invoked on
May  9 23:35:12 cmp02 salt-minion[2824]: +# VMware VC server.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#task_poll_interval=0.5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of times VMware vCenter server API must be retried on connection
May  9 23:35:12 cmp02 salt-minion[2824]: +# failures, e.g. socket error, etc.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#api_retry_count=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies VNC starting port.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Every VM created by ESX host has an option of enabling VNC client
May  9 23:35:12 cmp02 salt-minion[2824]: +# for remote connection. Above option 'vnc_port' helps you to set
May  9 23:35:12 cmp02 salt-minion[2824]: +# default starting port for the VNC client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid port number within 5900 -(5900 + vnc_port_total)
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Below options should be set to enable VNC client.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vnc.enabled = True
May  9 23:35:12 cmp02 salt-minion[2824]: +# * vnc_port_total
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#vnc_port=5900
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Total number of VNC ports.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#vnc_port_total=10000
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option enables/disables the use of linked clone.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The ESX hypervisor requires a copy of the VMDK file in order to boot
May  9 23:35:12 cmp02 salt-minion[2824]: +# up a virtual machine. The compute driver must download the VMDK via
May  9 23:35:12 cmp02 salt-minion[2824]: +# HTTP from the OpenStack Image service to a datastore that is visible
May  9 23:35:12 cmp02 salt-minion[2824]: +# to the hypervisor and cache it. Subsequent virtual machines that need
May  9 23:35:12 cmp02 salt-minion[2824]: +# the VMDK use the cached version and don't have to copy the file again
May  9 23:35:12 cmp02 salt-minion[2824]: +# from the OpenStack Image service.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set to false, even with a cached VMDK, there is still a copy
May  9 23:35:12 cmp02 salt-minion[2824]: +# operation from the cache location to the hypervisor file directory
May  9 23:35:12 cmp02 salt-minion[2824]: +# in the shared datastore. If set to true, the above copy operation
May  9 23:35:12 cmp02 salt-minion[2824]: +# is avoided as it creates copy of the virtual machine that shares
May  9 23:35:12 cmp02 salt-minion[2824]: +# virtual disks with its parent VM.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_linked_clone=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies VIM Service WSDL Location
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If vSphere API versions 5.1 and later is being used, this section can
May  9 23:35:12 cmp02 salt-minion[2824]: +# be ignored. If version is less than 5.1, WSDL files must be hosted
May  9 23:35:12 cmp02 salt-minion[2824]: +# locally and their location must be specified in the above section.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Optional over-ride to default location for bug work-arounds.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * http://<server>/vimService.wsdl
May  9 23:35:12 cmp02 salt-minion[2824]: +# * file:///opt/stack/vmware/SDK/wsdl/vim25/vimService.wsdl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason: Only vCenter versions earlier than 5.1 require this option and the
May  9 23:35:12 cmp02 salt-minion[2824]: +# current minimum version is 5.1.
May  9 23:35:12 cmp02 salt-minion[2824]: +#wsdl_location=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option enables or disables storage policy based placement
May  9 23:35:12 cmp02 salt-minion[2824]: +# of instances.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * pbm_default_policy
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#pbm_enabled=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the PBM service WSDL file location URL.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Setting this will disable storage policy based placement
May  9 23:35:12 cmp02 salt-minion[2824]: +# of instances.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid file path
May  9 23:35:12 cmp02 salt-minion[2824]: +#   e.g file:///opt/SDK/spbm/wsdl/pbmService.wsdl
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#pbm_wsdl_location=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the default policy to be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If pbm_enabled is set and there is no defined storage policy for the
May  9 23:35:12 cmp02 salt-minion[2824]: +# specific request, then this policy will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any valid storage policy such as VSAN default storage policy
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * pbm_enabled
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#pbm_default_policy=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the limit on the maximum number of objects to
May  9 23:35:12 cmp02 salt-minion[2824]: +# return in a single result.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# A positive value will cause the operation to suspend the retrieval
May  9 23:35:12 cmp02 salt-minion[2824]: +# when the count of objects reaches the specified limit. The server may
May  9 23:35:12 cmp02 salt-minion[2824]: +# still limit the count to something less than the configured value.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Any remaining objects may be retrieved with additional requests.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#maximum_objects=100
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option adds a prefix to the folder where cached images are stored
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is not the full path - just a folder prefix. This should only be
May  9 23:35:12 cmp02 salt-minion[2824]: +# used when a datastore cache is shared between compute nodes.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: This should only be used when the compute nodes are running on same
May  9 23:35:12 cmp02 salt-minion[2824]: +# host or they have a shared file system.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string representing the cache prefix to the folder
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#cache_prefix=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[vnc]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Virtual Network Computer (VNC) can be used to provide remote desktop
May  9 23:35:12 cmp02 salt-minion[2824]: +# console access to instances for tenants and/or administrators.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +enabled = true
May  9 23:35:12 cmp02 salt-minion[2824]: +novncproxy_base_url=http://10.16.0.107:6080/vnc_auto.html
May  9 23:35:12 cmp02 salt-minion[2824]: +novncproxy_port=6080
May  9 23:35:12 cmp02 salt-minion[2824]: +vncserver_listen=172.16.10.53
May  9 23:35:12 cmp02 salt-minion[2824]: +vncserver_proxyclient_address=172.16.10.53
May  9 23:35:12 cmp02 salt-minion[2824]: +keymap = en-us
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable VNC related features.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Guests will get created with graphical devices to support this. Clients
May  9 23:35:12 cmp02 salt-minion[2824]: +# (for example Horizon) can then establish a VNC connection to the guest.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vnc_enabled
May  9 23:35:12 cmp02 salt-minion[2824]: +#enabled=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Keymap for VNC.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The keyboard mapping (keymap) determines which keyboard layout a VNC
May  9 23:35:12 cmp02 salt-minion[2824]: +# session should use by default.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A keyboard layout which is supported by the underlying hypervisor on
May  9 23:35:12 cmp02 salt-minion[2824]: +#   this node. This is usually an 'IETF language tag' (for example
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'en-us').  If you use QEMU as hypervisor, you should find the  list
May  9 23:35:12 cmp02 salt-minion[2824]: +#   of supported keyboard layouts at ``/usr/share/qemu/keymaps``.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vnc_keymap
May  9 23:35:12 cmp02 salt-minion[2824]: +#keymap=en-us
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The IP address or hostname on which an instance should listen to for
May  9 23:35:12 cmp02 salt-minion[2824]: +# incoming VNC connection requests on this node.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vncserver_listen
May  9 23:35:12 cmp02 salt-minion[2824]: +#vncserver_listen=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Private, internal IP address or hostname of VNC console proxy.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the private address to which proxy clients, such as
May  9 23:35:12 cmp02 salt-minion[2824]: +# ``nova-xvpvncproxy``, should connect to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/vncserver_proxyclient_address
May  9 23:35:12 cmp02 salt-minion[2824]: +#vncserver_proxyclient_address=127.0.0.1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Public address of noVNC VNC console proxy.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients. noVNC provides
May  9 23:35:12 cmp02 salt-minion[2824]: +# VNC support through a websocket-based client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the public base URL to which client systems will
May  9 23:35:12 cmp02 salt-minion[2824]: +# connect. noVNC clients can use this address to connect to the noVNC
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance and, by extension, the VNC sessions.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * novncproxy_host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * novncproxy_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (uri value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/novncproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +#novncproxy_base_url=http://127.0.0.1:6080/vnc_auto.html
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# IP address or hostname that the XVP VNC console proxy should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients. Xen provides
May  9 23:35:12 cmp02 salt-minion[2824]: +# the Xenserver VNC Proxy, or XVP, as an alternative to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# websocket-based noVNC proxy used by Libvirt. In contrast to noVNC,
May  9 23:35:12 cmp02 salt-minion[2824]: +# XVP clients are Java-based.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the private address to which the XVP VNC console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +# service should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * xvpvncproxy_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * xvpvncproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/xvpvncproxy_host
May  9 23:35:12 cmp02 salt-minion[2824]: +#xvpvncproxy_host=0.0.0.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Port that the XVP VNC console proxy should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients. Xen provides
May  9 23:35:12 cmp02 salt-minion[2824]: +# the Xenserver VNC Proxy, or XVP, as an alternative to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# websocket-based noVNC proxy used by Libvirt. In contrast to noVNC,
May  9 23:35:12 cmp02 salt-minion[2824]: +# XVP clients are Java-based.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the private port to which the XVP VNC console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +# service should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * xvpvncproxy_host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * xvpvncproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/xvpvncproxy_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#xvpvncproxy_port=6081
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Public URL address of XVP VNC console proxy.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients. Xen provides
May  9 23:35:12 cmp02 salt-minion[2824]: +# the Xenserver VNC Proxy, or XVP, as an alternative to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# websocket-based noVNC proxy used by Libvirt. In contrast to noVNC,
May  9 23:35:12 cmp02 salt-minion[2824]: +# XVP clients are Java-based.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the public base URL to which client systems will
May  9 23:35:12 cmp02 salt-minion[2824]: +# connect. XVP clients can use this address to connect to the XVP
May  9 23:35:12 cmp02 salt-minion[2824]: +# instance and, by extension, the VNC sessions.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * xvpvncproxy_host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * xvpvncproxy_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (uri value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/xvpvncproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +#xvpvncproxy_base_url=http://127.0.0.1:6081/console
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# IP address that the noVNC console proxy should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients. noVNC provides
May  9 23:35:12 cmp02 salt-minion[2824]: +# VNC support through a websocket-based client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the private address to which the noVNC console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +# service should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * novncproxy_port
May  9 23:35:12 cmp02 salt-minion[2824]: +# * novncproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/novncproxy_host
May  9 23:35:12 cmp02 salt-minion[2824]: +#novncproxy_host=0.0.0.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Port that the noVNC console proxy should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The VNC proxy is an OpenStack component that enables compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +# users to access their instances through VNC clients. noVNC provides
May  9 23:35:12 cmp02 salt-minion[2824]: +# VNC support through a websocket-based client.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the private port to which the noVNC console proxy
May  9 23:35:12 cmp02 salt-minion[2824]: +# service should bind to.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * novncproxy_host
May  9 23:35:12 cmp02 salt-minion[2824]: +# * novncproxy_base_url
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/novncproxy_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#novncproxy_port=6080
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[workarounds]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# A collection of workarounds used to mitigate bugs or issues found in system
May  9 23:35:12 cmp02 salt-minion[2824]: +# tools (e.g. Libvirt or QEMU) or Nova itself under certain conditions. These
May  9 23:35:12 cmp02 salt-minion[2824]: +# should only be enabled in exceptional circumstances. All options are linked
May  9 23:35:12 cmp02 salt-minion[2824]: +# against bug IDs, where more information on the issue can be found.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use sudo instead of rootwrap.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allow fallback to sudo for performance reasons.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# For more information, refer to the bug report:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   https://bugs.launchpad.net/nova/+bug/1415106
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * True: Use sudo instead of rootwrap
May  9 23:35:12 cmp02 salt-minion[2824]: +# * False: Use rootwrap as usual
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Interdependencies to other options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any options that affect 'rootwrap' will be ignored.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#disable_rootwrap=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Disable live snapshots when using the libvirt driver.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Live snapshots allow the snapshot of the disk to happen without an
May  9 23:35:12 cmp02 salt-minion[2824]: +# interruption to the guest, using coordination with a guest agent to
May  9 23:35:12 cmp02 salt-minion[2824]: +# quiesce the filesystem.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When using libvirt 1.2.2 live snapshots fail intermittently under load
May  9 23:35:12 cmp02 salt-minion[2824]: +# (likely related to concurrent libvirt/qemu operations). This config
May  9 23:35:12 cmp02 salt-minion[2824]: +# option provides a mechanism to disable live snapshot, in favor of cold
May  9 23:35:12 cmp02 salt-minion[2824]: +# snapshot, while this is resolved. Cold snapshot causes an instance
May  9 23:35:12 cmp02 salt-minion[2824]: +# outage while the guest is going through the snapshotting process.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# For more information, refer to the bug report:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   https://bugs.launchpad.net/nova/+bug/1334398
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * True: Live snapshot is disabled when using libvirt
May  9 23:35:12 cmp02 salt-minion[2824]: +# * False: Live snapshots are always used when snapshotting (as long as
May  9 23:35:12 cmp02 salt-minion[2824]: +#   there is a new enough libvirt and the backend storage supports it)
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#disable_libvirt_livesnapshot=true
May  9 23:35:12 cmp02 salt-minion[2824]: +disable_libvirt_livesnapshot=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enable handling of events emitted from compute drivers.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Many compute drivers emit lifecycle events, which are events that occur when,
May  9 23:35:12 cmp02 salt-minion[2824]: +# for example, an instance is starting or stopping. If the instance is going
May  9 23:35:12 cmp02 salt-minion[2824]: +# through task state changes due to an API operation, like resize, the events
May  9 23:35:12 cmp02 salt-minion[2824]: +# are ignored.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is an advanced feature which allows the hypervisor to signal to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# compute service that an unexpected state change has occurred in an instance
May  9 23:35:12 cmp02 salt-minion[2824]: +# and that the instance can be shutdown automatically. Unfortunately, this can
May  9 23:35:12 cmp02 salt-minion[2824]: +# race in some conditions, for example in reboot operations or when the compute
May  9 23:35:12 cmp02 salt-minion[2824]: +# service or when host is rebooted (planned or due to an outage). If such races
May  9 23:35:12 cmp02 salt-minion[2824]: +# are common, then it is advisable to disable this feature.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Care should be taken when this feature is disabled and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'sync_power_state_interval' is set to a negative value. In this case, any
May  9 23:35:12 cmp02 salt-minion[2824]: +# instances that get out of sync between the hypervisor and the Nova database
May  9 23:35:12 cmp02 salt-minion[2824]: +# will have to be synchronized manually.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# For more information, refer to the bug report:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#   https://bugs.launchpad.net/bugs/1444630
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Interdependencies to other options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If ``sync_power_state_interval`` is negative and this feature is disabled,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   then instances that get out of sync between the hypervisor and the Nova
May  9 23:35:12 cmp02 salt-minion[2824]: +#   database will have to be synchronized manually.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#handle_virt_lifecycle_events=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[wsgi]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Options under this group are used to configure WSGI (Web Server Gateway
May  9 23:35:12 cmp02 salt-minion[2824]: +# Interface). WSGI is used to serve API requests.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option represents a file name for the paste.deploy config for nova-api.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing file name for the paste.deploy config.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/api_paste_config
May  9 23:35:12 cmp02 salt-minion[2824]: +api_paste_config=/etc/nova/api-paste.ini
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# It represents a python format string that is used as the template to generate
May  9 23:35:12 cmp02 salt-minion[2824]: +# log lines. The following values can be formatted into it: client_ip,
May  9 23:35:12 cmp02 salt-minion[2824]: +# date_time, request_line, status_code, body_length, wall_seconds.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is used for building custom request loglines.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * '%(client_ip)s "%(request_line)s" status: %(status_code)s'
May  9 23:35:12 cmp02 salt-minion[2824]: +#   'len: %(body_length)s time: %(wall_seconds).7f' (default)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any formatted string formed by specific values.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/wsgi_log_format
May  9 23:35:12 cmp02 salt-minion[2824]: +#wsgi_log_format=%(client_ip)s "%(request_line)s" status: %(status_code)s len: %(body_length)s time: %(wall_seconds).7f
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the HTTP header used to determine the protocol scheme
May  9 23:35:12 cmp02 salt-minion[2824]: +# for the original request, even if it was removed by a SSL terminating proxy.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * None (default) - the request scheme is not influenced by any HTTP headers.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Valid HTTP header, like HTTP_X_FORWARDED_PROTO
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/secure_proxy_ssl_header
May  9 23:35:12 cmp02 salt-minion[2824]: +#secure_proxy_ssl_header=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows setting path to the CA certificate file that should be used
May  9 23:35:12 cmp02 salt-minion[2824]: +# to verify connecting clients.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * String representing path to the CA certificate file.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * enabled_ssl_apis
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ssl_ca_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#ssl_ca_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows setting path to the SSL certificate of API server.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * String representing path to the SSL certificate.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * enabled_ssl_apis
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ssl_cert_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#ssl_cert_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the path to the file where SSL private key of API
May  9 23:35:12 cmp02 salt-minion[2824]: +# server is stored when SSL is in effect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * String representing path to the SSL private key.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * enabled_ssl_apis
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/ssl_key_file
May  9 23:35:12 cmp02 salt-minion[2824]: +#ssl_key_file=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets the value of TCP_KEEPIDLE in seconds for each server socket.
May  9 23:35:12 cmp02 salt-minion[2824]: +# It specifies the duration of time to keep connection active. TCP generates a
May  9 23:35:12 cmp02 salt-minion[2824]: +# KEEPALIVE transmission for an application that requests to keep connection
May  9 23:35:12 cmp02 salt-minion[2824]: +# active. Not supported on OS X.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * keep_alive
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/tcp_keepidle
May  9 23:35:12 cmp02 salt-minion[2824]: +#tcp_keepidle=600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the size of the pool of greenthreads used by wsgi.
May  9 23:35:12 cmp02 salt-minion[2824]: +# It is possible to limit the number of concurrent connections using this
May  9 23:35:12 cmp02 salt-minion[2824]: +# option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/wsgi_default_pool_size
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_pool_size=1000
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the maximum line size of message headers to be accepted.
May  9 23:35:12 cmp02 salt-minion[2824]: +# max_header_line may need to be increased when using large tokens (typically
May  9 23:35:12 cmp02 salt-minion[2824]: +# those generated by the Keystone v3 API with big service catalogs).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Since TCP is a stream based protocol, in order to reuse a connection, the HTTP
May  9 23:35:12 cmp02 salt-minion[2824]: +# has to have a way to indicate the end of the previous response and beginning
May  9 23:35:12 cmp02 salt-minion[2824]: +# of the next. Hence, in a keep_alive case, all messages must have a
May  9 23:35:12 cmp02 salt-minion[2824]: +# self-defined message length.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/max_header_line
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_header_line=16384
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows using the same TCP connection to send and receive multiple
May  9 23:35:12 cmp02 salt-minion[2824]: +# HTTP requests/responses, as opposed to opening a new one for every single
May  9 23:35:12 cmp02 salt-minion[2824]: +# request/response pair. HTTP keep-alive indicates HTTP connection reuse.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * True : reuse HTTP connection.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * False : closes the client socket connection explicitly.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * tcp_keepidle
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/wsgi_keep_alive
May  9 23:35:12 cmp02 salt-minion[2824]: +#keep_alive=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option specifies the timeout for client connections' socket operations.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If an incoming connection is idle for this number of seconds it will be
May  9 23:35:12 cmp02 salt-minion[2824]: +# closed. It indicates timeout on individual read/writes on the socket
May  9 23:35:12 cmp02 salt-minion[2824]: +# connection. To wait forever set to 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/client_socket_timeout
May  9 23:35:12 cmp02 salt-minion[2824]: +#client_socket_timeout=900
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[xenserver]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# XenServer options are used when the compute_driver is set to use
May  9 23:35:12 cmp02 salt-minion[2824]: +# XenServer (compute_driver=xenapi.XenAPIDriver).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Must specify connection_url, connection_password and ovs_integration_bridge to
May  9 23:35:12 cmp02 salt-minion[2824]: +# use compute_driver=xenapi.XenAPIDriver.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds to wait for agent's reply to a request.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Nova configures/performs certain administrative actions on a server with the
May  9 23:35:12 cmp02 salt-minion[2824]: +# help of an agent that's installed on the server. The communication between
May  9 23:35:12 cmp02 salt-minion[2824]: +# Nova and the agent is achieved via sharing messages, called records, over
May  9 23:35:12 cmp02 salt-minion[2824]: +# xenstore, a shared storage across all the domains on a Xenserver host.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Operations performed by the agent on behalf of nova are: 'version','
May  9 23:35:12 cmp02 salt-minion[2824]: +# key_init',
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'password','resetnetwork','inject_file', and 'agentupdate'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# To perform one of the above operations, the xapi 'agent' plugin writes the
May  9 23:35:12 cmp02 salt-minion[2824]: +# command and its associated parameters to a certain location known to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# domain
May  9 23:35:12 cmp02 salt-minion[2824]: +# and awaits response. On being notified of the message, the agent performs
May  9 23:35:12 cmp02 salt-minion[2824]: +# appropriate actions on the server and writes the result back to xenstore. This
May  9 23:35:12 cmp02 salt-minion[2824]: +# result is then read by the xapi 'agent' plugin to determine the
May  9 23:35:12 cmp02 salt-minion[2824]: +# success/failure
May  9 23:35:12 cmp02 salt-minion[2824]: +# of the operation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This config option determines how long the xapi 'agent' plugin shall wait to
May  9 23:35:12 cmp02 salt-minion[2824]: +# read the response off of xenstore for a given request/command. If the agent on
May  9 23:35:12 cmp02 salt-minion[2824]: +# the instance fails to write the result in this time period, the operation is
May  9 23:35:12 cmp02 salt-minion[2824]: +# considered to have timed out.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``agent_version_timeout``
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``agent_resetnetwork_timeout``
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#agent_timeout=30
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds to wait for agent't reply to version request.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This indicates the amount of time xapi 'agent' plugin waits for the agent to
May  9 23:35:12 cmp02 salt-minion[2824]: +# respond to the 'version' request specifically. The generic timeout for agent
May  9 23:35:12 cmp02 salt-minion[2824]: +# communication ``agent_timeout`` is ignored in this case.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# During the build process the 'version' request is used to determine if the
May  9 23:35:12 cmp02 salt-minion[2824]: +# agent is available/operational to perform other requests such as
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'resetnetwork', 'password', 'key_init' and 'inject_file'. If the 'version'
May  9 23:35:12 cmp02 salt-minion[2824]: +# call
May  9 23:35:12 cmp02 salt-minion[2824]: +# fails, the other configuration is skipped. So, this configuration option can
May  9 23:35:12 cmp02 salt-minion[2824]: +# also be interpreted as time in which agent is expected to be fully
May  9 23:35:12 cmp02 salt-minion[2824]: +# operational.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#agent_version_timeout=300
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds to wait for agent's reply to resetnetwork
May  9 23:35:12 cmp02 salt-minion[2824]: +# request.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This indicates the amount of time xapi 'agent' plugin waits for the agent to
May  9 23:35:12 cmp02 salt-minion[2824]: +# respond to the 'resetnetwork' request specifically. The generic timeout for
May  9 23:35:12 cmp02 salt-minion[2824]: +# agent communication ``agent_timeout`` is ignored in this case.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#agent_resetnetwork_timeout=60
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Path to locate guest agent on the server.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specifies the path in which the XenAPI guest agent should be located. If the
May  9 23:35:12 cmp02 salt-minion[2824]: +# agent is present, network configuration is not injected into the image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# For this option to have an effect:
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``flat_injected`` should be set to ``True``
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``compute_driver`` should be set to ``xenapi.XenAPIDriver``
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#agent_path=usr/sbin/xe-update-networking
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Disables the use of XenAPI agent.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This configuration option suggests whether the use of agent should be enabled
May  9 23:35:12 cmp02 salt-minion[2824]: +# or not regardless of what image properties are present. Image properties have
May  9 23:35:12 cmp02 salt-minion[2824]: +# an effect only when this is set to ``True``. Read description of config option
May  9 23:35:12 cmp02 salt-minion[2824]: +# ``use_agent_default`` for more information.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``use_agent_default``
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#disable_agent=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Whether or not to use the agent by default when its usage is enabled but not
May  9 23:35:12 cmp02 salt-minion[2824]: +# indicated by the image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The use of XenAPI agent can be disabled altogether using the configuration
May  9 23:35:12 cmp02 salt-minion[2824]: +# option ``disable_agent``. However, if it is not disabled, the use of an agent
May  9 23:35:12 cmp02 salt-minion[2824]: +# can still be controlled by the image in use through one of its properties,
May  9 23:35:12 cmp02 salt-minion[2824]: +# ``xenapi_use_agent``. If this property is either not present or specified
May  9 23:35:12 cmp02 salt-minion[2824]: +# incorrectly on the image, the use of agent is determined by this configuration
May  9 23:35:12 cmp02 salt-minion[2824]: +# option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note that if this configuration is set to ``True`` when the agent is not
May  9 23:35:12 cmp02 salt-minion[2824]: +# present, the boot times will increase significantly.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``disable_agent``
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_agent_default=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Timeout in seconds for XenAPI login. (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#login_timeout=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum number of concurrent XenAPI connections.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# In nova, multiple XenAPI requests can happen at a time.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuring this option will parallelize access to the XenAPI
May  9 23:35:12 cmp02 salt-minion[2824]: +# session, which allows you to make concurrent XenAPI connections.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_concurrent=5
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Base URL for torrent files; must contain a slash character (see RFC 1808,
May  9 23:35:12 cmp02 salt-minion[2824]: +# step 6).
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_base_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: Probability that peer will become a seeder (1.0 = 100%) (floating
May  9 23:35:12 cmp02 salt-minion[2824]: +# point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_seed_chance=1.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds after downloading an image via BitTorrent that it should
May  9 23:35:12 cmp02 salt-minion[2824]: +# be seeded for other peers.'
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_seed_duration=3600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cached torrent files not accessed within this number of seconds can be reaped.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_max_last_accessed=86400
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: Beginning of port range to listen on (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_listen_port_start=6881
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED: End of port range to listen on (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_listen_port_end=6891
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds a download can remain at the same progress percentage w/o
May  9 23:35:12 cmp02 salt-minion[2824]: +# being considered a stall.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_download_stall_cutoff=600
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum number of seeder processes to run concurrently within a given dom0
May  9 23:35:12 cmp02 salt-minion[2824]: +# (-1 = no limit).
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: -1
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The torrent feature has not been tested nor maintained, and as such is being
May  9 23:35:12 cmp02 salt-minion[2824]: +# removed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_max_seeder_processes_per_host=1
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Cache glance images locally.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The value for this option must be chosen from the choices listed
May  9 23:35:12 cmp02 salt-minion[2824]: +# here. Configuring a value other than these will default to 'all'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: There is nothing that deletes these images.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `all`: will cache all images.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `some`: will only cache images that have the
May  9 23:35:12 cmp02 salt-minion[2824]: +#   image_property `cache_in_nova=True`.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `none`: turns off caching entirely.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: all, some, none
May  9 23:35:12 cmp02 salt-minion[2824]: +#cache_images=all
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Compression level for images.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By setting this option we can configure the gzip compression level.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option sets GZIP environment variable before spawning tar -cz
May  9 23:35:12 cmp02 salt-minion[2824]: +# to force the compression level. It defaults to none, which means the
May  9 23:35:12 cmp02 salt-minion[2824]: +# GZIP environment variable is not set and the default (usually -6)
May  9 23:35:12 cmp02 salt-minion[2824]: +# is used.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Range is 1-9, e.g., 9 for gzip -9, 9 being most
May  9 23:35:12 cmp02 salt-minion[2824]: +#   compressed but most CPU intensive on dom0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any values out of this range will default to None.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 9
May  9 23:35:12 cmp02 salt-minion[2824]: +#image_compression_level=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Default OS type used when uploading an image to glance (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#default_os_type=linux
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Time in secs to wait for a block device to be created (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 1
May  9 23:35:12 cmp02 salt-minion[2824]: +#block_device_creation_timeout=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum size in bytes of kernel or ramdisk images.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specifying the maximum size of kernel or ramdisk will avoid copying
May  9 23:35:12 cmp02 salt-minion[2824]: +# large files to dom0 and fill up /boot/guest.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_kernel_ramdisk_size=16777216
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Filter for finding the SR to be used to install guest instances on.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * To use the Local Storage in default XenServer/XCP installations
May  9 23:35:12 cmp02 salt-minion[2824]: +#   set this flag to other-config:i18n-key=local-storage.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * To select an SR with a different matching criteria, you could
May  9 23:35:12 cmp02 salt-minion[2824]: +#   set it to other-config:my_favorite_sr=true.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * To fall back on the Default SR, as displayed by XenCenter,
May  9 23:35:12 cmp02 salt-minion[2824]: +#   set this flag to: default-sr:true.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#sr_matching_filter=default-sr:true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Whether to use sparse_copy for copying data on a resize down.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (False will use standard dd). This speeds up resizes down
May  9 23:35:12 cmp02 salt-minion[2824]: +# considerably since large runs of zeros won't have to be rsynced.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#sparse_copy=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum number of retries to unplug VBD.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set to 0, should try once, no retries.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#num_vbd_unplug_retries=10
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Whether or not to download images via Bit Torrent.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The value for this option must be chosen from the choices listed
May  9 23:35:12 cmp02 salt-minion[2824]: +# here. Configuring a value other than these will default to 'none'.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `all`: will download all images.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `some`: will only download images that have the image_property
May  9 23:35:12 cmp02 salt-minion[2824]: +#           `bittorrent=true`.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `none`: will turnoff downloading images via Bit Torrent.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Allowed values: all, some, none
May  9 23:35:12 cmp02 salt-minion[2824]: +#torrent_images=none
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Name of network to use for booting iPXE ISOs.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An iPXE ISO is a specially crafted ISO which supports iPXE booting.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This feature gives a means to roll your own image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By default this option is not set. Enable this option to
May  9 23:35:12 cmp02 salt-minion[2824]: +# boot an iPXE ISO.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related Options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `ipxe_boot_menu_url`
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `ipxe_mkisofs_cmd`
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ipxe_network_name=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# URL to the iPXE boot menu.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An iPXE ISO is a specially crafted ISO which supports iPXE booting.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This feature gives a means to roll your own image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# By default this option is not set. Enable this option to
May  9 23:35:12 cmp02 salt-minion[2824]: +# boot an iPXE ISO.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related Options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `ipxe_network_name`
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `ipxe_mkisofs_cmd`
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ipxe_boot_menu_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Name and optionally path of the tool used for ISO image creation.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# An iPXE ISO is a specially crafted ISO which supports iPXE booting.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This feature gives a means to roll your own image.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: By default `mkisofs` is not present in the Dom0, so the
May  9 23:35:12 cmp02 salt-minion[2824]: +# package can either be manually added to Dom0 or include the
May  9 23:35:12 cmp02 salt-minion[2824]: +# `mkisofs` binary in the image itself.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related Options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `ipxe_network_name`
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `ipxe_boot_menu_url`
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ipxe_mkisofs_cmd=mkisofs
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# URL for connection to XenServer/Xen Cloud Platform. A special value
May  9 23:35:12 cmp02 salt-minion[2824]: +# of unix://local can be used to connect to the local unix socket.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string that represents a URL. The connection_url is
May  9 23:35:12 cmp02 salt-minion[2824]: +#   generally the management network IP address of the XenServer.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * This option must be set if you chose the XenServer driver.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_url=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Username for connection to XenServer/Xen Cloud Platform (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_username=root
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Password for connection to XenServer/Xen Cloud Platform (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#connection_password=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The interval used for polling of coalescing vhds.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This is the interval after which the task of coalesce VHD is
May  9 23:35:12 cmp02 salt-minion[2824]: +# performed, until it reaches the max attempts that is set by
May  9 23:35:12 cmp02 salt-minion[2824]: +# vhd_coalesce_max_attempts.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `vhd_coalesce_max_attempts`
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (floating point value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#vhd_coalesce_poll_interval=5.0
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Ensure compute service is running on host XenAPI connects to.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option must be set to false if the 'independent_compute'
May  9 23:35:12 cmp02 salt-minion[2824]: +# option is set to true.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Setting this option to true will make sure that compute service
May  9 23:35:12 cmp02 salt-minion[2824]: +#   is running on the same host that is specified by connection_url.
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Setting this option to false, doesn't perform the check.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `independent_compute`
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#check_host=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Max number of times to poll for VHD to coalesce.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option determines the maximum number of attempts that can be
May  9 23:35:12 cmp02 salt-minion[2824]: +# made for coalescing the VHD before giving up.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related opitons:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * `vhd_coalesce_poll_interval`
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#vhd_coalesce_max_attempts=20
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Base path to the storage repository on the XenServer host. (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#sr_base_path=/var/run/sr-mount
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The iSCSI Target Host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option represents the hostname or ip of the iSCSI Target.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If the target host is not present in the connection information from
May  9 23:35:12 cmp02 salt-minion[2824]: +# the volume provider then the value from this option is taken.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string that represents hostname/ip of Target.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#target_host=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The iSCSI Target Port.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option represents the port of the iSCSI Target. If the
May  9 23:35:12 cmp02 salt-minion[2824]: +# target port is not present in the connection information from the
May  9 23:35:12 cmp02 salt-minion[2824]: +# volume provider then the value from this option is taken.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +#target_port=3260
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# Used to enable the remapping of VBD dev.
May  9 23:35:12 cmp02 salt-minion[2824]: +# (Works around an issue in Ubuntu Maverick)
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option provided a workaround for issues in Ubuntu Maverick, which
May  9 23:35:12 cmp02 salt-minion[2824]: +# was released in April 2010 and was dropped from support in April 2012.
May  9 23:35:12 cmp02 salt-minion[2824]: +# There's no reason to continue supporting this option.
May  9 23:35:12 cmp02 salt-minion[2824]: +#remap_vbd_dev=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Specify prefix to remap VBD dev to (ex. /dev/xvdb -> /dev/sdb).
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * If `remap_vbd_dev` is set to False this option has no impact.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#remap_vbd_dev_prefix=sd
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Used to prevent attempts to attach VBDs locally, so Nova can
May  9 23:35:12 cmp02 salt-minion[2824]: +# be run in a VM on a different host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``CONF.flat_injected`` (Must be False)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``CONF.xenserver.check_host`` (Must be False)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``CONF.default_ephemeral_format`` (Must be unset or 'ext3')
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Joining host aggregates (will error if attempted)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Swap disks for Windows VMs (will error if attempted)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Nova-based auto_configure_disk (will error if attempted)
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#independent_compute=false
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Wait time for instances to go to running state.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Provide an integer value representing time in seconds to set the
May  9 23:35:12 cmp02 salt-minion[2824]: +# wait time for an instance to go to running state.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When a request to create an instance is received by nova-api and
May  9 23:35:12 cmp02 salt-minion[2824]: +# communicated to nova-compute, the creation of the instance occurs
May  9 23:35:12 cmp02 salt-minion[2824]: +# through interaction with Xen via XenAPI in the compute node. Once
May  9 23:35:12 cmp02 salt-minion[2824]: +# the node on which the instance(s) are to be launched is decided by
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova-schedule and the launch is triggered, a certain amount of wait
May  9 23:35:12 cmp02 salt-minion[2824]: +# time is involved until the instance(s) can become available and
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'running'. This wait time is defined by running_timeout. If the
May  9 23:35:12 cmp02 salt-minion[2824]: +# instances do not go to running state within this specified wait
May  9 23:35:12 cmp02 salt-minion[2824]: +# time, the launch expires and the instance(s) are set to 'error'
May  9 23:35:12 cmp02 salt-minion[2824]: +# state.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#running_timeout=60
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# DEPRECATED:
May  9 23:35:12 cmp02 salt-minion[2824]: +# The XenAPI VIF driver using XenServer Network APIs.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Provide a string value representing the VIF XenAPI vif driver to use for
May  9 23:35:12 cmp02 salt-minion[2824]: +# plugging virtual network interfaces.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Xen configuration uses bridging within the backend domain to allow
May  9 23:35:12 cmp02 salt-minion[2824]: +# all VMs to appear on the network as individual hosts. Bridge
May  9 23:35:12 cmp02 salt-minion[2824]: +# interfaces are used to create a XenServer VLAN network in which
May  9 23:35:12 cmp02 salt-minion[2824]: +# the VIFs for the VM instances are plugged. If no VIF bridge driver
May  9 23:35:12 cmp02 salt-minion[2824]: +# is plugged, the bridge is not made available. This configuration
May  9 23:35:12 cmp02 salt-minion[2824]: +# option takes in a value for the VIF driver.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * nova.virt.xenapi.vif.XenAPIOpenVswitchDriver (default)
May  9 23:35:12 cmp02 salt-minion[2824]: +# * nova.virt.xenapi.vif.XenAPIBridgeDriver (deprecated)
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Related options:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``vlan_interface``
May  9 23:35:12 cmp02 salt-minion[2824]: +# * ``ovs_integration_bridge``
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option is deprecated for removal since 15.0.0.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Its value may be silently ignored in the future.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Reason:
May  9 23:35:12 cmp02 salt-minion[2824]: +# There are only two in-tree vif drivers for XenServer. XenAPIBridgeDriver is
May  9 23:35:12 cmp02 salt-minion[2824]: +# for
May  9 23:35:12 cmp02 salt-minion[2824]: +# nova-network which is deprecated and XenAPIOpenVswitchDriver is for Neutron
May  9 23:35:12 cmp02 salt-minion[2824]: +# which is the default configuration for Nova since the 15.0.0 Ocata release. In
May  9 23:35:12 cmp02 salt-minion[2824]: +# the future the "use_neutron" configuration option will be used to determine
May  9 23:35:12 cmp02 salt-minion[2824]: +# which vif driver to use.
May  9 23:35:12 cmp02 salt-minion[2824]: +#vif_driver=nova.virt.xenapi.vif.XenAPIOpenVswitchDriver
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Dom0 plugin driver used to handle image uploads.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Provide a string value representing a plugin driver required to
May  9 23:35:12 cmp02 salt-minion[2824]: +# handle the image uploading to GlanceStore.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Images, and snapshots from XenServer need to be uploaded to the data
May  9 23:35:12 cmp02 salt-minion[2824]: +# store for use. image_upload_handler takes in a value for the Dom0
May  9 23:35:12 cmp02 salt-minion[2824]: +# plugin driver. This driver is then called to uplaod images to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# GlanceStore.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#image_upload_handler=nova.virt.xenapi.image.glance.GlanceStore
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Number of seconds to wait for SR to settle if the VDI
May  9 23:35:12 cmp02 salt-minion[2824]: +# does not exist when first introduced.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Some SRs, particularly iSCSI connections are slow to see the VDIs
May  9 23:35:12 cmp02 salt-minion[2824]: +# right after they got introduced. Setting this option to a
May  9 23:35:12 cmp02 salt-minion[2824]: +# time interval will make the SR to wait for that time period
May  9 23:35:12 cmp02 salt-minion[2824]: +# before raising VDI not found exception.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (integer value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +#introduce_vdi_retry_wait=20
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# The name of the integration Bridge that is used with xenapi
May  9 23:35:12 cmp02 salt-minion[2824]: +# when connecting with Open vSwitch.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Note: The value of this config option is dependent on the
May  9 23:35:12 cmp02 salt-minion[2824]: +# environment, therefore this configuration value must be set
May  9 23:35:12 cmp02 salt-minion[2824]: +# accordingly if you are using XenAPI.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * Any string that represents a bridge name.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#ovs_integration_bridge=<None>
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# When adding new host to a pool, this will append a --force flag to the
May  9 23:35:12 cmp02 salt-minion[2824]: +# command, forcing hosts to join a pool, even if they have different CPUs.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Since XenServer version 5.6 it is possible to create a pool of hosts that have
May  9 23:35:12 cmp02 salt-minion[2824]: +# different CPU capabilities. To accommodate CPU differences, XenServer limited
May  9 23:35:12 cmp02 salt-minion[2824]: +# features it uses to determine CPU compatibility to only the ones that are
May  9 23:35:12 cmp02 salt-minion[2824]: +# exposed by CPU and support for CPU masking was added.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Despite this effort to level differences between CPUs, it is still possible
May  9 23:35:12 cmp02 salt-minion[2824]: +# that adding new host will fail, thus option to force join was introduced.
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (boolean value)
May  9 23:35:12 cmp02 salt-minion[2824]: +#use_join_force=true
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Publicly visible name for this console host.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Possible values:
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# * A string representing a valid hostname
May  9 23:35:12 cmp02 salt-minion[2824]: +#  (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_public_hostname
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_public_hostname=lcy01-22
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +[xvp]
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Configuration options for XVP.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# xvp (Xen VNC Proxy) is a proxy server providing password-protected VNC-based
May  9 23:35:12 cmp02 salt-minion[2824]: +# access to the consoles of virtual machines hosted on Citrix XenServer.
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# From nova.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# XVP conf template (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_xvp_conf_template
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_xvp_conf_template=$pybasedir/nova/console/xvp.conf.template
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Generated XVP conf file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_xvp_conf
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_xvp_conf=/etc/xvp.conf
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# XVP master process pid file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_xvp_pid
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_xvp_pid=/var/run/xvp.pid
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# XVP log file (string value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_xvp_log
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_xvp_log=/var/log/xvp.log
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# Port for XVP to multiplex VNC connections on (port value)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Minimum value: 0
May  9 23:35:12 cmp02 salt-minion[2824]: +# Maximum value: 65535
May  9 23:35:12 cmp02 salt-minion[2824]: +# Deprecated group/name - [DEFAULT]/console_xvp_multiplex_port
May  9 23:35:12 cmp02 salt-minion[2824]: +#console_xvp_multiplex_port=5900
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/nova/nova.conf] at time 23:35:11.562560 duration_in_ms=496.781
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/default/nova-compute] at time 23:35:11.563057
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/default/nova-compute
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/files/default'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:12 cmp02 salt-minion[2824]: New file
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/default/nova-compute] at time 23:35:11.595534 duration_in_ms=32.477
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [nova-compute] at time 23:35:11.597441
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state service.running for nova-compute
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'status', 'nova-compute.service', '-n', '0'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'nova-compute.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'nova-compute.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] The service nova-compute is already running
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova-compute] at time 23:35:11.676776 duration_in_ms=79.333
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [nova-compute] at time 23:35:11.677164
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state service.mod_watch for nova-compute
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'nova-compute.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'nova-compute.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'nova-compute.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] {'nova-compute': True}
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [nova-compute] at time 23:35:11.776734 duration_in_ms=99.571
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/default/libvirtd] at time 23:35:11.778485
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/default/libvirtd
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/files/pike/libvirt.Debian'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:12 cmp02 salt-minion[2824]: ---
May  9 23:35:12 cmp02 salt-minion[2824]: +++
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1,17 +1,13 @@
May  9 23:35:12 cmp02 salt-minion[2824]: -# Defaults for libvirtd initscript (/etc/init.d/libvirtd)
May  9 23:35:12 cmp02 salt-minion[2824]: +# Defaults for libvirt-bin initscript (/etc/init.d/libvirt-bin)
May  9 23:35:12 cmp02 salt-minion[2824]:  # This is a POSIX shell fragment
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Start libvirtd to handle qemu/kvm:
May  9 23:35:12 cmp02 salt-minion[2824]:  start_libvirtd="yes"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # options passed to libvirtd, add "-l" to listen on tcp
May  9 23:35:12 cmp02 salt-minion[2824]: -#libvirtd_opts=""
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: +# Don't use "-d" option with systemd
May  9 23:35:12 cmp02 salt-minion[2824]: +libvirtd_opts="-l"
May  9 23:35:12 cmp02 salt-minion[2824]: +LIBVIRTD_ARGS="--listen"
May  9 23:35:12 cmp02 salt-minion[2824]:  # pass in location of kerberos keytab
May  9 23:35:12 cmp02 salt-minion[2824]:  #export KRB5_KTNAME=/etc/libvirt/libvirt.keytab
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# Whether to mount a systemd like cgroup layout (only
May  9 23:35:12 cmp02 salt-minion[2824]: -# useful when not running systemd)
May  9 23:35:12 cmp02 salt-minion[2824]: -#mount_cgroups=yes
May  9 23:35:12 cmp02 salt-minion[2824]: -# Which cgroups to mount
May  9 23:35:12 cmp02 salt-minion[2824]: -#cgroups="memory devices"
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/default/libvirtd] at time 23:35:11.809859 duration_in_ms=31.375
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [service.systemctl_reload] at time 23:35:11.812272
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state module.wait for service.systemctl_reload
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] No changes made for service.systemctl_reload
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [service.systemctl_reload] at time 23:35:11.820023 duration_in_ms=7.752
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [service.systemctl_reload] at time 23:35:11.820218
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state module.mod_watch for service.systemctl_reload
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', '--system', 'daemon-reload'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] {'ret': True}
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [service.systemctl_reload] at time 23:35:11.929891 duration_in_ms=109.671
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/libvirt/qemu.conf] at time 23:35:11.930572
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/libvirt/qemu.conf
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/files/pike/qemu.conf.Debian'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:12 cmp02 salt-minion[2824]: ---
May  9 23:35:12 cmp02 salt-minion[2824]: +++
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1,61 +1,8 @@
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  # Master configuration file for the QEMU driver.
May  9 23:35:12 cmp02 salt-minion[2824]:  # All settings described here are optional - if omitted, sensible
May  9 23:35:12 cmp02 salt-minion[2824]:  # defaults are used.
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# Use of TLS requires that x509 certificates be issued. The default is
May  9 23:35:12 cmp02 salt-minion[2824]: -# to keep them in /etc/pki/qemu. This directory must contain
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#  ca-cert.pem - the CA master certificate
May  9 23:35:12 cmp02 salt-minion[2824]: -#  server-cert.pem - the server certificate signed with ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -#  server-key.pem  - the server private key
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# and optionally may contain
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#  dh-params.pem - the DH params configuration file
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the directory does not exist, libvirtd will fail to start. If the
May  9 23:35:12 cmp02 salt-minion[2824]: -# directory doesn't contain the necessary files, QEMU domains will fail
May  9 23:35:12 cmp02 salt-minion[2824]: -# to start if they are configured to use TLS.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to overwrite the default path alter the following. This path
May  9 23:35:12 cmp02 salt-minion[2824]: -# definition will be used as the default path for other *_tls_x509_cert_dir
May  9 23:35:12 cmp02 salt-minion[2824]: -# configuration settings if their default path does not exist or is not
May  9 23:35:12 cmp02 salt-minion[2824]: -# specifically set.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_tls_x509_cert_dir = "/etc/pki/qemu"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The default TLS configuration only uses certificates for the server
May  9 23:35:12 cmp02 salt-minion[2824]: -# allowing the client to verify the server's identity and establish
May  9 23:35:12 cmp02 salt-minion[2824]: -# an encrypted channel.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# It is possible to use x509 certificates for authentication too, by
May  9 23:35:12 cmp02 salt-minion[2824]: -# issuing an x509 certificate to every client who needs to connect.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enabling this option will reject any client who does not have a
May  9 23:35:12 cmp02 salt-minion[2824]: -# certificate signed by the CA in /etc/pki/qemu/ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# The default_tls_x509_cert_dir directory must also contain
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#  client-cert.pem - the client certificate signed with the ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -#  client-key.pem - the client private key
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_tls_x509_verify = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Libvirt assumes the server-key.pem file is unencrypted by default.
May  9 23:35:12 cmp02 salt-minion[2824]: -# To use an encrypted server-key.pem file, the password to decrypt
May  9 23:35:12 cmp02 salt-minion[2824]: -# the PEM file is required. This can be provided by creating a secret
May  9 23:35:12 cmp02 salt-minion[2824]: -# object in libvirt and then to uncomment this setting to set the UUID
May  9 23:35:12 cmp02 salt-minion[2824]: -# of the secret.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# NB This default all-zeros UUID will not work. Replace it with the
May  9 23:35:12 cmp02 salt-minion[2824]: -# output from the UUID for the TLS secret from a 'virsh secret-list'
May  9 23:35:12 cmp02 salt-minion[2824]: -# command and then uncomment the entry
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#default_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]:  # VNC is configured to listen on 127.0.0.1 by default.
May  9 23:35:12 cmp02 salt-minion[2824]:  # To make it listen on all public interfaces, uncomment
May  9 23:35:12 cmp02 salt-minion[2824]:  # this next option.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -69,9 +16,9 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # unix socket. This prevents unprivileged access from users on the
May  9 23:35:12 cmp02 salt-minion[2824]:  # host machine, though most VNC clients do not support it.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -# This will only be enabled for VNC configurations that have listen
May  9 23:35:12 cmp02 salt-minion[2824]: -# type=address but without any address specified. This setting takes
May  9 23:35:12 cmp02 salt-minion[2824]: -# preference over vnc_listen.
May  9 23:35:12 cmp02 salt-minion[2824]: +# This will only be enabled for VNC configurations that do not have
May  9 23:35:12 cmp02 salt-minion[2824]: +# a hardcoded 'listen' or 'socket' value. This setting takes preference
May  9 23:35:12 cmp02 salt-minion[2824]: +# over vnc_listen.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #vnc_auto_unix_socket = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -86,11 +33,15 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #vnc_tls = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to override the default TLS certificate location for
May  9 23:35:12 cmp02 salt-minion[2824]: -# vnc certificates, supply a valid path to the certificate directory.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the provided path does not exist, libvirtd will fail to start.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the path is not provided, but vnc_tls = 1, then the
May  9 23:35:12 cmp02 salt-minion[2824]: -# default_tls_x509_cert_dir path will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use of TLS requires that x509 certificates be issued. The
May  9 23:35:12 cmp02 salt-minion[2824]: +# default it to keep them in /etc/pki/libvirt-vnc. This directory
May  9 23:35:12 cmp02 salt-minion[2824]: +# must contain
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  ca-cert.pem - the CA master certificate
May  9 23:35:12 cmp02 salt-minion[2824]: +#  server-cert.pem - the server certificate signed with ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: +#  server-key.pem  - the server private key
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows the certificate directory to be changed
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #vnc_tls_x509_cert_dir = "/etc/pki/libvirt-vnc"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -100,15 +51,10 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # an encrypted channel.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # It is possible to use x509 certificates for authentication too, by
May  9 23:35:12 cmp02 salt-minion[2824]: -# issuing an x509 certificate to every client who needs to connect.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enabling this option will reject any client that does not have a
May  9 23:35:12 cmp02 salt-minion[2824]: -# ca-cert.pem certificate signed by the CA in the vnc_tls_x509_cert_dir
May  9 23:35:12 cmp02 salt-minion[2824]: -# (or default_tls_x509_cert_dir) as well as the corresponding client-*.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -# files described in default_tls_x509_cert_dir.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# If this option is not supplied, it will be set to the value of
May  9 23:35:12 cmp02 salt-minion[2824]: -# "default_tls_x509_verify".
May  9 23:35:12 cmp02 salt-minion[2824]: +# issuing a x509 certificate to every client who needs to connect.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Enabling this option will reject any client who does not have a
May  9 23:35:12 cmp02 salt-minion[2824]: +# certificate signed by the CA in /etc/pki/libvirt-vnc/ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #vnc_tls_x509_verify = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -172,24 +118,17 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #spice_tls = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to override the default TLS certificate location for
May  9 23:35:12 cmp02 salt-minion[2824]: -# spice certificates, supply a valid path to the certificate directory.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the provided path does not exist, libvirtd will fail to start.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the path is not provided, but spice_tls = 1, then the
May  9 23:35:12 cmp02 salt-minion[2824]: -# default_tls_x509_cert_dir path will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Use of TLS requires that x509 certificates be issued. The
May  9 23:35:12 cmp02 salt-minion[2824]: +# default it to keep them in /etc/pki/libvirt-spice. This directory
May  9 23:35:12 cmp02 salt-minion[2824]: +# must contain
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#  ca-cert.pem - the CA master certificate
May  9 23:35:12 cmp02 salt-minion[2824]: +#  server-cert.pem - the server certificate signed with ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: +#  server-key.pem  - the server private key
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# This option allows the certificate directory to be changed.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #spice_tls_x509_cert_dir = "/etc/pki/libvirt-spice"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enable this option to have SPICE served over an automatically created
May  9 23:35:12 cmp02 salt-minion[2824]: -# unix socket. This prevents unprivileged access from users on the
May  9 23:35:12 cmp02 salt-minion[2824]: -# host machine.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# This will only be enabled for SPICE configurations that have listen
May  9 23:35:12 cmp02 salt-minion[2824]: -# type=address but without any address specified. This setting takes
May  9 23:35:12 cmp02 salt-minion[2824]: -# preference over spice_listen.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#spice_auto_unix_socket = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The default SPICE password. This parameter is only used if the
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -216,123 +155,6 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # point to the directory, and create a qemu.conf in that location
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #spice_sasl_dir = "/some/directory/sasl2"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enable use of TLS encryption on the chardev TCP transports.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# It is necessary to setup CA and issue a server certificate
May  9 23:35:12 cmp02 salt-minion[2824]: -# before enabling this.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#chardev_tls = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to override the default TLS certificate location for character
May  9 23:35:12 cmp02 salt-minion[2824]: -# device TCP certificates, supply a valid path to the certificate directory.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the provided path does not exist, libvirtd will fail to start.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the path is not provided, but chardev_tls = 1, then the
May  9 23:35:12 cmp02 salt-minion[2824]: -# default_tls_x509_cert_dir path will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#chardev_tls_x509_cert_dir = "/etc/pki/libvirt-chardev"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The default TLS configuration only uses certificates for the server
May  9 23:35:12 cmp02 salt-minion[2824]: -# allowing the client to verify the server's identity and establish
May  9 23:35:12 cmp02 salt-minion[2824]: -# an encrypted channel.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# It is possible to use x509 certificates for authentication too, by
May  9 23:35:12 cmp02 salt-minion[2824]: -# issuing an x509 certificate to every client who needs to connect.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enabling this option will reject any client that does not have a
May  9 23:35:12 cmp02 salt-minion[2824]: -# ca-cert.pem certificate signed by the CA in the chardev_tls_x509_cert_dir
May  9 23:35:12 cmp02 salt-minion[2824]: -# (or default_tls_x509_cert_dir) as well as the corresponding client-*.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -# files described in default_tls_x509_cert_dir.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# If this option is not supplied, it will be set to the value of
May  9 23:35:12 cmp02 salt-minion[2824]: -# "default_tls_x509_verify".
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#chardev_tls_x509_verify = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Uncomment and use the following option to override the default secret
May  9 23:35:12 cmp02 salt-minion[2824]: -# UUID provided in the default_tls_x509_secret_uuid parameter.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# NB This default all-zeros UUID will not work. Replace it with the
May  9 23:35:12 cmp02 salt-minion[2824]: -# output from the UUID for the TLS secret from a 'virsh secret-list'
May  9 23:35:12 cmp02 salt-minion[2824]: -# command and then uncomment the entry
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#chardev_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enable use of TLS encryption for all VxHS network block devices that
May  9 23:35:12 cmp02 salt-minion[2824]: -# don't specifically disable.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# When the VxHS network block device server is set up appropriately,
May  9 23:35:12 cmp02 salt-minion[2824]: -# x509 certificates are required for authentication between the clients
May  9 23:35:12 cmp02 salt-minion[2824]: -# (qemu processes) and the remote VxHS server.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# It is necessary to setup CA and issue the client certificate before
May  9 23:35:12 cmp02 salt-minion[2824]: -# enabling this.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#vxhs_tls = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to override the default TLS certificate location for VxHS
May  9 23:35:12 cmp02 salt-minion[2824]: -# backed storage, supply a valid path to the certificate directory.
May  9 23:35:12 cmp02 salt-minion[2824]: -# This is used to authenticate the VxHS block device clients to the VxHS
May  9 23:35:12 cmp02 salt-minion[2824]: -# server.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the provided path does not exist, libvirtd will fail to start.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the path is not provided, but vxhs_tls = 1, then the
May  9 23:35:12 cmp02 salt-minion[2824]: -# default_tls_x509_cert_dir path will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# VxHS block device clients expect the client certificate and key to be
May  9 23:35:12 cmp02 salt-minion[2824]: -# present in the certificate directory along with the CA master certificate.
May  9 23:35:12 cmp02 salt-minion[2824]: -# If using the default environment, default_tls_x509_verify must be configured.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Since this is only a client the server-key.pem certificate is not needed.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Thus a VxHS directory must contain the following:
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#  ca-cert.pem - the CA master certificate
May  9 23:35:12 cmp02 salt-minion[2824]: -#  client-cert.pem - the client certificate signed with the ca-cert.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -#  client-key.pem - the client private key
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#vxhs_tls_x509_cert_dir = "/etc/pki/libvirt-vxhs"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to override the default TLS certificate location for migration
May  9 23:35:12 cmp02 salt-minion[2824]: -# certificates, supply a valid path to the certificate directory. If the
May  9 23:35:12 cmp02 salt-minion[2824]: -# provided path does not exist, libvirtd will fail to start. If the path is
May  9 23:35:12 cmp02 salt-minion[2824]: -# not provided, but migrate_tls = 1, then the default_tls_x509_cert_dir path
May  9 23:35:12 cmp02 salt-minion[2824]: -# will be used. Once/if a default certificate is enabled/defined, migration
May  9 23:35:12 cmp02 salt-minion[2824]: -# will then be able to use the certificate via migration API flags.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#migrate_tls_x509_cert_dir = "/etc/pki/libvirt-migrate"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The default TLS configuration only uses certificates for the server
May  9 23:35:12 cmp02 salt-minion[2824]: -# allowing the client to verify the server's identity and establish
May  9 23:35:12 cmp02 salt-minion[2824]: -# an encrypted channel.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# It is possible to use x509 certificates for authentication too, by
May  9 23:35:12 cmp02 salt-minion[2824]: -# issuing an x509 certificate to every client who needs to connect.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Enabling this option will reject any client that does not have a
May  9 23:35:12 cmp02 salt-minion[2824]: -# ca-cert.pem certificate signed by the CA in the migrate_tls_x509_cert_dir
May  9 23:35:12 cmp02 salt-minion[2824]: -# (or default_tls_x509_cert_dir) as well as the corresponding client-*.pem
May  9 23:35:12 cmp02 salt-minion[2824]: -# files described in default_tls_x509_cert_dir.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# If this option is not supplied, it will be set to the value of
May  9 23:35:12 cmp02 salt-minion[2824]: -# "default_tls_x509_verify".
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#migrate_tls_x509_verify = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Uncomment and use the following option to override the default secret
May  9 23:35:12 cmp02 salt-minion[2824]: -# UUID provided in the default_tls_x509_secret_uuid parameter.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# NB This default all-zeros UUID will not work. Replace it with the
May  9 23:35:12 cmp02 salt-minion[2824]: -# output from the UUID for the TLS secret from a 'virsh secret-list'
May  9 23:35:12 cmp02 salt-minion[2824]: -# command and then uncomment the entry
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#migrate_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # By default, if no graphical front end is configured, libvirt will disable
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -416,10 +238,9 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set to 0 to disable file ownership changes.
May  9 23:35:12 cmp02 salt-minion[2824]:  #dynamic_ownership = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]:  # What cgroup controllers to make use of with QEMU guests
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -#  - 'cpu' - use for scheduler tunables
May  9 23:35:12 cmp02 salt-minion[2824]: +#  - 'cpu' - use for schedular tunables
May  9 23:35:12 cmp02 salt-minion[2824]:  #  - 'devices' - use for device whitelisting
May  9 23:35:12 cmp02 salt-minion[2824]:  #  - 'memory' - use for memory tunables
May  9 23:35:12 cmp02 salt-minion[2824]:  #  - 'blkio' - use for block devices I/O tunables
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -451,19 +272,11 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #    "/dev/null", "/dev/full", "/dev/zero",
May  9 23:35:12 cmp02 salt-minion[2824]:  #    "/dev/random", "/dev/urandom",
May  9 23:35:12 cmp02 salt-minion[2824]:  #    "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
May  9 23:35:12 cmp02 salt-minion[2824]: -#    "/dev/rtc","/dev/hpet"
May  9 23:35:12 cmp02 salt-minion[2824]: +#    "/dev/rtc","/dev/hpet", "/dev/vfio/vfio"
May  9 23:35:12 cmp02 salt-minion[2824]:  #]
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# RDMA migration requires the following extra files to be added to the list:
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/dev/infiniband/rdma_cm",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/dev/infiniband/issm0",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/dev/infiniband/issm1",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/dev/infiniband/umad0",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/dev/infiniband/umad1",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/dev/infiniband/uverbs0"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The default format for QEMU/KVM guest save images is raw; that is, the
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +# The default format for Qemu/KVM guest save images is raw; that is, the
May  9 23:35:12 cmp02 salt-minion[2824]:  # memory from the domain is dumped out directly to a file.  If you have
May  9 23:35:12 cmp02 salt-minion[2824]:  # guests with a large amount of memory, however, this can take up quite
May  9 23:35:12 cmp02 salt-minion[2824]:  # a bit of space.  If you would like to compress the images while they
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -517,20 +330,13 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # unspecified here, determination of a host mount point in /proc/mounts
May  9 23:35:12 cmp02 salt-minion[2824]:  # will be attempted.  Specifying an explicit mount overrides detection
May  9 23:35:12 cmp02 salt-minion[2824]:  # of the same in /proc/mounts.  Setting the mount point to "" will
May  9 23:35:12 cmp02 salt-minion[2824]: -# disable guest hugepage backing. If desired, multiple mount points can
May  9 23:35:12 cmp02 salt-minion[2824]: -# be specified at once, separated by comma and enclosed in square
May  9 23:35:12 cmp02 salt-minion[2824]: -# brackets, for example:
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#     hugetlbfs_mount = ["/dev/hugepages2M", "/dev/hugepages1G"]
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# The size of huge page served by specific mount point is determined by
May  9 23:35:12 cmp02 salt-minion[2824]: -# libvirt at the daemon startup.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# NB, within these mount points, guests will create memory backing
May  9 23:35:12 cmp02 salt-minion[2824]: -# files in a location of $MOUNTPOINT/libvirt/qemu
May  9 23:35:12 cmp02 salt-minion[2824]: +# disable guest hugepage backing.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# NB, within this mount point, guests will create memory backing files
May  9 23:35:12 cmp02 salt-minion[2824]: +# in a location of $MOUNTPOINT/libvirt/qemu
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #hugetlbfs_mount = "/dev/hugepages"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: +#hugetlbfs_mount = ["/run/hugepages/kvm", "/mnt/hugepages_1GB"]
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Path to the setuid helper for creating tap devices.  This executable
May  9 23:35:12 cmp02 salt-minion[2824]:  # is used to create <source type='bridge'> interfaces when libvirtd is
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -566,42 +372,6 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # The same applies to max_files which sets the limit on the maximum
May  9 23:35:12 cmp02 salt-minion[2824]:  # number of opened files.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_processes = 0
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_files = 0
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# If max_core is set to a non-zero integer, then QEMU will be
May  9 23:35:12 cmp02 salt-minion[2824]: -# permitted to create core dumps when it crashes, provided its
May  9 23:35:12 cmp02 salt-minion[2824]: -# RAM size is smaller than the limit set.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Be warned that the core dump will include a full copy of the
May  9 23:35:12 cmp02 salt-minion[2824]: -# guest RAM, if the 'dump_guest_core' setting has been enabled,
May  9 23:35:12 cmp02 salt-minion[2824]: -# or if the guest XML contains
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#   <memory dumpcore="on">...guest ram...</memory>
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# If guest RAM is to be included, ensure the max_core limit
May  9 23:35:12 cmp02 salt-minion[2824]: -# is set to at least the size of the largest expected guest
May  9 23:35:12 cmp02 salt-minion[2824]: -# plus another 1GB for any QEMU host side memory mappings.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# As a special case it can be set to the string "unlimited" to
May  9 23:35:12 cmp02 salt-minion[2824]: -# to allow arbitrarily sized core dumps.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# By default the core dump size is set to 0 disabling all dumps
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Size is a positive integer specifying bytes or the
May  9 23:35:12 cmp02 salt-minion[2824]: -# string "unlimited"
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_core = "unlimited"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Determine if guest RAM is included in QEMU core dumps. By
May  9 23:35:12 cmp02 salt-minion[2824]: -# default guest RAM will be excluded if a new enough QEMU is
May  9 23:35:12 cmp02 salt-minion[2824]: -# present. Setting this to '1' will force guest RAM to always
May  9 23:35:12 cmp02 salt-minion[2824]: -# be included in QEMU core dumps.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# This setting will be ignored if the guest XML has set the
May  9 23:35:12 cmp02 salt-minion[2824]: -# dumpcore attribute on the <memory> element.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#dump_guest_core = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # mac_filter enables MAC addressed based filtering on bridge ports.
May  9 23:35:12 cmp02 salt-minion[2824]:  # This currently requires ebtables to be installed.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -628,13 +398,11 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #allow_disk_format_probing = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# In order to prevent accidentally starting two domains that
May  9 23:35:12 cmp02 salt-minion[2824]: -# share one writable disk, libvirt offers two approaches for
May  9 23:35:12 cmp02 salt-minion[2824]: -# locking files. The first one is sanlock, the other one,
May  9 23:35:12 cmp02 salt-minion[2824]: -# virtlockd, is then our own implementation. Accepted values
May  9 23:35:12 cmp02 salt-minion[2824]: -# are "sanlock" and "lockd".
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#lock_manager = "lockd"
May  9 23:35:12 cmp02 salt-minion[2824]: +# To enable 'Sanlock' project based locking of the file
May  9 23:35:12 cmp02 salt-minion[2824]: +# content (to prevent two VMs writing to the same
May  9 23:35:12 cmp02 salt-minion[2824]: +# disk), uncomment this
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#lock_manager = "sanlock"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: message repeated 2 times: [  ]
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -676,17 +444,10 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #seccomp_sandbox = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  # Override the listen address for all incoming migrations. Defaults to
May  9 23:35:12 cmp02 salt-minion[2824]:  # 0.0.0.0, or :: if both host and qemu are capable of IPv6.
May  9 23:35:12 cmp02 salt-minion[2824]: -#migration_address = "0.0.0.0"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The default hostname or IP address which will be used by a migration
May  9 23:35:12 cmp02 salt-minion[2824]: -# source for transferring migration data to this host.  The migration
May  9 23:35:12 cmp02 salt-minion[2824]: -# source has to be able to resolve this hostname and connect to it so
May  9 23:35:12 cmp02 salt-minion[2824]: -# setting "localhost" will not work.  By default, the host's configured
May  9 23:35:12 cmp02 salt-minion[2824]: -# hostname is used.
May  9 23:35:12 cmp02 salt-minion[2824]: -#migration_host = "host.example.com"
May  9 23:35:12 cmp02 salt-minion[2824]: +#migration_address = "127.0.0.1"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Override the port range used for incoming migrations.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -698,86 +459,9 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #migration_port_min = 49152
May  9 23:35:12 cmp02 salt-minion[2824]:  #migration_port_max = 49215
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: message repeated 2 times: [ -]
May  9 23:35:12 cmp02 salt-minion[2824]: -# Timestamp QEMU's log messages (if QEMU supports it)
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Defaults to 1.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#log_timestamp = 0
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Location of master nvram file
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# When a domain is configured to use UEFI instead of standard
May  9 23:35:12 cmp02 salt-minion[2824]: -# BIOS it may use a separate storage for UEFI variables. If
May  9 23:35:12 cmp02 salt-minion[2824]: -# that's the case libvirt creates the variable store per domain
May  9 23:35:12 cmp02 salt-minion[2824]: -# using this master file as image. Each UEFI firmware can,
May  9 23:35:12 cmp02 salt-minion[2824]: -# however, have different variables store. Therefore the nvram is
May  9 23:35:12 cmp02 salt-minion[2824]: -# a list of strings when a single item is in form of:
May  9 23:35:12 cmp02 salt-minion[2824]: -#   ${PATH_TO_UEFI_FW}:${PATH_TO_UEFI_VARS}.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Later, when libvirt creates per domain variable store, this list is
May  9 23:35:12 cmp02 salt-minion[2824]: -# searched for the master image. The UEFI firmware can be called
May  9 23:35:12 cmp02 salt-minion[2824]: -# differently for different guest architectures. For instance, it's OVMF
May  9 23:35:12 cmp02 salt-minion[2824]: -# for x86_64 and i686, but it's AAVMF for aarch64. The libvirt default
May  9 23:35:12 cmp02 salt-minion[2824]: -# follows this scheme.
May  9 23:35:12 cmp02 salt-minion[2824]: -#nvram = [
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/usr/share/OVMF/OVMF_CODE.fd:/usr/share/OVMF/OVMF_VARS.fd",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/usr/share/OVMF/OVMF_CODE.secboot.fd:/usr/share/OVMF/OVMF_VARS.fd",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/usr/share/AAVMF/AAVMF_CODE.fd:/usr/share/AAVMF/AAVMF_VARS.fd",
May  9 23:35:12 cmp02 salt-minion[2824]: -#   "/usr/share/AAVMF/AAVMF32_CODE.fd:/usr/share/AAVMF/AAVMF32_VARS.fd"
May  9 23:35:12 cmp02 salt-minion[2824]: -#]
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The backend to use for handling stdout/stderr output from
May  9 23:35:12 cmp02 salt-minion[2824]: -# QEMU processes.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#  'file': QEMU writes directly to a plain file. This is the
May  9 23:35:12 cmp02 salt-minion[2824]: -#          historical default, but allows QEMU to inflict a
May  9 23:35:12 cmp02 salt-minion[2824]: -#          denial of service attack on the host by exhausting
May  9 23:35:12 cmp02 salt-minion[2824]: -#          filesystem space
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#  'logd': QEMU writes to a pipe provided by virtlogd daemon.
May  9 23:35:12 cmp02 salt-minion[2824]: -#          This is the current default, providing protection
May  9 23:35:12 cmp02 salt-minion[2824]: -#          against denial of service by performing log file
May  9 23:35:12 cmp02 salt-minion[2824]: -#          rollover when a size limit is hit.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#stdio_handler = "logd"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# QEMU gluster libgfapi log level, debug levels are 0-9, with 9 being the
May  9 23:35:12 cmp02 salt-minion[2824]: -# most verbose, and 0 representing no debugging output.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# The current logging levels defined in the gluster GFAPI are:
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#    0 - None
May  9 23:35:12 cmp02 salt-minion[2824]: -#    1 - Emergency
May  9 23:35:12 cmp02 salt-minion[2824]: -#    2 - Alert
May  9 23:35:12 cmp02 salt-minion[2824]: -#    3 - Critical
May  9 23:35:12 cmp02 salt-minion[2824]: -#    4 - Error
May  9 23:35:12 cmp02 salt-minion[2824]: -#    5 - Warning
May  9 23:35:12 cmp02 salt-minion[2824]: -#    6 - Notice
May  9 23:35:12 cmp02 salt-minion[2824]: -#    7 - Info
May  9 23:35:12 cmp02 salt-minion[2824]: -#    8 - Debug
May  9 23:35:12 cmp02 salt-minion[2824]: -#    9 - Trace
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Defaults to 4
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#gluster_debug_level = 9
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# To enhance security, QEMU driver is capable of creating private namespaces
May  9 23:35:12 cmp02 salt-minion[2824]: -# for each domain started. Well, so far only "mount" namespace is supported. If
May  9 23:35:12 cmp02 salt-minion[2824]: -# enabled it means qemu process is unable to see all the devices on the system,
May  9 23:35:12 cmp02 salt-minion[2824]: -# only those configured for the domain in question. Libvirt then manages
May  9 23:35:12 cmp02 salt-minion[2824]: -# devices entries throughout the domain lifetime. This namespace is turned on
May  9 23:35:12 cmp02 salt-minion[2824]: -# by default.
May  9 23:35:12 cmp02 salt-minion[2824]: -#namespaces = [ "mount" ]
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# This directory is used for memoryBacking source if configured as file.
May  9 23:35:12 cmp02 salt-minion[2824]: -# NOTE: big files will be stored here
May  9 23:35:12 cmp02 salt-minion[2824]: -#memory_backing_dir = "/var/lib/libvirt/qemu/ram"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The following two values set the default RX/TX ring buffer size for virtio
May  9 23:35:12 cmp02 salt-minion[2824]: -# interfaces. These values are taken unless overridden in domain XML. For more
May  9 23:35:12 cmp02 salt-minion[2824]: -# info consult docs to corresponding attributes from domain XML.
May  9 23:35:12 cmp02 salt-minion[2824]: -#rx_queue_size = 1024
May  9 23:35:12 cmp02 salt-minion[2824]: -#tx_queue_size = 1024
May  9 23:35:12 cmp02 salt-minion[2824]: +cgroup_device_acl = [
May  9 23:35:12 cmp02 salt-minion[2824]: +    "/dev/null", "/dev/full", "/dev/zero",
May  9 23:35:12 cmp02 salt-minion[2824]: +    "/dev/random", "/dev/urandom",
May  9 23:35:12 cmp02 salt-minion[2824]: +    "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
May  9 23:35:12 cmp02 salt-minion[2824]: +    "/dev/rtc", "/dev/hpet","/dev/net/tun",
May  9 23:35:12 cmp02 salt-minion[2824]: +]
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/libvirt/qemu.conf] at time 23:35:12.110701 duration_in_ms=180.128
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/libvirt/libvirtd.conf] at time 23:35:12.111185
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/libvirt/libvirtd.conf
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'nova/files/pike/libvirtd.conf.Debian'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:35:12 cmp02 salt-minion[2824]: ---
May  9 23:35:12 cmp02 salt-minion[2824]: +++
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -1,6 +1,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  # Master libvirt daemon configuration file
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -# For further information consult https://libvirt.org/format.html
May  9 23:35:12 cmp02 salt-minion[2824]: +# For further information consult http://libvirt.org/format.html
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # NOTE: the tests/daemon-conf regression test script requires
May  9 23:35:12 cmp02 salt-minion[2824]:  # that each "PARAMETER = VALUE" line in this file have the parameter
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -21,6 +22,12 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # This is enabled by default, uncomment this to disable it
May  9 23:35:12 cmp02 salt-minion[2824]:  #listen_tls = 0
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +listen_tls = 0
May  9 23:35:12 cmp02 salt-minion[2824]: +listen_tcp = 1
May  9 23:35:12 cmp02 salt-minion[2824]: +auth_tcp = "none"
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  # Listen for unencrypted TCP connections on the public TCP/IP port.
May  9 23:35:12 cmp02 salt-minion[2824]:  # NB, must pass the --listen flag to the libvirtd process for this to
May  9 23:35:12 cmp02 salt-minion[2824]:  # have any effect.
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -48,10 +55,6 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # Override the default configuration which binds to all network
May  9 23:35:12 cmp02 salt-minion[2824]:  # interfaces. This can be a numeric IPv4/6 address, or hostname
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -# If the libvirtd service is started in parallel with network
May  9 23:35:12 cmp02 salt-minion[2824]: -# startup (e.g. with systemd), binding to addresses other than
May  9 23:35:12 cmp02 salt-minion[2824]: -# the wildcards (0.0.0.0/::) might not be available yet.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]:  #listen_addr = "192.168.0.1"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -67,7 +70,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # unique on the immediate broadcast network.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # The default is "Virtualization Host HOSTNAME", where HOSTNAME
May  9 23:35:12 cmp02 salt-minion[2824]: -# is substituted for the short hostname of the machine (without domain)
May  9 23:35:12 cmp02 salt-minion[2824]: +# is subsituted for the short hostname of the machine (without domain)
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #mdns_name = "Virtualization Host Joe Demo"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -82,14 +85,14 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # without becoming root.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # This is restricted to 'root' by default.
May  9 23:35:12 cmp02 salt-minion[2824]: -unix_sock_group = "libvirt"
May  9 23:35:12 cmp02 salt-minion[2824]: +unix_sock_group = "libvirtd"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set the UNIX socket permissions for the R/O socket. This is used
May  9 23:35:12 cmp02 salt-minion[2824]:  # for monitoring VM status only
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -# Default allows any user. If setting group ownership, you may want to
May  9 23:35:12 cmp02 salt-minion[2824]: -# restrict this too.
May  9 23:35:12 cmp02 salt-minion[2824]: -unix_sock_ro_perms = "0777"
May  9 23:35:12 cmp02 salt-minion[2824]: +# Default allows any user. If setting group ownership may want to
May  9 23:35:12 cmp02 salt-minion[2824]: +# restrict this to:
May  9 23:35:12 cmp02 salt-minion[2824]: +#unix_sock_ro_perms = "0777"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set the UNIX socket permissions for the R/W socket. This is used
May  9 23:35:12 cmp02 salt-minion[2824]:  # for full management of VMs
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -98,19 +101,11 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # the default will change to allow everyone (eg, 0777)
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # If not using PolicyKit and setting group ownership for access
May  9 23:35:12 cmp02 salt-minion[2824]: -# control, then you may want to relax this too.
May  9 23:35:12 cmp02 salt-minion[2824]: +# control then you may want to relax this to:
May  9 23:35:12 cmp02 salt-minion[2824]:  unix_sock_rw_perms = "0770"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Set the UNIX socket permissions for the admin interface socket.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Default allows only owner (root), do not change it unless you are
May  9 23:35:12 cmp02 salt-minion[2824]: -# sure to whom you are exposing the access to.
May  9 23:35:12 cmp02 salt-minion[2824]: -#unix_sock_admin_perms = "0700"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Set the name of the directory in which sockets will be found/created.
May  9 23:35:12 cmp02 salt-minion[2824]:  #unix_sock_dir = "/var/run/libvirt"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  #################################################################
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -125,7 +120,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #  - sasl: use SASL infrastructure. The actual auth scheme is then
May  9 23:35:12 cmp02 salt-minion[2824]:  #          controlled from /etc/sasl2/libvirt.conf. For the TCP
May  9 23:35:12 cmp02 salt-minion[2824]:  #          socket only GSSAPI & DIGEST-MD5 mechanisms will be used.
May  9 23:35:12 cmp02 salt-minion[2824]: -#          For non-TCP or TLS sockets, any scheme is allowed.
May  9 23:35:12 cmp02 salt-minion[2824]: +#          For non-TCP or TLS sockets,  any scheme is allowed.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #  - polkit: use PolicyKit to authenticate. This is only suitable
May  9 23:35:12 cmp02 salt-minion[2824]:  #            for use on the UNIX sockets. The default policy will
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -156,6 +151,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # use, always enable SASL and use the GSSAPI or DIGEST-MD5
May  9 23:35:12 cmp02 salt-minion[2824]:  # mechanism in /etc/sasl2/libvirt.conf
May  9 23:35:12 cmp02 salt-minion[2824]:  #auth_tcp = "sasl"
May  9 23:35:12 cmp02 salt-minion[2824]: +#auth_tcp = "none"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Change the authentication scheme for TLS sockets.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -167,15 +163,6 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #auth_tls = "none"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# Change the API access control scheme
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# By default an authenticated user is allowed access
May  9 23:35:12 cmp02 salt-minion[2824]: -# to all APIs. Access drivers can place restrictions
May  9 23:35:12 cmp02 salt-minion[2824]: -# on this. By default the 'nop' driver is enabled,
May  9 23:35:12 cmp02 salt-minion[2824]: -# meaning no access control checks are done once a
May  9 23:35:12 cmp02 salt-minion[2824]: -# client has authenticated with libvirtd
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#access_drivers = [ "polkit" ]
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  #################################################################
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -228,7 +215,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #tls_no_verify_certificate = 1
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# A whitelist of allowed x509 Distinguished Names
May  9 23:35:12 cmp02 salt-minion[2824]: +# A whitelist of allowed x509  Distinguished Names
May  9 23:35:12 cmp02 salt-minion[2824]:  # This list may contain wildcards such as
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #    "C=GB,ST=London,L=London,O=Red Hat,CN=*"
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -242,7 +229,7 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #tls_allowed_dn_list = ["DN1", "DN2"]
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# A whitelist of allowed SASL usernames. The format for username
May  9 23:35:12 cmp02 salt-minion[2824]: +# A whitelist of allowed SASL usernames. The format for usernames
May  9 23:35:12 cmp02 salt-minion[2824]:  # depends on the SASL authentication mechanism. Kerberos usernames
May  9 23:35:12 cmp02 salt-minion[2824]:  # look like username@REALM
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -259,13 +246,6 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #sasl_allowed_username_list = ["joe@EXAMPLE.COM", "fred@EXAMPLE.COM" ]
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# Override the compile time default TLS priority string. The
May  9 23:35:12 cmp02 salt-minion[2824]: -# default is usually "NORMAL" unless overridden at build time.
May  9 23:35:12 cmp02 salt-minion[2824]: -# Only set this is it is desired for libvirt to deviate from
May  9 23:35:12 cmp02 salt-minion[2824]: -# the global default settings.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#tls_priority="NORMAL"
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  #################################################################
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -274,22 +254,12 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The maximum number of concurrent client connections to allow
May  9 23:35:12 cmp02 salt-minion[2824]:  # over all sockets combined.
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_clients = 5000
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The maximum length of queue of connections waiting to be
May  9 23:35:12 cmp02 salt-minion[2824]: -# accepted by the daemon. Note, that some protocols supporting
May  9 23:35:12 cmp02 salt-minion[2824]: -# retransmission may obey this so that a later reattempt at
May  9 23:35:12 cmp02 salt-minion[2824]: -# connection succeeds.
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_queued_clients = 1000
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# The maximum length of queue of accepted but not yet
May  9 23:35:12 cmp02 salt-minion[2824]: -# authenticated clients. The default value is 20. Set this to
May  9 23:35:12 cmp02 salt-minion[2824]: -# zero to turn this feature off.
May  9 23:35:12 cmp02 salt-minion[2824]: -#max_anonymous_clients = 20
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_clients = 20
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The minimum limit sets the number of workers to start up
May  9 23:35:12 cmp02 salt-minion[2824]:  # initially. If the number of active clients exceeds this,
May  9 23:35:12 cmp02 salt-minion[2824]: -# then more threads are spawned, up to max_workers limit.
May  9 23:35:12 cmp02 salt-minion[2824]: +# then more threads are spawned, upto max_workers limit.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Typically you'd want max_workers to equal maximum number
May  9 23:35:12 cmp02 salt-minion[2824]:  # of clients allowed
May  9 23:35:12 cmp02 salt-minion[2824]:  #min_workers = 5
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -297,25 +267,25 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # The number of priority workers. If all workers from above
May  9 23:35:12 cmp02 salt-minion[2824]: -# pool are stuck, some calls marked as high priority
May  9 23:35:12 cmp02 salt-minion[2824]: +# pool will stuck, some calls marked as high priority
May  9 23:35:12 cmp02 salt-minion[2824]:  # (notably domainDestroy) can be executed in this pool.
May  9 23:35:12 cmp02 salt-minion[2824]:  #prio_workers = 5
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: +# Total global limit on concurrent RPC calls. Should be
May  9 23:35:12 cmp02 salt-minion[2824]: +# at least as large as max_workers. Beyond this, RPC requests
May  9 23:35:12 cmp02 salt-minion[2824]: +# will be read into memory and queued. This directly impact
May  9 23:35:12 cmp02 salt-minion[2824]: +# memory usage, currently each request requires 256 KB of
May  9 23:35:12 cmp02 salt-minion[2824]: +# memory. So by default upto 5 MB of memory is used
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# XXX this isn't actually enforced yet, only the per-client
May  9 23:35:12 cmp02 salt-minion[2824]: +# limit is used so far
May  9 23:35:12 cmp02 salt-minion[2824]: +#max_requests = 20
May  9 23:35:12 cmp02 salt-minion[2824]: +
May  9 23:35:12 cmp02 salt-minion[2824]:  # Limit on concurrent requests from a single client
May  9 23:35:12 cmp02 salt-minion[2824]:  # connection. To avoid one client monopolizing the server
May  9 23:35:12 cmp02 salt-minion[2824]: -# this should be a small fraction of the global max_workers
May  9 23:35:12 cmp02 salt-minion[2824]: -# parameter.
May  9 23:35:12 cmp02 salt-minion[2824]: +# this should be a small fraction of the global max_requests
May  9 23:35:12 cmp02 salt-minion[2824]: +# and max_workers parameter
May  9 23:35:12 cmp02 salt-minion[2824]:  #max_client_requests = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Same processing controls, but this time for the admin interface.
May  9 23:35:12 cmp02 salt-minion[2824]: -# For description of each option, be so kind to scroll few lines
May  9 23:35:12 cmp02 salt-minion[2824]: -# upwards.
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_min_workers = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_max_workers = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_max_clients = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_max_queued_clients = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_max_client_requests = 5
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  #################################################################
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -324,10 +294,6 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Logging level: 4 errors, 3 warnings, 2 information, 1 debug
May  9 23:35:12 cmp02 salt-minion[2824]:  # basically 1 will log everything possible
May  9 23:35:12 cmp02 salt-minion[2824]: -# Note: Journald may employ rate limiting of the messages logged
May  9 23:35:12 cmp02 salt-minion[2824]: -# and thus lock up the libvirt daemon. To use the debug level with
May  9 23:35:12 cmp02 salt-minion[2824]: -# journald you have to specify it explicitly in 'log_outputs', otherwise
May  9 23:35:12 cmp02 salt-minion[2824]: -# only information level messages will be logged.
May  9 23:35:12 cmp02 salt-minion[2824]:  #log_level = 3
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  # Logging filters:
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -336,22 +302,16 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # The format for a filter is one of:
May  9 23:35:12 cmp02 salt-minion[2824]:  #    x:name
May  9 23:35:12 cmp02 salt-minion[2824]:  #    x:+name
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -#      where name is a string which is matched against the category
May  9 23:35:12 cmp02 salt-minion[2824]: -#      given in the VIR_LOG_INIT() at the top of each libvirt source
May  9 23:35:12 cmp02 salt-minion[2824]: -#      file, e.g., "remote", "qemu", or "util.json" (the name in the
May  9 23:35:12 cmp02 salt-minion[2824]: -#      filter can be a substring of the full category name, in order
May  9 23:35:12 cmp02 salt-minion[2824]: -#      to match multiple similar categories), the optional "+" prefix
May  9 23:35:12 cmp02 salt-minion[2824]: -#      tells libvirt to log stack trace for each message matching
May  9 23:35:12 cmp02 salt-minion[2824]: -#      name, and x is the minimal level where matching messages should
May  9 23:35:12 cmp02 salt-minion[2824]: -#      be logged:
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: +#      where name is a string which is matched against source file name,
May  9 23:35:12 cmp02 salt-minion[2824]: +#      e.g., "remote", "qemu", or "util/json", the optional "+" prefix
May  9 23:35:12 cmp02 salt-minion[2824]: +#      tells libvirt to log stack trace for each message matching name,
May  9 23:35:12 cmp02 salt-minion[2824]: +#      and x is the minimal level where matching messages should be logged:
May  9 23:35:12 cmp02 salt-minion[2824]:  #    1: DEBUG
May  9 23:35:12 cmp02 salt-minion[2824]:  #    2: INFO
May  9 23:35:12 cmp02 salt-minion[2824]:  #    3: WARNING
May  9 23:35:12 cmp02 salt-minion[2824]:  #    4: ERROR
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -# Multiple filters can be defined in a single @filters, they just need to be
May  9 23:35:12 cmp02 salt-minion[2824]: +# Multiple filter can be defined in a single @filters, they just need to be
May  9 23:35:12 cmp02 salt-minion[2824]:  # separated by spaces.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  # e.g. to only get warning or errors from the remote layer and only errors
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -367,24 +327,22 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  #      use syslog for the output and use the given name as the ident
May  9 23:35:12 cmp02 salt-minion[2824]:  #    x:file:file_path
May  9 23:35:12 cmp02 salt-minion[2824]:  #      output to a file, with the given filepath
May  9 23:35:12 cmp02 salt-minion[2824]: -#    x:journald
May  9 23:35:12 cmp02 salt-minion[2824]: -#      output to journald logging system
May  9 23:35:12 cmp02 salt-minion[2824]:  # In all case the x prefix is the minimal level, acting as a filter
May  9 23:35:12 cmp02 salt-minion[2824]:  #    1: DEBUG
May  9 23:35:12 cmp02 salt-minion[2824]:  #    2: INFO
May  9 23:35:12 cmp02 salt-minion[2824]:  #    3: WARNING
May  9 23:35:12 cmp02 salt-minion[2824]:  #    4: ERROR
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]: -# Multiple outputs can be defined, they just need to be separated by spaces.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Multiple output can be defined, they just need to be separated by spaces.
May  9 23:35:12 cmp02 salt-minion[2824]:  # e.g. to log all warnings and errors to syslog under the libvirtd ident:
May  9 23:35:12 cmp02 salt-minion[2824]:  #log_outputs="3:syslog:libvirtd"
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: -# Log debug buffer size:
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# This configuration option is no longer used, since the global
May  9 23:35:12 cmp02 salt-minion[2824]: -# log buffer functionality has been removed. Please configure
May  9 23:35:12 cmp02 salt-minion[2824]: -# suitable log_outputs/log_filters settings to obtain logs.
May  9 23:35:12 cmp02 salt-minion[2824]: +# Log debug buffer size: default 64
May  9 23:35:12 cmp02 salt-minion[2824]: +# The daemon keeps an internal debug log buffer which will be dumped in case
May  9 23:35:12 cmp02 salt-minion[2824]: +# of crash or upon receiving a SIGUSR2 signal. This setting allows to override
May  9 23:35:12 cmp02 salt-minion[2824]: +# the default buffer size in kilobytes.
May  9 23:35:12 cmp02 salt-minion[2824]: +# If value is 0 or less the debug log buffer is deactivated
May  9 23:35:12 cmp02 salt-minion[2824]:  #log_buffer_size = 64
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -407,16 +365,10 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  ###################################################################
May  9 23:35:12 cmp02 salt-minion[2824]:  # UUID of the host:
May  9 23:35:12 cmp02 salt-minion[2824]: -# Host UUID is read from one of the sources specified in host_uuid_source.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# - 'smbios': fetch the UUID from 'dmidecode -s system-uuid'
May  9 23:35:12 cmp02 salt-minion[2824]: -# - 'machine-id': fetch the UUID from /etc/machine-id
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# The host_uuid_source default is 'smbios'. If 'dmidecode' does not provide
May  9 23:35:12 cmp02 salt-minion[2824]: -# a valid UUID a temporary UUID will be generated.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# Another option is to specify host UUID in host_uuid.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: +# Provide the UUID of the host here in case the command
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'dmidecode -s system-uuid' does not provide a valid uuid. In case
May  9 23:35:12 cmp02 salt-minion[2824]: +# 'dmidecode' does not provide a valid UUID and none is provided here, a
May  9 23:35:12 cmp02 salt-minion[2824]: +# temporary UUID will be generated.
May  9 23:35:12 cmp02 salt-minion[2824]:  # Keep the format of the example UUID below. UUID must not have all digits
May  9 23:35:12 cmp02 salt-minion[2824]:  # be the same.
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -424,12 +376,11 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # it with the output of the 'uuidgen' command and then
May  9 23:35:12 cmp02 salt-minion[2824]:  # uncomment this entry
May  9 23:35:12 cmp02 salt-minion[2824]:  #host_uuid = "00000000-0000-0000-0000-000000000000"
May  9 23:35:12 cmp02 salt-minion[2824]: -#host_uuid_source = "smbios"
May  9 23:35:12 cmp02 salt-minion[2824]:  
May  9 23:35:12 cmp02 salt-minion[2824]:  ###################################################################
May  9 23:35:12 cmp02 salt-minion[2824]:  # Keepalive protocol:
May  9 23:35:12 cmp02 salt-minion[2824]:  # This allows libvirtd to detect broken client connections or even
May  9 23:35:12 cmp02 salt-minion[2824]: -# dead clients.  A keepalive message is sent to a client after
May  9 23:35:12 cmp02 salt-minion[2824]: +# dead client.  A keepalive message is sent to a client after
May  9 23:35:12 cmp02 salt-minion[2824]:  # keepalive_interval seconds of inactivity to check if the client is
May  9 23:35:12 cmp02 salt-minion[2824]:  # still responding; keepalive_count is a maximum number of keepalive
May  9 23:35:12 cmp02 salt-minion[2824]:  # messages that are allowed to be sent to the client without getting
May  9 23:35:12 cmp02 salt-minion[2824]: @@ -438,31 +389,15 @@
May  9 23:35:12 cmp02 salt-minion[2824]:  # keepalive_interval * (keepalive_count + 1) seconds since the last
May  9 23:35:12 cmp02 salt-minion[2824]:  # message received from the client.  If keepalive_interval is set to
May  9 23:35:12 cmp02 salt-minion[2824]:  # -1, libvirtd will never send keepalive requests; however clients
May  9 23:35:12 cmp02 salt-minion[2824]: -# can still send them and the daemon will send responses.  When
May  9 23:35:12 cmp02 salt-minion[2824]: +# can still send them and the deamon will send responses.  When
May  9 23:35:12 cmp02 salt-minion[2824]:  # keepalive_count is set to 0, connections will be automatically
May  9 23:35:12 cmp02 salt-minion[2824]:  # closed after keepalive_interval seconds of inactivity without
May  9 23:35:12 cmp02 salt-minion[2824]:  # sending any keepalive messages.
May  9 23:35:12 cmp02 salt-minion[2824]:  #
May  9 23:35:12 cmp02 salt-minion[2824]:  #keepalive_interval = 5
May  9 23:35:12 cmp02 salt-minion[2824]:  #keepalive_count = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -# These configuration options are no longer used.  There is no way to
May  9 23:35:12 cmp02 salt-minion[2824]: -# restrict such clients from connecting since they first need to
May  9 23:35:12 cmp02 salt-minion[2824]: -# connect in order to ask for keepalive.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#keepalive_required = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_keepalive_required = 1
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -# Keepalive settings for the admin interface
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_keepalive_interval = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -#admin_keepalive_count = 5
May  9 23:35:12 cmp02 salt-minion[2824]: -
May  9 23:35:12 cmp02 salt-minion[2824]: -###################################################################
May  9 23:35:12 cmp02 salt-minion[2824]: -# Open vSwitch:
May  9 23:35:12 cmp02 salt-minion[2824]: -# This allows to specify a timeout for openvswitch calls made by
May  9 23:35:12 cmp02 salt-minion[2824]: -# libvirt. The ovs-vsctl utility is used for the configuration and
May  9 23:35:12 cmp02 salt-minion[2824]: -# its timeout option is set by default to 5 seconds to avoid
May  9 23:35:12 cmp02 salt-minion[2824]: -# potential infinite waits blocking libvirt.
May  9 23:35:12 cmp02 salt-minion[2824]: -#
May  9 23:35:12 cmp02 salt-minion[2824]: -#ovs_timeout = 5
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +# If set to 1, libvirtd will refuse to talk to clients that do not
May  9 23:35:12 cmp02 salt-minion[2824]: +# support keepalive protocol.  Defaults to 0.
May  9 23:35:12 cmp02 salt-minion[2824]: +#
May  9 23:35:12 cmp02 salt-minion[2824]: +#keepalive_required = 1
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/libvirt/libvirtd.conf] at time 23:35:12.302909 duration_in_ms=191.723
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [virsh net-destroy default] at time 23:35:12.304779
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state cmd.run for virsh net-destroy default
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command 'virsh net-list | grep default' in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command 'virsh net-destroy default' in directory '/root'
May  9 23:35:12 cmp02 dnsmasq[27939]: exiting on receipt of SIGTERM
May  9 23:35:12 cmp02 kernel: [ 1120.205260] device virbr0-nic left promiscuous mode
May  9 23:35:12 cmp02 kernel: [ 1120.205266] virbr0: port 1(virbr0-nic) entered disabled state
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] {'pid': 5551, 'retcode': 0, 'stderr': '', 'stdout': 'Network default destroyed'}
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [virsh net-destroy default] at time 23:35:12.640457 duration_in_ms=335.678
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [libvirtd] at time 23:35:12.644518
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state service.running for libvirtd
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'status', 'libvirtd.service', '-n', '0'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'libvirtd.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'libvirtd.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] The service libvirtd is already running
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [libvirtd] at time 23:35:12.714403 duration_in_ms=69.885
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Running state [libvirtd] at time 23:35:12.714726
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing state service.mod_watch for libvirtd
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'libvirtd.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'libvirtd.service'] in directory '/root'
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'libvirtd.service'] in directory '/root'
May  9 23:35:12 cmp02 systemd[1]: Started /bin/systemctl restart libvirtd.service.
May  9 23:35:12 cmp02 systemd[1]: Stopping Virtualization daemon...
May  9 23:35:12 cmp02 systemd[1]: Stopped Virtualization daemon.
May  9 23:35:12 cmp02 systemd[1]: Starting Virtualization daemon...
May  9 23:35:12 cmp02 systemd[1]: Started Virtualization daemon.
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] {'libvirtd': True}
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Completed state [libvirtd] at time 23:35:12.881009 duration_in_ms=166.283
May  9 23:35:12 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233256310298
May  9 23:35:13 cmp02 systemd-udevd[5717]: Could not generate persistent MAC address for virbr0: No such file or directory
May  9 23:35:13 cmp02 systemd-udevd[5720]: Could not generate persistent MAC address for virbr0-nic: No such file or directory
May  9 23:35:13 cmp02 kernel: [ 1121.711240] virbr0: port 1(virbr0-nic) entered blocking state
May  9 23:35:13 cmp02 kernel: [ 1121.711243] virbr0: port 1(virbr0-nic) entered disabled state
May  9 23:35:13 cmp02 kernel: [ 1121.711304] device virbr0-nic entered promiscuous mode
May  9 23:35:14 cmp02 kernel: [ 1121.854313] virbr0: port 1(virbr0-nic) entered blocking state
May  9 23:35:14 cmp02 kernel: [ 1121.854316] virbr0: port 1(virbr0-nic) entered listening state
May  9 23:35:14 cmp02 dnsmasq[5940]: started, version 2.78 cachesize 150
May  9 23:35:14 cmp02 dnsmasq[5940]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
May  9 23:35:14 cmp02 dnsmasq-dhcp[5940]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
May  9 23:35:14 cmp02 dnsmasq-dhcp[5940]: DHCP, sockets bound exclusively to interface virbr0
May  9 23:35:14 cmp02 dnsmasq[5940]: reading /etc/resolv.conf
May  9 23:35:14 cmp02 dnsmasq[5940]: using nameserver 192.168.11.1#53
May  9 23:35:14 cmp02 dnsmasq[5940]: read /etc/hosts - 12 addresses
May  9 23:35:14 cmp02 dnsmasq[5940]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
May  9 23:35:14 cmp02 dnsmasq-dhcp[5940]: read /var/lib/libvirt/dnsmasq/default.hostsfile
May  9 23:35:14 cmp02 kernel: [ 1121.896992] virbr0: port 1(virbr0-nic) entered disabled state
May  9 23:38:00 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command state.sls with jid 20180509233800436434
May  9 23:38:00 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 6006
May  9 23:38:02 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:38:02 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ceilometer/init.sls'
May  9 23:38:02 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ceilometer/agent.sls'
May  9 23:38:04 cmp02 salt-minion[2824]: [INFO    ] Running state [ceilometer-agent-compute] at time 23:38:04.810080
May  9 23:38:04 cmp02 salt-minion[2824]: [INFO    ] Executing state pkg.installed for ceilometer-agent-compute
May  9 23:38:04 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:38:05 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-cache', '-q', 'policy', 'ceilometer-agent-compute'] in directory '/root'
May  9 23:38:05 cmp02 salt-minion[2824]: [INFO    ] Executing command ['apt-get', '-q', 'update'] in directory '/root'
May  9 23:38:07 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg', '--get-selections', '*'] in directory '/root'
May  9 23:38:07 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'apt-get', '-q', '-y', '-o', 'DPkg::Options::=--force-confold', '-o', 'DPkg::Options::=--force-confdef', 'install', 'ceilometer-agent-compute'] in directory '/root'
May  9 23:38:07 cmp02 systemd[1]: Started /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-confdef install ceilometer-agent-compute.
May  9 23:38:10 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233810555296
May  9 23:38:10 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 6470
May  9 23:38:10 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233810555296
May  9 23:38:14 cmp02 systemd[1]: Reloading.
May  9 23:38:14 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:38:17 cmp02 systemd[1]: Reloading.
May  9 23:38:17 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:38:17 cmp02 systemd[1]: Reloading.
May  9 23:38:17 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:38:17 cmp02 systemd[1]: Reloading.
May  9 23:38:17 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:38:17 cmp02 systemd[1]: Starting Ceilometer Agent Compute...
May  9 23:38:17 cmp02 systemd[1]: Started Ceilometer Agent Compute.
May  9 23:38:20 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command saltutil.find_job with jid 20180509233820583008
May  9 23:38:20 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 7379
May  9 23:38:20 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233820583008
May  9 23:38:21 cmp02 systemd[1]: Reloading.
May  9 23:38:21 cmp02 systemd[1]: Started ACPI event daemon.
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Executing command ['dpkg-query', '--showformat', '${Status} ${Package} ${Version} ${Architecture}\n', '-W'] in directory '/root'
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Made the following changes:
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pysnmp4' changed from 'absent' to '4.2.5-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-waitress' changed from 'absent' to '0.8.10-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pysnmp4-mibs' changed from 'absent' to '0.1.3-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pysnmp2' changed from 'absent' to '1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-kafka' changed from 'absent' to '1.3.2-1.1~u16.04+mcp2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-webtest' changed from 'absent' to '2.0.18-1ubuntu1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-cotyledon' changed from 'absent' to '1.6.3-1.1~u16.04+mcp2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-ipaddr' changed from 'absent' to '2.1.11-2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-twisted-core' changed from 'absent' to '16.0.0-1ubuntu0.2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'ceilometer-common' changed from 'absent' to '1:9.0.5-2~u16.04+mcp13'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-logutils' changed from 'absent' to '0.3.3-5'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-jsonpath-rw' changed from 'absent' to '1.4.0-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-attr' changed from 'absent' to '15.2.0-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'smitools' changed from 'absent' to '0.4.8+dfsg2-11'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python2.7-waitress' changed from 'absent' to '1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-twisted-bin' changed from 'absent' to '16.0.0-1ubuntu0.2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-wsme' changed from 'absent' to '0.8.0-2ubuntu2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pysnmp-common' changed from 'absent' to '1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'ceilometer-agent-compute' changed from 'absent' to '1:9.0.5-2~u16.04+mcp13'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pam' changed from 'absent' to '0.4.2-13.2ubuntu2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-singledispatch' changed from 'absent' to '3.4.0.3-2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-simplegeneric' changed from 'absent' to '0.8.1-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-twisted' changed from 'absent' to '16.0.0-1ubuntu0.2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-ceilometer' changed from 'absent' to '1:9.0.5-2~u16.04+mcp13'
May  9 23:38:23 cmp02 salt-minion[2824]: 'libsmi2ldbl' changed from 'absent' to '0.4.8+dfsg2-11'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pecan' changed from 'absent' to '1.1.2-1.1~u16.04+mcp2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python2.7-twisted' changed from 'absent' to '1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-croniter' changed from 'absent' to '0.3.8-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-setproctitle' changed from 'absent' to '1.1.8-1build2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python2.7-twisted-core' changed from 'absent' to '1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-serial' changed from 'absent' to '3.0.1-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-service-identity' changed from 'absent' to '16.0.0-2'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-jsonpath-rw-ext' changed from 'absent' to '0.1.9-1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python2.7-twisted-bin' changed from 'absent' to '1'
May  9 23:38:23 cmp02 salt-minion[2824]: 'python-pysnmp4-apps' changed from 'absent' to '0.3.2-1'
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Loading fresh modules for state activity
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Completed state [ceilometer-agent-compute] at time 23:38:23.595755 duration_in_ms=18785.676
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/ceilometer/ceilometer.conf] at time 23:38:23.603662
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/ceilometer/ceilometer.conf
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ceilometer/files/pike/ceilometer-agent.conf.Debian'
May  9 23:38:23 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:38:23 cmp02 salt-minion[2824]: ---
May  9 23:38:23 cmp02 salt-minion[2824]: +++
May  9 23:38:23 cmp02 salt-minion[2824]: @@ -1,2173 +1,39 @@
May  9 23:38:23 cmp02 salt-minion[2824]:  [DEFAULT]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# To reduce polling agent load, samples are sent to the notification agent in a
May  9 23:38:23 cmp02 salt-minion[2824]: -# batch. To gain higher throughput at the cost of load set this to False.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#batch_polled_samples = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# To reduce large requests at same time to Nova or other components from
May  9 23:38:23 cmp02 salt-minion[2824]: -# different compute agents, shuffle start time of polling task. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#shuffle_time_before_polling_task = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Configuration file for WSGI definition of API. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#api_paste_config = api_paste.ini
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Inspector to use for inspecting the hypervisor layer. Known inspectors are
May  9 23:38:23 cmp02 salt-minion[2824]: -# libvirt, hyperv, vsphere and xenapi. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#hypervisor_inspector = libvirt
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Libvirt domain type. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: kvm, lxc, qemu, uml, xen
May  9 23:38:23 cmp02 salt-minion[2824]: -#libvirt_type = kvm
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Override the default libvirt URI (which is dependent on libvirt_type).
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#libvirt_uri =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Dispatchers to process metering data. (multi valued)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/dispatcher
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: This option only be used in collector service, the collector service
May  9 23:38:23 cmp02 salt-minion[2824]: -# has been deprecated and will be removed in the future, this should also be
May  9 23:38:23 cmp02 salt-minion[2824]: -# deprecated for removal with collector service.
May  9 23:38:23 cmp02 salt-minion[2824]: -#meter_dispatchers =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Dispatchers to process event data. (multi valued)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/dispatcher
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: This option only be used in collector service, the collector service
May  9 23:38:23 cmp02 salt-minion[2824]: -# has been deprecated and will be removed in the future, this should also be
May  9 23:38:23 cmp02 salt-minion[2824]: -# deprecated for removal with collector service.
May  9 23:38:23 cmp02 salt-minion[2824]: -#event_dispatchers =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Exchange name for Ironic notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ironic_exchange = ironic
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Allow novaclient's debug log output. (Use default_log_levels
May  9 23:38:23 cmp02 salt-minion[2824]: -# instead) (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -#nova_http_log_debug = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Swift reseller prefix. Must be on par with reseller_prefix in proxy-
May  9 23:38:23 cmp02 salt-minion[2824]: -# server.conf. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#reseller_prefix = AUTH_
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Configuration file for pipeline definition. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#pipeline_cfg_file = pipeline.yaml
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Configuration file for event pipeline definition. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#event_pipeline_cfg_file = event_pipeline.yaml
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Source for samples emitted on this instance. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sample_source = openstack
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# List of metadata prefixes reserved for metering use. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#reserved_metadata_namespace = metering.
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Limit on length of reserved metadata values. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#reserved_metadata_length = 256
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# List of metadata keys reserved for metering use. And these keys are
May  9 23:38:23 cmp02 salt-minion[2824]: -# additional to the ones included in the namespace. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#reserved_metadata_keys =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Path to the rootwrap configuration file to use for running commands as root
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rootwrap_config = /etc/ceilometer/rootwrap.conf
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Nova notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#nova_control_exchange = nova
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Neutron notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#neutron_control_exchange = neutron
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Heat notifications (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#heat_control_exchange = heat
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Glance notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#glance_control_exchange = glance
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Keystone notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#keystone_control_exchange = keystone
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Cinder notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#cinder_control_exchange = cinder
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Data Processing notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#sahara_control_exchange = sahara
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Swift notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#swift_control_exchange = swift
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Magnum notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#magnum_control_exchange = magnum
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for DBaaS notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#trove_control_exchange = trove
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for Messaging service notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#zaqar_control_exchange = zaqar
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for DNS service notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#dns_control_exchange = central
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Exchange name for ceilometer notifications. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Use notification_control_exchanges instead
May  9 23:38:23 cmp02 salt-minion[2824]: -#ceilometer_control_exchange = ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name of this node, which must be valid in an AMQP key. Can be an opaque
May  9 23:38:23 cmp02 salt-minion[2824]: -# identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP address.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (unknown value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#host = <your_hostname>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Timeout seconds for HTTP requests. Set it to None to disable timeout.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#http_timeout = 600
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum number of parallel requests for services to handle at the same time.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -#max_parallel_requests = 64
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.log
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If set to true, the logging level will be set to DEBUG instead of the default
May  9 23:38:23 cmp02 salt-minion[2824]: -# INFO level. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Note: This option can be changed without restarting.
May  9 23:38:23 cmp02 salt-minion[2824]: -#debug = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The name of a logging configuration file. This file is appended to any
May  9 23:38:23 cmp02 salt-minion[2824]: -# existing logging configuration files. For details about logging configuration
May  9 23:38:23 cmp02 salt-minion[2824]: -# files, see the Python logging module documentation. Note that when logging
May  9 23:38:23 cmp02 salt-minion[2824]: -# configuration files are used then all logging configuration is set in the
May  9 23:38:23 cmp02 salt-minion[2824]: -# configuration file and other logging configuration options are ignored (for
May  9 23:38:23 cmp02 salt-minion[2824]: -# example, logging_context_format_string). (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Note: This option can be changed without restarting.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/log_config
May  9 23:38:23 cmp02 salt-minion[2824]: -#log_config_append = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Defines the format string for %%(asctime)s in log records. Default:
May  9 23:38:23 cmp02 salt-minion[2824]: -# %(default)s . This option is ignored if log_config_append is set. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#log_date_format = %Y-%m-%d %H:%M:%S
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Name of log file to send logging output to. If no default is set,
May  9 23:38:23 cmp02 salt-minion[2824]: -# logging will go to stderr as defined by use_stderr. This option is ignored if
May  9 23:38:23 cmp02 salt-minion[2824]: -# log_config_append is set. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/logfile
May  9 23:38:23 cmp02 salt-minion[2824]: -#log_file = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) The base directory used for relative log_file  paths. This option
May  9 23:38:23 cmp02 salt-minion[2824]: -# is ignored if log_config_append is set. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/logdir
May  9 23:38:23 cmp02 salt-minion[2824]: -#log_dir = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Uses logging handler designed to watch file system. When log file is moved or
May  9 23:38:23 cmp02 salt-minion[2824]: -# removed this handler will open a new log file with specified path
May  9 23:38:23 cmp02 salt-minion[2824]: -# instantaneously. It makes sense only if log_file option is specified and
May  9 23:38:23 cmp02 salt-minion[2824]: -# Linux platform is used. This option is ignored if log_config_append is set.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#watch_log_file = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Use syslog for logging. Existing syslog format is DEPRECATED and will be
May  9 23:38:23 cmp02 salt-minion[2824]: -# changed later to honor RFC5424. This option is ignored if log_config_append
May  9 23:38:23 cmp02 salt-minion[2824]: -# is set. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_syslog = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enable journald for logging. If running in a systemd environment you may wish
May  9 23:38:23 cmp02 salt-minion[2824]: -# to enable journal support. Doing so will use the journal native protocol
May  9 23:38:23 cmp02 salt-minion[2824]: -# which includes structured metadata in addition to log messages.This option is
May  9 23:38:23 cmp02 salt-minion[2824]: -# ignored if log_config_append is set. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_journal = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Syslog facility to receive log lines. This option is ignored if
May  9 23:38:23 cmp02 salt-minion[2824]: -# log_config_append is set. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#syslog_log_facility = LOG_USER
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Log output to standard error. This option is ignored if log_config_append is
May  9 23:38:23 cmp02 salt-minion[2824]: -# set. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_stderr = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Format string to use for log messages with context. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Format string to use for log messages when context is undefined. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Additional data to append to log message when logging level for the message
May  9 23:38:23 cmp02 salt-minion[2824]: -# is DEBUG. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Prefix each line of exception output with this format. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Defines the format string for %(user_identity)s that is used in
May  9 23:38:23 cmp02 salt-minion[2824]: -# logging_context_format_string. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#logging_user_identity_format = %(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)s
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# List of package logging levels in logger=LEVEL pairs. This option is ignored
May  9 23:38:23 cmp02 salt-minion[2824]: -# if log_config_append is set. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#default_log_levels = amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=INFO,oslo.messaging=INFO,oslo_messaging=INFO,iso8601=WARN,requests.packages.urllib3.connectionpool=WARN,urllib3.connectionpool=WARN,websocket=WARN,requests.packages.urllib3.util.retry=WARN,urllib3.util.retry=WARN,keystonemiddleware=WARN,routes.middleware=WARN,stevedore=WARN,taskflow=WARN,keystoneauth=WARN,oslo.cache=INFO,dogpile.core.dogpile=INFO
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enables or disables publication of error events. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#publish_errors = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The format for an instance that is passed with the log message. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#instance_format = "[instance: %(uuid)s] "
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The format for an instance UUID that is passed with the log message. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#instance_uuid_format = "[instance: %(uuid)s] "
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Interval, number of seconds, of log rate limiting. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rate_limit_interval = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum number of logged messages per rate_limit_interval. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rate_limit_burst = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG
May  9 23:38:23 cmp02 salt-minion[2824]: -# or empty string. Logs with level greater or equal to rate_limit_except_level
May  9 23:38:23 cmp02 salt-minion[2824]: -# are not filtered. An empty string means that all levels are filtered. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rate_limit_except_level = CRITICAL
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enables or disables fatal status of deprecations. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#fatal_deprecations = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Size of RPC connection pool. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_conn_pool_size = 30
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The pool size limit for connections expiration policy (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#conn_pool_min_size = 2
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The time-to-live in sec of idle connections in the pool (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#conn_pool_ttl = 1200
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP.
May  9 23:38:23 cmp02 salt-minion[2824]: -# The "host" option should point or resolve to this address. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_bind_address = *
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# MatchMaker driver. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: redis, sentinel, dummy
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_matchmaker = redis
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of ZeroMQ contexts, defaults to 1. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_contexts = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum number of ingress messages to locally buffer per topic. Default is
May  9 23:38:23 cmp02 salt-minion[2824]: -# unlimited. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_topic_backlog = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Directory for holding IPC sockets. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_ipc_dir = /var/run/openstack
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name of this node. Must be a valid hostname, FQDN, or IP address. Must match
May  9 23:38:23 cmp02 salt-minion[2824]: -# "host" option, if running Nova. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_host = localhost
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds to wait before all pending messages will be sent after
May  9 23:38:23 cmp02 salt-minion[2824]: -# closing a socket. The default value of -1 specifies an infinite linger
May  9 23:38:23 cmp02 salt-minion[2824]: -# period. The value of 0 specifies no linger period. Pending messages shall be
May  9 23:38:23 cmp02 salt-minion[2824]: -# discarded immediately when the socket is closed. Positive values specify an
May  9 23:38:23 cmp02 salt-minion[2824]: -# upper bound for the linger period. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/rpc_cast_timeout
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_linger = -1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The default number of seconds that poll should wait. Poll raises timeout
May  9 23:38:23 cmp02 salt-minion[2824]: -# exception when timeout expired. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_poll_timeout = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Expiration timeout in seconds of a name service record about existing target
May  9 23:38:23 cmp02 salt-minion[2824]: -# ( < 0 means no timeout). (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_target_expire = 300
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Update period in seconds of a name service record about existing target.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_target_update = 180
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. (boolean
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_pub_sub = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Use ROUTER remote proxy. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_router_proxy = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option makes direct connections dynamic or static. It makes sense only
May  9 23:38:23 cmp02 salt-minion[2824]: -# with use_router_proxy=False which means to use direct connections for direct
May  9 23:38:23 cmp02 salt-minion[2824]: -# message types (ignored otherwise). (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_dynamic_connections = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# How many additional connections to a host will be made for failover reasons.
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is actual only in dynamic connections mode. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_failover_connections = 2
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimal port number for random ports range. (port value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_min_port = 49153
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximal port number for random ports range. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum value: 65536
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_max_port = 65536
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of retries to find free port number before fail with ZMQBindError.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_bind_port_retries = 100
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Default serialization mechanism for serializing/deserializing
May  9 23:38:23 cmp02 salt-minion[2824]: -# outgoing/incoming messages (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: json, msgpack
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_zmq_serialization = json
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option configures round-robin mode in zmq socket. True means not keeping
May  9 23:38:23 cmp02 salt-minion[2824]: -# a queue when server side disconnects. False means to keep queue and messages
May  9 23:38:23 cmp02 salt-minion[2824]: -# even if server is disconnected, when the server appears we send all
May  9 23:38:23 cmp02 salt-minion[2824]: -# accumulated messages to it. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_immediate = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any
May  9 23:38:23 cmp02 salt-minion[2824]: -# other negative value) means to skip any overrides and leave it to OS default;
May  9 23:38:23 cmp02 salt-minion[2824]: -# 0 and 1 (or any other positive value) mean to disable and enable the option
May  9 23:38:23 cmp02 salt-minion[2824]: -# respectively. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive = -1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The duration between two keepalive transmissions in idle condition. The unit
May  9 23:38:23 cmp02 salt-minion[2824]: -# is platform dependent, for example, seconds in Linux, milliseconds in Windows
May  9 23:38:23 cmp02 salt-minion[2824]: -# etc. The default value of -1 (or any other negative value and 0) means to
May  9 23:38:23 cmp02 salt-minion[2824]: -# skip any overrides and leave it to OS default. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_idle = -1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The number of retransmissions to be carried out before declaring that remote
May  9 23:38:23 cmp02 salt-minion[2824]: -# end is not available. The default value of -1 (or any other negative value
May  9 23:38:23 cmp02 salt-minion[2824]: -# and 0) means to skip any overrides and leave it to OS default. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_cnt = -1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The duration between two successive keepalive retransmissions, if
May  9 23:38:23 cmp02 salt-minion[2824]: -# acknowledgement to the previous keepalive transmission is not received. The
May  9 23:38:23 cmp02 salt-minion[2824]: -# unit is platform dependent, for example, seconds in Linux, milliseconds in
May  9 23:38:23 cmp02 salt-minion[2824]: -# Windows etc. The default value of -1 (or any other negative value and 0)
May  9 23:38:23 cmp02 salt-minion[2824]: -# means to skip any overrides and leave it to OS default. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_intvl = -1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum number of (green) threads to work concurrently. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_thread_pool_size = 100
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Expiration timeout in seconds of a sent/received message after which it is
May  9 23:38:23 cmp02 salt-minion[2824]: -# not tracked anymore by a client/server. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_message_ttl = 300
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Wait for message acknowledgements from receivers. This mechanism works only
May  9 23:38:23 cmp02 salt-minion[2824]: -# via proxy without PUB/SUB. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_use_acks = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds to wait for an ack from a cast/call. After each retry
May  9 23:38:23 cmp02 salt-minion[2824]: -# attempt this timeout is multiplied by some specified multiplier. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_ack_timeout_base = 15
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number to multiply base ack timeout by after each retry attempt. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_ack_timeout_multiplier = 2
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Default number of message sending attempts in case of any problems occurred:
May  9 23:38:23 cmp02 salt-minion[2824]: -# positive value N means at most N retries, 0 means no retries, None or -1 (or
May  9 23:38:23 cmp02 salt-minion[2824]: -# any other negative values) mean to retry forever. This option is used only if
May  9 23:38:23 cmp02 salt-minion[2824]: -# acknowledgments are enabled. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_retry_attempts = 3
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# List of publisher hosts SubConsumer can subscribe on. This option has higher
May  9 23:38:23 cmp02 salt-minion[2824]: -# priority then the default publishers list taken from the matchmaker. (list
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#subscribe_on =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Size of executor thread pool when executor is threading or eventlet. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/rpc_thread_pool_size
May  9 23:38:23 cmp02 salt-minion[2824]: -#executor_thread_pool_size = 64
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Seconds to wait for a response from a call. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_response_timeout = 60
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# A URL representing the messaging driver to use and its full configuration.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#transport_url = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: The messaging driver to use, defaults to rabbit. Other drivers
May  9 23:38:23 cmp02 salt-minion[2824]: -# include amqp and zmq. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:23 cmp02 salt-minion[2824]: -#rpc_backend = rabbit
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The default exchange under which topics are scoped. May be overridden by an
May  9 23:38:23 cmp02 salt-minion[2824]: -# exchange name specified in the transport_url option. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#control_exchange = openstack
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.service.service
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enable eventlet backdoor.  Acceptable values are 0, <port>, and
May  9 23:38:23 cmp02 salt-minion[2824]: -# <start>:<end>, where 0 results in listening on a random tcp port number;
May  9 23:38:23 cmp02 salt-minion[2824]: -# <port> results in listening on the specified port number (and not enabling
May  9 23:38:23 cmp02 salt-minion[2824]: -# backdoor if that port is in use); and <start>:<end> results in listening on
May  9 23:38:23 cmp02 salt-minion[2824]: -# the smallest unused port number within the specified range of port numbers.
May  9 23:38:23 cmp02 salt-minion[2824]: -# The chosen port is displayed in the service's log file. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#backdoor_port = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enable eventlet backdoor, using the provided path as a unix socket that can
May  9 23:38:23 cmp02 salt-minion[2824]: -# receive connections. This option is mutually exclusive with 'backdoor_port'
May  9 23:38:23 cmp02 salt-minion[2824]: -# in that only one should be provided. If both are provided then the existence
May  9 23:38:23 cmp02 salt-minion[2824]: -# of this option overrides the usage of that option. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#backdoor_socket = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enables or disables logging values of all registered options when starting a
May  9 23:38:23 cmp02 salt-minion[2824]: -# service (at DEBUG level). (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#log_options = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Specify a timeout after which a gracefully shutdown server will exit. Zero
May  9 23:38:23 cmp02 salt-minion[2824]: -# value means endless wait. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#graceful_shutdown_timeout = 60
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[api]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Default maximum number of items returned by API request. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -#default_api_return_limit = 100
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Set True to disable resource/meter/sample URLs. Default autodetection by
May  9 23:38:23 cmp02 salt-minion[2824]: -# querying keystone. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#gnocchi_is_enabled = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Set True to redirect alarms URLs to aodh. Default autodetection by querying
May  9 23:38:23 cmp02 salt-minion[2824]: -# keystone. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#aodh_is_enabled = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The endpoint of Aodh to redirect alarms URLs to Aodh API. Default
May  9 23:38:23 cmp02 salt-minion[2824]: -# autodetection by querying keystone. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#aodh_url = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Set True to redirect events URLs to Panko. Default autodetection by querying
May  9 23:38:23 cmp02 salt-minion[2824]: -# keystone. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#panko_is_enabled = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The endpoint of Panko to redirect events URLs to Panko API. Default
May  9 23:38:23 cmp02 salt-minion[2824]: -# autodetection by querying keystone. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#panko_url = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[collector]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Address to which the UDP socket is bound. Set to an empty string to disable.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (unknown value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#udp_address = 0.0.0.0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Port to which the UDP socket is bound. (port value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:23 cmp02 salt-minion[2824]: -#udp_port = 4952
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of notification messages to wait before dispatching them (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#batch_size = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds to wait before dispatching samples when batch_size is not
May  9 23:38:23 cmp02 salt-minion[2824]: -# reached (None means indefinitely) (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#batch_timeout = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of workers for collector service. default value is 1. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/collector_workers
May  9 23:38:23 cmp02 salt-minion[2824]: -#workers = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: +executor_thread_pool_size = 5
May  9 23:38:23 cmp02 salt-minion[2824]: +transport_url = rabbit://openstack:opnfv_secret@172.16.10.36:5672,openstack:opnfv_secret@172.16.10.37:5672,openstack:opnfv_secret@172.16.10.38:5672//openstack
May  9 23:38:23 cmp02 salt-minion[2824]:  
May  9 23:38:23 cmp02 salt-minion[2824]:  [compute]
May  9 23:38:23 cmp02 salt-minion[2824]:  
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Enable work-load partitioning, allowing multiple compute agents
May  9 23:38:23 cmp02 salt-minion[2824]: -# to be run simultaneously. (replaced by instance_discovery_method) (boolean
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -#workload_partitioning = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Ceilometer offers many methods to discover the instance running on a compute
May  9 23:38:23 cmp02 salt-minion[2824]: -# node:
May  9 23:38:23 cmp02 salt-minion[2824]: -# * naive: poll nova to get all instances
May  9 23:38:23 cmp02 salt-minion[2824]: -# * workload_partitioning: poll nova to get instances of the compute
May  9 23:38:23 cmp02 salt-minion[2824]: -# * libvirt_metadata: get instances from libvirt metadata   but without
May  9 23:38:23 cmp02 salt-minion[2824]: -# instance metadata (recommended for Gnocchi   backend (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: naive, workload_partitioning, libvirt_metadata
May  9 23:38:23 cmp02 salt-minion[2824]: -#instance_discovery_method = libvirt_metadata
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# New instances will be discovered periodically based on this option (in
May  9 23:38:23 cmp02 salt-minion[2824]: -# seconds). By default, the agent discovers instances according to pipeline
May  9 23:38:23 cmp02 salt-minion[2824]: -# polling interval. If option is greater than 0, the instance list to poll will
May  9 23:38:23 cmp02 salt-minion[2824]: -# be updated based on this option's interval. Measurements relating to the
May  9 23:38:23 cmp02 salt-minion[2824]: -# instances will match intervals defined in pipeline.  (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -#resource_update_interval = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The expiry to totally refresh the instances resource cache, since the
May  9 23:38:23 cmp02 salt-minion[2824]: -# instance may be migrated to another host, we need to clean the legacy
May  9 23:38:23 cmp02 salt-minion[2824]: -# instances info in local cache by totally refreshing the local cache. The
May  9 23:38:23 cmp02 salt-minion[2824]: -# minimum should be the value of the config option of resource_update_interval.
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is only used for agent polling to Nova API, so it will works only
May  9 23:38:23 cmp02 salt-minion[2824]: -# when 'instance_discovery_method' was set to 'naive'. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -#resource_cache_expiry = 3600
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[coordination]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The backend URL to use for distributed coordination. If left empty, per-
May  9 23:38:23 cmp02 salt-minion[2824]: -# deployment central agent and per-host compute agent won't do workload
May  9 23:38:23 cmp02 salt-minion[2824]: -# partitioning and will only function correctly if a single instance of that
May  9 23:38:23 cmp02 salt-minion[2824]: -# service is running. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#backend_url = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds between checks to see if group membership has changed
May  9 23:38:23 cmp02 salt-minion[2824]: -# (floating point value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#check_watchers = 10.0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[cors]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.middleware.cors
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicate whether this resource may be shared with the domain received in the
May  9 23:38:23 cmp02 salt-minion[2824]: -# requests "origin" header. Format: "<protocol>://<host>[:<port>]", no trailing
May  9 23:38:23 cmp02 salt-minion[2824]: -# slash. Example: https://horizon.example.com (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#allowed_origin = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicate that the actual request can include user credentials (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#allow_credentials = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicate which headers are safe to expose to the API. Defaults to HTTP Simple
May  9 23:38:23 cmp02 salt-minion[2824]: -# Headers. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#expose_headers = X-Auth-Token,X-Subject-Token,X-Service-Token,X-Openstack-Request-Id
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum cache age of CORS preflight requests. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#max_age = 3600
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicate which methods can be used during the actual request. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#allow_methods = GET,PUT,POST,DELETE,PATCH
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicate which header field names may be used during the actual request.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#allow_headers = X-Auth-Token,X-Identity-Status,X-Roles,X-Service-Catalog,X-User-Id,X-Tenant-Id,X-Openstack-Request-Id
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[database]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds that samples are kept in the database for (<= 0 means
May  9 23:38:23 cmp02 salt-minion[2824]: -# forever). (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [database]/time_to_live
May  9 23:38:23 cmp02 salt-minion[2824]: -#metering_time_to_live = -1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The connection string used to connect to the metering database. (if unset,
May  9 23:38:23 cmp02 salt-minion[2824]: -# connection is used) (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#metering_connection = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicates if expirer expires only samples. If set true, expired samples will
May  9 23:38:23 cmp02 salt-minion[2824]: -# be deleted, but residual resource and meter definition data will remain.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sql_expire_samples_only = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.db
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If True, SQLite uses synchronous mode. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sqlite_synchronous = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The back end to use for the database. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/db_backend
May  9 23:38:23 cmp02 salt-minion[2824]: -#backend = sqlalchemy
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The SQLAlchemy connection string to use to connect to the database. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_connection
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sql_connection
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [sql]/connection
May  9 23:38:23 cmp02 salt-minion[2824]: -#connection = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The SQLAlchemy connection string to use to connect to the slave database.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#slave_connection = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The SQL mode to be used for MySQL sessions. This option, including the
May  9 23:38:23 cmp02 salt-minion[2824]: -# default, overrides any server-set SQL mode. To use whatever SQL mode is set
May  9 23:38:23 cmp02 salt-minion[2824]: -# by the server configuration, set this to no value. Example: mysql_sql_mode=
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#mysql_sql_mode = TRADITIONAL
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If True, transparently enables support for handling MySQL Cluster (NDB).
May  9 23:38:23 cmp02 salt-minion[2824]: -# (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#mysql_enable_ndb = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Timeout before idle SQL connections are reaped. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_idle_timeout
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sql_idle_timeout
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [sql]/idle_timeout
May  9 23:38:23 cmp02 salt-minion[2824]: -#idle_timeout = 3600
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum number of SQL connections to keep open in a pool. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_min_pool_size
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sql_min_pool_size
May  9 23:38:23 cmp02 salt-minion[2824]: -#min_pool_size = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum number of SQL connections to keep open in a pool. Setting a value of
May  9 23:38:23 cmp02 salt-minion[2824]: -# 0 indicates no limit. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_max_pool_size
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sql_max_pool_size
May  9 23:38:23 cmp02 salt-minion[2824]: -#max_pool_size = 5
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum number of database connection retries during startup. Set to -1 to
May  9 23:38:23 cmp02 salt-minion[2824]: -# specify an infinite retry count. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_max_retries
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sql_max_retries
May  9 23:38:23 cmp02 salt-minion[2824]: -#max_retries = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Interval between retries of opening a SQL connection. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_retry_interval
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/reconnect_interval
May  9 23:38:23 cmp02 salt-minion[2824]: -#retry_interval = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If set, use this value for max_overflow with SQLAlchemy. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_max_overflow
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sqlalchemy_max_overflow
May  9 23:38:23 cmp02 salt-minion[2824]: -#max_overflow = 50
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Verbosity of SQL debugging information: 0=None, 100=Everything. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum value: 100
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_connection_debug
May  9 23:38:23 cmp02 salt-minion[2824]: -#connection_debug = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Add Python stack traces to SQL as comment strings. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/sql_connection_trace
May  9 23:38:23 cmp02 salt-minion[2824]: -#connection_trace = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If set, use this value for pool_timeout with SQLAlchemy. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DATABASE]/sqlalchemy_pool_timeout
May  9 23:38:23 cmp02 salt-minion[2824]: -#pool_timeout = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enable the experimental use of database reconnect on connection lost.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#use_db_reconnect = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Seconds between retries of a database transaction. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#db_retry_interval = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If True, increases the interval between retries of a database operation up to
May  9 23:38:23 cmp02 salt-minion[2824]: -# db_max_retry_interval. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#db_inc_retry_interval = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# If db_inc_retry_interval is set, the maximum seconds between retries of a
May  9 23:38:23 cmp02 salt-minion[2824]: -# database operation. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#db_max_retry_interval = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum retries in case of connection error or deadlock error before error is
May  9 23:38:23 cmp02 salt-minion[2824]: -# raised. Set to -1 to specify an infinite retry count. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#db_max_retries = 20
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[dispatcher_file]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name and the location of the file to record meters. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#file_path = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The max size of the file. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#max_bytes = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The max number of the files to keep. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#backup_count = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[dispatcher_gnocchi]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Filter out samples generated by Gnocchi service activity (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#filter_service_activity = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Gnocchi project used to filter out samples generated by Gnocchi service
May  9 23:38:23 cmp02 salt-minion[2824]: -# activity (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#filter_project = gnocchi
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The archive policy to use when the dispatcher create a new metric. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#archive_policy = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The Yaml file that defines mapping between samples and gnocchi
May  9 23:38:23 cmp02 salt-minion[2824]: -# resources/metrics (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#resources_definition_file = gnocchi_resources.yaml
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds before request to gnocchi times out (floating point value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -#request_timeout = 6.05
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[dispatcher_http]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The target where the http request will be sent. If this is not set, no data
May  9 23:38:23 cmp02 salt-minion[2824]: -# will be posted. For example: target = http://hostname:1234/path (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#target =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The target for event data where the http request will be sent to. If this is
May  9 23:38:23 cmp02 salt-minion[2824]: -# not set, it will default to same as Sample target. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#event_target = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The max time in seconds to wait for a request to timeout. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#timeout = 5
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The path to a server certificate or directory if the system CAs are not used
May  9 23:38:23 cmp02 salt-minion[2824]: -# or if a self-signed certificate is used. Set to False to ignore SSL cert
May  9 23:38:23 cmp02 salt-minion[2824]: -# verification. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#verify_ssl = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Indicates whether samples are published in a batch. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#batch_mode = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[event]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Configuration file for event definitions. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#definitions_cfg_file = event_definitions.yaml
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Drop notifications if no event definition matches. (Otherwise, we convert
May  9 23:38:23 cmp02 salt-minion[2824]: -# them with just the default traits) (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#drop_unmatched_notifications = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Store the raw notification for select priority levels (info and/or error). By
May  9 23:38:23 cmp02 salt-minion[2824]: -# default, raw details are not captured. (multi valued)
May  9 23:38:23 cmp02 salt-minion[2824]: -#store_raw =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[hardware]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# URL scheme to use for hardware nodes. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#url_scheme = snmp://
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# SNMPd user name of all nodes running in the cloud. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#readonly_user_name = ro_snmp_user
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# SNMPd v3 authentication password of all the nodes running in the cloud.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#readonly_user_password = password
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# SNMPd v3 authentication algorithm of all the nodes running in the cloud
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: md5, sha
May  9 23:38:23 cmp02 salt-minion[2824]: -#readonly_user_auth_proto = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# SNMPd v3 encryption algorithm of all the nodes running in the cloud (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: des, aes128, 3des, aes192, aes256
May  9 23:38:23 cmp02 salt-minion[2824]: -#readonly_user_priv_proto = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# SNMPd v3 encryption password of all the nodes running in the cloud. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#readonly_user_priv_password = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name of the control plane Tripleo network (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#tripleo_network_name = ctlplane
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Configuration file for defining hardware snmp meters. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#meter_definitions_file = snmp.yaml
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[ipmi]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of retries upon Intel Node Manager initialization failure (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#node_manager_init_retry = 3
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Tolerance of IPMI/NM polling failures before disable this pollster. Negative
May  9 23:38:23 cmp02 salt-minion[2824]: -# indicates retrying forever. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#polling_retry = 3
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: +instance_discovery_method = libvirt_metadata
May  9 23:38:23 cmp02 salt-minion[2824]:  
May  9 23:38:23 cmp02 salt-minion[2824]:  [keystone_authtoken]
May  9 23:38:23 cmp02 salt-minion[2824]:  
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From keystonemiddleware.auth_token
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Complete "public" Identity API endpoint. This endpoint should not be an
May  9 23:38:23 cmp02 salt-minion[2824]: -# "admin" endpoint, as it should be accessible by all end users.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Unauthenticated clients are redirected to this endpoint to authenticate.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Although this endpoint should ideally be unversioned, client support in the
May  9 23:38:23 cmp02 salt-minion[2824]: -# wild varies. If you're using a versioned v2 endpoint here, then this should
May  9 23:38:23 cmp02 salt-minion[2824]: -# *not* be the same endpoint the service user utilizes for validating tokens,
May  9 23:38:23 cmp02 salt-minion[2824]: -# because normal end users may not be able to reach that endpoint. (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_uri = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# API version of the admin Identity API endpoint. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_version = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Do not handle authorization requests within the middleware, but delegate the
May  9 23:38:23 cmp02 salt-minion[2824]: -# authorization decision to downstream WSGI components. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#delay_auth_decision = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Request timeout value for communicating with Identity API server. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#http_connect_timeout = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# How many times are we trying to reconnect when communicating with Identity
May  9 23:38:23 cmp02 salt-minion[2824]: -# API Server. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#http_request_max_retries = 3
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Request environment key where the Swift cache object is stored. When
May  9 23:38:23 cmp02 salt-minion[2824]: -# auth_token middleware is deployed with a Swift cache, use this option to have
May  9 23:38:23 cmp02 salt-minion[2824]: -# the middleware share a caching backend with swift. Otherwise, use the
May  9 23:38:23 cmp02 salt-minion[2824]: -# ``memcached_servers`` option instead. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#cache = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Required if identity server requires client certificate (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#certfile = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Required if identity server requires client certificate (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#keyfile = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# A PEM encoded Certificate Authority to use when verifying HTTPs connections.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Defaults to system CAs. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#cafile = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Verify HTTPS connections. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#insecure = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# The region in which the identity server can be found. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#region_name = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Directory used to cache files related to PKI tokens. This option
May  9 23:38:23 cmp02 salt-minion[2824]: -# has been deprecated in the Ocata release and will be removed in the P
May  9 23:38:23 cmp02 salt-minion[2824]: -# release. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal since Ocata.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: PKI token format is no longer supported.
May  9 23:38:23 cmp02 salt-minion[2824]: -#signing_dir = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Optionally specify a list of memcached server(s) to use for caching. If left
May  9 23:38:23 cmp02 salt-minion[2824]: -# undefined, tokens will instead be cached in-process. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [keystone_authtoken]/memcache_servers
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcached_servers = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# In order to prevent excessive effort spent validating tokens, the middleware
May  9 23:38:23 cmp02 salt-minion[2824]: -# caches previously-seen tokens for a configurable duration (in seconds). Set
May  9 23:38:23 cmp02 salt-minion[2824]: -# to -1 to disable caching completely. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#token_cache_time = 300
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Determines the frequency at which the list of revoked tokens is
May  9 23:38:23 cmp02 salt-minion[2824]: -# retrieved from the Identity service (in seconds). A high number of revocation
May  9 23:38:23 cmp02 salt-minion[2824]: -# events combined with a low cache duration may significantly reduce
May  9 23:38:23 cmp02 salt-minion[2824]: -# performance. Only valid for PKI tokens. This option has been deprecated in
May  9 23:38:23 cmp02 salt-minion[2824]: -# the Ocata release and will be removed in the P release. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal since Ocata.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: PKI token format is no longer supported.
May  9 23:38:23 cmp02 salt-minion[2824]: -#revocation_cache_time = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) If defined, indicate whether token data should be authenticated or
May  9 23:38:23 cmp02 salt-minion[2824]: -# authenticated and encrypted. If MAC, token data is authenticated (with HMAC)
May  9 23:38:23 cmp02 salt-minion[2824]: -# in the cache. If ENCRYPT, token data is encrypted and authenticated in the
May  9 23:38:23 cmp02 salt-minion[2824]: -# cache. If the value is not one of these options or empty, auth_token will
May  9 23:38:23 cmp02 salt-minion[2824]: -# raise an exception on initialization. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: None, MAC, ENCRYPT
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_security_strategy = None
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional, mandatory if memcache_security_strategy is defined) This string is
May  9 23:38:23 cmp02 salt-minion[2824]: -# used for key derivation. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_secret_key = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Number of seconds memcached server is considered dead before it is
May  9 23:38:23 cmp02 salt-minion[2824]: -# tried again. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_pool_dead_retry = 300
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Maximum total number of open connections to every memcached
May  9 23:38:23 cmp02 salt-minion[2824]: -# server. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_pool_maxsize = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Socket timeout in seconds for communicating with a memcached
May  9 23:38:23 cmp02 salt-minion[2824]: -# server. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_pool_socket_timeout = 3
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Number of seconds a connection to memcached is held unused in the
May  9 23:38:23 cmp02 salt-minion[2824]: -# pool before it is closed. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_pool_unused_timeout = 60
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Number of seconds that an operation will wait to get a memcached
May  9 23:38:23 cmp02 salt-minion[2824]: -# client connection from the pool. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_pool_conn_get_timeout = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Use the advanced (eventlet safe) memcached client pool. The
May  9 23:38:23 cmp02 salt-minion[2824]: -# advanced pool will only work under python 2.x. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#memcache_use_advanced_pool = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# (Optional) Indicate whether to set the X-Service-Catalog header. If False,
May  9 23:38:23 cmp02 salt-minion[2824]: -# middleware will not ask for service catalog on token validation and will not
May  9 23:38:23 cmp02 salt-minion[2824]: -# set the X-Service-Catalog header. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#include_service_catalog = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Used to control the use and type of token binding. Can be set to: "disabled"
May  9 23:38:23 cmp02 salt-minion[2824]: -# to not check token binding. "permissive" (default) to validate binding
May  9 23:38:23 cmp02 salt-minion[2824]: -# information if the bind type is of a form known to the server and ignore it
May  9 23:38:23 cmp02 salt-minion[2824]: -# if not. "strict" like "permissive" but if the bind type is unknown the token
May  9 23:38:23 cmp02 salt-minion[2824]: -# will be rejected. "required" any form of token binding is needed to be
May  9 23:38:23 cmp02 salt-minion[2824]: -# allowed. Finally the name of a binding method that must be present in tokens.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#enforce_token_bind = permissive
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: If true, the revocation list will be checked for cached tokens.
May  9 23:38:23 cmp02 salt-minion[2824]: -# This requires that PKI tokens are configured on the identity server. (boolean
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal since Ocata.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: PKI token format is no longer supported.
May  9 23:38:23 cmp02 salt-minion[2824]: -#check_revocations_for_cached = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Hash algorithms to use for hashing PKI tokens. This may be a
May  9 23:38:23 cmp02 salt-minion[2824]: -# single algorithm or multiple. The algorithms are those supported by Python
May  9 23:38:23 cmp02 salt-minion[2824]: -# standard hashlib.new(). The hashes will be tried in the order given, so put
May  9 23:38:23 cmp02 salt-minion[2824]: -# the preferred one first for performance. The result of the first hash will be
May  9 23:38:23 cmp02 salt-minion[2824]: -# stored in the cache. This will typically be set to multiple values only while
May  9 23:38:23 cmp02 salt-minion[2824]: -# migrating from a less secure algorithm to a more secure one. Once all the old
May  9 23:38:23 cmp02 salt-minion[2824]: -# tokens are expired this option should be set to a single value for better
May  9 23:38:23 cmp02 salt-minion[2824]: -# performance. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal since Ocata.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: PKI token format is no longer supported.
May  9 23:38:23 cmp02 salt-minion[2824]: -#hash_algorithms = md5
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# A choice of roles that must be present in a service token. Service tokens are
May  9 23:38:23 cmp02 salt-minion[2824]: -# allowed to request that an expired token can be used and so this check should
May  9 23:38:23 cmp02 salt-minion[2824]: -# tightly control that only actual services should be sending this token. Roles
May  9 23:38:23 cmp02 salt-minion[2824]: -# here are applied as an ANY check so any role in this list must be present.
May  9 23:38:23 cmp02 salt-minion[2824]: -# For backwards compatibility reasons this currently only affects the
May  9 23:38:23 cmp02 salt-minion[2824]: -# allow_expired check. (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#service_token_roles = service
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# For backwards compatibility reasons we must let valid service tokens pass
May  9 23:38:23 cmp02 salt-minion[2824]: -# that don't pass the service_token_roles check as valid. Setting this true
May  9 23:38:23 cmp02 salt-minion[2824]: -# will become the default in a future release and should be enabled if
May  9 23:38:23 cmp02 salt-minion[2824]: -# possible. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#service_token_roles_required = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Prefix to prepend at the beginning of the path. Deprecated, use identity_uri.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_admin_prefix =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Host providing the admin Identity API endpoint. Deprecated, use identity_uri.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_host = 127.0.0.1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Port of the admin Identity API endpoint. Deprecated, use identity_uri.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_port = 35357
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Protocol of the admin Identity API endpoint. Deprecated, use identity_uri.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Allowed values: http, https
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_protocol = https
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Complete admin Identity API endpoint. This should specify the unversioned
May  9 23:38:23 cmp02 salt-minion[2824]: -# root endpoint e.g. https://localhost:35357/ (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#identity_uri = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated and may be removed in a future release. Single
May  9 23:38:23 cmp02 salt-minion[2824]: -# shared secret with the Keystone configuration used for bootstrapping a
May  9 23:38:23 cmp02 salt-minion[2824]: -# Keystone installation, or otherwise bypassing the normal authentication
May  9 23:38:23 cmp02 salt-minion[2824]: -# process. This option should not be used, use `admin_user` and
May  9 23:38:23 cmp02 salt-minion[2824]: -# `admin_password` instead. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#admin_token = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Service username. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#admin_user = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Service user password. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#admin_password = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Service tenant name. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#admin_tenant_name = admin
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Authentication type to load (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [keystone_authtoken]/auth_plugin
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_type = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Config Section from which to load plugin specific options (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#auth_section = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[matchmaker_redis]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Host to locate redis. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:23 cmp02 salt-minion[2824]: -#host = 127.0.0.1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Use this port to connect to redis host. (port value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:23 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:23 cmp02 salt-minion[2824]: -#port = 6379
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Password for Redis server (optional). (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:23 cmp02 salt-minion[2824]: -#password =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: List of Redis Sentinel hosts (fault tolerance mode), e.g.,
May  9 23:38:23 cmp02 salt-minion[2824]: -# [host:port, host1:port ... ] (list value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:23 cmp02 salt-minion[2824]: -#sentinel_hosts =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Redis replica set name. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sentinel_group_name = oslo-messaging-zeromq
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Time in ms to wait between connection attempts. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#wait_timeout = 2000
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Time in ms to wait before the transaction is killed. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#check_timeout = 20000
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Timeout in ms on blocking socket operations. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#socket_timeout = 10000
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[meter]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Configuration file for defining meter notifications. This option
May  9 23:38:23 cmp02 salt-minion[2824]: -# is deprecated and use meter_definitions_dirs to configure meter notification
May  9 23:38:23 cmp02 salt-minion[2824]: -# file. Meter definitions configuration file will be sought according to the
May  9 23:38:23 cmp02 salt-minion[2824]: -# parameter. (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -#meter_definitions_cfg_file = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# List directory to find files of defining meter notifications. (multi valued)
May  9 23:38:23 cmp02 salt-minion[2824]: -#meter_definitions_dirs = /etc/ceilometer/meters.d
May  9 23:38:23 cmp02 salt-minion[2824]: -#meter_definitions_dirs = /build/ceilometer-H68fek/ceilometer-9.0.5/ceilometer/data/meters.d
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[notification]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of queues to parallelize workload across. This value should be larger
May  9 23:38:23 cmp02 salt-minion[2824]: -# than the number of active notification agents for optimal results. WARNING:
May  9 23:38:23 cmp02 salt-minion[2824]: -# Once set, lowering this value may result in lost data. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -#pipeline_processing_queues = 10
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Acknowledge message when event persistence fails. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ack_on_event_error = true
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enable workload partitioning, allowing multiple notification agents to be run
May  9 23:38:23 cmp02 salt-minion[2824]: -# simultaneously. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#workload_partitioning = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Messaging URLs to listen for notifications. Example:
May  9 23:38:23 cmp02 salt-minion[2824]: -# rabbit://user:pass@host1:port1[,user:pass@hostN:portN]/virtual_host
May  9 23:38:23 cmp02 salt-minion[2824]: -# (DEFAULT/transport_url is used if empty). This is useful when you have
May  9 23:38:23 cmp02 salt-minion[2824]: -# dedicate messaging nodes for each service, for example, all nova
May  9 23:38:23 cmp02 salt-minion[2824]: -# notifications go to rabbit-nova:5672, while all cinder notifications go to
May  9 23:38:23 cmp02 salt-minion[2824]: -# rabbit-cinder:5672. (multi valued)
May  9 23:38:23 cmp02 salt-minion[2824]: -#messaging_urls =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of notification messages to wait before publishing them. Batching is
May  9 23:38:23 cmp02 salt-minion[2824]: -# advised when transformations are applied in pipeline. (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -#batch_size = 100
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of seconds to wait before publishing samples when batch_size is not
May  9 23:38:23 cmp02 salt-minion[2824]: -# reached (None means indefinitely) (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#batch_timeout = 5
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Number of workers for notification service, default value is 1. (integer
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/notification_workers
May  9 23:38:23 cmp02 salt-minion[2824]: -#workers = 1
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Exchanges name to listen for notifications. (multi valued)
May  9 23:38:23 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/http_control_exchanges
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = nova
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = glance
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = neutron
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = cinder
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = heat
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = keystone
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = sahara
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = trove
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = zaqar
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = swift
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = ceilometer
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = magnum
May  9 23:38:23 cmp02 salt-minion[2824]: -#notification_control_exchanges = dns
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[oslo_concurrency]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.concurrency
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Enables or disables inter-process locks. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#disable_process_locking = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Directory to use for lock files.  For security, the specified directory
May  9 23:38:23 cmp02 salt-minion[2824]: -# should only be writable by the user running the processes that need locking.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Defaults to environment variable OSLO_LOCK_PATH. If OSLO_LOCK_PATH is not set
May  9 23:38:23 cmp02 salt-minion[2824]: -# in the environment, use the Python tempfile.gettempdir function to find a
May  9 23:38:23 cmp02 salt-minion[2824]: -# suitable location. If external locks are used, a lock path must be set.
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#lock_path = /tmp
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -[oslo_messaging_amqp]
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:23 cmp02 salt-minion[2824]: -#
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name for the AMQP container. must be globally unique. Defaults to a generated
May  9 23:38:23 cmp02 salt-minion[2824]: -# UUID (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#container_name = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Timeout for inactive connections (in seconds) (integer value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#idle_timeout = 0
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Debug: dump AMQP frames to stdout (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#trace = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Attempt to connect via SSL. If no other ssl-related parameters are given, it
May  9 23:38:23 cmp02 salt-minion[2824]: -# will use the system's CA-bundle to verify the server's certificate. (boolean
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ssl = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# CA certificate PEM file used to verify the server's certificate (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ssl_ca_file =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Self-identifying certificate PEM file for client authentication (string
May  9 23:38:23 cmp02 salt-minion[2824]: -# value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ssl_cert_file =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Private key PEM file used to sign ssl_cert_file certificate (optional)
May  9 23:38:23 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ssl_key_file =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Password for decrypting ssl_key_file (if encrypted) (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ssl_key_password = <None>
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# By default SSL checks that the name in the server's certificate matches the
May  9 23:38:23 cmp02 salt-minion[2824]: -# hostname in the transport_url. In some configurations it may be preferable to
May  9 23:38:23 cmp02 salt-minion[2824]: -# use the virtual hostname instead, for example if the server uses the Server
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name Indication TLS extension (rfc6066) to provide a certificate per virtual
May  9 23:38:23 cmp02 salt-minion[2824]: -# host. Set ssl_verify_vhost to True if the server's SSL certificate uses the
May  9 23:38:23 cmp02 salt-minion[2824]: -# virtual host name instead of the DNS name. (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#ssl_verify_vhost = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: Accept clients using either SSL or plain TCP (boolean value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Not applicable - not a SSL server
May  9 23:38:23 cmp02 salt-minion[2824]: -#allow_insecure_clients = false
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Space separated list of acceptable SASL mechanisms (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sasl_mechanisms =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Path to directory that contains the SASL configuration (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sasl_config_dir =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# Name of configuration file (without .conf suffix) (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sasl_config_name =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# SASL realm to use if no realm present in username (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -#sasl_default_realm =
May  9 23:38:23 cmp02 salt-minion[2824]: -
May  9 23:38:23 cmp02 salt-minion[2824]: -# DEPRECATED: User name for message broker authentication (string value)
May  9 23:38:23 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:23 cmp02 salt-minion[2824]: -# Reason: Should use configuration option transport_url to provide the
May  9 23:38:23 cmp02 salt-minion[2824]: -# username.
May  9 23:38:24 cmp02 salt-minion[2824]: -#username =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: Password for message broker authentication (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Should use configuration option transport_url to provide the
May  9 23:38:24 cmp02 salt-minion[2824]: -# password.
May  9 23:38:24 cmp02 salt-minion[2824]: -#password =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Seconds to pause before attempting to re-connect. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_retry_interval = 1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Increase the connection_retry_interval by this many seconds after each
May  9 23:38:24 cmp02 salt-minion[2824]: -# unsuccessful failover attempt. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_retry_backoff = 2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum limit for connection_retry_interval + connection_retry_backoff
May  9 23:38:24 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_retry_interval_max = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Time to pause between re-connecting an AMQP 1.0 link that failed due to a
May  9 23:38:24 cmp02 salt-minion[2824]: -# recoverable error. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#link_retry_delay = 10
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The maximum number of attempts to re-send a reply message which failed due to
May  9 23:38:24 cmp02 salt-minion[2824]: -# a recoverable error. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: -1
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_reply_retry = 0
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The deadline for an rpc reply message delivery. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 5
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_reply_timeout = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The deadline for an rpc cast or call message delivery. Only used when caller
May  9 23:38:24 cmp02 salt-minion[2824]: -# does not provide a timeout expiry. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 5
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_send_timeout = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The deadline for a sent notification message delivery. Only used when caller
May  9 23:38:24 cmp02 salt-minion[2824]: -# does not provide a timeout expiry. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 5
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_notify_timeout = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The duration to schedule a purge of idle sender links. Detach link after
May  9 23:38:24 cmp02 salt-minion[2824]: -# expiry. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_sender_link_timeout = 600
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Indicates the addressing mode used by the driver.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Permitted values:
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'legacy'   - use legacy non-routable addressing
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'routable' - use routable addresses
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'dynamic'  - use legacy addresses if the message bus does not support routing
May  9 23:38:24 cmp02 salt-minion[2824]: -# otherwise use routable addressing (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#addressing_mode = dynamic
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Enable virtual host support for those message buses that do not natively
May  9 23:38:24 cmp02 salt-minion[2824]: -# support virtual hosting (such as qpidd). When set to true the virtual host
May  9 23:38:24 cmp02 salt-minion[2824]: -# name will be added to all message bus addresses, effectively creating a
May  9 23:38:24 cmp02 salt-minion[2824]: -# private 'subnet' per virtual host. Set to False if the message bus supports
May  9 23:38:24 cmp02 salt-minion[2824]: -# virtual hosting using the 'hostname' field in the AMQP 1.0 Open performative
May  9 23:38:24 cmp02 salt-minion[2824]: -# as the name of the virtual host. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pseudo_vhost = true
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# address prefix used when sending to a specific server (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#server_request_prefix = exclusive
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# address prefix used when broadcasting to all servers (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#broadcast_prefix = broadcast
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# address prefix when sending to any server in group (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#group_request_prefix = unicast
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Address prefix for all generated RPC addresses (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_address_prefix = openstack.org/om/rpc
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Address prefix for all generated Notification addresses (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#notify_address_prefix = openstack.org/om/notify
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Appended to the address prefix when sending a fanout message. Used by the
May  9 23:38:24 cmp02 salt-minion[2824]: -# message bus to identify fanout messages. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#multicast_address = multicast
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Appended to the address prefix when sending to a particular RPC/Notification
May  9 23:38:24 cmp02 salt-minion[2824]: -# server. Used by the message bus to identify messages sent to a single
May  9 23:38:24 cmp02 salt-minion[2824]: -# destination. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#unicast_address = unicast
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Appended to the address prefix when sending to a group of consumers. Used by
May  9 23:38:24 cmp02 salt-minion[2824]: -# the message bus to identify messages that should be delivered in a round-
May  9 23:38:24 cmp02 salt-minion[2824]: -# robin fashion across consumers. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#anycast_address = anycast
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name used in notification addresses.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name resolution precedence:
May  9 23:38:24 cmp02 salt-minion[2824]: -# Target.exchange if set
May  9 23:38:24 cmp02 salt-minion[2824]: -# else default_notification_exchange if set
May  9 23:38:24 cmp02 salt-minion[2824]: -# else control_exchange if set
May  9 23:38:24 cmp02 salt-minion[2824]: -# else 'notify' (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_notification_exchange = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name used in RPC addresses.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name resolution precedence:
May  9 23:38:24 cmp02 salt-minion[2824]: -# Target.exchange if set
May  9 23:38:24 cmp02 salt-minion[2824]: -# else default_rpc_exchange if set
May  9 23:38:24 cmp02 salt-minion[2824]: -# else control_exchange if set
May  9 23:38:24 cmp02 salt-minion[2824]: -# else 'rpc' (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_rpc_exchange = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Window size for incoming RPC Reply messages. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#reply_link_credit = 200
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Window size for incoming RPC Request messages (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_server_credit = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Window size for incoming Notification messages (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#notify_server_credit = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Send messages of this type pre-settled.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Pre-settled messages will not receive acknowledgement
May  9 23:38:24 cmp02 salt-minion[2824]: -# from the peer. Note well: pre-settled messages may be
May  9 23:38:24 cmp02 salt-minion[2824]: -# silently discarded if the delivery fails.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Permitted values:
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'rpc-call' - send RPC Calls pre-settled
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'rpc-reply'- send RPC Replies pre-settled
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'rpc-cast' - Send RPC Casts pre-settled
May  9 23:38:24 cmp02 salt-minion[2824]: -# 'notify'   - Send Notifications pre-settled
May  9 23:38:24 cmp02 salt-minion[2824]: -#  (multi valued)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pre_settled = rpc-cast
May  9 23:38:24 cmp02 salt-minion[2824]: -#pre_settled = rpc-reply
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[oslo_messaging_kafka]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: Default Kafka broker Host (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#kafka_default_host = localhost
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: Default Kafka broker Port (port value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#kafka_default_port = 9092
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Max fetch bytes of Kafka consumer (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#kafka_max_fetch_bytes = 1048576
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Default timeout(s) for Kafka consumers (floating point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#kafka_consumer_timeout = 1.0
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Pool Size for Kafka Consumers (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pool_size = 10
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The pool size limit for connections expiration policy (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#conn_pool_min_size = 2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The time-to-live in sec of idle connections in the pool (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#conn_pool_ttl = 1200
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Group id for Kafka consumer. Consumers in one group will coordinate message
May  9 23:38:24 cmp02 salt-minion[2824]: -# consumption (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#consumer_group = oslo_messaging_consumer
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Upper bound on the delay for KafkaProducer batching in seconds (floating
May  9 23:38:24 cmp02 salt-minion[2824]: -# point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#producer_batch_timeout = 0.0
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Size of batch for the producer async send (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#producer_batch_size = 16384
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: +auth_type = password
May  9 23:38:24 cmp02 salt-minion[2824]: +user_domain_id = default
May  9 23:38:24 cmp02 salt-minion[2824]: +project_domain_id = default
May  9 23:38:24 cmp02 salt-minion[2824]: +project_name = service
May  9 23:38:24 cmp02 salt-minion[2824]: +username = ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: +password = opnfv_secret
May  9 23:38:24 cmp02 salt-minion[2824]: +auth_uri = http://172.16.10.36:5000
May  9 23:38:24 cmp02 salt-minion[2824]: +auth_url = http://172.16.10.36:35357
May  9 23:38:24 cmp02 salt-minion[2824]: +interface = internal
May  9 23:38:24 cmp02 salt-minion[2824]: +token_cache_time = -1
May  9 23:38:24 cmp02 salt-minion[2824]:  
May  9 23:38:24 cmp02 salt-minion[2824]:  [oslo_messaging_notifications]
May  9 23:38:24 cmp02 salt-minion[2824]:  
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The Drivers(s) to handle sending notifications. Possible values are
May  9 23:38:24 cmp02 salt-minion[2824]: -# messaging, messagingv2, routing, log, test, noop (multi valued)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/notification_driver
May  9 23:38:24 cmp02 salt-minion[2824]: -#driver =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# A URL representing the messaging driver to use for notifications. If not set,
May  9 23:38:24 cmp02 salt-minion[2824]: -# we fall back to the same configuration used for RPC. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/notification_transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#transport_url = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# AMQP topic used for OpenStack notifications. (list value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [rpc_notifier2]/topics
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/notification_topics
May  9 23:38:24 cmp02 salt-minion[2824]: -#topics = notifications
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The maximum number of attempts to re-send a notification message which failed
May  9 23:38:24 cmp02 salt-minion[2824]: -# to be delivered due to a recoverable error. 0 - No retry, -1 - indefinite
May  9 23:38:24 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#retry = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: +topics = notifications
May  9 23:38:24 cmp02 salt-minion[2824]:  
May  9 23:38:24 cmp02 salt-minion[2824]:  [oslo_messaging_rabbit]
May  9 23:38:24 cmp02 salt-minion[2824]:  
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Use durable queues in AMQP. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/amqp_durable_queues
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/rabbit_durable_queues
May  9 23:38:24 cmp02 salt-minion[2824]: -#amqp_durable_queues = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Auto-delete queues in AMQP. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#amqp_auto_delete = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Enable SSL (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#ssl = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and
May  9 23:38:24 cmp02 salt-minion[2824]: -# SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some
May  9 23:38:24 cmp02 salt-minion[2824]: -# distributions. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_version
May  9 23:38:24 cmp02 salt-minion[2824]: -#ssl_version =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# SSL key file (valid only if SSL enabled). (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_keyfile
May  9 23:38:24 cmp02 salt-minion[2824]: -#ssl_key_file =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# SSL cert file (valid only if SSL enabled). (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_certfile
May  9 23:38:24 cmp02 salt-minion[2824]: -#ssl_cert_file =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# SSL certification authority file (valid only if SSL enabled). (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_ca_certs
May  9 23:38:24 cmp02 salt-minion[2824]: -#ssl_ca_file =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How long to wait before reconnecting in response to an AMQP consumer cancel
May  9 23:38:24 cmp02 salt-minion[2824]: -# notification. (floating point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#kombu_reconnect_delay = 1.0
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not
May  9 23:38:24 cmp02 salt-minion[2824]: -# be used. This option may not be available in future versions. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#kombu_compression = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How long to wait a missing client before abandoning to send it its replies.
May  9 23:38:24 cmp02 salt-minion[2824]: -# This value should not be longer than rpc_response_timeout. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [oslo_messaging_rabbit]/kombu_reconnect_timeout
May  9 23:38:24 cmp02 salt-minion[2824]: -#kombu_missing_consumer_retry_timeout = 60
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Determines how the next RabbitMQ node is chosen in case the one we are
May  9 23:38:24 cmp02 salt-minion[2824]: -# currently connected to becomes unavailable. Takes effect only if more than
May  9 23:38:24 cmp02 salt-minion[2824]: -# one RabbitMQ node is provided in config. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: round-robin, shuffle
May  9 23:38:24 cmp02 salt-minion[2824]: -#kombu_failover_strategy = round-robin
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: The RabbitMQ broker address where a single node is used. (string
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_host = localhost
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: The RabbitMQ broker port where a single node is used. (port
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_port = 5672
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: RabbitMQ HA cluster host:port pairs. (list value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_hosts = $rabbit_host:$rabbit_port
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: The RabbitMQ userid. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_userid = guest
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: The RabbitMQ password. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_password = guest
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The RabbitMQ login method. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: PLAIN, AMQPLAIN, RABBIT-CR-DEMO
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_login_method = AMQPLAIN
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: The RabbitMQ virtual host. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reason: Replaced by [DEFAULT]/transport_url
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_virtual_host = /
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How frequently to retry connecting with RabbitMQ. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_retry_interval = 1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How long to backoff for between retries when connecting to RabbitMQ. (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_retry_backoff = 2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum interval of RabbitMQ connection retries. Default is 30 seconds.
May  9 23:38:24 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_interval_max = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# DEPRECATED: Maximum number of RabbitMQ connection retries. Default is 0
May  9 23:38:24 cmp02 salt-minion[2824]: -# (infinite retry count). (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is deprecated for removal.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Its value may be silently ignored in the future.
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_max_retries = 0
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this
May  9 23:38:24 cmp02 salt-minion[2824]: -# option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring
May  9 23:38:24 cmp02 salt-minion[2824]: -# is no longer controlled by the x-ha-policy argument when declaring a queue.
May  9 23:38:24 cmp02 salt-minion[2824]: -# If you just want to make sure that all queues (except those with auto-
May  9 23:38:24 cmp02 salt-minion[2824]: -# generated names) are mirrored across all nodes, run: "rabbitmqctl set_policy
May  9 23:38:24 cmp02 salt-minion[2824]: -# HA '^(?!amq\.).*' '{"ha-mode": "all"}' " (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_ha_queues = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Positive integer representing duration in seconds for queue TTL (x-expires).
May  9 23:38:24 cmp02 salt-minion[2824]: -# Queues which are unused for the duration of the TTL are automatically
May  9 23:38:24 cmp02 salt-minion[2824]: -# deleted. The parameter affects only reply and fanout queues. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_transient_queues_ttl = 1800
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Specifies the number of messages to prefetch. Setting to zero allows
May  9 23:38:24 cmp02 salt-minion[2824]: -# unlimited messages. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rabbit_qos_prefetch_count = 64
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number of seconds after which the Rabbit broker is considered down if
May  9 23:38:24 cmp02 salt-minion[2824]: -# heartbeat's keep-alive fails (0 disable the heartbeat). EXPERIMENTAL (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#heartbeat_timeout_threshold = 60
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How often times during the heartbeat_timeout_threshold we check the
May  9 23:38:24 cmp02 salt-minion[2824]: -# heartbeat. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#heartbeat_rate = 2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#fake_rabbit = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum number of channels to allow (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#channel_max = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The maximum byte size for an AMQP frame (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#frame_max = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How often to send heartbeats for consumer's connections (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#heartbeat_interval = 3
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Arguments passed to ssl.wrap_socket (dict value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#ssl_options = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Set socket timeout in seconds for connection's socket (floating point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#socket_timeout = 0.25
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Set TCP_USER_TIMEOUT in seconds for connection's socket (floating point
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#tcp_user_timeout = 0.25
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Set delay for reconnection to some host which has connection error (floating
May  9 23:38:24 cmp02 salt-minion[2824]: -# point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#host_connection_reconnect_delay = 0.25
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Connection factory implementation (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: new, single, read_write
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_factory = single
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum number of connections to keep queued. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pool_max_size = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum number of connections to create above `pool_max_size`. (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pool_max_overflow = 0
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Default number of seconds to wait for a connections to available (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pool_timeout = 30
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Lifetime of a connection (since creation) in seconds or None for no
May  9 23:38:24 cmp02 salt-minion[2824]: -# recycling. Expired connections are closed on acquire. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pool_recycle = 600
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Threshold at which inactive (since release) connections are considered stale
May  9 23:38:24 cmp02 salt-minion[2824]: -# in seconds or None for no staleness. Stale connections are closed on acquire.
May  9 23:38:24 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#pool_stale = 60
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Default serialization mechanism for serializing/deserializing
May  9 23:38:24 cmp02 salt-minion[2824]: -# outgoing/incoming messages (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: json, msgpack
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_serializer_type = json
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Persist notification messages. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#notification_persistence = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name for sending notifications (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_notification_exchange = ${control_exchange}_notification
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Max number of not acknowledged message which RabbitMQ can send to
May  9 23:38:24 cmp02 salt-minion[2824]: -# notification listener. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#notification_listener_prefetch_count = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reconnecting retry count in case of connectivity problem during sending
May  9 23:38:24 cmp02 salt-minion[2824]: -# notification, -1 means infinite retry. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_notification_retry_attempts = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reconnecting retry delay in case of connectivity problem during sending
May  9 23:38:24 cmp02 salt-minion[2824]: -# notification message (floating point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#notification_retry_delay = 0.25
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Time to live for rpc queues without consumers in seconds. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_queue_expiration = 60
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name for sending RPC messages (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_rpc_exchange = ${control_exchange}_rpc
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Exchange name for receiving RPC replies (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_reply_exchange = ${control_exchange}_rpc_reply
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Max number of not acknowledged message which RabbitMQ can send to rpc
May  9 23:38:24 cmp02 salt-minion[2824]: -# listener. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_listener_prefetch_count = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Max number of not acknowledged message which RabbitMQ can send to rpc reply
May  9 23:38:24 cmp02 salt-minion[2824]: -# listener. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_reply_listener_prefetch_count = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reconnecting retry count in case of connectivity problem during sending
May  9 23:38:24 cmp02 salt-minion[2824]: -# reply. -1 means infinite retry during rpc_timeout (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_reply_retry_attempts = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reconnecting retry delay in case of connectivity problem during sending
May  9 23:38:24 cmp02 salt-minion[2824]: -# reply. (floating point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_reply_retry_delay = 0.25
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reconnecting retry count in case of connectivity problem during sending RPC
May  9 23:38:24 cmp02 salt-minion[2824]: -# message, -1 means infinite retry. If actual retry attempts in not 0 the rpc
May  9 23:38:24 cmp02 salt-minion[2824]: -# request could be processed more than one time (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_rpc_retry_attempts = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Reconnecting retry delay in case of connectivity problem during sending RPC
May  9 23:38:24 cmp02 salt-minion[2824]: -# message (floating point value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_retry_delay = 0.25
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[oslo_messaging_zmq]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From oslo.messaging
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP.
May  9 23:38:24 cmp02 salt-minion[2824]: -# The "host" option should point or resolve to this address. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_bind_address = *
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# MatchMaker driver. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: redis, sentinel, dummy
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_matchmaker = redis
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number of ZeroMQ contexts, defaults to 1. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_contexts = 1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum number of ingress messages to locally buffer per topic. Default is
May  9 23:38:24 cmp02 salt-minion[2824]: -# unlimited. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_topic_backlog = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Directory for holding IPC sockets. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_ipc_dir = /var/run/openstack
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Name of this node. Must be a valid hostname, FQDN, or IP address. Must match
May  9 23:38:24 cmp02 salt-minion[2824]: -# "host" option, if running Nova. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_host = localhost
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number of seconds to wait before all pending messages will be sent after
May  9 23:38:24 cmp02 salt-minion[2824]: -# closing a socket. The default value of -1 specifies an infinite linger
May  9 23:38:24 cmp02 salt-minion[2824]: -# period. The value of 0 specifies no linger period. Pending messages shall be
May  9 23:38:24 cmp02 salt-minion[2824]: -# discarded immediately when the socket is closed. Positive values specify an
May  9 23:38:24 cmp02 salt-minion[2824]: -# upper bound for the linger period. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/rpc_cast_timeout
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_linger = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The default number of seconds that poll should wait. Poll raises timeout
May  9 23:38:24 cmp02 salt-minion[2824]: -# exception when timeout expired. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_poll_timeout = 1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Expiration timeout in seconds of a name service record about existing target
May  9 23:38:24 cmp02 salt-minion[2824]: -# ( < 0 means no timeout). (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_target_expire = 300
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Update period in seconds of a name service record about existing target.
May  9 23:38:24 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_target_update = 180
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. (boolean
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#use_pub_sub = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Use ROUTER remote proxy. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#use_router_proxy = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option makes direct connections dynamic or static. It makes sense only
May  9 23:38:24 cmp02 salt-minion[2824]: -# with use_router_proxy=False which means to use direct connections for direct
May  9 23:38:24 cmp02 salt-minion[2824]: -# message types (ignored otherwise). (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#use_dynamic_connections = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# How many additional connections to a host will be made for failover reasons.
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option is actual only in dynamic connections mode. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_failover_connections = 2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimal port number for random ports range. (port value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_min_port = 49153
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximal port number for random ports range. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 1
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum value: 65536
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_max_port = 65536
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number of retries to find free port number before fail with ZMQBindError.
May  9 23:38:24 cmp02 salt-minion[2824]: -# (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_bind_port_retries = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Default serialization mechanism for serializing/deserializing
May  9 23:38:24 cmp02 salt-minion[2824]: -# outgoing/incoming messages (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: json, msgpack
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_zmq_serialization = json
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# This option configures round-robin mode in zmq socket. True means not keeping
May  9 23:38:24 cmp02 salt-minion[2824]: -# a queue when server side disconnects. False means to keep queue and messages
May  9 23:38:24 cmp02 salt-minion[2824]: -# even if server is disconnected, when the server appears we send all
May  9 23:38:24 cmp02 salt-minion[2824]: -# accumulated messages to it. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_immediate = true
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any
May  9 23:38:24 cmp02 salt-minion[2824]: -# other negative value) means to skip any overrides and leave it to OS default;
May  9 23:38:24 cmp02 salt-minion[2824]: -# 0 and 1 (or any other positive value) mean to disable and enable the option
May  9 23:38:24 cmp02 salt-minion[2824]: -# respectively. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The duration between two keepalive transmissions in idle condition. The unit
May  9 23:38:24 cmp02 salt-minion[2824]: -# is platform dependent, for example, seconds in Linux, milliseconds in Windows
May  9 23:38:24 cmp02 salt-minion[2824]: -# etc. The default value of -1 (or any other negative value and 0) means to
May  9 23:38:24 cmp02 salt-minion[2824]: -# skip any overrides and leave it to OS default. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_idle = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The number of retransmissions to be carried out before declaring that remote
May  9 23:38:24 cmp02 salt-minion[2824]: -# end is not available. The default value of -1 (or any other negative value
May  9 23:38:24 cmp02 salt-minion[2824]: -# and 0) means to skip any overrides and leave it to OS default. (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_cnt = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The duration between two successive keepalive retransmissions, if
May  9 23:38:24 cmp02 salt-minion[2824]: -# acknowledgement to the previous keepalive transmission is not received. The
May  9 23:38:24 cmp02 salt-minion[2824]: -# unit is platform dependent, for example, seconds in Linux, milliseconds in
May  9 23:38:24 cmp02 salt-minion[2824]: -# Windows etc. The default value of -1 (or any other negative value and 0)
May  9 23:38:24 cmp02 salt-minion[2824]: -# means to skip any overrides and leave it to OS default. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#zmq_tcp_keepalive_intvl = -1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum number of (green) threads to work concurrently. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_thread_pool_size = 100
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Expiration timeout in seconds of a sent/received message after which it is
May  9 23:38:24 cmp02 salt-minion[2824]: -# not tracked anymore by a client/server. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_message_ttl = 300
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Wait for message acknowledgements from receivers. This mechanism works only
May  9 23:38:24 cmp02 salt-minion[2824]: -# via proxy without PUB/SUB. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_use_acks = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number of seconds to wait for an ack from a cast/call. After each retry
May  9 23:38:24 cmp02 salt-minion[2824]: -# attempt this timeout is multiplied by some specified multiplier. (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_ack_timeout_base = 15
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number to multiply base ack timeout by after each retry attempt. (integer
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_ack_timeout_multiplier = 2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Default number of message sending attempts in case of any problems occurred:
May  9 23:38:24 cmp02 salt-minion[2824]: -# positive value N means at most N retries, 0 means no retries, None or -1 (or
May  9 23:38:24 cmp02 salt-minion[2824]: -# any other negative values) mean to retry forever. This option is used only if
May  9 23:38:24 cmp02 salt-minion[2824]: -# acknowledgments are enabled. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#rpc_retry_attempts = 3
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# List of publisher hosts SubConsumer can subscribe on. This option has higher
May  9 23:38:24 cmp02 salt-minion[2824]: -# priority then the default publishers list taken from the matchmaker. (list
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#subscribe_on =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[oslo_middleware]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From oslo.middleware.http_proxy_to_wsgi
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Whether the application is behind a proxy or not. This determines if the
May  9 23:38:24 cmp02 salt-minion[2824]: -# middleware should parse the headers or not. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#enable_proxy_headers_parsing = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[oslo_policy]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From oslo.policy
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The file that defines policies. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#policy_file = policy.json
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Default rule. Enforced when a requested rule is not found. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#policy_default_rule = default
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Directories where policy configuration files are stored. They can be relative
May  9 23:38:24 cmp02 salt-minion[2824]: -# to any directory in the search path defined by the config_dir option, or
May  9 23:38:24 cmp02 salt-minion[2824]: -# absolute paths. The file defined by policy_file must exist for these
May  9 23:38:24 cmp02 salt-minion[2824]: -# directories to be searched.  Missing or empty directories are ignored. (multi
May  9 23:38:24 cmp02 salt-minion[2824]: -# valued)
May  9 23:38:24 cmp02 salt-minion[2824]: -#policy_dirs = policy.d
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[polling]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Configuration file for pipeline definition. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#cfg_file = polling.yaml
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Work-load partitioning group prefix. Use only if you want to run multiple
May  9 23:38:24 cmp02 salt-minion[2824]: -# polling agents with different config files. For each sub-group of the agent
May  9 23:38:24 cmp02 salt-minion[2824]: -# pool with the same partitioning_group_prefix a disjoint subset of pollsters
May  9 23:38:24 cmp02 salt-minion[2824]: -# should be loaded. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#partitioning_group_prefix = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[publisher]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Secret value for signing messages. Set value empty if signing is not required
May  9 23:38:24 cmp02 salt-minion[2824]: -# to avoid computational overhead. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/metering_secret
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [publisher_rpc]/metering_secret
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [publisher]/metering_secret
May  9 23:38:24 cmp02 salt-minion[2824]: -#telemetry_secret = change this for valid signing
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[publisher_notifier]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The topic that ceilometer uses for metering notifications. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#metering_topic = metering
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The topic that ceilometer uses for event notifications. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#event_topic = event
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# The driver that ceilometer uses for metering notifications. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [publisher_notifier]/metering_driver
May  9 23:38:24 cmp02 salt-minion[2824]: -#telemetry_driver = messagingv2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[rgw_admin_credentials]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Access key for Radosgw Admin. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#access_key = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Secret key for Radosgw Admin. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#secret_key = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]:  [service_credentials]
May  9 23:38:24 cmp02 salt-minion[2824]:  
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer-auth
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Authentication type to load (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [service_credentials]/auth_plugin
May  9 23:38:24 cmp02 salt-minion[2824]: -#auth_type = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Config Section from which to load plugin specific options (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#auth_section = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Authentication URL (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#auth_url = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Domain ID to scope to (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#domain_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Domain name to scope to (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#domain_name = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Project ID to scope to (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [service_credentials]/tenant_id
May  9 23:38:24 cmp02 salt-minion[2824]: -#project_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Project name to scope to (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [service_credentials]/tenant_name
May  9 23:38:24 cmp02 salt-minion[2824]: -#project_name = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Domain ID containing project (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#project_domain_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Domain name containing project (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#project_domain_name = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Trust ID (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#trust_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Optional domain ID to use with v3 and v2 parameters. It will be used for both
May  9 23:38:24 cmp02 salt-minion[2824]: -# the user and project domain in v3 and ignored in v2 authentication. (string
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_domain_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Optional domain name to use with v3 API and v2 parameters. It will be used
May  9 23:38:24 cmp02 salt-minion[2824]: -# for both the user and project domain in v3 and ignored in v2 authentication.
May  9 23:38:24 cmp02 salt-minion[2824]: -# (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#default_domain_name = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# User id (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#user_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Username (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [service_credentials]/user_name
May  9 23:38:24 cmp02 salt-minion[2824]: -#username = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# User's domain id (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#user_domain_id = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# User's domain name (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#user_domain_name = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# User's password (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#password = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Region name to use for OpenStack service endpoints. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [DEFAULT]/os_region_name
May  9 23:38:24 cmp02 salt-minion[2824]: -#region_name = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Type of endpoint in Identity service catalog to use for communication with
May  9 23:38:24 cmp02 salt-minion[2824]: -# OpenStack services. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: public, internal, admin, auth, publicURL, internalURL, adminURL
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [service_credentials]/os_endpoint_type
May  9 23:38:24 cmp02 salt-minion[2824]: -#interface = public
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[service_types]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Glance service type. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#glance = image
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Neutron service type. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#neutron = network
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Neutron load balancer version. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Allowed values: v1, v2
May  9 23:38:24 cmp02 salt-minion[2824]: -#neutron_lbaas_version = v2
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Nova service type. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#nova = compute
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Radosgw service type. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#radosgw = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Swift service type. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#swift = object-store
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Cinder service type. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Deprecated group/name - [service_types]/cinderv2
May  9 23:38:24 cmp02 salt-minion[2824]: -#cinder = volumev3
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[vmware]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# IP address of the VMware vSphere host. (unknown value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#host_ip = 127.0.0.1
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Port of the VMware vSphere host. (port value)
May  9 23:38:24 cmp02 salt-minion[2824]: -# Minimum value: 0
May  9 23:38:24 cmp02 salt-minion[2824]: -# Maximum value: 65535
May  9 23:38:24 cmp02 salt-minion[2824]: -#host_port = 443
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Username of VMware vSphere. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#host_username =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Password of VMware vSphere. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#host_password =
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# CA bundle file to use in verifying the vCenter server certificate. (string
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#ca_file = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# If true, the vCenter server certificate is not verified. If false, then the
May  9 23:38:24 cmp02 salt-minion[2824]: -# default CA truststore is used for verification. This option is ignored if
May  9 23:38:24 cmp02 salt-minion[2824]: -# "ca_file" is set. (boolean value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#insecure = false
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Number of times a VMware vSphere API may be retried. (integer value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#api_retry_count = 10
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Sleep time in seconds for polling an ongoing async task. (floating point
May  9 23:38:24 cmp02 salt-minion[2824]: -# value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#task_poll_interval = 0.5
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Optional vim service WSDL location e.g http://<server>/vimService.wsdl.
May  9 23:38:24 cmp02 salt-minion[2824]: -# Optional over-ride to default location for bug work-arounds. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#wsdl_location = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -[xenapi]
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -# From ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: -#
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# URL for connection to XenServer/Xen Cloud Platform. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_url = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Username for connection to XenServer/Xen Cloud Platform. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_username = root
May  9 23:38:24 cmp02 salt-minion[2824]: -
May  9 23:38:24 cmp02 salt-minion[2824]: -# Password for connection to XenServer/Xen Cloud Platform. (string value)
May  9 23:38:24 cmp02 salt-minion[2824]: -#connection_password = <None>
May  9 23:38:24 cmp02 salt-minion[2824]: +auth_type = password
May  9 23:38:24 cmp02 salt-minion[2824]: +user_domain_id = default
May  9 23:38:24 cmp02 salt-minion[2824]: +project_domain_id = default
May  9 23:38:24 cmp02 salt-minion[2824]: +project_name = service
May  9 23:38:24 cmp02 salt-minion[2824]: +username = ceilometer
May  9 23:38:24 cmp02 salt-minion[2824]: +password = opnfv_secret
May  9 23:38:24 cmp02 salt-minion[2824]: +auth_url = http://172.16.10.36:5000
May  9 23:38:24 cmp02 salt-minion[2824]: +token_cache_time = -1
May  9 23:38:24 cmp02 salt-minion[2824]: +interface = internal
May  9 23:38:24 cmp02 salt-minion[2824]: +region_name = RegionOne
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/ceilometer/ceilometer.conf] at time 23:38:23.761659 duration_in_ms=157.997
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/default/ceilometer-agent-compute] at time 23:38:23.761999
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/default/ceilometer-agent-compute
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ceilometer/files/default'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:38:24 cmp02 salt-minion[2824]: New file
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/default/ceilometer-agent-compute] at time 23:38:23.784046 duration_in_ms=22.047
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/ceilometer/pipeline.yaml] at time 23:38:23.784919
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/ceilometer/pipeline.yaml
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ceilometer/files/pike/pipeline.yaml'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:38:24 cmp02 salt-minion[2824]: New file
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/ceilometer/pipeline.yaml] at time 23:38:23.869926 duration_in_ms=85.007
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Running state [/etc/ceilometer/event_pipeline.yaml] at time 23:38:23.870228
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing state file.managed for /etc/ceilometer/event_pipeline.yaml
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Fetching file from saltenv 'base', ** done ** 'ceilometer/files/pike/event_pipeline.yaml'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] File changed:
May  9 23:38:24 cmp02 salt-minion[2824]: New file
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [/etc/ceilometer/event_pipeline.yaml] at time 23:38:23.957843 duration_in_ms=87.615
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Running state [ceilometer-agent-compute] at time 23:38:24.445117
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing state service.running for ceilometer-agent-compute
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'status', 'ceilometer-agent-compute.service', '-n', '0'] in directory '/root'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'ceilometer-agent-compute.service'] in directory '/root'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ceilometer-agent-compute.service'] in directory '/root'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] The service ceilometer-agent-compute is already running
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [ceilometer-agent-compute] at time 23:38:24.487688 duration_in_ms=42.572
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Running state [ceilometer-agent-compute] at time 23:38:24.487977
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing state service.mod_watch for ceilometer-agent-compute
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-active', 'ceilometer-agent-compute.service'] in directory '/root'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemctl', 'is-enabled', 'ceilometer-agent-compute.service'] in directory '/root'
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'restart', 'ceilometer-agent-compute.service'] in directory '/root'
May  9 23:38:24 cmp02 systemd[1]: Started /bin/systemctl restart ceilometer-agent-compute.service.
May  9 23:38:24 cmp02 systemd[1]: Stopping Ceilometer Agent Compute...
May  9 23:38:24 cmp02 libvirtd[5599]: 2018-05-09 23:38:24.568+0000: 5599: info : libvirt version: 4.0.0, package: 1.7~u16.04+mcp1 (Ivan Suzdal <mos-linux@mirantis.com> Tue, 03 Apr 2018 13:27:14 +0000)
May  9 23:38:24 cmp02 libvirtd[5599]: 2018-05-09 23:38:24.568+0000: 5599: info : hostname: cmp02
May  9 23:38:24 cmp02 libvirtd[5599]: 2018-05-09 23:38:24.568+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error
May  9 23:38:24 cmp02 libvirtd[5599]: message repeated 19 times: [ 2018-05-09 23:38:24.568+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error]
May  9 23:38:24 cmp02 libvirtd[5599]: 2018-05-09 23:38:24.569+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error
May  9 23:38:24 cmp02 libvirtd[5599]: message repeated 13 times: [ 2018-05-09 23:38:24.569+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error]
May  9 23:38:24 cmp02 libvirtd[5599]: 2018-05-09 23:38:24.573+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error
May  9 23:38:24 cmp02 libvirtd[5599]: message repeated 9 times: [ 2018-05-09 23:38:24.573+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error]
May  9 23:38:24 cmp02 libvirtd[5599]: 2018-05-09 23:38:24.574+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error
May  9 23:38:24 cmp02 libvirtd[5599]: message repeated 4 times: [ 2018-05-09 23:38:24.574+0000: 5599: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error]
May  9 23:38:24 cmp02 systemd[1]: Stopped Ceilometer Agent Compute.
May  9 23:38:24 cmp02 systemd[1]: Starting Ceilometer Agent Compute...
May  9 23:38:24 cmp02 systemd[1]: Started Ceilometer Agent Compute.
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] {'ceilometer-agent-compute': True}
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Completed state [ceilometer-agent-compute] at time 23:38:24.677056 duration_in_ms=189.079
May  9 23:38:24 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509233800436434
May  9 23:40:50 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May  9 23:40:50 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May  9 23:40:50 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1585 seconds.
May  9 23:41:36 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command cp.push_dir with jid 20180509234136994052
May  9 23:41:37 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 7621
May  9 23:41:39 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509234136994052
May  9 23:42:51 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command grains.get with jid 20180509234251236824
May  9 23:42:51 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 7697
May  9 23:42:51 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180509234251236824
May  9 23:44:40 cmp02 kernel: [ 1688.305356] Netfilter messages via NETLINK v0.30.
May  9 23:44:40 cmp02 kernel: [ 1688.309255] ctnetlink v0.93: registering with nfnetlink.
May  9 23:47:04 cmp02 kernel: [ 1832.820978] capability: warning: `privsep-helper' uses deprecated v2 capabilities in a way that may be insecure
May  9 23:47:05 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:47:06 cmp02 kernel: [ 1834.223476] audit: type=1400 audit(1525909626.388:19): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=7835 comm="apparmor_parser"
May  9 23:47:06 cmp02 kernel: [ 1834.461381] audit: type=1400 audit(1525909626.626:20): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=7838 comm="apparmor_parser"
May  9 23:47:06 cmp02 kernel: [ 1834.687871] audit: type=1400 audit(1525909626.852:21): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=7841 comm="apparmor_parser"
May  9 23:47:07 cmp02 kernel: [ 1834.916855] audit: type=1400 audit(1525909627.081:22): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=7844 comm="apparmor_parser"
May  9 23:47:07 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap39a27054-b2 -- add-port br-int tap39a27054-b2 -- set Interface tap39a27054-b2 "external-ids:attached-mac=\"fa:16:3e:42:55:3f\"" -- set Interface tap39a27054-b2 "external-ids:iface-id=\"39a27054-b2ad-4a49-9585-c9788ac748cd\"" -- set Interface tap39a27054-b2 "external-ids:vm-id=\"8afd032d-d327-44c6-a704-a9ddc2262dd2\"" -- set Interface tap39a27054-b2 external-ids:iface-status=active
May  9 23:47:07 cmp02 kernel: [ 1834.949830] device tap39a27054-b2 entered promiscuous mode
May  9 23:47:07 cmp02 kernel: [ 1835.205577] audit: type=1400 audit(1525909627.370:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=7945 comm="apparmor_parser"
May  9 23:47:07 cmp02 libvirtd[5599]: 2018-05-09 23:47:07.375+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=1 name='instance-00000002' uuid=8afd032d-d327-44c6-a704-a9ddc2262dd2 is tainted: host-cpu
May  9 23:47:16 cmp02 kernel: [ 1844.761145] scsi host2: iSCSI Initiator over TCP/IP
May  9 23:47:17 cmp02 kernel: [ 1845.779578] scsi 2:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May  9 23:47:17 cmp02 kernel: [ 1845.824212] scsi 2:0:0:0: Attached scsi generic sg1 type 12
May  9 23:47:17 cmp02 kernel: [ 1845.825138] scsi 2:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May  9 23:47:18 cmp02 kernel: [ 1845.864104] sd 2:0:0:1: Attached scsi generic sg2 type 0
May  9 23:47:18 cmp02 kernel: [ 1845.865116] sd 2:0:0:1: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
May  9 23:47:18 cmp02 kernel: [ 1845.866114] sd 2:0:0:1: [sda] Write Protect is off
May  9 23:47:18 cmp02 kernel: [ 1845.866117] sd 2:0:0:1: [sda] Mode Sense: 69 00 10 08
May  9 23:47:18 cmp02 kernel: [ 1845.866722] sd 2:0:0:1: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
May  9 23:47:18 cmp02 kernel: [ 1845.874373] sd 2:0:0:1: [sda] Attached SCSI disk
May  9 23:47:18 cmp02 iscsid: Connection1:0 to [target: iqn.2010-10.org.openstack:volume-1a45c258-9ddc-41a9-b315-b387f0d32328, portal: 192.168.11.42,3260] through [iface: default] is operational now
May  9 23:47:18 cmp02 kernel: [ 1846.194759] audit: type=1400 audit(1525909638.359:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=8039 comm="apparmor_parser"
May  9 23:47:24 cmp02 kernel: [ 1852.370361] audit: type=1400 audit(1525909644.534:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=8098 comm="apparmor_parser"
May  9 23:47:24 cmp02 kernel: [ 1852.580261] sd 2:0:0:1: [sda] Synchronizing SCSI cache
May  9 23:47:26 cmp02 iscsid: Connection1:0 to [target: iqn.2010-10.org.openstack:volume-1a45c258-9ddc-41a9-b315-b387f0d32328, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May  9 23:47:32 cmp02 kernel: [ 1860.276640] device tap39a27054-b2 left promiscuous mode
May  9 23:47:33 cmp02 kernel: [ 1860.857989] audit: type=1400 audit(1525909653.022:26): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-8afd032d-d327-44c6-a704-a9ddc2262dd2" pid=8170 comm="apparmor_parser"
May  9 23:47:33 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap39a27054-b2
May  9 23:48:00 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:48:01 cmp02 kernel: [ 1889.823310] audit: type=1400 audit(1525909681.986:27): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8261 comm="apparmor_parser"
May  9 23:48:02 cmp02 kernel: [ 1890.060272] audit: type=1400 audit(1525909682.223:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8264 comm="apparmor_parser"
May  9 23:48:02 cmp02 kernel: [ 1890.300144] audit: type=1400 audit(1525909682.463:29): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8267 comm="apparmor_parser"
May  9 23:48:02 cmp02 kernel: [ 1890.539609] audit: type=1400 audit(1525909682.703:30): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8270 comm="apparmor_parser"
May  9 23:48:02 cmp02 systemd-udevd[8273]: Could not generate persistent MAC address for tap11299a3d-08: No such file or directory
May  9 23:48:02 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap11299a3d-08 -- add-port br-int tap11299a3d-08 -- set Interface tap11299a3d-08 "external-ids:attached-mac=\"fa:16:3e:a5:cd:5c\"" -- set Interface tap11299a3d-08 "external-ids:iface-id=\"11299a3d-084c-4c07-b239-25ecfea1167a\"" -- set Interface tap11299a3d-08 "external-ids:vm-id=\"966334c1-5dd1-44ee-a4b8-bd0a4e105b78\"" -- set Interface tap11299a3d-08 external-ids:iface-status=active
May  9 23:48:02 cmp02 kernel: [ 1890.575332] device tap11299a3d-08 entered promiscuous mode
May  9 23:48:02 cmp02 kernel: [ 1890.813152] audit: type=1400 audit(1525909682.976:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8342 comm="apparmor_parser"
May  9 23:48:02 cmp02 libvirtd[5599]: 2018-05-09 23:48:02.982+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=2 name='instance-00000003' uuid=966334c1-5dd1-44ee-a4b8-bd0a4e105b78 is tainted: host-cpu
May  9 23:48:10 cmp02 kernel: [ 1898.134605] scsi host2: iSCSI Initiator over TCP/IP
May  9 23:48:11 cmp02 kernel: [ 1899.149243] scsi 2:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May  9 23:48:11 cmp02 iscsid: Connection2:0 to [target: iqn.2010-10.org.openstack:volume-333755bc-3fa8-415a-9103-edcf759598df, portal: 192.168.11.42,3260] through [iface: default] is operational now
May  9 23:48:11 cmp02 kernel: [ 1899.213506] scsi 2:0:0:0: Attached scsi generic sg1 type 12
May  9 23:48:11 cmp02 kernel: [ 1899.214858] scsi 2:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May  9 23:48:11 cmp02 kernel: [ 1899.249791] sd 2:0:0:1: Attached scsi generic sg2 type 0
May  9 23:48:11 cmp02 kernel: [ 1899.252176] sd 2:0:0:1: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
May  9 23:48:11 cmp02 kernel: [ 1899.252408] sd 2:0:0:1: [sda] Write Protect is off
May  9 23:48:11 cmp02 kernel: [ 1899.252411] sd 2:0:0:1: [sda] Mode Sense: 69 00 10 08
May  9 23:48:11 cmp02 kernel: [ 1899.255101] sd 2:0:0:1: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
May  9 23:48:11 cmp02 kernel: [ 1899.261423] sd 2:0:0:1: [sda] Attached SCSI disk
May  9 23:48:13 cmp02 kernel: [ 1901.577060] audit: type=1400 audit(1525909693.740:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8459 comm="apparmor_parser"
May  9 23:48:14 cmp02 kernel: [ 1902.143949] device tap11299a3d-08 left promiscuous mode
May  9 23:48:14 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap11299a3d-08
May  9 23:48:14 cmp02 libvirtd[5599]: 2018-05-09 23:48:14.746+0000: 5599: error : qemuMonitorIOWrite:565 : Unable to write to monitor: Broken pipe
May  9 23:48:14 cmp02 kernel: [ 1902.789269] audit: type=1400 audit(1525909694.952:33): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-966334c1-5dd1-44ee-a4b8-bd0a4e105b78" pid=8479 comm="apparmor_parser"
May  9 23:48:16 cmp02 kernel: [ 1904.274230]  connection2:0: detected conn error (1020)
May  9 23:48:17 cmp02 iscsid: Kernel reported iSCSI connection 2:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
May  9 23:48:44 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:48:45 cmp02 kernel: [ 1933.242714] audit: type=1400 audit(1525909725.404:34): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8572 comm="apparmor_parser"
May  9 23:48:45 cmp02 kernel: [ 1933.519797] audit: type=1400 audit(1525909725.682:35): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8575 comm="apparmor_parser"
May  9 23:48:45 cmp02 kernel: [ 1933.766685] audit: type=1400 audit(1525909725.929:36): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8578 comm="apparmor_parser"
May  9 23:48:46 cmp02 kernel: [ 1933.993998] audit: type=1400 audit(1525909726.156:37): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8581 comm="apparmor_parser"
May  9 23:48:46 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap4ba70160-a6 -- add-port br-int tap4ba70160-a6 -- set Interface tap4ba70160-a6 "external-ids:attached-mac=\"fa:16:3e:24:3b:d2\"" -- set Interface tap4ba70160-a6 "external-ids:iface-id=\"4ba70160-a644-431b-96bb-262cce2e54c0\"" -- set Interface tap4ba70160-a6 "external-ids:vm-id=\"02ff7183-1ead-4c7f-98a3-fd03672f38fc\"" -- set Interface tap4ba70160-a6 external-ids:iface-status=active
May  9 23:48:46 cmp02 kernel: [ 1934.036511] device tap4ba70160-a6 entered promiscuous mode
May  9 23:48:46 cmp02 kernel: [ 1934.300012] audit: type=1400 audit(1525909726.462:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8645 comm="apparmor_parser"
May  9 23:48:46 cmp02 libvirtd[5599]: 2018-05-09 23:48:46.474+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=3 name='instance-00000004' uuid=02ff7183-1ead-4c7f-98a3-fd03672f38fc is tainted: host-cpu
May  9 23:48:52 cmp02 kernel: [ 1940.758959] scsi host3: iSCSI Initiator over TCP/IP
May  9 23:48:53 cmp02 kernel: [ 1941.773787]  connection2:0: detected conn error (1020)
May  9 23:48:53 cmp02 kernel: [ 1941.775841] scsi 3:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May  9 23:48:53 cmp02 kernel: [ 1941.810804] scsi 3:0:0:0: Attached scsi generic sg3 type 12
May  9 23:48:53 cmp02 kernel: [ 1941.812606] scsi 3:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May  9 23:48:54 cmp02 kernel: [ 1941.846862] sd 3:0:0:1: Attached scsi generic sg4 type 0
May  9 23:48:54 cmp02 kernel: [ 1941.850023] sd 3:0:0:1: [sdb] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
May  9 23:48:54 cmp02 kernel: [ 1941.850279] sd 3:0:0:1: [sdb] Write Protect is off
May  9 23:48:54 cmp02 kernel: [ 1941.850283] sd 3:0:0:1: [sdb] Mode Sense: 69 00 10 08
May  9 23:48:54 cmp02 kernel: [ 1941.851000] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May  9 23:48:54 cmp02 kernel: [ 1941.861770] sd 3:0:0:1: [sdb] Attached SCSI disk
May  9 23:48:54 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session3/target3:0:0/3:0:0:1/block/sdb
May  9 23:48:54 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session3/target3:0:0/3:0:0:1/block/sdb
May  9 23:48:54 cmp02 kernel: [ 1942.184251] audit: type=1400 audit(1525909734.346:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8767 comm="apparmor_parser"
May  9 23:48:54 cmp02 iscsid: Connection3:0 to [target: iqn.2010-10.org.openstack:volume-40d11853-0f85-4fda-92e6-b95773cf1a93, portal: 192.168.11.42,3260] through [iface: default] is operational now
May  9 23:48:54 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May  9 23:48:56 cmp02 kernel: [ 1944.779229]  connection2:0: detected conn error (1020)
May  9 23:48:57 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session3/target3:0:0/3:0:0:1/block/sdb
May  9 23:48:57 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session3/target3:0:0/3:0:0:1/block/sdb
May  9 23:48:57 cmp02 kernel: [ 1945.122310] audit: type=1400 audit(1525909737.284:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8778 comm="apparmor_parser"
May  9 23:48:57 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May  9 23:48:57 cmp02 kernel: [ 1945.276273] sd 3:0:0:1: [sdb] Synchronizing SCSI cache
May  9 23:48:57 cmp02 kernel: [ 1945.797693] device tap4ba70160-a6 left promiscuous mode
May  9 23:48:58 cmp02 libvirtd[5599]: 2018-05-09 23:48:58.134+0000: 5599: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
May  9 23:48:58 cmp02 iscsid: Connection3:0 to [target: iqn.2010-10.org.openstack:volume-40d11853-0f85-4fda-92e6-b95773cf1a93, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May  9 23:49:03 cmp02 kernel: [ 1950.976613] audit: type=1400 audit(1525909743.138:41): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-02ff7183-1ead-4c7f-98a3-fd03672f38fc" pid=8814 comm="apparmor_parser"
May  9 23:49:03 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap4ba70160-a6
May  9 23:50:00 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:50:01 cmp02 kernel: [ 2009.100528] audit: type=1400 audit(1525909801.261:42): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-69a002d3-a8d6-45e9-ab00-fe9442fa1ac2" pid=8908 comm="apparmor_parser"
May  9 23:50:01 cmp02 kernel: [ 2009.342816] audit: type=1400 audit(1525909801.503:43): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-69a002d3-a8d6-45e9-ab00-fe9442fa1ac2" pid=8911 comm="apparmor_parser"
May  9 23:50:01 cmp02 kernel: [ 2009.572592] audit: type=1400 audit(1525909801.733:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-69a002d3-a8d6-45e9-ab00-fe9442fa1ac2" pid=8914 comm="apparmor_parser"
May  9 23:50:01 cmp02 kernel: [ 2009.818623] audit: type=1400 audit(1525909801.979:45): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-69a002d3-a8d6-45e9-ab00-fe9442fa1ac2" pid=8917 comm="apparmor_parser"
May  9 23:50:02 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3c9ea52c-d8 -- add-port br-int tap3c9ea52c-d8 -- set Interface tap3c9ea52c-d8 "external-ids:attached-mac=\"fa:16:3e:a8:70:ac\"" -- set Interface tap3c9ea52c-d8 "external-ids:iface-id=\"3c9ea52c-d818-453e-8c20-e84daeaa0df6\"" -- set Interface tap3c9ea52c-d8 "external-ids:vm-id=\"69a002d3-a8d6-45e9-ab00-fe9442fa1ac2\"" -- set Interface tap3c9ea52c-d8 external-ids:iface-status=active
May  9 23:50:02 cmp02 kernel: [ 2009.849077] device tap3c9ea52c-d8 entered promiscuous mode
May  9 23:50:02 cmp02 kernel: [ 2010.080006] audit: type=1400 audit(1525909802.240:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-69a002d3-a8d6-45e9-ab00-fe9442fa1ac2" pid=8984 comm="apparmor_parser"
May  9 23:50:02 cmp02 libvirtd[5599]: 2018-05-09 23:50:02.248+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=4 name='instance-00000006' uuid=69a002d3-a8d6-45e9-ab00-fe9442fa1ac2 is tainted: host-cpu
May  9 23:50:16 cmp02 kernel: [ 2024.588148]  session2: session recovery timed out after 120 secs
May  9 23:50:17 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:50:19 cmp02 kernel: [ 2026.894551] audit: type=1400 audit(1525909819.054:47): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-cabadec0-abe3-46b6-b60a-cfbddeededc3" pid=9160 comm="apparmor_parser"
May  9 23:50:19 cmp02 kernel: [ 2027.252701] audit: type=1400 audit(1525909819.413:48): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-cabadec0-abe3-46b6-b60a-cfbddeededc3" pid=9163 comm="apparmor_parser"
May  9 23:50:19 cmp02 kernel: [ 2027.539612] audit: type=1400 audit(1525909819.699:49): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-cabadec0-abe3-46b6-b60a-cfbddeededc3" pid=9166 comm="apparmor_parser"
May  9 23:50:20 cmp02 kernel: [ 2027.859092] audit: type=1400 audit(1525909820.019:50): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-cabadec0-abe3-46b6-b60a-cfbddeededc3" pid=9169 comm="apparmor_parser"
May  9 23:50:20 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap69502567-74 -- add-port br-int tap69502567-74 -- set Interface tap69502567-74 "external-ids:attached-mac=\"fa:16:3e:39:ce:9b\"" -- set Interface tap69502567-74 "external-ids:iface-id=\"69502567-746c-4cec-8594-233746cbd17a\"" -- set Interface tap69502567-74 "external-ids:vm-id=\"cabadec0-abe3-46b6-b60a-cfbddeededc3\"" -- set Interface tap69502567-74 external-ids:iface-status=active
May  9 23:50:20 cmp02 kernel: [ 2027.922719] device tap69502567-74 entered promiscuous mode
May  9 23:50:20 cmp02 kernel: [ 2028.249683] audit: type=1400 audit(1525909820.410:51): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-cabadec0-abe3-46b6-b60a-cfbddeededc3" pid=9256 comm="apparmor_parser"
May  9 23:50:20 cmp02 libvirtd[5599]: 2018-05-09 23:50:20.417+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=5 name='instance-00000007' uuid=cabadec0-abe3-46b6-b60a-cfbddeededc3 is tainted: host-cpu
May  9 23:50:25 cmp02 kernel: [ 2033.621181] device tap3c9ea52c-d8 left promiscuous mode
May  9 23:50:26 cmp02 kernel: [ 2034.000392] audit: type=1400 audit(1525909826.160:52): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-69a002d3-a8d6-45e9-ab00-fe9442fa1ac2" pid=9336 comm="apparmor_parser"
May  9 23:50:26 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3c9ea52c-d8
May  9 23:50:26 cmp02 kernel: [ 2034.068339] device tap69502567-74 left promiscuous mode
May  9 23:50:26 cmp02 kernel: [ 2034.452780] audit: type=1400 audit(1525909826.612:53): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-cabadec0-abe3-46b6-b60a-cfbddeededc3" pid=9355 comm="apparmor_parser"
May  9 23:50:26 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap69502567-74
May  9 23:50:44 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:50:45 cmp02 kernel: [ 2053.135664] audit: type=1400 audit(1525909845.295:54): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-d78562a4-e4d0-4f1d-8e39-94a85ffdb222" pid=9446 comm="apparmor_parser"
May  9 23:50:45 cmp02 kernel: [ 2053.375495] audit: type=1400 audit(1525909845.535:55): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d78562a4-e4d0-4f1d-8e39-94a85ffdb222" pid=9449 comm="apparmor_parser"
May  9 23:50:45 cmp02 kernel: [ 2053.611650] audit: type=1400 audit(1525909845.771:56): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d78562a4-e4d0-4f1d-8e39-94a85ffdb222" pid=9452 comm="apparmor_parser"
May  9 23:50:46 cmp02 kernel: [ 2053.871066] audit: type=1400 audit(1525909846.030:57): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-d78562a4-e4d0-4f1d-8e39-94a85ffdb222" pid=9455 comm="apparmor_parser"
May  9 23:50:46 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap9cd47a32-e1 -- add-port br-int tap9cd47a32-e1 -- set Interface tap9cd47a32-e1 "external-ids:attached-mac=\"fa:16:3e:d8:9a:68\"" -- set Interface tap9cd47a32-e1 "external-ids:iface-id=\"9cd47a32-e1e0-4ba2-b046-2768b6002462\"" -- set Interface tap9cd47a32-e1 "external-ids:vm-id=\"d78562a4-e4d0-4f1d-8e39-94a85ffdb222\"" -- set Interface tap9cd47a32-e1 external-ids:iface-status=active
May  9 23:50:46 cmp02 kernel: [ 2053.901182] device tap9cd47a32-e1 entered promiscuous mode
May  9 23:50:46 cmp02 kernel: [ 2054.154294] audit: type=1400 audit(1525909846.314:58): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d78562a4-e4d0-4f1d-8e39-94a85ffdb222" pid=9523 comm="apparmor_parser"
May  9 23:50:46 cmp02 libvirtd[5599]: 2018-05-09 23:50:46.321+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=6 name='instance-00000008' uuid=d78562a4-e4d0-4f1d-8e39-94a85ffdb222 is tainted: host-cpu
May  9 23:51:02 cmp02 kernel: [ 2070.541248] device tap9cd47a32-e1 left promiscuous mode
May  9 23:51:03 cmp02 kernel: [ 2070.909519] audit: type=1400 audit(1525909863.068:59): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-d78562a4-e4d0-4f1d-8e39-94a85ffdb222" pid=9664 comm="apparmor_parser"
May  9 23:51:03 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap9cd47a32-e1
May  9 23:52:23 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:52:24 cmp02 kernel: [ 2152.601410] audit: type=1400 audit(1525909944.759:60): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-f5127732-a21b-4847-b950-52221d06cadc" pid=9756 comm="apparmor_parser"
May  9 23:52:25 cmp02 kernel: [ 2152.838955] audit: type=1400 audit(1525909944.997:61): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f5127732-a21b-4847-b950-52221d06cadc" pid=9759 comm="apparmor_parser"
May  9 23:52:25 cmp02 kernel: [ 2153.073345] audit: type=1400 audit(1525909945.231:62): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f5127732-a21b-4847-b950-52221d06cadc" pid=9762 comm="apparmor_parser"
May  9 23:52:25 cmp02 kernel: [ 2153.317942] audit: type=1400 audit(1525909945.476:63): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-f5127732-a21b-4847-b950-52221d06cadc" pid=9765 comm="apparmor_parser"
May  9 23:52:25 cmp02 systemd-udevd[9768]: Could not generate persistent MAC address for tap39f1d11a-57: No such file or directory
May  9 23:52:25 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap39f1d11a-57 -- add-port br-int tap39f1d11a-57 -- set Interface tap39f1d11a-57 "external-ids:attached-mac=\"fa:16:3e:1b:3b:d6\"" -- set Interface tap39f1d11a-57 "external-ids:iface-id=\"39f1d11a-573c-4c69-8c48-2f3124d9e44f\"" -- set Interface tap39f1d11a-57 "external-ids:vm-id=\"f5127732-a21b-4847-b950-52221d06cadc\"" -- set Interface tap39f1d11a-57 external-ids:iface-status=active
May  9 23:52:25 cmp02 kernel: [ 2153.353744] device tap39f1d11a-57 entered promiscuous mode
May  9 23:52:25 cmp02 kernel: [ 2153.577402] audit: type=1400 audit(1525909945.735:64): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f5127732-a21b-4847-b950-52221d06cadc" pid=9849 comm="apparmor_parser"
May  9 23:52:25 cmp02 libvirtd[5599]: 2018-05-09 23:52:25.745+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=7 name='instance-0000000a' uuid=f5127732-a21b-4847-b950-52221d06cadc is tainted: host-cpu
May  9 23:52:39 cmp02 kernel: [ 2167.810680] device tap39f1d11a-57 left promiscuous mode
May  9 23:52:40 cmp02 kernel: [ 2168.383984] audit: type=1400 audit(1525909960.541:65): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-f5127732-a21b-4847-b950-52221d06cadc" pid=10088 comm="apparmor_parser"
May  9 23:52:40 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap39f1d11a-57
May  9 23:53:51 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:53:53 cmp02 kernel: [ 2240.929848] audit: type=1400 audit(1525910033.086:66): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-741cb8d8-816c-4e31-8799-a366e93e80cb" pid=10182 comm="apparmor_parser"
May  9 23:53:53 cmp02 kernel: [ 2241.164268] audit: type=1400 audit(1525910033.320:67): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-741cb8d8-816c-4e31-8799-a366e93e80cb" pid=10185 comm="apparmor_parser"
May  9 23:53:53 cmp02 kernel: [ 2241.400111] audit: type=1400 audit(1525910033.556:68): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-741cb8d8-816c-4e31-8799-a366e93e80cb" pid=10188 comm="apparmor_parser"
May  9 23:53:53 cmp02 kernel: [ 2241.638296] audit: type=1400 audit(1525910033.794:69): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-741cb8d8-816c-4e31-8799-a366e93e80cb" pid=10191 comm="apparmor_parser"
May  9 23:53:53 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapf2c7e984-40 -- add-port br-int tapf2c7e984-40 -- set Interface tapf2c7e984-40 "external-ids:attached-mac=\"fa:16:3e:b2:0e:a2\"" -- set Interface tapf2c7e984-40 "external-ids:iface-id=\"f2c7e984-4038-4339-90d9-dc6475b6d20c\"" -- set Interface tapf2c7e984-40 "external-ids:vm-id=\"741cb8d8-816c-4e31-8799-a366e93e80cb\"" -- set Interface tapf2c7e984-40 external-ids:iface-status=active
May  9 23:53:53 cmp02 kernel: [ 2241.669294] device tapf2c7e984-40 entered promiscuous mode
May  9 23:53:54 cmp02 kernel: [ 2241.906139] audit: type=1400 audit(1525910034.062:70): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-741cb8d8-816c-4e31-8799-a366e93e80cb" pid=10250 comm="apparmor_parser"
May  9 23:53:54 cmp02 libvirtd[5599]: 2018-05-09 23:53:54.067+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=8 name='instance-0000000b' uuid=741cb8d8-816c-4e31-8799-a366e93e80cb is tainted: host-cpu
May  9 23:54:29 cmp02 kernel: [ 2277.767074] device tapf2c7e984-40 left promiscuous mode
May  9 23:54:30 cmp02 kernel: [ 2278.369616] audit: type=1400 audit(1525910070.525:71): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-741cb8d8-816c-4e31-8799-a366e93e80cb" pid=10401 comm="apparmor_parser"
May  9 23:54:30 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapf2c7e984-40
May  9 23:57:46 cmp02 kernel: [ 2474.194228] scsi host3: iSCSI Initiator over TCP/IP
May  9 23:57:47 cmp02 kernel: [ 2475.212179] scsi 3:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May  9 23:57:47 cmp02 kernel: [ 2475.257141] scsi 3:0:0:0: Attached scsi generic sg3 type 12
May  9 23:57:47 cmp02 kernel: [ 2475.258947] scsi 3:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May  9 23:57:47 cmp02 kernel: [ 2475.290207] sd 3:0:0:1: Attached scsi generic sg4 type 0
May  9 23:57:47 cmp02 kernel: [ 2475.292509] sd 3:0:0:1: [sdb] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
May  9 23:57:47 cmp02 kernel: [ 2475.292753] sd 3:0:0:1: [sdb] Write Protect is off
May  9 23:57:47 cmp02 kernel: [ 2475.292756] sd 3:0:0:1: [sdb] Mode Sense: 69 00 10 08
May  9 23:57:47 cmp02 kernel: [ 2475.293599] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May  9 23:57:47 cmp02 kernel: [ 2475.307228] GPT:Primary header thinks Alt. header is not at the end of the disk.
May  9 23:57:47 cmp02 kernel: [ 2475.307230] GPT:90111 != 2097151
May  9 23:57:47 cmp02 kernel: [ 2475.307230] GPT:Alternate GPT header not at the end of the disk.
May  9 23:57:47 cmp02 kernel: [ 2475.307231] GPT:90111 != 2097151
May  9 23:57:47 cmp02 kernel: [ 2475.307231] GPT: Use GNU Parted to correct GPT errors.
May  9 23:57:47 cmp02 kernel: [ 2475.307240]  sdb: sdb1 sdb15
May  9 23:57:47 cmp02 kernel: [ 2475.309711] sd 3:0:0:1: [sdb] Attached SCSI disk
May  9 23:57:47 cmp02 iscsid: Connection4:0 to [target: iqn.2010-10.org.openstack:volume-fb3d0d54-b13f-4f3e-ac36-eda1d2819834, portal: 192.168.11.42,3260] through [iface: default] is operational now
May  9 23:57:47 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session4/target3:0:0/3:0:0:1/block/sdb
May  9 23:57:47 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session4/target3:0:0/3:0:0:1/block/sdb
May  9 23:57:47 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:57:48 cmp02 kernel: [ 2476.700085] audit: type=1400 audit(1525910268.852:72): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-5115dce8-8fd9-481b-8c90-92f7bc1ad798" pid=10559 comm="apparmor_parser"
May  9 23:57:49 cmp02 kernel: [ 2476.950992] audit: type=1400 audit(1525910269.103:73): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-5115dce8-8fd9-481b-8c90-92f7bc1ad798" pid=10562 comm="apparmor_parser"
May  9 23:57:49 cmp02 kernel: [ 2477.188466] audit: type=1400 audit(1525910269.340:74): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-5115dce8-8fd9-481b-8c90-92f7bc1ad798" pid=10565 comm="apparmor_parser"
May  9 23:57:49 cmp02 kernel: [ 2477.429604] audit: type=1400 audit(1525910269.581:75): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-5115dce8-8fd9-481b-8c90-92f7bc1ad798" pid=10568 comm="apparmor_parser"
May  9 23:57:49 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap8ab21223-7f -- add-port br-int tap8ab21223-7f -- set Interface tap8ab21223-7f "external-ids:attached-mac=\"fa:16:3e:4d:53:b4\"" -- set Interface tap8ab21223-7f "external-ids:iface-id=\"8ab21223-7f31-4b9d-9c6d-2fb0734d7a78\"" -- set Interface tap8ab21223-7f "external-ids:vm-id=\"5115dce8-8fd9-481b-8c90-92f7bc1ad798\"" -- set Interface tap8ab21223-7f external-ids:iface-status=active
May  9 23:57:49 cmp02 kernel: [ 2477.453003] device tap8ab21223-7f entered promiscuous mode
May  9 23:57:49 cmp02 kernel: [ 2477.679078] audit: type=1400 audit(1525910269.831:76): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-5115dce8-8fd9-481b-8c90-92f7bc1ad798" pid=10625 comm="apparmor_parser"
May  9 23:57:49 cmp02 libvirtd[5599]: 2018-05-09 23:57:49.838+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=9 name='instance-00000010' uuid=5115dce8-8fd9-481b-8c90-92f7bc1ad798 is tainted: host-cpu
May  9 23:57:52 cmp02 kernel: [ 2480.765431] GPT:Primary header thinks Alt. header is not at the end of the disk.
May  9 23:57:52 cmp02 kernel: [ 2480.765433] GPT:90111 != 2097151
May  9 23:57:52 cmp02 kernel: [ 2480.765433] GPT:Alternate GPT header not at the end of the disk.
May  9 23:57:52 cmp02 kernel: [ 2480.765434] GPT:90111 != 2097151
May  9 23:57:52 cmp02 kernel: [ 2480.765434] GPT: Use GNU Parted to correct GPT errors.
May  9 23:57:52 cmp02 kernel: [ 2480.765443]  sdb: sdb1 sdb15
May  9 23:57:52 cmp02 kernel: [ 2480.782004] device tap8ab21223-7f left promiscuous mode
May  9 23:57:52 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session4/target3:0:0/3:0:0:1/block/sdb
May  9 23:57:52 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session4/target3:0:0/3:0:0:1/block/sdb
May  9 23:57:53 cmp02 kernel: [ 2481.370420] audit: type=1400 audit(1525910273.522:77): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-5115dce8-8fd9-481b-8c90-92f7bc1ad798" pid=10726 comm="apparmor_parser"
May  9 23:57:53 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap8ab21223-7f
May  9 23:57:53 cmp02 kernel: [ 2481.585988] sd 3:0:0:1: [sdb] Synchronizing SCSI cache
May  9 23:57:54 cmp02 iscsid: Connection4:0 to [target: iqn.2010-10.org.openstack:volume-fb3d0d54-b13f-4f3e-ac36-eda1d2819834, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May  9 23:57:56 cmp02 kernel: [ 2484.446495]  connection2:0: detected conn error (1020)
May  9 23:57:57 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May  9 23:58:24 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:58:25 cmp02 kernel: [ 2513.686324] audit: type=1400 audit(1525910305.837:78): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-93abbbb3-075f-408e-9ab7-095bb08b5f82" pid=10824 comm="apparmor_parser"
May  9 23:58:26 cmp02 kernel: [ 2513.932253] audit: type=1400 audit(1525910306.083:79): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-93abbbb3-075f-408e-9ab7-095bb08b5f82" pid=10827 comm="apparmor_parser"
May  9 23:58:26 cmp02 kernel: [ 2514.179227] audit: type=1400 audit(1525910306.330:80): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-93abbbb3-075f-408e-9ab7-095bb08b5f82" pid=10830 comm="apparmor_parser"
May  9 23:58:26 cmp02 kernel: [ 2514.416016] audit: type=1400 audit(1525910306.567:81): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-93abbbb3-075f-408e-9ab7-095bb08b5f82" pid=10833 comm="apparmor_parser"
May  9 23:58:26 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapbd71b7c0-2b -- add-port br-int tapbd71b7c0-2b -- set Interface tapbd71b7c0-2b "external-ids:attached-mac=\"fa:16:3e:7d:82:42\"" -- set Interface tapbd71b7c0-2b "external-ids:iface-id=\"bd71b7c0-2b8f-45b1-ba5e-126b93c2c2a1\"" -- set Interface tapbd71b7c0-2b "external-ids:vm-id=\"93abbbb3-075f-408e-9ab7-095bb08b5f82\"" -- set Interface tapbd71b7c0-2b external-ids:iface-status=active
May  9 23:58:26 cmp02 kernel: [ 2514.468745] device tapbd71b7c0-2b entered promiscuous mode
May  9 23:58:26 cmp02 kernel: [ 2514.701205] audit: type=1400 audit(1525910306.852:82): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-93abbbb3-075f-408e-9ab7-095bb08b5f82" pid=10935 comm="apparmor_parser"
May  9 23:58:26 cmp02 libvirtd[5599]: 2018-05-09 23:58:26.858+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=10 name='instance-00000011' uuid=93abbbb3-075f-408e-9ab7-095bb08b5f82 is tainted: host-cpu
May  9 23:58:28 cmp02 systemd[1]: Started Daemon for generating UUIDs.
May  9 23:58:29 cmp02 kernel: [ 2517.543261] device tapbd71b7c0-2b left promiscuous mode
May  9 23:58:30 cmp02 kernel: [ 2517.907059] audit: type=1400 audit(1525910310.058:83): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-93abbbb3-075f-408e-9ab7-095bb08b5f82" pid=10983 comm="apparmor_parser"
May  9 23:58:30 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapbd71b7c0-2b
May  9 23:58:34 cmp02 ceilometer-agent-compute[7523]: libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '93abbbb3-075f-408e-9ab7-095bb08b5f82'
May  9 23:58:34 cmp02 ceilometer-agent-compute[7523]: message repeated 6 times: [ libvirt: QEMU Driver error : Domain not found: no domain with matching uuid '93abbbb3-075f-408e-9ab7-095bb08b5f82']
May  9 23:59:32 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:59:33 cmp02 kernel: [ 2581.577109] audit: type=1400 audit(1525910373.726:84): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11071 comm="apparmor_parser"
May  9 23:59:33 cmp02 kernel: [ 2581.817888] audit: type=1400 audit(1525910373.967:85): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11074 comm="apparmor_parser"
May  9 23:59:34 cmp02 kernel: [ 2582.051425] audit: type=1400 audit(1525910374.201:86): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11079 comm="apparmor_parser"
May  9 23:59:34 cmp02 kernel: [ 2582.302718] audit: type=1400 audit(1525910374.452:87): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11086 comm="apparmor_parser"
May  9 23:59:34 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapc75c1ea8-b9 -- add-port br-int tapc75c1ea8-b9 -- set Interface tapc75c1ea8-b9 "external-ids:attached-mac=\"fa:16:3e:41:9e:d7\"" -- set Interface tapc75c1ea8-b9 "external-ids:iface-id=\"c75c1ea8-b9d4-4fb7-835f-fad5ff318638\"" -- set Interface tapc75c1ea8-b9 "external-ids:vm-id=\"7f3b9a35-b529-44f4-ae0f-120b14b74a67\"" -- set Interface tapc75c1ea8-b9 external-ids:iface-status=active
May  9 23:59:34 cmp02 kernel: [ 2582.335465] device tapc75c1ea8-b9 entered promiscuous mode
May  9 23:59:34 cmp02 kernel: [ 2582.577889] audit: type=1400 audit(1525910374.727:88): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11175 comm="apparmor_parser"
May  9 23:59:34 cmp02 libvirtd[5599]: 2018-05-09 23:59:34.735+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=11 name='instance-00000013' uuid=7f3b9a35-b529-44f4-ae0f-120b14b74a67 is tainted: host-cpu
May  9 23:59:54 cmp02 kernel: [ 2602.251957] device tapc75c1ea8-b9 left promiscuous mode
May  9 23:59:54 cmp02 kernel: [ 2602.632463] audit: type=1400 audit(1525910394.781:89): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11314 comm="apparmor_parser"
May  9 23:59:54 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapc75c1ea8-b9
May  9 23:59:55 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May  9 23:59:55 cmp02 kernel: [ 2603.715140] audit: type=1400 audit(1525910395.864:90): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11372 comm="apparmor_parser"
May  9 23:59:56 cmp02 kernel: [ 2603.953953] audit: type=1400 audit(1525910396.103:91): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11375 comm="apparmor_parser"
May  9 23:59:56 cmp02 kernel: [ 2604.186632] audit: type=1400 audit(1525910396.336:92): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11378 comm="apparmor_parser"
May  9 23:59:56 cmp02 kernel: [ 2604.426679] audit: type=1400 audit(1525910396.576:93): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11381 comm="apparmor_parser"
May  9 23:59:56 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapc75c1ea8-b9 -- add-port br-int tapc75c1ea8-b9 -- set Interface tapc75c1ea8-b9 "external-ids:attached-mac=\"fa:16:3e:41:9e:d7\"" -- set Interface tapc75c1ea8-b9 "external-ids:iface-id=\"c75c1ea8-b9d4-4fb7-835f-fad5ff318638\"" -- set Interface tapc75c1ea8-b9 "external-ids:vm-id=\"7f3b9a35-b529-44f4-ae0f-120b14b74a67\"" -- set Interface tapc75c1ea8-b9 external-ids:iface-status=active
May  9 23:59:56 cmp02 kernel: [ 2604.470190] device tapc75c1ea8-b9 entered promiscuous mode
May  9 23:59:56 cmp02 kernel: [ 2604.709870] audit: type=1400 audit(1525910396.859:94): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11456 comm="apparmor_parser"
May  9 23:59:56 cmp02 libvirtd[5599]: 2018-05-09 23:59:56.866+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=12 name='instance-00000013' uuid=7f3b9a35-b529-44f4-ae0f-120b14b74a67 is tainted: host-cpu
May 10 00:00:13 cmp02 kernel: [ 2621.722865] device tapc75c1ea8-b9 left promiscuous mode
May 10 00:00:14 cmp02 kernel: [ 2622.112033] audit: type=1400 audit(1525910414.260:95): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-7f3b9a35-b529-44f4-ae0f-120b14b74a67" pid=11534 comm="apparmor_parser"
May 10 00:00:14 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapc75c1ea8-b9
May 10 00:07:15 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 00:07:15 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 00:07:15 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1199 seconds.
May 10 00:08:47 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:08:48 cmp02 kernel: [ 3136.372397] audit: type=1400 audit(1525910928.510:96): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-48981344-fe22-4555-afeb-3beccc280371" pid=11958 comm="apparmor_parser"
May 10 00:08:48 cmp02 kernel: [ 3136.620826] audit: type=1400 audit(1525910928.758:97): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-48981344-fe22-4555-afeb-3beccc280371" pid=11961 comm="apparmor_parser"
May 10 00:08:48 cmp02 kernel: [ 3136.853291] audit: type=1400 audit(1525910928.990:98): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-48981344-fe22-4555-afeb-3beccc280371" pid=11964 comm="apparmor_parser"
May 10 00:08:49 cmp02 kernel: [ 3137.102700] audit: type=1400 audit(1525910929.240:99): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-48981344-fe22-4555-afeb-3beccc280371" pid=11967 comm="apparmor_parser"
May 10 00:08:49 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap8109a86e-67 -- add-port br-int tap8109a86e-67 -- set Interface tap8109a86e-67 "external-ids:attached-mac=\"fa:16:3e:6c:65:76\"" -- set Interface tap8109a86e-67 "external-ids:iface-id=\"8109a86e-6738-4cb4-b795-bd445127caa3\"" -- set Interface tap8109a86e-67 "external-ids:vm-id=\"48981344-fe22-4555-afeb-3beccc280371\"" -- set Interface tap8109a86e-67 external-ids:iface-status=active
May 10 00:08:49 cmp02 kernel: [ 3137.135565] device tap8109a86e-67 entered promiscuous mode
May 10 00:08:49 cmp02 kernel: [ 3137.400180] audit: type=1400 audit(1525910929.537:100): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-48981344-fe22-4555-afeb-3beccc280371" pid=12031 comm="apparmor_parser"
May 10 00:08:49 cmp02 libvirtd[5599]: 2018-05-10 00:08:49.543+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=13 name='instance-00000017' uuid=48981344-fe22-4555-afeb-3beccc280371 is tainted: host-cpu
May 10 00:09:03 cmp02 kernel: [ 3151.605026] device tap8109a86e-67 left promiscuous mode
May 10 00:09:04 cmp02 kernel: [ 3152.000410] audit: type=1400 audit(1525910944.137:101): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-48981344-fe22-4555-afeb-3beccc280371" pid=12194 comm="apparmor_parser"
May 10 00:09:04 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap8109a86e-67
May 10 00:09:35 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:09:37 cmp02 kernel: [ 3184.908245] audit: type=1400 audit(1525910977.044:102): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-c81d15b2-3cd6-4724-9c82-571ef88aa1fa" pid=12333 comm="apparmor_parser"
May 10 00:09:37 cmp02 kernel: [ 3185.143925] audit: type=1400 audit(1525910977.280:103): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c81d15b2-3cd6-4724-9c82-571ef88aa1fa" pid=12336 comm="apparmor_parser"
May 10 00:09:37 cmp02 kernel: [ 3185.387542] audit: type=1400 audit(1525910977.524:104): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c81d15b2-3cd6-4724-9c82-571ef88aa1fa" pid=12339 comm="apparmor_parser"
May 10 00:09:37 cmp02 kernel: [ 3185.633828] audit: type=1400 audit(1525910977.770:105): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-c81d15b2-3cd6-4724-9c82-571ef88aa1fa" pid=12342 comm="apparmor_parser"
May 10 00:09:37 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapb18b7add-8b -- add-port br-int tapb18b7add-8b -- set Interface tapb18b7add-8b "external-ids:attached-mac=\"fa:16:3e:65:0c:57\"" -- set Interface tapb18b7add-8b "external-ids:iface-id=\"b18b7add-8b6e-43b3-b174-db193db6f47b\"" -- set Interface tapb18b7add-8b "external-ids:vm-id=\"c81d15b2-3cd6-4724-9c82-571ef88aa1fa\"" -- set Interface tapb18b7add-8b external-ids:iface-status=active
May 10 00:09:37 cmp02 kernel: [ 3185.668523] device tapb18b7add-8b entered promiscuous mode
May 10 00:09:38 cmp02 kernel: [ 3185.898032] audit: type=1400 audit(1525910978.034:106): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c81d15b2-3cd6-4724-9c82-571ef88aa1fa" pid=12426 comm="apparmor_parser"
May 10 00:09:38 cmp02 libvirtd[5599]: 2018-05-10 00:09:38.040+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=14 name='instance-00000018' uuid=c81d15b2-3cd6-4724-9c82-571ef88aa1fa is tainted: host-cpu
May 10 00:12:08 cmp02 kernel: [ 3336.780987] device tapb18b7add-8b left promiscuous mode
May 10 00:12:09 cmp02 kernel: [ 3337.364350] audit: type=1400 audit(1525911129.498:107): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-c81d15b2-3cd6-4724-9c82-571ef88aa1fa" pid=12616 comm="apparmor_parser"
May 10 00:12:09 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapb18b7add-8b
May 10 00:12:50 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:12:51 cmp02 kernel: [ 3379.471057] audit: type=1400 audit(1525911171.604:108): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-c1934203-f9ec-40be-bd19-ec9a318e5d19" pid=12704 comm="apparmor_parser"
May 10 00:12:51 cmp02 kernel: [ 3379.720790] audit: type=1400 audit(1525911171.854:109): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c1934203-f9ec-40be-bd19-ec9a318e5d19" pid=12710 comm="apparmor_parser"
May 10 00:12:52 cmp02 kernel: [ 3379.966822] audit: type=1400 audit(1525911172.100:110): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c1934203-f9ec-40be-bd19-ec9a318e5d19" pid=12713 comm="apparmor_parser"
May 10 00:12:52 cmp02 kernel: [ 3380.212838] audit: type=1400 audit(1525911172.346:111): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-c1934203-f9ec-40be-bd19-ec9a318e5d19" pid=12716 comm="apparmor_parser"
May 10 00:12:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap8896cd2b-23 -- add-port br-int tap8896cd2b-23 -- set Interface tap8896cd2b-23 "external-ids:attached-mac=\"fa:16:3e:ab:e0:26\"" -- set Interface tap8896cd2b-23 "external-ids:iface-id=\"8896cd2b-2318-4474-8e58-592c54f348eb\"" -- set Interface tap8896cd2b-23 "external-ids:vm-id=\"c1934203-f9ec-40be-bd19-ec9a318e5d19\"" -- set Interface tap8896cd2b-23 external-ids:iface-status=active
May 10 00:12:52 cmp02 kernel: [ 3380.248157] device tap8896cd2b-23 entered promiscuous mode
May 10 00:12:52 cmp02 kernel: [ 3380.494822] audit: type=1400 audit(1525911172.628:112): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c1934203-f9ec-40be-bd19-ec9a318e5d19" pid=12815 comm="apparmor_parser"
May 10 00:12:52 cmp02 libvirtd[5599]: 2018-05-10 00:12:52.634+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=15 name='instance-0000001a' uuid=c1934203-f9ec-40be-bd19-ec9a318e5d19 is tainted: host-cpu
May 10 00:12:54 cmp02 kernel: [ 3382.756572] device tap8896cd2b-23 left promiscuous mode
May 10 00:12:55 cmp02 kernel: [ 3383.127966] audit: type=1400 audit(1525911175.261:113): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-c1934203-f9ec-40be-bd19-ec9a318e5d19" pid=12872 comm="apparmor_parser"
May 10 00:12:55 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap8896cd2b-23
May 10 00:16:45 cmp02 salt-minion[2824]: [INFO    ] Running scheduled job: __mine_interval
May 10 00:17:01 cmp02 CRON[12933]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 10 00:27:14 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 00:27:14 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 00:27:14 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1563 seconds.
May 10 00:32:24 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:32:26 cmp02 kernel: [ 4554.304371] audit: type=1400 audit(1525912346.421:114): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c" pid=13092 comm="apparmor_parser"
May 10 00:32:26 cmp02 kernel: [ 4554.560629] audit: type=1400 audit(1525912346.677:115): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c" pid=13095 comm="apparmor_parser"
May 10 00:32:26 cmp02 kernel: [ 4554.802008] audit: type=1400 audit(1525912346.918:116): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c" pid=13098 comm="apparmor_parser"
May 10 00:32:27 cmp02 kernel: [ 4555.053023] audit: type=1400 audit(1525912347.169:117): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c" pid=13101 comm="apparmor_parser"
May 10 00:32:27 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap905a6fcb-cf -- add-port br-int tap905a6fcb-cf -- set Interface tap905a6fcb-cf "external-ids:attached-mac=\"fa:16:3e:ef:dd:7c\"" -- set Interface tap905a6fcb-cf "external-ids:iface-id=\"905a6fcb-cf26-4a11-b7d9-eab44fa9f6fe\"" -- set Interface tap905a6fcb-cf "external-ids:vm-id=\"3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c\"" -- set Interface tap905a6fcb-cf external-ids:iface-status=active
May 10 00:32:27 cmp02 kernel: [ 4555.087307] device tap905a6fcb-cf entered promiscuous mode
May 10 00:32:27 cmp02 kernel: [ 4555.360723] audit: type=1400 audit(1525912347.477:118): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c" pid=13185 comm="apparmor_parser"
May 10 00:32:27 cmp02 libvirtd[5599]: 2018-05-10 00:32:27.483+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=16 name='instance-0000001d' uuid=3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c is tainted: host-cpu
May 10 00:32:36 cmp02 kernel: [ 4564.277535] device tap905a6fcb-cf left promiscuous mode
May 10 00:32:36 cmp02 kernel: [ 4564.663119] audit: type=1400 audit(1525912356.779:119): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-3d3576c3-74a4-4d93-acc0-2cd31cfa6a9c" pid=13338 comm="apparmor_parser"
May 10 00:32:36 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap905a6fcb-cf
May 10 00:32:58 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:32:59 cmp02 kernel: [ 4587.434078] audit: type=1400 audit(1525912379.550:120): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13414 comm="apparmor_parser"
May 10 00:32:59 cmp02 kernel: [ 4587.685576] audit: type=1400 audit(1525912379.801:121): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13417 comm="apparmor_parser"
May 10 00:33:00 cmp02 kernel: [ 4587.946276] audit: type=1400 audit(1525912380.062:122): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13420 comm="apparmor_parser"
May 10 00:33:00 cmp02 kernel: [ 4588.209230] audit: type=1400 audit(1525912380.325:123): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13423 comm="apparmor_parser"
May 10 00:33:00 cmp02 systemd-udevd[13426]: Could not generate persistent MAC address for tape70b0d7d-7f: No such file or directory
May 10 00:33:00 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tape70b0d7d-7f -- add-port br-int tape70b0d7d-7f -- set Interface tape70b0d7d-7f "external-ids:attached-mac=\"fa:16:3e:cb:d7:6f\"" -- set Interface tape70b0d7d-7f "external-ids:iface-id=\"e70b0d7d-7f13-4377-8fa4-cc096db8fd9d\"" -- set Interface tape70b0d7d-7f "external-ids:vm-id=\"c9264882-d3ad-4b4a-b5ca-8a39181e9844\"" -- set Interface tape70b0d7d-7f external-ids:iface-status=active
May 10 00:33:00 cmp02 kernel: [ 4588.248205] device tape70b0d7d-7f entered promiscuous mode
May 10 00:33:00 cmp02 kernel: [ 4588.505975] audit: type=1400 audit(1525912380.622:124): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13466 comm="apparmor_parser"
May 10 00:33:00 cmp02 libvirtd[5599]: 2018-05-10 00:33:00.628+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=17 name='instance-0000001e' uuid=c9264882-d3ad-4b4a-b5ca-8a39181e9844 is tainted: host-cpu
May 10 00:33:08 cmp02 kernel: [ 4596.725897]  connection2:0: detected conn error (1020)
May 10 00:33:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:33:09 cmp02 kernel: [ 4597.732432] scsi host3: iSCSI Initiator over TCP/IP
May 10 00:33:10 cmp02 kernel: [ 4598.747234] scsi 3:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May 10 00:33:10 cmp02 kernel: [ 4598.781587] scsi 3:0:0:0: Attached scsi generic sg3 type 12
May 10 00:33:10 cmp02 kernel: [ 4598.783575] scsi 3:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May 10 00:33:10 cmp02 kernel: [ 4598.825037] sd 3:0:0:1: Attached scsi generic sg4 type 0
May 10 00:33:10 cmp02 kernel: [ 4598.826918] sd 3:0:0:1: [sdb] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
May 10 00:33:10 cmp02 kernel: [ 4598.827393] sd 3:0:0:1: [sdb] Write Protect is off
May 10 00:33:10 cmp02 kernel: [ 4598.827396] sd 3:0:0:1: [sdb] Mode Sense: 69 00 10 08
May 10 00:33:10 cmp02 kernel: [ 4598.828610] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 10 00:33:10 cmp02 kernel: [ 4598.837347] sd 3:0:0:1: [sdb] Attached SCSI disk
May 10 00:33:11 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session5/target3:0:0/3:0:0:1/block/sdb
May 10 00:33:11 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session5/target3:0:0/3:0:0:1/block/sdb
May 10 00:33:11 cmp02 iscsid: Connection5:0 to [target: iqn.2010-10.org.openstack:volume-bccc0ad1-c1da-4a9e-8f2e-c47ded507058, portal: 192.168.11.42,3260] through [iface: default] is operational now
May 10 00:33:11 cmp02 kernel: [ 4599.206444] audit: type=1400 audit(1525912391.322:125): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13612 comm="apparmor_parser"
May 10 00:33:12 cmp02 kernel: [ 4600.249088]  connection2:0: detected conn error (1020)
May 10 00:33:13 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:33:15 cmp02 kernel: [ 4603.266539]  connection2:0: detected conn error (1020)
May 10 00:33:18 cmp02 kernel: [ 4606.274990]  connection2:0: detected conn error (1020)
May 10 00:33:21 cmp02 kernel: [ 4609.281981]  connection2:0: detected conn error (1020)
May 10 00:33:23 cmp02 kernel: [ 4611.324703] device tape70b0d7d-7f left promiscuous mode
May 10 00:33:22 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 00:33:23 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session5/target3:0:0/3:0:0:1/block/sdb
May 10 00:33:23 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session5/target3:0:0/3:0:0:1/block/sdb
May 10 00:33:23 cmp02 kernel: [ 4611.705506] audit: type=1400 audit(1525912403.821:126): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-c9264882-d3ad-4b4a-b5ca-8a39181e9844" pid=13713 comm="apparmor_parser"
May 10 00:33:23 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tape70b0d7d-7f
May 10 00:33:24 cmp02 kernel: [ 4612.297528]  connection2:0: detected conn error (1020)
May 10 00:33:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:33:25 cmp02 kernel: [ 4613.877734] sd 3:0:0:1: [sdb] Synchronizing SCSI cache
May 10 00:33:27 cmp02 iscsid: Connection5:0 to [target: iqn.2010-10.org.openstack:volume-bccc0ad1-c1da-4a9e-8f2e-c47ded507058, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May 10 00:33:27 cmp02 kernel: [ 4615.499107]  connection2:0: detected conn error (1020)
May 10 00:33:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:33:30 cmp02 kernel: [ 4618.509214]  connection2:0: detected conn error (1020)
May 10 00:33:33 cmp02 kernel: [ 4621.518902]  connection2:0: detected conn error (1020)
May 10 00:33:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:33:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:34:45 cmp02 kernel: [ 4693.174667] scsi host3: iSCSI Initiator over TCP/IP
May 10 00:34:46 cmp02 kernel: [ 4693.937287]  connection2:0: detected conn error (1020)
May 10 00:34:46 cmp02 kernel: [ 4694.191111] scsi 3:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May 10 00:34:46 cmp02 kernel: [ 4694.226822] scsi 3:0:0:0: Attached scsi generic sg3 type 12
May 10 00:34:46 cmp02 kernel: [ 4694.231112] scsi 3:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May 10 00:34:46 cmp02 kernel: [ 4694.275633] sd 3:0:0:1: Attached scsi generic sg4 type 0
May 10 00:34:46 cmp02 kernel: [ 4694.278579] sd 3:0:0:1: [sdb] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
May 10 00:34:46 cmp02 kernel: [ 4694.278941] sd 3:0:0:1: [sdb] Write Protect is off
May 10 00:34:46 cmp02 kernel: [ 4694.278945] sd 3:0:0:1: [sdb] Mode Sense: 69 00 10 08
May 10 00:34:46 cmp02 kernel: [ 4694.279569] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 10 00:34:46 cmp02 kernel: [ 4694.290109] GPT:Primary header thinks Alt. header is not at the end of the disk.
May 10 00:34:46 cmp02 kernel: [ 4694.290110] GPT:90111 != 20971519
May 10 00:34:46 cmp02 kernel: [ 4694.290111] GPT:Alternate GPT header not at the end of the disk.
May 10 00:34:46 cmp02 kernel: [ 4694.290111] GPT:90111 != 20971519
May 10 00:34:46 cmp02 kernel: [ 4694.290112] GPT: Use GNU Parted to correct GPT errors.
May 10 00:34:46 cmp02 kernel: [ 4694.290120]  sdb: sdb1 sdb15
May 10 00:34:46 cmp02 kernel: [ 4694.292442] sd 3:0:0:1: [sdb] Attached SCSI disk
May 10 00:34:46 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session6/target3:0:0/3:0:0:1/block/sdb
May 10 00:34:46 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session6/target3:0:0/3:0:0:1/block/sdb
May 10 00:34:46 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:34:47 cmp02 iscsid: Connection6:0 to [target: iqn.2010-10.org.openstack:volume-e6a2f1a5-abf6-4f32-a666-af47611879a4, portal: 192.168.11.42,3260] through [iface: default] is operational now
May 10 00:34:47 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:34:48 cmp02 kernel: [ 4696.380071] audit: type=1400 audit(1525912488.494:127): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-b9811a5c-59c4-4255-8dba-cf6a93efc975" pid=13824 comm="apparmor_parser"
May 10 00:34:48 cmp02 kernel: [ 4696.618767] audit: type=1400 audit(1525912488.732:128): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-b9811a5c-59c4-4255-8dba-cf6a93efc975" pid=13827 comm="apparmor_parser"
May 10 00:34:48 cmp02 kernel: [ 4696.870497] audit: type=1400 audit(1525912488.984:129): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-b9811a5c-59c4-4255-8dba-cf6a93efc975" pid=13830 comm="apparmor_parser"
May 10 00:34:49 cmp02 kernel: [ 4696.948487]  connection2:0: detected conn error (1020)
May 10 00:34:49 cmp02 kernel: [ 4697.128080] audit: type=1400 audit(1525912489.241:130): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-b9811a5c-59c4-4255-8dba-cf6a93efc975" pid=13833 comm="apparmor_parser"
May 10 00:34:49 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapf3951115-ea -- add-port br-int tapf3951115-ea -- set Interface tapf3951115-ea "external-ids:attached-mac=\"fa:16:3e:d1:56:fe\"" -- set Interface tapf3951115-ea "external-ids:iface-id=\"f3951115-ea79-4439-9bf4-68934b8bf72c\"" -- set Interface tapf3951115-ea "external-ids:vm-id=\"b9811a5c-59c4-4255-8dba-cf6a93efc975\"" -- set Interface tapf3951115-ea external-ids:iface-status=active
May 10 00:34:49 cmp02 kernel: [ 4697.155725] device tapf3951115-ea entered promiscuous mode
May 10 00:34:49 cmp02 kernel: [ 4697.414536] audit: type=1400 audit(1525912489.528:131): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-b9811a5c-59c4-4255-8dba-cf6a93efc975" pid=13882 comm="apparmor_parser"
May 10 00:34:49 cmp02 libvirtd[5599]: 2018-05-10 00:34:49.535+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=18 name='instance-0000001f' uuid=b9811a5c-59c4-4255-8dba-cf6a93efc975 is tainted: host-cpu
May 10 00:34:50 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:34:52 cmp02 kernel: [ 4699.954049]  connection2:0: detected conn error (1020)
May 10 00:34:55 cmp02 kernel: [ 4702.960862]  connection2:0: detected conn error (1020)
May 10 00:34:58 cmp02 kernel: [ 4705.979162]  connection2:0: detected conn error (1020)
May 10 00:34:59 cmp02 kernel: [ 4707.844466]  sdb: sdb1 sdb15
May 10 00:34:59 cmp02 kernel: [ 4707.855388] device tapf3951115-ea left promiscuous mode
May 10 00:34:59 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 00:35:00 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session6/target3:0:0/3:0:0:1/block/sdb
May 10 00:35:00 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session6/target3:0:0/3:0:0:1/block/sdb
May 10 00:35:00 cmp02 kernel: [ 4708.266895] audit: type=1400 audit(1525912500.380:132): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-b9811a5c-59c4-4255-8dba-cf6a93efc975" pid=14006 comm="apparmor_parser"
May 10 00:35:00 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapf3951115-ea
May 10 00:35:00 cmp02 kernel: [ 4708.508572] sd 3:0:0:1: [sdb] Synchronizing SCSI cache
May 10 00:35:01 cmp02 kernel: [ 4709.129023]  connection2:0: detected conn error (1020)
May 10 00:35:01 cmp02 iscsid: Connection6:0 to [target: iqn.2010-10.org.openstack:volume-e6a2f1a5-abf6-4f32-a666-af47611879a4, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May 10 00:35:02 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:36:30 cmp02 kernel: [ 4798.591709]  connection2:0: detected conn error (1020)
May 10 00:36:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:37:53 cmp02 systemd[1]: Created slice User Slice of nova.
May 10 00:37:53 cmp02 systemd[1]: Starting User Manager for UID 303...
May 10 00:37:53 cmp02 systemd[1]: Started Session 3 of user nova.
May 10 00:37:53 cmp02 systemd[14082]: Reached target Paths.
May 10 00:37:53 cmp02 systemd[14082]: Reached target Timers.
May 10 00:37:53 cmp02 systemd[14082]: Reached target Sockets.
May 10 00:37:53 cmp02 systemd[14082]: Reached target Basic System.
May 10 00:37:53 cmp02 systemd[14082]: Reached target Default.
May 10 00:37:53 cmp02 systemd[14082]: Startup finished in 28ms.
May 10 00:37:53 cmp02 systemd[1]: Started User Manager for UID 303.
May 10 00:37:54 cmp02 systemd[1]: Stopping User Manager for UID 303...
May 10 00:37:54 cmp02 systemd[14082]: Reached target Shutdown.
May 10 00:37:54 cmp02 systemd[14082]: Starting Exit the Session...
May 10 00:37:54 cmp02 systemd[14082]: Stopped target Default.
May 10 00:37:54 cmp02 systemd[14082]: Stopped target Basic System.
May 10 00:37:54 cmp02 systemd[14082]: Stopped target Sockets.
May 10 00:37:54 cmp02 systemd[14082]: Stopped target Timers.
May 10 00:37:54 cmp02 systemd[14082]: Stopped target Paths.
May 10 00:37:54 cmp02 systemd[14082]: Received SIGRTMIN+24 from PID 14158 (kill).
May 10 00:37:54 cmp02 systemd[1]: Stopped User Manager for UID 303.
May 10 00:37:54 cmp02 systemd[1]: Removed slice User Slice of nova.
May 10 00:38:32 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:38:33 cmp02 kernel: [ 4921.234569] audit: type=1400 audit(1525912713.344:133): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-4b8f774d-389f-498a-8535-573827486a3f" pid=14216 comm="apparmor_parser"
May 10 00:38:33 cmp02 kernel: [ 4921.502988] audit: type=1400 audit(1525912713.612:134): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-4b8f774d-389f-498a-8535-573827486a3f" pid=14219 comm="apparmor_parser"
May 10 00:38:33 cmp02 kernel: [ 4921.753367] audit: type=1400 audit(1525912713.863:135): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-4b8f774d-389f-498a-8535-573827486a3f" pid=14222 comm="apparmor_parser"
May 10 00:38:34 cmp02 kernel: [ 4922.006625] audit: type=1400 audit(1525912714.116:136): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-4b8f774d-389f-498a-8535-573827486a3f" pid=14225 comm="apparmor_parser"
May 10 00:38:34 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapf2fb6875-b7 -- add-port br-int tapf2fb6875-b7 -- set Interface tapf2fb6875-b7 "external-ids:attached-mac=\"fa:16:3e:11:39:14\"" -- set Interface tapf2fb6875-b7 "external-ids:iface-id=\"f2fb6875-b7f6-4e2c-9817-97259c34bd0b\"" -- set Interface tapf2fb6875-b7 "external-ids:vm-id=\"4b8f774d-389f-498a-8535-573827486a3f\"" -- set Interface tapf2fb6875-b7 external-ids:iface-status=active
May 10 00:38:34 cmp02 kernel: [ 4922.065071] device tapf2fb6875-b7 entered promiscuous mode
May 10 00:38:34 cmp02 kernel: [ 4922.321694] audit: type=1400 audit(1525912714.431:137): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-4b8f774d-389f-498a-8535-573827486a3f" pid=14316 comm="apparmor_parser"
May 10 00:38:34 cmp02 libvirtd[5599]: 2018-05-10 00:38:34.438+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=19 name='instance-00000023' uuid=4b8f774d-389f-498a-8535-573827486a3f is tainted: host-cpu
May 10 00:38:34 cmp02 libvirtd[5599]: 2018-05-10 00:38:34.616+0000: 5612: error : qemuDomainAgentAvailable:7147 : argument unsupported: QEMU guest agent is not configured
May 10 00:38:40 cmp02 kernel: [ 4927.947587] device tapf2fb6875-b7 left promiscuous mode
May 10 00:38:40 cmp02 kernel: [ 4928.340030] audit: type=1400 audit(1525912720.449:138): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-4b8f774d-389f-498a-8535-573827486a3f" pid=14379 comm="apparmor_parser"
May 10 00:38:40 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapf2fb6875-b7
May 10 00:39:08 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:39:09 cmp02 kernel: [ 4957.324708] audit: type=1400 audit(1525912749.434:139): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-df234469-ff7c-4a3f-a943-36205e15289d" pid=14453 comm="apparmor_parser"
May 10 00:39:09 cmp02 kernel: [ 4957.568080] audit: type=1400 audit(1525912749.677:140): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-df234469-ff7c-4a3f-a943-36205e15289d" pid=14456 comm="apparmor_parser"
May 10 00:39:09 cmp02 kernel: [ 4957.838791] audit: type=1400 audit(1525912749.948:141): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-df234469-ff7c-4a3f-a943-36205e15289d" pid=14459 comm="apparmor_parser"
May 10 00:39:10 cmp02 kernel: [ 4958.090087] audit: type=1400 audit(1525912750.199:142): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-df234469-ff7c-4a3f-a943-36205e15289d" pid=14462 comm="apparmor_parser"
May 10 00:39:10 cmp02 systemd-udevd[14465]: Could not generate persistent MAC address for tap35458f84-69: No such file or directory
May 10 00:39:10 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap35458f84-69 -- add-port br-int tap35458f84-69 -- set Interface tap35458f84-69 "external-ids:attached-mac=\"fa:16:3e:38:d2:42\"" -- set Interface tap35458f84-69 "external-ids:iface-id=\"35458f84-6939-41b8-ad00-08d17fa0db66\"" -- set Interface tap35458f84-69 "external-ids:vm-id=\"df234469-ff7c-4a3f-a943-36205e15289d\"" -- set Interface tap35458f84-69 external-ids:iface-status=active
May 10 00:39:10 cmp02 kernel: [ 4958.141980] device tap35458f84-69 entered promiscuous mode
May 10 00:39:10 cmp02 kernel: [ 4958.389326] audit: type=1400 audit(1525912750.498:143): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-df234469-ff7c-4a3f-a943-36205e15289d" pid=14557 comm="apparmor_parser"
May 10 00:39:10 cmp02 libvirtd[5599]: 2018-05-10 00:39:10.503+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=20 name='instance-00000024' uuid=df234469-ff7c-4a3f-a943-36205e15289d is tainted: host-cpu
May 10 00:39:14 cmp02 kernel: [ 4962.492303] device tap35458f84-69 left promiscuous mode
May 10 00:39:14 cmp02 kernel: [ 4962.870371] audit: type=1400 audit(1525912754.979:144): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-df234469-ff7c-4a3f-a943-36205e15289d" pid=14614 comm="apparmor_parser"
May 10 00:39:14 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap35458f84-69
May 10 00:43:26 cmp02 kernel: [ 5214.642185] audit: type=1400 audit(1525913006.746:145): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-a59d8165-c85f-43d8-8a7a-ba9ef88ac28a" pid=14960 comm="apparmor_parser"
May 10 00:43:26 cmp02 kernel: [ 5214.890149] audit: type=1400 audit(1525913006.994:146): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-a59d8165-c85f-43d8-8a7a-ba9ef88ac28a" pid=15004 comm="apparmor_parser"
May 10 00:43:27 cmp02 kernel: [ 5215.113018] audit: type=1400 audit(1525913007.217:147): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-a59d8165-c85f-43d8-8a7a-ba9ef88ac28a" pid=15020 comm="apparmor_parser"
May 10 00:43:27 cmp02 kernel: [ 5215.377488] audit: type=1400 audit(1525913007.481:148): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-a59d8165-c85f-43d8-8a7a-ba9ef88ac28a" pid=15035 comm="apparmor_parser"
May 10 00:43:27 cmp02 libvirtd[5599]: 2018-05-10 00:43:27.497+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=21 name='instance-00000028' uuid=a59d8165-c85f-43d8-8a7a-ba9ef88ac28a is tainted: host-cpu
May 10 00:43:27 cmp02 kernel: [ 5215.625605] audit: type=1400 audit(1525913007.729:149): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-8ba6e506-0122-4176-90fe-9baec01b43ef" pid=15068 comm="apparmor_parser"
May 10 00:43:27 cmp02 kernel: [ 5215.841223] audit: type=1400 audit(1525913007.945:150): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8ba6e506-0122-4176-90fe-9baec01b43ef" pid=15078 comm="apparmor_parser"
May 10 00:43:28 cmp02 kernel: [ 5216.099391] audit: type=1400 audit(1525913008.203:151): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8ba6e506-0122-4176-90fe-9baec01b43ef" pid=15088 comm="apparmor_parser"
May 10 00:43:28 cmp02 kernel: [ 5216.325916] audit: type=1400 audit(1525913008.430:152): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-8ba6e506-0122-4176-90fe-9baec01b43ef" pid=15102 comm="apparmor_parser"
May 10 00:43:28 cmp02 libvirtd[5599]: 2018-05-10 00:43:28.447+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=22 name='instance-00000027' uuid=8ba6e506-0122-4176-90fe-9baec01b43ef is tainted: host-cpu
May 10 00:43:33 cmp02 kernel: [ 5221.480927] audit: type=1400 audit(1525913013.585:153): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15212 comm="apparmor_parser"
May 10 00:43:33 cmp02 kernel: [ 5221.730239] audit: type=1400 audit(1525913013.834:154): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15215 comm="apparmor_parser"
May 10 00:43:34 cmp02 kernel: [ 5221.967197] audit: type=1400 audit(1525913014.071:155): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15225 comm="apparmor_parser"
May 10 00:43:34 cmp02 kernel: [ 5222.207577] audit: type=1400 audit(1525913014.311:156): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15239 comm="apparmor_parser"
May 10 00:43:34 cmp02 libvirtd[5599]: 2018-05-10 00:43:34.323+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=23 name='instance-0000002a' uuid=e82079be-a330-4f4d-9aaa-ec89b6660050 is tainted: host-cpu
May 10 00:43:35 cmp02 kernel: [ 5223.366521] audit: type=1400 audit(1525913015.470:157): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-8ba6e506-0122-4176-90fe-9baec01b43ef" pid=15286 comm="apparmor_parser"
May 10 00:43:43 cmp02 kernel: [ 5231.811695] audit: type=1400 audit(1525913023.915:158): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-a59d8165-c85f-43d8-8a7a-ba9ef88ac28a" pid=15457 comm="apparmor_parser"
May 10 00:43:50 cmp02 systemd[1]: Started Device-mapper event daemon.
May 10 00:43:53 cmp02 kernel: [ 5241.779405] audit: type=1400 audit(1525913033.883:159): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15755 comm="apparmor_parser"
May 10 00:43:53 cmp02 libvirtd[5599]: 2018-05-10 00:43:53.895+0000: 5611: warning : AppArmorSetFDLabel:1164 : could not find path for descriptor /proc/self/fd/77, skipping
May 10 00:43:54 cmp02 kernel: [ 5242.660386] audit: type=1400 audit(1525913034.764:160): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15779 comm="apparmor_parser"
May 10 00:43:59 cmp02 kernel: [ 5247.137719] audit: type=1400 audit(1525913039.241:161): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15844 comm="apparmor_parser"
May 10 00:43:59 cmp02 kernel: [ 5247.390932] audit: type=1400 audit(1525913039.494:162): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15847 comm="apparmor_parser"
May 10 00:43:59 cmp02 kernel: [ 5247.619631] audit: type=1400 audit(1525913039.723:163): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15851 comm="apparmor_parser"
May 10 00:43:59 cmp02 kernel: [ 5247.852437] audit: type=1400 audit(1525913039.956:164): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15859 comm="apparmor_parser"
May 10 00:43:59 cmp02 libvirtd[5599]: 2018-05-10 00:43:59.965+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=24 name='instance-0000002a' uuid=e82079be-a330-4f4d-9aaa-ec89b6660050 is tainted: host-cpu
May 10 00:44:00 cmp02 kernel: [ 5248.121001] audit: type=1400 audit(1525913040.224:165): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15868 comm="apparmor_parser"
May 10 00:44:00 cmp02 kernel: [ 5248.702949] audit: type=1400 audit(1525913040.806:166): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15894 comm="apparmor_parser"
May 10 00:44:11 cmp02 kernel: [ 5259.375741] audit: type=1400 audit(1525913051.479:167): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15983 comm="apparmor_parser"
May 10 00:44:11 cmp02 libvirtd[5599]: 2018-05-10 00:44:11.484+0000: 5608: warning : AppArmorSetFDLabel:1164 : could not find path for descriptor /proc/self/fd/77, skipping
May 10 00:44:12 cmp02 kernel: [ 5260.295822] audit: type=1400 audit(1525913052.399:168): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-e82079be-a330-4f4d-9aaa-ec89b6660050" pid=15990 comm="apparmor_parser"
May 10 00:44:16 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:44:19 cmp02 kernel: [ 5266.921043] audit: type=1400 audit(1525913059.024:169): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-61d1ac68-fbd3-4b94-941a-e018967c58b7" pid=16068 comm="apparmor_parser"
May 10 00:44:19 cmp02 kernel: [ 5267.140059] audit: type=1400 audit(1525913059.243:170): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-61d1ac68-fbd3-4b94-941a-e018967c58b7" pid=16071 comm="apparmor_parser"
May 10 00:44:19 cmp02 kernel: [ 5267.378648] audit: type=1400 audit(1525913059.481:171): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-61d1ac68-fbd3-4b94-941a-e018967c58b7" pid=16074 comm="apparmor_parser"
May 10 00:44:19 cmp02 kernel: [ 5267.597433] audit: type=1400 audit(1525913059.700:172): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-61d1ac68-fbd3-4b94-941a-e018967c58b7" pid=16077 comm="apparmor_parser"
May 10 00:44:19 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapadada0dc-f4 -- add-port br-int tapadada0dc-f4 -- set Interface tapadada0dc-f4 "external-ids:attached-mac=\"fa:16:3e:66:05:5c\"" -- set Interface tapadada0dc-f4 "external-ids:iface-id=\"adada0dc-f413-47b7-a635-97e6c58d13bd\"" -- set Interface tapadada0dc-f4 "external-ids:vm-id=\"61d1ac68-fbd3-4b94-941a-e018967c58b7\"" -- set Interface tapadada0dc-f4 external-ids:iface-status=active
May 10 00:44:19 cmp02 kernel: [ 5267.621771] device tapadada0dc-f4 entered promiscuous mode
May 10 00:44:19 cmp02 kernel: [ 5267.849005] audit: type=1400 audit(1525913059.952:173): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-61d1ac68-fbd3-4b94-941a-e018967c58b7" pid=16154 comm="apparmor_parser"
May 10 00:44:19 cmp02 libvirtd[5599]: 2018-05-10 00:44:19.957+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=25 name='instance-0000002f' uuid=61d1ac68-fbd3-4b94-941a-e018967c58b7 is tainted: host-cpu
May 10 00:44:43 cmp02 kernel: [ 5290.906979] hrtimer: interrupt took 65984 ns
May 10 00:44:45 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:44:47 cmp02 kernel: [ 5295.156148] audit: type=1400 audit(1525913087.258:174): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-869a89cd-c603-42a3-93ac-a04a838c631b" pid=16467 comm="apparmor_parser"
May 10 00:44:47 cmp02 kernel: [ 5295.391331] audit: type=1400 audit(1525913087.493:175): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-869a89cd-c603-42a3-93ac-a04a838c631b" pid=16476 comm="apparmor_parser"
May 10 00:44:47 cmp02 kernel: [ 5295.628069] audit: type=1400 audit(1525913087.730:176): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-869a89cd-c603-42a3-93ac-a04a838c631b" pid=16485 comm="apparmor_parser"
May 10 00:44:47 cmp02 kernel: [ 5295.863096] audit: type=1400 audit(1525913087.965:177): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-869a89cd-c603-42a3-93ac-a04a838c631b" pid=16508 comm="apparmor_parser"
May 10 00:44:47 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap7471a1fb-fd -- add-port br-int tap7471a1fb-fd -- set Interface tap7471a1fb-fd "external-ids:attached-mac=\"fa:16:3e:25:90:f7\"" -- set Interface tap7471a1fb-fd "external-ids:iface-id=\"7471a1fb-fd20-4725-8558-c1a26175d0a7\"" -- set Interface tap7471a1fb-fd "external-ids:vm-id=\"869a89cd-c603-42a3-93ac-a04a838c631b\"" -- set Interface tap7471a1fb-fd external-ids:iface-status=active
May 10 00:44:48 cmp02 kernel: [ 5295.904262] device tap7471a1fb-fd entered promiscuous mode
May 10 00:44:48 cmp02 kernel: [ 5296.157727] audit: type=1400 audit(1525913088.260:178): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-869a89cd-c603-42a3-93ac-a04a838c631b" pid=16613 comm="apparmor_parser"
May 10 00:44:48 cmp02 libvirtd[5599]: 2018-05-10 00:44:48.265+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=26 name='instance-00000032' uuid=869a89cd-c603-42a3-93ac-a04a838c631b is tainted: host-cpu
May 10 00:44:48 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:44:49 cmp02 kernel: [ 5297.212804] audit: type=1400 audit(1525913089.315:179): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-a0374dcc-ace0-4b45-8ec8-8bbcc486341a" pid=16685 comm="apparmor_parser"
May 10 00:44:49 cmp02 kernel: [ 5297.449352] audit: type=1400 audit(1525913089.551:180): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-a0374dcc-ace0-4b45-8ec8-8bbcc486341a" pid=16688 comm="apparmor_parser"
May 10 00:44:49 cmp02 kernel: [ 5297.690717] audit: type=1400 audit(1525913089.793:181): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-a0374dcc-ace0-4b45-8ec8-8bbcc486341a" pid=16691 comm="apparmor_parser"
May 10 00:44:50 cmp02 kernel: [ 5297.914310] audit: type=1400 audit(1525913090.016:182): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-a0374dcc-ace0-4b45-8ec8-8bbcc486341a" pid=16697 comm="apparmor_parser"
May 10 00:44:50 cmp02 libvirtd[5599]: 2018-05-10 00:44:50.026+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=27 name='instance-00000036' uuid=a0374dcc-ace0-4b45-8ec8-8bbcc486341a is tainted: host-cpu
May 10 00:44:50 cmp02 kernel: [ 5298.372776] audit: type=1400 audit(1525913090.475:183): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=16747 comm="apparmor_parser"
May 10 00:44:51 cmp02 systemd-udevd[16759]: Could not generate persistent MAC address for tapcda4c0bf-9a: No such file or directory
May 10 00:44:51 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapcda4c0bf-9a -- add-port br-int tapcda4c0bf-9a -- set Interface tapcda4c0bf-9a "external-ids:attached-mac=\"fa:16:3e:60:cf:ae\"" -- set Interface tapcda4c0bf-9a "external-ids:iface-id=\"cda4c0bf-9abc-4eca-8925-a351d3c04a8d\"" -- set Interface tapcda4c0bf-9a "external-ids:vm-id=\"fff57574-c56a-4e88-aa96-e0648c02ca03\"" -- set Interface tapcda4c0bf-9a external-ids:iface-status=active
May 10 00:44:51 cmp02 kernel: [ 5299.069544] device tapcda4c0bf-9a entered promiscuous mode
May 10 00:44:51 cmp02 libvirtd[5599]: 2018-05-10 00:44:51.424+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=28 name='instance-00000035' uuid=fff57574-c56a-4e88-aa96-e0648c02ca03 is tainted: host-cpu
May 10 00:44:53 cmp02 kernel: [ 5301.115818] kauditd_printk_skb: 4 callbacks suppressed
May 10 00:44:53 cmp02 kernel: [ 5301.115819] audit: type=1400 audit(1525913093.218:188): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-a0374dcc-ace0-4b45-8ec8-8bbcc486341a" pid=16896 comm="apparmor_parser"
May 10 00:44:53 cmp02 kernel: [ 5301.149750] device tapadada0dc-f4 left promiscuous mode
May 10 00:44:53 cmp02 kernel: [ 5301.544851] audit: type=1400 audit(1525913093.647:189): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-61d1ac68-fbd3-4b94-941a-e018967c58b7" pid=16924 comm="apparmor_parser"
May 10 00:44:53 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapadada0dc-f4
May 10 00:45:11 cmp02 kernel: [ 5318.898328] device tap7471a1fb-fd left promiscuous mode
May 10 00:45:11 cmp02 kernel: [ 5319.276732] audit: type=1400 audit(1525913111.378:190): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-869a89cd-c603-42a3-93ac-a04a838c631b" pid=17073 comm="apparmor_parser"
May 10 00:45:11 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap7471a1fb-fd
May 10 00:45:22 cmp02 kernel: [ 5330.839796] scsi host3: iSCSI Initiator over TCP/IP
May 10 00:45:23 cmp02 kernel: [ 5331.850749] scsi 3:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May 10 00:45:24 cmp02 kernel: [ 5331.898947] scsi 3:0:0:0: Attached scsi generic sg3 type 12
May 10 00:45:24 cmp02 kernel: [ 5331.900594] scsi 3:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May 10 00:45:24 cmp02 kernel: [ 5331.944423] sd 3:0:0:1: Attached scsi generic sg4 type 0
May 10 00:45:24 cmp02 kernel: [ 5331.945049] sd 3:0:0:1: [sdb] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
May 10 00:45:24 cmp02 kernel: [ 5331.945174] sd 3:0:0:1: [sdb] Write Protect is off
May 10 00:45:24 cmp02 kernel: [ 5331.945176] sd 3:0:0:1: [sdb] Mode Sense: 69 00 10 08
May 10 00:45:24 cmp02 kernel: [ 5331.945398] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 10 00:45:24 cmp02 kernel: [ 5331.951459] sd 3:0:0:1: [sdb] Attached SCSI disk
May 10 00:45:24 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session7/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:24 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session7/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:24 cmp02 kernel: [ 5332.308333] audit: type=1400 audit(1525913124.410:191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17147 comm="apparmor_parser"
May 10 00:45:24 cmp02 iscsid: Connection7:0 to [target: iqn.2010-10.org.openstack:volume-bb5508d5-36b1-4231-8d44-ad870b011136, portal: 192.168.11.42,3260] through [iface: default] is operational now
May 10 00:45:28 cmp02 kernel: [ 5336.495401] device tapcda4c0bf-9a left promiscuous mode
May 10 00:45:28 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session7/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:28 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session7/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:28 cmp02 libvirtd[5599]: 2018-05-10 00:45:28.621+0000: 5599: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
May 10 00:45:29 cmp02 kernel: [ 5336.927042] audit: type=1400 audit(1525913129.028:192): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17174 comm="apparmor_parser"
May 10 00:45:29 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapcda4c0bf-9a
May 10 00:45:29 cmp02 kernel: [ 5337.862961]  connection2:0: detected conn error (1020)
May 10 00:45:30 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:45:31 cmp02 kernel: [ 5339.891801] sd 3:0:0:1: [sdb] Synchronizing SCSI cache
May 10 00:45:33 cmp02 kernel: [ 5341.263422]  connection2:0: detected conn error (1020)
May 10 00:45:33 cmp02 kernel: [ 5341.263442] scsi host3: iSCSI Initiator over TCP/IP
May 10 00:45:33 cmp02 iscsid: Connection7:0 to [target: iqn.2010-10.org.openstack:volume-bb5508d5-36b1-4231-8d44-ad870b011136, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May 10 00:45:34 cmp02 kernel: [ 5342.276056] scsi 3:0:0:0: RAID              IET      Controller       0001 PQ: 0 ANSI: 5
May 10 00:45:34 cmp02 kernel: [ 5342.315094] scsi 3:0:0:0: Attached scsi generic sg3 type 12
May 10 00:45:34 cmp02 kernel: [ 5342.315870] scsi 3:0:0:1: Direct-Access     IET      VIRTUAL-DISK     0001 PQ: 0 ANSI: 5
May 10 00:45:34 cmp02 kernel: [ 5342.351037] sd 3:0:0:1: Attached scsi generic sg4 type 0
May 10 00:45:34 cmp02 kernel: [ 5342.352574] sd 3:0:0:1: [sdb] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
May 10 00:45:34 cmp02 kernel: [ 5342.352706] sd 3:0:0:1: [sdb] Write Protect is off
May 10 00:45:34 cmp02 kernel: [ 5342.352709] sd 3:0:0:1: [sdb] Mode Sense: 69 00 10 08
May 10 00:45:34 cmp02 kernel: [ 5342.353248] sd 3:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 10 00:45:34 cmp02 kernel: [ 5342.360535] sd 3:0:0:1: [sdb] Attached SCSI disk
May 10 00:45:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:45:34 cmp02 iscsid: Connection8:0 to [target: iqn.2010-10.org.openstack:volume-bb5508d5-36b1-4231-8d44-ad870b011136, portal: 192.168.11.42,3260] through [iface: default] is operational now
May 10 00:45:34 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session8/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:34 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session8/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:35 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:45:35 cmp02 kernel: [ 5343.432133] audit: type=1400 audit(1525913135.533:193): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17304 comm="apparmor_parser"
May 10 00:45:35 cmp02 kernel: [ 5343.671306] audit: type=1400 audit(1525913135.772:194): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17307 comm="apparmor_parser"
May 10 00:45:36 cmp02 kernel: [ 5343.915697] audit: type=1400 audit(1525913136.017:195): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17310 comm="apparmor_parser"
May 10 00:45:36 cmp02 kernel: [ 5344.162284] audit: type=1400 audit(1525913136.263:196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17313 comm="apparmor_parser"
May 10 00:45:36 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapcda4c0bf-9a -- add-port br-int tapcda4c0bf-9a -- set Interface tapcda4c0bf-9a "external-ids:attached-mac=\"fa:16:3e:60:cf:ae\"" -- set Interface tapcda4c0bf-9a "external-ids:iface-id=\"cda4c0bf-9abc-4eca-8925-a351d3c04a8d\"" -- set Interface tapcda4c0bf-9a "external-ids:vm-id=\"fff57574-c56a-4e88-aa96-e0648c02ca03\"" -- set Interface tapcda4c0bf-9a external-ids:iface-status=active
May 10 00:45:36 cmp02 kernel: [ 5344.192793] device tapcda4c0bf-9a entered promiscuous mode
May 10 00:45:36 cmp02 kernel: [ 5344.279470]  connection2:0: detected conn error (1020)
May 10 00:45:36 cmp02 kernel: [ 5344.443985] audit: type=1400 audit(1525913136.545:197): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17380 comm="apparmor_parser"
May 10 00:45:36 cmp02 libvirtd[5599]: 2018-05-10 00:45:36.551+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=29 name='instance-00000035' uuid=fff57574-c56a-4e88-aa96-e0648c02ca03 is tainted: host-cpu
May 10 00:45:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:45:39 cmp02 kernel: [ 5347.286371]  connection2:0: detected conn error (1020)
May 10 00:45:42 cmp02 kernel: [ 5350.292964]  connection2:0: detected conn error (1020)
May 10 00:45:45 cmp02 kernel: [ 5353.299310]  connection2:0: detected conn error (1020)
May 10 00:45:48 cmp02 kernel: [ 5356.305672]  connection2:0: detected conn error (1020)
May 10 00:45:51 cmp02 kernel: [ 5359.311336]  connection2:0: detected conn error (1020)
May 10 00:45:52 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 00:45:53 cmp02 systemd[1]: dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device: Dev dev-disk-by\x2did-scsi\x2d360000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session8/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:53 cmp02 systemd[1]: dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device: Dev dev-disk-by\x2did-wwn\x2d0x60000000000000000e00000000010001.device appeared twice with different sysfs paths /sys/devices/platform/host2/session2/target2:0:0/2:0:0:1/block/sda and /sys/devices/platform/host3/session8/target3:0:0/3:0:0:1/block/sdb
May 10 00:45:53 cmp02 kernel: [ 5361.684824] audit: type=1400 audit(1525913153.786:198): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17464 comm="apparmor_parser"
May 10 00:45:53 cmp02 kernel: [ 5361.876722] sd 3:0:0:1: [sdb] Synchronizing SCSI cache
May 10 00:45:54 cmp02 kernel: [ 5362.486399]  connection2:0: detected conn error (1020)
May 10 00:45:55 cmp02 iscsid: Connection8:0 to [target: iqn.2010-10.org.openstack:volume-bb5508d5-36b1-4231-8d44-ad870b011136, portal: 192.168.11.42,3260] through [iface: default] is shutdown.
May 10 00:45:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:45:59 cmp02 kernel: [ 5367.285473] device tapcda4c0bf-9a left promiscuous mode
May 10 00:45:59 cmp02 libvirtd[5599]: 2018-05-10 00:45:59.405+0000: 5599: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
May 10 00:45:59 cmp02 kernel: [ 5367.747319] audit: type=1400 audit(1525913159.848:199): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17496 comm="apparmor_parser"
May 10 00:45:59 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapcda4c0bf-9a
May 10 00:46:02 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 00:46:03 cmp02 kernel: [ 5371.159783] audit: type=1400 audit(1525913163.260:200): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17554 comm="apparmor_parser"
May 10 00:46:03 cmp02 kernel: [ 5371.393561] audit: type=1400 audit(1525913163.494:201): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17557 comm="apparmor_parser"
May 10 00:46:03 cmp02 kernel: [ 5371.634574] audit: type=1400 audit(1525913163.735:202): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17560 comm="apparmor_parser"
May 10 00:46:03 cmp02 kernel: [ 5371.863384] audit: type=1400 audit(1525913163.964:203): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17563 comm="apparmor_parser"
May 10 00:46:03 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapcda4c0bf-9a -- add-port br-int tapcda4c0bf-9a -- set Interface tapcda4c0bf-9a "external-ids:attached-mac=\"fa:16:3e:60:cf:ae\"" -- set Interface tapcda4c0bf-9a "external-ids:iface-id=\"cda4c0bf-9abc-4eca-8925-a351d3c04a8d\"" -- set Interface tapcda4c0bf-9a "external-ids:vm-id=\"fff57574-c56a-4e88-aa96-e0648c02ca03\"" -- set Interface tapcda4c0bf-9a external-ids:iface-status=active
May 10 00:46:03 cmp02 kernel: [ 5371.888729] device tapcda4c0bf-9a entered promiscuous mode
May 10 00:46:04 cmp02 kernel: [ 5372.118842] audit: type=1400 audit(1525913164.219:204): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17640 comm="apparmor_parser"
May 10 00:46:04 cmp02 libvirtd[5599]: 2018-05-10 00:46:04.224+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=30 name='instance-00000035' uuid=fff57574-c56a-4e88-aa96-e0648c02ca03 is tainted: host-cpu
May 10 00:46:22 cmp02 kernel: [ 5389.984807] device tapcda4c0bf-9a left promiscuous mode
May 10 00:46:22 cmp02 kernel: [ 5390.382488] audit: type=1400 audit(1525913182.483:205): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-fff57574-c56a-4e88-aa96-e0648c02ca03" pid=17714 comm="apparmor_parser"
May 10 00:46:22 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapcda4c0bf-9a
May 10 00:46:49 cmp02 kernel: [ 5417.349108]  connection2:0: detected conn error (1020)
May 10 00:46:50 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:46:52 cmp02 kernel: [ 5420.354654]  connection2:0: detected conn error (1020)
May 10 00:46:52 cmp02 tgtd[13270]: tgtd: device_mgmt(246) sz:68 params:path=/dev/cinder-volume/volume-4e7d22db-907d-4c87-9cf6-68304876d3a3
May 10 00:46:52 cmp02 tgtd[13270]: tgtd: bs_thread_open(409) 16
May 10 00:46:53 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 00:46:55 cmp02 kernel: [ 5423.361758]  connection2:0: detected conn error (1020)
May 10 00:46:58 cmp02 kernel: [ 5426.368699]  connection2:0: detected conn error (1020)
May 10 00:46:59 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 00:53:17 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 00:53:17 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 00:53:17 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1452 seconds.
May 10 01:04:58 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:04:59 cmp02 kernel: [ 6507.904847] audit: type=1400 audit(1525914299.985:206): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-8c8e926f-31e1-4b6c-a989-f6f44cee7581" pid=19575 comm="apparmor_parser"
May 10 01:05:00 cmp02 kernel: [ 6508.148761] audit: type=1400 audit(1525914300.229:207): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8c8e926f-31e1-4b6c-a989-f6f44cee7581" pid=19578 comm="apparmor_parser"
May 10 01:05:00 cmp02 kernel: [ 6508.386176] audit: type=1400 audit(1525914300.467:208): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8c8e926f-31e1-4b6c-a989-f6f44cee7581" pid=19581 comm="apparmor_parser"
May 10 01:05:00 cmp02 kernel: [ 6508.633944] audit: type=1400 audit(1525914300.714:209): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-8c8e926f-31e1-4b6c-a989-f6f44cee7581" pid=19584 comm="apparmor_parser"
May 10 01:05:00 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapbe9565f8-b0 -- add-port br-int tapbe9565f8-b0 -- set Interface tapbe9565f8-b0 "external-ids:attached-mac=\"fa:16:3e:fe:4c:18\"" -- set Interface tapbe9565f8-b0 "external-ids:iface-id=\"be9565f8-b044-4f22-a5e4-98762ac94649\"" -- set Interface tapbe9565f8-b0 "external-ids:vm-id=\"8c8e926f-31e1-4b6c-a989-f6f44cee7581\"" -- set Interface tapbe9565f8-b0 external-ids:iface-status=active
May 10 01:05:00 cmp02 kernel: [ 6508.666249] device tapbe9565f8-b0 entered promiscuous mode
May 10 01:05:00 cmp02 kernel: [ 6508.915102] audit: type=1400 audit(1525914300.995:210): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8c8e926f-31e1-4b6c-a989-f6f44cee7581" pid=19671 comm="apparmor_parser"
May 10 01:05:01 cmp02 libvirtd[5599]: 2018-05-10 01:05:01.001+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=31 name='instance-0000003a' uuid=8c8e926f-31e1-4b6c-a989-f6f44cee7581 is tainted: host-cpu
May 10 01:05:14 cmp02 kernel: [ 6522.767793] device tapbe9565f8-b0 left promiscuous mode
May 10 01:05:15 cmp02 libvirtd[5599]: 2018-05-10 01:05:15.015+0000: 5599: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
May 10 01:05:20 cmp02 kernel: [ 6527.940502] audit: type=1400 audit(1525914320.021:211): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-8c8e926f-31e1-4b6c-a989-f6f44cee7581" pid=19900 comm="apparmor_parser"
May 10 01:05:20 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapbe9565f8-b0
May 10 01:06:14 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:06:15 cmp02 kernel: [ 6583.645287] audit: type=1400 audit(1525914375.724:212): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-8be198d9-5dd7-4764-964e-0b244c268a4c" pid=19985 comm="apparmor_parser"
May 10 01:06:15 cmp02 kernel: [ 6583.899757] audit: type=1400 audit(1525914375.979:213): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8be198d9-5dd7-4764-964e-0b244c268a4c" pid=19988 comm="apparmor_parser"
May 10 01:06:16 cmp02 kernel: [ 6584.150874] audit: type=1400 audit(1525914376.230:214): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8be198d9-5dd7-4764-964e-0b244c268a4c" pid=19991 comm="apparmor_parser"
May 10 01:06:16 cmp02 kernel: [ 6584.390533] audit: type=1400 audit(1525914376.470:215): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-8be198d9-5dd7-4764-964e-0b244c268a4c" pid=19994 comm="apparmor_parser"
May 10 01:06:16 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap2870f1c0-21 -- add-port br-int tap2870f1c0-21 -- set Interface tap2870f1c0-21 "external-ids:attached-mac=\"fa:16:3e:4f:47:09\"" -- set Interface tap2870f1c0-21 "external-ids:iface-id=\"2870f1c0-215a-40c7-bbf1-02effe4d716b\"" -- set Interface tap2870f1c0-21 "external-ids:vm-id=\"8be198d9-5dd7-4764-964e-0b244c268a4c\"" -- set Interface tap2870f1c0-21 external-ids:iface-status=active
May 10 01:06:16 cmp02 kernel: [ 6584.425606] device tap2870f1c0-21 entered promiscuous mode
May 10 01:06:16 cmp02 kernel: [ 6584.698769] audit: type=1400 audit(1525914376.778:216): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-8be198d9-5dd7-4764-964e-0b244c268a4c" pid=20044 comm="apparmor_parser"
May 10 01:06:16 cmp02 libvirtd[5599]: 2018-05-10 01:06:16.787+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=32 name='instance-0000003c' uuid=8be198d9-5dd7-4764-964e-0b244c268a4c is tainted: host-cpu
May 10 01:06:51 cmp02 kernel: [ 6619.345396] device tap2870f1c0-21 left promiscuous mode
May 10 01:06:51 cmp02 kernel: [ 6619.734777] audit: type=1400 audit(1525914411.813:217): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-8be198d9-5dd7-4764-964e-0b244c268a4c" pid=20317 comm="apparmor_parser"
May 10 01:06:51 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap2870f1c0-21
May 10 01:07:57 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:07:58 cmp02 kernel: [ 6686.530875] audit: type=1400 audit(1525914478.608:218): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-9206fb71-cc04-476a-a2f0-6418a38656d0" pid=20412 comm="apparmor_parser"
May 10 01:07:58 cmp02 kernel: [ 6686.791152] audit: type=1400 audit(1525914478.869:219): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-9206fb71-cc04-476a-a2f0-6418a38656d0" pid=20415 comm="apparmor_parser"
May 10 01:07:59 cmp02 kernel: [ 6687.025620] audit: type=1400 audit(1525914479.103:220): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-9206fb71-cc04-476a-a2f0-6418a38656d0" pid=20418 comm="apparmor_parser"
May 10 01:07:59 cmp02 kernel: [ 6687.265683] audit: type=1400 audit(1525914479.343:221): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-9206fb71-cc04-476a-a2f0-6418a38656d0" pid=20421 comm="apparmor_parser"
May 10 01:07:59 cmp02 systemd-udevd[20424]: Could not generate persistent MAC address for tap57bc3e52-12: No such file or directory
May 10 01:07:59 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap57bc3e52-12 -- add-port br-int tap57bc3e52-12 -- set Interface tap57bc3e52-12 "external-ids:attached-mac=\"fa:16:3e:4d:ce:aa\"" -- set Interface tap57bc3e52-12 "external-ids:iface-id=\"57bc3e52-1222-402a-a92c-ef54971de6ca\"" -- set Interface tap57bc3e52-12 "external-ids:vm-id=\"9206fb71-cc04-476a-a2f0-6418a38656d0\"" -- set Interface tap57bc3e52-12 external-ids:iface-status=active
May 10 01:07:59 cmp02 kernel: [ 6687.300261] device tap57bc3e52-12 entered promiscuous mode
May 10 01:07:59 cmp02 kernel: [ 6687.565048] audit: type=1400 audit(1525914479.642:222): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-9206fb71-cc04-476a-a2f0-6418a38656d0" pid=20493 comm="apparmor_parser"
May 10 01:07:59 cmp02 libvirtd[5599]: 2018-05-10 01:07:59.647+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=33 name='instance-0000003e' uuid=9206fb71-cc04-476a-a2f0-6418a38656d0 is tainted: host-cpu
May 10 01:08:05 cmp02 kernel: [ 6693.555053] device tap57bc3e52-12 left promiscuous mode
May 10 01:08:06 cmp02 kernel: [ 6693.924698] audit: type=1400 audit(1525914486.002:223): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-9206fb71-cc04-476a-a2f0-6418a38656d0" pid=20563 comm="apparmor_parser"
May 10 01:08:06 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap57bc3e52-12
May 10 01:10:00 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:10:01 cmp02 kernel: [ 6809.507120] audit: type=1400 audit(1525914601.582:224): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-e9f7163f-dceb-4eac-8fd6-86f5998ae1af" pid=20663 comm="apparmor_parser"
May 10 01:10:01 cmp02 kernel: [ 6809.748262] audit: type=1400 audit(1525914601.824:225): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e9f7163f-dceb-4eac-8fd6-86f5998ae1af" pid=20666 comm="apparmor_parser"
May 10 01:10:02 cmp02 kernel: [ 6809.998062] audit: type=1400 audit(1525914602.073:226): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e9f7163f-dceb-4eac-8fd6-86f5998ae1af" pid=20669 comm="apparmor_parser"
May 10 01:10:02 cmp02 kernel: [ 6810.245034] audit: type=1400 audit(1525914602.320:227): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-e9f7163f-dceb-4eac-8fd6-86f5998ae1af" pid=20672 comm="apparmor_parser"
May 10 01:10:02 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap27768ac1-cc -- add-port br-int tap27768ac1-cc -- set Interface tap27768ac1-cc "external-ids:attached-mac=\"0a:1b:2c:3d:4e:5f\"" -- set Interface tap27768ac1-cc "external-ids:iface-id=\"27768ac1-ccbe-42a0-9656-559c7aeb1ad3\"" -- set Interface tap27768ac1-cc "external-ids:vm-id=\"e9f7163f-dceb-4eac-8fd6-86f5998ae1af\"" -- set Interface tap27768ac1-cc external-ids:iface-status=active
May 10 01:10:02 cmp02 kernel: [ 6810.274948] device tap27768ac1-cc entered promiscuous mode
May 10 01:10:02 cmp02 kernel: [ 6810.516360] audit: type=1400 audit(1525914602.592:228): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-e9f7163f-dceb-4eac-8fd6-86f5998ae1af" pid=20744 comm="apparmor_parser"
May 10 01:10:02 cmp02 libvirtd[5599]: 2018-05-10 01:10:02.597+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=34 name='instance-00000040' uuid=e9f7163f-dceb-4eac-8fd6-86f5998ae1af is tainted: host-cpu
May 10 01:10:05 cmp02 kernel: [ 6813.764268] device tap27768ac1-cc left promiscuous mode
May 10 01:10:06 cmp02 kernel: [ 6814.147406] audit: type=1400 audit(1525914606.223:229): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-e9f7163f-dceb-4eac-8fd6-86f5998ae1af" pid=20818 comm="apparmor_parser"
May 10 01:10:06 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap27768ac1-cc
May 10 01:10:29 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:10:30 cmp02 kernel: [ 6838.905844] audit: type=1400 audit(1525914630.981:230): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a" pid=20905 comm="apparmor_parser"
May 10 01:10:31 cmp02 kernel: [ 6839.149804] audit: type=1400 audit(1525914631.225:231): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a" pid=20908 comm="apparmor_parser"
May 10 01:10:31 cmp02 kernel: [ 6839.391849] audit: type=1400 audit(1525914631.467:232): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a" pid=20911 comm="apparmor_parser"
May 10 01:10:31 cmp02 kernel: [ 6839.635141] audit: type=1400 audit(1525914631.710:233): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a" pid=20914 comm="apparmor_parser"
May 10 01:10:31 cmp02 systemd-udevd[20917]: Could not generate persistent MAC address for tap7c05deea-0c: No such file or directory
May 10 01:10:31 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap7c05deea-0c -- add-port br-int tap7c05deea-0c -- set Interface tap7c05deea-0c "external-ids:attached-mac=\"fa:16:3e:f0:c9:af\"" -- set Interface tap7c05deea-0c "external-ids:iface-id=\"7c05deea-0cdb-4bb8-bb65-d07a1e836623\"" -- set Interface tap7c05deea-0c "external-ids:vm-id=\"b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a\"" -- set Interface tap7c05deea-0c external-ids:iface-status=active
May 10 01:10:31 cmp02 kernel: [ 6839.678304] device tap7c05deea-0c entered promiscuous mode
May 10 01:10:32 cmp02 kernel: [ 6839.926589] audit: type=1400 audit(1525914632.001:234): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a" pid=20996 comm="apparmor_parser"
May 10 01:10:32 cmp02 libvirtd[5599]: 2018-05-10 01:10:32.008+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=35 name='instance-00000041' uuid=b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a is tainted: host-cpu
May 10 01:10:35 cmp02 kernel: [ 6843.366814] device tap7c05deea-0c left promiscuous mode
May 10 01:10:35 cmp02 libvirtd[5599]: 2018-05-10 01:10:35.590+0000: 5599: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
May 10 01:10:40 cmp02 kernel: [ 6848.509080] audit: type=1400 audit(1525914640.584:235): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-b4f6bbc0-f747-4f8d-ab4c-78f8a317af2a" pid=21073 comm="apparmor_parser"
May 10 01:10:40 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap7c05deea-0c
May 10 01:12:38 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:12:40 cmp02 kernel: [ 6968.159607] audit: type=1400 audit(1525914760.232:236): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-cd57f284-8e5d-4c2a-8e19-82623b0e9367" pid=21173 comm="apparmor_parser"
May 10 01:12:40 cmp02 kernel: [ 6968.400356] audit: type=1400 audit(1525914760.473:237): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-cd57f284-8e5d-4c2a-8e19-82623b0e9367" pid=21176 comm="apparmor_parser"
May 10 01:12:40 cmp02 kernel: [ 6968.635738] audit: type=1400 audit(1525914760.708:238): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-cd57f284-8e5d-4c2a-8e19-82623b0e9367" pid=21179 comm="apparmor_parser"
May 10 01:12:40 cmp02 kernel: [ 6968.881039] audit: type=1400 audit(1525914760.953:239): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-cd57f284-8e5d-4c2a-8e19-82623b0e9367" pid=21182 comm="apparmor_parser"
May 10 01:12:40 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap4c6b039b-f8 -- add-port br-int tap4c6b039b-f8 -- set Interface tap4c6b039b-f8 "external-ids:attached-mac=\"fa:16:3e:40:a3:6b\"" -- set Interface tap4c6b039b-f8 "external-ids:iface-id=\"4c6b039b-f85d-4946-8876-9033af989eda\"" -- set Interface tap4c6b039b-f8 "external-ids:vm-id=\"cd57f284-8e5d-4c2a-8e19-82623b0e9367\"" -- set Interface tap4c6b039b-f8 external-ids:iface-status=active
May 10 01:12:40 cmp02 kernel: [ 6968.923364] device tap4c6b039b-f8 entered promiscuous mode
May 10 01:12:41 cmp02 kernel: [ 6969.177724] audit: type=1400 audit(1525914761.250:240): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-cd57f284-8e5d-4c2a-8e19-82623b0e9367" pid=21266 comm="apparmor_parser"
May 10 01:12:41 cmp02 libvirtd[5599]: 2018-05-10 01:12:41.256+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=36 name='instance-00000045' uuid=cd57f284-8e5d-4c2a-8e19-82623b0e9367 is tainted: host-cpu
May 10 01:12:51 cmp02 kernel: [ 6979.700607] device tap4c6b039b-f8 left promiscuous mode
May 10 01:12:52 cmp02 kernel: [ 6980.105335] audit: type=1400 audit(1525914772.177:241): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-cd57f284-8e5d-4c2a-8e19-82623b0e9367" pid=21344 comm="apparmor_parser"
May 10 01:12:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap4c6b039b-f8
May 10 01:16:09 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:16:10 cmp02 kernel: [ 7178.775716] audit: type=1400 audit(1525914970.844:242): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-f52e936c-da29-485f-9f6c-1e876864f607" pid=21456 comm="apparmor_parser"
May 10 01:16:11 cmp02 kernel: [ 7179.008559] audit: type=1400 audit(1525914971.077:243): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f52e936c-da29-485f-9f6c-1e876864f607" pid=21459 comm="apparmor_parser"
May 10 01:16:11 cmp02 kernel: [ 7179.252350] audit: type=1400 audit(1525914971.321:244): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f52e936c-da29-485f-9f6c-1e876864f607" pid=21462 comm="apparmor_parser"
May 10 01:16:11 cmp02 kernel: [ 7179.500981] audit: type=1400 audit(1525914971.569:245): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-f52e936c-da29-485f-9f6c-1e876864f607" pid=21465 comm="apparmor_parser"
May 10 01:16:11 cmp02 systemd-udevd[21468]: Could not generate persistent MAC address for tap60817f1e-bd: No such file or directory
May 10 01:16:11 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap60817f1e-bd -- add-port br-int tap60817f1e-bd -- set Interface tap60817f1e-bd "external-ids:attached-mac=\"fa:16:3e:d3:32:79\"" -- set Interface tap60817f1e-bd "external-ids:iface-id=\"60817f1e-bd20-4e1a-a49a-f0ef704822f2\"" -- set Interface tap60817f1e-bd "external-ids:vm-id=\"f52e936c-da29-485f-9f6c-1e876864f607\"" -- set Interface tap60817f1e-bd external-ids:iface-status=active
May 10 01:16:11 cmp02 kernel: [ 7179.544669] device tap60817f1e-bd entered promiscuous mode
May 10 01:16:11 cmp02 kernel: [ 7179.816600] audit: type=1400 audit(1525914971.885:246): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f52e936c-da29-485f-9f6c-1e876864f607" pid=21562 comm="apparmor_parser"
May 10 01:16:11 cmp02 libvirtd[5599]: 2018-05-10 01:16:11.891+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=37 name='instance-0000004b' uuid=f52e936c-da29-485f-9f6c-1e876864f607 is tainted: host-cpu
May 10 01:16:26 cmp02 kernel: [ 7194.325808] device tap60817f1e-bd left promiscuous mode
May 10 01:16:26 cmp02 libvirtd[5599]: 2018-05-10 01:16:26.760+0000: 5599: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor
May 10 01:16:31 cmp02 kernel: [ 7199.515274] audit: type=1400 audit(1525914991.583:247): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-f52e936c-da29-485f-9f6c-1e876864f607" pid=21680 comm="apparmor_parser"
May 10 01:16:31 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap60817f1e-bd
May 10 01:16:45 cmp02 salt-minion[2824]: [INFO    ] Running scheduled job: __mine_interval
May 10 01:17:01 cmp02 CRON[21715]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 10 01:17:29 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 01:17:29 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 01:17:29 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1378 seconds.
May 10 01:17:51 cmp02 kernel: [ 7279.232368]  connection2:0: detected conn error (1020)
May 10 01:17:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:17:54 cmp02 kernel: [ 7282.240406]  connection2:0: detected conn error (1020)
May 10 01:17:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:17:57 cmp02 kernel: [ 7285.249160]  connection2:0: detected conn error (1020)
May 10 01:18:00 cmp02 kernel: [ 7288.256191]  connection2:0: detected conn error (1020)
May 10 01:18:03 cmp02 kernel: [ 7291.263616]  connection2:0: detected conn error (1020)
May 10 01:18:06 cmp02 kernel: [ 7294.272486]  connection2:0: detected conn error (1020)
May 10 01:18:09 cmp02 kernel: [ 7297.279336]  connection2:0: detected conn error (1020)
May 10 01:18:12 cmp02 kernel: [ 7300.287766]  connection2:0: detected conn error (1020)
May 10 01:18:15 cmp02 kernel: [ 7303.297803]  connection2:0: detected conn error (1020)
May 10 01:18:18 cmp02 kernel: [ 7306.307192]  connection2:0: detected conn error (1020)
May 10 01:18:21 cmp02 kernel: [ 7309.314404]  connection2:0: detected conn error (1020)
May 10 01:18:24 cmp02 kernel: [ 7312.323125]  connection2:0: detected conn error (1020)
May 10 01:18:27 cmp02 kernel: [ 7315.331465]  connection2:0: detected conn error (1020)
May 10 01:18:30 cmp02 kernel: [ 7318.342604]  connection2:0: detected conn error (1020)
May 10 01:18:33 cmp02 kernel: [ 7321.354949]  connection2:0: detected conn error (1020)
May 10 01:18:34 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:18:36 cmp02 kernel: [ 7324.368434]  connection2:0: detected conn error (1020)
May 10 01:18:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:18:39 cmp02 kernel: [ 7327.377877]  connection2:0: detected conn error (1020)
May 10 01:18:42 cmp02 kernel: [ 7330.388242]  connection2:0: detected conn error (1020)
May 10 01:18:45 cmp02 kernel: [ 7333.396928]  connection2:0: detected conn error (1020)
May 10 01:18:48 cmp02 kernel: [ 7336.406515]  connection2:0: detected conn error (1020)
May 10 01:18:51 cmp02 kernel: [ 7339.416728]  connection2:0: detected conn error (1020)
May 10 01:18:54 cmp02 kernel: [ 7342.425506]  connection2:0: detected conn error (1020)
May 10 01:18:52 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:18:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:18:57 cmp02 kernel: [ 7345.433310]  connection2:0: detected conn error (1020)
May 10 01:18:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:00 cmp02 kernel: [ 7348.440647]  connection2:0: detected conn error (1020)
May 10 01:19:03 cmp02 kernel: [ 7351.448839]  connection2:0: detected conn error (1020)
May 10 01:19:06 cmp02 kernel: [ 7354.459284]  connection2:0: detected conn error (1020)
May 10 01:19:07 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:19:09 cmp02 kernel: [ 7357.467487]  connection2:0: detected conn error (1020)
May 10 01:19:10 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:12 cmp02 kernel: [ 7360.474258]  connection2:0: detected conn error (1020)
May 10 01:19:15 cmp02 kernel: [ 7363.483911]  connection2:0: detected conn error (1020)
May 10 01:19:18 cmp02 kernel: [ 7366.493547]  connection2:0: detected conn error (1020)
May 10 01:19:21 cmp02 kernel: [ 7369.500122]  connection2:0: detected conn error (1020)
May 10 01:19:24 cmp02 kernel: [ 7372.505960]  connection2:0: detected conn error (1020)
May 10 01:19:27 cmp02 kernel: [ 7375.514253]  connection2:0: detected conn error (1020)
May 10 01:19:30 cmp02 kernel: [ 7378.521029]  connection2:0: detected conn error (1020)
May 10 01:19:31 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:19:32 cmp02 tgtd[13270]: tgtd: device_mgmt(246) sz:68 params:path=/dev/cinder-volume/volume-bf28c8eb-ec30-4cf2-82ec-ccc466548c4a
May 10 01:19:32 cmp02 tgtd[13270]: tgtd: bs_thread_open(409) 16
May 10 01:19:33 cmp02 kernel: [ 7381.530090]  connection2:0: detected conn error (1020)
May 10 01:19:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:36 cmp02 kernel: [ 7384.541650]  connection2:0: detected conn error (1020)
May 10 01:19:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:39 cmp02 kernel: [ 7387.549417]  connection2:0: detected conn error (1020)
May 10 01:19:42 cmp02 kernel: [ 7390.556649]  connection2:0: detected conn error (1020)
May 10 01:19:40 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:43 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:45 cmp02 kernel: [ 7393.564035]  connection2:0: detected conn error (1020)
May 10 01:19:46 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:19:48 cmp02 kernel: [ 7396.571931]  connection2:0: detected conn error (1020)
May 10 01:19:51 cmp02 kernel: [ 7399.577429]  connection2:0: detected conn error (1020)
May 10 01:19:54 cmp02 kernel: [ 7402.586588]  connection2:0: detected conn error (1020)
May 10 01:19:55 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:19:57 cmp02 kernel: [ 7405.592870]  connection2:0: detected conn error (1020)
May 10 01:19:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:20:00 cmp02 kernel: [ 7408.600525]  connection2:0: detected conn error (1020)
May 10 01:20:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:20:03 cmp02 kernel: [ 7411.609859]  connection2:0: detected conn error (1020)
May 10 01:20:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:20:06 cmp02 kernel: [ 7414.617099]  connection2:0: detected conn error (1020)
May 10 01:20:07 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:20:09 cmp02 kernel: [ 7417.626686]  connection2:0: detected conn error (1020)
May 10 01:20:10 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:20:12 cmp02 kernel: [ 7420.637125]  connection2:0: detected conn error (1020)
May 10 01:20:15 cmp02 kernel: [ 7423.647425]  connection2:0: detected conn error (1020)
May 10 01:20:18 cmp02 kernel: [ 7426.654334]  connection2:0: detected conn error (1020)
May 10 01:20:21 cmp02 kernel: [ 7429.662093]  connection2:0: detected conn error (1020)
May 10 01:20:24 cmp02 kernel: [ 7432.669095]  connection2:0: detected conn error (1020)
May 10 01:20:27 cmp02 kernel: [ 7435.676628]  connection2:0: detected conn error (1020)
May 10 01:20:30 cmp02 kernel: [ 7438.684156]  connection2:0: detected conn error (1020)
May 10 01:20:33 cmp02 kernel: [ 7441.692108]  connection2:0: detected conn error (1020)
May 10 01:20:34 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:20:36 cmp02 kernel: [ 7444.697987]  connection2:0: detected conn error (1020)
May 10 01:20:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:20:39 cmp02 kernel: [ 7447.707174]  connection2:0: detected conn error (1020)
May 10 01:20:42 cmp02 kernel: [ 7450.716268]  connection2:0: detected conn error (1020)
May 10 01:20:45 cmp02 kernel: [ 7453.725224]  connection2:0: detected conn error (1020)
May 10 01:20:48 cmp02 kernel: [ 7456.734148]  connection2:0: detected conn error (1020)
May 10 01:20:51 cmp02 kernel: [ 7459.740340]  connection2:0: detected conn error (1020)
May 10 01:20:54 cmp02 kernel: [ 7462.746657]  connection2:0: detected conn error (1020)
May 10 01:20:57 cmp02 kernel: [ 7465.754212]  connection2:0: detected conn error (1020)
May 10 01:20:55 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:20:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:21:00 cmp02 kernel: [ 7468.761291]  connection2:0: detected conn error (1020)
May 10 01:21:03 cmp02 kernel: [ 7471.768459]  connection2:0: detected conn error (1020)
May 10 01:21:06 cmp02 kernel: [ 7474.774921]  connection2:0: detected conn error (1020)
May 10 01:21:09 cmp02 kernel: [ 7477.783216]  connection2:0: detected conn error (1020)
May 10 01:21:12 cmp02 kernel: [ 7480.790592]  connection2:0: detected conn error (1020)
May 10 01:21:15 cmp02 kernel: [ 7483.796871]  connection2:0: detected conn error (1020)
May 10 01:21:18 cmp02 kernel: [ 7486.803525]  connection2:0: detected conn error (1020)
May 10 01:21:21 cmp02 kernel: [ 7489.810497]  connection2:0: detected conn error (1020)
May 10 01:21:24 cmp02 kernel: [ 7492.817560]  connection2:0: detected conn error (1020)
May 10 01:21:27 cmp02 kernel: [ 7495.825328]  connection2:0: detected conn error (1020)
May 10 01:21:30 cmp02 kernel: [ 7498.833322]  connection2:0: detected conn error (1020)
May 10 01:21:33 cmp02 kernel: [ 7501.841161]  connection2:0: detected conn error (1020)
May 10 01:21:34 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:21:36 cmp02 kernel: [ 7504.853200]  connection2:0: detected conn error (1020)
May 10 01:21:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:21:39 cmp02 kernel: [ 7507.861065]  connection2:0: detected conn error (1020)
May 10 01:21:42 cmp02 kernel: [ 7510.872361]  connection2:0: detected conn error (1020)
May 10 01:21:45 cmp02 kernel: [ 7513.879338]  connection2:0: detected conn error (1020)
May 10 01:21:48 cmp02 kernel: [ 7516.886493]  connection2:0: detected conn error (1020)
May 10 01:21:51 cmp02 kernel: [ 7519.892149]  connection2:0: detected conn error (1020)
May 10 01:21:54 cmp02 kernel: [ 7522.898809]  connection2:0: detected conn error (1020)
May 10 01:21:57 cmp02 kernel: [ 7525.906647]  connection2:0: detected conn error (1020)
May 10 01:21:55 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:21:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:22:00 cmp02 kernel: [ 7528.913686]  connection2:0: detected conn error (1020)
May 10 01:22:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:22:03 cmp02 kernel: [ 7531.921384]  connection2:0: detected conn error (1020)
May 10 01:22:06 cmp02 kernel: [ 7534.926830]  connection2:0: detected conn error (1020)
May 10 01:22:10 cmp02 kernel: [ 7537.934653]  connection2:0: detected conn error (1020)
May 10 01:22:13 cmp02 kernel: [ 7540.942931]  connection2:0: detected conn error (1020)
May 10 01:22:16 cmp02 kernel: [ 7543.950754]  connection2:0: detected conn error (1020)
May 10 01:22:19 cmp02 kernel: [ 7546.961242]  connection2:0: detected conn error (1020)
May 10 01:22:22 cmp02 kernel: [ 7549.966761]  connection2:0: detected conn error (1020)
May 10 01:22:25 cmp02 kernel: [ 7552.975314]  connection2:0: detected conn error (1020)
May 10 01:22:28 cmp02 kernel: [ 7555.981433]  connection2:0: detected conn error (1020)
May 10 01:22:31 cmp02 kernel: [ 7558.989600]  connection2:0: detected conn error (1020)
May 10 01:22:34 cmp02 kernel: [ 7561.995867]  connection2:0: detected conn error (1020)
May 10 01:22:32 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:22:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:22:37 cmp02 kernel: [ 7565.005589]  connection2:0: detected conn error (1020)
May 10 01:22:40 cmp02 kernel: [ 7568.011893]  connection2:0: detected conn error (1020)
May 10 01:22:43 cmp02 kernel: [ 7571.019368]  connection2:0: detected conn error (1020)
May 10 01:22:46 cmp02 kernel: [ 7574.025673]  connection2:0: detected conn error (1020)
May 10 01:22:49 cmp02 kernel: [ 7577.033663]  connection2:0: detected conn error (1020)
May 10 01:22:52 cmp02 kernel: [ 7580.043349]  connection2:0: detected conn error (1020)
May 10 01:22:55 cmp02 kernel: [ 7583.053193]  connection2:0: detected conn error (1020)
May 10 01:22:58 cmp02 kernel: [ 7586.061970]  connection2:0: detected conn error (1020)
May 10 01:22:56 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:22:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:23:01 cmp02 kernel: [ 7589.071774]  connection2:0: detected conn error (1020)
May 10 01:23:04 cmp02 kernel: [ 7592.077752]  connection2:0: detected conn error (1020)
May 10 01:23:07 cmp02 kernel: [ 7595.086780]  connection2:0: detected conn error (1020)
May 10 01:23:10 cmp02 kernel: [ 7598.095458]  connection2:0: detected conn error (1020)
May 10 01:23:13 cmp02 kernel: [ 7601.103240]  connection2:0: detected conn error (1020)
May 10 01:23:14 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:23:16 cmp02 kernel: [ 7604.109870]  connection2:0: detected conn error (1020)
May 10 01:23:16 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:23:17 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:23:18 cmp02 kernel: [ 7606.152842] audit: type=1400 audit(1525915398.213:248): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-c4603357-1e1f-4d06-8471-5fc9da9559c3" pid=22126 comm="apparmor_parser"
May 10 01:23:18 cmp02 kernel: [ 7606.396158] audit: type=1400 audit(1525915398.456:249): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c4603357-1e1f-4d06-8471-5fc9da9559c3" pid=22129 comm="apparmor_parser"
May 10 01:23:18 cmp02 kernel: [ 7606.643356] audit: type=1400 audit(1525915398.703:250): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c4603357-1e1f-4d06-8471-5fc9da9559c3" pid=22132 comm="apparmor_parser"
May 10 01:23:18 cmp02 kernel: [ 7606.884284] audit: type=1400 audit(1525915398.944:251): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-c4603357-1e1f-4d06-8471-5fc9da9559c3" pid=22135 comm="apparmor_parser"
May 10 01:23:18 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapc3bafb86-01 -- add-port br-int tapc3bafb86-01 -- set Interface tapc3bafb86-01 "external-ids:attached-mac=\"fa:16:3e:ef:f8:ae\"" -- set Interface tapc3bafb86-01 "external-ids:iface-id=\"c3bafb86-014b-4bdb-aae9-520a27a80914\"" -- set Interface tapc3bafb86-01 "external-ids:vm-id=\"c4603357-1e1f-4d06-8471-5fc9da9559c3\"" -- set Interface tapc3bafb86-01 external-ids:iface-status=active
May 10 01:23:19 cmp02 kernel: [ 7606.936312] device tapc3bafb86-01 entered promiscuous mode
May 10 01:23:19 cmp02 kernel: [ 7607.116617]  connection2:0: detected conn error (1020)
May 10 01:23:19 cmp02 kernel: [ 7607.182171] audit: type=1400 audit(1525915399.242:252): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-c4603357-1e1f-4d06-8471-5fc9da9559c3" pid=22210 comm="apparmor_parser"
May 10 01:23:19 cmp02 libvirtd[5599]: 2018-05-10 01:23:19.249+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=38 name='instance-00000053' uuid=c4603357-1e1f-4d06-8471-5fc9da9559c3 is tainted: host-cpu
May 10 01:23:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:23:22 cmp02 kernel: [ 7610.122180]  connection2:0: detected conn error (1020)
May 10 01:23:25 cmp02 kernel: [ 7613.127852]  connection2:0: detected conn error (1020)
May 10 01:23:25 cmp02 kernel: [ 7613.674000] device tapc3bafb86-01 left promiscuous mode
May 10 01:23:26 cmp02 kernel: [ 7614.067884] audit: type=1400 audit(1525915406.128:253): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-c4603357-1e1f-4d06-8471-5fc9da9559c3" pid=22278 comm="apparmor_parser"
May 10 01:23:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:23:26 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapc3bafb86-01
May 10 01:23:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:23:28 cmp02 kernel: [ 7616.134349]  connection2:0: detected conn error (1020)
May 10 01:23:31 cmp02 kernel: [ 7619.143966]  connection2:0: detected conn error (1020)
May 10 01:23:34 cmp02 kernel: [ 7622.152579]  connection2:0: detected conn error (1020)
May 10 01:23:32 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:23:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:23:37 cmp02 kernel: [ 7625.161839]  connection2:0: detected conn error (1020)
May 10 01:23:40 cmp02 kernel: [ 7628.168461]  connection2:0: detected conn error (1020)
May 10 01:23:43 cmp02 kernel: [ 7631.176832]  connection2:0: detected conn error (1020)
May 10 01:23:46 cmp02 kernel: [ 7634.185707]  connection2:0: detected conn error (1020)
May 10 01:23:49 cmp02 kernel: [ 7637.194372]  connection2:0: detected conn error (1020)
May 10 01:23:52 cmp02 kernel: [ 7640.202767]  connection2:0: detected conn error (1020)
May 10 01:23:55 cmp02 kernel: [ 7643.210500]  connection2:0: detected conn error (1020)
May 10 01:23:58 cmp02 kernel: [ 7646.219971]  connection2:0: detected conn error (1020)
May 10 01:23:56 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:23:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:01 cmp02 kernel: [ 7649.227452]  connection2:0: detected conn error (1020)
May 10 01:24:02 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:04 cmp02 kernel: [ 7652.232844]  connection2:0: detected conn error (1020)
May 10 01:24:07 cmp02 kernel: [ 7655.238880]  connection2:0: detected conn error (1020)
May 10 01:24:10 cmp02 kernel: [ 7658.244261]  connection2:0: detected conn error (1020)
May 10 01:24:13 cmp02 kernel: [ 7661.251936]  connection2:0: detected conn error (1020)
May 10 01:24:16 cmp02 kernel: [ 7664.259081]  connection2:0: detected conn error (1020)
May 10 01:24:19 cmp02 kernel: [ 7667.283649]  connection2:0: detected conn error (1020)
May 10 01:24:22 cmp02 kernel: [ 7670.291114]  connection2:0: detected conn error (1020)
May 10 01:24:25 cmp02 kernel: [ 7673.298648]  connection2:0: detected conn error (1020)
May 10 01:24:28 cmp02 kernel: [ 7676.306586]  connection2:0: detected conn error (1020)
May 10 01:24:26 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:24:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:31 cmp02 kernel: [ 7679.315182]  connection2:0: detected conn error (1020)
May 10 01:24:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:34 cmp02 kernel: [ 7682.322644]  connection2:0: detected conn error (1020)
May 10 01:24:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:37 cmp02 kernel: [ 7685.327695]  connection2:0: detected conn error (1020)
May 10 01:24:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:40 cmp02 kernel: [ 7688.336100]  connection2:0: detected conn error (1020)
May 10 01:24:43 cmp02 kernel: [ 7691.346073]  connection2:0: detected conn error (1020)
May 10 01:24:46 cmp02 kernel: [ 7694.353697]  connection2:0: detected conn error (1020)
May 10 01:24:44 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:24:47 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:49 cmp02 kernel: [ 7697.360573]  connection2:0: detected conn error (1020)
May 10 01:24:50 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:52 cmp02 kernel: [ 7700.368557]  connection2:0: detected conn error (1020)
May 10 01:24:53 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:55 cmp02 kernel: [ 7703.376191]  connection2:0: detected conn error (1020)
May 10 01:24:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:24:58 cmp02 kernel: [ 7706.382507]  connection2:0: detected conn error (1020)
May 10 01:25:01 cmp02 kernel: [ 7709.388064]  connection2:0: detected conn error (1020)
May 10 01:24:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:25:02 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:25:04 cmp02 kernel: [ 7712.397079]  connection2:0: detected conn error (1020)
May 10 01:25:07 cmp02 kernel: [ 7715.404103]  connection2:0: detected conn error (1020)
May 10 01:25:10 cmp02 kernel: [ 7718.409754]  connection2:0: detected conn error (1020)
May 10 01:25:13 cmp02 kernel: [ 7721.417086]  connection2:0: detected conn error (1020)
May 10 01:25:16 cmp02 kernel: [ 7724.426017]  connection2:0: detected conn error (1020)
May 10 01:25:19 cmp02 kernel: [ 7727.431052]  connection2:0: detected conn error (1020)
May 10 01:25:22 cmp02 kernel: [ 7730.438791]  connection2:0: detected conn error (1020)
May 10 01:25:25 cmp02 kernel: [ 7733.445028]  connection2:0: detected conn error (1020)
May 10 01:25:28 cmp02 kernel: [ 7736.450332]  connection2:0: detected conn error (1020)
May 10 01:25:31 cmp02 kernel: [ 7739.458190]  connection2:0: detected conn error (1020)
May 10 01:25:32 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:25:34 cmp02 kernel: [ 7742.465312]  connection2:0: detected conn error (1020)
May 10 01:25:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:25:37 cmp02 kernel: [ 7745.473513]  connection2:0: detected conn error (1020)
May 10 01:25:40 cmp02 kernel: [ 7748.480703]  connection2:0: detected conn error (1020)
May 10 01:25:43 cmp02 kernel: [ 7751.490470]  connection2:0: detected conn error (1020)
May 10 01:25:46 cmp02 kernel: [ 7754.500673]  connection2:0: detected conn error (1020)
May 10 01:25:49 cmp02 kernel: [ 7757.507915]  connection2:0: detected conn error (1020)
May 10 01:25:52 cmp02 kernel: [ 7760.516954]  connection2:0: detected conn error (1020)
May 10 01:25:55 cmp02 kernel: [ 7763.523228]  connection2:0: detected conn error (1020)
May 10 01:25:58 cmp02 kernel: [ 7766.533274]  connection2:0: detected conn error (1020)
May 10 01:26:01 cmp02 kernel: [ 7769.539866]  connection2:0: detected conn error (1020)
May 10 01:26:02 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:26:04 cmp02 kernel: [ 7772.547705]  connection2:0: detected conn error (1020)
May 10 01:26:05 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:26:07 cmp02 kernel: [ 7775.563251]  connection2:0: detected conn error (1020)
May 10 01:26:10 cmp02 kernel: [ 7778.571096]  connection2:0: detected conn error (1020)
May 10 01:26:13 cmp02 kernel: [ 7781.577857]  connection2:0: detected conn error (1020)
May 10 01:26:16 cmp02 kernel: [ 7784.585368]  connection2:0: detected conn error (1020)
May 10 01:26:19 cmp02 kernel: [ 7787.593547]  connection2:0: detected conn error (1020)
May 10 01:26:22 cmp02 kernel: [ 7790.600382]  connection2:0: detected conn error (1020)
May 10 01:26:25 cmp02 kernel: [ 7793.607556]  connection2:0: detected conn error (1020)
May 10 01:26:28 cmp02 kernel: [ 7796.612955]  connection2:0: detected conn error (1020)
May 10 01:26:31 cmp02 kernel: [ 7799.619944]  connection2:0: detected conn error (1020)
May 10 01:26:32 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:26:34 cmp02 kernel: [ 7802.625606]  connection2:0: detected conn error (1020)
May 10 01:26:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:26:37 cmp02 kernel: [ 7805.634931]  connection2:0: detected conn error (1020)
May 10 01:26:40 cmp02 kernel: [ 7808.643781]  connection2:0: detected conn error (1020)
May 10 01:26:43 cmp02 kernel: [ 7811.653417]  connection2:0: detected conn error (1020)
May 10 01:26:46 cmp02 kernel: [ 7814.659709]  connection2:0: detected conn error (1020)
May 10 01:26:49 cmp02 kernel: [ 7817.668794]  connection2:0: detected conn error (1020)
May 10 01:26:52 cmp02 kernel: [ 7820.675596]  connection2:0: detected conn error (1020)
May 10 01:26:55 cmp02 kernel: [ 7823.681489]  connection2:0: detected conn error (1020)
May 10 01:26:58 cmp02 kernel: [ 7826.690339]  connection2:0: detected conn error (1020)
May 10 01:27:01 cmp02 kernel: [ 7829.697369]  connection2:0: detected conn error (1020)
May 10 01:27:02 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:27:04 cmp02 kernel: [ 7832.705025]  connection2:0: detected conn error (1020)
May 10 01:27:05 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:27:07 cmp02 kernel: [ 7835.711430]  connection2:0: detected conn error (1020)
May 10 01:27:10 cmp02 kernel: [ 7838.717994]  connection2:0: detected conn error (1020)
May 10 01:27:13 cmp02 kernel: [ 7841.723608]  connection2:0: detected conn error (1020)
May 10 01:27:16 cmp02 kernel: [ 7844.729756]  connection2:0: detected conn error (1020)
May 10 01:27:19 cmp02 kernel: [ 7847.738085]  connection2:0: detected conn error (1020)
May 10 01:27:22 cmp02 kernel: [ 7850.744078]  connection2:0: detected conn error (1020)
May 10 01:27:25 cmp02 kernel: [ 7853.751310]  connection2:0: detected conn error (1020)
May 10 01:27:28 cmp02 kernel: [ 7856.757946]  connection2:0: detected conn error (1020)
May 10 01:27:31 cmp02 kernel: [ 7859.766792]  connection2:0: detected conn error (1020)
May 10 01:27:32 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:27:34 cmp02 kernel: [ 7862.774580]  connection2:0: detected conn error (1020)
May 10 01:27:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:27:37 cmp02 kernel: [ 7865.782449]  connection2:0: detected conn error (1020)
May 10 01:27:40 cmp02 kernel: [ 7868.789530]  connection2:0: detected conn error (1020)
May 10 01:27:43 cmp02 kernel: [ 7871.797424]  connection2:0: detected conn error (1020)
May 10 01:27:46 cmp02 kernel: [ 7874.806591]  connection2:0: detected conn error (1020)
May 10 01:27:49 cmp02 kernel: [ 7877.815918]  connection2:0: detected conn error (1020)
May 10 01:27:52 cmp02 kernel: [ 7880.822448]  connection2:0: detected conn error (1020)
May 10 01:27:55 cmp02 kernel: [ 7883.830814]  connection2:0: detected conn error (1020)
May 10 01:27:58 cmp02 kernel: [ 7886.838428]  connection2:0: detected conn error (1020)
May 10 01:28:01 cmp02 kernel: [ 7889.845104]  connection2:0: detected conn error (1020)
May 10 01:28:02 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:28:04 cmp02 kernel: [ 7892.852979]  connection2:0: detected conn error (1020)
May 10 01:28:05 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:07 cmp02 kernel: [ 7895.859844]  connection2:0: detected conn error (1020)
May 10 01:28:10 cmp02 kernel: [ 7898.866416]  connection2:0: detected conn error (1020)
May 10 01:28:13 cmp02 kernel: [ 7901.875555]  connection2:0: detected conn error (1020)
May 10 01:28:16 cmp02 kernel: [ 7904.880550]  connection2:0: detected conn error (1020)
May 10 01:28:19 cmp02 kernel: [ 7907.885962]  connection2:0: detected conn error (1020)
May 10 01:28:20 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:28:22 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:28:22 cmp02 kernel: [ 7910.893331]  connection2:0: detected conn error (1020)
May 10 01:28:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:24 cmp02 kernel: [ 7912.228030] audit: type=1400 audit(1525915704.282:254): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-33ca4fcb-9fb2-4929-8126-b512e66af72a" pid=22606 comm="apparmor_parser"
May 10 01:28:24 cmp02 kernel: [ 7912.474740] audit: type=1400 audit(1525915704.529:255): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-33ca4fcb-9fb2-4929-8126-b512e66af72a" pid=22609 comm="apparmor_parser"
May 10 01:28:24 cmp02 kernel: [ 7912.718298] audit: type=1400 audit(1525915704.773:256): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-33ca4fcb-9fb2-4929-8126-b512e66af72a" pid=22612 comm="apparmor_parser"
May 10 01:28:25 cmp02 kernel: [ 7912.979352] audit: type=1400 audit(1525915705.034:257): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-33ca4fcb-9fb2-4929-8126-b512e66af72a" pid=22615 comm="apparmor_parser"
May 10 01:28:25 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap5e0ad53c-a8 -- add-port br-int tap5e0ad53c-a8 -- set Interface tap5e0ad53c-a8 "external-ids:attached-mac=\"fa:16:3e:39:9e:76\"" -- set Interface tap5e0ad53c-a8 "external-ids:iface-id=\"5e0ad53c-a849-42bf-bb5b-3f969e906c6c\"" -- set Interface tap5e0ad53c-a8 "external-ids:vm-id=\"33ca4fcb-9fb2-4929-8126-b512e66af72a\"" -- set Interface tap5e0ad53c-a8 external-ids:iface-status=active
May 10 01:28:25 cmp02 kernel: [ 7913.039260] device tap5e0ad53c-a8 entered promiscuous mode
May 10 01:28:25 cmp02 kernel: [ 7913.281549] audit: type=1400 audit(1525915705.335:258): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-33ca4fcb-9fb2-4929-8126-b512e66af72a" pid=22720 comm="apparmor_parser"
May 10 01:28:25 cmp02 libvirtd[5599]: 2018-05-10 01:28:25.342+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=39 name='instance-00000057' uuid=33ca4fcb-9fb2-4929-8126-b512e66af72a is tainted: host-cpu
May 10 01:28:25 cmp02 kernel: [ 7913.904531]  connection2:0: detected conn error (1020)
May 10 01:28:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:28 cmp02 kernel: [ 7916.909480]  connection2:0: detected conn error (1020)
May 10 01:28:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:31 cmp02 kernel: [ 7919.916375]  connection2:0: detected conn error (1020)
May 10 01:28:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:34 cmp02 kernel: [ 7922.921789]  connection2:0: detected conn error (1020)
May 10 01:28:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:37 cmp02 kernel: [ 7925.929045]  connection2:0: detected conn error (1020)
May 10 01:28:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:40 cmp02 kernel: [ 7928.936366]  connection2:0: detected conn error (1020)
May 10 01:28:41 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:28:44 cmp02 kernel: [ 7931.944172]  connection2:0: detected conn error (1020)
May 10 01:28:47 cmp02 kernel: [ 7934.949585]  connection2:0: detected conn error (1020)
May 10 01:28:50 cmp02 kernel: [ 7937.957207]  connection2:0: detected conn error (1020)
May 10 01:28:53 cmp02 kernel: [ 7940.966588]  connection2:0: detected conn error (1020)
May 10 01:28:56 cmp02 kernel: [ 7943.977279]  connection2:0: detected conn error (1020)
May 10 01:28:59 cmp02 kernel: [ 7946.984777]  connection2:0: detected conn error (1020)
May 10 01:29:02 cmp02 kernel: [ 7949.991662]  connection2:0: detected conn error (1020)
May 10 01:29:02 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:29:05 cmp02 kernel: [ 7953.001335]  connection2:0: detected conn error (1020)
May 10 01:29:05 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:29:07 cmp02 libvirtd[5599]: 2018-05-10 01:29:07.051+0000: 5611: error : virProcessKillPainfully:401 : Failed to terminate process 22724 with SIGKILL: Device or resource busy
May 10 01:29:07 cmp02 libvirtd[5599]: 2018-05-10 01:29:07.057+0000: 5611: warning : qemuGetProcessInfo:1460 : cannot parse process status data
May 10 01:29:07 cmp02 libvirtd[5599]: 2018-05-10 01:29:07.057+0000: 5611: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 22742: No such process
May 10 01:29:08 cmp02 kernel: [ 7956.006652]  connection2:0: detected conn error (1020)
May 10 01:29:08 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:29:11 cmp02 kernel: [ 7959.014819]  connection2:0: detected conn error (1020)
May 10 01:29:14 cmp02 kernel: [ 7962.021772]  connection2:0: detected conn error (1020)
May 10 01:29:17 cmp02 kernel: [ 7965.035117]  connection2:0: detected conn error (1020)
May 10 01:29:20 cmp02 kernel: [ 7968.044855]  connection2:0: detected conn error (1020)
May 10 01:29:20 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:29:22 cmp02 libvirtd[5599]: 2018-05-10 01:29:22.098+0000: 5616: error : virProcessKillPainfully:401 : Failed to terminate process 22724 with SIGKILL: Device or resource busy
May 10 01:29:23 cmp02 kernel: [ 7971.057285]  connection2:0: detected conn error (1020)
May 10 01:29:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:29:26 cmp02 kernel: [ 7974.066896]  connection2:0: detected conn error (1020)
May 10 01:29:29 cmp02 kernel: [ 7977.076623]  connection2:0: detected conn error (1020)
May 10 01:29:32 cmp02 kernel: [ 7980.084048]  connection2:0: detected conn error (1020)
May 10 01:29:32 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:29:35 cmp02 kernel: [ 7983.094937]  connection2:0: detected conn error (1020)
May 10 01:29:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:29:37 cmp02 libvirtd[5599]: 2018-05-10 01:29:37.140+0000: 5612: error : virProcessKillPainfully:401 : Failed to terminate process 22724 with SIGKILL: Device or resource busy
May 10 01:29:38 cmp02 kernel: [ 7986.109206]  connection2:0: detected conn error (1020)
May 10 01:29:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:29:41 cmp02 kernel: [ 7989.117120]  connection2:0: detected conn error (1020)
May 10 01:29:44 cmp02 kernel: [ 7992.124443]  connection2:0: detected conn error (1020)
May 10 01:29:47 cmp02 kernel: [ 7995.134430]  connection2:0: detected conn error (1020)
May 10 01:29:50 cmp02 kernel: [ 7998.141175]  connection2:0: detected conn error (1020)
May 10 01:29:53 cmp02 kernel: [ 8001.149577]  connection2:0: detected conn error (1020)
May 10 01:29:56 cmp02 kernel: [ 8004.167322]  connection2:0: detected conn error (1020)
May 10 01:29:59 cmp02 kernel: [ 8007.173789]  connection2:0: detected conn error (1020)
May 10 01:30:02 cmp02 kernel: [ 8010.183938]  connection2:0: detected conn error (1020)
May 10 01:30:03 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:30:05 cmp02 kernel: [ 8013.189966]  connection2:0: detected conn error (1020)
May 10 01:30:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:30:06 cmp02 libvirtd[5599]: 2018-05-10 01:30:06.995+0000: 5608: warning : qemuGetProcessInfo:1460 : cannot parse process status data
May 10 01:30:06 cmp02 libvirtd[5599]: 2018-05-10 01:30:06.995+0000: 5608: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 22742: No such process
May 10 01:30:08 cmp02 kernel: [ 8016.198832]  connection2:0: detected conn error (1020)
May 10 01:30:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:30:11 cmp02 kernel: [ 8019.208292]  connection2:0: detected conn error (1020)
May 10 01:30:14 cmp02 kernel: [ 8022.214528]  connection2:0: detected conn error (1020)
May 10 01:30:17 cmp02 kernel: [ 8025.220780]  connection2:0: detected conn error (1020)
May 10 01:30:20 cmp02 kernel: [ 8028.228601]  connection2:0: detected conn error (1020)
May 10 01:30:23 cmp02 kernel: [ 8031.233504]  connection2:0: detected conn error (1020)
May 10 01:30:25 cmp02 kernel: [ 8033.552923] device tap5e0ad53c-a8 left promiscuous mode
May 10 01:30:24 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:30:25 cmp02 libvirtd[5599]: 2018-05-10 01:30:25.624+0000: 5599: error : qemuMonitorIORead:610 : Unable to read from monitor: Connection reset by peer
May 10 01:30:26 cmp02 kernel: [ 8034.005702] audit: type=1400 audit(1525915826.058:259): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-33ca4fcb-9fb2-4929-8126-b512e66af72a" pid=22966 comm="apparmor_parser"
May 10 01:30:26 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap5e0ad53c-a8
May 10 01:30:26 cmp02 kernel: [ 8034.240832]  connection2:0: detected conn error (1020)
May 10 01:30:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:30:29 cmp02 kernel: [ 8037.248962]  connection2:0: detected conn error (1020)
May 10 01:30:32 cmp02 kernel: [ 8040.256258]  connection2:0: detected conn error (1020)
May 10 01:30:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:30:35 cmp02 kernel: [ 8043.263959]  connection2:0: detected conn error (1020)
May 10 01:30:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:30:38 cmp02 kernel: [ 8046.272505]  connection2:0: detected conn error (1020)
May 10 01:30:41 cmp02 kernel: [ 8049.279214]  connection2:0: detected conn error (1020)
May 10 01:30:44 cmp02 kernel: [ 8052.286844]  connection2:0: detected conn error (1020)
May 10 01:30:47 cmp02 kernel: [ 8055.292861]  connection2:0: detected conn error (1020)
May 10 01:30:50 cmp02 kernel: [ 8058.301992]  connection2:0: detected conn error (1020)
May 10 01:30:53 cmp02 kernel: [ 8061.308637]  connection2:0: detected conn error (1020)
May 10 01:30:56 cmp02 kernel: [ 8064.314601]  connection2:0: detected conn error (1020)
May 10 01:30:59 cmp02 kernel: [ 8067.320439]  connection2:0: detected conn error (1020)
May 10 01:31:02 cmp02 kernel: [ 8070.328931]  connection2:0: detected conn error (1020)
May 10 01:31:03 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:31:05 cmp02 kernel: [ 8073.335129]  connection2:0: detected conn error (1020)
May 10 01:31:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:31:08 cmp02 kernel: [ 8076.341465]  connection2:0: detected conn error (1020)
May 10 01:31:11 cmp02 kernel: [ 8079.347680]  connection2:0: detected conn error (1020)
May 10 01:31:14 cmp02 kernel: [ 8082.353656]  connection2:0: detected conn error (1020)
May 10 01:31:17 cmp02 kernel: [ 8085.362020]  connection2:0: detected conn error (1020)
May 10 01:31:20 cmp02 kernel: [ 8088.368655]  connection2:0: detected conn error (1020)
May 10 01:31:23 cmp02 kernel: [ 8091.375139]  connection2:0: detected conn error (1020)
May 10 01:31:26 cmp02 kernel: [ 8094.384945]  connection2:0: detected conn error (1020)
May 10 01:31:29 cmp02 kernel: [ 8097.393120]  connection2:0: detected conn error (1020)
May 10 01:31:32 cmp02 kernel: [ 8100.399572]  connection2:0: detected conn error (1020)
May 10 01:31:33 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:31:35 cmp02 kernel: [ 8103.407725]  connection2:0: detected conn error (1020)
May 10 01:31:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:31:38 cmp02 kernel: [ 8106.414256]  connection2:0: detected conn error (1020)
May 10 01:31:41 cmp02 kernel: [ 8109.421193]  connection2:0: detected conn error (1020)
May 10 01:31:44 cmp02 kernel: [ 8112.427110]  connection2:0: detected conn error (1020)
May 10 01:31:47 cmp02 kernel: [ 8115.435756]  connection2:0: detected conn error (1020)
May 10 01:31:50 cmp02 kernel: [ 8118.442276]  connection2:0: detected conn error (1020)
May 10 01:31:53 cmp02 kernel: [ 8121.447377]  connection2:0: detected conn error (1020)
May 10 01:31:56 cmp02 kernel: [ 8124.453524]  connection2:0: detected conn error (1020)
May 10 01:31:59 cmp02 kernel: [ 8127.463338]  connection2:0: detected conn error (1020)
May 10 01:32:02 cmp02 kernel: [ 8130.475451]  connection2:0: detected conn error (1020)
May 10 01:32:03 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:32:05 cmp02 kernel: [ 8133.485689]  connection2:0: detected conn error (1020)
May 10 01:32:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:32:08 cmp02 kernel: [ 8136.493158]  connection2:0: detected conn error (1020)
May 10 01:32:11 cmp02 kernel: [ 8139.502630]  connection2:0: detected conn error (1020)
May 10 01:32:14 cmp02 kernel: [ 8142.512061]  connection2:0: detected conn error (1020)
May 10 01:32:17 cmp02 kernel: [ 8145.524896]  connection2:0: detected conn error (1020)
May 10 01:32:20 cmp02 kernel: [ 8148.533354]  connection2:0: detected conn error (1020)
May 10 01:32:23 cmp02 kernel: [ 8151.542430]  connection2:0: detected conn error (1020)
May 10 01:32:26 cmp02 kernel: [ 8154.554856]  connection2:0: detected conn error (1020)
May 10 01:32:29 cmp02 kernel: [ 8157.562981]  connection2:0: detected conn error (1020)
May 10 01:32:32 cmp02 kernel: [ 8160.570877]  connection2:0: detected conn error (1020)
May 10 01:32:33 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:32:35 cmp02 kernel: [ 8163.579862]  connection2:0: detected conn error (1020)
May 10 01:32:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:32:38 cmp02 kernel: [ 8166.586574]  connection2:0: detected conn error (1020)
May 10 01:32:41 cmp02 kernel: [ 8169.592719]  connection2:0: detected conn error (1020)
May 10 01:32:44 cmp02 kernel: [ 8172.599639]  connection2:0: detected conn error (1020)
May 10 01:32:47 cmp02 kernel: [ 8175.608452]  connection2:0: detected conn error (1020)
May 10 01:32:50 cmp02 kernel: [ 8178.614977]  connection2:0: detected conn error (1020)
May 10 01:32:53 cmp02 kernel: [ 8181.625618]  connection2:0: detected conn error (1020)
May 10 01:32:56 cmp02 kernel: [ 8184.638288]  connection2:0: detected conn error (1020)
May 10 01:32:59 cmp02 kernel: [ 8187.646358]  connection2:0: detected conn error (1020)
May 10 01:33:02 cmp02 kernel: [ 8190.654704]  connection2:0: detected conn error (1020)
May 10 01:33:05 cmp02 kernel: [ 8193.667974]  connection2:0: detected conn error (1020)
May 10 01:33:03 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:33:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:33:08 cmp02 kernel: [ 8196.674155]  connection2:0: detected conn error (1020)
May 10 01:33:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:33:11 cmp02 kernel: [ 8199.680153]  connection2:0: detected conn error (1020)
May 10 01:33:14 cmp02 kernel: [ 8202.691300]  connection2:0: detected conn error (1020)
May 10 01:33:17 cmp02 kernel: [ 8205.699015]  connection2:0: detected conn error (1020)
May 10 01:33:20 cmp02 kernel: [ 8208.706966]  connection2:0: detected conn error (1020)
May 10 01:33:23 cmp02 kernel: [ 8211.712570]  connection2:0: detected conn error (1020)
May 10 01:33:26 cmp02 kernel: [ 8214.719047]  connection2:0: detected conn error (1020)
May 10 01:33:29 cmp02 kernel: [ 8217.724602]  connection2:0: detected conn error (1020)
May 10 01:33:32 cmp02 kernel: [ 8220.731516]  connection2:0: detected conn error (1020)
May 10 01:33:33 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:33:35 cmp02 kernel: [ 8223.738066]  connection2:0: detected conn error (1020)
May 10 01:33:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:33:38 cmp02 kernel: [ 8226.744023]  connection2:0: detected conn error (1020)
May 10 01:33:41 cmp02 kernel: [ 8229.751340]  connection2:0: detected conn error (1020)
May 10 01:33:44 cmp02 kernel: [ 8232.763507]  connection2:0: detected conn error (1020)
May 10 01:33:47 cmp02 kernel: [ 8235.770415]  connection2:0: detected conn error (1020)
May 10 01:33:50 cmp02 kernel: [ 8238.778802]  connection2:0: detected conn error (1020)
May 10 01:33:53 cmp02 kernel: [ 8241.786151]  connection2:0: detected conn error (1020)
May 10 01:33:56 cmp02 kernel: [ 8244.794329]  connection2:0: detected conn error (1020)
May 10 01:33:59 cmp02 kernel: [ 8247.801946]  connection2:0: detected conn error (1020)
May 10 01:34:02 cmp02 kernel: [ 8250.811048]  connection2:0: detected conn error (1020)
May 10 01:34:05 cmp02 kernel: [ 8253.818642]  connection2:0: detected conn error (1020)
May 10 01:34:06 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:34:08 cmp02 kernel: [ 8256.825115]  connection2:0: detected conn error (1020)
May 10 01:34:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:34:11 cmp02 kernel: [ 8259.832378]  connection2:0: detected conn error (1020)
May 10 01:34:14 cmp02 kernel: [ 8262.838511]  connection2:0: detected conn error (1020)
May 10 01:34:17 cmp02 kernel: [ 8265.845639]  connection2:0: detected conn error (1020)
May 10 01:34:20 cmp02 kernel: [ 8268.852835]  connection2:0: detected conn error (1020)
May 10 01:34:23 cmp02 kernel: [ 8271.865637]  connection2:0: detected conn error (1020)
May 10 01:34:26 cmp02 kernel: [ 8274.873014]  connection2:0: detected conn error (1020)
May 10 01:34:29 cmp02 kernel: [ 8277.881103]  connection2:0: detected conn error (1020)
May 10 01:34:32 cmp02 kernel: [ 8280.887634]  connection2:0: detected conn error (1020)
May 10 01:34:33 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:34:35 cmp02 kernel: [ 8283.897241]  connection2:0: detected conn error (1020)
May 10 01:34:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:34:38 cmp02 kernel: [ 8286.905428]  connection2:0: detected conn error (1020)
May 10 01:34:41 cmp02 kernel: [ 8289.911364]  connection2:0: detected conn error (1020)
May 10 01:34:42 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:34:44 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:34:44 cmp02 kernel: [ 8292.916911]  connection2:0: detected conn error (1020)
May 10 01:34:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:34:46 cmp02 kernel: [ 8294.066228] audit: type=1400 audit(1525916086.114:260): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-793e77f2-44e5-469c-a85c-1a3822431a95" pid=23194 comm="apparmor_parser"
May 10 01:34:46 cmp02 kernel: [ 8294.315596] audit: type=1400 audit(1525916086.363:261): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-793e77f2-44e5-469c-a85c-1a3822431a95" pid=23197 comm="apparmor_parser"
May 10 01:34:46 cmp02 kernel: [ 8294.570968] audit: type=1400 audit(1525916086.618:262): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-793e77f2-44e5-469c-a85c-1a3822431a95" pid=23200 comm="apparmor_parser"
May 10 01:34:46 cmp02 kernel: [ 8294.817551] audit: type=1400 audit(1525916086.865:263): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-793e77f2-44e5-469c-a85c-1a3822431a95" pid=23203 comm="apparmor_parser"
May 10 01:34:46 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapa9990ed1-cc -- add-port br-int tapa9990ed1-cc -- set Interface tapa9990ed1-cc "external-ids:attached-mac=\"fa:16:3e:4e:b1:d4\"" -- set Interface tapa9990ed1-cc "external-ids:iface-id=\"a9990ed1-ccf6-40f1-93ee-b1e3db71aff7\"" -- set Interface tapa9990ed1-cc "external-ids:vm-id=\"793e77f2-44e5-469c-a85c-1a3822431a95\"" -- set Interface tapa9990ed1-cc external-ids:iface-status=active
May 10 01:34:46 cmp02 kernel: [ 8294.843380] device tapa9990ed1-cc entered promiscuous mode
May 10 01:34:47 cmp02 kernel: [ 8295.091097] audit: type=1400 audit(1525916087.138:264): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-793e77f2-44e5-469c-a85c-1a3822431a95" pid=23270 comm="apparmor_parser"
May 10 01:34:47 cmp02 libvirtd[5599]: 2018-05-10 01:34:47.144+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=40 name='instance-0000005a' uuid=793e77f2-44e5-469c-a85c-1a3822431a95 is tainted: host-cpu
May 10 01:34:47 cmp02 kernel: [ 8295.924711]  connection2:0: detected conn error (1020)
May 10 01:34:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:34:50 cmp02 kernel: [ 8298.932787]  connection2:0: detected conn error (1020)
May 10 01:34:53 cmp02 kernel: [ 8301.937970]  connection2:0: detected conn error (1020)
May 10 01:34:56 cmp02 kernel: [ 8304.943550]  connection2:0: detected conn error (1020)
May 10 01:35:00 cmp02 kernel: [ 8307.949741]  connection2:0: detected conn error (1020)
May 10 01:35:03 cmp02 kernel: [ 8310.956275]  connection2:0: detected conn error (1020)
May 10 01:35:06 cmp02 kernel: [ 8313.964073]  connection2:0: detected conn error (1020)
May 10 01:35:09 cmp02 kernel: [ 8316.973570]  connection2:0: detected conn error (1020)
May 10 01:35:06 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:35:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:35:12 cmp02 kernel: [ 8319.980801]  connection2:0: detected conn error (1020)
May 10 01:35:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:35:15 cmp02 kernel: [ 8322.989147]  connection2:0: detected conn error (1020)
May 10 01:35:18 cmp02 kernel: [ 8326.001341]  connection2:0: detected conn error (1020)
May 10 01:35:21 cmp02 kernel: [ 8329.008338]  connection2:0: detected conn error (1020)
May 10 01:35:24 cmp02 kernel: [ 8332.021328]  connection2:0: detected conn error (1020)
May 10 01:35:27 cmp02 kernel: [ 8335.030690]  connection2:0: detected conn error (1020)
May 10 01:35:30 cmp02 kernel: [ 8338.039029]  connection2:0: detected conn error (1020)
May 10 01:35:33 cmp02 kernel: [ 8341.047872]  connection2:0: detected conn error (1020)
May 10 01:35:33 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:35:36 cmp02 kernel: [ 8344.053954]  connection2:0: detected conn error (1020)
May 10 01:35:36 cmp02 libvirtd[5599]: 2018-05-10 01:35:36.204+0000: 5617: error : virProcessKillPainfully:401 : Failed to terminate process 23312 with SIGKILL: Device or resource busy
May 10 01:35:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:35:39 cmp02 kernel: [ 8347.062465]  connection2:0: detected conn error (1020)
May 10 01:35:42 cmp02 kernel: [ 8350.070383]  connection2:0: detected conn error (1020)
May 10 01:35:45 cmp02 kernel: [ 8353.079639]  connection2:0: detected conn error (1020)
May 10 01:35:48 cmp02 kernel: [ 8356.086365]  connection2:0: detected conn error (1020)
May 10 01:35:51 cmp02 kernel: [ 8359.092173]  connection2:0: detected conn error (1020)
May 10 01:35:48 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:35:51 cmp02 libvirtd[5599]: 2018-05-10 01:35:51.246+0000: 5611: error : virProcessKillPainfully:401 : Failed to terminate process 23312 with SIGKILL: Device or resource busy
May 10 01:35:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:35:54 cmp02 kernel: [ 8362.098396]  connection2:0: detected conn error (1020)
May 10 01:35:57 cmp02 kernel: [ 8365.107064]  connection2:0: detected conn error (1020)
May 10 01:36:00 cmp02 kernel: [ 8368.114629]  connection2:0: detected conn error (1020)
May 10 01:36:03 cmp02 kernel: [ 8371.124245]  connection2:0: detected conn error (1020)
May 10 01:36:06 cmp02 kernel: [ 8374.132565]  connection2:0: detected conn error (1020)
May 10 01:36:03 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:36:06 cmp02 libvirtd[5599]: 2018-05-10 01:36:06.295+0000: 5614: error : virProcessKillPainfully:401 : Failed to terminate process 23312 with SIGKILL: Device or resource busy
May 10 01:36:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:36:09 cmp02 kernel: [ 8377.139616]  connection2:0: detected conn error (1020)
May 10 01:36:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:36:12 cmp02 kernel: [ 8380.145653]  connection2:0: detected conn error (1020)
May 10 01:36:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:36:14 cmp02 libvirtd[5599]: 2018-05-10 01:36:14.999+0000: 5614: warning : qemuGetProcessInfo:1460 : cannot parse process status data
May 10 01:36:15 cmp02 libvirtd[5599]: 2018-05-10 01:36:15.000+0000: 5614: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 23329: No such process
May 10 01:36:15 cmp02 kernel: [ 8383.153216]  connection2:0: detected conn error (1020)
May 10 01:36:15 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:36:18 cmp02 kernel: [ 8386.163704]  connection2:0: detected conn error (1020)
May 10 01:36:21 cmp02 kernel: [ 8389.172271]  connection2:0: detected conn error (1020)
May 10 01:36:24 cmp02 kernel: [ 8392.179491]  connection2:0: detected conn error (1020)
May 10 01:36:27 cmp02 kernel: [ 8395.184638]  connection2:0: detected conn error (1020)
May 10 01:36:30 cmp02 kernel: [ 8398.191293]  connection2:0: detected conn error (1020)
May 10 01:36:33 cmp02 kernel: [ 8401.201536]  connection2:0: detected conn error (1020)
May 10 01:36:33 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:36:36 cmp02 kernel: [ 8404.207734]  connection2:0: detected conn error (1020)
May 10 01:36:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:36:39 cmp02 kernel: [ 8407.216264]  connection2:0: detected conn error (1020)
May 10 01:36:42 cmp02 kernel: [ 8410.222843]  connection2:0: detected conn error (1020)
May 10 01:36:45 cmp02 kernel: [ 8413.229692]  connection2:0: detected conn error (1020)
May 10 01:36:48 cmp02 kernel: [ 8416.237743]  connection2:0: detected conn error (1020)
May 10 01:36:51 cmp02 kernel: [ 8419.244925]  connection2:0: detected conn error (1020)
May 10 01:36:54 cmp02 kernel: [ 8422.251231]  connection2:0: detected conn error (1020)
May 10 01:36:57 cmp02 kernel: [ 8425.256756]  connection2:0: detected conn error (1020)
May 10 01:37:00 cmp02 kernel: [ 8428.263137]  connection2:0: detected conn error (1020)
May 10 01:37:03 cmp02 kernel: [ 8431.268625]  connection2:0: detected conn error (1020)
May 10 01:37:06 cmp02 kernel: [ 8434.276483]  connection2:0: detected conn error (1020)
May 10 01:37:09 cmp02 kernel: [ 8437.282809]  connection2:0: detected conn error (1020)
May 10 01:37:09 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:37:12 cmp02 kernel: [ 8440.289693]  connection2:0: detected conn error (1020)
May 10 01:37:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:15 cmp02 kernel: [ 8443.295724]  connection2:0: detected conn error (1020)
May 10 01:37:15 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:16 cmp02 libvirtd[5599]: 2018-05-10 01:37:16.001+0000: 5608: warning : qemuGetProcessInfo:1460 : cannot parse process status data
May 10 01:37:16 cmp02 libvirtd[5599]: 2018-05-10 01:37:16.001+0000: 5608: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 23329: No such process
May 10 01:37:18 cmp02 kernel: [ 8446.303253]  connection2:0: detected conn error (1020)
May 10 01:37:18 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:21 cmp02 kernel: [ 8449.312580]  connection2:0: detected conn error (1020)
May 10 01:37:23 cmp02 kernel: [ 8451.939880] device tapa9990ed1-cc left promiscuous mode
May 10 01:37:21 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:24 cmp02 libvirtd[5599]: 2018-05-10 01:37:24.004+0000: 5599: error : qemuMonitorIORead:610 : Unable to read from monitor: Connection reset by peer
May 10 01:37:24 cmp02 kernel: [ 8452.322503]  connection2:0: detected conn error (1020)
May 10 01:37:24 cmp02 kernel: [ 8452.397051] audit: type=1400 audit(1525916244.443:265): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-793e77f2-44e5-469c-a85c-1a3822431a95" pid=23558 comm="apparmor_parser"
May 10 01:37:24 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapa9990ed1-cc
May 10 01:37:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:27 cmp02 kernel: [ 8455.328452]  connection2:0: detected conn error (1020)
May 10 01:37:30 cmp02 kernel: [ 8458.333919]  connection2:0: detected conn error (1020)
May 10 01:37:33 cmp02 kernel: [ 8461.340926]  connection2:0: detected conn error (1020)
May 10 01:37:31 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:37:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:36 cmp02 kernel: [ 8464.348829]  connection2:0: detected conn error (1020)
May 10 01:37:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:37:39 cmp02 kernel: [ 8467.358332]  connection2:0: detected conn error (1020)
May 10 01:37:42 cmp02 kernel: [ 8470.368871]  connection2:0: detected conn error (1020)
May 10 01:37:45 cmp02 kernel: [ 8473.377133]  connection2:0: detected conn error (1020)
May 10 01:37:48 cmp02 kernel: [ 8476.385999]  connection2:0: detected conn error (1020)
May 10 01:37:51 cmp02 kernel: [ 8479.393728]  connection2:0: detected conn error (1020)
May 10 01:37:54 cmp02 kernel: [ 8482.402423]  connection2:0: detected conn error (1020)
May 10 01:37:57 cmp02 kernel: [ 8485.412752]  connection2:0: detected conn error (1020)
May 10 01:38:00 cmp02 kernel: [ 8488.424899]  connection2:0: detected conn error (1020)
May 10 01:38:03 cmp02 kernel: [ 8491.431176]  connection2:0: detected conn error (1020)
May 10 01:38:06 cmp02 kernel: [ 8494.436647]  connection2:0: detected conn error (1020)
May 10 01:38:09 cmp02 kernel: [ 8497.443243]  connection2:0: detected conn error (1020)
May 10 01:38:12 cmp02 kernel: [ 8500.454482]  connection2:0: detected conn error (1020)
May 10 01:38:10 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:38:13 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:15 cmp02 kernel: [ 8503.464022]  connection2:0: detected conn error (1020)
May 10 01:38:16 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:18 cmp02 kernel: [ 8506.475392]  connection2:0: detected conn error (1020)
May 10 01:38:21 cmp02 kernel: [ 8509.484619]  connection2:0: detected conn error (1020)
May 10 01:38:24 cmp02 kernel: [ 8512.493248]  connection2:0: detected conn error (1020)
May 10 01:38:27 cmp02 kernel: [ 8515.501338]  connection2:0: detected conn error (1020)
May 10 01:38:30 cmp02 kernel: [ 8518.510672]  connection2:0: detected conn error (1020)
May 10 01:38:33 cmp02 kernel: [ 8521.516818]  connection2:0: detected conn error (1020)
May 10 01:38:31 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:38:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:36 cmp02 kernel: [ 8524.523485]  connection2:0: detected conn error (1020)
May 10 01:38:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:39 cmp02 kernel: [ 8527.531523]  connection2:0: detected conn error (1020)
May 10 01:38:42 cmp02 kernel: [ 8530.543356]  connection2:0: detected conn error (1020)
May 10 01:38:45 cmp02 kernel: [ 8533.551108]  connection2:0: detected conn error (1020)
May 10 01:38:46 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:38:48 cmp02 kernel: [ 8536.556421]  connection2:0: detected conn error (1020)
May 10 01:38:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:51 cmp02 kernel: [ 8539.565205]  connection2:0: detected conn error (1020)
May 10 01:38:54 cmp02 kernel: [ 8542.571731]  connection2:0: detected conn error (1020)
May 10 01:38:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:54 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:38:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:38:56 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:38:56 cmp02 kernel: [ 8544.166473] audit: type=1400 audit(1525916336.211:266): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-fd6e2667-601f-42f7-aa98-2f0307da6c21" pid=23717 comm="apparmor_parser"
May 10 01:38:56 cmp02 kernel: [ 8544.419558] audit: type=1400 audit(1525916336.464:267): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fd6e2667-601f-42f7-aa98-2f0307da6c21" pid=23739 comm="apparmor_parser"
May 10 01:38:56 cmp02 kernel: [ 8544.683947] audit: type=1400 audit(1525916336.728:268): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fd6e2667-601f-42f7-aa98-2f0307da6c21" pid=23743 comm="apparmor_parser"
May 10 01:38:56 cmp02 kernel: [ 8544.924152] audit: type=1400 audit(1525916336.968:269): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-fd6e2667-601f-42f7-aa98-2f0307da6c21" pid=23753 comm="apparmor_parser"
May 10 01:38:56 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3747395b-9b -- add-port br-int tap3747395b-9b -- set Interface tap3747395b-9b "external-ids:attached-mac=\"fa:16:3e:22:ce:56\"" -- set Interface tap3747395b-9b "external-ids:iface-id=\"3747395b-9b88-42bb-ab2f-8eb88ad97c6c\"" -- set Interface tap3747395b-9b "external-ids:vm-id=\"fd6e2667-601f-42f7-aa98-2f0307da6c21\"" -- set Interface tap3747395b-9b external-ids:iface-status=active
May 10 01:38:57 cmp02 kernel: [ 8544.953159] device tap3747395b-9b entered promiscuous mode
May 10 01:38:57 cmp02 kernel: [ 8545.205739] audit: type=1400 audit(1525916337.250:270): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-fd6e2667-601f-42f7-aa98-2f0307da6c21" pid=23814 comm="apparmor_parser"
May 10 01:38:57 cmp02 libvirtd[5599]: 2018-05-10 01:38:57.267+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=41 name='instance-0000005c' uuid=fd6e2667-601f-42f7-aa98-2f0307da6c21 is tainted: host-cpu
May 10 01:38:57 cmp02 kernel: [ 8545.452150] audit: type=1400 audit(1525916337.496:271): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682" pid=23881 comm="apparmor_parser"
May 10 01:38:57 cmp02 kernel: [ 8545.584372]  connection2:0: detected conn error (1020)
May 10 01:38:57 cmp02 kernel: [ 8545.703971] audit: type=1400 audit(1525916337.748:272): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682" pid=23886 comm="apparmor_parser"
May 10 01:38:57 cmp02 kernel: [ 8545.951480] audit: type=1400 audit(1525916337.996:273): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682" pid=23907 comm="apparmor_parser"
May 10 01:38:58 cmp02 kernel: [ 8546.212556] audit: type=1400 audit(1525916338.257:274): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682" pid=23917 comm="apparmor_parser"
May 10 01:38:58 cmp02 systemd-udevd[23920]: Could not generate persistent MAC address for tap9c6c9399-e9: No such file or directory
May 10 01:38:58 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap9c6c9399-e9 -- add-port br-int tap9c6c9399-e9 -- set Interface tap9c6c9399-e9 "external-ids:attached-mac=\"fa:16:3e:ce:ee:54\"" -- set Interface tap9c6c9399-e9 "external-ids:iface-id=\"9c6c9399-e91c-4ba9-a63e-b5b54307d8c0\"" -- set Interface tap9c6c9399-e9 "external-ids:vm-id=\"7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682\"" -- set Interface tap9c6c9399-e9 external-ids:iface-status=active
May 10 01:38:58 cmp02 kernel: [ 8546.253474] device tap9c6c9399-e9 entered promiscuous mode
May 10 01:38:58 cmp02 kernel: [ 8546.495403] audit: type=1400 audit(1525916338.540:275): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682" pid=23979 comm="apparmor_parser"
May 10 01:38:58 cmp02 libvirtd[5599]: 2018-05-10 01:38:58.546+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=42 name='instance-0000005d' uuid=7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682 is tainted: host-cpu
May 10 01:38:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:39:00 cmp02 kernel: [ 8548.590300]  connection2:0: detected conn error (1020)
May 10 01:39:03 cmp02 kernel: [ 8551.595831]  connection2:0: detected conn error (1020)
May 10 01:39:06 cmp02 kernel: [ 8554.602931]  connection2:0: detected conn error (1020)
May 10 01:39:09 cmp02 kernel: [ 8557.609502]  connection2:0: detected conn error (1020)
May 10 01:39:12 cmp02 kernel: [ 8560.615099]  connection2:0: detected conn error (1020)
May 10 01:39:10 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:39:13 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:39:15 cmp02 kernel: [ 8563.624509]  connection2:0: detected conn error (1020)
May 10 01:39:16 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:39:18 cmp02 kernel: [ 8566.630132]  connection2:0: detected conn error (1020)
May 10 01:39:21 cmp02 kernel: [ 8569.638172]  connection2:0: detected conn error (1020)
May 10 01:39:24 cmp02 kernel: [ 8572.644803]  connection2:0: detected conn error (1020)
May 10 01:39:27 cmp02 kernel: [ 8575.654600]  connection2:0: detected conn error (1020)
May 10 01:39:30 cmp02 kernel: [ 8578.663485]  connection2:0: detected conn error (1020)
May 10 01:39:33 cmp02 kernel: [ 8581.670209]  connection2:0: detected conn error (1020)
May 10 01:39:31 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:39:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:39:36 cmp02 kernel: [ 8584.676118]  connection2:0: detected conn error (1020)
May 10 01:39:36 cmp02 kernel: [ 8584.853263] device tap3747395b-9b left promiscuous mode
May 10 01:39:37 cmp02 kernel: [ 8585.439759] audit: type=1400 audit(1525916377.483:276): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-fd6e2667-601f-42f7-aa98-2f0307da6c21" pid=24261 comm="apparmor_parser"
May 10 01:39:37 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3747395b-9b
May 10 01:39:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:39:39 cmp02 kernel: [ 8587.683885]  connection2:0: detected conn error (1020)
May 10 01:39:42 cmp02 kernel: [ 8590.690803]  connection2:0: detected conn error (1020)
May 10 01:39:45 cmp02 kernel: [ 8593.700070]  connection2:0: detected conn error (1020)
May 10 01:39:48 cmp02 kernel: [ 8596.712280]  connection2:0: detected conn error (1020)
May 10 01:39:51 cmp02 kernel: [ 8599.719626]  connection2:0: detected conn error (1020)
May 10 01:39:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:39:52 cmp02 libvirtd[5599]: 2018-05-10 01:39:52.658+0000: 5619: error : virProcessKillPainfully:401 : Failed to terminate process 24026 with SIGKILL: Device or resource busy
May 10 01:39:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:39:54 cmp02 kernel: [ 8602.727495]  connection2:0: detected conn error (1020)
May 10 01:39:57 cmp02 kernel: [ 8605.739674]  connection2:0: detected conn error (1020)
May 10 01:40:00 cmp02 kernel: [ 8608.747253]  connection2:0: detected conn error (1020)
May 10 01:40:03 cmp02 kernel: [ 8611.754907]  connection2:0: detected conn error (1020)
May 10 01:40:06 cmp02 kernel: [ 8614.764375]  connection2:0: detected conn error (1020)
May 10 01:40:07 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:40:07 cmp02 libvirtd[5599]: 2018-05-10 01:40:07.713+0000: 5611: error : virProcessKillPainfully:401 : Failed to terminate process 24026 with SIGKILL: Device or resource busy
May 10 01:40:09 cmp02 kernel: [ 8617.771250]  connection2:0: detected conn error (1020)
May 10 01:40:10 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:12 cmp02 kernel: [ 8620.779821]  connection2:0: detected conn error (1020)
May 10 01:40:13 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:15 cmp02 kernel: [ 8623.788494]  connection2:0: detected conn error (1020)
May 10 01:40:16 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:18 cmp02 kernel: [ 8626.797022]  connection2:0: detected conn error (1020)
May 10 01:40:21 cmp02 kernel: [ 8629.805895]  connection2:0: detected conn error (1020)
May 10 01:40:22 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:40:22 cmp02 libvirtd[5599]: 2018-05-10 01:40:22.743+0000: 5614: error : virProcessKillPainfully:401 : Failed to terminate process 24026 with SIGKILL: Device or resource busy
May 10 01:40:22 cmp02 libvirtd[5599]: 2018-05-10 01:40:22.748+0000: 5610: warning : qemuGetProcessInfo:1460 : cannot parse process status data
May 10 01:40:22 cmp02 libvirtd[5599]: 2018-05-10 01:40:22.748+0000: 5610: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 24039: No such process
May 10 01:40:24 cmp02 kernel: [ 8632.811476]  connection2:0: detected conn error (1020)
May 10 01:40:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:27 cmp02 kernel: [ 8635.834937]  connection2:0: detected conn error (1020)
May 10 01:40:28 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 01:40:28 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 01:40:28 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1520 seconds.
May 10 01:40:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:30 cmp02 kernel: [ 8638.840878]  connection2:0: detected conn error (1020)
May 10 01:40:33 cmp02 kernel: [ 8641.846849]  connection2:0: detected conn error (1020)
May 10 01:40:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:36 cmp02 kernel: [ 8644.855371]  connection2:0: detected conn error (1020)
May 10 01:40:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:39 cmp02 kernel: [ 8647.864373]  connection2:0: detected conn error (1020)
May 10 01:40:42 cmp02 kernel: [ 8650.872536]  connection2:0: detected conn error (1020)
May 10 01:40:45 cmp02 kernel: [ 8653.879792]  connection2:0: detected conn error (1020)
May 10 01:40:48 cmp02 kernel: [ 8656.885915]  connection2:0: detected conn error (1020)
May 10 01:40:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:40:51 cmp02 kernel: [ 8659.892366]  connection2:0: detected conn error (1020)
May 10 01:40:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:54 cmp02 kernel: [ 8662.902616]  connection2:0: detected conn error (1020)
May 10 01:40:55 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:40:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:40:56 cmp02 kernel: [ 8664.339655] audit: type=1400 audit(1525916456.382:277): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-f039a0e5-e16d-42c1-9344-1efeb1bcea15" pid=24419 comm="apparmor_parser"
May 10 01:40:56 cmp02 kernel: [ 8664.578095] audit: type=1400 audit(1525916456.621:278): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f039a0e5-e16d-42c1-9344-1efeb1bcea15" pid=24422 comm="apparmor_parser"
May 10 01:40:56 cmp02 kernel: [ 8664.801196] audit: type=1400 audit(1525916456.844:279): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f039a0e5-e16d-42c1-9344-1efeb1bcea15" pid=24425 comm="apparmor_parser"
May 10 01:40:57 cmp02 kernel: [ 8665.033468] audit: type=1400 audit(1525916457.076:280): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-f039a0e5-e16d-42c1-9344-1efeb1bcea15" pid=24428 comm="apparmor_parser"
May 10 01:40:57 cmp02 systemd-udevd[24431]: Could not generate persistent MAC address for tap26f28a7d-49: No such file or directory
May 10 01:40:57 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap26f28a7d-49 -- add-port br-int tap26f28a7d-49 -- set Interface tap26f28a7d-49 "external-ids:attached-mac=\"fa:16:3e:2b:ff:be\"" -- set Interface tap26f28a7d-49 "external-ids:iface-id=\"26f28a7d-4928-4242-9ff0-f465ba50b072\"" -- set Interface tap26f28a7d-49 "external-ids:vm-id=\"f039a0e5-e16d-42c1-9344-1efeb1bcea15\"" -- set Interface tap26f28a7d-49 external-ids:iface-status=active
May 10 01:40:57 cmp02 kernel: [ 8665.061680] device tap26f28a7d-49 entered promiscuous mode
May 10 01:40:57 cmp02 kernel: [ 8665.303754] audit: type=1400 audit(1525916457.346:281): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-f039a0e5-e16d-42c1-9344-1efeb1bcea15" pid=24505 comm="apparmor_parser"
May 10 01:40:57 cmp02 libvirtd[5599]: 2018-05-10 01:40:57.354+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=43 name='instance-0000005f' uuid=f039a0e5-e16d-42c1-9344-1efeb1bcea15 is tainted: host-cpu
May 10 01:40:57 cmp02 kernel: [ 8665.910956]  connection2:0: detected conn error (1020)
May 10 01:40:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:41:00 cmp02 kernel: [ 8668.917279]  connection2:0: detected conn error (1020)
May 10 01:41:03 cmp02 kernel: [ 8671.922141]  connection2:0: detected conn error (1020)
May 10 01:41:06 cmp02 kernel: [ 8674.928434]  connection2:0: detected conn error (1020)
May 10 01:41:09 cmp02 kernel: [ 8677.936447]  connection2:0: detected conn error (1020)
May 10 01:41:12 cmp02 kernel: [ 8680.947664]  connection2:0: detected conn error (1020)
May 10 01:41:13 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:41:15 cmp02 kernel: [ 8683.952367]  connection2:0: detected conn error (1020)
May 10 01:41:16 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:41:17 cmp02 kernel: [ 8684.962509] device tap9c6c9399-e9 left promiscuous mode
May 10 01:41:17 cmp02 libvirtd[5599]: 2018-05-10 01:41:17.036+0000: 5599: error : qemuMonitorIORead:610 : Unable to read from monitor: Connection reset by peer
May 10 01:41:17 cmp02 kernel: [ 8685.410087] audit: type=1400 audit(1525916477.452:282): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-7c94d1c7-8b21-4ff2-9be1-d5cc89d7c682" pid=24679 comm="apparmor_parser"
May 10 01:41:17 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap9c6c9399-e9
May 10 01:41:19 cmp02 kernel: [ 8686.959696]  connection2:0: detected conn error (1020)
May 10 01:41:19 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:41:21 cmp02 kernel: [ 8689.236105] device tap26f28a7d-49 left promiscuous mode
May 10 01:41:21 cmp02 kernel: [ 8689.622608] audit: type=1400 audit(1525916481.665:283): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-f039a0e5-e16d-42c1-9344-1efeb1bcea15" pid=24701 comm="apparmor_parser"
May 10 01:41:21 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap26f28a7d-49
May 10 01:41:22 cmp02 kernel: [ 8689.965189]  connection2:0: detected conn error (1020)
May 10 01:41:22 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:41:25 cmp02 kernel: [ 8692.975373]  connection2:0: detected conn error (1020)
May 10 01:41:28 cmp02 kernel: [ 8695.984281]  connection2:0: detected conn error (1020)
May 10 01:41:31 cmp02 kernel: [ 8698.994017]  connection2:0: detected conn error (1020)
May 10 01:41:34 cmp02 kernel: [ 8702.001211]  connection2:0: detected conn error (1020)
May 10 01:41:31 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:41:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:41:37 cmp02 kernel: [ 8705.010432]  connection2:0: detected conn error (1020)
May 10 01:41:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:41:40 cmp02 kernel: [ 8708.018796]  connection2:0: detected conn error (1020)
May 10 01:41:43 cmp02 kernel: [ 8711.026916]  connection2:0: detected conn error (1020)
May 10 01:41:46 cmp02 kernel: [ 8714.035285]  connection2:0: detected conn error (1020)
May 10 01:41:49 cmp02 kernel: [ 8717.043819]  connection2:0: detected conn error (1020)
May 10 01:41:52 cmp02 kernel: [ 8720.051306]  connection2:0: detected conn error (1020)
May 10 01:41:55 cmp02 kernel: [ 8723.058410]  connection2:0: detected conn error (1020)
May 10 01:41:58 cmp02 kernel: [ 8726.067726]  connection2:0: detected conn error (1020)
May 10 01:42:01 cmp02 kernel: [ 8729.075888]  connection2:0: detected conn error (1020)
May 10 01:42:04 cmp02 kernel: [ 8732.082113]  connection2:0: detected conn error (1020)
May 10 01:42:07 cmp02 kernel: [ 8735.088895]  connection2:0: detected conn error (1020)
May 10 01:42:10 cmp02 kernel: [ 8738.097014]  connection2:0: detected conn error (1020)
May 10 01:42:13 cmp02 kernel: [ 8741.103310]  connection2:0: detected conn error (1020)
May 10 01:42:16 cmp02 kernel: [ 8744.110368]  connection2:0: detected conn error (1020)
May 10 01:42:16 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:42:19 cmp02 kernel: [ 8747.116242]  connection2:0: detected conn error (1020)
May 10 01:42:19 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:42:22 cmp02 kernel: [ 8750.124221]  connection2:0: detected conn error (1020)
May 10 01:42:25 cmp02 kernel: [ 8753.131925]  connection2:0: detected conn error (1020)
May 10 01:42:28 cmp02 kernel: [ 8756.145113]  connection2:0: detected conn error (1020)
May 10 01:42:31 cmp02 kernel: [ 8759.152341]  connection2:0: detected conn error (1020)
May 10 01:42:34 cmp02 kernel: [ 8762.158420]  connection2:0: detected conn error (1020)
May 10 01:42:37 cmp02 kernel: [ 8765.167234]  connection2:0: detected conn error (1020)
May 10 01:42:40 cmp02 kernel: [ 8768.175091]  connection2:0: detected conn error (1020)
May 10 01:42:43 cmp02 kernel: [ 8771.182089]  connection2:0: detected conn error (1020)
May 10 01:42:46 cmp02 kernel: [ 8774.190085]  connection2:0: detected conn error (1020)
May 10 01:42:49 cmp02 kernel: [ 8777.200473]  connection2:0: detected conn error (1020)
May 10 01:42:52 cmp02 kernel: [ 8780.205921]  connection2:0: detected conn error (1020)
May 10 01:42:55 cmp02 kernel: [ 8783.212915]  connection2:0: detected conn error (1020)
May 10 01:42:58 cmp02 kernel: [ 8786.220205]  connection2:0: detected conn error (1020)
May 10 01:43:01 cmp02 kernel: [ 8789.227120]  connection2:0: detected conn error (1020)
May 10 01:43:04 cmp02 kernel: [ 8792.234943]  connection2:0: detected conn error (1020)
May 10 01:43:07 cmp02 kernel: [ 8795.244793]  connection2:0: detected conn error (1020)
May 10 01:43:10 cmp02 kernel: [ 8798.254678]  connection2:0: detected conn error (1020)
May 10 01:43:13 cmp02 kernel: [ 8801.263288]  connection2:0: detected conn error (1020)
May 10 01:43:16 cmp02 kernel: [ 8804.270614]  connection2:0: detected conn error (1020)
May 10 01:43:16 cmp02 iscsid: message repeated 19 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:43:19 cmp02 kernel: [ 8807.280541]  connection2:0: detected conn error (1020)
May 10 01:43:19 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:43:22 cmp02 kernel: [ 8810.287307]  connection2:0: detected conn error (1020)
May 10 01:43:25 cmp02 kernel: [ 8813.294799]  connection2:0: detected conn error (1020)
May 10 01:43:28 cmp02 kernel: [ 8816.305112]  connection2:0: detected conn error (1020)
May 10 01:43:31 cmp02 kernel: [ 8819.314401]  connection2:0: detected conn error (1020)
May 10 01:43:34 cmp02 kernel: [ 8822.328431]  connection2:0: detected conn error (1020)
May 10 01:43:31 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:43:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:43:37 cmp02 kernel: [ 8825.334262]  connection2:0: detected conn error (1020)
May 10 01:43:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:43:40 cmp02 kernel: [ 8828.342950]  connection2:0: detected conn error (1020)
May 10 01:43:43 cmp02 kernel: [ 8831.348509]  connection2:0: detected conn error (1020)
May 10 01:43:46 cmp02 kernel: [ 8834.356674]  connection2:0: detected conn error (1020)
May 10 01:43:49 cmp02 kernel: [ 8837.362877]  connection2:0: detected conn error (1020)
May 10 01:43:52 cmp02 kernel: [ 8840.370075]  connection2:0: detected conn error (1020)
May 10 01:43:55 cmp02 kernel: [ 8843.382532]  connection2:0: detected conn error (1020)
May 10 01:43:58 cmp02 kernel: [ 8846.391145]  connection2:0: detected conn error (1020)
May 10 01:44:01 cmp02 kernel: [ 8849.397997]  connection2:0: detected conn error (1020)
May 10 01:44:04 cmp02 kernel: [ 8852.405774]  connection2:0: detected conn error (1020)
May 10 01:44:07 cmp02 kernel: [ 8855.412876]  connection2:0: detected conn error (1020)
May 10 01:44:10 cmp02 kernel: [ 8858.419035]  connection2:0: detected conn error (1020)
May 10 01:44:13 cmp02 kernel: [ 8861.425044]  connection2:0: detected conn error (1020)
May 10 01:44:16 cmp02 kernel: [ 8864.432034]  connection2:0: detected conn error (1020)
May 10 01:44:19 cmp02 kernel: [ 8867.437905]  connection2:0: detected conn error (1020)
May 10 01:44:19 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:44:22 cmp02 kernel: [ 8870.444431]  connection2:0: detected conn error (1020)
May 10 01:44:22 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:44:25 cmp02 kernel: [ 8873.451882]  connection2:0: detected conn error (1020)
May 10 01:44:28 cmp02 kernel: [ 8876.457268]  connection2:0: detected conn error (1020)
May 10 01:44:31 cmp02 kernel: [ 8879.466170]  connection2:0: detected conn error (1020)
May 10 01:44:31 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:44:34 cmp02 kernel: [ 8882.471558]  connection2:0: detected conn error (1020)
May 10 01:44:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:44:37 cmp02 kernel: [ 8885.479418]  connection2:0: detected conn error (1020)
May 10 01:44:40 cmp02 kernel: [ 8888.484695]  connection2:0: detected conn error (1020)
May 10 01:44:43 cmp02 kernel: [ 8891.491534]  connection2:0: detected conn error (1020)
May 10 01:44:46 cmp02 kernel: [ 8894.501746]  connection2:0: detected conn error (1020)
May 10 01:44:49 cmp02 kernel: [ 8897.509752]  connection2:0: detected conn error (1020)
May 10 01:44:52 cmp02 kernel: [ 8900.514989]  connection2:0: detected conn error (1020)
May 10 01:44:55 cmp02 kernel: [ 8903.521281]  connection2:0: detected conn error (1020)
May 10 01:44:58 cmp02 kernel: [ 8906.528291]  connection2:0: detected conn error (1020)
May 10 01:45:01 cmp02 kernel: [ 8909.535690]  connection2:0: detected conn error (1020)
May 10 01:45:04 cmp02 kernel: [ 8912.544251]  connection2:0: detected conn error (1020)
May 10 01:45:07 cmp02 kernel: [ 8915.550724]  connection2:0: detected conn error (1020)
May 10 01:45:10 cmp02 kernel: [ 8918.558912]  connection2:0: detected conn error (1020)
May 10 01:45:13 cmp02 kernel: [ 8921.565831]  connection2:0: detected conn error (1020)
May 10 01:45:16 cmp02 kernel: [ 8924.576519]  connection2:0: detected conn error (1020)
May 10 01:45:19 cmp02 kernel: [ 8927.587057]  connection2:0: detected conn error (1020)
May 10 01:45:20 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:45:22 cmp02 kernel: [ 8930.596634]  connection2:0: detected conn error (1020)
May 10 01:45:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:45:25 cmp02 kernel: [ 8933.605849]  connection2:0: detected conn error (1020)
May 10 01:45:28 cmp02 kernel: [ 8936.614640]  connection2:0: detected conn error (1020)
May 10 01:45:31 cmp02 kernel: [ 8939.623232]  connection2:0: detected conn error (1020)
May 10 01:45:32 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:45:34 cmp02 kernel: [ 8942.630040]  connection2:0: detected conn error (1020)
May 10 01:45:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:45:37 cmp02 kernel: [ 8945.638294]  connection2:0: detected conn error (1020)
May 10 01:45:40 cmp02 kernel: [ 8948.647379]  connection2:0: detected conn error (1020)
May 10 01:45:43 cmp02 kernel: [ 8951.656424]  connection2:0: detected conn error (1020)
May 10 01:45:46 cmp02 kernel: [ 8954.664443]  connection2:0: detected conn error (1020)
May 10 01:45:49 cmp02 kernel: [ 8957.671538]  connection2:0: detected conn error (1020)
May 10 01:45:52 cmp02 kernel: [ 8960.679287]  connection2:0: detected conn error (1020)
May 10 01:45:55 cmp02 kernel: [ 8963.685314]  connection2:0: detected conn error (1020)
May 10 01:45:58 cmp02 kernel: [ 8966.693354]  connection2:0: detected conn error (1020)
May 10 01:46:01 cmp02 kernel: [ 8969.700413]  connection2:0: detected conn error (1020)
May 10 01:46:04 cmp02 kernel: [ 8972.705199]  connection2:0: detected conn error (1020)
May 10 01:46:07 cmp02 kernel: [ 8975.713136]  connection2:0: detected conn error (1020)
May 10 01:46:10 cmp02 kernel: [ 8978.720648]  connection2:0: detected conn error (1020)
May 10 01:46:13 cmp02 kernel: [ 8981.731221]  connection2:0: detected conn error (1020)
May 10 01:46:16 cmp02 kernel: [ 8984.739232]  connection2:0: detected conn error (1020)
May 10 01:46:19 cmp02 kernel: [ 8987.745306]  connection2:0: detected conn error (1020)
May 10 01:46:22 cmp02 kernel: [ 8990.751784]  connection2:0: detected conn error (1020)
May 10 01:46:20 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:46:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:46:25 cmp02 kernel: [ 8993.759673]  connection2:0: detected conn error (1020)
May 10 01:46:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:46:28 cmp02 kernel: [ 8996.765017]  connection2:0: detected conn error (1020)
May 10 01:46:31 cmp02 kernel: [ 8999.775350]  connection2:0: detected conn error (1020)
May 10 01:46:32 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:46:34 cmp02 kernel: [ 9002.783104]  connection2:0: detected conn error (1020)
May 10 01:46:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:46:37 cmp02 kernel: [ 9005.792175]  connection2:0: detected conn error (1020)
May 10 01:46:40 cmp02 kernel: [ 9008.798701]  connection2:0: detected conn error (1020)
May 10 01:46:43 cmp02 kernel: [ 9011.804250]  connection2:0: detected conn error (1020)
May 10 01:46:46 cmp02 kernel: [ 9014.814601]  connection2:0: detected conn error (1020)
May 10 01:46:49 cmp02 kernel: [ 9017.823965]  connection2:0: detected conn error (1020)
May 10 01:46:52 cmp02 kernel: [ 9020.839983]  connection2:0: detected conn error (1020)
May 10 01:46:55 cmp02 kernel: [ 9023.852395]  connection2:0: detected conn error (1020)
May 10 01:46:58 cmp02 kernel: [ 9026.863602]  connection2:0: detected conn error (1020)
May 10 01:47:01 cmp02 kernel: [ 9029.880535]  connection2:0: detected conn error (1020)
May 10 01:47:04 cmp02 kernel: [ 9032.898481]  connection2:0: detected conn error (1020)
May 10 01:47:07 cmp02 kernel: [ 9035.934169]  connection2:0: detected conn error (1020)
May 10 01:47:10 cmp02 kernel: [ 9038.940443]  connection2:0: detected conn error (1020)
May 10 01:47:13 cmp02 kernel: [ 9041.945217]  connection2:0: detected conn error (1020)
May 10 01:47:16 cmp02 kernel: [ 9044.951540]  connection2:0: detected conn error (1020)
May 10 01:47:19 cmp02 kernel: [ 9047.957007]  connection2:0: detected conn error (1020)
May 10 01:47:23 cmp02 kernel: [ 9050.963724]  connection2:0: detected conn error (1020)
May 10 01:47:20 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:47:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:47:26 cmp02 kernel: [ 9053.969425]  connection2:0: detected conn error (1020)
May 10 01:47:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:47:29 cmp02 kernel: [ 9056.975307]  connection2:0: detected conn error (1020)
May 10 01:47:32 cmp02 kernel: [ 9059.982744]  connection2:0: detected conn error (1020)
May 10 01:47:32 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:47:35 cmp02 kernel: [ 9062.988371]  connection2:0: detected conn error (1020)
May 10 01:47:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:47:37 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:47:38 cmp02 kernel: [ 9065.993624]  connection2:0: detected conn error (1020)
May 10 01:47:38 cmp02 kernel: [ 9066.748829] audit: type=1400 audit(1525916858.785:284): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-90efa46a-6f65-4bef-b900-e54e6c4f5646" pid=25210 comm="apparmor_parser"
May 10 01:47:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:47:39 cmp02 kernel: [ 9066.976923] audit: type=1400 audit(1525916859.013:285): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-90efa46a-6f65-4bef-b900-e54e6c4f5646" pid=25213 comm="apparmor_parser"
May 10 01:47:39 cmp02 kernel: [ 9067.204719] audit: type=1400 audit(1525916859.241:286): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-90efa46a-6f65-4bef-b900-e54e6c4f5646" pid=25216 comm="apparmor_parser"
May 10 01:47:39 cmp02 kernel: [ 9067.431164] audit: type=1400 audit(1525916859.467:287): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-90efa46a-6f65-4bef-b900-e54e6c4f5646" pid=25219 comm="apparmor_parser"
May 10 01:47:39 cmp02 systemd-udevd[25222]: Could not generate persistent MAC address for tapff5bf901-2e: No such file or directory
May 10 01:47:39 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapff5bf901-2e -- add-port br-int tapff5bf901-2e -- set Interface tapff5bf901-2e "external-ids:attached-mac=\"fa:16:3e:5a:aa:1e\"" -- set Interface tapff5bf901-2e "external-ids:iface-id=\"ff5bf901-2eb6-4fba-aa8a-61003824e81d\"" -- set Interface tapff5bf901-2e "external-ids:vm-id=\"90efa46a-6f65-4bef-b900-e54e6c4f5646\"" -- set Interface tapff5bf901-2e external-ids:iface-status=active
May 10 01:47:39 cmp02 kernel: [ 9067.494167] device tapff5bf901-2e entered promiscuous mode
May 10 01:47:39 cmp02 kernel: [ 9067.719877] audit: type=1400 audit(1525916859.756:288): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-90efa46a-6f65-4bef-b900-e54e6c4f5646" pid=25325 comm="apparmor_parser"
May 10 01:47:39 cmp02 libvirtd[5599]: 2018-05-10 01:47:39.762+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=44 name='instance-00000062' uuid=90efa46a-6f65-4bef-b900-e54e6c4f5646 is tainted: host-cpu
May 10 01:47:41 cmp02 kernel: [ 9068.999709]  connection2:0: detected conn error (1020)
May 10 01:47:41 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:47:44 cmp02 kernel: [ 9072.005307]  connection2:0: detected conn error (1020)
May 10 01:47:47 cmp02 kernel: [ 9075.010296]  connection2:0: detected conn error (1020)
May 10 01:47:50 cmp02 kernel: [ 9078.015372]  connection2:0: detected conn error (1020)
May 10 01:47:53 cmp02 kernel: [ 9081.021596]  connection2:0: detected conn error (1020)
May 10 01:47:56 cmp02 kernel: [ 9084.029921]  connection2:0: detected conn error (1020)
May 10 01:47:59 cmp02 kernel: [ 9087.036640]  connection2:0: detected conn error (1020)
May 10 01:48:02 cmp02 kernel: [ 9090.044875]  connection2:0: detected conn error (1020)
May 10 01:48:05 cmp02 kernel: [ 9093.051673]  connection2:0: detected conn error (1020)
May 10 01:48:08 cmp02 kernel: [ 9096.057742]  connection2:0: detected conn error (1020)
May 10 01:48:11 cmp02 kernel: [ 9099.065255]  connection2:0: detected conn error (1020)
May 10 01:48:14 cmp02 kernel: [ 9102.071749]  connection2:0: detected conn error (1020)
May 10 01:48:17 cmp02 kernel: [ 9105.077720]  connection2:0: detected conn error (1020)
May 10 01:48:20 cmp02 kernel: [ 9108.083605]  connection2:0: detected conn error (1020)
May 10 01:48:23 cmp02 kernel: [ 9111.088369]  connection2:0: detected conn error (1020)
May 10 01:48:23 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:48:26 cmp02 kernel: [ 9114.093682]  connection2:0: detected conn error (1020)
May 10 01:48:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:48:29 cmp02 kernel: [ 9117.097003]  connection2:0: detected conn error (1020)
May 10 01:48:32 cmp02 kernel: [ 9120.101066]  connection2:0: detected conn error (1020)
May 10 01:48:32 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:48:35 cmp02 kernel: [ 9123.106848]  connection2:0: detected conn error (1020)
May 10 01:48:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:48:38 cmp02 kernel: [ 9126.112790]  connection2:0: detected conn error (1020)
May 10 01:48:41 cmp02 kernel: [ 9129.120164]  connection2:0: detected conn error (1020)
May 10 01:48:44 cmp02 kernel: [ 9132.127987]  connection2:0: detected conn error (1020)
May 10 01:48:47 cmp02 kernel: [ 9135.144728]  connection2:0: detected conn error (1020)
May 10 01:48:50 cmp02 kernel: [ 9138.149860]  connection2:0: detected conn error (1020)
May 10 01:48:53 cmp02 kernel: [ 9141.170157]  connection2:0: detected conn error (1020)
May 10 01:48:56 cmp02 kernel: [ 9144.176348]  connection2:0: detected conn error (1020)
May 10 01:48:59 cmp02 kernel: [ 9147.194601]  connection2:0: detected conn error (1020)
May 10 01:49:02 cmp02 kernel: [ 9150.218264]  connection2:0: detected conn error (1020)
May 10 01:49:02 cmp02 kernel: [ 9150.611006] device tapff5bf901-2e left promiscuous mode
May 10 01:48:59 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:49:02 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapff5bf901-2e
May 10 01:49:02 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:49:05 cmp02 kernel: [ 9153.225232]  connection2:0: detected conn error (1020)
May 10 01:49:06 cmp02 kernel: [ 9153.972625] audit: type=1400 audit(1525916946.007:289): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-90efa46a-6f65-4bef-b900-e54e6c4f5646" pid=25525 comm="apparmor_parser"
May 10 01:49:08 cmp02 kernel: [ 9156.246066]  connection2:0: detected conn error (1020)
May 10 01:49:11 cmp02 kernel: [ 9159.260411]  connection2:0: detected conn error (1020)
May 10 01:49:14 cmp02 kernel: [ 9162.268441]  connection2:0: detected conn error (1020)
May 10 01:49:17 cmp02 kernel: [ 9165.277905]  connection2:0: detected conn error (1020)
May 10 01:49:20 cmp02 kernel: [ 9168.286751]  connection2:0: detected conn error (1020)
May 10 01:49:23 cmp02 kernel: [ 9171.293085]  connection2:0: detected conn error (1020)
May 10 01:49:23 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:49:26 cmp02 kernel: [ 9174.300414]  connection2:0: detected conn error (1020)
May 10 01:49:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:49:29 cmp02 kernel: [ 9177.309597]  connection2:0: detected conn error (1020)
May 10 01:49:32 cmp02 kernel: [ 9180.316361]  connection2:0: detected conn error (1020)
May 10 01:49:32 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:49:35 cmp02 kernel: [ 9183.321724]  connection2:0: detected conn error (1020)
May 10 01:49:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:49:38 cmp02 kernel: [ 9186.327176]  connection2:0: detected conn error (1020)
May 10 01:49:41 cmp02 kernel: [ 9189.332844]  connection2:0: detected conn error (1020)
May 10 01:49:44 cmp02 kernel: [ 9192.341757]  connection2:0: detected conn error (1020)
May 10 01:49:47 cmp02 kernel: [ 9195.350535]  connection2:0: detected conn error (1020)
May 10 01:49:50 cmp02 kernel: [ 9198.359106]  connection2:0: detected conn error (1020)
May 10 01:49:53 cmp02 kernel: [ 9201.365440]  connection2:0: detected conn error (1020)
May 10 01:49:56 cmp02 kernel: [ 9204.372729]  connection2:0: detected conn error (1020)
May 10 01:49:59 cmp02 kernel: [ 9207.380216]  connection2:0: detected conn error (1020)
May 10 01:50:02 cmp02 kernel: [ 9210.387495]  connection2:0: detected conn error (1020)
May 10 01:50:05 cmp02 kernel: [ 9213.393255]  connection2:0: detected conn error (1020)
May 10 01:50:08 cmp02 kernel: [ 9216.401342]  connection2:0: detected conn error (1020)
May 10 01:50:11 cmp02 kernel: [ 9219.410221]  connection2:0: detected conn error (1020)
May 10 01:50:14 cmp02 kernel: [ 9222.419442]  connection2:0: detected conn error (1020)
May 10 01:50:17 cmp02 kernel: [ 9225.425904]  connection2:0: detected conn error (1020)
May 10 01:50:20 cmp02 kernel: [ 9228.432344]  connection2:0: detected conn error (1020)
May 10 01:50:23 cmp02 kernel: [ 9231.441902]  connection2:0: detected conn error (1020)
May 10 01:50:23 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:50:26 cmp02 kernel: [ 9234.453101]  connection2:0: detected conn error (1020)
May 10 01:50:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:50:29 cmp02 kernel: [ 9237.460653]  connection2:0: detected conn error (1020)
May 10 01:50:32 cmp02 kernel: [ 9240.469010]  connection2:0: detected conn error (1020)
May 10 01:50:32 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:50:35 cmp02 kernel: [ 9243.476004]  connection2:0: detected conn error (1020)
May 10 01:50:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:50:38 cmp02 kernel: [ 9246.483977]  connection2:0: detected conn error (1020)
May 10 01:50:41 cmp02 kernel: [ 9249.496446]  connection2:0: detected conn error (1020)
May 10 01:50:44 cmp02 kernel: [ 9252.504743]  connection2:0: detected conn error (1020)
May 10 01:50:47 cmp02 kernel: [ 9255.512901]  connection2:0: detected conn error (1020)
May 10 01:50:50 cmp02 kernel: [ 9258.524618]  connection2:0: detected conn error (1020)
May 10 01:50:53 cmp02 kernel: [ 9261.536515]  connection2:0: detected conn error (1020)
May 10 01:50:56 cmp02 kernel: [ 9264.552854]  connection2:0: detected conn error (1020)
May 10 01:50:59 cmp02 kernel: [ 9267.560810]  connection2:0: detected conn error (1020)
May 10 01:51:02 cmp02 kernel: [ 9270.571089]  connection2:0: detected conn error (1020)
May 10 01:51:05 cmp02 kernel: [ 9273.577138]  connection2:0: detected conn error (1020)
May 10 01:51:08 cmp02 kernel: [ 9276.587078]  connection2:0: detected conn error (1020)
May 10 01:51:11 cmp02 kernel: [ 9279.597163]  connection2:0: detected conn error (1020)
May 10 01:51:14 cmp02 kernel: [ 9282.613482]  connection2:0: detected conn error (1020)
May 10 01:51:17 cmp02 kernel: [ 9285.619482]  connection2:0: detected conn error (1020)
May 10 01:51:20 cmp02 kernel: [ 9288.630233]  connection2:0: detected conn error (1020)
May 10 01:51:23 cmp02 kernel: [ 9291.640811]  connection2:0: detected conn error (1020)
May 10 01:51:23 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:51:26 cmp02 kernel: [ 9294.649446]  connection2:0: detected conn error (1020)
May 10 01:51:26 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:51:29 cmp02 kernel: [ 9297.658351]  connection2:0: detected conn error (1020)
May 10 01:51:32 cmp02 kernel: [ 9300.665069]  connection2:0: detected conn error (1020)
May 10 01:51:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:51:35 cmp02 kernel: [ 9303.696879]  connection2:0: detected conn error (1020)
May 10 01:51:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:51:38 cmp02 kernel: [ 9306.716417]  connection2:0: detected conn error (1020)
May 10 01:51:41 cmp02 kernel: [ 9309.725685]  connection2:0: detected conn error (1020)
May 10 01:51:44 cmp02 kernel: [ 9312.735805]  connection2:0: detected conn error (1020)
May 10 01:51:47 cmp02 kernel: [ 9315.746436]  connection2:0: detected conn error (1020)
May 10 01:51:50 cmp02 kernel: [ 9318.757381]  connection2:0: detected conn error (1020)
May 10 01:51:53 cmp02 kernel: [ 9321.766731]  connection2:0: detected conn error (1020)
May 10 01:51:56 cmp02 kernel: [ 9324.773884]  connection2:0: detected conn error (1020)
May 10 01:51:59 cmp02 kernel: [ 9327.780408]  connection2:0: detected conn error (1020)
May 10 01:52:02 cmp02 kernel: [ 9330.789614]  connection2:0: detected conn error (1020)
May 10 01:52:05 cmp02 kernel: [ 9333.795814]  connection2:0: detected conn error (1020)
May 10 01:52:08 cmp02 kernel: [ 9336.804989]  connection2:0: detected conn error (1020)
May 10 01:52:11 cmp02 kernel: [ 9339.814271]  connection2:0: detected conn error (1020)
May 10 01:52:14 cmp02 kernel: [ 9342.823477]  connection2:0: detected conn error (1020)
May 10 01:52:17 cmp02 kernel: [ 9345.831335]  connection2:0: detected conn error (1020)
May 10 01:52:20 cmp02 kernel: [ 9348.841078]  connection2:0: detected conn error (1020)
May 10 01:52:23 cmp02 kernel: [ 9351.847921]  connection2:0: detected conn error (1020)
May 10 01:52:24 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:52:26 cmp02 kernel: [ 9354.855010]  connection2:0: detected conn error (1020)
May 10 01:52:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:52:29 cmp02 kernel: [ 9357.865117]  connection2:0: detected conn error (1020)
May 10 01:52:32 cmp02 kernel: [ 9360.873608]  connection2:0: detected conn error (1020)
May 10 01:52:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:52:35 cmp02 kernel: [ 9363.888979]  connection2:0: detected conn error (1020)
May 10 01:52:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:52:38 cmp02 kernel: [ 9366.904971]  connection2:0: detected conn error (1020)
May 10 01:52:41 cmp02 kernel: [ 9369.911218]  connection2:0: detected conn error (1020)
May 10 01:52:44 cmp02 kernel: [ 9372.918381]  connection2:0: detected conn error (1020)
May 10 01:52:47 cmp02 kernel: [ 9375.928893]  connection2:0: detected conn error (1020)
May 10 01:52:50 cmp02 kernel: [ 9378.937273]  connection2:0: detected conn error (1020)
May 10 01:52:53 cmp02 kernel: [ 9381.948002]  connection2:0: detected conn error (1020)
May 10 01:52:56 cmp02 kernel: [ 9384.959233]  connection2:0: detected conn error (1020)
May 10 01:53:00 cmp02 kernel: [ 9387.970084]  connection2:0: detected conn error (1020)
May 10 01:53:03 cmp02 kernel: [ 9390.979472]  connection2:0: detected conn error (1020)
May 10 01:53:06 cmp02 kernel: [ 9393.988709]  connection2:0: detected conn error (1020)
May 10 01:53:09 cmp02 kernel: [ 9396.996129]  connection2:0: detected conn error (1020)
May 10 01:53:09 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:53:10 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command grains.get with jid 20180510015310115039
May 10 01:53:10 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 25797
May 10 01:53:10 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180510015310115039
May 10 01:53:12 cmp02 kernel: [ 9400.003492]  connection2:0: detected conn error (1020)
May 10 01:53:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:53:15 cmp02 kernel: [ 9403.011052]  connection2:0: detected conn error (1020)
May 10 01:53:18 cmp02 kernel: [ 9406.019295]  connection2:0: detected conn error (1020)
May 10 01:53:21 cmp02 kernel: [ 9409.027051]  connection2:0: detected conn error (1020)
May 10 01:53:24 cmp02 kernel: [ 9412.045831]  connection2:0: detected conn error (1020)
May 10 01:53:24 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:53:27 cmp02 kernel: [ 9415.052001]  connection2:0: detected conn error (1020)
May 10 01:53:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:53:30 cmp02 kernel: [ 9418.061696]  connection2:0: detected conn error (1020)
May 10 01:53:33 cmp02 kernel: [ 9421.069699]  connection2:0: detected conn error (1020)
May 10 01:53:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:53:34 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command grains.get with jid 20180510015334667553
May 10 01:53:34 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 25863
May 10 01:53:34 cmp02 salt-minion[2824]: [INFO    ] Returning information for job: 20180510015334667553
May 10 01:53:36 cmp02 kernel: [ 9424.076038]  connection2:0: detected conn error (1020)
May 10 01:53:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:53:39 cmp02 kernel: [ 9427.086306]  connection2:0: detected conn error (1020)
May 10 01:53:42 cmp02 kernel: [ 9430.094256]  connection2:0: detected conn error (1020)
May 10 01:53:45 cmp02 kernel: [ 9433.102033]  connection2:0: detected conn error (1020)
May 10 01:53:48 cmp02 kernel: [ 9436.113261]  connection2:0: detected conn error (1020)
May 10 01:53:51 cmp02 kernel: [ 9439.122424]  connection2:0: detected conn error (1020)
May 10 01:53:54 cmp02 kernel: [ 9442.134398]  connection2:0: detected conn error (1020)
May 10 01:53:57 cmp02 kernel: [ 9445.140516]  connection2:0: detected conn error (1020)
May 10 01:54:00 cmp02 kernel: [ 9448.147893]  connection2:0: detected conn error (1020)
May 10 01:54:03 cmp02 kernel: [ 9451.156002]  connection2:0: detected conn error (1020)
May 10 01:54:06 cmp02 kernel: [ 9454.167444]  connection2:0: detected conn error (1020)
May 10 01:54:09 cmp02 kernel: [ 9457.173258]  connection2:0: detected conn error (1020)
May 10 01:54:12 cmp02 kernel: [ 9460.181083]  connection2:0: detected conn error (1020)
May 10 01:54:15 cmp02 kernel: [ 9463.196993]  connection2:0: detected conn error (1020)
May 10 01:54:18 cmp02 kernel: [ 9466.217938]  connection2:0: detected conn error (1020)
May 10 01:54:21 cmp02 kernel: [ 9469.230372]  connection2:0: detected conn error (1020)
May 10 01:54:24 cmp02 kernel: [ 9472.250405]  connection2:0: detected conn error (1020)
May 10 01:54:25 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:54:27 cmp02 kernel: [ 9475.261174]  connection2:0: detected conn error (1020)
May 10 01:54:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:54:30 cmp02 kernel: [ 9478.295439]  connection2:0: detected conn error (1020)
May 10 01:54:33 cmp02 kernel: [ 9481.318894]  connection2:0: detected conn error (1020)
May 10 01:54:34 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:54:36 cmp02 kernel: [ 9484.326339]  connection2:0: detected conn error (1020)
May 10 01:54:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:54:39 cmp02 kernel: [ 9487.349672]  connection2:0: detected conn error (1020)
May 10 01:54:42 cmp02 kernel: [ 9490.356382]  connection2:0: detected conn error (1020)
May 10 01:54:45 cmp02 kernel: [ 9493.367798]  connection2:0: detected conn error (1020)
May 10 01:54:48 cmp02 kernel: [ 9496.379384]  connection2:0: detected conn error (1020)
May 10 01:54:51 cmp02 kernel: [ 9499.384927]  connection2:0: detected conn error (1020)
May 10 01:54:54 cmp02 kernel: [ 9502.392769]  connection2:0: detected conn error (1020)
May 10 01:54:57 cmp02 kernel: [ 9505.397940]  connection2:0: detected conn error (1020)
May 10 01:55:00 cmp02 kernel: [ 9508.411550]  connection2:0: detected conn error (1020)
May 10 01:55:03 cmp02 kernel: [ 9511.421764]  connection2:0: detected conn error (1020)
May 10 01:55:06 cmp02 kernel: [ 9514.431466]  connection2:0: detected conn error (1020)
May 10 01:55:09 cmp02 kernel: [ 9517.441350]  connection2:0: detected conn error (1020)
May 10 01:55:12 cmp02 kernel: [ 9520.453003]  connection2:0: detected conn error (1020)
May 10 01:55:15 cmp02 kernel: [ 9523.462019]  connection2:0: detected conn error (1020)
May 10 01:55:18 cmp02 kernel: [ 9526.470391]  connection2:0: detected conn error (1020)
May 10 01:55:21 cmp02 kernel: [ 9529.481481]  connection2:0: detected conn error (1020)
May 10 01:55:24 cmp02 kernel: [ 9532.490049]  connection2:0: detected conn error (1020)
May 10 01:55:27 cmp02 kernel: [ 9535.499416]  connection2:0: detected conn error (1020)
May 10 01:55:28 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:55:30 cmp02 kernel: [ 9538.505244]  connection2:0: detected conn error (1020)
May 10 01:55:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:55:33 cmp02 kernel: [ 9541.517161]  connection2:0: detected conn error (1020)
May 10 01:55:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:55:36 cmp02 kernel: [ 9544.530103]  connection2:0: detected conn error (1020)
May 10 01:55:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:55:39 cmp02 kernel: [ 9547.541045]  connection2:0: detected conn error (1020)
May 10 01:55:42 cmp02 kernel: [ 9550.552996]  connection2:0: detected conn error (1020)
May 10 01:55:45 cmp02 kernel: [ 9553.564454]  connection2:0: detected conn error (1020)
May 10 01:55:48 cmp02 kernel: [ 9556.579324]  connection2:0: detected conn error (1020)
May 10 01:55:51 cmp02 kernel: [ 9559.593436]  connection2:0: detected conn error (1020)
May 10 01:55:54 cmp02 kernel: [ 9562.613952]  connection2:0: detected conn error (1020)
May 10 01:55:57 cmp02 kernel: [ 9565.626315]  connection2:0: detected conn error (1020)
May 10 01:56:00 cmp02 kernel: [ 9568.636074]  connection2:0: detected conn error (1020)
May 10 01:56:03 cmp02 kernel: [ 9571.646776]  connection2:0: detected conn error (1020)
May 10 01:56:06 cmp02 kernel: [ 9574.656464]  connection2:0: detected conn error (1020)
May 10 01:56:09 cmp02 kernel: [ 9577.668249]  connection2:0: detected conn error (1020)
May 10 01:56:12 cmp02 kernel: [ 9580.677504]  connection2:0: detected conn error (1020)
May 10 01:56:15 cmp02 kernel: [ 9583.684541]  connection2:0: detected conn error (1020)
May 10 01:56:18 cmp02 kernel: [ 9586.695457]  connection2:0: detected conn error (1020)
May 10 01:56:21 cmp02 kernel: [ 9589.703461]  connection2:0: detected conn error (1020)
May 10 01:56:24 cmp02 kernel: [ 9592.710785]  connection2:0: detected conn error (1020)
May 10 01:56:27 cmp02 kernel: [ 9595.721178]  connection2:0: detected conn error (1020)
May 10 01:56:28 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:56:30 cmp02 kernel: [ 9598.730964]  connection2:0: detected conn error (1020)
May 10 01:56:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:56:33 cmp02 kernel: [ 9601.737177]  connection2:0: detected conn error (1020)
May 10 01:56:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:56:36 cmp02 kernel: [ 9604.748903]  connection2:0: detected conn error (1020)
May 10 01:56:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:56:39 cmp02 kernel: [ 9607.756589]  connection2:0: detected conn error (1020)
May 10 01:56:42 cmp02 kernel: [ 9610.763519]  connection2:0: detected conn error (1020)
May 10 01:56:45 cmp02 kernel: [ 9613.770421]  connection2:0: detected conn error (1020)
May 10 01:56:48 cmp02 kernel: [ 9616.777428]  connection2:0: detected conn error (1020)
May 10 01:56:51 cmp02 kernel: [ 9619.783703]  connection2:0: detected conn error (1020)
May 10 01:56:54 cmp02 kernel: [ 9622.791623]  connection2:0: detected conn error (1020)
May 10 01:56:57 cmp02 kernel: [ 9625.797354]  connection2:0: detected conn error (1020)
May 10 01:57:00 cmp02 kernel: [ 9628.804685]  connection2:0: detected conn error (1020)
May 10 01:57:03 cmp02 kernel: [ 9631.811588]  connection2:0: detected conn error (1020)
May 10 01:57:06 cmp02 kernel: [ 9634.819151]  connection2:0: detected conn error (1020)
May 10 01:57:09 cmp02 kernel: [ 9637.827234]  connection2:0: detected conn error (1020)
May 10 01:57:12 cmp02 kernel: [ 9640.838043]  connection2:0: detected conn error (1020)
May 10 01:57:15 cmp02 kernel: [ 9643.845751]  connection2:0: detected conn error (1020)
May 10 01:57:18 cmp02 kernel: [ 9646.853955]  connection2:0: detected conn error (1020)
May 10 01:57:21 cmp02 kernel: [ 9649.863429]  connection2:0: detected conn error (1020)
May 10 01:57:24 cmp02 kernel: [ 9652.870827]  connection2:0: detected conn error (1020)
May 10 01:57:27 cmp02 kernel: [ 9655.878944]  connection2:0: detected conn error (1020)
May 10 01:57:30 cmp02 kernel: [ 9658.904823]  connection2:0: detected conn error (1020)
May 10 01:57:32 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:57:33 cmp02 kernel: [ 9661.912268]  connection2:0: detected conn error (1020)
May 10 01:57:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:57:36 cmp02 kernel: [ 9664.936756]  connection2:0: detected conn error (1020)
May 10 01:57:39 cmp02 kernel: [ 9667.945005]  connection2:0: detected conn error (1020)
May 10 01:57:42 cmp02 kernel: [ 9670.951968]  connection2:0: detected conn error (1020)
May 10 01:57:45 cmp02 kernel: [ 9673.959662]  connection2:0: detected conn error (1020)
May 10 01:57:48 cmp02 kernel: [ 9676.967303]  connection2:0: detected conn error (1020)
May 10 01:57:52 cmp02 kernel: [ 9679.977313]  connection2:0: detected conn error (1020)
May 10 01:57:55 cmp02 kernel: [ 9682.985034]  connection2:0: detected conn error (1020)
May 10 01:57:58 cmp02 kernel: [ 9685.994580]  connection2:0: detected conn error (1020)
May 10 01:58:01 cmp02 kernel: [ 9689.003986]  connection2:0: detected conn error (1020)
May 10 01:58:04 cmp02 kernel: [ 9692.012404]  connection2:0: detected conn error (1020)
May 10 01:58:07 cmp02 kernel: [ 9695.019209]  connection2:0: detected conn error (1020)
May 10 01:58:10 cmp02 kernel: [ 9698.029266]  connection2:0: detected conn error (1020)
May 10 01:58:13 cmp02 kernel: [ 9701.038714]  connection2:0: detected conn error (1020)
May 10 01:58:16 cmp02 kernel: [ 9704.046570]  connection2:0: detected conn error (1020)
May 10 01:58:19 cmp02 kernel: [ 9707.055421]  connection2:0: detected conn error (1020)
May 10 01:58:22 cmp02 kernel: [ 9710.062990]  connection2:0: detected conn error (1020)
May 10 01:58:25 cmp02 kernel: [ 9713.069549]  connection2:0: detected conn error (1020)
May 10 01:58:28 cmp02 kernel: [ 9716.078402]  connection2:0: detected conn error (1020)
May 10 01:58:31 cmp02 kernel: [ 9719.084294]  connection2:0: detected conn error (1020)
May 10 01:58:29 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:58:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:58:34 cmp02 kernel: [ 9722.090181]  connection2:0: detected conn error (1020)
May 10 01:58:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:58:37 cmp02 kernel: [ 9725.097825]  connection2:0: detected conn error (1020)
May 10 01:58:40 cmp02 kernel: [ 9728.105083]  connection2:0: detected conn error (1020)
May 10 01:58:43 cmp02 kernel: [ 9731.110880]  connection2:0: detected conn error (1020)
May 10 01:58:46 cmp02 kernel: [ 9734.117744]  connection2:0: detected conn error (1020)
May 10 01:58:49 cmp02 kernel: [ 9737.125160]  connection2:0: detected conn error (1020)
May 10 01:58:52 cmp02 kernel: [ 9740.131328]  connection2:0: detected conn error (1020)
May 10 01:58:55 cmp02 kernel: [ 9743.139315]  connection2:0: detected conn error (1020)
May 10 01:58:58 cmp02 kernel: [ 9746.146613]  connection2:0: detected conn error (1020)
May 10 01:59:01 cmp02 kernel: [ 9749.152699]  connection2:0: detected conn error (1020)
May 10 01:59:04 cmp02 kernel: [ 9752.161462]  connection2:0: detected conn error (1020)
May 10 01:59:07 cmp02 kernel: [ 9755.168581]  connection2:0: detected conn error (1020)
May 10 01:59:10 cmp02 kernel: [ 9758.173909]  connection2:0: detected conn error (1020)
May 10 01:59:13 cmp02 kernel: [ 9761.182919]  connection2:0: detected conn error (1020)
May 10 01:59:16 cmp02 kernel: [ 9764.193707]  connection2:0: detected conn error (1020)
May 10 01:59:19 cmp02 kernel: [ 9767.201696]  connection2:0: detected conn error (1020)
May 10 01:59:22 cmp02 kernel: [ 9770.212271]  connection2:0: detected conn error (1020)
May 10 01:59:25 cmp02 kernel: [ 9773.223694]  connection2:0: detected conn error (1020)
May 10 01:59:28 cmp02 kernel: [ 9776.233398]  connection2:0: detected conn error (1020)
May 10 01:59:31 cmp02 kernel: [ 9779.243747]  connection2:0: detected conn error (1020)
May 10 01:59:29 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:59:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:59:34 cmp02 kernel: [ 9782.250643]  connection2:0: detected conn error (1020)
May 10 01:59:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:59:37 cmp02 kernel: [ 9785.258511]  connection2:0: detected conn error (1020)
May 10 01:59:40 cmp02 kernel: [ 9788.265591]  connection2:0: detected conn error (1020)
May 10 01:59:43 cmp02 kernel: [ 9791.273710]  connection2:0: detected conn error (1020)
May 10 01:59:46 cmp02 kernel: [ 9794.281366]  connection2:0: detected conn error (1020)
May 10 01:59:47 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 01:59:49 cmp02 kernel: [ 9797.287525]  connection2:0: detected conn error (1020)
May 10 01:59:50 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:59:50 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 01:59:52 cmp02 kernel: [ 9800.085763] audit: type=1400 audit(1525917592.108:290): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-255557d5-cf0b-447f-9b15-1f7ff9217b32" pid=26315 comm="apparmor_parser"
May 10 01:59:52 cmp02 kernel: [ 9800.293885]  connection2:0: detected conn error (1020)
May 10 01:59:52 cmp02 kernel: [ 9800.334169] audit: type=1400 audit(1525917592.356:291): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-255557d5-cf0b-447f-9b15-1f7ff9217b32" pid=26318 comm="apparmor_parser"
May 10 01:59:52 cmp02 kernel: [ 9800.590182] audit: type=1400 audit(1525917592.612:292): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-255557d5-cf0b-447f-9b15-1f7ff9217b32" pid=26321 comm="apparmor_parser"
May 10 01:59:52 cmp02 kernel: [ 9800.840705] audit: type=1400 audit(1525917592.863:293): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-255557d5-cf0b-447f-9b15-1f7ff9217b32" pid=26324 comm="apparmor_parser"
May 10 01:59:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3805d51e-27 -- add-port br-int tap3805d51e-27 -- set Interface tap3805d51e-27 "external-ids:attached-mac=\"fa:16:3e:cc:85:0f\"" -- set Interface tap3805d51e-27 "external-ids:iface-id=\"3805d51e-27ca-412c-9ecb-f9a596db21c0\"" -- set Interface tap3805d51e-27 "external-ids:vm-id=\"255557d5-cf0b-447f-9b15-1f7ff9217b32\"" -- set Interface tap3805d51e-27 external-ids:iface-status=active
May 10 01:59:52 cmp02 kernel: [ 9800.878295] device tap3805d51e-27 entered promiscuous mode
May 10 01:59:53 cmp02 kernel: [ 9801.128743] audit: type=1400 audit(1525917593.151:294): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-255557d5-cf0b-447f-9b15-1f7ff9217b32" pid=26386 comm="apparmor_parser"
May 10 01:59:53 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:59:53 cmp02 libvirtd[5599]: 2018-05-10 01:59:53.159+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=45 name='instance-00000065' uuid=255557d5-cf0b-447f-9b15-1f7ff9217b32 is tainted: host-cpu
May 10 01:59:55 cmp02 kernel: [ 9803.300469]  connection2:0: detected conn error (1020)
May 10 01:59:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 01:59:58 cmp02 kernel: [ 9806.307113]  connection2:0: detected conn error (1020)
May 10 02:00:01 cmp02 kernel: [ 9809.313708]  connection2:0: detected conn error (1020)
May 10 02:00:04 cmp02 kernel: [ 9812.319781]  connection2:0: detected conn error (1020)
May 10 02:00:07 cmp02 kernel: [ 9815.328585]  connection2:0: detected conn error (1020)
May 10 02:00:10 cmp02 kernel: [ 9818.335114]  connection2:0: detected conn error (1020)
May 10 02:00:13 cmp02 kernel: [ 9821.341982]  connection2:0: detected conn error (1020)
May 10 02:00:16 cmp02 kernel: [ 9824.349654]  connection2:0: detected conn error (1020)
May 10 02:00:19 cmp02 kernel: [ 9827.358058]  connection2:0: detected conn error (1020)
May 10 02:00:22 cmp02 kernel: [ 9830.368406]  connection2:0: detected conn error (1020)
May 10 02:00:25 cmp02 kernel: [ 9833.378165]  connection2:0: detected conn error (1020)
May 10 02:00:28 cmp02 kernel: [ 9836.384825]  connection2:0: detected conn error (1020)
May 10 02:00:31 cmp02 kernel: [ 9839.391528]  connection2:0: detected conn error (1020)
May 10 02:00:29 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:00:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:00:34 cmp02 kernel: [ 9842.396762]  connection2:0: detected conn error (1020)
May 10 02:00:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:00:37 cmp02 kernel: [ 9845.403775]  connection2:0: detected conn error (1020)
May 10 02:00:40 cmp02 kernel: [ 9848.415427]  connection2:0: detected conn error (1020)
May 10 02:00:43 cmp02 kernel: [ 9851.428800]  connection2:0: detected conn error (1020)
May 10 02:00:46 cmp02 kernel: [ 9854.435107]  connection2:0: detected conn error (1020)
May 10 02:00:49 cmp02 kernel: [ 9857.443151]  connection2:0: detected conn error (1020)
May 10 02:00:52 cmp02 kernel: [ 9860.450263]  connection2:0: detected conn error (1020)
May 10 02:00:55 cmp02 kernel: [ 9863.458840]  connection2:0: detected conn error (1020)
May 10 02:00:58 cmp02 kernel: [ 9866.468356]  connection2:0: detected conn error (1020)
May 10 02:01:01 cmp02 kernel: [ 9869.474716]  connection2:0: detected conn error (1020)
May 10 02:01:04 cmp02 kernel: [ 9872.483540]  connection2:0: detected conn error (1020)
May 10 02:01:07 cmp02 kernel: [ 9875.492044]  connection2:0: detected conn error (1020)
May 10 02:01:10 cmp02 kernel: [ 9878.499884]  connection2:0: detected conn error (1020)
May 10 02:01:13 cmp02 kernel: [ 9881.507115]  connection2:0: detected conn error (1020)
May 10 02:01:16 cmp02 kernel: [ 9884.516420]  connection2:0: detected conn error (1020)
May 10 02:01:19 cmp02 kernel: [ 9887.522584]  connection2:0: detected conn error (1020)
May 10 02:01:22 cmp02 kernel: [ 9890.529288]  connection2:0: detected conn error (1020)
May 10 02:01:25 cmp02 kernel: [ 9893.537804]  connection2:0: detected conn error (1020)
May 10 02:01:28 cmp02 kernel: [ 9896.544610]  connection2:0: detected conn error (1020)
May 10 02:01:31 cmp02 kernel: [ 9899.550349]  connection2:0: detected conn error (1020)
May 10 02:01:32 cmp02 iscsid: message repeated 19 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:01:34 cmp02 kernel: [ 9902.559323]  connection2:0: detected conn error (1020)
May 10 02:01:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:01:37 cmp02 kernel: [ 9905.569627]  connection2:0: detected conn error (1020)
May 10 02:01:40 cmp02 kernel: [ 9908.580593]  connection2:0: detected conn error (1020)
May 10 02:01:43 cmp02 kernel: [ 9911.589676]  connection2:0: detected conn error (1020)
May 10 02:01:46 cmp02 kernel: [ 9914.599307]  connection2:0: detected conn error (1020)
May 10 02:01:49 cmp02 kernel: [ 9917.603866]  connection2:0: detected conn error (1020)
May 10 02:01:52 cmp02 kernel: [ 9920.610774]  connection2:0: detected conn error (1020)
May 10 02:01:55 cmp02 kernel: [ 9923.617443]  connection2:0: detected conn error (1020)
May 10 02:01:58 cmp02 kernel: [ 9926.624783]  connection2:0: detected conn error (1020)
May 10 02:02:01 cmp02 kernel: [ 9929.632413]  connection2:0: detected conn error (1020)
May 10 02:02:04 cmp02 kernel: [ 9932.641781]  connection2:0: detected conn error (1020)
May 10 02:02:07 cmp02 kernel: [ 9935.649189]  connection2:0: detected conn error (1020)
May 10 02:02:10 cmp02 kernel: [ 9938.658799]  connection2:0: detected conn error (1020)
May 10 02:02:13 cmp02 kernel: [ 9941.667976]  connection2:0: detected conn error (1020)
May 10 02:02:16 cmp02 kernel: [ 9944.677016]  connection2:0: detected conn error (1020)
May 10 02:02:19 cmp02 kernel: [ 9947.682950]  connection2:0: detected conn error (1020)
May 10 02:02:22 cmp02 kernel: [ 9950.693359]  connection2:0: detected conn error (1020)
May 10 02:02:25 cmp02 kernel: [ 9953.701803]  connection2:0: detected conn error (1020)
May 10 02:02:28 cmp02 kernel: [ 9956.709920]  connection2:0: detected conn error (1020)
May 10 02:02:31 cmp02 kernel: [ 9959.720081]  connection2:0: detected conn error (1020)
May 10 02:02:32 cmp02 iscsid: message repeated 19 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:02:34 cmp02 kernel: [ 9962.726910]  connection2:0: detected conn error (1020)
May 10 02:02:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:02:37 cmp02 kernel: [ 9965.733660]  connection2:0: detected conn error (1020)
May 10 02:02:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:02:40 cmp02 kernel: [ 9968.740880]  connection2:0: detected conn error (1020)
May 10 02:02:43 cmp02 kernel: [ 9971.747926]  connection2:0: detected conn error (1020)
May 10 02:02:46 cmp02 kernel: [ 9974.756121]  connection2:0: detected conn error (1020)
May 10 02:02:49 cmp02 kernel: [ 9977.762752]  connection2:0: detected conn error (1020)
May 10 02:02:52 cmp02 kernel: [ 9980.772017]  connection2:0: detected conn error (1020)
May 10 02:02:55 cmp02 kernel: [ 9983.783004]  connection2:0: detected conn error (1020)
May 10 02:02:58 cmp02 kernel: [ 9986.788756]  connection2:0: detected conn error (1020)
May 10 02:03:01 cmp02 kernel: [ 9989.799599]  connection2:0: detected conn error (1020)
May 10 02:03:04 cmp02 kernel: [ 9992.807248]  connection2:0: detected conn error (1020)
May 10 02:03:07 cmp02 kernel: [ 9995.812841]  connection2:0: detected conn error (1020)
May 10 02:03:10 cmp02 kernel: [ 9998.822822]  connection2:0: detected conn error (1020)
May 10 02:03:13 cmp02 kernel: [10001.834706]  connection2:0: detected conn error (1020)
May 10 02:03:16 cmp02 kernel: [10004.844712]  connection2:0: detected conn error (1020)
May 10 02:03:19 cmp02 kernel: [10007.851645]  connection2:0: detected conn error (1020)
May 10 02:03:22 cmp02 kernel: [10010.857278]  connection2:0: detected conn error (1020)
May 10 02:03:25 cmp02 kernel: [10013.862988]  connection2:0: detected conn error (1020)
May 10 02:03:28 cmp02 kernel: [10016.872018]  connection2:0: detected conn error (1020)
May 10 02:03:31 cmp02 kernel: [10019.879309]  connection2:0: detected conn error (1020)
May 10 02:03:32 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:03:34 cmp02 kernel: [10022.887244]  connection2:0: detected conn error (1020)
May 10 02:03:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:03:37 cmp02 kernel: [10025.894846]  connection2:0: detected conn error (1020)
May 10 02:03:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:03:40 cmp02 kernel: [10028.904763]  connection2:0: detected conn error (1020)
May 10 02:03:41 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:03:43 cmp02 kernel: [10031.912973]  connection2:0: detected conn error (1020)
May 10 02:03:46 cmp02 kernel: [10034.919315]  connection2:0: detected conn error (1020)
May 10 02:03:49 cmp02 kernel: [10037.926052]  connection2:0: detected conn error (1020)
May 10 02:03:52 cmp02 kernel: [10040.933961]  connection2:0: detected conn error (1020)
May 10 02:03:55 cmp02 kernel: [10043.943104]  connection2:0: detected conn error (1020)
May 10 02:03:58 cmp02 kernel: [10046.953119]  connection2:0: detected conn error (1020)
May 10 02:04:01 cmp02 kernel: [10049.958841]  connection2:0: detected conn error (1020)
May 10 02:04:04 cmp02 kernel: [10052.966865]  connection2:0: detected conn error (1020)
May 10 02:04:07 cmp02 kernel: [10055.974775]  connection2:0: detected conn error (1020)
May 10 02:04:11 cmp02 kernel: [10058.982584]  connection2:0: detected conn error (1020)
May 10 02:04:14 cmp02 kernel: [10061.992367]  connection2:0: detected conn error (1020)
May 10 02:04:17 cmp02 kernel: [10064.999237]  connection2:0: detected conn error (1020)
May 10 02:04:20 cmp02 kernel: [10068.007737]  connection2:0: detected conn error (1020)
May 10 02:04:23 cmp02 kernel: [10071.014645]  connection2:0: detected conn error (1020)
May 10 02:04:26 cmp02 kernel: [10074.023749]  connection2:0: detected conn error (1020)
May 10 02:04:29 cmp02 kernel: [10077.029615]  connection2:0: detected conn error (1020)
May 10 02:04:32 cmp02 kernel: [10080.038688]  connection2:0: detected conn error (1020)
May 10 02:04:33 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:04:35 cmp02 kernel: [10083.046696]  connection2:0: detected conn error (1020)
May 10 02:04:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:04:38 cmp02 kernel: [10086.053032]  connection2:0: detected conn error (1020)
May 10 02:04:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:04:41 cmp02 kernel: [10089.059885]  connection2:0: detected conn error (1020)
May 10 02:04:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:04:44 cmp02 kernel: [10092.067094]  connection2:0: detected conn error (1020)
May 10 02:04:47 cmp02 kernel: [10095.074152]  connection2:0: detected conn error (1020)
May 10 02:04:50 cmp02 kernel: [10098.080753]  connection2:0: detected conn error (1020)
May 10 02:04:53 cmp02 kernel: [10101.090113]  connection2:0: detected conn error (1020)
May 10 02:04:56 cmp02 kernel: [10104.099701]  connection2:0: detected conn error (1020)
May 10 02:04:59 cmp02 kernel: [10107.105504]  connection2:0: detected conn error (1020)
May 10 02:05:02 cmp02 kernel: [10110.114107]  connection2:0: detected conn error (1020)
May 10 02:05:05 cmp02 kernel: [10113.120771]  connection2:0: detected conn error (1020)
May 10 02:05:08 cmp02 kernel: [10116.129488]  connection2:0: detected conn error (1020)
May 10 02:05:11 cmp02 kernel: [10119.137752]  connection2:0: detected conn error (1020)
May 10 02:05:14 cmp02 kernel: [10122.145251]  connection2:0: detected conn error (1020)
May 10 02:05:17 cmp02 kernel: [10125.154947]  connection2:0: detected conn error (1020)
May 10 02:05:20 cmp02 kernel: [10128.162123]  connection2:0: detected conn error (1020)
May 10 02:05:23 cmp02 kernel: [10131.168341]  connection2:0: detected conn error (1020)
May 10 02:05:26 cmp02 kernel: [10134.176761]  connection2:0: detected conn error (1020)
May 10 02:05:29 cmp02 kernel: [10137.186680]  connection2:0: detected conn error (1020)
May 10 02:05:32 cmp02 kernel: [10140.193742]  connection2:0: detected conn error (1020)
May 10 02:05:33 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:05:35 cmp02 kernel: [10143.199639]  connection2:0: detected conn error (1020)
May 10 02:05:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:05:38 cmp02 kernel: [10146.209974]  connection2:0: detected conn error (1020)
May 10 02:05:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:05:41 cmp02 kernel: [10149.217424]  connection2:0: detected conn error (1020)
May 10 02:05:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:05:44 cmp02 kernel: [10152.225165]  connection2:0: detected conn error (1020)
May 10 02:05:47 cmp02 kernel: [10155.233449]  connection2:0: detected conn error (1020)
May 10 02:05:48 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:05:48 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 02:05:48 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 02:05:48 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1440 seconds.
May 10 02:05:50 cmp02 kernel: [10158.243066]  connection2:0: detected conn error (1020)
May 10 02:05:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:05:53 cmp02 kernel: [10161.249396]  connection2:0: detected conn error (1020)
May 10 02:05:56 cmp02 kernel: [10164.256300]  connection2:0: detected conn error (1020)
May 10 02:05:59 cmp02 kernel: [10167.262166]  connection2:0: detected conn error (1020)
May 10 02:06:02 cmp02 kernel: [10170.274290]  connection2:0: detected conn error (1020)
May 10 02:06:05 cmp02 kernel: [10173.280088]  connection2:0: detected conn error (1020)
May 10 02:06:08 cmp02 kernel: [10176.287165]  connection2:0: detected conn error (1020)
May 10 02:06:11 cmp02 kernel: [10179.297328]  connection2:0: detected conn error (1020)
May 10 02:06:14 cmp02 kernel: [10182.306255]  connection2:0: detected conn error (1020)
May 10 02:06:17 cmp02 kernel: [10185.315513]  connection2:0: detected conn error (1020)
May 10 02:06:20 cmp02 kernel: [10188.327154]  connection2:0: detected conn error (1020)
May 10 02:06:23 cmp02 kernel: [10191.336743]  connection2:0: detected conn error (1020)
May 10 02:06:26 cmp02 kernel: [10194.343444]  connection2:0: detected conn error (1020)
May 10 02:06:29 cmp02 kernel: [10197.351200]  connection2:0: detected conn error (1020)
May 10 02:06:32 cmp02 kernel: [10200.358246]  connection2:0: detected conn error (1020)
May 10 02:06:33 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:06:35 cmp02 kernel: [10203.365206]  connection2:0: detected conn error (1020)
May 10 02:06:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:06:38 cmp02 kernel: [10206.375761]  connection2:0: detected conn error (1020)
May 10 02:06:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:06:41 cmp02 kernel: [10209.385062]  connection2:0: detected conn error (1020)
May 10 02:06:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:06:44 cmp02 kernel: [10212.393958]  connection2:0: detected conn error (1020)
May 10 02:06:47 cmp02 kernel: [10215.400357]  connection2:0: detected conn error (1020)
May 10 02:06:50 cmp02 kernel: [10218.410059]  connection2:0: detected conn error (1020)
May 10 02:06:53 cmp02 kernel: [10221.420935]  connection2:0: detected conn error (1020)
May 10 02:06:56 cmp02 kernel: [10224.430093]  connection2:0: detected conn error (1020)
May 10 02:06:59 cmp02 kernel: [10227.439342]  connection2:0: detected conn error (1020)
May 10 02:07:02 cmp02 kernel: [10230.486245]  connection2:0: detected conn error (1020)
May 10 02:07:05 cmp02 kernel: [10233.495530]  connection2:0: detected conn error (1020)
May 10 02:07:08 cmp02 kernel: [10236.501500]  connection2:0: detected conn error (1020)
May 10 02:07:11 cmp02 kernel: [10239.509309]  connection2:0: detected conn error (1020)
May 10 02:07:14 cmp02 kernel: [10242.514830]  connection2:0: detected conn error (1020)
May 10 02:07:17 cmp02 kernel: [10245.522657]  connection2:0: detected conn error (1020)
May 10 02:07:20 cmp02 kernel: [10248.531303]  connection2:0: detected conn error (1020)
May 10 02:07:23 cmp02 kernel: [10251.540568]  connection2:0: detected conn error (1020)
May 10 02:07:26 cmp02 kernel: [10254.548634]  connection2:0: detected conn error (1020)
May 10 02:07:29 cmp02 kernel: [10257.557384]  connection2:0: detected conn error (1020)
May 10 02:07:32 cmp02 kernel: [10260.567167]  connection2:0: detected conn error (1020)
May 10 02:07:33 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:07:35 cmp02 kernel: [10263.574644]  connection2:0: detected conn error (1020)
May 10 02:07:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:07:38 cmp02 kernel: [10266.581118]  connection2:0: detected conn error (1020)
May 10 02:07:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:07:41 cmp02 kernel: [10269.587426]  connection2:0: detected conn error (1020)
May 10 02:07:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:07:44 cmp02 kernel: [10272.592821]  connection2:0: detected conn error (1020)
May 10 02:07:47 cmp02 kernel: [10275.601228]  connection2:0: detected conn error (1020)
May 10 02:07:50 cmp02 kernel: [10278.608135]  connection2:0: detected conn error (1020)
May 10 02:07:53 cmp02 kernel: [10281.617729]  connection2:0: detected conn error (1020)
May 10 02:07:56 cmp02 kernel: [10284.624186]  connection2:0: detected conn error (1020)
May 10 02:07:59 cmp02 kernel: [10287.635730]  connection2:0: detected conn error (1020)
May 10 02:08:02 cmp02 kernel: [10290.644697]  connection2:0: detected conn error (1020)
May 10 02:08:05 cmp02 kernel: [10293.651616]  connection2:0: detected conn error (1020)
May 10 02:08:08 cmp02 kernel: [10296.660553]  connection2:0: detected conn error (1020)
May 10 02:08:11 cmp02 kernel: [10299.670064]  connection2:0: detected conn error (1020)
May 10 02:08:14 cmp02 kernel: [10302.677222]  connection2:0: detected conn error (1020)
May 10 02:08:17 cmp02 kernel: [10305.687972]  connection2:0: detected conn error (1020)
May 10 02:08:20 cmp02 kernel: [10308.698458]  connection2:0: detected conn error (1020)
May 10 02:08:23 cmp02 kernel: [10311.708644]  connection2:0: detected conn error (1020)
May 10 02:08:26 cmp02 kernel: [10314.718622]  connection2:0: detected conn error (1020)
May 10 02:08:29 cmp02 kernel: [10317.724335]  connection2:0: detected conn error (1020)
May 10 02:08:32 cmp02 kernel: [10320.735493]  connection2:0: detected conn error (1020)
May 10 02:08:33 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:08:35 cmp02 kernel: [10323.742643]  connection2:0: detected conn error (1020)
May 10 02:08:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:08:38 cmp02 kernel: [10326.747992]  connection2:0: detected conn error (1020)
May 10 02:08:41 cmp02 kernel: [10329.757404]  connection2:0: detected conn error (1020)
May 10 02:08:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:08:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:08:44 cmp02 kernel: [10332.763343]  connection2:0: detected conn error (1020)
May 10 02:08:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:08:47 cmp02 kernel: [10335.770273]  connection2:0: detected conn error (1020)
May 10 02:08:50 cmp02 kernel: [10338.779297]  connection2:0: detected conn error (1020)
May 10 02:08:53 cmp02 kernel: [10341.785298]  connection2:0: detected conn error (1020)
May 10 02:08:56 cmp02 kernel: [10344.793059]  connection2:0: detected conn error (1020)
May 10 02:08:59 cmp02 kernel: [10347.800581]  connection2:0: detected conn error (1020)
May 10 02:09:02 cmp02 kernel: [10350.811120]  connection2:0: detected conn error (1020)
May 10 02:09:05 cmp02 kernel: [10353.819986]  connection2:0: detected conn error (1020)
May 10 02:09:08 cmp02 kernel: [10356.826698]  connection2:0: detected conn error (1020)
May 10 02:09:11 cmp02 kernel: [10359.833231]  connection2:0: detected conn error (1020)
May 10 02:09:14 cmp02 kernel: [10362.840639]  connection2:0: detected conn error (1020)
May 10 02:09:17 cmp02 kernel: [10365.847293]  connection2:0: detected conn error (1020)
May 10 02:09:20 cmp02 kernel: [10368.863588]  connection2:0: detected conn error (1020)
May 10 02:09:23 cmp02 kernel: [10371.870639]  connection2:0: detected conn error (1020)
May 10 02:09:26 cmp02 kernel: [10374.883601]  connection2:0: detected conn error (1020)
May 10 02:09:29 cmp02 kernel: [10377.890800]  connection2:0: detected conn error (1020)
May 10 02:09:32 cmp02 kernel: [10380.898645]  connection2:0: detected conn error (1020)
May 10 02:09:33 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:09:35 cmp02 kernel: [10383.908238]  connection2:0: detected conn error (1020)
May 10 02:09:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:09:38 cmp02 kernel: [10386.916377]  connection2:0: detected conn error (1020)
May 10 02:09:41 cmp02 kernel: [10389.925480]  connection2:0: detected conn error (1020)
May 10 02:09:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:09:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:09:44 cmp02 kernel: [10392.932378]  connection2:0: detected conn error (1020)
May 10 02:09:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:09:47 cmp02 kernel: [10395.939295]  connection2:0: detected conn error (1020)
May 10 02:09:50 cmp02 kernel: [10398.947089]  connection2:0: detected conn error (1020)
May 10 02:09:53 cmp02 kernel: [10401.958857]  connection2:0: detected conn error (1020)
May 10 02:09:56 cmp02 kernel: [10404.966211]  connection2:0: detected conn error (1020)
May 10 02:09:59 cmp02 kernel: [10407.974393]  connection2:0: detected conn error (1020)
May 10 02:10:02 cmp02 kernel: [10410.981088]  connection2:0: detected conn error (1020)
May 10 02:10:03 cmp02 kernel: [10411.640415] device tap3805d51e-27 left promiscuous mode
May 10 02:10:04 cmp02 kernel: [10412.007363] audit: type=1400 audit(1525918204.018:295): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-255557d5-cf0b-447f-9b15-1f7ff9217b32" pid=27295 comm="apparmor_parser"
May 10 02:10:03 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:10:04 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap3805d51e-27
May 10 02:10:06 cmp02 kernel: [10413.987846]  connection2:0: detected conn error (1020)
May 10 02:10:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:10:09 cmp02 kernel: [10416.995287]  connection2:0: detected conn error (1020)
May 10 02:10:12 cmp02 kernel: [10420.001965]  connection2:0: detected conn error (1020)
May 10 02:10:15 cmp02 kernel: [10423.011054]  connection2:0: detected conn error (1020)
May 10 02:10:18 cmp02 kernel: [10426.020360]  connection2:0: detected conn error (1020)
May 10 02:10:21 cmp02 kernel: [10429.029057]  connection2:0: detected conn error (1020)
May 10 02:10:24 cmp02 kernel: [10432.038644]  connection2:0: detected conn error (1020)
May 10 02:10:27 cmp02 kernel: [10435.046093]  connection2:0: detected conn error (1020)
May 10 02:10:30 cmp02 kernel: [10438.055056]  connection2:0: detected conn error (1020)
May 10 02:10:33 cmp02 kernel: [10441.064233]  connection2:0: detected conn error (1020)
May 10 02:10:33 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:10:36 cmp02 kernel: [10444.070519]  connection2:0: detected conn error (1020)
May 10 02:10:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:10:39 cmp02 kernel: [10447.077715]  connection2:0: detected conn error (1020)
May 10 02:10:42 cmp02 kernel: [10450.083898]  connection2:0: detected conn error (1020)
May 10 02:10:45 cmp02 kernel: [10453.088991]  connection2:0: detected conn error (1020)
May 10 02:10:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:10:48 cmp02 kernel: [10456.096776]  connection2:0: detected conn error (1020)
May 10 02:10:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:10:51 cmp02 kernel: [10459.101643]  connection2:0: detected conn error (1020)
May 10 02:10:54 cmp02 kernel: [10462.109420]  connection2:0: detected conn error (1020)
May 10 02:10:57 cmp02 kernel: [10465.115812]  connection2:0: detected conn error (1020)
May 10 02:11:00 cmp02 kernel: [10468.122544]  connection2:0: detected conn error (1020)
May 10 02:11:00 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:11:02 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 02:11:03 cmp02 kernel: [10471.130838]  connection2:0: detected conn error (1020)
May 10 02:11:03 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:11:04 cmp02 kernel: [10472.072445] audit: type=1400 audit(1525918264.083:296): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-3db936f7-0769-47e4-a9d3-e79a050ca044" pid=27446 comm="apparmor_parser"
May 10 02:11:04 cmp02 kernel: [10472.312738] audit: type=1400 audit(1525918264.323:297): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-3db936f7-0769-47e4-a9d3-e79a050ca044" pid=27449 comm="apparmor_parser"
May 10 02:11:04 cmp02 kernel: [10472.565569] audit: type=1400 audit(1525918264.576:298): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-3db936f7-0769-47e4-a9d3-e79a050ca044" pid=27452 comm="apparmor_parser"
May 10 02:11:04 cmp02 kernel: [10472.825205] audit: type=1400 audit(1525918264.836:299): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-3db936f7-0769-47e4-a9d3-e79a050ca044" pid=27455 comm="apparmor_parser"
May 10 02:11:04 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapabc5f0be-84 -- add-port br-int tapabc5f0be-84 -- set Interface tapabc5f0be-84 "external-ids:attached-mac=\"fa:16:3e:71:c6:1f\"" -- set Interface tapabc5f0be-84 "external-ids:iface-id=\"abc5f0be-84e4-4624-a23e-c0cf5006f00c\"" -- set Interface tapabc5f0be-84 "external-ids:vm-id=\"3db936f7-0769-47e4-a9d3-e79a050ca044\"" -- set Interface tapabc5f0be-84 external-ids:iface-status=active
May 10 02:11:04 cmp02 kernel: [10472.857670] device tapabc5f0be-84 entered promiscuous mode
May 10 02:11:05 cmp02 kernel: [10473.097740] audit: type=1400 audit(1525918265.108:300): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-3db936f7-0769-47e4-a9d3-e79a050ca044" pid=27527 comm="apparmor_parser"
May 10 02:11:05 cmp02 libvirtd[5599]: 2018-05-10 02:11:05.116+0000: 5608: warning : qemuDomainObjTaint:5532 : Domain id=46 name='instance-00000066' uuid=3db936f7-0769-47e4-a9d3-e79a050ca044 is tainted: host-cpu
May 10 02:11:06 cmp02 kernel: [10474.137130]  connection2:0: detected conn error (1020)
May 10 02:11:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:11:09 cmp02 kernel: [10477.142961]  connection2:0: detected conn error (1020)
May 10 02:11:12 cmp02 kernel: [10480.149553]  connection2:0: detected conn error (1020)
May 10 02:11:15 cmp02 kernel: [10483.155767]  connection2:0: detected conn error (1020)
May 10 02:11:18 cmp02 kernel: [10486.161572]  connection2:0: detected conn error (1020)
May 10 02:11:21 cmp02 kernel: [10489.170507]  connection2:0: detected conn error (1020)
May 10 02:11:24 cmp02 kernel: [10492.178069]  connection2:0: detected conn error (1020)
May 10 02:11:27 cmp02 kernel: [10495.184105]  connection2:0: detected conn error (1020)
May 10 02:11:30 cmp02 kernel: [10498.192337]  connection2:0: detected conn error (1020)
May 10 02:11:33 cmp02 kernel: [10501.201530]  connection2:0: detected conn error (1020)
May 10 02:11:34 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:11:36 cmp02 kernel: [10504.208582]  connection2:0: detected conn error (1020)
May 10 02:11:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:11:39 cmp02 kernel: [10507.215054]  connection2:0: detected conn error (1020)
May 10 02:11:42 cmp02 kernel: [10510.222057]  connection2:0: detected conn error (1020)
May 10 02:11:43 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:11:45 cmp02 kernel: [10513.230313]  connection2:0: detected conn error (1020)
May 10 02:11:46 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:11:48 cmp02 kernel: [10516.236872]  connection2:0: detected conn error (1020)
May 10 02:11:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:11:51 cmp02 kernel: [10519.242820]  connection2:0: detected conn error (1020)
May 10 02:11:54 cmp02 kernel: [10522.250525]  connection2:0: detected conn error (1020)
May 10 02:11:57 cmp02 kernel: [10525.257650]  connection2:0: detected conn error (1020)
May 10 02:12:00 cmp02 kernel: [10528.265266]  connection2:0: detected conn error (1020)
May 10 02:12:03 cmp02 kernel: [10531.275204]  connection2:0: detected conn error (1020)
May 10 02:12:06 cmp02 kernel: [10534.284619]  connection2:0: detected conn error (1020)
May 10 02:12:09 cmp02 kernel: [10537.293895]  connection2:0: detected conn error (1020)
May 10 02:12:12 cmp02 kernel: [10540.302668]  connection2:0: detected conn error (1020)
May 10 02:12:15 cmp02 kernel: [10543.312032]  connection2:0: detected conn error (1020)
May 10 02:12:18 cmp02 kernel: [10546.318993]  connection2:0: detected conn error (1020)
May 10 02:12:21 cmp02 kernel: [10549.324910]  connection2:0: detected conn error (1020)
May 10 02:12:24 cmp02 kernel: [10552.332127]  connection2:0: detected conn error (1020)
May 10 02:12:27 cmp02 kernel: [10555.338839]  connection2:0: detected conn error (1020)
May 10 02:12:30 cmp02 kernel: [10558.345174]  connection2:0: detected conn error (1020)
May 10 02:12:33 cmp02 kernel: [10561.352650]  connection2:0: detected conn error (1020)
May 10 02:12:34 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:12:36 cmp02 kernel: [10564.364122]  connection2:0: detected conn error (1020)
May 10 02:12:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:12:39 cmp02 kernel: [10567.370747]  connection2:0: detected conn error (1020)
May 10 02:12:42 cmp02 kernel: [10570.378656]  connection2:0: detected conn error (1020)
May 10 02:12:45 cmp02 kernel: [10573.391242]  connection2:0: detected conn error (1020)
May 10 02:12:46 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:12:48 cmp02 kernel: [10576.398528]  connection2:0: detected conn error (1020)
May 10 02:12:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:12:51 cmp02 kernel: [10579.404576]  connection2:0: detected conn error (1020)
May 10 02:12:54 cmp02 kernel: [10582.411443]  connection2:0: detected conn error (1020)
May 10 02:12:57 cmp02 kernel: [10585.419566]  connection2:0: detected conn error (1020)
May 10 02:13:00 cmp02 kernel: [10588.426035]  connection2:0: detected conn error (1020)
May 10 02:13:03 cmp02 kernel: [10591.431231]  connection2:0: detected conn error (1020)
May 10 02:13:06 cmp02 kernel: [10594.439470]  connection2:0: detected conn error (1020)
May 10 02:13:09 cmp02 kernel: [10597.445966]  connection2:0: detected conn error (1020)
May 10 02:13:12 cmp02 kernel: [10600.454210]  connection2:0: detected conn error (1020)
May 10 02:13:15 cmp02 kernel: [10603.460027]  connection2:0: detected conn error (1020)
May 10 02:13:18 cmp02 kernel: [10606.468027]  connection2:0: detected conn error (1020)
May 10 02:13:21 cmp02 kernel: [10609.474622]  connection2:0: detected conn error (1020)
May 10 02:13:24 cmp02 kernel: [10612.488540]  connection2:0: detected conn error (1020)
May 10 02:13:27 cmp02 kernel: [10615.494115]  connection2:0: detected conn error (1020)
May 10 02:13:30 cmp02 kernel: [10618.503081]  connection2:0: detected conn error (1020)
May 10 02:13:33 cmp02 kernel: [10621.510345]  connection2:0: detected conn error (1020)
May 10 02:13:31 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:13:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:13:36 cmp02 kernel: [10624.517887]  connection2:0: detected conn error (1020)
May 10 02:13:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:13:39 cmp02 kernel: [10627.525327]  connection2:0: detected conn error (1020)
May 10 02:13:42 cmp02 kernel: [10630.534732]  connection2:0: detected conn error (1020)
May 10 02:13:45 cmp02 kernel: [10633.543183]  connection2:0: detected conn error (1020)
May 10 02:13:46 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:13:48 cmp02 kernel: [10636.549210]  connection2:0: detected conn error (1020)
May 10 02:13:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:13:51 cmp02 kernel: [10639.555897]  connection2:0: detected conn error (1020)
May 10 02:13:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:13:54 cmp02 kernel: [10642.565179]  connection2:0: detected conn error (1020)
May 10 02:13:57 cmp02 kernel: [10645.571190]  connection2:0: detected conn error (1020)
May 10 02:14:00 cmp02 kernel: [10648.579079]  connection2:0: detected conn error (1020)
May 10 02:14:03 cmp02 kernel: [10651.586987]  connection2:0: detected conn error (1020)
May 10 02:14:06 cmp02 kernel: [10654.595107]  connection2:0: detected conn error (1020)
May 10 02:14:09 cmp02 kernel: [10657.604217]  connection2:0: detected conn error (1020)
May 10 02:14:12 cmp02 kernel: [10660.610617]  connection2:0: detected conn error (1020)
May 10 02:14:15 cmp02 kernel: [10663.619667]  connection2:0: detected conn error (1020)
May 10 02:14:18 cmp02 kernel: [10666.630894]  connection2:0: detected conn error (1020)
May 10 02:14:21 cmp02 kernel: [10669.638668]  connection2:0: detected conn error (1020)
May 10 02:14:24 cmp02 kernel: [10672.646586]  connection2:0: detected conn error (1020)
May 10 02:14:27 cmp02 kernel: [10675.655598]  connection2:0: detected conn error (1020)
May 10 02:14:30 cmp02 kernel: [10678.662562]  connection2:0: detected conn error (1020)
May 10 02:14:33 cmp02 kernel: [10681.668452]  connection2:0: detected conn error (1020)
May 10 02:14:31 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:14:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:14:36 cmp02 kernel: [10684.676770]  connection2:0: detected conn error (1020)
May 10 02:14:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:14:39 cmp02 kernel: [10687.683602]  connection2:0: detected conn error (1020)
May 10 02:14:42 cmp02 kernel: [10690.690129]  connection2:0: detected conn error (1020)
May 10 02:14:45 cmp02 kernel: [10693.698042]  connection2:0: detected conn error (1020)
May 10 02:14:48 cmp02 kernel: [10696.707571]  connection2:0: detected conn error (1020)
May 10 02:14:46 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:14:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:14:51 cmp02 kernel: [10699.714515]  connection2:0: detected conn error (1020)
May 10 02:14:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:14:54 cmp02 kernel: [10702.722587]  connection2:0: detected conn error (1020)
May 10 02:14:57 cmp02 kernel: [10705.733299]  connection2:0: detected conn error (1020)
May 10 02:15:00 cmp02 kernel: [10708.739828]  connection2:0: detected conn error (1020)
May 10 02:15:03 cmp02 kernel: [10711.748183]  connection2:0: detected conn error (1020)
May 10 02:15:06 cmp02 kernel: [10714.753576]  connection2:0: detected conn error (1020)
May 10 02:15:09 cmp02 kernel: [10717.761267]  connection2:0: detected conn error (1020)
May 10 02:15:12 cmp02 kernel: [10720.774107]  connection2:0: detected conn error (1020)
May 10 02:15:15 cmp02 kernel: [10723.779445]  connection2:0: detected conn error (1020)
May 10 02:15:18 cmp02 kernel: [10726.796465]  connection2:0: detected conn error (1020)
May 10 02:15:21 cmp02 kernel: [10729.802779]  connection2:0: detected conn error (1020)
May 10 02:15:24 cmp02 kernel: [10732.809686]  connection2:0: detected conn error (1020)
May 10 02:15:27 cmp02 kernel: [10735.817384]  connection2:0: detected conn error (1020)
May 10 02:15:30 cmp02 kernel: [10738.827636]  connection2:0: detected conn error (1020)
May 10 02:15:33 cmp02 kernel: [10741.835694]  connection2:0: detected conn error (1020)
May 10 02:15:31 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:15:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:15:36 cmp02 kernel: [10744.844875]  connection2:0: detected conn error (1020)
May 10 02:15:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:15:39 cmp02 kernel: [10747.852060]  connection2:0: detected conn error (1020)
May 10 02:15:42 cmp02 kernel: [10750.863062]  connection2:0: detected conn error (1020)
May 10 02:15:45 cmp02 kernel: [10753.872319]  connection2:0: detected conn error (1020)
May 10 02:15:48 cmp02 kernel: [10756.885140]  connection2:0: detected conn error (1020)
May 10 02:15:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:15:51 cmp02 kernel: [10759.890088]  connection2:0: detected conn error (1020)
May 10 02:15:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:15:54 cmp02 kernel: [10762.899780]  connection2:0: detected conn error (1020)
May 10 02:15:57 cmp02 kernel: [10765.907082]  connection2:0: detected conn error (1020)
May 10 02:16:00 cmp02 kernel: [10768.914275]  connection2:0: detected conn error (1020)
May 10 02:16:03 cmp02 kernel: [10771.923040]  connection2:0: detected conn error (1020)
May 10 02:16:06 cmp02 kernel: [10774.929604]  connection2:0: detected conn error (1020)
May 10 02:16:09 cmp02 kernel: [10777.936923]  connection2:0: detected conn error (1020)
May 10 02:16:12 cmp02 kernel: [10780.944376]  connection2:0: detected conn error (1020)
May 10 02:16:15 cmp02 kernel: [10783.951927]  connection2:0: detected conn error (1020)
May 10 02:16:18 cmp02 kernel: [10786.958987]  connection2:0: detected conn error (1020)
May 10 02:16:21 cmp02 kernel: [10789.965996]  connection2:0: detected conn error (1020)
May 10 02:16:24 cmp02 kernel: [10792.972929]  connection2:0: detected conn error (1020)
May 10 02:16:27 cmp02 kernel: [10795.979739]  connection2:0: detected conn error (1020)
May 10 02:16:30 cmp02 kernel: [10798.989619]  connection2:0: detected conn error (1020)
May 10 02:16:34 cmp02 kernel: [10801.998148]  connection2:0: detected conn error (1020)
May 10 02:16:31 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:16:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:16:37 cmp02 kernel: [10805.004516]  connection2:0: detected conn error (1020)
May 10 02:16:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:16:40 cmp02 kernel: [10808.011332]  connection2:0: detected conn error (1020)
May 10 02:16:43 cmp02 kernel: [10811.019039]  connection2:0: detected conn error (1020)
May 10 02:16:43 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:16:45 cmp02 salt-minion[2824]: [INFO    ] Running scheduled job: __mine_interval
May 10 02:16:46 cmp02 kernel: [10814.028216]  connection2:0: detected conn error (1020)
May 10 02:16:46 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:16:49 cmp02 kernel: [10817.035695]  connection2:0: detected conn error (1020)
May 10 02:16:52 cmp02 kernel: [10820.049940]  connection2:0: detected conn error (1020)
May 10 02:16:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:16:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:16:55 cmp02 kernel: [10823.057854]  connection2:0: detected conn error (1020)
May 10 02:16:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:16:58 cmp02 kernel: [10826.066252]  connection2:0: detected conn error (1020)
May 10 02:17:01 cmp02 kernel: [10829.072958]  connection2:0: detected conn error (1020)
May 10 02:16:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:17:01 cmp02 CRON[28221]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 10 02:17:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:17:04 cmp02 kernel: [10832.079166]  connection2:0: detected conn error (1020)
May 10 02:17:07 cmp02 kernel: [10835.096022]  connection2:0: detected conn error (1020)
May 10 02:17:10 cmp02 kernel: [10838.104355]  connection2:0: detected conn error (1020)
May 10 02:17:13 cmp02 kernel: [10841.111469]  connection2:0: detected conn error (1020)
May 10 02:17:16 cmp02 kernel: [10844.121656]  connection2:0: detected conn error (1020)
May 10 02:17:19 cmp02 kernel: [10847.130707]  connection2:0: detected conn error (1020)
May 10 02:17:22 cmp02 kernel: [10850.139245]  connection2:0: detected conn error (1020)
May 10 02:17:25 cmp02 kernel: [10853.148075]  connection2:0: detected conn error (1020)
May 10 02:17:28 cmp02 kernel: [10856.154176]  connection2:0: detected conn error (1020)
May 10 02:17:31 cmp02 kernel: [10859.160397]  connection2:0: detected conn error (1020)
May 10 02:17:34 cmp02 kernel: [10862.166772]  connection2:0: detected conn error (1020)
May 10 02:17:31 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:17:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:17:37 cmp02 kernel: [10865.172190]  connection2:0: detected conn error (1020)
May 10 02:17:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:17:40 cmp02 kernel: [10868.179713]  connection2:0: detected conn error (1020)
May 10 02:17:43 cmp02 kernel: [10871.189681]  connection2:0: detected conn error (1020)
May 10 02:17:46 cmp02 kernel: [10874.198830]  connection2:0: detected conn error (1020)
May 10 02:17:49 cmp02 kernel: [10877.207716]  connection2:0: detected conn error (1020)
May 10 02:17:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:17:52 cmp02 kernel: [10880.214637]  connection2:0: detected conn error (1020)
May 10 02:17:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:17:55 cmp02 kernel: [10883.221397]  connection2:0: detected conn error (1020)
May 10 02:17:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:17:58 cmp02 kernel: [10886.235277]  connection2:0: detected conn error (1020)
May 10 02:18:01 cmp02 kernel: [10889.244609]  connection2:0: detected conn error (1020)
May 10 02:18:04 cmp02 kernel: [10892.252856]  connection2:0: detected conn error (1020)
May 10 02:18:07 cmp02 kernel: [10895.258698]  connection2:0: detected conn error (1020)
May 10 02:18:10 cmp02 kernel: [10898.269098]  connection2:0: detected conn error (1020)
May 10 02:18:13 cmp02 kernel: [10901.285209]  connection2:0: detected conn error (1020)
May 10 02:18:16 cmp02 kernel: [10904.296068]  connection2:0: detected conn error (1020)
May 10 02:18:19 cmp02 kernel: [10907.301935]  connection2:0: detected conn error (1020)
May 10 02:18:22 cmp02 kernel: [10910.307240]  connection2:0: detected conn error (1020)
May 10 02:18:25 cmp02 kernel: [10913.316433]  connection2:0: detected conn error (1020)
May 10 02:18:28 cmp02 kernel: [10916.325747]  connection2:0: detected conn error (1020)
May 10 02:18:31 cmp02 kernel: [10919.334467]  connection2:0: detected conn error (1020)
May 10 02:18:34 cmp02 kernel: [10922.338934]  connection2:0: detected conn error (1020)
May 10 02:18:31 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:18:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:18:37 cmp02 kernel: [10925.345290]  connection2:0: detected conn error (1020)
May 10 02:18:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:18:40 cmp02 kernel: [10928.353638]  connection2:0: detected conn error (1020)
May 10 02:18:43 cmp02 kernel: [10931.362444]  connection2:0: detected conn error (1020)
May 10 02:18:46 cmp02 kernel: [10934.370919]  connection2:0: detected conn error (1020)
May 10 02:18:49 cmp02 kernel: [10937.387415]  connection2:0: detected conn error (1020)
May 10 02:18:52 cmp02 kernel: [10940.392514]  connection2:0: detected conn error (1020)
May 10 02:18:53 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:18:55 cmp02 kernel: [10943.400254]  connection2:0: detected conn error (1020)
May 10 02:18:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:18:58 cmp02 kernel: [10946.407466]  connection2:0: detected conn error (1020)
May 10 02:19:01 cmp02 kernel: [10949.413974]  connection2:0: detected conn error (1020)
May 10 02:19:04 cmp02 kernel: [10952.420150]  connection2:0: detected conn error (1020)
May 10 02:19:07 cmp02 kernel: [10955.426498]  connection2:0: detected conn error (1020)
May 10 02:19:10 cmp02 kernel: [10958.433767]  connection2:0: detected conn error (1020)
May 10 02:19:13 cmp02 kernel: [10961.446165]  connection2:0: detected conn error (1020)
May 10 02:19:16 cmp02 kernel: [10964.452110]  connection2:0: detected conn error (1020)
May 10 02:19:19 cmp02 kernel: [10967.459249]  connection2:0: detected conn error (1020)
May 10 02:19:22 cmp02 kernel: [10970.468283]  connection2:0: detected conn error (1020)
May 10 02:19:25 cmp02 kernel: [10973.475306]  connection2:0: detected conn error (1020)
May 10 02:19:28 cmp02 kernel: [10976.481727]  connection2:0: detected conn error (1020)
May 10 02:19:31 cmp02 kernel: [10979.490322]  connection2:0: detected conn error (1020)
May 10 02:19:32 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:19:34 cmp02 kernel: [10982.501254]  connection2:0: detected conn error (1020)
May 10 02:19:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:19:37 cmp02 kernel: [10985.508352]  connection2:0: detected conn error (1020)
May 10 02:19:40 cmp02 kernel: [10988.518463]  connection2:0: detected conn error (1020)
May 10 02:19:43 cmp02 kernel: [10991.527747]  connection2:0: detected conn error (1020)
May 10 02:19:46 cmp02 kernel: [10994.534637]  connection2:0: detected conn error (1020)
May 10 02:19:49 cmp02 kernel: [10997.546843]  connection2:0: detected conn error (1020)
May 10 02:19:52 cmp02 kernel: [11000.570430]  connection2:0: detected conn error (1020)
May 10 02:19:55 cmp02 kernel: [11003.579619]  connection2:0: detected conn error (1020)
May 10 02:19:53 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:19:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:19:58 cmp02 kernel: [11006.601185]  connection2:0: detected conn error (1020)
May 10 02:19:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:20:01 cmp02 kernel: [11009.608884]  connection2:0: detected conn error (1020)
May 10 02:20:04 cmp02 kernel: [11012.620004]  connection2:0: detected conn error (1020)
May 10 02:20:07 cmp02 kernel: [11015.627753]  connection2:0: detected conn error (1020)
May 10 02:20:10 cmp02 kernel: [11018.633737]  connection2:0: detected conn error (1020)
May 10 02:20:13 cmp02 kernel: [11021.639588]  connection2:0: detected conn error (1020)
May 10 02:20:16 cmp02 kernel: [11024.646942]  connection2:0: detected conn error (1020)
May 10 02:20:19 cmp02 kernel: [11027.654898]  connection2:0: detected conn error (1020)
May 10 02:20:22 cmp02 kernel: [11030.662108]  connection2:0: detected conn error (1020)
May 10 02:20:25 cmp02 kernel: [11033.672177]  connection2:0: detected conn error (1020)
May 10 02:20:28 cmp02 kernel: [11036.679419]  connection2:0: detected conn error (1020)
May 10 02:20:31 cmp02 kernel: [11039.691258]  connection2:0: detected conn error (1020)
May 10 02:20:32 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:20:34 cmp02 kernel: [11042.699269]  connection2:0: detected conn error (1020)
May 10 02:20:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:20:37 cmp02 kernel: [11045.710113]  connection2:0: detected conn error (1020)
May 10 02:20:40 cmp02 kernel: [11048.717331]  connection2:0: detected conn error (1020)
May 10 02:20:43 cmp02 kernel: [11051.725616]  connection2:0: detected conn error (1020)
May 10 02:20:46 cmp02 kernel: [11054.736362]  connection2:0: detected conn error (1020)
May 10 02:20:49 cmp02 kernel: [11057.744390]  connection2:0: detected conn error (1020)
May 10 02:20:52 cmp02 kernel: [11060.750754]  connection2:0: detected conn error (1020)
May 10 02:20:55 cmp02 kernel: [11063.763448]  connection2:0: detected conn error (1020)
May 10 02:20:53 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:20:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:20:58 cmp02 kernel: [11066.769146]  connection2:0: detected conn error (1020)
May 10 02:20:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:21:01 cmp02 kernel: [11069.775535]  connection2:0: detected conn error (1020)
May 10 02:21:04 cmp02 kernel: [11072.783919]  connection2:0: detected conn error (1020)
May 10 02:21:07 cmp02 kernel: [11075.789703]  connection2:0: detected conn error (1020)
May 10 02:21:10 cmp02 kernel: [11078.796996]  connection2:0: detected conn error (1020)
May 10 02:21:13 cmp02 kernel: [11081.803764]  connection2:0: detected conn error (1020)
May 10 02:21:16 cmp02 kernel: [11084.807894]  connection2:0: detected conn error (1020)
May 10 02:21:17 cmp02 kernel: [11085.677315] device tapabc5f0be-84 left promiscuous mode
May 10 02:21:18 cmp02 kernel: [11086.024689] audit: type=1400 audit(1525918878.023:301): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-3db936f7-0769-47e4-a9d3-e79a050ca044" pid=28585 comm="apparmor_parser"
May 10 02:21:17 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:21:18 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapabc5f0be-84
May 10 02:21:19 cmp02 kernel: [11087.814128]  connection2:0: detected conn error (1020)
May 10 02:21:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:21:22 cmp02 kernel: [11090.822028]  connection2:0: detected conn error (1020)
May 10 02:21:25 cmp02 kernel: [11093.830524]  connection2:0: detected conn error (1020)
May 10 02:21:28 cmp02 kernel: [11096.840913]  connection2:0: detected conn error (1020)
May 10 02:21:31 cmp02 kernel: [11099.852053]  connection2:0: detected conn error (1020)
May 10 02:21:32 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:21:34 cmp02 kernel: [11102.861474]  connection2:0: detected conn error (1020)
May 10 02:21:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:21:37 cmp02 kernel: [11105.869559]  connection2:0: detected conn error (1020)
May 10 02:21:40 cmp02 kernel: [11108.878276]  connection2:0: detected conn error (1020)
May 10 02:21:43 cmp02 kernel: [11111.885747]  connection2:0: detected conn error (1020)
May 10 02:21:46 cmp02 kernel: [11114.892043]  connection2:0: detected conn error (1020)
May 10 02:21:49 cmp02 kernel: [11117.898809]  connection2:0: detected conn error (1020)
May 10 02:21:47 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:21:50 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:21:52 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 02:21:52 cmp02 kernel: [11120.905633]  connection2:0: detected conn error (1020)
May 10 02:21:53 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:21:53 cmp02 kernel: [11121.765716] audit: type=1400 audit(1525918913.763:302): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-5e7343f1-cd07-4efc-8ee9-e7f651f3b75f" pid=28670 comm="apparmor_parser"
May 10 02:21:54 cmp02 kernel: [11122.025049] audit: type=1400 audit(1525918914.022:303): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-5e7343f1-cd07-4efc-8ee9-e7f651f3b75f" pid=28673 comm="apparmor_parser"
May 10 02:21:54 cmp02 kernel: [11122.279373] audit: type=1400 audit(1525918914.277:304): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-5e7343f1-cd07-4efc-8ee9-e7f651f3b75f" pid=28676 comm="apparmor_parser"
May 10 02:21:54 cmp02 kernel: [11122.519523] audit: type=1400 audit(1525918914.517:305): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-5e7343f1-cd07-4efc-8ee9-e7f651f3b75f" pid=28679 comm="apparmor_parser"
May 10 02:21:54 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap57c2fdea-b9 -- add-port br-int tap57c2fdea-b9 -- set Interface tap57c2fdea-b9 "external-ids:attached-mac=\"fa:16:3e:d9:f7:6c\"" -- set Interface tap57c2fdea-b9 "external-ids:iface-id=\"57c2fdea-b911-47d5-9f1b-7dc2c3537634\"" -- set Interface tap57c2fdea-b9 "external-ids:vm-id=\"5e7343f1-cd07-4efc-8ee9-e7f651f3b75f\"" -- set Interface tap57c2fdea-b9 external-ids:iface-status=active
May 10 02:21:54 cmp02 kernel: [11122.551296] device tap57c2fdea-b9 entered promiscuous mode
May 10 02:21:54 cmp02 kernel: [11122.800775] audit: type=1400 audit(1525918914.798:306): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-5e7343f1-cd07-4efc-8ee9-e7f651f3b75f" pid=28786 comm="apparmor_parser"
May 10 02:21:54 cmp02 libvirtd[5599]: 2018-05-10 02:21:54.806+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=47 name='instance-00000067' uuid=5e7343f1-cd07-4efc-8ee9-e7f651f3b75f is tainted: host-cpu
May 10 02:21:55 cmp02 kernel: [11123.913028]  connection2:0: detected conn error (1020)
May 10 02:21:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:21:58 cmp02 kernel: [11126.922402]  connection2:0: detected conn error (1020)
May 10 02:21:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:22:01 cmp02 kernel: [11129.929696]  connection2:0: detected conn error (1020)
May 10 02:22:04 cmp02 kernel: [11132.936039]  connection2:0: detected conn error (1020)
May 10 02:22:07 cmp02 kernel: [11135.943733]  connection2:0: detected conn error (1020)
May 10 02:22:10 cmp02 kernel: [11138.949963]  connection2:0: detected conn error (1020)
May 10 02:22:13 cmp02 kernel: [11141.958570]  connection2:0: detected conn error (1020)
May 10 02:22:16 cmp02 kernel: [11144.963887]  connection2:0: detected conn error (1020)
May 10 02:22:19 cmp02 kernel: [11147.969000]  connection2:0: detected conn error (1020)
May 10 02:22:22 cmp02 kernel: [11150.975002]  connection2:0: detected conn error (1020)
May 10 02:22:25 cmp02 kernel: [11153.981662]  connection2:0: detected conn error (1020)
May 10 02:22:28 cmp02 kernel: [11156.988817]  connection2:0: detected conn error (1020)
May 10 02:22:31 cmp02 kernel: [11159.995034]  connection2:0: detected conn error (1020)
May 10 02:22:32 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:22:35 cmp02 kernel: [11163.001231]  connection2:0: detected conn error (1020)
May 10 02:22:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:22:38 cmp02 kernel: [11166.011120]  connection2:0: detected conn error (1020)
May 10 02:22:41 cmp02 kernel: [11169.018953]  connection2:0: detected conn error (1020)
May 10 02:22:44 cmp02 kernel: [11172.024298]  connection2:0: detected conn error (1020)
May 10 02:22:47 cmp02 kernel: [11175.030832]  connection2:0: detected conn error (1020)
May 10 02:22:50 cmp02 kernel: [11178.039045]  connection2:0: detected conn error (1020)
May 10 02:22:53 cmp02 kernel: [11181.046237]  connection2:0: detected conn error (1020)
May 10 02:22:56 cmp02 kernel: [11184.055591]  connection2:0: detected conn error (1020)
May 10 02:22:59 cmp02 kernel: [11187.060946]  connection2:0: detected conn error (1020)
May 10 02:22:56 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:22:59 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:23:02 cmp02 kernel: [11190.067377]  connection2:0: detected conn error (1020)
May 10 02:23:02 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:23:05 cmp02 kernel: [11193.078456]  connection2:0: detected conn error (1020)
May 10 02:23:08 cmp02 kernel: [11196.085116]  connection2:0: detected conn error (1020)
May 10 02:23:11 cmp02 kernel: [11199.092281]  connection2:0: detected conn error (1020)
May 10 02:23:14 cmp02 kernel: [11202.099779]  connection2:0: detected conn error (1020)
May 10 02:23:17 cmp02 kernel: [11205.124454]  connection2:0: detected conn error (1020)
May 10 02:23:20 cmp02 kernel: [11208.134550]  connection2:0: detected conn error (1020)
May 10 02:23:23 cmp02 kernel: [11211.143885]  connection2:0: detected conn error (1020)
May 10 02:23:26 cmp02 kernel: [11214.156500]  connection2:0: detected conn error (1020)
May 10 02:23:29 cmp02 kernel: [11217.162599]  connection2:0: detected conn error (1020)
May 10 02:23:32 cmp02 kernel: [11220.171754]  connection2:0: detected conn error (1020)
May 10 02:23:32 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:23:35 cmp02 kernel: [11223.177277]  connection2:0: detected conn error (1020)
May 10 02:23:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:23:38 cmp02 kernel: [11226.186746]  connection2:0: detected conn error (1020)
May 10 02:23:41 cmp02 kernel: [11229.197157]  connection2:0: detected conn error (1020)
May 10 02:23:44 cmp02 kernel: [11232.208796]  connection2:0: detected conn error (1020)
May 10 02:23:47 cmp02 kernel: [11235.216979]  connection2:0: detected conn error (1020)
May 10 02:23:50 cmp02 kernel: [11238.226631]  connection2:0: detected conn error (1020)
May 10 02:23:53 cmp02 kernel: [11241.235381]  connection2:0: detected conn error (1020)
May 10 02:23:56 cmp02 kernel: [11244.241819]  connection2:0: detected conn error (1020)
May 10 02:23:59 cmp02 kernel: [11247.252427]  connection2:0: detected conn error (1020)
May 10 02:23:59 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:24:02 cmp02 kernel: [11250.262490]  connection2:0: detected conn error (1020)
May 10 02:24:02 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:24:05 cmp02 kernel: [11253.270110]  connection2:0: detected conn error (1020)
May 10 02:24:08 cmp02 kernel: [11256.280506]  connection2:0: detected conn error (1020)
May 10 02:24:11 cmp02 kernel: [11259.290355]  connection2:0: detected conn error (1020)
May 10 02:24:14 cmp02 kernel: [11262.296514]  connection2:0: detected conn error (1020)
May 10 02:24:17 cmp02 kernel: [11265.306835]  connection2:0: detected conn error (1020)
May 10 02:24:20 cmp02 kernel: [11268.312981]  connection2:0: detected conn error (1020)
May 10 02:24:23 cmp02 kernel: [11271.318488]  connection2:0: detected conn error (1020)
May 10 02:24:26 cmp02 kernel: [11274.331816]  connection2:0: detected conn error (1020)
May 10 02:24:29 cmp02 kernel: [11277.340386]  connection2:0: detected conn error (1020)
May 10 02:24:32 cmp02 kernel: [11280.347319]  connection2:0: detected conn error (1020)
May 10 02:24:32 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:24:35 cmp02 kernel: [11283.359423]  connection2:0: detected conn error (1020)
May 10 02:24:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:24:38 cmp02 kernel: [11286.370317]  connection2:0: detected conn error (1020)
May 10 02:24:41 cmp02 kernel: [11289.379699]  connection2:0: detected conn error (1020)
May 10 02:24:44 cmp02 kernel: [11292.391742]  connection2:0: detected conn error (1020)
May 10 02:24:47 cmp02 kernel: [11295.400638]  connection2:0: detected conn error (1020)
May 10 02:24:50 cmp02 kernel: [11298.407347]  connection2:0: detected conn error (1020)
May 10 02:24:53 cmp02 kernel: [11301.419572]  connection2:0: detected conn error (1020)
May 10 02:24:56 cmp02 kernel: [11304.425422]  connection2:0: detected conn error (1020)
May 10 02:24:59 cmp02 kernel: [11307.434601]  connection2:0: detected conn error (1020)
May 10 02:25:02 cmp02 kernel: [11310.440942]  connection2:0: detected conn error (1020)
May 10 02:25:02 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:25:05 cmp02 kernel: [11313.449636]  connection2:0: detected conn error (1020)
May 10 02:25:05 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:25:08 cmp02 kernel: [11316.460542]  connection2:0: detected conn error (1020)
May 10 02:25:11 cmp02 kernel: [11319.468110]  connection2:0: detected conn error (1020)
May 10 02:25:14 cmp02 kernel: [11322.479098]  connection2:0: detected conn error (1020)
May 10 02:25:17 cmp02 kernel: [11325.485218]  connection2:0: detected conn error (1020)
May 10 02:25:20 cmp02 kernel: [11328.490825]  connection2:0: detected conn error (1020)
May 10 02:25:23 cmp02 kernel: [11331.498983]  connection2:0: detected conn error (1020)
May 10 02:25:26 cmp02 kernel: [11334.506993]  connection2:0: detected conn error (1020)
May 10 02:25:29 cmp02 kernel: [11337.515338]  connection2:0: detected conn error (1020)
May 10 02:25:32 cmp02 kernel: [11340.527696]  connection2:0: detected conn error (1020)
May 10 02:25:33 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:25:35 cmp02 kernel: [11343.536625]  connection2:0: detected conn error (1020)
May 10 02:25:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:25:38 cmp02 kernel: [11346.549300]  connection2:0: detected conn error (1020)
May 10 02:25:41 cmp02 kernel: [11349.557795]  connection2:0: detected conn error (1020)
May 10 02:25:44 cmp02 kernel: [11352.567008]  connection2:0: detected conn error (1020)
May 10 02:25:47 cmp02 kernel: [11355.575789]  connection2:0: detected conn error (1020)
May 10 02:25:50 cmp02 kernel: [11358.587779]  connection2:0: detected conn error (1020)
May 10 02:25:53 cmp02 kernel: [11361.596129]  connection2:0: detected conn error (1020)
May 10 02:25:56 cmp02 kernel: [11364.605045]  connection2:0: detected conn error (1020)
May 10 02:25:59 cmp02 kernel: [11367.611985]  connection2:0: detected conn error (1020)
May 10 02:26:02 cmp02 kernel: [11370.621640]  connection2:0: detected conn error (1020)
May 10 02:26:00 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:26:03 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:26:05 cmp02 kernel: [11373.627594]  connection2:0: detected conn error (1020)
May 10 02:26:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:26:08 cmp02 kernel: [11376.638793]  connection2:0: detected conn error (1020)
May 10 02:26:11 cmp02 kernel: [11379.646875]  connection2:0: detected conn error (1020)
May 10 02:26:14 cmp02 kernel: [11382.654817]  connection2:0: detected conn error (1020)
May 10 02:26:17 cmp02 kernel: [11385.664540]  connection2:0: detected conn error (1020)
May 10 02:26:20 cmp02 kernel: [11388.672741]  connection2:0: detected conn error (1020)
May 10 02:26:23 cmp02 kernel: [11391.680558]  connection2:0: detected conn error (1020)
May 10 02:26:26 cmp02 kernel: [11394.688573]  connection2:0: detected conn error (1020)
May 10 02:26:29 cmp02 kernel: [11397.696472]  connection2:0: detected conn error (1020)
May 10 02:26:32 cmp02 kernel: [11400.705294]  connection2:0: detected conn error (1020)
May 10 02:26:33 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:26:35 cmp02 kernel: [11403.711862]  connection2:0: detected conn error (1020)
May 10 02:26:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:26:38 cmp02 kernel: [11406.725728]  connection2:0: detected conn error (1020)
May 10 02:26:41 cmp02 kernel: [11409.733276]  connection2:0: detected conn error (1020)
May 10 02:26:44 cmp02 kernel: [11412.740794]  connection2:0: detected conn error (1020)
May 10 02:26:47 cmp02 kernel: [11415.747365]  connection2:0: detected conn error (1020)
May 10 02:26:50 cmp02 kernel: [11418.754683]  connection2:0: detected conn error (1020)
May 10 02:26:53 cmp02 kernel: [11421.762004]  connection2:0: detected conn error (1020)
May 10 02:26:56 cmp02 kernel: [11424.771172]  connection2:0: detected conn error (1020)
May 10 02:26:59 cmp02 kernel: [11427.779274]  connection2:0: detected conn error (1020)
May 10 02:27:02 cmp02 kernel: [11430.786969]  connection2:0: detected conn error (1020)
May 10 02:27:03 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:27:05 cmp02 kernel: [11433.793137]  connection2:0: detected conn error (1020)
May 10 02:27:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:27:08 cmp02 kernel: [11436.800681]  connection2:0: detected conn error (1020)
May 10 02:27:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:27:11 cmp02 kernel: [11439.809841]  connection2:0: detected conn error (1020)
May 10 02:27:14 cmp02 kernel: [11442.817734]  connection2:0: detected conn error (1020)
May 10 02:27:17 cmp02 kernel: [11445.824658]  connection2:0: detected conn error (1020)
May 10 02:27:20 cmp02 kernel: [11448.834086]  connection2:0: detected conn error (1020)
May 10 02:27:23 cmp02 kernel: [11451.841215]  connection2:0: detected conn error (1020)
May 10 02:27:26 cmp02 kernel: [11454.847838]  connection2:0: detected conn error (1020)
May 10 02:27:29 cmp02 kernel: [11457.855572]  connection2:0: detected conn error (1020)
May 10 02:27:32 cmp02 kernel: [11460.866533]  connection2:0: detected conn error (1020)
May 10 02:27:33 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:27:35 cmp02 kernel: [11463.873848]  connection2:0: detected conn error (1020)
May 10 02:27:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:27:38 cmp02 kernel: [11466.881049]  connection2:0: detected conn error (1020)
May 10 02:27:41 cmp02 kernel: [11469.886187]  connection2:0: detected conn error (1020)
May 10 02:27:44 cmp02 kernel: [11472.893456]  connection2:0: detected conn error (1020)
May 10 02:27:47 cmp02 kernel: [11475.899576]  connection2:0: detected conn error (1020)
May 10 02:27:50 cmp02 kernel: [11478.904890]  connection2:0: detected conn error (1020)
May 10 02:27:53 cmp02 kernel: [11481.912454]  connection2:0: detected conn error (1020)
May 10 02:27:56 cmp02 kernel: [11484.922377]  connection2:0: detected conn error (1020)
May 10 02:27:59 cmp02 kernel: [11487.935066]  connection2:0: detected conn error (1020)
May 10 02:28:02 cmp02 kernel: [11490.952348]  connection2:0: detected conn error (1020)
May 10 02:28:05 cmp02 kernel: [11493.962294]  connection2:0: detected conn error (1020)
May 10 02:28:03 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:28:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:28:08 cmp02 kernel: [11496.968855]  connection2:0: detected conn error (1020)
May 10 02:28:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:28:11 cmp02 kernel: [11499.979176]  connection2:0: detected conn error (1020)
May 10 02:28:14 cmp02 kernel: [11502.985459]  connection2:0: detected conn error (1020)
May 10 02:28:17 cmp02 kernel: [11505.994780]  connection2:0: detected conn error (1020)
May 10 02:28:20 cmp02 kernel: [11509.002299]  connection2:0: detected conn error (1020)
May 10 02:28:24 cmp02 kernel: [11512.011035]  connection2:0: detected conn error (1020)
May 10 02:28:27 cmp02 kernel: [11515.017846]  connection2:0: detected conn error (1020)
May 10 02:28:30 cmp02 kernel: [11518.024161]  connection2:0: detected conn error (1020)
May 10 02:28:33 cmp02 kernel: [11521.034757]  connection2:0: detected conn error (1020)
May 10 02:28:33 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:28:36 cmp02 kernel: [11524.042201]  connection2:0: detected conn error (1020)
May 10 02:28:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:28:39 cmp02 kernel: [11527.047168]  connection2:0: detected conn error (1020)
May 10 02:28:42 cmp02 kernel: [11530.055126]  connection2:0: detected conn error (1020)
May 10 02:28:45 cmp02 kernel: [11533.062064]  connection2:0: detected conn error (1020)
May 10 02:28:48 cmp02 kernel: [11536.069612]  connection2:0: detected conn error (1020)
May 10 02:28:51 cmp02 kernel: [11539.077599]  connection2:0: detected conn error (1020)
May 10 02:28:54 cmp02 kernel: [11542.085910]  connection2:0: detected conn error (1020)
May 10 02:28:57 cmp02 kernel: [11545.093379]  connection2:0: detected conn error (1020)
May 10 02:29:00 cmp02 kernel: [11548.101044]  connection2:0: detected conn error (1020)
May 10 02:29:03 cmp02 kernel: [11551.109436]  connection2:0: detected conn error (1020)
May 10 02:29:06 cmp02 kernel: [11554.115598]  connection2:0: detected conn error (1020)
May 10 02:29:06 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:29:09 cmp02 kernel: [11557.124408]  connection2:0: detected conn error (1020)
May 10 02:29:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:29:12 cmp02 kernel: [11560.131792]  connection2:0: detected conn error (1020)
May 10 02:29:15 cmp02 kernel: [11563.138237]  connection2:0: detected conn error (1020)
May 10 02:29:18 cmp02 kernel: [11566.147789]  connection2:0: detected conn error (1020)
May 10 02:29:21 cmp02 kernel: [11569.158641]  connection2:0: detected conn error (1020)
May 10 02:29:24 cmp02 kernel: [11572.168298]  connection2:0: detected conn error (1020)
May 10 02:29:27 cmp02 kernel: [11575.173130]  connection2:0: detected conn error (1020)
May 10 02:29:30 cmp02 kernel: [11578.182506]  connection2:0: detected conn error (1020)
May 10 02:29:33 cmp02 kernel: [11581.192985]  connection2:0: detected conn error (1020)
May 10 02:29:33 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:29:36 cmp02 kernel: [11584.200287]  connection2:0: detected conn error (1020)
May 10 02:29:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:29:39 cmp02 kernel: [11587.206318]  connection2:0: detected conn error (1020)
May 10 02:29:42 cmp02 kernel: [11590.213787]  connection2:0: detected conn error (1020)
May 10 02:29:45 cmp02 kernel: [11593.223793]  connection2:0: detected conn error (1020)
May 10 02:29:48 cmp02 kernel: [11596.235352]  connection2:0: detected conn error (1020)
May 10 02:29:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:29:48 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 02:29:48 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 02:29:48 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1277 seconds.
May 10 02:29:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:29:51 cmp02 kernel: [11599.244749]  connection2:0: detected conn error (1020)
May 10 02:29:54 cmp02 kernel: [11602.253325]  connection2:0: detected conn error (1020)
May 10 02:29:57 cmp02 kernel: [11605.263536]  connection2:0: detected conn error (1020)
May 10 02:30:00 cmp02 kernel: [11608.270830]  connection2:0: detected conn error (1020)
May 10 02:30:03 cmp02 kernel: [11611.277607]  connection2:0: detected conn error (1020)
May 10 02:30:06 cmp02 kernel: [11614.286657]  connection2:0: detected conn error (1020)
May 10 02:30:09 cmp02 kernel: [11617.293034]  connection2:0: detected conn error (1020)
May 10 02:30:09 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:30:12 cmp02 kernel: [11620.301705]  connection2:0: detected conn error (1020)
May 10 02:30:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:30:15 cmp02 kernel: [11623.306744]  connection2:0: detected conn error (1020)
May 10 02:30:18 cmp02 kernel: [11626.313772]  connection2:0: detected conn error (1020)
May 10 02:30:21 cmp02 kernel: [11629.323878]  connection2:0: detected conn error (1020)
May 10 02:30:24 cmp02 kernel: [11632.333617]  connection2:0: detected conn error (1020)
May 10 02:30:27 cmp02 kernel: [11635.342262]  connection2:0: detected conn error (1020)
May 10 02:30:30 cmp02 kernel: [11638.350232]  connection2:0: detected conn error (1020)
May 10 02:30:33 cmp02 kernel: [11641.356412]  connection2:0: detected conn error (1020)
May 10 02:30:33 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:30:36 cmp02 kernel: [11644.365872]  connection2:0: detected conn error (1020)
May 10 02:30:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:30:39 cmp02 kernel: [11647.372413]  connection2:0: detected conn error (1020)
May 10 02:30:42 cmp02 kernel: [11650.379467]  connection2:0: detected conn error (1020)
May 10 02:30:45 cmp02 kernel: [11653.384657]  connection2:0: detected conn error (1020)
May 10 02:30:48 cmp02 kernel: [11656.392170]  connection2:0: detected conn error (1020)
May 10 02:30:51 cmp02 kernel: [11659.400206]  connection2:0: detected conn error (1020)
May 10 02:30:54 cmp02 kernel: [11662.412719]  connection2:0: detected conn error (1020)
May 10 02:30:57 cmp02 kernel: [11665.418741]  connection2:0: detected conn error (1020)
May 10 02:31:00 cmp02 kernel: [11668.427696]  connection2:0: detected conn error (1020)
May 10 02:31:03 cmp02 kernel: [11671.437404]  connection2:0: detected conn error (1020)
May 10 02:31:06 cmp02 kernel: [11674.444633]  connection2:0: detected conn error (1020)
May 10 02:31:09 cmp02 kernel: [11677.455835]  connection2:0: detected conn error (1020)
May 10 02:31:09 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:31:12 cmp02 kernel: [11680.460152]  connection2:0: detected conn error (1020)
May 10 02:31:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:31:15 cmp02 kernel: [11683.470866]  connection2:0: detected conn error (1020)
May 10 02:31:15 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:31:18 cmp02 kernel: [11686.480247]  connection2:0: detected conn error (1020)
May 10 02:31:21 cmp02 kernel: [11689.486979]  connection2:0: detected conn error (1020)
May 10 02:31:24 cmp02 kernel: [11692.517486]  connection2:0: detected conn error (1020)
May 10 02:31:27 cmp02 kernel: [11695.525351]  connection2:0: detected conn error (1020)
May 10 02:31:30 cmp02 kernel: [11698.535765]  connection2:0: detected conn error (1020)
May 10 02:31:33 cmp02 kernel: [11701.547116]  connection2:0: detected conn error (1020)
May 10 02:31:33 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:31:36 cmp02 kernel: [11704.555544]  connection2:0: detected conn error (1020)
May 10 02:31:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:31:39 cmp02 kernel: [11707.574765]  connection2:0: detected conn error (1020)
May 10 02:31:42 cmp02 kernel: [11710.582386]  connection2:0: detected conn error (1020)
May 10 02:31:45 cmp02 kernel: [11713.590745]  connection2:0: detected conn error (1020)
May 10 02:31:48 cmp02 kernel: [11716.601700]  connection2:0: detected conn error (1020)
May 10 02:31:51 cmp02 kernel: [11719.607158]  connection2:0: detected conn error (1020)
May 10 02:31:54 cmp02 kernel: [11722.622583]  connection2:0: detected conn error (1020)
May 10 02:31:57 cmp02 kernel: [11725.627985]  connection2:0: detected conn error (1020)
May 10 02:32:00 cmp02 kernel: [11728.634706]  connection2:0: detected conn error (1020)
May 10 02:32:03 cmp02 kernel: [11731.641409]  connection2:0: detected conn error (1020)
May 10 02:32:05 cmp02 kernel: [11733.264468] device tap57c2fdea-b9 left promiscuous mode
May 10 02:32:05 cmp02 kernel: [11733.832186] audit: type=1400 audit(1525919525.818:307): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-5e7343f1-cd07-4efc-8ee9-e7f651f3b75f" pid=29809 comm="apparmor_parser"
May 10 02:32:03 cmp02 iscsid: message repeated 9 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:32:05 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap57c2fdea-b9
May 10 02:32:06 cmp02 kernel: [11734.648495]  connection2:0: detected conn error (1020)
May 10 02:32:06 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:09 cmp02 kernel: [11737.654494]  connection2:0: detected conn error (1020)
May 10 02:32:09 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:12 cmp02 kernel: [11740.660695]  connection2:0: detected conn error (1020)
May 10 02:32:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:15 cmp02 kernel: [11743.669990]  connection2:0: detected conn error (1020)
May 10 02:32:15 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:18 cmp02 kernel: [11746.679084]  connection2:0: detected conn error (1020)
May 10 02:32:21 cmp02 kernel: [11749.688848]  connection2:0: detected conn error (1020)
May 10 02:32:24 cmp02 kernel: [11752.697612]  connection2:0: detected conn error (1020)
May 10 02:32:27 cmp02 kernel: [11755.704199]  connection2:0: detected conn error (1020)
May 10 02:32:30 cmp02 kernel: [11758.710428]  connection2:0: detected conn error (1020)
May 10 02:32:33 cmp02 kernel: [11761.723215]  connection2:0: detected conn error (1020)
May 10 02:32:30 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:32:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:36 cmp02 kernel: [11764.730085]  connection2:0: detected conn error (1020)
May 10 02:32:39 cmp02 kernel: [11767.735278]  connection2:0: detected conn error (1020)
May 10 02:32:42 cmp02 kernel: [11770.742256]  connection2:0: detected conn error (1020)
May 10 02:32:40 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:32:43 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:45 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 02:32:45 cmp02 kernel: [11773.748544]  connection2:0: detected conn error (1020)
May 10 02:32:46 cmp02 kernel: [11774.554434] audit: type=1400 audit(1525919566.539:308): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-97dd54f5-50ba-44d3-9556-6b9067e69bcf" pid=29947 comm="apparmor_parser"
May 10 02:32:46 cmp02 kernel: [11774.796157] audit: type=1400 audit(1525919566.781:309): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-97dd54f5-50ba-44d3-9556-6b9067e69bcf" pid=29950 comm="apparmor_parser"
May 10 02:32:46 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:47 cmp02 kernel: [11775.035309] audit: type=1400 audit(1525919567.020:310): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-97dd54f5-50ba-44d3-9556-6b9067e69bcf" pid=29953 comm="apparmor_parser"
May 10 02:32:47 cmp02 kernel: [11775.280405] audit: type=1400 audit(1525919567.265:311): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-97dd54f5-50ba-44d3-9556-6b9067e69bcf" pid=29956 comm="apparmor_parser"
May 10 02:32:47 cmp02 systemd-udevd[29959]: Could not generate persistent MAC address for tapaed0df75-3d: No such file or directory
May 10 02:32:47 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapaed0df75-3d -- add-port br-int tapaed0df75-3d -- set Interface tapaed0df75-3d "external-ids:attached-mac=\"fa:16:3e:b1:08:6d\"" -- set Interface tapaed0df75-3d "external-ids:iface-id=\"aed0df75-3d51-466c-bf16-46a909ec46da\"" -- set Interface tapaed0df75-3d "external-ids:vm-id=\"97dd54f5-50ba-44d3-9556-6b9067e69bcf\"" -- set Interface tapaed0df75-3d external-ids:iface-status=active
May 10 02:32:47 cmp02 kernel: [11775.313805] device tapaed0df75-3d entered promiscuous mode
May 10 02:32:47 cmp02 kernel: [11775.569553] audit: type=1400 audit(1525919567.554:312): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-97dd54f5-50ba-44d3-9556-6b9067e69bcf" pid=30061 comm="apparmor_parser"
May 10 02:32:47 cmp02 libvirtd[5599]: 2018-05-10 02:32:47.561+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=48 name='instance-00000068' uuid=97dd54f5-50ba-44d3-9556-6b9067e69bcf is tainted: host-cpu
May 10 02:32:48 cmp02 kernel: [11776.754366]  connection2:0: detected conn error (1020)
May 10 02:32:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:32:51 cmp02 kernel: [11779.760668]  connection2:0: detected conn error (1020)
May 10 02:32:54 cmp02 kernel: [11782.768478]  connection2:0: detected conn error (1020)
May 10 02:32:57 cmp02 kernel: [11785.776385]  connection2:0: detected conn error (1020)
May 10 02:33:00 cmp02 kernel: [11788.782422]  connection2:0: detected conn error (1020)
May 10 02:33:03 cmp02 kernel: [11791.786416]  connection2:0: detected conn error (1020)
May 10 02:33:06 cmp02 kernel: [11794.791705]  connection2:0: detected conn error (1020)
May 10 02:33:09 cmp02 kernel: [11797.795860]  connection2:0: detected conn error (1020)
May 10 02:33:12 cmp02 kernel: [11800.802143]  connection2:0: detected conn error (1020)
May 10 02:33:10 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:33:13 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:33:15 cmp02 kernel: [11803.806904]  connection2:0: detected conn error (1020)
May 10 02:33:16 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:33:18 cmp02 kernel: [11806.813689]  connection2:0: detected conn error (1020)
May 10 02:33:21 cmp02 kernel: [11809.820197]  connection2:0: detected conn error (1020)
May 10 02:33:24 cmp02 kernel: [11812.826529]  connection2:0: detected conn error (1020)
May 10 02:33:27 cmp02 kernel: [11815.830907]  connection2:0: detected conn error (1020)
May 10 02:33:30 cmp02 kernel: [11818.836551]  connection2:0: detected conn error (1020)
May 10 02:33:33 cmp02 kernel: [11821.843518]  connection2:0: detected conn error (1020)
May 10 02:33:31 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:33:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:33:36 cmp02 kernel: [11824.847669]  connection2:0: detected conn error (1020)
May 10 02:33:39 cmp02 kernel: [11827.851581]  connection2:0: detected conn error (1020)
May 10 02:33:42 cmp02 kernel: [11830.857217]  connection2:0: detected conn error (1020)
May 10 02:33:45 cmp02 kernel: [11833.864633]  connection2:0: detected conn error (1020)
May 10 02:33:48 cmp02 kernel: [11836.870143]  connection2:0: detected conn error (1020)
May 10 02:33:51 cmp02 kernel: [11839.886261]  connection2:0: detected conn error (1020)
May 10 02:33:54 cmp02 kernel: [11842.894047]  connection2:0: detected conn error (1020)
May 10 02:33:57 cmp02 kernel: [11845.902738]  connection2:0: detected conn error (1020)
May 10 02:34:00 cmp02 kernel: [11848.910504]  connection2:0: detected conn error (1020)
May 10 02:34:03 cmp02 kernel: [11851.917157]  connection2:0: detected conn error (1020)
May 10 02:34:06 cmp02 kernel: [11854.924177]  connection2:0: detected conn error (1020)
May 10 02:34:09 cmp02 kernel: [11857.933644]  connection2:0: detected conn error (1020)
May 10 02:34:12 cmp02 kernel: [11860.942868]  connection2:0: detected conn error (1020)
May 10 02:34:13 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:34:15 cmp02 kernel: [11863.950970]  connection2:0: detected conn error (1020)
May 10 02:34:16 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:34:18 cmp02 kernel: [11866.956523]  connection2:0: detected conn error (1020)
May 10 02:34:21 cmp02 kernel: [11869.964756]  connection2:0: detected conn error (1020)
May 10 02:34:24 cmp02 kernel: [11872.974956]  connection2:0: detected conn error (1020)
May 10 02:34:27 cmp02 kernel: [11875.985425]  connection2:0: detected conn error (1020)
May 10 02:34:30 cmp02 kernel: [11878.994458]  connection2:0: detected conn error (1020)
May 10 02:34:33 cmp02 kernel: [11882.003254]  connection2:0: detected conn error (1020)
May 10 02:34:31 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:34:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:34:37 cmp02 kernel: [11885.014113]  connection2:0: detected conn error (1020)
May 10 02:34:40 cmp02 kernel: [11888.019399]  connection2:0: detected conn error (1020)
May 10 02:34:43 cmp02 kernel: [11891.026000]  connection2:0: detected conn error (1020)
May 10 02:34:46 cmp02 kernel: [11894.036361]  connection2:0: detected conn error (1020)
May 10 02:34:49 cmp02 kernel: [11897.043376]  connection2:0: detected conn error (1020)
May 10 02:34:52 cmp02 kernel: [11900.052561]  connection2:0: detected conn error (1020)
May 10 02:34:55 cmp02 kernel: [11903.061862]  connection2:0: detected conn error (1020)
May 10 02:34:58 cmp02 kernel: [11906.073639]  connection2:0: detected conn error (1020)
May 10 02:35:01 cmp02 kernel: [11909.084467]  connection2:0: detected conn error (1020)
May 10 02:35:04 cmp02 kernel: [11912.092313]  connection2:0: detected conn error (1020)
May 10 02:35:07 cmp02 kernel: [11915.099280]  connection2:0: detected conn error (1020)
May 10 02:35:10 cmp02 kernel: [11918.108631]  connection2:0: detected conn error (1020)
May 10 02:35:13 cmp02 kernel: [11921.117155]  connection2:0: detected conn error (1020)
May 10 02:35:16 cmp02 kernel: [11924.128114]  connection2:0: detected conn error (1020)
May 10 02:35:14 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:35:17 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:35:19 cmp02 kernel: [11927.134397]  connection2:0: detected conn error (1020)
May 10 02:35:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:35:22 cmp02 kernel: [11930.138937]  connection2:0: detected conn error (1020)
May 10 02:35:25 cmp02 kernel: [11933.147353]  connection2:0: detected conn error (1020)
May 10 02:35:28 cmp02 kernel: [11936.157329]  connection2:0: detected conn error (1020)
May 10 02:35:31 cmp02 kernel: [11939.167159]  connection2:0: detected conn error (1020)
May 10 02:35:34 cmp02 kernel: [11942.179228]  connection2:0: detected conn error (1020)
May 10 02:35:32 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:35:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:35:37 cmp02 kernel: [11945.186497]  connection2:0: detected conn error (1020)
May 10 02:35:40 cmp02 kernel: [11948.195903]  connection2:0: detected conn error (1020)
May 10 02:35:43 cmp02 kernel: [11951.205719]  connection2:0: detected conn error (1020)
May 10 02:35:46 cmp02 kernel: [11954.210506]  connection2:0: detected conn error (1020)
May 10 02:35:49 cmp02 kernel: [11957.218711]  connection2:0: detected conn error (1020)
May 10 02:35:52 cmp02 kernel: [11960.231328]  connection2:0: detected conn error (1020)
May 10 02:35:55 cmp02 kernel: [11963.242235]  connection2:0: detected conn error (1020)
May 10 02:35:58 cmp02 kernel: [11966.251263]  connection2:0: detected conn error (1020)
May 10 02:36:01 cmp02 kernel: [11969.261128]  connection2:0: detected conn error (1020)
May 10 02:36:04 cmp02 kernel: [11972.267467]  connection2:0: detected conn error (1020)
May 10 02:36:07 cmp02 kernel: [11975.277016]  connection2:0: detected conn error (1020)
May 10 02:36:10 cmp02 kernel: [11978.284486]  connection2:0: detected conn error (1020)
May 10 02:36:13 cmp02 kernel: [11981.291743]  connection2:0: detected conn error (1020)
May 10 02:36:16 cmp02 kernel: [11984.298636]  connection2:0: detected conn error (1020)
May 10 02:36:17 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:36:19 cmp02 kernel: [11987.305244]  connection2:0: detected conn error (1020)
May 10 02:36:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:36:22 cmp02 kernel: [11990.315711]  connection2:0: detected conn error (1020)
May 10 02:36:25 cmp02 kernel: [11993.322623]  connection2:0: detected conn error (1020)
May 10 02:36:28 cmp02 kernel: [11996.331879]  connection2:0: detected conn error (1020)
May 10 02:36:31 cmp02 kernel: [11999.342905]  connection2:0: detected conn error (1020)
May 10 02:36:34 cmp02 kernel: [12002.353055]  connection2:0: detected conn error (1020)
May 10 02:36:32 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:36:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:36:37 cmp02 kernel: [12005.362421]  connection2:0: detected conn error (1020)
May 10 02:36:40 cmp02 kernel: [12008.367689]  connection2:0: detected conn error (1020)
May 10 02:36:43 cmp02 kernel: [12011.375987]  connection2:0: detected conn error (1020)
May 10 02:36:46 cmp02 kernel: [12014.383665]  connection2:0: detected conn error (1020)
May 10 02:36:49 cmp02 kernel: [12017.391889]  connection2:0: detected conn error (1020)
May 10 02:36:52 cmp02 kernel: [12020.399534]  connection2:0: detected conn error (1020)
May 10 02:36:55 cmp02 kernel: [12023.406104]  connection2:0: detected conn error (1020)
May 10 02:36:58 cmp02 kernel: [12026.415962]  connection2:0: detected conn error (1020)
May 10 02:37:01 cmp02 kernel: [12029.423659]  connection2:0: detected conn error (1020)
May 10 02:37:04 cmp02 kernel: [12032.431089]  connection2:0: detected conn error (1020)
May 10 02:37:07 cmp02 kernel: [12035.441760]  connection2:0: detected conn error (1020)
May 10 02:37:10 cmp02 kernel: [12038.452239]  connection2:0: detected conn error (1020)
May 10 02:37:13 cmp02 kernel: [12041.459731]  connection2:0: detected conn error (1020)
May 10 02:37:16 cmp02 kernel: [12044.467797]  connection2:0: detected conn error (1020)
May 10 02:37:17 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:37:19 cmp02 kernel: [12047.477340]  connection2:0: detected conn error (1020)
May 10 02:37:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:37:22 cmp02 kernel: [12050.482511]  connection2:0: detected conn error (1020)
May 10 02:37:25 cmp02 kernel: [12053.490053]  connection2:0: detected conn error (1020)
May 10 02:37:28 cmp02 kernel: [12056.498197]  connection2:0: detected conn error (1020)
May 10 02:37:31 cmp02 kernel: [12059.506533]  connection2:0: detected conn error (1020)
May 10 02:37:34 cmp02 kernel: [12062.514293]  connection2:0: detected conn error (1020)
May 10 02:37:32 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:37:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:37:37 cmp02 kernel: [12065.523302]  connection2:0: detected conn error (1020)
May 10 02:37:40 cmp02 kernel: [12068.532883]  connection2:0: detected conn error (1020)
May 10 02:37:43 cmp02 kernel: [12071.544139]  connection2:0: detected conn error (1020)
May 10 02:37:46 cmp02 kernel: [12074.559105]  connection2:0: detected conn error (1020)
May 10 02:37:49 cmp02 kernel: [12077.566579]  connection2:0: detected conn error (1020)
May 10 02:37:52 cmp02 kernel: [12080.574366]  connection2:0: detected conn error (1020)
May 10 02:37:55 cmp02 kernel: [12083.582250]  connection2:0: detected conn error (1020)
May 10 02:37:58 cmp02 kernel: [12086.588241]  connection2:0: detected conn error (1020)
May 10 02:38:01 cmp02 kernel: [12089.594868]  connection2:0: detected conn error (1020)
May 10 02:38:04 cmp02 kernel: [12092.600886]  connection2:0: detected conn error (1020)
May 10 02:38:07 cmp02 kernel: [12095.608990]  connection2:0: detected conn error (1020)
May 10 02:38:10 cmp02 kernel: [12098.615544]  connection2:0: detected conn error (1020)
May 10 02:38:13 cmp02 kernel: [12101.622261]  connection2:0: detected conn error (1020)
May 10 02:38:16 cmp02 kernel: [12104.628877]  connection2:0: detected conn error (1020)
May 10 02:38:17 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:38:19 cmp02 kernel: [12107.634057]  connection2:0: detected conn error (1020)
May 10 02:38:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:38:22 cmp02 kernel: [12110.640216]  connection2:0: detected conn error (1020)
May 10 02:38:25 cmp02 kernel: [12113.648248]  connection2:0: detected conn error (1020)
May 10 02:38:28 cmp02 kernel: [12116.655912]  connection2:0: detected conn error (1020)
May 10 02:38:31 cmp02 kernel: [12119.661714]  connection2:0: detected conn error (1020)
May 10 02:38:32 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:38:34 cmp02 kernel: [12122.669039]  connection2:0: detected conn error (1020)
May 10 02:38:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:38:37 cmp02 kernel: [12125.679521]  connection2:0: detected conn error (1020)
May 10 02:38:40 cmp02 kernel: [12128.688950]  connection2:0: detected conn error (1020)
May 10 02:38:43 cmp02 kernel: [12131.702388]  connection2:0: detected conn error (1020)
May 10 02:38:46 cmp02 kernel: [12134.710643]  connection2:0: detected conn error (1020)
May 10 02:38:49 cmp02 kernel: [12137.717941]  connection2:0: detected conn error (1020)
May 10 02:38:52 cmp02 kernel: [12140.725110]  connection2:0: detected conn error (1020)
May 10 02:38:55 cmp02 kernel: [12143.733096]  connection2:0: detected conn error (1020)
May 10 02:38:58 cmp02 kernel: [12146.741460]  connection2:0: detected conn error (1020)
May 10 02:39:01 cmp02 kernel: [12149.749356]  connection2:0: detected conn error (1020)
May 10 02:39:04 cmp02 kernel: [12152.755932]  connection2:0: detected conn error (1020)
May 10 02:39:07 cmp02 kernel: [12155.761858]  connection2:0: detected conn error (1020)
May 10 02:39:10 cmp02 kernel: [12158.769087]  connection2:0: detected conn error (1020)
May 10 02:39:13 cmp02 kernel: [12161.777537]  connection2:0: detected conn error (1020)
May 10 02:39:16 cmp02 kernel: [12164.788132]  connection2:0: detected conn error (1020)
May 10 02:39:17 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:39:19 cmp02 kernel: [12167.795035]  connection2:0: detected conn error (1020)
May 10 02:39:20 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:39:22 cmp02 kernel: [12170.801256]  connection2:0: detected conn error (1020)
May 10 02:39:23 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:39:25 cmp02 kernel: [12173.807275]  connection2:0: detected conn error (1020)
May 10 02:39:28 cmp02 kernel: [12176.814679]  connection2:0: detected conn error (1020)
May 10 02:39:31 cmp02 kernel: [12179.822003]  connection2:0: detected conn error (1020)
May 10 02:39:32 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:39:34 cmp02 kernel: [12182.831242]  connection2:0: detected conn error (1020)
May 10 02:39:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:39:37 cmp02 kernel: [12185.842742]  connection2:0: detected conn error (1020)
May 10 02:39:40 cmp02 kernel: [12188.853097]  connection2:0: detected conn error (1020)
May 10 02:39:43 cmp02 kernel: [12191.865567]  connection2:0: detected conn error (1020)
May 10 02:39:46 cmp02 kernel: [12194.873768]  connection2:0: detected conn error (1020)
May 10 02:39:49 cmp02 kernel: [12197.883167]  connection2:0: detected conn error (1020)
May 10 02:39:52 cmp02 kernel: [12200.891808]  connection2:0: detected conn error (1020)
May 10 02:39:55 cmp02 kernel: [12203.903375]  connection2:0: detected conn error (1020)
May 10 02:39:58 cmp02 kernel: [12206.916445]  connection2:0: detected conn error (1020)
May 10 02:40:01 cmp02 kernel: [12209.928361]  connection2:0: detected conn error (1020)
May 10 02:40:04 cmp02 kernel: [12212.937745]  connection2:0: detected conn error (1020)
May 10 02:40:07 cmp02 kernel: [12215.946156]  connection2:0: detected conn error (1020)
May 10 02:40:10 cmp02 kernel: [12218.952216]  connection2:0: detected conn error (1020)
May 10 02:40:13 cmp02 kernel: [12221.962271]  connection2:0: detected conn error (1020)
May 10 02:40:16 cmp02 kernel: [12224.973683]  connection2:0: detected conn error (1020)
May 10 02:40:19 cmp02 kernel: [12227.985343]  connection2:0: detected conn error (1020)
May 10 02:40:21 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:40:22 cmp02 kernel: [12230.994110]  connection2:0: detected conn error (1020)
May 10 02:40:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:40:25 cmp02 kernel: [12234.000634]  connection2:0: detected conn error (1020)
May 10 02:40:28 cmp02 kernel: [12237.008011]  connection2:0: detected conn error (1020)
May 10 02:40:31 cmp02 kernel: [12240.014713]  connection2:0: detected conn error (1020)
May 10 02:40:33 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:40:35 cmp02 kernel: [12243.032422]  connection2:0: detected conn error (1020)
May 10 02:40:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:40:38 cmp02 kernel: [12246.038875]  connection2:0: detected conn error (1020)
May 10 02:40:41 cmp02 kernel: [12249.048083]  connection2:0: detected conn error (1020)
May 10 02:40:44 cmp02 kernel: [12252.057523]  connection2:0: detected conn error (1020)
May 10 02:40:47 cmp02 kernel: [12255.065152]  connection2:0: detected conn error (1020)
May 10 02:40:50 cmp02 kernel: [12258.071814]  connection2:0: detected conn error (1020)
May 10 02:40:53 cmp02 kernel: [12261.079559]  connection2:0: detected conn error (1020)
May 10 02:40:56 cmp02 kernel: [12264.087140]  connection2:0: detected conn error (1020)
May 10 02:40:59 cmp02 kernel: [12267.094565]  connection2:0: detected conn error (1020)
May 10 02:41:02 cmp02 kernel: [12270.101563]  connection2:0: detected conn error (1020)
May 10 02:41:05 cmp02 kernel: [12273.110148]  connection2:0: detected conn error (1020)
May 10 02:41:08 cmp02 kernel: [12276.117791]  connection2:0: detected conn error (1020)
May 10 02:41:11 cmp02 kernel: [12279.131707]  connection2:0: detected conn error (1020)
May 10 02:41:14 cmp02 kernel: [12282.142928]  connection2:0: detected conn error (1020)
May 10 02:41:17 cmp02 kernel: [12285.155740]  connection2:0: detected conn error (1020)
May 10 02:41:20 cmp02 kernel: [12288.164559]  connection2:0: detected conn error (1020)
May 10 02:41:21 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:41:23 cmp02 kernel: [12291.172726]  connection2:0: detected conn error (1020)
May 10 02:41:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:41:26 cmp02 kernel: [12294.179061]  connection2:0: detected conn error (1020)
May 10 02:41:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:41:29 cmp02 kernel: [12297.187486]  connection2:0: detected conn error (1020)
May 10 02:41:32 cmp02 kernel: [12300.212620]  connection2:0: detected conn error (1020)
May 10 02:41:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:41:35 cmp02 kernel: [12303.220618]  connection2:0: detected conn error (1020)
May 10 02:41:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:41:38 cmp02 kernel: [12306.237883]  connection2:0: detected conn error (1020)
May 10 02:41:41 cmp02 kernel: [12309.248393]  connection2:0: detected conn error (1020)
May 10 02:41:44 cmp02 kernel: [12312.257129]  connection2:0: detected conn error (1020)
May 10 02:41:47 cmp02 kernel: [12315.264510]  connection2:0: detected conn error (1020)
May 10 02:41:50 cmp02 kernel: [12318.272503]  connection2:0: detected conn error (1020)
May 10 02:41:53 cmp02 kernel: [12321.278807]  connection2:0: detected conn error (1020)
May 10 02:41:56 cmp02 kernel: [12324.288421]  connection2:0: detected conn error (1020)
May 10 02:41:59 cmp02 kernel: [12327.296641]  connection2:0: detected conn error (1020)
May 10 02:42:02 cmp02 kernel: [12330.303891]  connection2:0: detected conn error (1020)
May 10 02:42:05 cmp02 kernel: [12333.311079]  connection2:0: detected conn error (1020)
May 10 02:42:08 cmp02 kernel: [12336.317093]  connection2:0: detected conn error (1020)
May 10 02:42:11 cmp02 kernel: [12339.325279]  connection2:0: detected conn error (1020)
May 10 02:42:14 cmp02 kernel: [12342.332500]  connection2:0: detected conn error (1020)
May 10 02:42:17 cmp02 kernel: [12345.342032]  connection2:0: detected conn error (1020)
May 10 02:42:20 cmp02 kernel: [12348.348788]  connection2:0: detected conn error (1020)
May 10 02:42:21 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:42:23 cmp02 kernel: [12351.357507]  connection2:0: detected conn error (1020)
May 10 02:42:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:42:26 cmp02 kernel: [12354.364704]  connection2:0: detected conn error (1020)
May 10 02:42:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:42:29 cmp02 kernel: [12357.375180]  connection2:0: detected conn error (1020)
May 10 02:42:32 cmp02 kernel: [12360.381753]  connection2:0: detected conn error (1020)
May 10 02:42:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:42:35 cmp02 kernel: [12363.387299]  connection2:0: detected conn error (1020)
May 10 02:42:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:42:38 cmp02 kernel: [12366.397345]  connection2:0: detected conn error (1020)
May 10 02:42:41 cmp02 kernel: [12369.406192]  connection2:0: detected conn error (1020)
May 10 02:42:44 cmp02 kernel: [12372.420601]  connection2:0: detected conn error (1020)
May 10 02:42:47 cmp02 kernel: [12375.428862]  connection2:0: detected conn error (1020)
May 10 02:42:50 cmp02 kernel: [12378.433543]  connection2:0: detected conn error (1020)
May 10 02:42:53 cmp02 kernel: [12381.440496]  connection2:0: detected conn error (1020)
May 10 02:42:56 cmp02 kernel: [12384.449572]  connection2:0: detected conn error (1020)
May 10 02:42:59 cmp02 kernel: [12387.455618]  connection2:0: detected conn error (1020)
May 10 02:43:02 cmp02 kernel: [12390.464806]  connection2:0: detected conn error (1020)
May 10 02:43:05 cmp02 kernel: [12393.471968]  connection2:0: detected conn error (1020)
May 10 02:43:08 cmp02 kernel: [12396.479666]  connection2:0: detected conn error (1020)
May 10 02:43:08 cmp02 kernel: [12396.884091] device tapaed0df75-3d left promiscuous mode
May 10 02:43:09 cmp02 kernel: [12397.257929] audit: type=1400 audit(1525920189.232:313): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-97dd54f5-50ba-44d3-9556-6b9067e69bcf" pid=31038 comm="apparmor_parser"
May 10 02:43:09 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:43:09 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapaed0df75-3d
May 10 02:43:11 cmp02 kernel: [12399.486662]  connection2:0: detected conn error (1020)
May 10 02:43:12 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:43:14 cmp02 kernel: [12402.493085]  connection2:0: detected conn error (1020)
May 10 02:43:17 cmp02 kernel: [12405.499378]  connection2:0: detected conn error (1020)
May 10 02:43:20 cmp02 kernel: [12408.507296]  connection2:0: detected conn error (1020)
May 10 02:43:23 cmp02 kernel: [12411.516477]  connection2:0: detected conn error (1020)
May 10 02:43:21 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:43:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:43:26 cmp02 kernel: [12414.522657]  connection2:0: detected conn error (1020)
May 10 02:43:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:43:29 cmp02 kernel: [12417.531073]  connection2:0: detected conn error (1020)
May 10 02:43:32 cmp02 kernel: [12420.536604]  connection2:0: detected conn error (1020)
May 10 02:43:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:43:35 cmp02 kernel: [12423.544889]  connection2:0: detected conn error (1020)
May 10 02:43:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:43:38 cmp02 kernel: [12426.550351]  connection2:0: detected conn error (1020)
May 10 02:43:41 cmp02 kernel: [12429.556737]  connection2:0: detected conn error (1020)
May 10 02:43:44 cmp02 kernel: [12432.562614]  connection2:0: detected conn error (1020)
May 10 02:43:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:43:47 cmp02 kernel: [12435.568960]  connection2:0: detected conn error (1020)
May 10 02:43:47 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 02:43:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:43:48 cmp02 kernel: [12436.879218] audit: type=1400 audit(1525920228.852:314): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-92c7fbad-edf1-4bee-b7ee-404df52d6012" pid=31176 comm="apparmor_parser"
May 10 02:43:49 cmp02 kernel: [12437.125256] audit: type=1400 audit(1525920229.098:315): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-92c7fbad-edf1-4bee-b7ee-404df52d6012" pid=31179 comm="apparmor_parser"
May 10 02:43:49 cmp02 kernel: [12437.368777] audit: type=1400 audit(1525920229.342:316): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-92c7fbad-edf1-4bee-b7ee-404df52d6012" pid=31182 comm="apparmor_parser"
May 10 02:43:49 cmp02 kernel: [12437.608231] audit: type=1400 audit(1525920229.581:317): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-92c7fbad-edf1-4bee-b7ee-404df52d6012" pid=31185 comm="apparmor_parser"
May 10 02:43:49 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap89d26cad-bc -- add-port br-int tap89d26cad-bc -- set Interface tap89d26cad-bc "external-ids:attached-mac=\"fa:16:3e:01:e2:7f\"" -- set Interface tap89d26cad-bc "external-ids:iface-id=\"89d26cad-bcbe-4d59-b44f-6ff9d6ba6cc4\"" -- set Interface tap89d26cad-bc "external-ids:vm-id=\"92c7fbad-edf1-4bee-b7ee-404df52d6012\"" -- set Interface tap89d26cad-bc external-ids:iface-status=active
May 10 02:43:49 cmp02 kernel: [12437.639809] device tap89d26cad-bc entered promiscuous mode
May 10 02:43:49 cmp02 kernel: [12437.894819] audit: type=1400 audit(1525920229.868:318): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-92c7fbad-edf1-4bee-b7ee-404df52d6012" pid=31254 comm="apparmor_parser"
May 10 02:43:49 cmp02 libvirtd[5599]: 2018-05-10 02:43:49.876+0000: 5612: warning : qemuDomainObjTaint:5532 : Domain id=49 name='instance-0000006a' uuid=92c7fbad-edf1-4bee-b7ee-404df52d6012 is tainted: host-cpu
May 10 02:43:50 cmp02 kernel: [12438.574043]  connection2:0: detected conn error (1020)
May 10 02:43:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:43:53 cmp02 kernel: [12441.579466]  connection2:0: detected conn error (1020)
May 10 02:43:56 cmp02 kernel: [12444.585950]  connection2:0: detected conn error (1020)
May 10 02:43:59 cmp02 kernel: [12447.593071]  connection2:0: detected conn error (1020)
May 10 02:44:02 cmp02 kernel: [12450.599153]  connection2:0: detected conn error (1020)
May 10 02:44:05 cmp02 kernel: [12453.607790]  connection2:0: detected conn error (1020)
May 10 02:44:08 cmp02 kernel: [12456.615022]  connection2:0: detected conn error (1020)
May 10 02:44:11 cmp02 kernel: [12459.623217]  connection2:0: detected conn error (1020)
May 10 02:44:14 cmp02 kernel: [12462.628513]  connection2:0: detected conn error (1020)
May 10 02:44:17 cmp02 kernel: [12465.635045]  connection2:0: detected conn error (1020)
May 10 02:44:20 cmp02 kernel: [12468.641613]  connection2:0: detected conn error (1020)
May 10 02:44:23 cmp02 kernel: [12471.647689]  connection2:0: detected conn error (1020)
May 10 02:44:21 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:44:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:44:26 cmp02 kernel: [12474.654636]  connection2:0: detected conn error (1020)
May 10 02:44:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:44:29 cmp02 kernel: [12477.666549]  connection2:0: detected conn error (1020)
May 10 02:44:32 cmp02 kernel: [12480.672497]  connection2:0: detected conn error (1020)
May 10 02:44:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:44:35 cmp02 kernel: [12483.678171]  connection2:0: detected conn error (1020)
May 10 02:44:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:44:38 cmp02 kernel: [12486.686295]  connection2:0: detected conn error (1020)
May 10 02:44:41 cmp02 kernel: [12489.691165]  connection2:0: detected conn error (1020)
May 10 02:44:44 cmp02 kernel: [12492.700118]  connection2:0: detected conn error (1020)
May 10 02:44:47 cmp02 kernel: [12495.709911]  connection2:0: detected conn error (1020)
May 10 02:44:50 cmp02 kernel: [12498.719723]  connection2:0: detected conn error (1020)
May 10 02:44:53 cmp02 kernel: [12501.727676]  connection2:0: detected conn error (1020)
May 10 02:44:56 cmp02 kernel: [12504.737178]  connection2:0: detected conn error (1020)
May 10 02:44:59 cmp02 kernel: [12507.746245]  connection2:0: detected conn error (1020)
May 10 02:45:02 cmp02 kernel: [12510.758457]  connection2:0: detected conn error (1020)
May 10 02:45:05 cmp02 kernel: [12513.768490]  connection2:0: detected conn error (1020)
May 10 02:45:08 cmp02 kernel: [12516.779368]  connection2:0: detected conn error (1020)
May 10 02:45:11 cmp02 kernel: [12519.791753]  connection2:0: detected conn error (1020)
May 10 02:45:14 cmp02 kernel: [12522.800067]  connection2:0: detected conn error (1020)
May 10 02:45:17 cmp02 kernel: [12525.807067]  connection2:0: detected conn error (1020)
May 10 02:45:20 cmp02 kernel: [12528.813500]  connection2:0: detected conn error (1020)
May 10 02:45:23 cmp02 kernel: [12531.822181]  connection2:0: detected conn error (1020)
May 10 02:45:21 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:45:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:45:26 cmp02 kernel: [12534.829579]  connection2:0: detected conn error (1020)
May 10 02:45:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:45:29 cmp02 kernel: [12537.838615]  connection2:0: detected conn error (1020)
May 10 02:45:32 cmp02 kernel: [12540.844661]  connection2:0: detected conn error (1020)
May 10 02:45:33 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:45:35 cmp02 kernel: [12543.852190]  connection2:0: detected conn error (1020)
May 10 02:45:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:45:38 cmp02 kernel: [12546.862146]  connection2:0: detected conn error (1020)
May 10 02:45:41 cmp02 kernel: [12549.871019]  connection2:0: detected conn error (1020)
May 10 02:45:44 cmp02 kernel: [12552.887469]  connection2:0: detected conn error (1020)
May 10 02:45:47 cmp02 kernel: [12555.895291]  connection2:0: detected conn error (1020)
May 10 02:45:50 cmp02 kernel: [12558.903419]  connection2:0: detected conn error (1020)
May 10 02:45:53 cmp02 kernel: [12561.913867]  connection2:0: detected conn error (1020)
May 10 02:45:56 cmp02 kernel: [12564.924084]  connection2:0: detected conn error (1020)
May 10 02:45:59 cmp02 kernel: [12567.931884]  connection2:0: detected conn error (1020)
May 10 02:46:02 cmp02 kernel: [12570.940250]  connection2:0: detected conn error (1020)
May 10 02:46:05 cmp02 kernel: [12573.949676]  connection2:0: detected conn error (1020)
May 10 02:46:08 cmp02 kernel: [12576.957736]  connection2:0: detected conn error (1020)
May 10 02:46:11 cmp02 kernel: [12579.965324]  connection2:0: detected conn error (1020)
May 10 02:46:14 cmp02 kernel: [12582.970608]  connection2:0: detected conn error (1020)
May 10 02:46:17 cmp02 kernel: [12585.978583]  connection2:0: detected conn error (1020)
May 10 02:46:20 cmp02 kernel: [12588.984664]  connection2:0: detected conn error (1020)
May 10 02:46:23 cmp02 kernel: [12591.992829]  connection2:0: detected conn error (1020)
May 10 02:46:24 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:46:26 cmp02 kernel: [12595.000521]  connection2:0: detected conn error (1020)
May 10 02:46:27 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:46:29 cmp02 kernel: [12598.007973]  connection2:0: detected conn error (1020)
May 10 02:46:30 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:46:32 cmp02 kernel: [12601.013526]  connection2:0: detected conn error (1020)
May 10 02:46:33 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:46:35 cmp02 kernel: [12604.023147]  connection2:0: detected conn error (1020)
May 10 02:46:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:46:39 cmp02 kernel: [12607.033128]  connection2:0: detected conn error (1020)
May 10 02:46:42 cmp02 kernel: [12610.041175]  connection2:0: detected conn error (1020)
May 10 02:46:45 cmp02 kernel: [12613.048027]  connection2:0: detected conn error (1020)
May 10 02:46:48 cmp02 kernel: [12616.054625]  connection2:0: detected conn error (1020)
May 10 02:46:51 cmp02 kernel: [12619.061302]  connection2:0: detected conn error (1020)
May 10 02:46:54 cmp02 kernel: [12622.066685]  connection2:0: detected conn error (1020)
May 10 02:46:57 cmp02 kernel: [12625.073968]  connection2:0: detected conn error (1020)
May 10 02:47:00 cmp02 kernel: [12628.081268]  connection2:0: detected conn error (1020)
May 10 02:47:03 cmp02 kernel: [12631.088950]  connection2:0: detected conn error (1020)
May 10 02:47:06 cmp02 kernel: [12634.096111]  connection2:0: detected conn error (1020)
May 10 02:47:09 cmp02 kernel: [12637.102912]  connection2:0: detected conn error (1020)
May 10 02:47:12 cmp02 kernel: [12640.113335]  connection2:0: detected conn error (1020)
May 10 02:47:15 cmp02 kernel: [12643.119239]  connection2:0: detected conn error (1020)
May 10 02:47:18 cmp02 kernel: [12646.130093]  connection2:0: detected conn error (1020)
May 10 02:47:21 cmp02 kernel: [12649.136696]  connection2:0: detected conn error (1020)
May 10 02:47:24 cmp02 kernel: [12652.146718]  connection2:0: detected conn error (1020)
May 10 02:47:27 cmp02 kernel: [12655.154339]  connection2:0: detected conn error (1020)
May 10 02:47:25 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:47:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:47:30 cmp02 kernel: [12658.162878]  connection2:0: detected conn error (1020)
May 10 02:47:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:47:33 cmp02 kernel: [12661.170505]  connection2:0: detected conn error (1020)
May 10 02:47:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:47:36 cmp02 kernel: [12664.176140]  connection2:0: detected conn error (1020)
May 10 02:47:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:47:39 cmp02 kernel: [12667.185648]  connection2:0: detected conn error (1020)
May 10 02:47:42 cmp02 kernel: [12670.191214]  connection2:0: detected conn error (1020)
May 10 02:47:45 cmp02 kernel: [12673.197577]  connection2:0: detected conn error (1020)
May 10 02:47:48 cmp02 kernel: [12676.207776]  connection2:0: detected conn error (1020)
May 10 02:47:51 cmp02 kernel: [12679.219479]  connection2:0: detected conn error (1020)
May 10 02:47:54 cmp02 kernel: [12682.230232]  connection2:0: detected conn error (1020)
May 10 02:47:57 cmp02 kernel: [12685.236923]  connection2:0: detected conn error (1020)
May 10 02:48:00 cmp02 kernel: [12688.243773]  connection2:0: detected conn error (1020)
May 10 02:48:03 cmp02 kernel: [12691.250910]  connection2:0: detected conn error (1020)
May 10 02:48:06 cmp02 kernel: [12694.260531]  connection2:0: detected conn error (1020)
May 10 02:48:09 cmp02 kernel: [12697.267055]  connection2:0: detected conn error (1020)
May 10 02:48:12 cmp02 kernel: [12700.275028]  connection2:0: detected conn error (1020)
May 10 02:48:15 cmp02 kernel: [12703.282348]  connection2:0: detected conn error (1020)
May 10 02:48:18 cmp02 kernel: [12706.293927]  connection2:0: detected conn error (1020)
May 10 02:48:21 cmp02 kernel: [12709.303107]  connection2:0: detected conn error (1020)
May 10 02:48:24 cmp02 kernel: [12712.311578]  connection2:0: detected conn error (1020)
May 10 02:48:27 cmp02 kernel: [12715.318136]  connection2:0: detected conn error (1020)
May 10 02:48:28 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:48:30 cmp02 kernel: [12718.324319]  connection2:0: detected conn error (1020)
May 10 02:48:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:48:33 cmp02 kernel: [12721.332023]  connection2:0: detected conn error (1020)
May 10 02:48:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:48:36 cmp02 kernel: [12724.340606]  connection2:0: detected conn error (1020)
May 10 02:48:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:48:39 cmp02 kernel: [12727.348182]  connection2:0: detected conn error (1020)
May 10 02:48:42 cmp02 kernel: [12730.355836]  connection2:0: detected conn error (1020)
May 10 02:48:45 cmp02 kernel: [12733.361862]  connection2:0: detected conn error (1020)
May 10 02:48:48 cmp02 kernel: [12736.367776]  connection2:0: detected conn error (1020)
May 10 02:48:51 cmp02 kernel: [12739.381597]  connection2:0: detected conn error (1020)
May 10 02:48:54 cmp02 kernel: [12742.388823]  connection2:0: detected conn error (1020)
May 10 02:48:57 cmp02 kernel: [12745.394829]  connection2:0: detected conn error (1020)
May 10 02:49:00 cmp02 kernel: [12748.401280]  connection2:0: detected conn error (1020)
May 10 02:49:03 cmp02 kernel: [12751.411612]  connection2:0: detected conn error (1020)
May 10 02:49:06 cmp02 kernel: [12754.421899]  connection2:0: detected conn error (1020)
May 10 02:49:09 cmp02 kernel: [12757.431176]  connection2:0: detected conn error (1020)
May 10 02:49:12 cmp02 kernel: [12760.441173]  connection2:0: detected conn error (1020)
May 10 02:49:15 cmp02 kernel: [12763.449996]  connection2:0: detected conn error (1020)
May 10 02:49:18 cmp02 kernel: [12766.460260]  connection2:0: detected conn error (1020)
May 10 02:49:21 cmp02 kernel: [12769.469670]  connection2:0: detected conn error (1020)
May 10 02:49:24 cmp02 kernel: [12772.477944]  connection2:0: detected conn error (1020)
May 10 02:49:27 cmp02 kernel: [12775.485988]  connection2:0: detected conn error (1020)
May 10 02:49:28 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:49:30 cmp02 kernel: [12778.493364]  connection2:0: detected conn error (1020)
May 10 02:49:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:49:33 cmp02 kernel: [12781.506098]  connection2:0: detected conn error (1020)
May 10 02:49:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:49:36 cmp02 kernel: [12784.516248]  connection2:0: detected conn error (1020)
May 10 02:49:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:49:39 cmp02 kernel: [12787.524047]  connection2:0: detected conn error (1020)
May 10 02:49:42 cmp02 kernel: [12790.535014]  connection2:0: detected conn error (1020)
May 10 02:49:45 cmp02 kernel: [12793.546828]  connection2:0: detected conn error (1020)
May 10 02:49:48 cmp02 kernel: [12796.557326]  connection2:0: detected conn error (1020)
May 10 02:49:51 cmp02 kernel: [12799.565657]  connection2:0: detected conn error (1020)
May 10 02:49:54 cmp02 kernel: [12802.574569]  connection2:0: detected conn error (1020)
May 10 02:49:57 cmp02 kernel: [12805.585090]  connection2:0: detected conn error (1020)
May 10 02:50:00 cmp02 kernel: [12808.591063]  connection2:0: detected conn error (1020)
May 10 02:50:03 cmp02 kernel: [12811.597807]  connection2:0: detected conn error (1020)
May 10 02:50:06 cmp02 kernel: [12814.604357]  connection2:0: detected conn error (1020)
May 10 02:50:09 cmp02 kernel: [12817.611973]  connection2:0: detected conn error (1020)
May 10 02:50:12 cmp02 kernel: [12820.622783]  connection2:0: detected conn error (1020)
May 10 02:50:15 cmp02 kernel: [12823.630565]  connection2:0: detected conn error (1020)
May 10 02:50:18 cmp02 kernel: [12826.636869]  connection2:0: detected conn error (1020)
May 10 02:50:21 cmp02 kernel: [12829.647311]  connection2:0: detected conn error (1020)
May 10 02:50:24 cmp02 kernel: [12832.653425]  connection2:0: detected conn error (1020)
May 10 02:50:27 cmp02 kernel: [12835.662515]  connection2:0: detected conn error (1020)
May 10 02:50:30 cmp02 kernel: [12838.667757]  connection2:0: detected conn error (1020)
May 10 02:50:28 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:50:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:50:33 cmp02 kernel: [12841.674635]  connection2:0: detected conn error (1020)
May 10 02:50:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:50:36 cmp02 kernel: [12844.680712]  connection2:0: detected conn error (1020)
May 10 02:50:39 cmp02 kernel: [12847.689960]  connection2:0: detected conn error (1020)
May 10 02:50:42 cmp02 kernel: [12850.695627]  connection2:0: detected conn error (1020)
May 10 02:50:45 cmp02 kernel: [12853.702389]  connection2:0: detected conn error (1020)
May 10 02:50:48 cmp02 kernel: [12856.712511]  connection2:0: detected conn error (1020)
May 10 02:50:51 cmp02 kernel: [12859.723876]  connection2:0: detected conn error (1020)
May 10 02:50:54 cmp02 kernel: [12862.738920]  connection2:0: detected conn error (1020)
May 10 02:50:57 cmp02 kernel: [12865.746324]  connection2:0: detected conn error (1020)
May 10 02:51:00 cmp02 kernel: [12868.753491]  connection2:0: detected conn error (1020)
May 10 02:51:03 cmp02 kernel: [12871.766585]  connection2:0: detected conn error (1020)
May 10 02:51:04 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:51:05 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 02:51:05 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 02:51:05 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1421 seconds.
May 10 02:51:06 cmp02 kernel: [12874.779485]  connection2:0: detected conn error (1020)
May 10 02:51:07 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:51:09 cmp02 kernel: [12877.790976]  connection2:0: detected conn error (1020)
May 10 02:51:12 cmp02 kernel: [12880.797792]  connection2:0: detected conn error (1020)
May 10 02:51:15 cmp02 kernel: [12883.805718]  connection2:0: detected conn error (1020)
May 10 02:51:18 cmp02 kernel: [12886.814888]  connection2:0: detected conn error (1020)
May 10 02:51:21 cmp02 kernel: [12889.821948]  connection2:0: detected conn error (1020)
May 10 02:51:24 cmp02 kernel: [12892.829666]  connection2:0: detected conn error (1020)
May 10 02:51:27 cmp02 kernel: [12895.835724]  connection2:0: detected conn error (1020)
May 10 02:51:30 cmp02 kernel: [12898.846401]  connection2:0: detected conn error (1020)
May 10 02:51:28 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:51:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:51:33 cmp02 kernel: [12901.851868]  connection2:0: detected conn error (1020)
May 10 02:51:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:51:36 cmp02 kernel: [12904.861274]  connection2:0: detected conn error (1020)
May 10 02:51:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:51:39 cmp02 kernel: [12907.870765]  connection2:0: detected conn error (1020)
May 10 02:51:42 cmp02 kernel: [12910.876198]  connection2:0: detected conn error (1020)
May 10 02:51:45 cmp02 kernel: [12913.885429]  connection2:0: detected conn error (1020)
May 10 02:51:48 cmp02 kernel: [12916.893912]  connection2:0: detected conn error (1020)
May 10 02:51:51 cmp02 kernel: [12919.901932]  connection2:0: detected conn error (1020)
May 10 02:51:54 cmp02 kernel: [12922.907727]  connection2:0: detected conn error (1020)
May 10 02:51:57 cmp02 kernel: [12925.917269]  connection2:0: detected conn error (1020)
May 10 02:52:00 cmp02 kernel: [12928.925811]  connection2:0: detected conn error (1020)
May 10 02:52:03 cmp02 kernel: [12931.931467]  connection2:0: detected conn error (1020)
May 10 02:52:06 cmp02 kernel: [12934.938994]  connection2:0: detected conn error (1020)
May 10 02:52:09 cmp02 kernel: [12937.952244]  connection2:0: detected conn error (1020)
May 10 02:52:12 cmp02 kernel: [12940.958668]  connection2:0: detected conn error (1020)
May 10 02:52:15 cmp02 kernel: [12943.964372]  connection2:0: detected conn error (1020)
May 10 02:52:18 cmp02 kernel: [12946.973504]  connection2:0: detected conn error (1020)
May 10 02:52:21 cmp02 kernel: [12949.986379]  connection2:0: detected conn error (1020)
May 10 02:52:24 cmp02 kernel: [12952.991916]  connection2:0: detected conn error (1020)
May 10 02:52:27 cmp02 kernel: [12956.000615]  connection2:0: detected conn error (1020)
May 10 02:52:30 cmp02 kernel: [12959.007272]  connection2:0: detected conn error (1020)
May 10 02:52:31 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:52:33 cmp02 kernel: [12962.012528]  connection2:0: detected conn error (1020)
May 10 02:52:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:52:36 cmp02 kernel: [12965.021653]  connection2:0: detected conn error (1020)
May 10 02:52:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:52:40 cmp02 kernel: [12968.031476]  connection2:0: detected conn error (1020)
May 10 02:52:43 cmp02 kernel: [12971.041571]  connection2:0: detected conn error (1020)
May 10 02:52:46 cmp02 kernel: [12974.049725]  connection2:0: detected conn error (1020)
May 10 02:52:49 cmp02 kernel: [12977.056671]  connection2:0: detected conn error (1020)
May 10 02:52:52 cmp02 kernel: [12980.063849]  connection2:0: detected conn error (1020)
May 10 02:52:55 cmp02 kernel: [12983.075724]  connection2:0: detected conn error (1020)
May 10 02:52:58 cmp02 kernel: [12986.084494]  connection2:0: detected conn error (1020)
May 10 02:53:01 cmp02 kernel: [12989.091572]  connection2:0: detected conn error (1020)
May 10 02:53:04 cmp02 kernel: [12992.099908]  connection2:0: detected conn error (1020)
May 10 02:53:07 cmp02 kernel: [12995.109324]  connection2:0: detected conn error (1020)
May 10 02:53:10 cmp02 kernel: [12998.115996]  connection2:0: detected conn error (1020)
May 10 02:53:13 cmp02 kernel: [13001.124878]  connection2:0: detected conn error (1020)
May 10 02:53:16 cmp02 kernel: [13004.134649]  connection2:0: detected conn error (1020)
May 10 02:53:19 cmp02 kernel: [13007.142597]  connection2:0: detected conn error (1020)
May 10 02:53:22 cmp02 kernel: [13010.149951]  connection2:0: detected conn error (1020)
May 10 02:53:25 cmp02 kernel: [13013.158021]  connection2:0: detected conn error (1020)
May 10 02:53:28 cmp02 kernel: [13016.168407]  connection2:0: detected conn error (1020)
May 10 02:53:31 cmp02 kernel: [13019.175595]  connection2:0: detected conn error (1020)
May 10 02:53:31 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:53:34 cmp02 kernel: [13022.181339]  connection2:0: detected conn error (1020)
May 10 02:53:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:53:37 cmp02 kernel: [13025.188736]  connection2:0: detected conn error (1020)
May 10 02:53:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:53:40 cmp02 kernel: [13028.198610]  connection2:0: detected conn error (1020)
May 10 02:53:43 cmp02 kernel: [13031.204218]  connection2:0: detected conn error (1020)
May 10 02:53:46 cmp02 kernel: [13034.214782]  connection2:0: detected conn error (1020)
May 10 02:53:49 cmp02 kernel: [13037.222102]  connection2:0: detected conn error (1020)
May 10 02:53:52 cmp02 kernel: [13040.228104]  connection2:0: detected conn error (1020)
May 10 02:53:55 cmp02 kernel: [13043.234883]  connection2:0: detected conn error (1020)
May 10 02:53:56 cmp02 kernel: [13044.587619] device tap89d26cad-bc left promiscuous mode
May 10 02:53:56 cmp02 kernel: [13044.967306] audit: type=1400 audit(1525920836.930:319): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-92c7fbad-edf1-4bee-b7ee-404df52d6012" pid=32259 comm="apparmor_parser"
May 10 02:53:55 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:53:56 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap89d26cad-bc
May 10 02:53:58 cmp02 kernel: [13046.242175]  connection2:0: detected conn error (1020)
May 10 02:53:58 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:54:01 cmp02 kernel: [13049.250519]  connection2:0: detected conn error (1020)
May 10 02:54:04 cmp02 kernel: [13052.257821]  connection2:0: detected conn error (1020)
May 10 02:54:07 cmp02 kernel: [13055.270126]  connection2:0: detected conn error (1020)
May 10 02:54:10 cmp02 kernel: [13058.277968]  connection2:0: detected conn error (1020)
May 10 02:54:13 cmp02 kernel: [13061.288579]  connection2:0: detected conn error (1020)
May 10 02:54:16 cmp02 kernel: [13064.297152]  connection2:0: detected conn error (1020)
May 10 02:54:19 cmp02 kernel: [13067.304353]  connection2:0: detected conn error (1020)
May 10 02:54:22 cmp02 kernel: [13070.313393]  connection2:0: detected conn error (1020)
May 10 02:54:25 cmp02 kernel: [13073.322243]  connection2:0: detected conn error (1020)
May 10 02:54:28 cmp02 kernel: [13076.328928]  connection2:0: detected conn error (1020)
May 10 02:54:31 cmp02 kernel: [13079.337186]  connection2:0: detected conn error (1020)
May 10 02:54:32 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:54:34 cmp02 kernel: [13082.344220]  connection2:0: detected conn error (1020)
May 10 02:54:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:54:37 cmp02 kernel: [13085.349896]  connection2:0: detected conn error (1020)
May 10 02:54:40 cmp02 kernel: [13088.358882]  connection2:0: detected conn error (1020)
May 10 02:54:43 cmp02 kernel: [13091.364033]  connection2:0: detected conn error (1020)
May 10 02:54:46 cmp02 kernel: [13094.372630]  connection2:0: detected conn error (1020)
May 10 02:54:49 cmp02 kernel: [13097.378740]  connection2:0: detected conn error (1020)
May 10 02:54:52 cmp02 kernel: [13100.390132]  connection2:0: detected conn error (1020)
May 10 02:54:55 cmp02 kernel: [13103.398455]  connection2:0: detected conn error (1020)
May 10 02:54:58 cmp02 kernel: [13106.404940]  connection2:0: detected conn error (1020)
May 10 02:55:01 cmp02 kernel: [13109.413124]  connection2:0: detected conn error (1020)
May 10 02:55:04 cmp02 kernel: [13112.418701]  connection2:0: detected conn error (1020)
May 10 02:55:07 cmp02 kernel: [13115.425517]  connection2:0: detected conn error (1020)
May 10 02:55:10 cmp02 kernel: [13118.432395]  connection2:0: detected conn error (1020)
May 10 02:55:13 cmp02 kernel: [13121.438436]  connection2:0: detected conn error (1020)
May 10 02:55:16 cmp02 kernel: [13124.445454]  connection2:0: detected conn error (1020)
May 10 02:55:19 cmp02 kernel: [13127.455240]  connection2:0: detected conn error (1020)
May 10 02:55:22 cmp02 kernel: [13130.463273]  connection2:0: detected conn error (1020)
May 10 02:55:25 cmp02 kernel: [13133.470456]  connection2:0: detected conn error (1020)
May 10 02:55:28 cmp02 kernel: [13136.477280]  connection2:0: detected conn error (1020)
May 10 02:55:31 cmp02 kernel: [13139.486573]  connection2:0: detected conn error (1020)
May 10 02:55:34 cmp02 kernel: [13142.493389]  connection2:0: detected conn error (1020)
May 10 02:55:32 cmp02 iscsid: message repeated 19 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:55:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:55:37 cmp02 kernel: [13145.500394]  connection2:0: detected conn error (1020)
May 10 02:55:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:55:40 cmp02 kernel: [13148.509471]  connection2:0: detected conn error (1020)
May 10 02:55:43 cmp02 kernel: [13151.517655]  connection2:0: detected conn error (1020)
May 10 02:55:46 cmp02 kernel: [13154.523410]  connection2:0: detected conn error (1020)
May 10 02:55:49 cmp02 kernel: [13157.529296]  connection2:0: detected conn error (1020)
May 10 02:55:52 cmp02 kernel: [13160.537439]  connection2:0: detected conn error (1020)
May 10 02:55:55 cmp02 kernel: [13163.546438]  connection2:0: detected conn error (1020)
May 10 02:55:58 cmp02 kernel: [13166.556439]  connection2:0: detected conn error (1020)
May 10 02:56:01 cmp02 kernel: [13169.570625]  connection2:0: detected conn error (1020)
May 10 02:56:04 cmp02 kernel: [13172.584149]  connection2:0: detected conn error (1020)
May 10 02:56:07 cmp02 kernel: [13175.595473]  connection2:0: detected conn error (1020)
May 10 02:56:10 cmp02 kernel: [13178.604698]  connection2:0: detected conn error (1020)
May 10 02:56:13 cmp02 kernel: [13181.617494]  connection2:0: detected conn error (1020)
May 10 02:56:16 cmp02 kernel: [13184.631689]  connection2:0: detected conn error (1020)
May 10 02:56:19 cmp02 kernel: [13187.639925]  connection2:0: detected conn error (1020)
May 10 02:56:22 cmp02 kernel: [13190.648595]  connection2:0: detected conn error (1020)
May 10 02:56:25 cmp02 kernel: [13193.658234]  connection2:0: detected conn error (1020)
May 10 02:56:28 cmp02 kernel: [13196.664580]  connection2:0: detected conn error (1020)
May 10 02:56:31 cmp02 kernel: [13199.675626]  connection2:0: detected conn error (1020)
May 10 02:56:32 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:56:34 cmp02 kernel: [13202.682967]  connection2:0: detected conn error (1020)
May 10 02:56:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:56:37 cmp02 kernel: [13205.690636]  connection2:0: detected conn error (1020)
May 10 02:56:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:56:40 cmp02 kernel: [13208.700875]  connection2:0: detected conn error (1020)
May 10 02:56:41 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:56:43 cmp02 kernel: [13211.707409]  connection2:0: detected conn error (1020)
May 10 02:56:46 cmp02 kernel: [13214.712749]  connection2:0: detected conn error (1020)
May 10 02:56:49 cmp02 kernel: [13217.722957]  connection2:0: detected conn error (1020)
May 10 02:56:52 cmp02 kernel: [13220.729837]  connection2:0: detected conn error (1020)
May 10 02:56:55 cmp02 kernel: [13223.738048]  connection2:0: detected conn error (1020)
May 10 02:56:58 cmp02 kernel: [13226.748017]  connection2:0: detected conn error (1020)
May 10 02:57:01 cmp02 kernel: [13229.757124]  connection2:0: detected conn error (1020)
May 10 02:57:04 cmp02 kernel: [13232.766041]  connection2:0: detected conn error (1020)
May 10 02:57:07 cmp02 kernel: [13235.772297]  connection2:0: detected conn error (1020)
May 10 02:57:10 cmp02 kernel: [13238.780662]  connection2:0: detected conn error (1020)
May 10 02:57:13 cmp02 kernel: [13241.787831]  connection2:0: detected conn error (1020)
May 10 02:57:16 cmp02 kernel: [13244.795403]  connection2:0: detected conn error (1020)
May 10 02:57:19 cmp02 kernel: [13247.806729]  connection2:0: detected conn error (1020)
May 10 02:57:22 cmp02 kernel: [13250.814387]  connection2:0: detected conn error (1020)
May 10 02:57:25 cmp02 kernel: [13253.824124]  connection2:0: detected conn error (1020)
May 10 02:57:28 cmp02 kernel: [13256.832398]  connection2:0: detected conn error (1020)
May 10 02:57:31 cmp02 kernel: [13259.842828]  connection2:0: detected conn error (1020)
May 10 02:57:32 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:57:34 cmp02 kernel: [13262.852499]  connection2:0: detected conn error (1020)
May 10 02:57:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:57:37 cmp02 kernel: [13265.863237]  connection2:0: detected conn error (1020)
May 10 02:57:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:57:40 cmp02 kernel: [13268.869919]  connection2:0: detected conn error (1020)
May 10 02:57:41 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:57:43 cmp02 kernel: [13271.878580]  connection2:0: detected conn error (1020)
May 10 02:57:46 cmp02 kernel: [13274.887250]  connection2:0: detected conn error (1020)
May 10 02:57:49 cmp02 kernel: [13277.898502]  connection2:0: detected conn error (1020)
May 10 02:57:52 cmp02 kernel: [13280.910817]  connection2:0: detected conn error (1020)
May 10 02:57:55 cmp02 kernel: [13283.917539]  connection2:0: detected conn error (1020)
May 10 02:57:58 cmp02 kernel: [13286.928139]  connection2:0: detected conn error (1020)
May 10 02:58:01 cmp02 kernel: [13289.937037]  connection2:0: detected conn error (1020)
May 10 02:58:04 cmp02 kernel: [13292.944041]  connection2:0: detected conn error (1020)
May 10 02:58:07 cmp02 kernel: [13295.954973]  connection2:0: detected conn error (1020)
May 10 02:58:10 cmp02 kernel: [13298.963883]  connection2:0: detected conn error (1020)
May 10 02:58:13 cmp02 kernel: [13301.976631]  connection2:0: detected conn error (1020)
May 10 02:58:16 cmp02 kernel: [13304.986344]  connection2:0: detected conn error (1020)
May 10 02:58:19 cmp02 kernel: [13307.992788]  connection2:0: detected conn error (1020)
May 10 02:58:22 cmp02 kernel: [13311.001373]  connection2:0: detected conn error (1020)
May 10 02:58:25 cmp02 kernel: [13314.011403]  connection2:0: detected conn error (1020)
May 10 02:58:28 cmp02 kernel: [13317.017973]  connection2:0: detected conn error (1020)
May 10 02:58:31 cmp02 kernel: [13320.028328]  connection2:0: detected conn error (1020)
May 10 02:58:32 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:58:34 cmp02 kernel: [13323.035851]  connection2:0: detected conn error (1020)
May 10 02:58:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:58:38 cmp02 kernel: [13326.043736]  connection2:0: detected conn error (1020)
May 10 02:58:38 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:58:41 cmp02 kernel: [13329.051703]  connection2:0: detected conn error (1020)
May 10 02:58:41 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:58:44 cmp02 kernel: [13332.059761]  connection2:0: detected conn error (1020)
May 10 02:58:47 cmp02 kernel: [13335.066542]  connection2:0: detected conn error (1020)
May 10 02:58:50 cmp02 kernel: [13338.075612]  connection2:0: detected conn error (1020)
May 10 02:58:53 cmp02 kernel: [13341.083070]  connection2:0: detected conn error (1020)
May 10 02:58:56 cmp02 kernel: [13344.106659]  connection2:0: detected conn error (1020)
May 10 02:58:59 cmp02 kernel: [13347.116807]  connection2:0: detected conn error (1020)
May 10 02:59:02 cmp02 kernel: [13350.123356]  connection2:0: detected conn error (1020)
May 10 02:59:05 cmp02 kernel: [13353.133535]  connection2:0: detected conn error (1020)
May 10 02:59:08 cmp02 kernel: [13356.145373]  connection2:0: detected conn error (1020)
May 10 02:59:11 cmp02 kernel: [13359.157190]  connection2:0: detected conn error (1020)
May 10 02:59:14 cmp02 kernel: [13362.166447]  connection2:0: detected conn error (1020)
May 10 02:59:17 cmp02 kernel: [13365.175752]  connection2:0: detected conn error (1020)
May 10 02:59:20 cmp02 kernel: [13368.182668]  connection2:0: detected conn error (1020)
May 10 02:59:23 cmp02 kernel: [13371.187738]  connection2:0: detected conn error (1020)
May 10 02:59:26 cmp02 kernel: [13374.196152]  connection2:0: detected conn error (1020)
May 10 02:59:29 cmp02 kernel: [13377.202340]  connection2:0: detected conn error (1020)
May 10 02:59:32 cmp02 kernel: [13380.210320]  connection2:0: detected conn error (1020)
May 10 02:59:32 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:59:35 cmp02 kernel: [13383.218249]  connection2:0: detected conn error (1020)
May 10 02:59:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:59:38 cmp02 kernel: [13386.227953]  connection2:0: detected conn error (1020)
May 10 02:59:41 cmp02 kernel: [13389.239539]  connection2:0: detected conn error (1020)
May 10 02:59:41 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 02:59:44 cmp02 kernel: [13392.247056]  connection2:0: detected conn error (1020)
May 10 02:59:44 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 02:59:47 cmp02 kernel: [13395.256603]  connection2:0: detected conn error (1020)
May 10 02:59:50 cmp02 kernel: [13398.264877]  connection2:0: detected conn error (1020)
May 10 02:59:53 cmp02 kernel: [13401.275145]  connection2:0: detected conn error (1020)
May 10 02:59:56 cmp02 kernel: [13404.283809]  connection2:0: detected conn error (1020)
May 10 02:59:59 cmp02 kernel: [13407.293353]  connection2:0: detected conn error (1020)
May 10 03:00:02 cmp02 kernel: [13410.301791]  connection2:0: detected conn error (1020)
May 10 03:00:05 cmp02 kernel: [13413.315372]  connection2:0: detected conn error (1020)
May 10 03:00:08 cmp02 kernel: [13416.326289]  connection2:0: detected conn error (1020)
May 10 03:00:11 cmp02 kernel: [13419.334808]  connection2:0: detected conn error (1020)
May 10 03:00:14 cmp02 kernel: [13422.344118]  connection2:0: detected conn error (1020)
May 10 03:00:17 cmp02 kernel: [13425.355524]  connection2:0: detected conn error (1020)
May 10 03:00:20 cmp02 kernel: [13428.366566]  connection2:0: detected conn error (1020)
May 10 03:00:23 cmp02 kernel: [13431.377810]  connection2:0: detected conn error (1020)
May 10 03:00:26 cmp02 kernel: [13434.389667]  connection2:0: detected conn error (1020)
May 10 03:00:29 cmp02 kernel: [13437.396444]  connection2:0: detected conn error (1020)
May 10 03:00:32 cmp02 kernel: [13440.407153]  connection2:0: detected conn error (1020)
May 10 03:00:32 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:00:35 cmp02 kernel: [13443.417398]  connection2:0: detected conn error (1020)
May 10 03:00:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:00:38 cmp02 kernel: [13446.422381]  connection2:0: detected conn error (1020)
May 10 03:00:41 cmp02 kernel: [13449.431398]  connection2:0: detected conn error (1020)
May 10 03:00:42 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:00:44 cmp02 kernel: [13452.440178]  connection2:0: detected conn error (1020)
May 10 03:00:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:00:47 cmp02 kernel: [13455.449522]  connection2:0: detected conn error (1020)
May 10 03:00:50 cmp02 kernel: [13458.463448]  connection2:0: detected conn error (1020)
May 10 03:00:53 cmp02 kernel: [13461.474342]  connection2:0: detected conn error (1020)
May 10 03:00:56 cmp02 kernel: [13464.486244]  connection2:0: detected conn error (1020)
May 10 03:00:59 cmp02 kernel: [13467.494202]  connection2:0: detected conn error (1020)
May 10 03:01:02 cmp02 kernel: [13470.503211]  connection2:0: detected conn error (1020)
May 10 03:01:05 cmp02 kernel: [13473.510329]  connection2:0: detected conn error (1020)
May 10 03:01:08 cmp02 kernel: [13476.517551]  connection2:0: detected conn error (1020)
May 10 03:01:11 cmp02 kernel: [13479.526623]  connection2:0: detected conn error (1020)
May 10 03:01:14 cmp02 kernel: [13482.534835]  connection2:0: detected conn error (1020)
May 10 03:01:17 cmp02 kernel: [13485.541999]  connection2:0: detected conn error (1020)
May 10 03:01:20 cmp02 kernel: [13488.548940]  connection2:0: detected conn error (1020)
May 10 03:01:23 cmp02 kernel: [13491.557833]  connection2:0: detected conn error (1020)
May 10 03:01:26 cmp02 kernel: [13494.567904]  connection2:0: detected conn error (1020)
May 10 03:01:29 cmp02 kernel: [13497.578701]  connection2:0: detected conn error (1020)
May 10 03:01:32 cmp02 kernel: [13500.585961]  connection2:0: detected conn error (1020)
May 10 03:01:33 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:01:35 cmp02 kernel: [13503.594140]  connection2:0: detected conn error (1020)
May 10 03:01:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:01:38 cmp02 kernel: [13506.601948]  connection2:0: detected conn error (1020)
May 10 03:01:41 cmp02 kernel: [13509.608928]  connection2:0: detected conn error (1020)
May 10 03:01:44 cmp02 kernel: [13512.618530]  connection2:0: detected conn error (1020)
May 10 03:01:42 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:01:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:01:47 cmp02 kernel: [13515.625179]  connection2:0: detected conn error (1020)
May 10 03:01:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:01:50 cmp02 kernel: [13518.633564]  connection2:0: detected conn error (1020)
May 10 03:01:53 cmp02 kernel: [13521.641847]  connection2:0: detected conn error (1020)
May 10 03:01:56 cmp02 kernel: [13524.649987]  connection2:0: detected conn error (1020)
May 10 03:01:59 cmp02 kernel: [13527.657917]  connection2:0: detected conn error (1020)
May 10 03:02:02 cmp02 kernel: [13530.665011]  connection2:0: detected conn error (1020)
May 10 03:02:05 cmp02 kernel: [13533.676479]  connection2:0: detected conn error (1020)
May 10 03:02:08 cmp02 kernel: [13536.693846]  connection2:0: detected conn error (1020)
May 10 03:02:11 cmp02 kernel: [13539.703287]  connection2:0: detected conn error (1020)
May 10 03:02:14 cmp02 kernel: [13542.721901]  connection2:0: detected conn error (1020)
May 10 03:02:17 cmp02 kernel: [13545.735132]  connection2:0: detected conn error (1020)
May 10 03:02:20 cmp02 kernel: [13548.749232]  connection2:0: detected conn error (1020)
May 10 03:02:23 cmp02 kernel: [13551.760338]  connection2:0: detected conn error (1020)
May 10 03:02:26 cmp02 kernel: [13554.767486]  connection2:0: detected conn error (1020)
May 10 03:02:29 cmp02 kernel: [13557.787610]  connection2:0: detected conn error (1020)
May 10 03:02:32 cmp02 kernel: [13560.806175]  connection2:0: detected conn error (1020)
May 10 03:02:33 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:02:35 cmp02 kernel: [13563.814525]  connection2:0: detected conn error (1020)
May 10 03:02:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:02:38 cmp02 kernel: [13566.824081]  connection2:0: detected conn error (1020)
May 10 03:02:41 cmp02 kernel: [13569.836575]  connection2:0: detected conn error (1020)
May 10 03:02:44 cmp02 kernel: [13572.858068]  connection2:0: detected conn error (1020)
May 10 03:02:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:02:47 cmp02 kernel: [13575.878349]  connection2:0: detected conn error (1020)
May 10 03:02:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:02:50 cmp02 kernel: [13578.885988]  connection2:0: detected conn error (1020)
May 10 03:02:53 cmp02 kernel: [13581.901922]  connection2:0: detected conn error (1020)
May 10 03:02:56 cmp02 kernel: [13584.912340]  connection2:0: detected conn error (1020)
May 10 03:02:59 cmp02 kernel: [13587.940915]  connection2:0: detected conn error (1020)
May 10 03:03:02 cmp02 kernel: [13590.948590]  connection2:0: detected conn error (1020)
May 10 03:03:05 cmp02 kernel: [13593.959395]  connection2:0: detected conn error (1020)
May 10 03:03:08 cmp02 kernel: [13596.968102]  connection2:0: detected conn error (1020)
May 10 03:03:11 cmp02 kernel: [13599.976438]  connection2:0: detected conn error (1020)
May 10 03:03:14 cmp02 kernel: [13602.984398]  connection2:0: detected conn error (1020)
May 10 03:03:17 cmp02 kernel: [13605.992960]  connection2:0: detected conn error (1020)
May 10 03:03:20 cmp02 kernel: [13609.000361]  connection2:0: detected conn error (1020)
May 10 03:03:23 cmp02 kernel: [13612.009118]  connection2:0: detected conn error (1020)
May 10 03:03:26 cmp02 kernel: [13615.017106]  connection2:0: detected conn error (1020)
May 10 03:03:29 cmp02 kernel: [13618.023778]  connection2:0: detected conn error (1020)
May 10 03:03:32 cmp02 kernel: [13621.034062]  connection2:0: detected conn error (1020)
May 10 03:03:33 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:03:35 cmp02 kernel: [13624.041157]  connection2:0: detected conn error (1020)
May 10 03:03:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:03:39 cmp02 kernel: [13627.050311]  connection2:0: detected conn error (1020)
May 10 03:03:42 cmp02 kernel: [13630.056953]  connection2:0: detected conn error (1020)
May 10 03:03:45 cmp02 kernel: [13633.063258]  connection2:0: detected conn error (1020)
May 10 03:03:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:03:48 cmp02 kernel: [13636.072154]  connection2:0: detected conn error (1020)
May 10 03:03:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:03:51 cmp02 kernel: [13639.081685]  connection2:0: detected conn error (1020)
May 10 03:03:54 cmp02 kernel: [13642.089288]  connection2:0: detected conn error (1020)
May 10 03:03:57 cmp02 kernel: [13645.096411]  connection2:0: detected conn error (1020)
May 10 03:04:00 cmp02 kernel: [13648.105587]  connection2:0: detected conn error (1020)
May 10 03:04:03 cmp02 kernel: [13651.113321]  connection2:0: detected conn error (1020)
May 10 03:04:06 cmp02 kernel: [13654.122441]  connection2:0: detected conn error (1020)
May 10 03:04:09 cmp02 kernel: [13657.131725]  connection2:0: detected conn error (1020)
May 10 03:04:12 cmp02 kernel: [13660.139939]  connection2:0: detected conn error (1020)
May 10 03:04:15 cmp02 kernel: [13663.148739]  connection2:0: detected conn error (1020)
May 10 03:04:18 cmp02 kernel: [13666.155863]  connection2:0: detected conn error (1020)
May 10 03:04:21 cmp02 kernel: [13669.163277]  connection2:0: detected conn error (1020)
May 10 03:04:24 cmp02 kernel: [13672.173658]  connection2:0: detected conn error (1020)
May 10 03:04:27 cmp02 kernel: [13675.181843]  connection2:0: detected conn error (1020)
May 10 03:04:30 cmp02 kernel: [13678.192005]  connection2:0: detected conn error (1020)
May 10 03:04:33 cmp02 kernel: [13681.198818]  connection2:0: detected conn error (1020)
May 10 03:04:33 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:04:36 cmp02 kernel: [13684.205253]  connection2:0: detected conn error (1020)
May 10 03:04:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:04:39 cmp02 kernel: [13687.211578]  connection2:0: detected conn error (1020)
May 10 03:04:42 cmp02 kernel: [13690.218502]  connection2:0: detected conn error (1020)
May 10 03:04:45 cmp02 kernel: [13693.225866]  connection2:0: detected conn error (1020)
May 10 03:04:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:04:48 cmp02 kernel: [13696.235147]  connection2:0: detected conn error (1020)
May 10 03:04:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:04:51 cmp02 kernel: [13699.243765]  connection2:0: detected conn error (1020)
May 10 03:04:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:04:54 cmp02 kernel: [13702.249103]  connection2:0: detected conn error (1020)
May 10 03:04:57 cmp02 kernel: [13705.255085]  connection2:0: detected conn error (1020)
May 10 03:05:00 cmp02 kernel: [13708.263309]  connection2:0: detected conn error (1020)
May 10 03:05:03 cmp02 kernel: [13711.269119]  connection2:0: detected conn error (1020)
May 10 03:05:06 cmp02 kernel: [13714.276742]  connection2:0: detected conn error (1020)
May 10 03:05:09 cmp02 kernel: [13717.285695]  connection2:0: detected conn error (1020)
May 10 03:05:12 cmp02 kernel: [13720.290919]  connection2:0: detected conn error (1020)
May 10 03:05:15 cmp02 kernel: [13723.297454]  connection2:0: detected conn error (1020)
May 10 03:05:18 cmp02 kernel: [13726.305046]  connection2:0: detected conn error (1020)
May 10 03:05:21 cmp02 kernel: [13729.312923]  connection2:0: detected conn error (1020)
May 10 03:05:24 cmp02 kernel: [13732.320074]  connection2:0: detected conn error (1020)
May 10 03:05:27 cmp02 kernel: [13735.325266]  connection2:0: detected conn error (1020)
May 10 03:05:30 cmp02 kernel: [13738.334249]  connection2:0: detected conn error (1020)
May 10 03:05:33 cmp02 kernel: [13741.341181]  connection2:0: detected conn error (1020)
May 10 03:05:33 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:05:36 cmp02 kernel: [13744.347180]  connection2:0: detected conn error (1020)
May 10 03:05:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:05:38 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 03:05:39 cmp02 kernel: [13747.355059]  connection2:0: detected conn error (1020)
May 10 03:05:39 cmp02 kernel: [13747.651952] audit: type=1400 audit(1525921539.601:320): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-098fa717-d565-4c41-aba5-05e6d845200a" pid=644 comm="apparmor_parser"
May 10 03:05:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:05:39 cmp02 kernel: [13747.898118] audit: type=1400 audit(1525921539.848:321): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-098fa717-d565-4c41-aba5-05e6d845200a" pid=647 comm="apparmor_parser"
May 10 03:05:40 cmp02 kernel: [13748.145167] audit: type=1400 audit(1525921540.095:322): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-098fa717-d565-4c41-aba5-05e6d845200a" pid=650 comm="apparmor_parser"
May 10 03:05:40 cmp02 kernel: [13748.397949] audit: type=1400 audit(1525921540.348:323): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-098fa717-d565-4c41-aba5-05e6d845200a" pid=653 comm="apparmor_parser"
May 10 03:05:40 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapbe670a0e-bf -- add-port br-int tapbe670a0e-bf -- set Interface tapbe670a0e-bf "external-ids:attached-mac=\"fa:16:3e:1d:64:ea\"" -- set Interface tapbe670a0e-bf "external-ids:iface-id=\"be670a0e-bfea-4d81-8744-c247ed9a9801\"" -- set Interface tapbe670a0e-bf "external-ids:vm-id=\"098fa717-d565-4c41-aba5-05e6d845200a\"" -- set Interface tapbe670a0e-bf external-ids:iface-status=active
May 10 03:05:40 cmp02 kernel: [13748.434733] device tapbe670a0e-bf entered promiscuous mode
May 10 03:05:40 cmp02 kernel: [13748.674934] audit: type=1400 audit(1525921540.625:324): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-098fa717-d565-4c41-aba5-05e6d845200a" pid=739 comm="apparmor_parser"
May 10 03:05:40 cmp02 libvirtd[5599]: 2018-05-10 03:05:40.631+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=50 name='instance-0000006d' uuid=098fa717-d565-4c41-aba5-05e6d845200a is tainted: host-cpu
May 10 03:05:42 cmp02 kernel: [13750.362721]  connection2:0: detected conn error (1020)
May 10 03:05:42 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:05:45 cmp02 kernel: [13753.367704]  connection2:0: detected conn error (1020)
May 10 03:05:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:05:48 cmp02 kernel: [13756.373837]  connection2:0: detected conn error (1020)
May 10 03:05:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:05:51 cmp02 kernel: [13759.380430]  connection2:0: detected conn error (1020)
May 10 03:05:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:05:54 cmp02 kernel: [13762.386610]  connection2:0: detected conn error (1020)
May 10 03:05:57 cmp02 kernel: [13765.392250]  connection2:0: detected conn error (1020)
May 10 03:06:00 cmp02 kernel: [13768.398254]  connection2:0: detected conn error (1020)
May 10 03:06:03 cmp02 kernel: [13771.404459]  connection2:0: detected conn error (1020)
May 10 03:06:06 cmp02 kernel: [13774.410242]  connection2:0: detected conn error (1020)
May 10 03:06:09 cmp02 kernel: [13777.416241]  connection2:0: detected conn error (1020)
May 10 03:06:12 cmp02 kernel: [13780.420593]  connection2:0: detected conn error (1020)
May 10 03:06:15 cmp02 kernel: [13783.426781]  connection2:0: detected conn error (1020)
May 10 03:06:18 cmp02 kernel: [13786.435000]  connection2:0: detected conn error (1020)
May 10 03:06:21 cmp02 kernel: [13789.440205]  connection2:0: detected conn error (1020)
May 10 03:06:24 cmp02 kernel: [13792.447266]  connection2:0: detected conn error (1020)
May 10 03:06:27 cmp02 kernel: [13795.455634]  connection2:0: detected conn error (1020)
May 10 03:06:30 cmp02 kernel: [13798.474688]  connection2:0: detected conn error (1020)
May 10 03:06:33 cmp02 kernel: [13801.482804]  connection2:0: detected conn error (1020)
May 10 03:06:33 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:06:36 cmp02 kernel: [13804.496016]  connection2:0: detected conn error (1020)
May 10 03:06:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:06:39 cmp02 kernel: [13807.502462]  connection2:0: detected conn error (1020)
May 10 03:06:42 cmp02 kernel: [13810.509332]  connection2:0: detected conn error (1020)
May 10 03:06:45 cmp02 kernel: [13813.517637]  connection2:0: detected conn error (1020)
May 10 03:06:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:06:48 cmp02 kernel: [13816.525905]  connection2:0: detected conn error (1020)
May 10 03:06:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:06:51 cmp02 kernel: [13819.533239]  connection2:0: detected conn error (1020)
May 10 03:06:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:06:54 cmp02 kernel: [13822.542898]  connection2:0: detected conn error (1020)
May 10 03:06:57 cmp02 kernel: [13825.547990]  connection2:0: detected conn error (1020)
May 10 03:07:00 cmp02 kernel: [13828.558525]  connection2:0: detected conn error (1020)
May 10 03:07:03 cmp02 kernel: [13831.568595]  connection2:0: detected conn error (1020)
May 10 03:07:06 cmp02 kernel: [13834.576268]  connection2:0: detected conn error (1020)
May 10 03:07:09 cmp02 kernel: [13837.588426]  connection2:0: detected conn error (1020)
May 10 03:07:12 cmp02 kernel: [13840.597991]  connection2:0: detected conn error (1020)
May 10 03:07:15 cmp02 kernel: [13843.610413]  connection2:0: detected conn error (1020)
May 10 03:07:18 cmp02 kernel: [13846.620145]  connection2:0: detected conn error (1020)
May 10 03:07:21 cmp02 kernel: [13849.630928]  connection2:0: detected conn error (1020)
May 10 03:07:24 cmp02 kernel: [13852.638755]  connection2:0: detected conn error (1020)
May 10 03:07:27 cmp02 kernel: [13855.647271]  connection2:0: detected conn error (1020)
May 10 03:07:30 cmp02 kernel: [13858.658090]  connection2:0: detected conn error (1020)
May 10 03:07:33 cmp02 kernel: [13861.666088]  connection2:0: detected conn error (1020)
May 10 03:07:31 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:07:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:07:36 cmp02 kernel: [13864.673260]  connection2:0: detected conn error (1020)
May 10 03:07:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:07:39 cmp02 kernel: [13867.681944]  connection2:0: detected conn error (1020)
May 10 03:07:42 cmp02 kernel: [13870.688906]  connection2:0: detected conn error (1020)
May 10 03:07:45 cmp02 kernel: [13873.697219]  connection2:0: detected conn error (1020)
May 10 03:07:46 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:07:48 cmp02 kernel: [13876.703692]  connection2:0: detected conn error (1020)
May 10 03:07:49 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:07:51 cmp02 kernel: [13879.710349]  connection2:0: detected conn error (1020)
May 10 03:07:54 cmp02 kernel: [13882.718915]  connection2:0: detected conn error (1020)
May 10 03:07:57 cmp02 kernel: [13885.726444]  connection2:0: detected conn error (1020)
May 10 03:08:00 cmp02 kernel: [13888.734927]  connection2:0: detected conn error (1020)
May 10 03:08:03 cmp02 kernel: [13891.744731]  connection2:0: detected conn error (1020)
May 10 03:08:06 cmp02 kernel: [13894.755568]  connection2:0: detected conn error (1020)
May 10 03:08:09 cmp02 kernel: [13897.762101]  connection2:0: detected conn error (1020)
May 10 03:08:12 cmp02 kernel: [13900.769790]  connection2:0: detected conn error (1020)
May 10 03:08:15 cmp02 kernel: [13903.777741]  connection2:0: detected conn error (1020)
May 10 03:08:18 cmp02 kernel: [13906.785652]  connection2:0: detected conn error (1020)
May 10 03:08:21 cmp02 kernel: [13909.794537]  connection2:0: detected conn error (1020)
May 10 03:08:24 cmp02 kernel: [13912.805075]  connection2:0: detected conn error (1020)
May 10 03:08:27 cmp02 kernel: [13915.813725]  connection2:0: detected conn error (1020)
May 10 03:08:30 cmp02 kernel: [13918.824938]  connection2:0: detected conn error (1020)
May 10 03:08:33 cmp02 kernel: [13921.834457]  connection2:0: detected conn error (1020)
May 10 03:08:31 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:08:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:08:36 cmp02 kernel: [13924.841172]  connection2:0: detected conn error (1020)
May 10 03:08:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:08:39 cmp02 kernel: [13927.851989]  connection2:0: detected conn error (1020)
May 10 03:08:42 cmp02 kernel: [13930.860928]  connection2:0: detected conn error (1020)
May 10 03:08:45 cmp02 kernel: [13933.869660]  connection2:0: detected conn error (1020)
May 10 03:08:48 cmp02 kernel: [13936.877607]  connection2:0: detected conn error (1020)
May 10 03:08:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:08:51 cmp02 kernel: [13939.887952]  connection2:0: detected conn error (1020)
May 10 03:08:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:08:54 cmp02 kernel: [13942.895714]  connection2:0: detected conn error (1020)
May 10 03:08:57 cmp02 kernel: [13945.903035]  connection2:0: detected conn error (1020)
May 10 03:09:00 cmp02 kernel: [13948.913714]  connection2:0: detected conn error (1020)
May 10 03:09:03 cmp02 kernel: [13951.924946]  connection2:0: detected conn error (1020)
May 10 03:09:06 cmp02 kernel: [13954.936719]  connection2:0: detected conn error (1020)
May 10 03:09:09 cmp02 kernel: [13957.950034]  connection2:0: detected conn error (1020)
May 10 03:09:12 cmp02 kernel: [13960.956357]  connection2:0: detected conn error (1020)
May 10 03:09:15 cmp02 kernel: [13963.966032]  connection2:0: detected conn error (1020)
May 10 03:09:18 cmp02 kernel: [13966.973268]  connection2:0: detected conn error (1020)
May 10 03:09:21 cmp02 kernel: [13969.982130]  connection2:0: detected conn error (1020)
May 10 03:09:24 cmp02 kernel: [13972.989826]  connection2:0: detected conn error (1020)
May 10 03:09:27 cmp02 kernel: [13976.001286]  connection2:0: detected conn error (1020)
May 10 03:09:30 cmp02 kernel: [13979.007329]  connection2:0: detected conn error (1020)
May 10 03:09:33 cmp02 kernel: [13982.014013]  connection2:0: detected conn error (1020)
May 10 03:09:31 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:09:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:09:36 cmp02 kernel: [13985.022186]  connection2:0: detected conn error (1020)
May 10 03:09:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:09:39 cmp02 kernel: [13988.028209]  connection2:0: detected conn error (1020)
May 10 03:09:42 cmp02 kernel: [13991.034333]  connection2:0: detected conn error (1020)
May 10 03:09:45 cmp02 kernel: [13994.040319]  connection2:0: detected conn error (1020)
May 10 03:09:48 cmp02 kernel: [13997.047074]  connection2:0: detected conn error (1020)
May 10 03:09:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:09:52 cmp02 kernel: [14000.052853]  connection2:0: detected conn error (1020)
May 10 03:09:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:09:55 cmp02 kernel: [14003.060630]  connection2:0: detected conn error (1020)
May 10 03:09:58 cmp02 kernel: [14006.068438]  connection2:0: detected conn error (1020)
May 10 03:10:01 cmp02 kernel: [14009.074611]  connection2:0: detected conn error (1020)
May 10 03:10:04 cmp02 kernel: [14012.081393]  connection2:0: detected conn error (1020)
May 10 03:10:07 cmp02 kernel: [14015.090153]  connection2:0: detected conn error (1020)
May 10 03:10:10 cmp02 kernel: [14018.096216]  connection2:0: detected conn error (1020)
May 10 03:10:13 cmp02 kernel: [14021.103347]  connection2:0: detected conn error (1020)
May 10 03:10:16 cmp02 kernel: [14024.113103]  connection2:0: detected conn error (1020)
May 10 03:10:19 cmp02 kernel: [14027.119859]  connection2:0: detected conn error (1020)
May 10 03:10:22 cmp02 kernel: [14030.132277]  connection2:0: detected conn error (1020)
May 10 03:10:25 cmp02 kernel: [14033.145311]  connection2:0: detected conn error (1020)
May 10 03:10:28 cmp02 kernel: [14036.156447]  connection2:0: detected conn error (1020)
May 10 03:10:31 cmp02 kernel: [14039.167221]  connection2:0: detected conn error (1020)
May 10 03:10:34 cmp02 kernel: [14042.175824]  connection2:0: detected conn error (1020)
May 10 03:10:31 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:10:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:10:37 cmp02 kernel: [14045.183515]  connection2:0: detected conn error (1020)
May 10 03:10:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:10:40 cmp02 kernel: [14048.192078]  connection2:0: detected conn error (1020)
May 10 03:10:43 cmp02 kernel: [14051.201512]  connection2:0: detected conn error (1020)
May 10 03:10:46 cmp02 kernel: [14054.208722]  connection2:0: detected conn error (1020)
May 10 03:10:49 cmp02 kernel: [14057.214943]  connection2:0: detected conn error (1020)
May 10 03:10:52 cmp02 kernel: [14060.222137]  connection2:0: detected conn error (1020)
May 10 03:10:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:10:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:10:55 cmp02 kernel: [14063.228647]  connection2:0: detected conn error (1020)
May 10 03:10:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:10:58 cmp02 kernel: [14066.238236]  connection2:0: detected conn error (1020)
May 10 03:11:01 cmp02 kernel: [14069.243144]  connection2:0: detected conn error (1020)
May 10 03:11:04 cmp02 kernel: [14072.249707]  connection2:0: detected conn error (1020)
May 10 03:11:07 cmp02 kernel: [14075.257057]  connection2:0: detected conn error (1020)
May 10 03:11:10 cmp02 kernel: [14078.265142]  connection2:0: detected conn error (1020)
May 10 03:11:13 cmp02 kernel: [14081.271181]  connection2:0: detected conn error (1020)
May 10 03:11:16 cmp02 kernel: [14084.280931]  connection2:0: detected conn error (1020)
May 10 03:11:19 cmp02 kernel: [14087.288529]  connection2:0: detected conn error (1020)
May 10 03:11:22 cmp02 kernel: [14090.294522]  connection2:0: detected conn error (1020)
May 10 03:11:25 cmp02 kernel: [14093.304680]  connection2:0: detected conn error (1020)
May 10 03:11:28 cmp02 kernel: [14096.313410]  connection2:0: detected conn error (1020)
May 10 03:11:31 cmp02 kernel: [14099.322932]  connection2:0: detected conn error (1020)
May 10 03:11:34 cmp02 kernel: [14102.332188]  connection2:0: detected conn error (1020)
May 10 03:11:31 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:11:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:11:37 cmp02 kernel: [14105.342163]  connection2:0: detected conn error (1020)
May 10 03:11:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:11:40 cmp02 kernel: [14108.354457]  connection2:0: detected conn error (1020)
May 10 03:11:43 cmp02 kernel: [14111.360966]  connection2:0: detected conn error (1020)
May 10 03:11:46 cmp02 kernel: [14114.368720]  connection2:0: detected conn error (1020)
May 10 03:11:49 cmp02 kernel: [14117.375673]  connection2:0: detected conn error (1020)
May 10 03:11:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:11:52 cmp02 kernel: [14120.384776]  connection2:0: detected conn error (1020)
May 10 03:11:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:11:55 cmp02 kernel: [14123.392731]  connection2:0: detected conn error (1020)
May 10 03:11:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:11:58 cmp02 kernel: [14126.401826]  connection2:0: detected conn error (1020)
May 10 03:12:01 cmp02 kernel: [14129.410310]  connection2:0: detected conn error (1020)
May 10 03:12:04 cmp02 kernel: [14132.419548]  connection2:0: detected conn error (1020)
May 10 03:12:07 cmp02 kernel: [14135.430622]  connection2:0: detected conn error (1020)
May 10 03:12:10 cmp02 kernel: [14138.439015]  connection2:0: detected conn error (1020)
May 10 03:12:13 cmp02 kernel: [14141.446393]  connection2:0: detected conn error (1020)
May 10 03:12:16 cmp02 kernel: [14144.454354]  connection2:0: detected conn error (1020)
May 10 03:12:19 cmp02 kernel: [14147.462165]  connection2:0: detected conn error (1020)
May 10 03:12:22 cmp02 kernel: [14150.471328]  connection2:0: detected conn error (1020)
May 10 03:12:25 cmp02 kernel: [14153.479512]  connection2:0: detected conn error (1020)
May 10 03:12:28 cmp02 kernel: [14156.487931]  connection2:0: detected conn error (1020)
May 10 03:12:31 cmp02 kernel: [14159.495489]  connection2:0: detected conn error (1020)
May 10 03:12:34 cmp02 kernel: [14162.502247]  connection2:0: detected conn error (1020)
May 10 03:12:31 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:12:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:12:37 cmp02 kernel: [14165.511005]  connection2:0: detected conn error (1020)
May 10 03:12:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:12:40 cmp02 kernel: [14168.519133]  connection2:0: detected conn error (1020)
May 10 03:12:43 cmp02 kernel: [14171.526439]  connection2:0: detected conn error (1020)
May 10 03:12:46 cmp02 kernel: [14174.534632]  connection2:0: detected conn error (1020)
May 10 03:12:49 cmp02 kernel: [14177.543030]  connection2:0: detected conn error (1020)
May 10 03:12:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:12:52 cmp02 kernel: [14180.550082]  connection2:0: detected conn error (1020)
May 10 03:12:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:12:55 cmp02 kernel: [14183.559695]  connection2:0: detected conn error (1020)
May 10 03:12:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:12:58 cmp02 kernel: [14186.569503]  connection2:0: detected conn error (1020)
May 10 03:13:01 cmp02 kernel: [14189.575692]  connection2:0: detected conn error (1020)
May 10 03:13:04 cmp02 kernel: [14192.582706]  connection2:0: detected conn error (1020)
May 10 03:13:07 cmp02 kernel: [14195.593329]  connection2:0: detected conn error (1020)
May 10 03:13:10 cmp02 kernel: [14198.599026]  connection2:0: detected conn error (1020)
May 10 03:13:13 cmp02 kernel: [14201.605918]  connection2:0: detected conn error (1020)
May 10 03:13:16 cmp02 kernel: [14204.613076]  connection2:0: detected conn error (1020)
May 10 03:13:19 cmp02 kernel: [14207.620777]  connection2:0: detected conn error (1020)
May 10 03:13:22 cmp02 kernel: [14210.632084]  connection2:0: detected conn error (1020)
May 10 03:13:25 cmp02 kernel: [14213.640385]  connection2:0: detected conn error (1020)
May 10 03:13:28 cmp02 kernel: [14216.650108]  connection2:0: detected conn error (1020)
May 10 03:13:31 cmp02 kernel: [14219.658509]  connection2:0: detected conn error (1020)
May 10 03:13:31 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:13:34 cmp02 kernel: [14222.667914]  connection2:0: detected conn error (1020)
May 10 03:13:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:13:37 cmp02 kernel: [14225.679195]  connection2:0: detected conn error (1020)
May 10 03:13:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:13:40 cmp02 kernel: [14228.688426]  connection2:0: detected conn error (1020)
May 10 03:13:43 cmp02 kernel: [14231.696767]  connection2:0: detected conn error (1020)
May 10 03:13:46 cmp02 kernel: [14234.704427]  connection2:0: detected conn error (1020)
May 10 03:13:49 cmp02 kernel: [14237.713225]  connection2:0: detected conn error (1020)
May 10 03:13:49 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:13:52 cmp02 kernel: [14240.720838]  connection2:0: detected conn error (1020)
May 10 03:13:52 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:13:55 cmp02 kernel: [14243.727464]  connection2:0: detected conn error (1020)
May 10 03:13:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:13:58 cmp02 kernel: [14246.733587]  connection2:0: detected conn error (1020)
May 10 03:14:01 cmp02 kernel: [14249.739690]  connection2:0: detected conn error (1020)
May 10 03:14:04 cmp02 kernel: [14252.746505]  connection2:0: detected conn error (1020)
May 10 03:14:07 cmp02 kernel: [14255.752020]  connection2:0: detected conn error (1020)
May 10 03:14:10 cmp02 kernel: [14258.761505]  connection2:0: detected conn error (1020)
May 10 03:14:13 cmp02 kernel: [14261.771476]  connection2:0: detected conn error (1020)
May 10 03:14:16 cmp02 kernel: [14264.781017]  connection2:0: detected conn error (1020)
May 10 03:14:19 cmp02 kernel: [14267.786179]  connection2:0: detected conn error (1020)
May 10 03:14:22 cmp02 kernel: [14270.794123]  connection2:0: detected conn error (1020)
May 10 03:14:25 cmp02 kernel: [14273.800973]  connection2:0: detected conn error (1020)
May 10 03:14:28 cmp02 kernel: [14276.808386]  connection2:0: detected conn error (1020)
May 10 03:14:31 cmp02 kernel: [14279.814321]  connection2:0: detected conn error (1020)
May 10 03:14:32 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:14:34 cmp02 kernel: [14282.823219]  connection2:0: detected conn error (1020)
May 10 03:14:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:14:37 cmp02 kernel: [14285.831690]  connection2:0: detected conn error (1020)
May 10 03:14:40 cmp02 kernel: [14288.839747]  connection2:0: detected conn error (1020)
May 10 03:14:43 cmp02 kernel: [14291.846833]  connection2:0: detected conn error (1020)
May 10 03:14:46 cmp02 kernel: [14294.852906]  connection2:0: detected conn error (1020)
May 10 03:14:44 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:14:47 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 03:14:47 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 03:14:47 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1490 seconds.
May 10 03:14:47 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:14:49 cmp02 kernel: [14297.860203]  connection2:0: detected conn error (1020)
May 10 03:14:52 cmp02 kernel: [14300.869071]  connection2:0: detected conn error (1020)
May 10 03:14:53 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:14:55 cmp02 kernel: [14303.883105]  connection2:0: detected conn error (1020)
May 10 03:14:56 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:14:58 cmp02 kernel: [14306.900298]  connection2:0: detected conn error (1020)
May 10 03:15:01 cmp02 kernel: [14309.906649]  connection2:0: detected conn error (1020)
May 10 03:15:04 cmp02 kernel: [14312.922668]  connection2:0: detected conn error (1020)
May 10 03:15:07 cmp02 kernel: [14315.934673]  connection2:0: detected conn error (1020)
May 10 03:15:10 cmp02 kernel: [14318.940545]  connection2:0: detected conn error (1020)
May 10 03:15:13 cmp02 kernel: [14321.959826]  connection2:0: detected conn error (1020)
May 10 03:15:16 cmp02 kernel: [14324.967524]  connection2:0: detected conn error (1020)
May 10 03:15:19 cmp02 kernel: [14327.989838]  connection2:0: detected conn error (1020)
May 10 03:15:22 cmp02 kernel: [14331.005051]  connection2:0: detected conn error (1020)
May 10 03:15:25 cmp02 kernel: [14334.012781]  connection2:0: detected conn error (1020)
May 10 03:15:28 cmp02 kernel: [14337.032483]  connection2:0: detected conn error (1020)
May 10 03:15:31 cmp02 kernel: [14340.039200]  connection2:0: detected conn error (1020)
May 10 03:15:33 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:15:34 cmp02 kernel: [14343.049155]  connection2:0: detected conn error (1020)
May 10 03:15:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:15:38 cmp02 kernel: [14346.069296]  connection2:0: detected conn error (1020)
May 10 03:15:41 cmp02 kernel: [14349.074974]  connection2:0: detected conn error (1020)
May 10 03:15:44 cmp02 kernel: [14352.095713]  connection2:0: detected conn error (1020)
May 10 03:15:47 cmp02 kernel: [14355.101613]  connection2:0: detected conn error (1020)
May 10 03:15:49 cmp02 kernel: [14357.316033] device tapbe670a0e-bf left promiscuous mode
May 10 03:15:49 cmp02 kernel: [14357.695691] audit: type=1400 audit(1525922149.634:325): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-098fa717-d565-4c41-aba5-05e6d845200a" pid=1742 comm="apparmor_parser"
May 10 03:15:48 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:15:49 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tapbe670a0e-bf
May 10 03:15:50 cmp02 kernel: [14358.107603]  connection2:0: detected conn error (1020)
May 10 03:15:51 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:15:53 cmp02 kernel: [14361.115536]  connection2:0: detected conn error (1020)
May 10 03:15:54 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:15:56 cmp02 kernel: [14364.120633]  connection2:0: detected conn error (1020)
May 10 03:15:57 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:15:59 cmp02 kernel: [14367.128226]  connection2:0: detected conn error (1020)
May 10 03:16:02 cmp02 kernel: [14370.134346]  connection2:0: detected conn error (1020)
May 10 03:16:05 cmp02 kernel: [14373.140168]  connection2:0: detected conn error (1020)
May 10 03:16:08 cmp02 kernel: [14376.148092]  connection2:0: detected conn error (1020)
May 10 03:16:11 cmp02 kernel: [14379.156274]  connection2:0: detected conn error (1020)
May 10 03:16:14 cmp02 kernel: [14382.164621]  connection2:0: detected conn error (1020)
May 10 03:16:17 cmp02 kernel: [14385.171962]  connection2:0: detected conn error (1020)
May 10 03:16:20 cmp02 kernel: [14388.179572]  connection2:0: detected conn error (1020)
May 10 03:16:23 cmp02 kernel: [14391.185985]  connection2:0: detected conn error (1020)
May 10 03:16:26 cmp02 kernel: [14394.191715]  connection2:0: detected conn error (1020)
May 10 03:16:29 cmp02 kernel: [14397.199800]  connection2:0: detected conn error (1020)
May 10 03:16:32 cmp02 kernel: [14400.208652]  connection2:0: detected conn error (1020)
May 10 03:16:33 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:16:35 cmp02 kernel: [14403.215333]  connection2:0: detected conn error (1020)
May 10 03:16:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:16:38 cmp02 kernel: [14406.222347]  connection2:0: detected conn error (1020)
May 10 03:16:41 cmp02 kernel: [14409.228519]  connection2:0: detected conn error (1020)
May 10 03:16:44 cmp02 kernel: [14412.236562]  connection2:0: detected conn error (1020)
May 10 03:16:45 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:16:45 cmp02 salt-minion[2824]: [INFO    ] Running scheduled job: __mine_interval
May 10 03:16:47 cmp02 kernel: [14415.244631]  connection2:0: detected conn error (1020)
May 10 03:16:48 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:16:50 cmp02 kernel: [14418.253103]  connection2:0: detected conn error (1020)
May 10 03:16:53 cmp02 kernel: [14421.258253]  connection2:0: detected conn error (1020)
May 10 03:16:54 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:16:56 cmp02 kernel: [14424.263892]  connection2:0: detected conn error (1020)
May 10 03:16:57 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:16:59 cmp02 kernel: [14427.273149]  connection2:0: detected conn error (1020)
May 10 03:17:00 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:17:01 cmp02 CRON[1865]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 10 03:17:02 cmp02 kernel: [14430.280493]  connection2:0: detected conn error (1020)
May 10 03:17:03 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:17:05 cmp02 kernel: [14433.286961]  connection2:0: detected conn error (1020)
May 10 03:17:08 cmp02 kernel: [14436.294289]  connection2:0: detected conn error (1020)
May 10 03:17:11 cmp02 kernel: [14439.301345]  connection2:0: detected conn error (1020)
May 10 03:17:14 cmp02 kernel: [14442.309870]  connection2:0: detected conn error (1020)
May 10 03:17:17 cmp02 kernel: [14445.317988]  connection2:0: detected conn error (1020)
May 10 03:17:20 cmp02 kernel: [14448.326348]  connection2:0: detected conn error (1020)
May 10 03:17:23 cmp02 kernel: [14451.336212]  connection2:0: detected conn error (1020)
May 10 03:17:26 cmp02 kernel: [14454.353024]  connection2:0: detected conn error (1020)
May 10 03:17:29 cmp02 kernel: [14457.362259]  connection2:0: detected conn error (1020)
May 10 03:17:32 cmp02 kernel: [14460.369712]  connection2:0: detected conn error (1020)
May 10 03:17:33 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:17:35 cmp02 kernel: [14463.379757]  connection2:0: detected conn error (1020)
May 10 03:17:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:17:38 cmp02 kernel: [14466.386539]  connection2:0: detected conn error (1020)
May 10 03:17:41 cmp02 kernel: [14469.395223]  connection2:0: detected conn error (1020)
May 10 03:17:44 cmp02 kernel: [14472.402756]  connection2:0: detected conn error (1020)
May 10 03:17:47 cmp02 kernel: [14475.409512]  connection2:0: detected conn error (1020)
May 10 03:17:50 cmp02 kernel: [14478.417244]  connection2:0: detected conn error (1020)
May 10 03:17:53 cmp02 kernel: [14481.425302]  connection2:0: detected conn error (1020)
May 10 03:17:56 cmp02 kernel: [14484.433724]  connection2:0: detected conn error (1020)
May 10 03:17:57 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:17:59 cmp02 kernel: [14487.440545]  connection2:0: detected conn error (1020)
May 10 03:18:00 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:18:02 cmp02 kernel: [14490.449743]  connection2:0: detected conn error (1020)
May 10 03:18:05 cmp02 kernel: [14493.456120]  connection2:0: detected conn error (1020)
May 10 03:18:08 cmp02 kernel: [14496.464056]  connection2:0: detected conn error (1020)
May 10 03:18:11 cmp02 kernel: [14499.470700]  connection2:0: detected conn error (1020)
May 10 03:18:14 cmp02 kernel: [14502.479094]  connection2:0: detected conn error (1020)
May 10 03:18:17 cmp02 kernel: [14505.486139]  connection2:0: detected conn error (1020)
May 10 03:18:20 cmp02 kernel: [14508.497451]  connection2:0: detected conn error (1020)
May 10 03:18:23 cmp02 kernel: [14511.505695]  connection2:0: detected conn error (1020)
May 10 03:18:26 cmp02 kernel: [14514.514607]  connection2:0: detected conn error (1020)
May 10 03:18:29 cmp02 kernel: [14517.522204]  connection2:0: detected conn error (1020)
May 10 03:18:32 cmp02 kernel: [14520.534077]  connection2:0: detected conn error (1020)
May 10 03:18:33 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:18:35 cmp02 kernel: [14523.545879]  connection2:0: detected conn error (1020)
May 10 03:18:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:18:38 cmp02 kernel: [14526.557083]  connection2:0: detected conn error (1020)
May 10 03:18:41 cmp02 kernel: [14529.565148]  connection2:0: detected conn error (1020)
May 10 03:18:44 cmp02 kernel: [14532.571985]  connection2:0: detected conn error (1020)
May 10 03:18:47 cmp02 kernel: [14535.580586]  connection2:0: detected conn error (1020)
May 10 03:18:50 cmp02 kernel: [14538.587920]  connection2:0: detected conn error (1020)
May 10 03:18:53 cmp02 kernel: [14541.594014]  connection2:0: detected conn error (1020)
May 10 03:18:56 cmp02 kernel: [14544.605673]  connection2:0: detected conn error (1020)
May 10 03:18:57 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:18:59 cmp02 kernel: [14547.611990]  connection2:0: detected conn error (1020)
May 10 03:19:00 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:19:02 cmp02 kernel: [14550.620175]  connection2:0: detected conn error (1020)
May 10 03:19:05 cmp02 kernel: [14553.629745]  connection2:0: detected conn error (1020)
May 10 03:19:08 cmp02 kernel: [14556.640060]  connection2:0: detected conn error (1020)
May 10 03:19:11 cmp02 kernel: [14559.647210]  connection2:0: detected conn error (1020)
May 10 03:19:14 cmp02 kernel: [14562.661364]  connection2:0: detected conn error (1020)
May 10 03:19:17 cmp02 kernel: [14565.674311]  connection2:0: detected conn error (1020)
May 10 03:19:20 cmp02 kernel: [14568.682653]  connection2:0: detected conn error (1020)
May 10 03:19:23 cmp02 kernel: [14571.690374]  connection2:0: detected conn error (1020)
May 10 03:19:26 cmp02 kernel: [14574.698726]  connection2:0: detected conn error (1020)
May 10 03:19:29 cmp02 kernel: [14577.706126]  connection2:0: detected conn error (1020)
May 10 03:19:32 cmp02 kernel: [14580.714373]  connection2:0: detected conn error (1020)
May 10 03:19:33 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:19:35 cmp02 kernel: [14583.722543]  connection2:0: detected conn error (1020)
May 10 03:19:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:19:38 cmp02 kernel: [14586.731936]  connection2:0: detected conn error (1020)
May 10 03:19:41 cmp02 kernel: [14589.739857]  connection2:0: detected conn error (1020)
May 10 03:19:44 cmp02 kernel: [14592.745894]  connection2:0: detected conn error (1020)
May 10 03:19:47 cmp02 kernel: [14595.756322]  connection2:0: detected conn error (1020)
May 10 03:19:50 cmp02 kernel: [14598.763773]  connection2:0: detected conn error (1020)
May 10 03:19:53 cmp02 kernel: [14601.770825]  connection2:0: detected conn error (1020)
May 10 03:19:56 cmp02 kernel: [14604.780178]  connection2:0: detected conn error (1020)
May 10 03:19:59 cmp02 kernel: [14607.787071]  connection2:0: detected conn error (1020)
May 10 03:20:00 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:20:02 cmp02 kernel: [14610.794177]  connection2:0: detected conn error (1020)
May 10 03:20:03 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:20:05 cmp02 kernel: [14613.799223]  connection2:0: detected conn error (1020)
May 10 03:20:08 cmp02 kernel: [14616.807560]  connection2:0: detected conn error (1020)
May 10 03:20:11 cmp02 kernel: [14619.813738]  connection2:0: detected conn error (1020)
May 10 03:20:14 cmp02 kernel: [14622.824488]  connection2:0: detected conn error (1020)
May 10 03:20:17 cmp02 kernel: [14625.835219]  connection2:0: detected conn error (1020)
May 10 03:20:20 cmp02 kernel: [14628.843890]  connection2:0: detected conn error (1020)
May 10 03:20:23 cmp02 kernel: [14631.852484]  connection2:0: detected conn error (1020)
May 10 03:20:26 cmp02 kernel: [14634.860904]  connection2:0: detected conn error (1020)
May 10 03:20:29 cmp02 kernel: [14637.868869]  connection2:0: detected conn error (1020)
May 10 03:20:32 cmp02 kernel: [14640.876442]  connection2:0: detected conn error (1020)
May 10 03:20:33 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:20:35 cmp02 kernel: [14643.885763]  connection2:0: detected conn error (1020)
May 10 03:20:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:20:38 cmp02 kernel: [14646.894457]  connection2:0: detected conn error (1020)
May 10 03:20:41 cmp02 kernel: [14649.900736]  connection2:0: detected conn error (1020)
May 10 03:20:44 cmp02 kernel: [14652.908615]  connection2:0: detected conn error (1020)
May 10 03:20:47 cmp02 kernel: [14655.919781]  connection2:0: detected conn error (1020)
May 10 03:20:50 cmp02 kernel: [14658.928505]  connection2:0: detected conn error (1020)
May 10 03:20:53 cmp02 kernel: [14661.936255]  connection2:0: detected conn error (1020)
May 10 03:20:56 cmp02 kernel: [14664.944167]  connection2:0: detected conn error (1020)
May 10 03:20:59 cmp02 kernel: [14667.954758]  connection2:0: detected conn error (1020)
May 10 03:20:57 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:21:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:21:02 cmp02 kernel: [14670.962320]  connection2:0: detected conn error (1020)
May 10 03:21:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:21:05 cmp02 kernel: [14673.968678]  connection2:0: detected conn error (1020)
May 10 03:21:08 cmp02 kernel: [14676.975631]  connection2:0: detected conn error (1020)
May 10 03:21:11 cmp02 kernel: [14679.987338]  connection2:0: detected conn error (1020)
May 10 03:21:14 cmp02 kernel: [14682.995046]  connection2:0: detected conn error (1020)
May 10 03:21:17 cmp02 kernel: [14686.005784]  connection2:0: detected conn error (1020)
May 10 03:21:20 cmp02 kernel: [14689.014351]  connection2:0: detected conn error (1020)
May 10 03:21:23 cmp02 kernel: [14692.025101]  connection2:0: detected conn error (1020)
May 10 03:21:26 cmp02 kernel: [14695.033978]  connection2:0: detected conn error (1020)
May 10 03:21:29 cmp02 kernel: [14698.039870]  connection2:0: detected conn error (1020)
May 10 03:21:32 cmp02 kernel: [14701.048789]  connection2:0: detected conn error (1020)
May 10 03:21:34 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:21:35 cmp02 kernel: [14704.059259]  connection2:0: detected conn error (1020)
May 10 03:21:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:21:39 cmp02 kernel: [14707.068472]  connection2:0: detected conn error (1020)
May 10 03:21:42 cmp02 kernel: [14710.076000]  connection2:0: detected conn error (1020)
May 10 03:21:45 cmp02 kernel: [14713.083544]  connection2:0: detected conn error (1020)
May 10 03:21:48 cmp02 kernel: [14716.090231]  connection2:0: detected conn error (1020)
May 10 03:21:51 cmp02 kernel: [14719.097647]  connection2:0: detected conn error (1020)
May 10 03:21:54 cmp02 kernel: [14722.108283]  connection2:0: detected conn error (1020)
May 10 03:21:57 cmp02 kernel: [14725.118750]  connection2:0: detected conn error (1020)
May 10 03:22:00 cmp02 kernel: [14728.129259]  connection2:0: detected conn error (1020)
May 10 03:21:58 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:22:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:22:03 cmp02 kernel: [14731.136408]  connection2:0: detected conn error (1020)
May 10 03:22:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:22:06 cmp02 kernel: [14734.144944]  connection2:0: detected conn error (1020)
May 10 03:22:09 cmp02 kernel: [14737.153894]  connection2:0: detected conn error (1020)
May 10 03:22:12 cmp02 kernel: [14740.162769]  connection2:0: detected conn error (1020)
May 10 03:22:15 cmp02 kernel: [14743.171306]  connection2:0: detected conn error (1020)
May 10 03:22:18 cmp02 kernel: [14746.178273]  connection2:0: detected conn error (1020)
May 10 03:22:21 cmp02 kernel: [14749.185887]  connection2:0: detected conn error (1020)
May 10 03:22:24 cmp02 kernel: [14752.193189]  connection2:0: detected conn error (1020)
May 10 03:22:27 cmp02 kernel: [14755.199922]  connection2:0: detected conn error (1020)
May 10 03:22:30 cmp02 kernel: [14758.206514]  connection2:0: detected conn error (1020)
May 10 03:22:33 cmp02 kernel: [14761.213095]  connection2:0: detected conn error (1020)
May 10 03:22:34 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:22:36 cmp02 kernel: [14764.220915]  connection2:0: detected conn error (1020)
May 10 03:22:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:22:39 cmp02 kernel: [14767.230236]  connection2:0: detected conn error (1020)
May 10 03:22:42 cmp02 kernel: [14770.240204]  connection2:0: detected conn error (1020)
May 10 03:22:45 cmp02 kernel: [14773.248149]  connection2:0: detected conn error (1020)
May 10 03:22:48 cmp02 kernel: [14776.257383]  connection2:0: detected conn error (1020)
May 10 03:22:51 cmp02 kernel: [14779.268367]  connection2:0: detected conn error (1020)
May 10 03:22:54 cmp02 kernel: [14782.279593]  connection2:0: detected conn error (1020)
May 10 03:22:57 cmp02 kernel: [14785.286695]  connection2:0: detected conn error (1020)
May 10 03:23:00 cmp02 kernel: [14788.292763]  connection2:0: detected conn error (1020)
May 10 03:22:58 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:23:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:23:03 cmp02 kernel: [14791.302283]  connection2:0: detected conn error (1020)
May 10 03:23:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:23:06 cmp02 kernel: [14794.314390]  connection2:0: detected conn error (1020)
May 10 03:23:09 cmp02 kernel: [14797.320929]  connection2:0: detected conn error (1020)
May 10 03:23:12 cmp02 kernel: [14800.329293]  connection2:0: detected conn error (1020)
May 10 03:23:15 cmp02 kernel: [14803.337413]  connection2:0: detected conn error (1020)
May 10 03:23:18 cmp02 kernel: [14806.345304]  connection2:0: detected conn error (1020)
May 10 03:23:21 cmp02 kernel: [14809.353926]  connection2:0: detected conn error (1020)
May 10 03:23:24 cmp02 kernel: [14812.360252]  connection2:0: detected conn error (1020)
May 10 03:23:27 cmp02 kernel: [14815.371929]  connection2:0: detected conn error (1020)
May 10 03:23:30 cmp02 kernel: [14818.380125]  connection2:0: detected conn error (1020)
May 10 03:23:33 cmp02 kernel: [14821.387973]  connection2:0: detected conn error (1020)
May 10 03:23:34 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:23:36 cmp02 kernel: [14824.396979]  connection2:0: detected conn error (1020)
May 10 03:23:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:23:39 cmp02 kernel: [14827.405981]  connection2:0: detected conn error (1020)
May 10 03:23:42 cmp02 kernel: [14830.412110]  connection2:0: detected conn error (1020)
May 10 03:23:45 cmp02 kernel: [14833.419452]  connection2:0: detected conn error (1020)
May 10 03:23:48 cmp02 kernel: [14836.430810]  connection2:0: detected conn error (1020)
May 10 03:23:51 cmp02 kernel: [14839.438039]  connection2:0: detected conn error (1020)
May 10 03:23:54 cmp02 kernel: [14842.445270]  connection2:0: detected conn error (1020)
May 10 03:23:57 cmp02 kernel: [14845.452518]  connection2:0: detected conn error (1020)
May 10 03:23:58 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:24:00 cmp02 kernel: [14848.462608]  connection2:0: detected conn error (1020)
May 10 03:24:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:24:03 cmp02 kernel: [14851.470564]  connection2:0: detected conn error (1020)
May 10 03:24:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:24:06 cmp02 kernel: [14854.476897]  connection2:0: detected conn error (1020)
May 10 03:24:09 cmp02 kernel: [14857.483840]  connection2:0: detected conn error (1020)
May 10 03:24:12 cmp02 kernel: [14860.493162]  connection2:0: detected conn error (1020)
May 10 03:24:15 cmp02 kernel: [14863.500899]  connection2:0: detected conn error (1020)
May 10 03:24:18 cmp02 kernel: [14866.506435]  connection2:0: detected conn error (1020)
May 10 03:24:21 cmp02 kernel: [14869.514485]  connection2:0: detected conn error (1020)
May 10 03:24:24 cmp02 kernel: [14872.522877]  connection2:0: detected conn error (1020)
May 10 03:24:27 cmp02 kernel: [14875.529147]  connection2:0: detected conn error (1020)
May 10 03:24:30 cmp02 kernel: [14878.534870]  connection2:0: detected conn error (1020)
May 10 03:24:33 cmp02 kernel: [14881.546979]  connection2:0: detected conn error (1020)
May 10 03:24:34 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:24:36 cmp02 kernel: [14884.555383]  connection2:0: detected conn error (1020)
May 10 03:24:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:24:39 cmp02 kernel: [14887.562690]  connection2:0: detected conn error (1020)
May 10 03:24:42 cmp02 kernel: [14890.571190]  connection2:0: detected conn error (1020)
May 10 03:24:45 cmp02 kernel: [14893.580397]  connection2:0: detected conn error (1020)
May 10 03:24:48 cmp02 kernel: [14896.585874]  connection2:0: detected conn error (1020)
May 10 03:24:51 cmp02 kernel: [14899.594900]  connection2:0: detected conn error (1020)
May 10 03:24:54 cmp02 kernel: [14902.602594]  connection2:0: detected conn error (1020)
May 10 03:24:57 cmp02 kernel: [14905.635230]  connection2:0: detected conn error (1020)
May 10 03:25:00 cmp02 kernel: [14908.671894]  connection2:0: detected conn error (1020)
May 10 03:24:58 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:25:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:25:03 cmp02 kernel: [14911.680737]  connection2:0: detected conn error (1020)
May 10 03:25:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:25:06 cmp02 kernel: [14914.689277]  connection2:0: detected conn error (1020)
May 10 03:25:09 cmp02 kernel: [14917.698225]  connection2:0: detected conn error (1020)
May 10 03:25:12 cmp02 kernel: [14920.705310]  connection2:0: detected conn error (1020)
May 10 03:25:15 cmp02 kernel: [14923.715829]  connection2:0: detected conn error (1020)
May 10 03:25:18 cmp02 kernel: [14926.722920]  connection2:0: detected conn error (1020)
May 10 03:25:21 cmp02 kernel: [14929.733054]  connection2:0: detected conn error (1020)
May 10 03:25:24 cmp02 kernel: [14932.744362]  connection2:0: detected conn error (1020)
May 10 03:25:27 cmp02 kernel: [14935.753692]  connection2:0: detected conn error (1020)
May 10 03:25:30 cmp02 kernel: [14938.761086]  connection2:0: detected conn error (1020)
May 10 03:25:33 cmp02 kernel: [14941.768015]  connection2:0: detected conn error (1020)
May 10 03:25:34 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:25:36 cmp02 kernel: [14944.777272]  connection2:0: detected conn error (1020)
May 10 03:25:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:25:39 cmp02 kernel: [14947.783760]  connection2:0: detected conn error (1020)
May 10 03:25:42 cmp02 kernel: [14950.790285]  connection2:0: detected conn error (1020)
May 10 03:25:45 cmp02 kernel: [14953.796615]  connection2:0: detected conn error (1020)
May 10 03:25:48 cmp02 kernel: [14956.804854]  connection2:0: detected conn error (1020)
May 10 03:25:51 cmp02 kernel: [14959.816092]  connection2:0: detected conn error (1020)
May 10 03:25:54 cmp02 kernel: [14962.826127]  connection2:0: detected conn error (1020)
May 10 03:25:57 cmp02 kernel: [14965.832506]  connection2:0: detected conn error (1020)
May 10 03:26:00 cmp02 kernel: [14968.842125]  connection2:0: detected conn error (1020)
May 10 03:25:58 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:26:01 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:26:03 cmp02 kernel: [14971.848470]  connection2:0: detected conn error (1020)
May 10 03:26:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:26:06 cmp02 kernel: [14974.862193]  connection2:0: detected conn error (1020)
May 10 03:26:09 cmp02 kernel: [14977.867891]  connection2:0: detected conn error (1020)
May 10 03:26:12 cmp02 kernel: [14980.879451]  connection2:0: detected conn error (1020)
May 10 03:26:15 cmp02 kernel: [14983.886647]  connection2:0: detected conn error (1020)
May 10 03:26:18 cmp02 kernel: [14986.895230]  connection2:0: detected conn error (1020)
May 10 03:26:21 cmp02 kernel: [14989.904180]  connection2:0: detected conn error (1020)
May 10 03:26:24 cmp02 kernel: [14992.915436]  connection2:0: detected conn error (1020)
May 10 03:26:27 cmp02 kernel: [14995.925073]  connection2:0: detected conn error (1020)
May 10 03:26:30 cmp02 kernel: [14998.934330]  connection2:0: detected conn error (1020)
May 10 03:26:33 cmp02 kernel: [15001.944694]  connection2:0: detected conn error (1020)
May 10 03:26:34 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:26:36 cmp02 kernel: [15004.953290]  connection2:0: detected conn error (1020)
May 10 03:26:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:26:39 cmp02 kernel: [15007.958868]  connection2:0: detected conn error (1020)
May 10 03:26:42 cmp02 kernel: [15010.966068]  connection2:0: detected conn error (1020)
May 10 03:26:45 cmp02 kernel: [15013.973183]  connection2:0: detected conn error (1020)
May 10 03:26:48 cmp02 kernel: [15016.981008]  connection2:0: detected conn error (1020)
May 10 03:26:51 cmp02 kernel: [15019.990788]  connection2:0: detected conn error (1020)
May 10 03:26:54 cmp02 kernel: [15023.008379]  connection2:0: detected conn error (1020)
May 10 03:26:57 cmp02 kernel: [15026.016647]  connection2:0: detected conn error (1020)
May 10 03:27:00 cmp02 kernel: [15029.027782]  connection2:0: detected conn error (1020)
May 10 03:27:01 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:27:03 cmp02 kernel: [15032.034084]  connection2:0: detected conn error (1020)
May 10 03:27:04 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:27:06 cmp02 kernel: [15035.042662]  connection2:0: detected conn error (1020)
May 10 03:27:07 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:27:09 cmp02 kernel: [15038.049601]  connection2:0: detected conn error (1020)
May 10 03:27:12 cmp02 kernel: [15041.056010]  connection2:0: detected conn error (1020)
May 10 03:27:15 cmp02 kernel: [15044.063555]  connection2:0: detected conn error (1020)
May 10 03:27:16 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:27:18 cmp02 kernel: [15047.069230]  connection2:0: detected conn error (1020)
May 10 03:27:19 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:27:20 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 03:27:21 cmp02 kernel: [15050.018082] audit: type=1400 audit(1525922841.944:326): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-61160985-7c48-4d13-a0fe-76b7c1b4ba0b" pid=2636 comm="apparmor_parser"
May 10 03:27:22 cmp02 kernel: [15050.076223]  connection2:0: detected conn error (1020)
May 10 03:27:22 cmp02 kernel: [15050.270837] audit: type=1400 audit(1525922842.197:327): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-61160985-7c48-4d13-a0fe-76b7c1b4ba0b" pid=2639 comm="apparmor_parser"
May 10 03:27:22 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:27:22 cmp02 kernel: [15050.513945] audit: type=1400 audit(1525922842.440:328): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-61160985-7c48-4d13-a0fe-76b7c1b4ba0b" pid=2642 comm="apparmor_parser"
May 10 03:27:22 cmp02 kernel: [15050.771444] audit: type=1400 audit(1525922842.697:329): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-61160985-7c48-4d13-a0fe-76b7c1b4ba0b" pid=2645 comm="apparmor_parser"
May 10 03:27:22 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap4e58bce0-50 -- add-port br-int tap4e58bce0-50 -- set Interface tap4e58bce0-50 "external-ids:attached-mac=\"fa:16:3e:72:48:a7\"" -- set Interface tap4e58bce0-50 "external-ids:iface-id=\"4e58bce0-505d-4579-bdb0-fd5ad592c9ec\"" -- set Interface tap4e58bce0-50 "external-ids:vm-id=\"61160985-7c48-4d13-a0fe-76b7c1b4ba0b\"" -- set Interface tap4e58bce0-50 external-ids:iface-status=active
May 10 03:27:22 cmp02 kernel: [15050.800803] device tap4e58bce0-50 entered promiscuous mode
May 10 03:27:22 cmp02 kernel: [15051.034501] audit: type=1400 audit(1525922842.960:330): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-61160985-7c48-4d13-a0fe-76b7c1b4ba0b" pid=2745 comm="apparmor_parser"
May 10 03:27:22 cmp02 libvirtd[5599]: 2018-05-10 03:27:22.968+0000: 5611: warning : qemuDomainObjTaint:5532 : Domain id=51 name='instance-0000006f' uuid=61160985-7c48-4d13-a0fe-76b7c1b4ba0b is tainted: host-cpu
May 10 03:27:25 cmp02 kernel: [15053.081670]  connection2:0: detected conn error (1020)
May 10 03:27:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:27:28 cmp02 kernel: [15056.091728]  connection2:0: detected conn error (1020)
May 10 03:27:31 cmp02 kernel: [15059.096469]  connection2:0: detected conn error (1020)
May 10 03:27:34 cmp02 kernel: [15062.101944]  connection2:0: detected conn error (1020)
May 10 03:27:34 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:27:37 cmp02 kernel: [15065.110468]  connection2:0: detected conn error (1020)
May 10 03:27:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:27:40 cmp02 kernel: [15068.116326]  connection2:0: detected conn error (1020)
May 10 03:27:43 cmp02 kernel: [15071.129154]  connection2:0: detected conn error (1020)
May 10 03:27:46 cmp02 kernel: [15074.135466]  connection2:0: detected conn error (1020)
May 10 03:27:49 cmp02 kernel: [15077.142640]  connection2:0: detected conn error (1020)
May 10 03:27:52 cmp02 kernel: [15080.149053]  connection2:0: detected conn error (1020)
May 10 03:27:55 cmp02 kernel: [15083.155337]  connection2:0: detected conn error (1020)
May 10 03:27:58 cmp02 kernel: [15086.161179]  connection2:0: detected conn error (1020)
May 10 03:28:01 cmp02 kernel: [15089.169924]  connection2:0: detected conn error (1020)
May 10 03:28:04 cmp02 kernel: [15092.175729]  connection2:0: detected conn error (1020)
May 10 03:28:02 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:28:05 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:28:07 cmp02 kernel: [15095.182635]  connection2:0: detected conn error (1020)
May 10 03:28:08 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:28:10 cmp02 kernel: [15098.188624]  connection2:0: detected conn error (1020)
May 10 03:28:13 cmp02 kernel: [15101.195150]  connection2:0: detected conn error (1020)
May 10 03:28:16 cmp02 kernel: [15104.201899]  connection2:0: detected conn error (1020)
May 10 03:28:19 cmp02 kernel: [15107.209485]  connection2:0: detected conn error (1020)
May 10 03:28:22 cmp02 kernel: [15110.214628]  connection2:0: detected conn error (1020)
May 10 03:28:25 cmp02 kernel: [15113.221657]  connection2:0: detected conn error (1020)
May 10 03:28:28 cmp02 kernel: [15116.227699]  connection2:0: detected conn error (1020)
May 10 03:28:31 cmp02 kernel: [15119.235837]  connection2:0: detected conn error (1020)
May 10 03:28:34 cmp02 kernel: [15122.244147]  connection2:0: detected conn error (1020)
May 10 03:28:32 cmp02 iscsid: message repeated 8 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:28:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:28:37 cmp02 kernel: [15125.254015]  connection2:0: detected conn error (1020)
May 10 03:28:40 cmp02 kernel: [15128.259827]  connection2:0: detected conn error (1020)
May 10 03:28:43 cmp02 kernel: [15131.269358]  connection2:0: detected conn error (1020)
May 10 03:28:46 cmp02 kernel: [15134.275393]  connection2:0: detected conn error (1020)
May 10 03:28:49 cmp02 kernel: [15137.282903]  connection2:0: detected conn error (1020)
May 10 03:28:52 cmp02 kernel: [15140.291164]  connection2:0: detected conn error (1020)
May 10 03:28:55 cmp02 kernel: [15143.299729]  connection2:0: detected conn error (1020)
May 10 03:28:58 cmp02 kernel: [15146.311418]  connection2:0: detected conn error (1020)
May 10 03:29:01 cmp02 kernel: [15149.320300]  connection2:0: detected conn error (1020)
May 10 03:29:04 cmp02 kernel: [15152.325616]  connection2:0: detected conn error (1020)
May 10 03:29:05 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:29:07 cmp02 kernel: [15155.333258]  connection2:0: detected conn error (1020)
May 10 03:29:08 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:29:10 cmp02 kernel: [15158.341012]  connection2:0: detected conn error (1020)
May 10 03:29:11 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:29:13 cmp02 kernel: [15161.347493]  connection2:0: detected conn error (1020)
May 10 03:29:16 cmp02 kernel: [15164.355683]  connection2:0: detected conn error (1020)
May 10 03:29:19 cmp02 kernel: [15167.362023]  connection2:0: detected conn error (1020)
May 10 03:29:22 cmp02 kernel: [15170.369305]  connection2:0: detected conn error (1020)
May 10 03:29:25 cmp02 kernel: [15173.376854]  connection2:0: detected conn error (1020)
May 10 03:29:28 cmp02 kernel: [15176.383215]  connection2:0: detected conn error (1020)
May 10 03:29:31 cmp02 kernel: [15179.389293]  connection2:0: detected conn error (1020)
May 10 03:29:34 cmp02 kernel: [15182.395805]  connection2:0: detected conn error (1020)
May 10 03:29:32 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:29:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:29:37 cmp02 kernel: [15185.400991]  connection2:0: detected conn error (1020)
May 10 03:29:40 cmp02 kernel: [15188.411473]  connection2:0: detected conn error (1020)
May 10 03:29:43 cmp02 kernel: [15191.418408]  connection2:0: detected conn error (1020)
May 10 03:29:46 cmp02 kernel: [15194.422996]  connection2:0: detected conn error (1020)
May 10 03:29:49 cmp02 kernel: [15197.429462]  connection2:0: detected conn error (1020)
May 10 03:29:52 cmp02 kernel: [15200.440039]  connection2:0: detected conn error (1020)
May 10 03:29:55 cmp02 kernel: [15203.448137]  connection2:0: detected conn error (1020)
May 10 03:29:58 cmp02 kernel: [15206.454393]  connection2:0: detected conn error (1020)
May 10 03:30:01 cmp02 kernel: [15209.462530]  connection2:0: detected conn error (1020)
May 10 03:30:04 cmp02 kernel: [15212.469772]  connection2:0: detected conn error (1020)
May 10 03:30:07 cmp02 kernel: [15215.479290]  connection2:0: detected conn error (1020)
May 10 03:30:05 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:30:08 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:30:10 cmp02 kernel: [15218.488884]  connection2:0: detected conn error (1020)
May 10 03:30:11 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:30:13 cmp02 kernel: [15221.496721]  connection2:0: detected conn error (1020)
May 10 03:30:16 cmp02 kernel: [15224.504079]  connection2:0: detected conn error (1020)
May 10 03:30:19 cmp02 kernel: [15227.510000]  connection2:0: detected conn error (1020)
May 10 03:30:22 cmp02 kernel: [15230.518061]  connection2:0: detected conn error (1020)
May 10 03:30:25 cmp02 kernel: [15233.525262]  connection2:0: detected conn error (1020)
May 10 03:30:28 cmp02 kernel: [15236.535968]  connection2:0: detected conn error (1020)
May 10 03:30:31 cmp02 kernel: [15239.542911]  connection2:0: detected conn error (1020)
May 10 03:30:34 cmp02 kernel: [15242.550141]  connection2:0: detected conn error (1020)
May 10 03:30:32 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:30:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:30:37 cmp02 kernel: [15245.557523]  connection2:0: detected conn error (1020)
May 10 03:30:40 cmp02 kernel: [15248.564375]  connection2:0: detected conn error (1020)
May 10 03:30:43 cmp02 kernel: [15251.569959]  connection2:0: detected conn error (1020)
May 10 03:30:46 cmp02 kernel: [15254.579358]  connection2:0: detected conn error (1020)
May 10 03:30:49 cmp02 kernel: [15257.583885]  connection2:0: detected conn error (1020)
May 10 03:30:52 cmp02 kernel: [15260.595305]  connection2:0: detected conn error (1020)
May 10 03:30:55 cmp02 kernel: [15263.604609]  connection2:0: detected conn error (1020)
May 10 03:30:58 cmp02 kernel: [15266.615015]  connection2:0: detected conn error (1020)
May 10 03:31:01 cmp02 kernel: [15269.623447]  connection2:0: detected conn error (1020)
May 10 03:31:04 cmp02 kernel: [15272.631564]  connection2:0: detected conn error (1020)
May 10 03:31:07 cmp02 kernel: [15275.643146]  connection2:0: detected conn error (1020)
May 10 03:31:05 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:31:08 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:31:10 cmp02 kernel: [15278.652699]  connection2:0: detected conn error (1020)
May 10 03:31:11 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:31:13 cmp02 kernel: [15281.663994]  connection2:0: detected conn error (1020)
May 10 03:31:16 cmp02 kernel: [15284.670062]  connection2:0: detected conn error (1020)
May 10 03:31:19 cmp02 kernel: [15287.680007]  connection2:0: detected conn error (1020)
May 10 03:31:22 cmp02 kernel: [15290.688406]  connection2:0: detected conn error (1020)
May 10 03:31:25 cmp02 kernel: [15293.701112]  connection2:0: detected conn error (1020)
May 10 03:31:28 cmp02 kernel: [15296.708190]  connection2:0: detected conn error (1020)
May 10 03:31:31 cmp02 kernel: [15299.714392]  connection2:0: detected conn error (1020)
May 10 03:31:32 cmp02 iscsid: message repeated 7 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:31:34 cmp02 kernel: [15302.721309]  connection2:0: detected conn error (1020)
May 10 03:31:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:31:37 cmp02 kernel: [15305.728903]  connection2:0: detected conn error (1020)
May 10 03:31:40 cmp02 kernel: [15308.735757]  connection2:0: detected conn error (1020)
May 10 03:31:43 cmp02 kernel: [15311.742988]  connection2:0: detected conn error (1020)
May 10 03:31:46 cmp02 kernel: [15314.750382]  connection2:0: detected conn error (1020)
May 10 03:31:49 cmp02 kernel: [15317.757265]  connection2:0: detected conn error (1020)
May 10 03:31:52 cmp02 kernel: [15320.765729]  connection2:0: detected conn error (1020)
May 10 03:31:55 cmp02 kernel: [15323.775913]  connection2:0: detected conn error (1020)
May 10 03:31:58 cmp02 kernel: [15326.783288]  connection2:0: detected conn error (1020)
May 10 03:32:01 cmp02 kernel: [15329.793810]  connection2:0: detected conn error (1020)
May 10 03:32:04 cmp02 kernel: [15332.803467]  connection2:0: detected conn error (1020)
May 10 03:32:07 cmp02 kernel: [15335.813084]  connection2:0: detected conn error (1020)
May 10 03:32:08 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:32:10 cmp02 kernel: [15338.819509]  connection2:0: detected conn error (1020)
May 10 03:32:11 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:32:13 cmp02 kernel: [15341.825717]  connection2:0: detected conn error (1020)
May 10 03:32:14 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:32:16 cmp02 kernel: [15344.833559]  connection2:0: detected conn error (1020)
May 10 03:32:19 cmp02 kernel: [15347.842915]  connection2:0: detected conn error (1020)
May 10 03:32:22 cmp02 kernel: [15350.856455]  connection2:0: detected conn error (1020)
May 10 03:32:25 cmp02 kernel: [15353.861698]  connection2:0: detected conn error (1020)
May 10 03:32:28 cmp02 kernel: [15356.869515]  connection2:0: detected conn error (1020)
May 10 03:32:31 cmp02 kernel: [15359.876611]  connection2:0: detected conn error (1020)
May 10 03:32:32 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:32:34 cmp02 kernel: [15362.883000]  connection2:0: detected conn error (1020)
May 10 03:32:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:32:37 cmp02 kernel: [15365.892971]  connection2:0: detected conn error (1020)
May 10 03:32:40 cmp02 kernel: [15368.899711]  connection2:0: detected conn error (1020)
May 10 03:32:43 cmp02 kernel: [15371.909890]  connection2:0: detected conn error (1020)
May 10 03:32:46 cmp02 kernel: [15374.920353]  connection2:0: detected conn error (1020)
May 10 03:32:49 cmp02 kernel: [15377.927890]  connection2:0: detected conn error (1020)
May 10 03:32:52 cmp02 kernel: [15380.939448]  connection2:0: detected conn error (1020)
May 10 03:32:55 cmp02 kernel: [15383.946401]  connection2:0: detected conn error (1020)
May 10 03:32:58 cmp02 kernel: [15386.954843]  connection2:0: detected conn error (1020)
May 10 03:33:01 cmp02 kernel: [15389.961698]  connection2:0: detected conn error (1020)
May 10 03:33:04 cmp02 kernel: [15392.967537]  connection2:0: detected conn error (1020)
May 10 03:33:07 cmp02 kernel: [15395.975078]  connection2:0: detected conn error (1020)
May 10 03:33:10 cmp02 kernel: [15398.981285]  connection2:0: detected conn error (1020)
May 10 03:33:08 cmp02 iscsid: message repeated 11 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:33:11 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:33:13 cmp02 kernel: [15401.989285]  connection2:0: detected conn error (1020)
May 10 03:33:14 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:33:16 cmp02 kernel: [15405.008422]  connection2:0: detected conn error (1020)
May 10 03:33:19 cmp02 kernel: [15408.016601]  connection2:0: detected conn error (1020)
May 10 03:33:22 cmp02 kernel: [15411.038880]  connection2:0: detected conn error (1020)
May 10 03:33:25 cmp02 kernel: [15414.059506]  connection2:0: detected conn error (1020)
May 10 03:33:28 cmp02 kernel: [15417.066718]  connection2:0: detected conn error (1020)
May 10 03:33:32 cmp02 kernel: [15420.087283]  connection2:0: detected conn error (1020)
May 10 03:33:32 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:33:35 cmp02 kernel: [15423.095684]  connection2:0: detected conn error (1020)
May 10 03:33:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:33:38 cmp02 kernel: [15426.115339]  connection2:0: detected conn error (1020)
May 10 03:33:41 cmp02 kernel: [15429.133471]  connection2:0: detected conn error (1020)
May 10 03:33:44 cmp02 kernel: [15432.140186]  connection2:0: detected conn error (1020)
May 10 03:33:47 cmp02 kernel: [15435.149195]  connection2:0: detected conn error (1020)
May 10 03:33:50 cmp02 kernel: [15438.164429]  connection2:0: detected conn error (1020)
May 10 03:33:53 cmp02 kernel: [15441.173934]  connection2:0: detected conn error (1020)
May 10 03:33:56 cmp02 kernel: [15444.180219]  connection2:0: detected conn error (1020)
May 10 03:33:59 cmp02 kernel: [15447.195209]  connection2:0: detected conn error (1020)
May 10 03:34:02 cmp02 kernel: [15450.202055]  connection2:0: detected conn error (1020)
May 10 03:34:05 cmp02 kernel: [15453.208310]  connection2:0: detected conn error (1020)
May 10 03:34:08 cmp02 kernel: [15456.215725]  connection2:0: detected conn error (1020)
May 10 03:34:11 cmp02 kernel: [15459.222807]  connection2:0: detected conn error (1020)
May 10 03:34:11 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:34:14 cmp02 kernel: [15462.229555]  connection2:0: detected conn error (1020)
May 10 03:34:14 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:34:17 cmp02 kernel: [15465.234781]  connection2:0: detected conn error (1020)
May 10 03:34:20 cmp02 kernel: [15468.243404]  connection2:0: detected conn error (1020)
May 10 03:34:23 cmp02 kernel: [15471.255296]  connection2:0: detected conn error (1020)
May 10 03:34:26 cmp02 kernel: [15474.263358]  connection2:0: detected conn error (1020)
May 10 03:34:29 cmp02 kernel: [15477.269576]  connection2:0: detected conn error (1020)
May 10 03:34:32 cmp02 kernel: [15480.276552]  connection2:0: detected conn error (1020)
May 10 03:34:32 cmp02 iscsid: message repeated 6 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:34:35 cmp02 kernel: [15483.283234]  connection2:0: detected conn error (1020)
May 10 03:34:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:34:38 cmp02 kernel: [15486.292739]  connection2:0: detected conn error (1020)
May 10 03:34:41 cmp02 kernel: [15489.301573]  connection2:0: detected conn error (1020)
May 10 03:34:44 cmp02 kernel: [15492.308785]  connection2:0: detected conn error (1020)
May 10 03:34:47 cmp02 kernel: [15495.317745]  connection2:0: detected conn error (1020)
May 10 03:34:50 cmp02 kernel: [15498.325552]  connection2:0: detected conn error (1020)
May 10 03:34:53 cmp02 kernel: [15501.333438]  connection2:0: detected conn error (1020)
May 10 03:34:56 cmp02 kernel: [15504.341696]  connection2:0: detected conn error (1020)
May 10 03:34:59 cmp02 kernel: [15507.349929]  connection2:0: detected conn error (1020)
May 10 03:35:02 cmp02 kernel: [15510.359808]  connection2:0: detected conn error (1020)
May 10 03:35:05 cmp02 kernel: [15513.368246]  connection2:0: detected conn error (1020)
May 10 03:35:08 cmp02 kernel: [15516.374808]  connection2:0: detected conn error (1020)
May 10 03:35:11 cmp02 kernel: [15519.383709]  connection2:0: detected conn error (1020)
May 10 03:35:12 cmp02 iscsid: message repeated 12 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:35:14 cmp02 kernel: [15522.390287]  connection2:0: detected conn error (1020)
May 10 03:35:15 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:35:17 cmp02 kernel: [15525.395726]  connection2:0: detected conn error (1020)
May 10 03:35:18 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:35:20 cmp02 kernel: [15528.402729]  connection2:0: detected conn error (1020)
May 10 03:35:23 cmp02 kernel: [15531.411920]  connection2:0: detected conn error (1020)
May 10 03:35:26 cmp02 kernel: [15534.418052]  connection2:0: detected conn error (1020)
May 10 03:35:29 cmp02 kernel: [15537.427472]  connection2:0: detected conn error (1020)
May 10 03:35:32 cmp02 kernel: [15540.434885]  connection2:0: detected conn error (1020)
May 10 03:35:33 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:35:35 cmp02 kernel: [15543.440328]  connection2:0: detected conn error (1020)
May 10 03:35:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:35:38 cmp02 kernel: [15546.448336]  connection2:0: detected conn error (1020)
May 10 03:35:41 cmp02 kernel: [15549.456236]  connection2:0: detected conn error (1020)
May 10 03:35:44 cmp02 kernel: [15552.462507]  connection2:0: detected conn error (1020)
May 10 03:35:47 cmp02 kernel: [15555.469433]  connection2:0: detected conn error (1020)
May 10 03:35:50 cmp02 kernel: [15558.476060]  connection2:0: detected conn error (1020)
May 10 03:35:53 cmp02 kernel: [15561.484883]  connection2:0: detected conn error (1020)
May 10 03:35:56 cmp02 kernel: [15564.494480]  connection2:0: detected conn error (1020)
May 10 03:35:59 cmp02 kernel: [15567.501522]  connection2:0: detected conn error (1020)
May 10 03:36:02 cmp02 kernel: [15570.507965]  connection2:0: detected conn error (1020)
May 10 03:36:05 cmp02 kernel: [15573.514108]  connection2:0: detected conn error (1020)
May 10 03:36:08 cmp02 kernel: [15576.524080]  connection2:0: detected conn error (1020)
May 10 03:36:11 cmp02 kernel: [15579.531525]  connection2:0: detected conn error (1020)
May 10 03:36:14 cmp02 kernel: [15582.539357]  connection2:0: detected conn error (1020)
May 10 03:36:15 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:36:17 cmp02 kernel: [15585.548705]  connection2:0: detected conn error (1020)
May 10 03:36:18 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:36:20 cmp02 kernel: [15588.557315]  connection2:0: detected conn error (1020)
May 10 03:36:23 cmp02 kernel: [15591.564547]  connection2:0: detected conn error (1020)
May 10 03:36:26 cmp02 kernel: [15594.572527]  connection2:0: detected conn error (1020)
May 10 03:36:29 cmp02 kernel: [15597.584721]  connection2:0: detected conn error (1020)
May 10 03:36:32 cmp02 kernel: [15600.597108]  connection2:0: detected conn error (1020)
May 10 03:36:33 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:36:35 cmp02 kernel: [15603.604172]  connection2:0: detected conn error (1020)
May 10 03:36:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:36:38 cmp02 kernel: [15606.611475]  connection2:0: detected conn error (1020)
May 10 03:36:41 cmp02 kernel: [15609.616989]  connection2:0: detected conn error (1020)
May 10 03:36:44 cmp02 kernel: [15612.626289]  connection2:0: detected conn error (1020)
May 10 03:36:47 cmp02 kernel: [15615.632660]  connection2:0: detected conn error (1020)
May 10 03:36:50 cmp02 kernel: [15618.640386]  connection2:0: detected conn error (1020)
May 10 03:36:53 cmp02 kernel: [15621.647535]  connection2:0: detected conn error (1020)
May 10 03:36:56 cmp02 kernel: [15624.652594]  connection2:0: detected conn error (1020)
May 10 03:36:59 cmp02 kernel: [15627.666252]  connection2:0: detected conn error (1020)
May 10 03:37:02 cmp02 kernel: [15630.672648]  connection2:0: detected conn error (1020)
May 10 03:37:05 cmp02 kernel: [15633.681932]  connection2:0: detected conn error (1020)
May 10 03:37:08 cmp02 kernel: [15636.691479]  connection2:0: detected conn error (1020)
May 10 03:37:11 cmp02 kernel: [15639.702465]  connection2:0: detected conn error (1020)
May 10 03:37:14 cmp02 kernel: [15642.713707]  connection2:0: detected conn error (1020)
May 10 03:37:15 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:37:17 cmp02 kernel: [15645.726253]  connection2:0: detected conn error (1020)
May 10 03:37:18 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:37:20 cmp02 kernel: [15648.734996]  connection2:0: detected conn error (1020)
May 10 03:37:21 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:37:23 cmp02 kernel: [15651.748116]  connection2:0: detected conn error (1020)
May 10 03:37:26 cmp02 kernel: [15654.755511]  connection2:0: detected conn error (1020)
May 10 03:37:29 cmp02 kernel: [15657.763324]  connection2:0: detected conn error (1020)
May 10 03:37:32 cmp02 kernel: [15660.770240]  connection2:0: detected conn error (1020)
May 10 03:37:33 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:37:35 cmp02 kernel: [15663.782349]  connection2:0: detected conn error (1020)
May 10 03:37:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:37:38 cmp02 kernel: [15666.789206]  connection2:0: detected conn error (1020)
May 10 03:37:41 cmp02 kernel: [15669.796010]  connection2:0: detected conn error (1020)
May 10 03:37:44 cmp02 kernel: [15672.803417]  connection2:0: detected conn error (1020)
May 10 03:37:44 cmp02 kernel: [15672.921125] device tap4e58bce0-50 left promiscuous mode
May 10 03:37:45 cmp02 kernel: [15673.299661] audit: type=1400 audit(1525923465.214:331): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-61160985-7c48-4d13-a0fe-76b7c1b4ba0b" pid=3803 comm="apparmor_parser"
May 10 03:37:42 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:37:45 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap4e58bce0-50
May 10 03:37:45 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:37:47 cmp02 kernel: [15675.809923]  connection2:0: detected conn error (1020)
May 10 03:37:50 cmp02 kernel: [15678.817645]  connection2:0: detected conn error (1020)
May 10 03:37:53 cmp02 kernel: [15681.825454]  connection2:0: detected conn error (1020)
May 10 03:37:56 cmp02 kernel: [15684.834636]  connection2:0: detected conn error (1020)
May 10 03:37:59 cmp02 kernel: [15687.840357]  connection2:0: detected conn error (1020)
May 10 03:38:02 cmp02 kernel: [15690.850197]  connection2:0: detected conn error (1020)
May 10 03:38:05 cmp02 kernel: [15693.860458]  connection2:0: detected conn error (1020)
May 10 03:38:08 cmp02 kernel: [15696.870104]  connection2:0: detected conn error (1020)
May 10 03:38:11 cmp02 kernel: [15699.876995]  connection2:0: detected conn error (1020)
May 10 03:38:14 cmp02 kernel: [15702.885013]  connection2:0: detected conn error (1020)
May 10 03:38:17 cmp02 kernel: [15705.891980]  connection2:0: detected conn error (1020)
May 10 03:38:15 cmp02 iscsid: message repeated 10 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:38:18 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:38:20 cmp02 kernel: [15708.898222]  connection2:0: detected conn error (1020)
May 10 03:38:21 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:38:23 cmp02 kernel: [15711.902625]  connection2:0: detected conn error (1020)
May 10 03:38:26 cmp02 kernel: [15714.908026]  connection2:0: detected conn error (1020)
May 10 03:38:29 cmp02 kernel: [15717.914703]  connection2:0: detected conn error (1020)
May 10 03:38:27 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:38:30 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:38:32 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 03:38:32 cmp02 kernel: [15720.920074]  connection2:0: detected conn error (1020)
May 10 03:38:33 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:38:33 cmp02 kernel: [15721.648727] audit: type=1400 audit(1525923513.562:332): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-d10d8fdf-6853-4b3a-86d0-9be218f49c83" pid=3934 comm="apparmor_parser"
May 10 03:38:33 cmp02 kernel: [15721.884897] audit: type=1400 audit(1525923513.798:333): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d10d8fdf-6853-4b3a-86d0-9be218f49c83" pid=3937 comm="apparmor_parser"
May 10 03:38:34 cmp02 kernel: [15722.118705] audit: type=1400 audit(1525923514.032:334): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d10d8fdf-6853-4b3a-86d0-9be218f49c83" pid=3940 comm="apparmor_parser"
May 10 03:38:34 cmp02 kernel: [15722.352471] audit: type=1400 audit(1525923514.266:335): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-d10d8fdf-6853-4b3a-86d0-9be218f49c83" pid=3943 comm="apparmor_parser"
May 10 03:38:34 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tape91147ee-e2 -- add-port br-int tape91147ee-e2 -- set Interface tape91147ee-e2 "external-ids:attached-mac=\"fa:16:3e:f4:72:47\"" -- set Interface tape91147ee-e2 "external-ids:iface-id=\"e91147ee-e253-43dd-874b-9a372a86066a\"" -- set Interface tape91147ee-e2 "external-ids:vm-id=\"d10d8fdf-6853-4b3a-86d0-9be218f49c83\"" -- set Interface tape91147ee-e2 external-ids:iface-status=active
May 10 03:38:34 cmp02 kernel: [15722.384692] device tape91147ee-e2 entered promiscuous mode
May 10 03:38:34 cmp02 kernel: [15722.619905] audit: type=1400 audit(1525923514.533:336): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-d10d8fdf-6853-4b3a-86d0-9be218f49c83" pid=4000 comm="apparmor_parser"
May 10 03:38:34 cmp02 libvirtd[5599]: 2018-05-10 03:38:34.541+0000: 5610: warning : qemuDomainObjTaint:5532 : Domain id=52 name='instance-00000072' uuid=d10d8fdf-6853-4b3a-86d0-9be218f49c83 is tainted: host-cpu
May 10 03:38:35 cmp02 kernel: [15723.925227]  connection2:0: detected conn error (1020)
May 10 03:38:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:38:38 cmp02 kernel: [15726.932466]  connection2:0: detected conn error (1020)
May 10 03:38:41 cmp02 kernel: [15729.937080]  connection2:0: detected conn error (1020)
May 10 03:38:44 cmp02 kernel: [15732.942856]  connection2:0: detected conn error (1020)
May 10 03:38:47 cmp02 kernel: [15735.949120]  connection2:0: detected conn error (1020)
May 10 03:38:50 cmp02 kernel: [15738.955597]  connection2:0: detected conn error (1020)
May 10 03:38:53 cmp02 kernel: [15741.964051]  connection2:0: detected conn error (1020)
May 10 03:38:56 cmp02 kernel: [15744.968422]  connection2:0: detected conn error (1020)
May 10 03:38:59 cmp02 kernel: [15747.973721]  connection2:0: detected conn error (1020)
May 10 03:39:02 cmp02 kernel: [15750.980117]  connection2:0: detected conn error (1020)
May 10 03:39:05 cmp02 kernel: [15753.985085]  connection2:0: detected conn error (1020)
May 10 03:39:08 cmp02 kernel: [15756.990673]  connection2:0: detected conn error (1020)
May 10 03:39:11 cmp02 kernel: [15759.995855]  connection2:0: detected conn error (1020)
May 10 03:39:14 cmp02 kernel: [15763.000182]  connection2:0: detected conn error (1020)
May 10 03:39:17 cmp02 kernel: [15766.004761]  connection2:0: detected conn error (1020)
May 10 03:39:18 cmp02 iscsid: message repeated 14 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:39:20 cmp02 kernel: [15769.011192]  connection2:0: detected conn error (1020)
May 10 03:39:21 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:39:23 cmp02 kernel: [15772.017497]  connection2:0: detected conn error (1020)
May 10 03:39:26 cmp02 kernel: [15775.023846]  connection2:0: detected conn error (1020)
May 10 03:39:29 cmp02 kernel: [15778.030477]  connection2:0: detected conn error (1020)
May 10 03:39:32 cmp02 kernel: [15781.039237]  connection2:0: detected conn error (1020)
May 10 03:39:33 cmp02 iscsid: message repeated 4 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:39:35 cmp02 kernel: [15784.046737]  connection2:0: detected conn error (1020)
May 10 03:39:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:39:37 cmp02 dhclient[2304]: DHCPREQUEST of 192.168.11.50 on ens3 to 192.168.11.1 port 67 (xid=0x5f70db96)
May 10 03:39:37 cmp02 dhclient[2304]: DHCPACK of 192.168.11.50 from 192.168.11.1
May 10 03:39:37 cmp02 dhclient[2304]: bound to 192.168.11.50 -- renewal in 1450 seconds.
May 10 03:39:38 cmp02 kernel: [15787.054814]  connection2:0: detected conn error (1020)
May 10 03:39:39 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:39:41 cmp02 kernel: [15790.063632]  connection2:0: detected conn error (1020)
May 10 03:39:44 cmp02 kernel: [15793.070539]  connection2:0: detected conn error (1020)
May 10 03:39:47 cmp02 kernel: [15796.078425]  connection2:0: detected conn error (1020)
May 10 03:39:51 cmp02 kernel: [15799.085386]  connection2:0: detected conn error (1020)
May 10 03:39:54 cmp02 kernel: [15802.094416]  connection2:0: detected conn error (1020)
May 10 03:39:57 cmp02 kernel: [15805.108201]  connection2:0: detected conn error (1020)
May 10 03:40:00 cmp02 kernel: [15808.118500]  connection2:0: detected conn error (1020)
May 10 03:40:03 cmp02 kernel: [15811.128207]  connection2:0: detected conn error (1020)
May 10 03:40:06 cmp02 kernel: [15814.138700]  connection2:0: detected conn error (1020)
May 10 03:40:09 cmp02 kernel: [15817.145504]  connection2:0: detected conn error (1020)
May 10 03:40:12 cmp02 kernel: [15820.155481]  connection2:0: detected conn error (1020)
May 10 03:40:15 cmp02 kernel: [15823.163622]  connection2:0: detected conn error (1020)
May 10 03:40:18 cmp02 kernel: [15826.168837]  connection2:0: detected conn error (1020)
May 10 03:40:21 cmp02 kernel: [15829.177838]  connection2:0: detected conn error (1020)
May 10 03:40:18 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:40:21 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:40:24 cmp02 kernel: [15832.186916]  connection2:0: detected conn error (1020)
May 10 03:40:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:40:27 cmp02 kernel: [15835.194232]  connection2:0: detected conn error (1020)
May 10 03:40:30 cmp02 kernel: [15838.204901]  connection2:0: detected conn error (1020)
May 10 03:40:33 cmp02 kernel: [15841.211069]  connection2:0: detected conn error (1020)
May 10 03:40:33 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:40:36 cmp02 kernel: [15844.217237]  connection2:0: detected conn error (1020)
May 10 03:40:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:40:39 cmp02 kernel: [15847.223578]  connection2:0: detected conn error (1020)
May 10 03:40:42 cmp02 kernel: [15850.235400]  connection2:0: detected conn error (1020)
May 10 03:40:45 cmp02 kernel: [15853.243161]  connection2:0: detected conn error (1020)
May 10 03:40:48 cmp02 kernel: [15856.252801]  connection2:0: detected conn error (1020)
May 10 03:40:51 cmp02 kernel: [15859.260726]  connection2:0: detected conn error (1020)
May 10 03:40:54 cmp02 kernel: [15862.267544]  connection2:0: detected conn error (1020)
May 10 03:40:57 cmp02 kernel: [15865.274027]  connection2:0: detected conn error (1020)
May 10 03:41:00 cmp02 kernel: [15868.282083]  connection2:0: detected conn error (1020)
May 10 03:41:03 cmp02 kernel: [15871.291822]  connection2:0: detected conn error (1020)
May 10 03:41:06 cmp02 kernel: [15874.300585]  connection2:0: detected conn error (1020)
May 10 03:41:09 cmp02 kernel: [15877.311491]  connection2:0: detected conn error (1020)
May 10 03:41:12 cmp02 kernel: [15880.317142]  connection2:0: detected conn error (1020)
May 10 03:41:15 cmp02 kernel: [15883.341098]  connection2:0: detected conn error (1020)
May 10 03:41:18 cmp02 kernel: [15886.347982]  connection2:0: detected conn error (1020)
May 10 03:41:21 cmp02 kernel: [15889.355947]  connection2:0: detected conn error (1020)
May 10 03:41:21 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:41:24 cmp02 kernel: [15892.366196]  connection2:0: detected conn error (1020)
May 10 03:41:24 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:41:27 cmp02 kernel: [15895.373701]  connection2:0: detected conn error (1020)
May 10 03:41:30 cmp02 kernel: [15898.382217]  connection2:0: detected conn error (1020)
May 10 03:41:33 cmp02 kernel: [15901.392071]  connection2:0: detected conn error (1020)
May 10 03:41:33 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:41:36 cmp02 kernel: [15904.401738]  connection2:0: detected conn error (1020)
May 10 03:41:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:41:39 cmp02 kernel: [15907.410308]  connection2:0: detected conn error (1020)
May 10 03:41:42 cmp02 kernel: [15910.419714]  connection2:0: detected conn error (1020)
May 10 03:41:45 cmp02 kernel: [15913.428803]  connection2:0: detected conn error (1020)
May 10 03:41:48 cmp02 kernel: [15916.435542]  connection2:0: detected conn error (1020)
May 10 03:41:51 cmp02 kernel: [15919.442762]  connection2:0: detected conn error (1020)
May 10 03:41:54 cmp02 kernel: [15922.450260]  connection2:0: detected conn error (1020)
May 10 03:41:57 cmp02 kernel: [15925.461764]  connection2:0: detected conn error (1020)
May 10 03:42:00 cmp02 kernel: [15928.471198]  connection2:0: detected conn error (1020)
May 10 03:42:03 cmp02 kernel: [15931.481880]  connection2:0: detected conn error (1020)
May 10 03:42:06 cmp02 kernel: [15934.490017]  connection2:0: detected conn error (1020)
May 10 03:42:09 cmp02 kernel: [15937.497146]  connection2:0: detected conn error (1020)
May 10 03:42:12 cmp02 kernel: [15940.501651]  connection2:0: detected conn error (1020)
May 10 03:42:15 cmp02 kernel: [15943.507274]  connection2:0: detected conn error (1020)
May 10 03:42:18 cmp02 kernel: [15946.518688]  connection2:0: detected conn error (1020)
May 10 03:42:21 cmp02 kernel: [15949.527486]  connection2:0: detected conn error (1020)
May 10 03:42:22 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:42:24 cmp02 kernel: [15952.534436]  connection2:0: detected conn error (1020)
May 10 03:42:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:42:27 cmp02 kernel: [15955.539454]  connection2:0: detected conn error (1020)
May 10 03:42:30 cmp02 kernel: [15958.545245]  connection2:0: detected conn error (1020)
May 10 03:42:33 cmp02 kernel: [15961.556362]  connection2:0: detected conn error (1020)
May 10 03:42:31 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:42:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:42:36 cmp02 kernel: [15964.565096]  connection2:0: detected conn error (1020)
May 10 03:42:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:42:39 cmp02 kernel: [15967.572774]  connection2:0: detected conn error (1020)
May 10 03:42:42 cmp02 kernel: [15970.581492]  connection2:0: detected conn error (1020)
May 10 03:42:45 cmp02 kernel: [15973.590822]  connection2:0: detected conn error (1020)
May 10 03:42:48 cmp02 kernel: [15976.599068]  connection2:0: detected conn error (1020)
May 10 03:42:51 cmp02 kernel: [15979.608198]  connection2:0: detected conn error (1020)
May 10 03:42:54 cmp02 kernel: [15982.614554]  connection2:0: detected conn error (1020)
May 10 03:42:57 cmp02 kernel: [15985.621487]  connection2:0: detected conn error (1020)
May 10 03:43:00 cmp02 kernel: [15988.626769]  connection2:0: detected conn error (1020)
May 10 03:43:03 cmp02 kernel: [15991.635178]  connection2:0: detected conn error (1020)
May 10 03:43:06 cmp02 kernel: [15994.641869]  connection2:0: detected conn error (1020)
May 10 03:43:09 cmp02 kernel: [15997.651621]  connection2:0: detected conn error (1020)
May 10 03:43:12 cmp02 kernel: [16000.660570]  connection2:0: detected conn error (1020)
May 10 03:43:15 cmp02 kernel: [16003.669616]  connection2:0: detected conn error (1020)
May 10 03:43:18 cmp02 kernel: [16006.679933]  connection2:0: detected conn error (1020)
May 10 03:43:21 cmp02 kernel: [16009.688483]  connection2:0: detected conn error (1020)
May 10 03:43:22 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:43:24 cmp02 kernel: [16012.697482]  connection2:0: detected conn error (1020)
May 10 03:43:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:43:27 cmp02 kernel: [16015.703558]  connection2:0: detected conn error (1020)
May 10 03:43:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:43:30 cmp02 kernel: [16018.708281]  connection2:0: detected conn error (1020)
May 10 03:43:33 cmp02 kernel: [16021.715941]  connection2:0: detected conn error (1020)
May 10 03:43:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:43:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:43:36 cmp02 kernel: [16024.723681]  connection2:0: detected conn error (1020)
May 10 03:43:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:43:39 cmp02 kernel: [16027.729799]  connection2:0: detected conn error (1020)
May 10 03:43:42 cmp02 kernel: [16030.736935]  connection2:0: detected conn error (1020)
May 10 03:43:45 cmp02 kernel: [16033.751201]  connection2:0: detected conn error (1020)
May 10 03:43:48 cmp02 kernel: [16036.759070]  connection2:0: detected conn error (1020)
May 10 03:43:51 cmp02 kernel: [16039.766747]  connection2:0: detected conn error (1020)
May 10 03:43:54 cmp02 kernel: [16042.775469]  connection2:0: detected conn error (1020)
May 10 03:43:57 cmp02 kernel: [16045.784399]  connection2:0: detected conn error (1020)
May 10 03:44:00 cmp02 kernel: [16048.793930]  connection2:0: detected conn error (1020)
May 10 03:44:03 cmp02 kernel: [16051.804741]  connection2:0: detected conn error (1020)
May 10 03:44:06 cmp02 kernel: [16054.811414]  connection2:0: detected conn error (1020)
May 10 03:44:09 cmp02 kernel: [16057.819522]  connection2:0: detected conn error (1020)
May 10 03:44:12 cmp02 kernel: [16060.829650]  connection2:0: detected conn error (1020)
May 10 03:44:15 cmp02 kernel: [16063.837533]  connection2:0: detected conn error (1020)
May 10 03:44:18 cmp02 kernel: [16066.846346]  connection2:0: detected conn error (1020)
May 10 03:44:21 cmp02 kernel: [16069.858018]  connection2:0: detected conn error (1020)
May 10 03:44:22 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:44:24 cmp02 kernel: [16072.866462]  connection2:0: detected conn error (1020)
May 10 03:44:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:44:27 cmp02 kernel: [16075.873931]  connection2:0: detected conn error (1020)
May 10 03:44:30 cmp02 kernel: [16078.880507]  connection2:0: detected conn error (1020)
May 10 03:44:33 cmp02 kernel: [16081.887051]  connection2:0: detected conn error (1020)
May 10 03:44:31 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:44:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:44:36 cmp02 kernel: [16084.892857]  connection2:0: detected conn error (1020)
May 10 03:44:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:44:39 cmp02 kernel: [16087.898288]  connection2:0: detected conn error (1020)
May 10 03:44:42 cmp02 kernel: [16090.904676]  connection2:0: detected conn error (1020)
May 10 03:44:45 cmp02 kernel: [16093.912057]  connection2:0: detected conn error (1020)
May 10 03:44:48 cmp02 kernel: [16096.924289]  connection2:0: detected conn error (1020)
May 10 03:44:51 cmp02 kernel: [16099.933253]  connection2:0: detected conn error (1020)
May 10 03:44:54 cmp02 kernel: [16102.941423]  connection2:0: detected conn error (1020)
May 10 03:44:57 cmp02 kernel: [16105.950842]  connection2:0: detected conn error (1020)
May 10 03:45:00 cmp02 kernel: [16108.957904]  connection2:0: detected conn error (1020)
May 10 03:45:03 cmp02 kernel: [16111.965964]  connection2:0: detected conn error (1020)
May 10 03:45:06 cmp02 kernel: [16114.976451]  connection2:0: detected conn error (1020)
May 10 03:45:09 cmp02 kernel: [16117.987477]  connection2:0: detected conn error (1020)
May 10 03:45:12 cmp02 kernel: [16120.998437]  connection2:0: detected conn error (1020)
May 10 03:45:15 cmp02 kernel: [16124.006900]  connection2:0: detected conn error (1020)
May 10 03:45:18 cmp02 kernel: [16127.014183]  connection2:0: detected conn error (1020)
May 10 03:45:21 cmp02 kernel: [16130.021938]  connection2:0: detected conn error (1020)
May 10 03:45:22 cmp02 iscsid: message repeated 15 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:45:24 cmp02 kernel: [16133.035844]  connection2:0: detected conn error (1020)
May 10 03:45:25 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:45:27 cmp02 kernel: [16136.042904]  connection2:0: detected conn error (1020)
May 10 03:45:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:45:30 cmp02 kernel: [16139.049889]  connection2:0: detected conn error (1020)
May 10 03:45:33 cmp02 kernel: [16142.059660]  connection2:0: detected conn error (1020)
May 10 03:45:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:45:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:45:36 cmp02 kernel: [16145.067607]  connection2:0: detected conn error (1020)
May 10 03:45:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:45:39 cmp02 kernel: [16148.075774]  connection2:0: detected conn error (1020)
May 10 03:45:42 cmp02 kernel: [16151.082105]  connection2:0: detected conn error (1020)
May 10 03:45:45 cmp02 kernel: [16154.088289]  connection2:0: detected conn error (1020)
May 10 03:45:49 cmp02 kernel: [16157.094349]  connection2:0: detected conn error (1020)
May 10 03:45:52 cmp02 kernel: [16160.108833]  connection2:0: detected conn error (1020)
May 10 03:45:55 cmp02 kernel: [16163.121716]  connection2:0: detected conn error (1020)
May 10 03:45:58 cmp02 kernel: [16166.133554]  connection2:0: detected conn error (1020)
May 10 03:46:01 cmp02 kernel: [16169.144098]  connection2:0: detected conn error (1020)
May 10 03:46:04 cmp02 kernel: [16172.155595]  connection2:0: detected conn error (1020)
May 10 03:46:07 cmp02 kernel: [16175.166485]  connection2:0: detected conn error (1020)
May 10 03:46:10 cmp02 kernel: [16178.173803]  connection2:0: detected conn error (1020)
May 10 03:46:13 cmp02 kernel: [16181.181783]  connection2:0: detected conn error (1020)
May 10 03:46:16 cmp02 kernel: [16184.187132]  connection2:0: detected conn error (1020)
May 10 03:46:19 cmp02 kernel: [16187.195673]  connection2:0: detected conn error (1020)
May 10 03:46:22 cmp02 kernel: [16190.205048]  connection2:0: detected conn error (1020)
May 10 03:46:25 cmp02 kernel: [16193.212462]  connection2:0: detected conn error (1020)
May 10 03:46:25 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:46:28 cmp02 kernel: [16196.217165]  connection2:0: detected conn error (1020)
May 10 03:46:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:46:31 cmp02 kernel: [16199.225352]  connection2:0: detected conn error (1020)
May 10 03:46:34 cmp02 kernel: [16202.235816]  connection2:0: detected conn error (1020)
May 10 03:46:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:46:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:46:37 cmp02 kernel: [16205.243840]  connection2:0: detected conn error (1020)
May 10 03:46:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:46:40 cmp02 kernel: [16208.256284]  connection2:0: detected conn error (1020)
May 10 03:46:43 cmp02 kernel: [16211.265851]  connection2:0: detected conn error (1020)
May 10 03:46:46 cmp02 kernel: [16214.274238]  connection2:0: detected conn error (1020)
May 10 03:46:49 cmp02 kernel: [16217.282848]  connection2:0: detected conn error (1020)
May 10 03:46:52 cmp02 kernel: [16220.290025]  connection2:0: detected conn error (1020)
May 10 03:46:55 cmp02 kernel: [16223.300030]  connection2:0: detected conn error (1020)
May 10 03:46:58 cmp02 kernel: [16226.306548]  connection2:0: detected conn error (1020)
May 10 03:47:01 cmp02 kernel: [16229.313651]  connection2:0: detected conn error (1020)
May 10 03:47:04 cmp02 kernel: [16232.321940]  connection2:0: detected conn error (1020)
May 10 03:47:07 cmp02 kernel: [16235.328589]  connection2:0: detected conn error (1020)
May 10 03:47:10 cmp02 kernel: [16238.339723]  connection2:0: detected conn error (1020)
May 10 03:47:13 cmp02 kernel: [16241.349517]  connection2:0: detected conn error (1020)
May 10 03:47:16 cmp02 kernel: [16244.356772]  connection2:0: detected conn error (1020)
May 10 03:47:19 cmp02 kernel: [16247.363127]  connection2:0: detected conn error (1020)
May 10 03:47:22 cmp02 kernel: [16250.369552]  connection2:0: detected conn error (1020)
May 10 03:47:25 cmp02 kernel: [16253.380000]  connection2:0: detected conn error (1020)
May 10 03:47:25 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:47:28 cmp02 kernel: [16256.386192]  connection2:0: detected conn error (1020)
May 10 03:47:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:47:31 cmp02 kernel: [16259.391826]  connection2:0: detected conn error (1020)
May 10 03:47:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:47:34 cmp02 kernel: [16262.397236]  connection2:0: detected conn error (1020)
May 10 03:47:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:47:37 cmp02 kernel: [16265.405083]  connection2:0: detected conn error (1020)
May 10 03:47:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:47:40 cmp02 kernel: [16268.412413]  connection2:0: detected conn error (1020)
May 10 03:47:43 cmp02 kernel: [16271.418886]  connection2:0: detected conn error (1020)
May 10 03:47:46 cmp02 kernel: [16274.427647]  connection2:0: detected conn error (1020)
May 10 03:47:49 cmp02 kernel: [16277.437427]  connection2:0: detected conn error (1020)
May 10 03:47:52 cmp02 kernel: [16280.444982]  connection2:0: detected conn error (1020)
May 10 03:47:55 cmp02 kernel: [16283.452704]  connection2:0: detected conn error (1020)
May 10 03:47:58 cmp02 kernel: [16286.461423]  connection2:0: detected conn error (1020)
May 10 03:48:01 cmp02 kernel: [16289.472756]  connection2:0: detected conn error (1020)
May 10 03:48:04 cmp02 kernel: [16292.480929]  connection2:0: detected conn error (1020)
May 10 03:48:07 cmp02 kernel: [16295.490286]  connection2:0: detected conn error (1020)
May 10 03:48:10 cmp02 kernel: [16298.497508]  connection2:0: detected conn error (1020)
May 10 03:48:13 cmp02 kernel: [16301.504380]  connection2:0: detected conn error (1020)
May 10 03:48:16 cmp02 kernel: [16304.511364]  connection2:0: detected conn error (1020)
May 10 03:48:19 cmp02 kernel: [16307.525992]  connection2:0: detected conn error (1020)
May 10 03:48:22 cmp02 kernel: [16310.537276]  connection2:0: detected conn error (1020)
May 10 03:48:25 cmp02 kernel: [16313.545751]  connection2:0: detected conn error (1020)
May 10 03:48:25 cmp02 iscsid: message repeated 16 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:48:28 cmp02 kernel: [16316.551976]  connection2:0: detected conn error (1020)
May 10 03:48:28 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:48:31 cmp02 kernel: [16319.560652]  connection2:0: detected conn error (1020)
May 10 03:48:31 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:48:34 cmp02 kernel: [16322.567803]  connection2:0: detected conn error (1020)
May 10 03:48:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:48:37 cmp02 kernel: [16325.576118]  connection2:0: detected conn error (1020)
May 10 03:48:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:48:40 cmp02 kernel: [16328.585212]  connection2:0: detected conn error (1020)
May 10 03:48:43 cmp02 kernel: [16331.590890]  connection2:0: detected conn error (1020)
May 10 03:48:45 cmp02 kernel: [16333.168410] device tape91147ee-e2 left promiscuous mode
May 10 03:48:45 cmp02 kernel: [16333.553312] audit: type=1400 audit(1525924125.456:337): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-d10d8fdf-6853-4b3a-86d0-9be218f49c83" pid=5007 comm="apparmor_parser"
May 10 03:48:43 cmp02 iscsid: message repeated 2 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:48:45 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tape91147ee-e2
May 10 03:48:46 cmp02 kernel: [16334.596452]  connection2:0: detected conn error (1020)
May 10 03:48:46 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:48:49 cmp02 kernel: [16337.602338]  connection2:0: detected conn error (1020)
May 10 03:48:52 cmp02 kernel: [16340.610015]  connection2:0: detected conn error (1020)
May 10 03:48:55 cmp02 kernel: [16343.617695]  connection2:0: detected conn error (1020)
May 10 03:48:58 cmp02 kernel: [16346.629385]  connection2:0: detected conn error (1020)
May 10 03:49:01 cmp02 kernel: [16349.634935]  connection2:0: detected conn error (1020)
May 10 03:49:04 cmp02 kernel: [16352.648164]  connection2:0: detected conn error (1020)
May 10 03:49:07 cmp02 kernel: [16355.656492]  connection2:0: detected conn error (1020)
May 10 03:49:10 cmp02 kernel: [16358.665213]  connection2:0: detected conn error (1020)
May 10 03:49:13 cmp02 kernel: [16361.675724]  connection2:0: detected conn error (1020)
May 10 03:49:16 cmp02 kernel: [16364.685043]  connection2:0: detected conn error (1020)
May 10 03:49:19 cmp02 kernel: [16367.691264]  connection2:0: detected conn error (1020)
May 10 03:49:22 cmp02 kernel: [16370.696982]  connection2:0: detected conn error (1020)
May 10 03:49:25 cmp02 kernel: [16373.703499]  connection2:0: detected conn error (1020)
May 10 03:49:26 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:49:28 cmp02 kernel: [16376.710082]  connection2:0: detected conn error (1020)
May 10 03:49:28 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl -- --may-exist add-br br-int -- set Bridge br-int datapath_type=system
May 10 03:49:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:49:30 cmp02 kernel: [16378.465990] audit: type=1400 audit(1525924170.367:338): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-44ec709f-847a-4354-bb40-9d4efae94a31" pid=5119 comm="apparmor_parser"
May 10 03:49:30 cmp02 kernel: [16378.708404] audit: type=1400 audit(1525924170.610:339): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-44ec709f-847a-4354-bb40-9d4efae94a31" pid=5122 comm="apparmor_parser"
May 10 03:49:30 cmp02 kernel: [16378.944428] audit: type=1400 audit(1525924170.846:340): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-44ec709f-847a-4354-bb40-9d4efae94a31" pid=5125 comm="apparmor_parser"
May 10 03:49:31 cmp02 kernel: [16379.194777] audit: type=1400 audit(1525924171.096:341): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-44ec709f-847a-4354-bb40-9d4efae94a31" pid=5128 comm="apparmor_parser"
May 10 03:49:31 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap044ed6c9-f8 -- add-port br-int tap044ed6c9-f8 -- set Interface tap044ed6c9-f8 "external-ids:attached-mac=\"fa:16:3e:65:d4:15\"" -- set Interface tap044ed6c9-f8 "external-ids:iface-id=\"044ed6c9-f816-4664-a552-2c2e692f40e0\"" -- set Interface tap044ed6c9-f8 "external-ids:vm-id=\"44ec709f-847a-4354-bb40-9d4efae94a31\"" -- set Interface tap044ed6c9-f8 external-ids:iface-status=active
May 10 03:49:31 cmp02 kernel: [16379.247258] device tap044ed6c9-f8 entered promiscuous mode
May 10 03:49:31 cmp02 kernel: [16379.497603] audit: type=1400 audit(1525924171.399:342): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-44ec709f-847a-4354-bb40-9d4efae94a31" pid=5232 comm="apparmor_parser"
May 10 03:49:31 cmp02 libvirtd[5599]: 2018-05-10 03:49:31.406+0000: 5613: warning : qemuDomainObjTaint:5532 : Domain id=53 name='instance-00000073' uuid=44ec709f-847a-4354-bb40-9d4efae94a31 is tainted: host-cpu
May 10 03:49:31 cmp02 kernel: [16379.717313]  connection2:0: detected conn error (1020)
May 10 03:49:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:49:34 cmp02 kernel: [16382.724879]  connection2:0: detected conn error (1020)
May 10 03:49:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:49:37 cmp02 kernel: [16385.731150]  connection2:0: detected conn error (1020)
May 10 03:49:40 cmp02 kernel: [16388.738974]  connection2:0: detected conn error (1020)
May 10 03:49:43 cmp02 kernel: [16391.744634]  connection2:0: detected conn error (1020)
May 10 03:49:46 cmp02 kernel: [16394.751748]  connection2:0: detected conn error (1020)
May 10 03:49:49 cmp02 kernel: [16397.759580]  connection2:0: detected conn error (1020)
May 10 03:49:52 cmp02 kernel: [16400.765324]  connection2:0: detected conn error (1020)
May 10 03:49:55 cmp02 kernel: [16403.771983]  connection2:0: detected conn error (1020)
May 10 03:49:58 cmp02 kernel: [16406.779049]  connection2:0: detected conn error (1020)
May 10 03:50:01 cmp02 kernel: [16409.786406]  connection2:0: detected conn error (1020)
May 10 03:50:04 cmp02 kernel: [16412.791217]  connection2:0: detected conn error (1020)
May 10 03:50:07 cmp02 kernel: [16415.796448]  connection2:0: detected conn error (1020)
May 10 03:50:10 cmp02 kernel: [16418.803232]  connection2:0: detected conn error (1020)
May 10 03:50:13 cmp02 kernel: [16421.809577]  connection2:0: detected conn error (1020)
May 10 03:50:16 cmp02 kernel: [16424.815115]  connection2:0: detected conn error (1020)
May 10 03:50:19 cmp02 kernel: [16427.822809]  connection2:0: detected conn error (1020)
May 10 03:50:22 cmp02 kernel: [16430.828937]  connection2:0: detected conn error (1020)
May 10 03:50:25 cmp02 kernel: [16433.834656]  connection2:0: detected conn error (1020)
May 10 03:50:26 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:50:28 cmp02 kernel: [16436.841762]  connection2:0: detected conn error (1020)
May 10 03:50:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:50:31 cmp02 kernel: [16439.846111]  connection2:0: detected conn error (1020)
May 10 03:50:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:50:34 cmp02 kernel: [16442.852625]  connection2:0: detected conn error (1020)
May 10 03:50:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:50:37 cmp02 kernel: [16445.858754]  connection2:0: detected conn error (1020)
May 10 03:50:40 cmp02 kernel: [16448.867442]  connection2:0: detected conn error (1020)
May 10 03:50:43 cmp02 kernel: [16451.874177]  connection2:0: detected conn error (1020)
May 10 03:50:46 cmp02 kernel: [16454.884652]  connection2:0: detected conn error (1020)
May 10 03:50:49 cmp02 kernel: [16457.895475]  connection2:0: detected conn error (1020)
May 10 03:50:52 cmp02 kernel: [16460.905600]  connection2:0: detected conn error (1020)
May 10 03:50:55 cmp02 kernel: [16463.918925]  connection2:0: detected conn error (1020)
May 10 03:50:58 cmp02 kernel: [16466.926895]  connection2:0: detected conn error (1020)
May 10 03:51:01 cmp02 kernel: [16469.934754]  connection2:0: detected conn error (1020)
May 10 03:51:04 cmp02 kernel: [16472.943859]  connection2:0: detected conn error (1020)
May 10 03:51:07 cmp02 kernel: [16475.951628]  connection2:0: detected conn error (1020)
May 10 03:51:10 cmp02 kernel: [16478.967244]  connection2:0: detected conn error (1020)
May 10 03:51:13 cmp02 kernel: [16481.978470]  connection2:0: detected conn error (1020)
May 10 03:51:16 cmp02 kernel: [16484.987322]  connection2:0: detected conn error (1020)
May 10 03:51:19 cmp02 kernel: [16487.995987]  connection2:0: detected conn error (1020)
May 10 03:51:22 cmp02 kernel: [16491.010294]  connection2:0: detected conn error (1020)
May 10 03:51:25 cmp02 kernel: [16494.016569]  connection2:0: detected conn error (1020)
May 10 03:51:26 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:51:28 cmp02 kernel: [16497.025632]  connection2:0: detected conn error (1020)
May 10 03:51:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:51:31 cmp02 kernel: [16500.033708]  connection2:0: detected conn error (1020)
May 10 03:51:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:51:34 cmp02 kernel: [16503.039669]  connection2:0: detected conn error (1020)
May 10 03:51:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:51:37 cmp02 kernel: [16506.046486]  connection2:0: detected conn error (1020)
May 10 03:51:40 cmp02 kernel: [16509.057166]  connection2:0: detected conn error (1020)
May 10 03:51:43 cmp02 kernel: [16512.068926]  connection2:0: detected conn error (1020)
May 10 03:51:46 cmp02 kernel: [16515.075260]  connection2:0: detected conn error (1020)
May 10 03:51:49 cmp02 kernel: [16518.081212]  connection2:0: detected conn error (1020)
May 10 03:51:52 cmp02 kernel: [16521.090611]  connection2:0: detected conn error (1020)
May 10 03:51:56 cmp02 kernel: [16524.101064]  connection2:0: detected conn error (1020)
May 10 03:51:59 cmp02 kernel: [16527.109636]  connection2:0: detected conn error (1020)
May 10 03:52:02 cmp02 kernel: [16530.117453]  connection2:0: detected conn error (1020)
May 10 03:52:05 cmp02 kernel: [16533.127015]  connection2:0: detected conn error (1020)
May 10 03:52:08 cmp02 kernel: [16536.136427]  connection2:0: detected conn error (1020)
May 10 03:52:11 cmp02 kernel: [16539.142506]  connection2:0: detected conn error (1020)
May 10 03:52:14 cmp02 kernel: [16542.152318]  connection2:0: detected conn error (1020)
May 10 03:52:17 cmp02 kernel: [16545.160488]  connection2:0: detected conn error (1020)
May 10 03:52:20 cmp02 kernel: [16548.168933]  connection2:0: detected conn error (1020)
May 10 03:52:23 cmp02 kernel: [16551.177366]  connection2:0: detected conn error (1020)
May 10 03:52:26 cmp02 kernel: [16554.195560]  connection2:0: detected conn error (1020)
May 10 03:52:26 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:52:29 cmp02 kernel: [16557.202331]  connection2:0: detected conn error (1020)
May 10 03:52:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:52:32 cmp02 kernel: [16560.210829]  connection2:0: detected conn error (1020)
May 10 03:52:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:52:35 cmp02 kernel: [16563.229168]  connection2:0: detected conn error (1020)
May 10 03:52:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:52:38 cmp02 kernel: [16566.234528]  connection2:0: detected conn error (1020)
May 10 03:52:41 cmp02 kernel: [16569.255942]  connection2:0: detected conn error (1020)
May 10 03:52:44 cmp02 kernel: [16572.277723]  connection2:0: detected conn error (1020)
May 10 03:52:47 cmp02 kernel: [16575.285874]  connection2:0: detected conn error (1020)
May 10 03:52:50 cmp02 kernel: [16578.307271]  connection2:0: detected conn error (1020)
May 10 03:52:53 cmp02 kernel: [16581.314500]  connection2:0: detected conn error (1020)
May 10 03:52:56 cmp02 kernel: [16584.326419]  connection2:0: detected conn error (1020)
May 10 03:52:59 cmp02 kernel: [16587.345962]  connection2:0: detected conn error (1020)
May 10 03:53:02 cmp02 kernel: [16590.350717]  connection2:0: detected conn error (1020)
May 10 03:53:05 cmp02 kernel: [16593.377291]  connection2:0: detected conn error (1020)
May 10 03:53:08 cmp02 kernel: [16596.383113]  connection2:0: detected conn error (1020)
May 10 03:53:11 cmp02 kernel: [16599.392089]  connection2:0: detected conn error (1020)
May 10 03:53:14 cmp02 kernel: [16602.401762]  connection2:0: detected conn error (1020)
May 10 03:53:17 cmp02 kernel: [16605.408157]  connection2:0: detected conn error (1020)
May 10 03:53:20 cmp02 kernel: [16608.414324]  connection2:0: detected conn error (1020)
May 10 03:53:23 cmp02 kernel: [16611.419144]  connection2:0: detected conn error (1020)
May 10 03:53:26 cmp02 kernel: [16614.428373]  connection2:0: detected conn error (1020)
May 10 03:53:26 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:53:29 cmp02 kernel: [16617.439743]  connection2:0: detected conn error (1020)
May 10 03:53:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:53:32 cmp02 kernel: [16620.447248]  connection2:0: detected conn error (1020)
May 10 03:53:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:53:35 cmp02 kernel: [16623.454505]  connection2:0: detected conn error (1020)
May 10 03:53:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:53:38 cmp02 kernel: [16626.463717]  connection2:0: detected conn error (1020)
May 10 03:53:41 cmp02 kernel: [16629.471583]  connection2:0: detected conn error (1020)
May 10 03:53:44 cmp02 kernel: [16632.479786]  connection2:0: detected conn error (1020)
May 10 03:53:47 cmp02 kernel: [16635.489203]  connection2:0: detected conn error (1020)
May 10 03:53:50 cmp02 kernel: [16638.496755]  connection2:0: detected conn error (1020)
May 10 03:53:53 cmp02 kernel: [16641.505147]  connection2:0: detected conn error (1020)
May 10 03:53:56 cmp02 kernel: [16644.511234]  connection2:0: detected conn error (1020)
May 10 03:53:59 cmp02 kernel: [16647.521910]  connection2:0: detected conn error (1020)
May 10 03:54:02 cmp02 kernel: [16650.534114]  connection2:0: detected conn error (1020)
May 10 03:54:05 cmp02 kernel: [16653.540769]  connection2:0: detected conn error (1020)
May 10 03:54:08 cmp02 kernel: [16656.553725]  connection2:0: detected conn error (1020)
May 10 03:54:11 cmp02 kernel: [16659.574835]  connection2:0: detected conn error (1020)
May 10 03:54:14 cmp02 kernel: [16662.584963]  connection2:0: detected conn error (1020)
May 10 03:54:17 cmp02 kernel: [16665.595854]  connection2:0: detected conn error (1020)
May 10 03:54:20 cmp02 kernel: [16668.601628]  connection2:0: detected conn error (1020)
May 10 03:54:23 cmp02 kernel: [16671.609796]  connection2:0: detected conn error (1020)
May 10 03:54:26 cmp02 kernel: [16674.633793]  connection2:0: detected conn error (1020)
May 10 03:54:26 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:54:29 cmp02 kernel: [16677.642997]  connection2:0: detected conn error (1020)
May 10 03:54:29 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:54:32 cmp02 kernel: [16680.666256]  connection2:0: detected conn error (1020)
May 10 03:54:32 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:54:35 cmp02 kernel: [16683.673538]  connection2:0: detected conn error (1020)
May 10 03:54:35 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:54:38 cmp02 kernel: [16686.680238]  connection2:0: detected conn error (1020)
May 10 03:54:41 cmp02 kernel: [16689.687688]  connection2:0: detected conn error (1020)
May 10 03:54:44 cmp02 kernel: [16692.693032]  connection2:0: detected conn error (1020)
May 10 03:54:47 cmp02 kernel: [16695.703140]  connection2:0: detected conn error (1020)
May 10 03:54:50 cmp02 kernel: [16698.709423]  connection2:0: detected conn error (1020)
May 10 03:54:53 cmp02 kernel: [16701.714900]  connection2:0: detected conn error (1020)
May 10 03:54:56 cmp02 kernel: [16704.722297]  connection2:0: detected conn error (1020)
May 10 03:54:59 cmp02 kernel: [16707.732588]  connection2:0: detected conn error (1020)
May 10 03:55:02 cmp02 kernel: [16710.741657]  connection2:0: detected conn error (1020)
May 10 03:55:05 cmp02 kernel: [16713.749186]  connection2:0: detected conn error (1020)
May 10 03:55:08 cmp02 kernel: [16716.759281]  connection2:0: detected conn error (1020)
May 10 03:55:11 cmp02 kernel: [16719.769661]  connection2:0: detected conn error (1020)
May 10 03:55:14 cmp02 kernel: [16722.774994]  connection2:0: detected conn error (1020)
May 10 03:55:17 cmp02 kernel: [16725.784881]  connection2:0: detected conn error (1020)
May 10 03:55:20 cmp02 kernel: [16728.794759]  connection2:0: detected conn error (1020)
May 10 03:55:23 cmp02 kernel: [16731.800774]  connection2:0: detected conn error (1020)
May 10 03:55:26 cmp02 kernel: [16734.812034]  connection2:0: detected conn error (1020)
May 10 03:55:29 cmp02 kernel: [16737.821400]  connection2:0: detected conn error (1020)
May 10 03:55:27 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:55:30 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:55:32 cmp02 kernel: [16740.826884]  connection2:0: detected conn error (1020)
May 10 03:55:33 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:55:35 cmp02 kernel: [16743.836628]  connection2:0: detected conn error (1020)
May 10 03:55:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:55:38 cmp02 kernel: [16746.843103]  connection2:0: detected conn error (1020)
May 10 03:55:41 cmp02 kernel: [16749.854454]  connection2:0: detected conn error (1020)
May 10 03:55:44 cmp02 kernel: [16752.864008]  connection2:0: detected conn error (1020)
May 10 03:55:47 cmp02 kernel: [16755.874096]  connection2:0: detected conn error (1020)
May 10 03:55:50 cmp02 kernel: [16758.882760]  connection2:0: detected conn error (1020)
May 10 03:55:53 cmp02 kernel: [16761.889306]  connection2:0: detected conn error (1020)
May 10 03:55:56 cmp02 kernel: [16764.896242]  connection2:0: detected conn error (1020)
May 10 03:55:59 cmp02 kernel: [16767.905685]  connection2:0: detected conn error (1020)
May 10 03:56:02 cmp02 kernel: [16770.914893]  connection2:0: detected conn error (1020)
May 10 03:56:05 cmp02 kernel: [16773.922633]  connection2:0: detected conn error (1020)
May 10 03:56:08 cmp02 kernel: [16776.933140]  connection2:0: detected conn error (1020)
May 10 03:56:11 cmp02 kernel: [16779.938916]  connection2:0: detected conn error (1020)
May 10 03:56:14 cmp02 kernel: [16782.946519]  connection2:0: detected conn error (1020)
May 10 03:56:17 cmp02 kernel: [16785.953940]  connection2:0: detected conn error (1020)
May 10 03:56:20 cmp02 kernel: [16788.962735]  connection2:0: detected conn error (1020)
May 10 03:56:23 cmp02 kernel: [16791.971266]  connection2:0: detected conn error (1020)
May 10 03:56:26 cmp02 kernel: [16794.980860]  connection2:0: detected conn error (1020)
May 10 03:56:29 cmp02 kernel: [16797.991009]  connection2:0: detected conn error (1020)
May 10 03:56:27 cmp02 iscsid: message repeated 17 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:56:30 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:56:32 cmp02 kernel: [16800.998054]  connection2:0: detected conn error (1020)
May 10 03:56:33 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:56:35 cmp02 kernel: [16804.005469]  connection2:0: detected conn error (1020)
May 10 03:56:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:56:38 cmp02 kernel: [16807.014607]  connection2:0: detected conn error (1020)
May 10 03:56:41 cmp02 kernel: [16810.021420]  connection2:0: detected conn error (1020)
May 10 03:56:44 cmp02 kernel: [16813.031277]  connection2:0: detected conn error (1020)
May 10 03:56:47 cmp02 kernel: [16816.038660]  connection2:0: detected conn error (1020)
May 10 03:56:50 cmp02 kernel: [16819.048793]  connection2:0: detected conn error (1020)
May 10 03:56:53 cmp02 kernel: [16822.056827]  connection2:0: detected conn error (1020)
May 10 03:56:56 cmp02 kernel: [16825.065666]  connection2:0: detected conn error (1020)
May 10 03:56:59 cmp02 kernel: [16828.072376]  connection2:0: detected conn error (1020)
May 10 03:57:02 cmp02 kernel: [16831.078908]  connection2:0: detected conn error (1020)
May 10 03:57:05 cmp02 kernel: [16834.085155]  connection2:0: detected conn error (1020)
May 10 03:57:08 cmp02 kernel: [16837.092667]  connection2:0: detected conn error (1020)
May 10 03:57:11 cmp02 kernel: [16840.099756]  connection2:0: detected conn error (1020)
May 10 03:57:15 cmp02 kernel: [16843.109241]  connection2:0: detected conn error (1020)
May 10 03:57:18 cmp02 kernel: [16846.120793]  connection2:0: detected conn error (1020)
May 10 03:57:21 cmp02 kernel: [16849.127026]  connection2:0: detected conn error (1020)
May 10 03:57:24 cmp02 kernel: [16852.135301]  connection2:0: detected conn error (1020)
May 10 03:57:27 cmp02 kernel: [16855.143748]  connection2:0: detected conn error (1020)
May 10 03:57:30 cmp02 kernel: [16858.150951]  connection2:0: detected conn error (1020)
May 10 03:57:30 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:57:33 cmp02 kernel: [16861.156185]  connection2:0: detected conn error (1020)
May 10 03:57:33 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:57:36 cmp02 kernel: [16864.169462]  connection2:0: detected conn error (1020)
May 10 03:57:36 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:57:39 cmp02 kernel: [16867.179938]  connection2:0: detected conn error (1020)
May 10 03:57:42 cmp02 kernel: [16870.187369]  connection2:0: detected conn error (1020)
May 10 03:57:45 cmp02 kernel: [16873.197966]  connection2:0: detected conn error (1020)
May 10 03:57:48 cmp02 kernel: [16876.208877]  connection2:0: detected conn error (1020)
May 10 03:57:51 cmp02 kernel: [16879.219124]  connection2:0: detected conn error (1020)
May 10 03:57:54 cmp02 kernel: [16882.226412]  connection2:0: detected conn error (1020)
May 10 03:57:57 cmp02 kernel: [16885.232835]  connection2:0: detected conn error (1020)
May 10 03:58:00 cmp02 kernel: [16888.239992]  connection2:0: detected conn error (1020)
May 10 03:58:03 cmp02 kernel: [16891.249970]  connection2:0: detected conn error (1020)
May 10 03:58:06 cmp02 kernel: [16894.256802]  connection2:0: detected conn error (1020)
May 10 03:58:09 cmp02 kernel: [16897.267230]  connection2:0: detected conn error (1020)
May 10 03:58:12 cmp02 kernel: [16900.275436]  connection2:0: detected conn error (1020)
May 10 03:58:15 cmp02 kernel: [16903.282795]  connection2:0: detected conn error (1020)
May 10 03:58:18 cmp02 kernel: [16906.292091]  connection2:0: detected conn error (1020)
May 10 03:58:21 cmp02 kernel: [16909.300682]  connection2:0: detected conn error (1020)
May 10 03:58:24 cmp02 kernel: [16912.307701]  connection2:0: detected conn error (1020)
May 10 03:58:27 cmp02 kernel: [16915.314860]  connection2:0: detected conn error (1020)
May 10 03:58:30 cmp02 kernel: [16918.328264]  connection2:0: detected conn error (1020)
May 10 03:58:31 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:58:33 cmp02 kernel: [16921.338502]  connection2:0: detected conn error (1020)
May 10 03:58:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:58:36 cmp02 kernel: [16924.345451]  connection2:0: detected conn error (1020)
May 10 03:58:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:58:39 cmp02 kernel: [16927.353062]  connection2:0: detected conn error (1020)
May 10 03:58:42 cmp02 kernel: [16930.363595]  connection2:0: detected conn error (1020)
May 10 03:58:45 cmp02 kernel: [16933.370362]  connection2:0: detected conn error (1020)
May 10 03:58:48 cmp02 kernel: [16936.377440]  connection2:0: detected conn error (1020)
May 10 03:58:51 cmp02 kernel: [16939.384565]  connection2:0: detected conn error (1020)
May 10 03:58:54 cmp02 kernel: [16942.394728]  connection2:0: detected conn error (1020)
May 10 03:58:57 cmp02 kernel: [16945.408861]  connection2:0: detected conn error (1020)
May 10 03:59:00 cmp02 kernel: [16948.416923]  connection2:0: detected conn error (1020)
May 10 03:59:03 cmp02 kernel: [16951.426347]  connection2:0: detected conn error (1020)
May 10 03:59:06 cmp02 kernel: [16954.431497]  connection2:0: detected conn error (1020)
May 10 03:59:09 cmp02 kernel: [16957.454768]  connection2:0: detected conn error (1020)
May 10 03:59:12 cmp02 kernel: [16960.473788]  connection2:0: detected conn error (1020)
May 10 03:59:15 cmp02 kernel: [16963.478802]  connection2:0: detected conn error (1020)
May 10 03:59:18 cmp02 kernel: [16966.515681]  connection2:0: detected conn error (1020)
May 10 03:59:21 cmp02 kernel: [16969.523525]  connection2:0: detected conn error (1020)
May 10 03:59:24 cmp02 kernel: [16972.533131]  connection2:0: detected conn error (1020)
May 10 03:59:27 cmp02 kernel: [16975.557896]  connection2:0: detected conn error (1020)
May 10 03:59:30 cmp02 kernel: [16978.565218]  connection2:0: detected conn error (1020)
May 10 03:59:31 cmp02 iscsid: message repeated 18 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:59:33 cmp02 kernel: [16981.583262]  connection2:0: detected conn error (1020)
May 10 03:59:34 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:59:36 cmp02 kernel: [16984.589669]  connection2:0: detected conn error (1020)
May 10 03:59:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:59:39 cmp02 kernel: [16987.615946]  connection2:0: detected conn error (1020)
May 10 03:59:42 cmp02 kernel: [16990.634844]  connection2:0: detected conn error (1020)
May 10 03:59:45 cmp02 kernel: [16993.643411]  connection2:0: detected conn error (1020)
May 10 03:59:48 cmp02 kernel: [16996.648986]  connection2:0: detected conn error (1020)
May 10 03:59:51 cmp02 kernel: [16999.654961]  connection2:0: detected conn error (1020)
May 10 03:59:54 cmp02 kernel: [17002.174546] device tap044ed6c9-f8 left promiscuous mode
May 10 03:59:54 cmp02 kernel: [17002.556763] audit: type=1400 audit(1525924794.446:343): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-44ec709f-847a-4354-bb40-9d4efae94a31" pid=6342 comm="apparmor_parser"
May 10 03:59:52 cmp02 iscsid: message repeated 5 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 03:59:54 cmp02 ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --timeout=5 -- --if-exists del-port tap044ed6c9-f8
May 10 03:59:54 cmp02 kernel: [17002.660931]  connection2:0: detected conn error (1020)
May 10 03:59:55 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 03:59:57 cmp02 kernel: [17005.668075]  connection2:0: detected conn error (1020)
May 10 04:00:00 cmp02 kernel: [17008.673734]  connection2:0: detected conn error (1020)
May 10 04:00:03 cmp02 kernel: [17011.679960]  connection2:0: detected conn error (1020)
May 10 04:00:06 cmp02 kernel: [17014.686892]  connection2:0: detected conn error (1020)
May 10 04:00:09 cmp02 kernel: [17017.695204]  connection2:0: detected conn error (1020)
May 10 04:00:12 cmp02 kernel: [17020.705823]  connection2:0: detected conn error (1020)
May 10 04:00:15 cmp02 kernel: [17023.712052]  connection2:0: detected conn error (1020)
May 10 04:00:18 cmp02 kernel: [17026.720442]  connection2:0: detected conn error (1020)
May 10 04:00:21 cmp02 kernel: [17029.727975]  connection2:0: detected conn error (1020)
May 10 04:00:24 cmp02 kernel: [17032.736878]  connection2:0: detected conn error (1020)
May 10 04:00:27 cmp02 kernel: [17035.745631]  connection2:0: detected conn error (1020)
May 10 04:00:30 cmp02 kernel: [17038.753531]  connection2:0: detected conn error (1020)
May 10 04:00:33 cmp02 kernel: [17041.761308]  connection2:0: detected conn error (1020)
May 10 04:00:34 cmp02 iscsid: message repeated 13 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 04:00:36 cmp02 kernel: [17044.772200]  connection2:0: detected conn error (1020)
May 10 04:00:37 cmp02 iscsid: conn 0 login rejected: initiator error - target not found (02/03)
May 10 04:00:39 cmp02 kernel: [17047.782981]  connection2:0: detected conn error (1020)
May 10 04:00:42 cmp02 kernel: [17050.791293]  connection2:0: detected conn error (1020)
May 10 04:00:45 cmp02 kernel: [17053.802029]  connection2:0: detected conn error (1020)
May 10 04:00:46 cmp02 iscsid: message repeated 3 times: [ conn 0 login rejected: initiator error - target not found (02/03)]
May 10 04:00:48 cmp02 salt-minion[2824]: [INFO    ] User sudo_ubuntu Executing command cp.push_dir with jid 20180510040048569149
May 10 04:00:48 cmp02 salt-minion[2824]: [INFO    ] Starting a new job with PID 6412
May 10 04:00:48 cmp02 kernel: [17056.818704]  connection2:0: detected conn error (1020)
