I'm working on setting up a new razor server and have gotten the microkernel boot to work fine. But now, when it tries to provision the new node, I get this:
Now, I noticed two things here: First, it's using a "Noop" installer when the profile I have calls for centos/7:
[root@puppet ~]# razor policies
+---------+--------+--------+--------+--------+--------+--------+-------+
| name | repo | task | broker | enable | max_co | tags | nodes |
+---------+--------+--------+--------+--------+--------+--------+-------+
| centos- | centos | centos | puppet | true | | (none) | 0 |
| for-sma | 7 | /7 | | | | | |
+---------+--------+--------+--------+--------+--------+--------+-------+
Query an entry by including its name, e.g. `razor policies centos-for-small`
[root@puppet ~]# razor brokers
+--------+-------------+-----------------------------------------+----------+
| name | broker_type | configuration | policies |
+--------+-------------+-----------------------------------------+----------+
| noop | noop | (none) | 0 |
+--------+-------------+-----------------------------------------+----------+
| | | ronment"=>"production"} | |
+--------+-------------+-----------------------------------------+----------+
Query an entry by including its name, e.g. `razor brokers noop`
[root@puppet ~]# razor repos centos7
Query additional details via: `razor repos centos7 [task]`
[root@puppet ~]# razor policies centos-for-small
Query additional details via: `razor policies centos-for-small [broker, configuration, nodes, repo, tags, task]`
So I'm not sure where the noop is coming from. It had been set in the policy originally, but I updated it to what you see here and still it's trying to use the noop installer.
Thanks.