| 2020-08-25 18:15:24 |
Michael Quiniola |
bug |
|
|
added bug |
| 2020-08-25 18:16:29 |
Michael Quiniola |
description |
After upgrading from percona charm to mysql-innodb-cluster following the guide found at https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-series-upgrade-specific-procedures.html#percona-cluster-charm-series-upgrade-to-focal, N-C-C has been looking for the old mysql IP address.
At first the upgrade worked fine and using the openstack CLI client worked. But, accessing via horizon I would get errors in the nova-api log:
Can't connect to MySQL server on '10.0.3.116' ([Errno 113] EHOSTUNREACH)
I couldn't find ANYWHERE this IP address was defined in any charm. The old sql server was removed and the charm was removed from the model.
I completely removed Nova Cloud Controller and redeployed the charm. It STILL is looking for the old IP address:
2020-08-25 18:04:24 ERROR juju-log shared-db:316: db sync failed
b'ERROR: Could not access cell0.\nHas the nova_api database been created?\nHas the nova_cell0 database been created?\nHas "nova-manage api_db sync" been run?\nHas "nova-manage cell_v2 map_cell0" been run?\nIs [api_database]/connection set in nova.conf?\nIs the cell0 database connection URL correct?\nError: (pymysql.err.OperationalError) (2003, "Can\'t connect to MySQL server on \'10.0.3.116\' ([Errno 113] EHOSTUNREACH)")\n(Background on this error at: http://sqlalche.me/e/e3q8)\n'
I looked through all the config files and can't find ANYWHERE this IP address is still defined. |
After upgrading from percona charm to mysql-innodb-cluster following the guide found at https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-series-upgrade-specific-procedures.html#percona-cluster-charm-series-upgrade-to-focal, N-C-C has been looking for the old mysql IP address.
At first the upgrade worked fine and using the openstack CLI client worked. But, accessing via horizon I would get errors in the nova-api log:
Can't connect to MySQL server on '10.0.3.116' ([Errno 113] EHOSTUNREACH)
I couldn't find ANYWHERE this IP address was defined in any charm. The old sql server was removed and the charm was removed from the model.
I completely removed Nova Cloud Controller and redeployed the charm. It STILL is looking for the old IP address:
2020-08-25 18:04:24 ERROR juju-log shared-db:316: db sync failed
b'ERROR: Could not access cell0.\nHas the nova_api database been created?\nHas the nova_cell0 database been created?\nHas "nova-manage api_db sync" been run?\nHas "nova-manage cell_v2 map_cell0" been run?\nIs [api_database]/connection set in nova.conf?\nIs the cell0 database connection URL correct?\nError: (pymysql.err.OperationalError) (2003, "Can\'t connect to MySQL server on \'10.0.3.116\' ([Errno 113] EHOSTUNREACH)")\n(Background on this error at: http://sqlalche.me/e/e3q8)\n'
I looked through all the config files and can't find ANYWHERE this IP address is still defined.
nova-cloud-controller 21.0.0 nova-cloud-controller 346 |
|
| 2020-08-25 18:17:27 |
Michael Quiniola |
description |
After upgrading from percona charm to mysql-innodb-cluster following the guide found at https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-series-upgrade-specific-procedures.html#percona-cluster-charm-series-upgrade-to-focal, N-C-C has been looking for the old mysql IP address.
At first the upgrade worked fine and using the openstack CLI client worked. But, accessing via horizon I would get errors in the nova-api log:
Can't connect to MySQL server on '10.0.3.116' ([Errno 113] EHOSTUNREACH)
I couldn't find ANYWHERE this IP address was defined in any charm. The old sql server was removed and the charm was removed from the model.
I completely removed Nova Cloud Controller and redeployed the charm. It STILL is looking for the old IP address:
2020-08-25 18:04:24 ERROR juju-log shared-db:316: db sync failed
b'ERROR: Could not access cell0.\nHas the nova_api database been created?\nHas the nova_cell0 database been created?\nHas "nova-manage api_db sync" been run?\nHas "nova-manage cell_v2 map_cell0" been run?\nIs [api_database]/connection set in nova.conf?\nIs the cell0 database connection URL correct?\nError: (pymysql.err.OperationalError) (2003, "Can\'t connect to MySQL server on \'10.0.3.116\' ([Errno 113] EHOSTUNREACH)")\n(Background on this error at: http://sqlalche.me/e/e3q8)\n'
I looked through all the config files and can't find ANYWHERE this IP address is still defined.
nova-cloud-controller 21.0.0 nova-cloud-controller 346 |
After upgrading from percona charm to mysql-innodb-cluster following the guide found at https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-series-upgrade-specific-procedures.html#percona-cluster-charm-series-upgrade-to-focal, N-C-C has been looking for the old mysql IP address.
At first the upgrade worked fine and using the openstack CLI client worked. But, accessing via horizon I would get errors in the nova-api log:
Can't connect to MySQL server on '10.0.3.116' ([Errno 113] EHOSTUNREACH)
I couldn't find ANYWHERE this IP address was defined in any charm. The old sql server was removed and the charm was removed from the model.
I completely removed Nova Cloud Controller and redeployed the charm. It STILL is looking for the old IP address, but now its ALSO affecting the rest of the charm:
2020-08-25 18:04:24 ERROR juju-log shared-db:316: db sync failed
b'ERROR: Could not access cell0.\nHas the nova_api database been created?\nHas the nova_cell0 database been created?\nHas "nova-manage api_db sync" been run?\nHas "nova-manage cell_v2 map_cell0" been run?\nIs [api_database]/connection set in nova.conf?\nIs the cell0 database connection URL correct?\nError: (pymysql.err.OperationalError) (2003, "Can\'t connect to MySQL server on \'10.0.3.116\' ([Errno 113] EHOSTUNREACH)")\n(Background on this error at: http://sqlalche.me/e/e3q8)\n'
I looked through all the config files and can't find ANYWHERE this IP address is still defined.
nova-cloud-controller 21.0.0 nova-cloud-controller 346 |
|
| 2020-08-26 19:15:37 |
Corey Bryant |
attachment added |
|
corey-repro-1892904.txt https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1892904/+attachment/5404897/+files/corey-repro-1892904.txt |
|
| 2020-08-27 12:35:49 |
Corey Bryant |
charm-nova-cloud-controller: status |
New |
Invalid |
|
| 2020-08-31 20:20:17 |
Corey Bryant |
charm-nova-cloud-controller: status |
Invalid |
New |
|
| 2020-08-31 22:12:59 |
Corey Bryant |
attachment added |
|
corey-repro-1892904-2.txt https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1892904/+attachment/5406258/+files/corey-repro-1892904-2.txt |
|
| 2020-08-31 22:13:05 |
Corey Bryant |
charm-nova-cloud-controller: status |
New |
Triaged |
|
| 2020-08-31 22:13:07 |
Corey Bryant |
charm-nova-cloud-controller: importance |
Undecided |
High |
|
| 2020-09-09 13:10:34 |
Corey Bryant |
attachment added |
|
corey-fixtest-1892904.txt https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1892904/+attachment/5409038/+files/corey-fixtest-1892904.txt |
|
| 2020-09-09 20:31:31 |
OpenStack Infra |
charm-nova-cloud-controller: status |
In Progress |
Fix Committed |
|
| 2020-11-02 14:43:20 |
Alex Kavanagh |
charm-nova-cloud-controller: milestone |
|
20.10 |
|
| 2020-11-02 14:52:01 |
Alex Kavanagh |
charm-nova-cloud-controller: status |
Fix Committed |
Fix Released |
|
