Project

Profile

Help

Issue #4584

closed

No serializer for UpdateRecord related models

Added by ttereshc about 5 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 52
Quarter:

Description

No info about references, pkglist when accessed via REST API.
There is a serialiser for UpdateRecord model but not for any related ones.

$ http :8000/pulp/api/v3/content/rpm/errata/5eeabc0b-3b86-4264-bb3a-5889530a6f5b/

HTTP/1.1 200 OK
Allow: GET, HEAD, OPTIONS
Connection: close
Content-Length: 4868
Content-Type: application/json
Date: Tue, 26 Mar 2019 20:45:04 GMT
Server: gunicorn/19.9.0
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN

{
    "_created": "2019-03-25T13:02:02.133719Z",
    "_href": "/pulp/api/v3/content/rpm/errata/5eeabc0b-3b86-4264-bb3a-5889530a6f5b/",
    "_type": "rpm.update",
    "description": "Bacula is a set of programs that allow you to manage the backup, recovery, and\nverification of computer data across a network of different computers. \n\nThis update fixes the following bugs:\n\n* Prior to this update, the bacula packages were not distributed with the\napplybaculadate file. As a result, the logwatch cron script failed. The problem\nhas been fixed by including the applybaculadate file in the bacula packages so\nthat the logwatch cron script now works as expected. (BZ#651776)\n\n* Prior to this update, the make_catalog_backup.pl script created a MySQL\nconfiguration file, which had the file permissions set to world-writeable and\nworld-readable so that MySQL did not accept the configuration file with these\npermissions and the MySQL database login configuration was not used. As a\nresult, it was not possible to complete a MySQL database dump. With this update,\nthe configuration file is now created with correct permissions, and the MySQL\ndatabase login configuration is used by MySQL so that it is now possible to\ncomplete the MySQL database dump as expected. (BZ#651780)\n\n* Prior to this update, there was no option to change Bacula's runtime user. As\na consequence, Bacula was always run under the root user. The problem has been\nfixed by adding support for the bacula-dir, bacula-fd, and bacula-sd files in\nthe /etc/sysconfig/ directory; these files can be used for specifying a non-root\nuser and group with the DIR_USER, FD_USER, SD_USER, and DIR_GROUP, FD_GROUP and\nSD_GROUP options, respectively. With this update, Bacula can be run under the\nspecified user. (BZ#651786)\n\n* Prior to this update, when creating a symbolic link to the \"bscan\" utility,\nthe new link was erroneously named \"dbcheck\". As a result, the already existing\n\"dbcheck\" symbolic link was overwritten by the erroneous one. Thus the \"dbcheck\"\ncommand ran the \"bscan\" utility so that it was not possible to execute the\n\"bscan\" utility with the \"bscan\" command. The problem has been fixed in this\nupdate so that the \"dbcheck\" and \"bscan\" utilities now work as expected.\n(BZ#651787)\n\n* Prior to this update, Bacula's default configuration missed a required option.\nAs a result, the Bacula tray monitor component terminated unexpectedly. The\nproblem has been fixed by adding the \"Address\" option to the \"Director\" section\nin the Bacula tray monitor configuration file so that the Bacula tray monitor\nnow works as expected with the default configuration file. Note that this bug\nfix does not alter any existing Bacula tray monitor configuration file. As a\nconsequence, the Bacula tray monitor can terminate unexpectedly if the existing\nBacula tray monitor configuration is incorrect. (BZ#657297)\n\n* Prior to this update, the backup size was computed incorrectly under certain\ncircumstances. As a consequence, the reported size of the incremental backup\ncould have been wrong. The problem has been fixed by correcting the backup size\ncomputation process so that the size of the incremental backup is now reported\ncorrectly. (BZ#689400)\n\n* Prior to this update, the shadow-utils package was not listed among the\npackage dependencies for Bacula. As a result, the bacula user and bacula group\nwere not created when the shadow-utils package was not present on the system,\nand a warning message was displayed during the bacula packages installation.\nThis bug has been fixed by adding shadow-utils to the package dependencies.\n(BZ#712794)\n\n* Prior to this update, the chkconfig package, which contains the \"alternatives\"\nutility, was not listed among the package dependencies for Bacula. As a result,\nthe bacula-dir and bacula-sd services were not configured, the \"alternatives\"\nutility was not found, and Bacula's symbolic links were not created. These\nproblems have been fixed by adding chkconfig to the package dependencies.\n(BZ#712804)\n\nAll users of Bacula are advised to upgrade to these updated packages, which fix\nthese bugs.\n",
    "fromstr": "security@redhat.com",
    "id": "RHBA-2011:1232",
    "issued_date": "2011-08-31 00:00:00",
    "pushcount": "",
    "release": "",
    "rights": "Copyright 2011 Red Hat Inc",
    "severity": "",
    "solution": "Before applying this update, make sure all previously-released errata\nrelevant to your system have been applied.\n\nThis update is available via the Red Hat Network. Details on how to\nuse the Red Hat Network to apply this update are available at\nhttps://access.redhat.com/kb/docs/DOC-11259\n",
    "status": "final",
    "summary": "Updated bacula packages that fix multiple bugs are now available for Red Hat\nEnterprise Linux 6.\n",
    "title": "bacula bug fix update",
    "type": "bugfix",
    "updated_date": "2011-12-06 01:14:43",
    "version": "1"
}

Also available in: Atom PDF