Fedora Account System
Red Hat Associate
Red Hat Customer
Considering the upgrade scripts for the migration from 4.1 to 4.2 expect that the database be mounted onto another mountpoint and the way the appliance_console handles hard drve expansion, I believe we should prevent customers from creating a database on an appliance without using a secondary hard drive. This would result in environments difficult to upgrade that would require a lot f mainteance to bring back to what is expected
https://github.com/ManageIQ/manageiq-gems-pending/pull/276
https://github.com/ManageIQ/manageiq-gems-pending/pull/277
New commit detected on ManageIQ/manageiq-gems-pending/master: https://github.com/ManageIQ/manageiq-gems-pending/commit/7ae42c0221436d03a94620ce58cfabc97363f797 commit 7ae42c0221436d03a94620ce58cfabc97363f797 Author: Bo Yao <icerove> AuthorDate: Wed Oct 4 15:10:16 2017 -0400 Commit: Bo Yao <icerove> CommitDate: Fri Oct 6 11:34:51 2017 -0400 check and only allow to create database in a mount point https://bugzilla.redhat.com/show_bug.cgi?id=1431815 https://bugzilla.redhat.com/show_bug.cgi?id=1425153 .../appliance_console/internal_database_configuration.rb | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
Verified in 5.9.0.3
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/RHSA-2018:0380
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days