[Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration

Marcel Schaible marcel at schaible-consulting.de
Fri Feb 1 16:47:54 UTC 2019


[root at controller-0 ~(keystone_admin)]# openstack endpoint list
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
| ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                      |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
| 8bca85c075e74635a4c81c978da9434c | RegionOne | keystone     | identity     | True    | admin     | http://127.0.0.1:5000/v3 |
| edc1d5eb056744adba859c0d4630ba5b | RegionOne | keystone     | identity     | True    | internal  | http://127.0.0.1:5000/v3 |
| 73e43933bd6744d7ae37bb938194be88 | RegionOne | keystone     | identity     | True    | public    | http://127.0.0.1:5000/v3 |
| f5b6a70a9a3a42b99230462fd72188e1 | RegionOne | sysinv       | platform     | True    | admin     | http://127.0.0.1:6385/v1 |
| 99c8461427b54839a0ca647815e0a469 | RegionOne | sysinv       | platform     | True    | internal  | http://127.0.0.1:6385/v1 |
| a8a78b29d3054189bd734261c442ad4e | RegionOne | sysinv       | platform     | True    | public    | http://127.0.0.1:6385/v1 |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+

> "Peters, Matt" <Matt.Peters at windriver.com> hat am 1. Februar 2019 um 17:38 geschrieben:
> 
> 
> Hello,
> I'm not sure why it is giving that error response.
> 
> Are you able to run the following?
> openstack endpoint list
> 
> 
> On 2019-02-01, 11:19 AM, "Marcel Schaible" <marcel at schaible-consulting.de> wrote:
> 
>     Hi Matt,
>     
>     thanks for your response.
>     
>     controller-0:~# source /etc/nova/openrc
>     -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller
>     internalURL endpoint for smapi service in RegionOne region not found
>     [root at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0
>     internalURL endpoint for smapi service in RegionOne region not found
>     [root at controller-0 ~(keystone_admin)]#
>     
>     Any idea what "RegionOne" mean?
>     Thanks
>     Marcel
>     
>     
>     > "Peters, Matt" <Matt.Peters at windriver.com> hat am 1. Februar 2019 um 17:07 geschrieben:
>     > 
>     > 
>     > Hell Marcel,
>     > If your system is still in that state, can you run the following commands?
>     > 
>     > source /etc/nova/openrc
>     > system host-ethernet-port-list controller-0
>     > system host-if-list -a controller-0
>     > 
>     > 
>     > On 2019-02-01, 10:32 AM, "Marcel Schaible" <marcel at schaible-consulting.de> wrote:
>     > 
>     >     Hi,
>     >     
>     >     during installation when appling the configuration I'll get an error message from hiera:
>     >     
>     >     Configuration failed: Failed to update hiera configuration
>     >     
>     >     Configuration log and apply_manifet.log is attached below.
>     >     
>     >     Any idea or hint?
>     >     
>     >     Thanks
>     >     
>     >     Marcel
>     >     
>     >     
>     >     
>     >     localhost:~# config_controller
>     >     System Configuration
>     >     ====================
>     >     Enter Q at any prompt to abort...
>     >     
>     >     System date and time:
>     >     ---------------------
>     >     
>     >     The system date and time must be set now. Note that UTC time must be used and
>     >     that the date and time must be set as accurately as possible, even if NTP/PTP is
>     >     to be configured later.
>     >     
>     >     Current system date and time (UTC): 2019-02-01 15:15:25
>     >     
>     >     Is the current date and time correct? [y/n]: y
>     >     Current system date and time will be used.
>     >     
>     >     System timezone:
>     >     ----------------
>     >     
>     >     The system timezone must be set now. The timezone must be a valid timezone from
>     >     /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...)
>     >     
>     >     Please input the timezone[UTC]:Europe/Berlin
>     >     
>     >     System Configuration:
>     >     ---------------------
>     >     
>     >     System mode. Available options are:
>     >     
>     >     1) duplex-direct - two node redundant configuration. Management and
>     >     infrastructure networks are directly connected to peer ports
>     >     2) duplex - two node redundant configuration.
>     >     3) simplex - single node non-redundant configuration.
>     >     System mode [duplex-direct]:
>     >     
>     >     PXEBoot Network:
>     >     ----------------
>     >     
>     >     The PXEBoot network is used for initial booting and installation of each node.
>     >     IP addresses on this network are reachable only within the data center.
>     >     
>     >     The default configuration combines the PXEBoot network and the management
>     >     network. If a separate PXEBoot network is used, it will share the management
>     >     interface, which requires the management network to be placed on a VLAN.
>     >     
>     >     Configure a separate PXEBoot network [y/N]:
>     >     Aborting configuration
>     >     localhost:~# config_controller
>     >     System Configuration
>     >     ====================
>     >     Enter Q at any prompt to abort...
>     >     
>     >     System date and time:
>     >     ---------------------
>     >     
>     >     The system date and time must be set now. Note that UTC time must be used and
>     >     that the date and time must be set as accurately as possible, even if NTP/PTP is
>     >     to be configured later.
>     >     
>     >     Current system date and time (UTC): 2019-02-01 15:15:40
>     >     
>     >     Is the current date and time correct? [y/n]: y
>     >     Current system date and time will be used.
>     >     
>     >     System timezone:
>     >     ----------------
>     >     
>     >     The system timezone must be set now. The timezone must be a valid timezone from
>     >     /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...)
>     >     
>     >     Please input the timezone[UTC]:Europe/Berlin
>     >     
>     >     System Configuration:
>     >     ---------------------
>     >     
>     >     System mode. Available options are:
>     >     
>     >     1) duplex-direct - two node redundant configuration. Management and
>     >     infrastructure networks are directly connected to peer ports
>     >     2) duplex - two node redundant configuration.
>     >     3) simplex - single node non-redundant configuration.
>     >     System mode [duplex-direct]: 1
>     >     
>     >     PXEBoot Network:
>     >     ----------------
>     >     
>     >     The PXEBoot network is used for initial booting and installation of each node.
>     >     IP addresses on this network are reachable only within the data center.
>     >     
>     >     The default configuration combines the PXEBoot network and the management
>     >     network. If a separate PXEBoot network is used, it will share the management
>     >     interface, which requires the management network to be placed on a VLAN.
>     >     
>     >     Configure a separate PXEBoot network [y/N]: N
>     >     
>     >     Management Network:
>     >     -------------------
>     >     
>     >     The management network is used for internal communication between platform
>     >     components. IP addresses on this network are reachable only within the data
>     >     center.
>     >     
>     >     A management bond interface provides redundant connections for the management
>     >     network.
>     >     It is strongly recommended to configure Management interface link
>     >     aggregation, for All-in-one duplex-direct.
>     >     
>     >     Management interface link aggregation [y/N]: y
>     >     Management interface [bond0]:
>     >     Management interface MTU [1500]:
>     >     
>     >     Specify one of the bonding policies. Possible values are:
>     >       1) 802.3ad (LACP) policy
>     >       2) Active-backup policy
>     >     
>     >     Management interface bonding policy [802.3ad]:
>     >     A maximum of 2 physical interfaces can be attached to the management interface.
>     >     
>     >     First management interface member [enp3s0f1]: enp8s20f4
>     >     Second management interface member []: enp8s20f5
>     >     Management subnet [192.168.204.0/24]: 172.27.1.0/24
>     >     Use entire management subnet [Y/n]: Y
>     >     
>     >     IP addresses can be assigned to hosts dynamically or a static IP address can be
>     >     specified for each host. This choice applies to both the management network and
>     >     infrastructure network (if configured).
>     >     Warning: Selecting 'N', or static IP address allocation, disables automatic
>     >     provisioning of new hosts in System Inventory, requiring the user to manually
>     >     provision using the 'system host-add' command.
>     >     Dynamic IP address allocation [Y/n]: Y
>     >     Management Network Multicast subnet [239.1.1.0/28]:
>     >     
>     >     Infrastructure Network:
>     >     -----------------------
>     >     
>     >     The infrastructure network is used for internal communication between platform
>     >     components to offload the management network of high bandwidth services. IP
>     >     addresses on this network are reachable only within the data center.
>     >     
>     >     If a separate infrastructure interface is not configured the management network
>     >     will be used.
>     >     
>     >     It is NOT recommended to configure infrastructure network for All-in-
>     >     one duplex-direct.
>     >     Configure an infrastructure interface [y/N]: N
>     >     
>     >     External OAM Network:
>     >     ---------------------
>     >     
>     >     The external OAM network is used for management of the cloud. It also provides
>     >     access to the platform APIs. IP addresses on this network are reachable outside
>     >     the data center.
>     >     
>     >     An external OAM bond interface provides redundant connections for the OAM
>     >     network.
>     >     
>     >     External OAM interface link aggregation [y/N]: y
>     >     External OAM interface [bond1]:
>     >     Configure an external OAM VLAN [y/N]:
>     >     External OAM interface MTU [1500]:
>     >     
>     >     Specify one of the bonding policies. Possible values are:
>     >       1) Active-backup policy
>     >       2) Balanced XOR policy
>     >       3) 802.3ad (LACP) policy
>     >     
>     >     External OAM interface bonding policy [active-backup]:
>     >     A maximum of 2 physical interfaces can be attached to the external OAM
>     >     interface.
>     >     
>     >     First external OAM interface member [enp3s0f0]: enp7s16f1
>     >     Second external oam interface member []: enp7s16f7
>     >     External OAM subnet [10.10.10.0/24]: 10.62.150.0/24
>     >     External OAM gateway address [10.62.150.1]:
>     >     External OAM floating address [10.62.150.2]:
>     >     External OAM address for first controller node [10.62.150.3]: 10.62.150.210
>     >     External OAM address for second controller node [10.62.150.211]:
>     >     
>     >     Cloud Authentication:
>     >     -------------------------------
>     >     
>     >     Configure a password for the Cloud admin user The Password must have a minimum
>     >     length of 7 character, and conform to password complexity rules
>     >     Create admin user password:
>     >     Repeat admin user password:
>     >     
>     >     
>     >     
>     >     The following configuration will be applied:
>     >     
>     >     System Configuration
>     >     --------------------
>     >     Time Zone: Europe/Berlin
>     >     System mode: duplex-direct
>     >     
>     >     PXEBoot Network Configuration
>     >     -----------------------------
>     >     Separate PXEBoot network not configured
>     >     PXEBoot Controller floating hostname: pxecontroller
>     >     
>     >     Management Network Configuration
>     >     --------------------------------
>     >     Management interface name: bond0
>     >     Management interface: bond0
>     >     Management interface MTU: 1500
>     >     Management ae member 0: enp8s20f4
>     >     Management ae member 1: enp8s20f5
>     >     Management ae policy : 802.3ad
>     >     Management subnet: 172.27.1.0/24
>     >     Controller floating address: 172.27.1.2
>     >     Controller 0 address: 172.27.1.3
>     >     Controller 1 address: 172.27.1.4
>     >     NFS Management Address 1: 172.27.1.5
>     >     NFS Management Address 2: 172.27.1.6
>     >     Controller floating hostname: controller
>     >     Controller hostname prefix: controller-
>     >     OAM Controller floating hostname: oamcontroller
>     >     Dynamic IP address allocation is selected
>     >     Management multicast subnet: 239.1.1.0/28
>     >     
>     >     Infrastructure Network Configuration
>     >     ------------------------------------
>     >     Infrastructure interface not configured
>     >     
>     >     External OAM Network Configuration
>     >     ----------------------------------
>     >     External OAM interface name: bond1
>     >     External OAM interface: bond1
>     >     External OAM interface MTU: 1500
>     >     External OAM ae member 0: enp7s16f1
>     >     External OAM ae member 1: enp7s16f7
>     >     External OAM ae policy : active-backup
>     >     External OAM subnet: 10.62.150.0/24
>     >     External OAM gateway address: 10.62.150.1
>     >     External OAM floating address: 10.62.150.2
>     >     External OAM 0 address: 10.62.150.210
>     >     External OAM 1 address: 10.62.150.211
>     >     
>     >     Apply the above configuration? [y/n]: y
>     >     
>     >     Applying configuration (this will take several minutes):
>     >     
>     >     01/08: Creating bootstrap configuration ... DONE
>     >     02/08: Applying bootstrap manifest ... DONE
>     >     03/08: Persisting local configuration ... DONE
>     >     04/08: Populating initial system inventory ... DONE
>     >     05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last):
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/bin/sysinv-puppet", line 10, in <module>
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     sys.exit(main())
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     CONF.action.func(CONF.action.path, CONF.action.hostname)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     operator.update_host_config(host)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     func(self, *args, **kwargs)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     config.update(puppet_plugin.obj.get_host_config(host))
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     generate_interface_configs(context, config)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     generate_network_config(context, config, iface)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     network_config = get_interface_network_config(context, iface)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     os_ifname = get_interface_os_ifname(context, iface)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     os_ifname = get_interface_port_name(context, iface)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     port = get_interface_port(context, iface)
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv   File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv     return context['ports'][iface['id']]
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24
>     >     2019-02-01 15:20:44.053 25508 TRACE sysinv
>     >     Failed to update puppet hiera host config
>     >     
>     >     Configuration failed: Failed to update hiera configuration
>     >     localhost:~# 
>     >     
>     >     /tmp/apply_manifest.log:
>     >     ========================
>     >     
>     >     cp: cannot stat ‘/tmp/hieradata/172.27.1.3.yaml’: No such file or directory
>     >     cp: cannot stat ‘/tmp/hieradata/system.yaml’: No such file or directory
>     >     cp: cannot stat ‘/tmp/hieradata/secure_system.yaml’: No such file or directory
>     >     Applying puppet bootstrap manifest...
>     >     [DONE]
>     >     
>     >     
>     >     ls /tmp/puppet/hieradata/
>     >     =========================
>     >     global.yaml  personality.yaml  secure_static.yaml  static.yaml
>     >     localhost:~#
>     >     
>     >     _______________________________________________
>     >     Starlingx-discuss mailing list
>     >     Starlingx-discuss at lists.starlingx.io
>     >     http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>     >     
>     >
>     
>



More information about the Starlingx-discuss mailing list