Hello, Yeah, that's true. There shouldn't be any VBox specific hacks, and I believe PostgreSQL uses locale's encoding by default (which is ASCII in containers).
Well, basically the bug should be assigned on library team - we should specify UTF-8 explicitly in PostgreSQL config, since Nailgun works with UTF-8 [1] and we must be in sync here. Thanks, Igor [1] https://github.com/openstack/fuel-web/blob/35dda0f36c4c5e52bc68492ab7ad154d14747eef/nailgun/nailgun/db/sqlalchemy/__init__.py#L36 On Thu, Nov 5, 2015 at 12:38 AM, Evgeniy L <e...@mirantis.com> wrote: > Hi, > > I believe we don't have any VirtualBox specific hacks, especially in terms > of > database configuration. By "development env" Vitaly meant fake UI, when > developer installs and configures the database by himself, without any iso > images, so probably his db is configured correctly with utf-8. > > Also we should make sure that upgrade works correctly, after the problem is > fixed. > > Thanks, > > On Wed, Nov 4, 2015 at 2:30 PM, Artem Roma <ar...@mirantis.com> wrote: >> >> Hi, folks! >> >> Recently I've been working on this bug [1] and have found that default >> encoding of database server used by FUEL infrastructure components (Nailgun, >> OSTF, etc) is ascii. At least this is true for environment set up via >> VirtualBox scripts. This situation may (and already does returning to the >> bug) cause obfuscating problems when dealing with non-ascii string data >> supplied by user such as names for nodes, clusters etc. Nailgun encodes such >> data in UTF-8 before sending to the database so misinterpretation by former >> while saving it is sure thing. >> >> I wonder if we have such situation on all Fuel environments or only on >> those set by VB scripts, because as for me it seems as pretty serious flaw >> in our infrastructure. It would be great to have some comments from people >> more competent in areas regarding to the matter. >> >> [1] https://bugs.launchpad.net/fuel/+bug/1472275 >> >> -- >> Regards!) >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev