Bug 1734671
Summary: | [scale] updatevmdynamic broken if too many users logged in - psql ERROR: value too long for type character varying(255) | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Steven Rosenberg <srosenbe> |
Component: | ovirt-engine | Assignee: | Steven Rosenberg <srosenbe> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.3.6 | CC: | bugs, dagur, emarcus, gveitmic, michal.skrivanek, pelauter, rbarry, Rhev-m-bugs |
Target Milestone: | ovirt-4.3.6 | Keywords: | ZStream |
Target Release: | 4.3.6 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.3.6.1 | Doc Type: | Bug Fix |
Doc Text: |
The Database field guest_cur_user_name in the vm_dynamic Database Table was limited to a size of 255 characters, which was not enough to accept a large number of users (for example, more than 100) to log in.
In this release, there is no character limit for the guest_cur_user_name field.
|
Story Points: | --- |
Clone Of: | 1729811 | Environment: | |
Last Closed: | 2019-10-10 15:36:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1729811 | ||
Bug Blocks: |
Description
Steven Rosenberg
2019-07-31 07:43:33 UTC
Verified on ovirt-engine-4.3.6.3-0.1.el7.noarch sync2jira sync2jira INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Tag 'ovirt-engine-4.3.5.6' doesn't contain patch 'https://gerrit.ovirt.org/102297'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.3.5.6 For more info please contact: rhv-devops Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:3010 |