Majic Projects
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Closed Bug report MAR-76 Role database_server does not apply UTF-8 configuration immediatelly
Go to the next issue (open or closed)
Go to the next open issue
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targetted for
  • Status
  • Progress
  • Priority
    Must fix before next release
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (1)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    Not estimated
  • Time spent
    1 hour
    Click here to see time logged against this issue
Issue details
  • Resolution
  • Reproducability
  • Severity
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates

At the moment the database_server role applies the UTF-8 configuration via handler. Unfortunately this means that if a database and/or tables are being created in the same play, they will not have the UTF-8 set-up correctly.

It is necessary to modify the database_server role to restart the service as soon as it deploys the UTF-8 configuration file.

Steps to reproduce this issue
  1. Create playbook that invokes database_server role, follwed by database role, followed by creation of tables in the database.

  2. Run the playbook on a fresh server.

  3. Dump the created database.

  4. Examine if tables are dumped with utf-8 or latin1 for collation.

Expected results:

  1. Tables are created using utf-8 for collation.

Actual results:

  1. Tables are created using latin1 for collation.
Comments ()
There are no comments