Description of problem: When deploying rhosp9 with rhel-registration information, though the deployment is successful, nodes are not registered to redhat still How reproducible: 100% Steps to Reproduce: 1. Deploy rhosp 9 with Bigswitch plugins 2. Deploy rhosp 9 again with rhel-registration yaml files 3. Deployment succeed, but checking all overcloud nodes shows none is registered to Redhat. 4. Attempt to run update failed since nodes are not registered. This is bigswitch environment-rhel-registration.yaml files # Note this can be specified either in the call # to heat stack-create via an additional -e option # or via the global environment on the seed in # /etc/heat/environment.d/default.yaml parameter_defaults: rhel_reg_activation_key: "key1" rhel_reg_auto_attach: "" rhel_reg_base_url: "" rhel_reg_environment: "" rhel_reg_force: "true" rhel_reg_machine_name: "" rhel_reg_org: "7697224" rhel_reg_password: "" rhel_reg_pool_id: "8a85f98157083df101570f3cfdd37f43" rhel_reg_release: "" rhel_reg_repos: "" rhel_reg_repos: "rhel-7-server-rpms, rhel-7-server-extras-rpms, rhel-7-server-rh-common-rpms, rhel-7-server-satellite-tools-6.1-rpms, rhel-ha-for-rhel-7-server-rpms, rhel-7-server-openstack-9-director-rpms, rhel-7-server-openstack-9-rpms, rhel-7-server-rhceph-1.3-mon-rpms" rhel_reg_sat_url: "" rhel_reg_server_url: "" rhel_reg_service_level: "" rhel_reg_user: "" rhel_reg_type: "" rhel_reg_method: "portal" rhel_reg_sat_repo: ""
are you overriding OS::TripleO::NodeExtraConfig in any of your environment files? it's possible this is caused by https://bugzilla.redhat.com/show_bug.cgi?id=1459716
are you able to check what I asked in comment 1?