Odd razor error on freshly set up server

109 views
Skip to first unread message

Bret Wortman

unread,
Apr 12, 2016, 6:30:55 AM4/12/16
to Puppet Users
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:

:
Filename: bootstrap.ipxe
bootstrap.ipxe : 1626 bytes [script]
Noop installer (Installed by Razor)
forcing local booting with sanboot 0x80
Booting from SAN device 0x80
Boot from SAN device 0x80 failed: Exec format error (http://ipxe.org/2e852001)
Could not boot: Exec format error (http://ipxe.org/2e852001)
Could not boot image: Result too large (http://ipxe.org/46022001)
No more network devices

Operating System not found

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 |
|         |        |        |        | d      | unt    |        |       |
+---------+--------+--------+--------+--------+--------+--------+-------+
| centos- | centos | centos | puppet | true   |        | (none) | 0     |
| for-sma | 7      | /7     |        |        |        |        |       |
| ll      |        |        |        |        |        |        |       |
+---------+--------+--------+--------+--------+--------+--------+-------+

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        |
+--------+-------------+-----------------------------------------+----------+
| puppet | puppet      | {"server"=>"puppet.wedgeofli.me", "envi | 1        |
|        |             | ronment"=>"production"}                 |          |
+--------+-------------+-----------------------------------------+----------+

Query an entry by including its name, e.g. `razor brokers noop`

[root@puppet ~]# razor repos centos7

     name: centos7
  iso_url: ---
     task: centos/7

Query additional details via: `razor repos centos7 [task]`

[root@puppet ~]# razor policies centos-for-small

       name: centos-for-small
       repo: centos7
       task: centos/7
     broker: puppet
    enabled: true
  max_count: nil
       tags: (none)
      nodes: 0

Query additional details via: `razor policies centos-for-small [broker, configuration, nodes, repo, tags, task]`

[root@puppet ~]# 

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.

Secondly, The url http://192.168.1.101:8150/api/nodes/5 is wrong -- it should be /api/collections/nodes/node5. Is this partly to blame, and if so, why is razor using the wrong url to its own api? Did I mis-set this somewhere?

Thanks.
Reply all
Reply to author
Forward
0 new messages