[2.3] Strange error when registering external rack controller

Bug #1704026 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Critical
Unassigned

Bug Description

After I added a new rack controller that happened to be an older version, started seeing stranger errors.

Region - 2.3 (from experimental3)
Rack - 2.1.5 (from archive)

Errors:

2017-07-13 01:09:39 regiond: [info] 10.90.90.13 POST /MAAS/metadata/status/spn6m8/latest HTTP/1.1 --> 400 BAD_REQUEST (referrer: -; agent: Python-urllib/3.5)
2017-07-13 01:09:43 metadataserver: [error] Status payload is not valid JSON:
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox
Content-Disposition: form-data; name="op"

signal
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox
Content-Disposition: form-data; name="error"

Starting 00-maas-01-lshw [1/5]
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox
Content-Disposition: form-data; name="status"

WORKING
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox--

2017-07-13 01:09:43 regiond: [info] 10.90.90.13 POST /MAAS/metadata/status/spn6m8/latest HTTP/1.1 --> 400 BAD_REQUEST (referrer: -; agent: Python-urllib/3.5)
2017-07-13 01:09:51 metadataserver: [error] Status payload is not valid JSON:
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox
Content-Disposition: form-data; name="op"

signal
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox
Content-Disposition: form-data; name="error"

Starting 00-maas-01-lshw [1/5]
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox
Content-Disposition: form-data; name="status"

WORKING
--sNafcEKTyPKNZRkdYptQGkZPTdxKRox--

2017-07-13 01:09:51 regiond: [info] 10.90.90.13 POST /MAAS/metadata/status/spn6m8/latest HTTP/1.1 --> 400 BAD_REQUEST (referrer: -; agent: Python-urllib/3.5)

[....]

         <configuration>
          <setting id="created" value="2017-07-13 00:33:22" />
          <setting id="filesystem" value="ext4" />
          <setting id="label" value="root" />
          <setting id="lastmountpoint" value="/" />
          <setting id="modified" value="2017-07-13 00:34:55" />
          <setting id="mount.fstype" value="ext4" />
          <setting id="mount.options" value="rw,relatime,data=ordered" />
          <setting id="mounted" value="2017-07-13 00:35:20" />
          <setting id="state" value="mounted" />
         </configuration>
         <capabilities>
          <capability id="journaled" />
          <capability id="extended_attributes" >Extended Attributes</capability>
          <capability id="large_files" >4GB+ files</capability>
          <capability id="huge_files" >16TB+ files</capability>
          <capability id="dir_nlink" >directories with 65000+ subdirs</capability>
          <capability id="recover" >needs recovery</capability>
          <capability id="extents" >extent-based allocation</capability>
          <capability id="ext4" />
          <capability id="ext2" >EXT2/EXT3</capability>
          <capability id="initialized" >initialized volume</capability>
         </capabilities>
        </node>
      </node>
    </node>
  </node>
</node>
</list>

--QubcZajxjwFZLMotbpEyyQnprrMjOzg
Content-Disposition: form-data; name="00-maas-01-lshw.err"; filename="00-maas-01-lshw.err"
Content-Type: application/octet-stream

--QubcZajxjwFZLMotbpEyyQnprrMjOzg--

Tags: ha
description: updated
Changed in maas:
milestone: none → 2.3.0
importance: Undecided → Critical
status: New → Triaged
description: updated
tags: added: ha
description: updated
Changed in maas:
status: Triaged → Incomplete
Changed in maas:
status: Incomplete → Invalid
milestone: 2.3.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.