On Wed, Sep 30, 2015 at 8:15 AM, George Shuklin <[email protected]> wrote: > Yes, we using swift as backend, and swift running as separate installation > (own keystone, etc). > > I can't find any logs about any problems with backend. They should be logged > by glance? >
I'd look for timeouts. Snapshots with raw disks and swift can take time and end up timing out at loadbalancers, or perhaps even tokens. Just a thought... Thanks, Curtis. > > > On 09/29/2015 01:21 AM, David Wahlstrom wrote: > > George, > > What is your storage backend using (Gluster/ceph/local disk/etc)? Some of > the distributed backend drivers have bugs in them or mask the real issue > (such as watchers on objects). > > On Thu, Sep 24, 2015 at 8:11 AM, Kris G. Lindgren <[email protected]> > wrote: >> >> I believe I was talking to Josh Harlow (he's harlowja in >> #openstack-operators on freenode) from Yahoo, about something like this the >> other day. He was saying that recently on a few hypervisors they would >> randomly run into HV disks that were completely full due to snapshots. I >> have not personally ran into this, so I can't be of more help. >> >> ___________________________________________________________________ >> Kris Lindgren >> Senior Linux Systems Engineer >> GoDaddy >> >> >> >> >> >> On 9/24/15, 7:02 AM, "George Shuklin" <[email protected]> wrote: >> >> >Hello everyone. >> > >> >Is someone ever saw 'endless snapshot' problem? Some instances (with raw >> >disks and live snapshoting enabled) are stuck at image_uploading forever. >> > >> >It looks like this: >> > >> >> > >+--------------------------------------+----------------------------------------------------------+ >> >| Property | Value >> > | >> >> > >+--------------------------------------+----------------------------------------------------------+ >> >| status | ACTIVE >> > | >> >| updated | 2015-07-16T08:07:00Z >> > | >> >| OS-EXT-STS:task_state | image_uploading >> > | >> >| OS-EXT-SRV-ATTR:host | compute >> > | >> >| key_name | ses >> > | >> >| image | Ubuntu 14.04 >> > (3736af94-b25e-4b8d-96fd-fd5949bbd81e) | >> >| OS-EXT-STS:vm_state | active >> > | >> >| OS-EXT-SRV-ATTR:instance_name | instance-0000000d >> > | >> >| OS-SRV-USG:launched_at | 2015-05-09T17:28:09.000000 >> > | >> >| OS-EXT-SRV-ATTR:hypervisor_hostname | compute.lab.internal >> > | >> >| flavor | flavor2 (2) >> > | >> >| id | >> > f2365fe4-9b30-4c24-b7b9-f7fcb4165160 | >> >| security_groups | [{u'name': u'default'}] >> > | >> >| OS-SRV-USG:terminated_at | None >> > | >> >| user_id | 61096c639d674e4cb8bf487cec01432a >> > | >> >| name | non-test >> > | >> >| created | 2015-05-09T17:27:48Z >> > | >> >...etc >> > >> >Any ideas why this happens? All logs are clear, no errors or anything. >> >And it happens at random so no 'debug' log available... >> > >> >_______________________________________________ >> >OpenStack-operators mailing list >> >[email protected] >> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > -- > David W. > Unix, because every barista in Seattle has an MCSE. > > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Twitter: @serverascode Blog: serverascode.com _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
