View Issue Details

IDProjectCategoryView StatusLast Update
0000118FromDual Ops Center for MariaDB and MySQL (focmm)Generalpublic2014-05-02 20:48
Reporterabdel-mawla Assigned Tooli  
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionwon't fix 
PlatformLinuxOSCentosOS Version6.x
Product Version1.0.0 
Target Version1.0.0 
Summary0000118: Change server IP cause Database connection errors
DescriptionAs reported in bug#117 "Filling serverIP automatically when adding new database instance", I would say it should be linked to the server not only filling the IP automatically once we chose the server in the database instance creation.

I had to change a server IP which was already registered in MOC. As a result of this change neither the server nor the database instances could connect successfully.
To get this fixed I had to change the IP to the correct one in both server and database and if I have many database instances attached to the same server it will be more complicated.

I tried to change the server name in the server section and it was reflected directly on each database instance attached to that server.

I suggest that each database instance should be linked to its server, so that each change will be made on the server IP will be reflected automatically (like the server name) on all related database instances without the needs to change them manually.
Steps To Reproduce1- Register server and database instances for a host.
2- Change the host IP.
3- Change the IP in the server section to match the new host IP.
4- The same change must be done on the database instance otherwise it wont work.

Step 0000004 should be done automatically after step 0000003.
TagsNo tags attached.

Activities

oli

2014-05-02 20:48

developer   ~0000102

As mentioned earlier the service IP of the database has nothing to do with the IP of a server. In practice they are in most cases the same.
But we cannot conclude, that when I change the server IP also the DB IP should change.
Further server IPs change rarely and you should carefully plan what you do.

Issue History

Date Modified Username Field Change
2014-02-19 17:03 abdel-mawla New Issue
2014-02-19 17:03 abdel-mawla Status new => assigned
2014-02-19 17:03 abdel-mawla Assigned To => oli
2014-05-02 20:48 oli Note Added: 0000102
2014-05-02 20:48 oli Status assigned => resolved
2014-05-02 20:48 oli Resolution open => won't fix