Dumpdata failing for table metadataserver.nodeuserdata
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Unassigned | ||
2.3 |
Won't Fix
|
High
|
Unassigned |
Bug Description
1) Output from dpkg -l '*maas*'|cat
root@maas-server:~# dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.2.0+bzr6054-
ii maas-cli 2.2.0+bzr6054-
un maas-cluster-
ii maas-common 2.2.0+bzr6054-
ii maas-dhcp 2.2.0+bzr6054-
ii maas-dns 2.2.0+bzr6054-
ii maas-proxy 2.2.0+bzr6054-
ii maas-rack-
ii maas-region-api 2.2.0+bzr6054-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.2.0+bzr6054-
ii python3-maas-client 2.2.0+bzr6054-
ii python3-
-------
2) Instructions on how we can re-create your bug and what the expected result should be.
Please see command executed and output:
sudo maas-region dumpdata metadataserver.
CommandError: Unable to serialize database: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte. You passed in b'\x1f\
A select or a pg_dump to that table works fine.
information type: | Public → Private |
information type: | Private → Public |
tags: | added: sts |
tags: | added: internal |
Changed in maas: | |
milestone: | none → 2.4.x |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
milestone: | 2.4.x → next |
Changed in maas: | |
status: | Triaged → Won't Fix |
Changed in maas: | |
milestone: | next → none |
This occurs after MAAS deploys a node for Juju. The "data" field for the row contains base64-encoded gzip data which contains: cloud-init- output. log'
#cloud-config
apt_mirror: ""
output:
all: '| tee -a /var/log/
package_update: true
package_upgrade: true
packages:
- bridge-utils
- curl
- cpu-checker
.
.
.