First time here? Check out the FAQ!
2018-03-26 04:30:07 -0600 | commented answer | No handlers could be found for logger "swift-proxy" I was able to get rid of this error by not specifying a default log route, i.e. log_name etc in the [DEFAULT] section. |
2017-08-10 13:17:31 -0600 | commented answer | DNS Resolution fails All right, thanks for the heads up anyway! :) |
2017-07-13 05:57:33 -0600 | commented answer | DNS Resolution fails Would you happen to have any details to share on this issue, bug reports or whatnot? I'm facing similar issues on a Mitaka installation that can't easily be upgraded. |
2017-07-11 02:39:21 -0600 | received badge | ● Enthusiast |
2017-07-06 10:07:59 -0600 | commented answer | Search domain in resolv.conf not updating Same thing happened for me, S. Boran. Tried changing |
2017-07-06 10:05:32 -0600 | received badge | ● Supporter (source) |
2016-03-21 07:28:34 -0600 | received badge | ● Famous Question (source) |
2016-03-19 13:02:38 -0600 | received badge | ● Notable Question (source) |
2016-03-18 23:27:52 -0600 | received badge | ● Popular Question (source) |
2016-03-18 12:12:22 -0600 | commented answer | Instances with large images sometimes fail to start/spawn Thanks for the steps on how to replace the Swift endpoint though! |
2016-03-18 12:10:41 -0600 | commented answer | Instances with large images sometimes fail to start/spawn CentOS 6.6 is one of the images registered in Glance, not the distro that Kilo is running on. Having a complete and seperate Swift install is definitely a better solution and is in the works, but I'm still curious why this is one is now broken. For now, the 6.6 image is disabled (not public). |
2016-03-17 11:38:53 -0600 | asked a question | Instances with large images sometimes fail to start/spawn OpenStack Kilo 2015.1.1 (Mirantis) When creating instances with a CentOS 6.6 image sized at 1.1 GB it fails consistently for all compute nodes but one. However when using an Ubuntu 14.04 image sized at ~250 MB it works all the time. This setup used to work, so it may have been triggered by a config change or something else. Looking at the traceback it looks like Glance is having some issues. Tried restarting both the glance-api and glance-registry service but didn't help. Using Horizon or novaclient it initially reports as 'building', and looking at Not sure what could be wrong, or where to look next. Logs filtered for readability.
Traceback: (more) |